WIP Add CNV-dependent sig-node CI jobs for AWS/Azure FIPS (release-4.21)

[BhargaviGudi]

Add CNV-dependent sig-node CI jobs for AWS and Azure FIPS on release-4.21.

This PR introduces two new presubmit CI jobs to test sig-node functionality with Container Native Virtualization (CNV) deployed on the cluster.

Changes
New CI Jobs

1. e2e-aws-cnv-sig-node
   - Platform: AWS (using aws-5 cluster profile)
   - Test suite: openshift/nodes/cnv
   - Deploys CNV before running sig-node tests
   - Enables resource watch observers for better debugging
2. e2e-azure-fips-cnv-sig-node
   - Platform: Azure (using azure4 cluster profile)
   - FIPS mode: Enabled
   - Test suite: openshift/nodes/cnv
   - Includes FIPS validation check
   - Deploys CNV before running sig-node tests
   - Enables resource watch observers for better debugging

Files Modified

• ci-operator/config/openshift/origin/openshift-origin-release-4.21.yaml - Added test configurations
• ci-operator/jobs/openshift/origin/openshift-origin-release-4.21-presubmits.yaml - Generated Prow job definitions

Test Plan
Both jobs can be triggered manually on PRs using:

• /test e2e-aws-cnv-sig-node
• /test e2e-azure-fips-cnv-sig-node

The jobs are configured with always_run: false to allow for on-demand testing.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: BhargaviGudi
Once this PR has been reviewed and has the lgtm label, please assign xueqzhan for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/origin/OWNERS
• ci-operator/jobs/openshift/origin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@BhargaviGudi: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-origin-release-4.21-e2e-aws-cnv-sig-node	openshift/origin	presubmit	Presubmit changed
pull-ci-openshift-origin-release-4.21-e2e-azure-fips-cnv-sig-node	openshift/origin	presubmit	Presubmit changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[cpmeadors]

It looks like this job would be optional and would be need to be explicitly executed manually through PRs. This might be good enough for now until we figure out where and how often we need to run these tests. It might make more sense to make these periodic.

[openshift-ci]

@BhargaviGudi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/yamllint	a5be5ad	link	true	/test yamllint
ci/prow/core-valid	a5be5ad	link	true	/test core-valid

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-bot]

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale