CORENET-7538: Add EgressIPNodeSelector feature gate

[tssurya]

Introduce the EgressIPNodeSelector feature gate for the ovn-kubernetes networking component, enabled in DevPreviewNoUpgrade and TechPreviewNoUpgrade feature sets.

Enhancement: ovn-kubernetes/ovn-kubernetes#6801

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@tssurya: This pull request references CORENET-7538 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Introduce the EgressIPNodeSelector feature gate for the ovn-kubernetes networking component, enabled in DevPreviewNoUpgrade and TechPreviewNoUpgrade feature sets.

Enhancement: ovn-kubernetes/ovn-kubernetes#6801

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hello @tssurya! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[everettraven]

/lgtm
/approve

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change
/test minor-e2e-upgrade-minor

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [everettraven]

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

[tssurya]

/lgtm /approve

btw @everettraven did I mention that your response time on PRs in this repo always amazes me? :) I guess you and Joel both rock and not sure how you can have such a good turn around time on some of these PRs. thanks for the review

[tssurya]

/test images

[tssurya]

/verified by CI

[openshift-ci-robot]

@tssurya: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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 openshift-eng/jira-lifecycle-plugin repository.

[tssurya]

/retest-required

[tssurya]

/retest-required

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD 6733660 and 2 for PR HEAD 1ce44c8 in total

[tssurya]

/retest-required

[tssurya]

/retest-required

[tssurya]

/test e2e-azure

[openshift-ci]

@tssurya: all tests passed!

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.