User or Developer story

As a WMCO developer, I want to incorporate CI signal of the openshift-e2e-tests suite in the WMCO repository so that it checks for Windows nodes test coverage with every new k8s library bump.

Description

This story involves creating a job in the WMCO within the existing OpenShift test suite framework at https://github.com/openshift/origin/tree/master/test/extended.

The initial step included setting up a simple test to validate Windows workloads (https://github.com/openshift/origin/pull/29190) and the number of tests can be grow to ensure that OCP/OKD can handle Windows nodes effectively.

This task requires coordination with existing CI processes and should integrate seamlessly with current testing practices, making sure that the presence of Windows nodes doesn’t disrupt other test functionalities in the origin test suite. 

A placeholder PR was opened https://github.com/openshift/release/pull/55796  to pilot the integration of openshift-e2e-test using ovn-hybrid networking in AWS as the target plaform

Required

• Integrate the new tests with the current CI pipeline to ensure they run conditionally, based on the presence of Windows nodes.

Nice to have

• Detailed logging and reporting for the Windows-specific tests to aid in troubleshooting and improvements.

  Engineering Details

• The primary repository involved is https://github.com/openshift/origin., where the test definition lives
• The setup for tests does not provision new Windows nodes but assumes their presence.
• References to previous discussions and PRs related to this effort
  https://redhat-internal.slack.com/archives/CK1AE4ZCK/p1728933833596349?thread_ts=1721917091.505859&cid=CK1AE4ZCK 

Acceptance Criteria

• A new directory for Windows-specific tests is successfully created in the OpenShift test suite.
• The initial test runs successfully and validates a basic Windows node containing the required version annotation without causing disruptions to other tests.
• The new tests are integrated into the CI pipeline and are only triggered when Windows nodes are detected.