Skip to content

CORENET-6100: Regenerate apply configurations for OVN no-overlay mode - #349

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
ricky-rav:nooverlay
Mar 20, 2026
Merged

CORENET-6100: Regenerate apply configurations for OVN no-overlay mode#349
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
ricky-rav:nooverlay

Conversation

@ricky-rav

Copy link
Copy Markdown

Vendor openshift/api changes that add no-overlay mode support to the Network operator API. This regenerates the apply configurations to include:

  • DefaultNetworkTransport field
  • DefaultNetworkNoOverlayOptions field
  • BGPManagedConfig field
  • NoOverlayOptions struct
  • BGPManagedConfig struct

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 1, 2025
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Dec 1, 2025
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Dec 1, 2025
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Dec 4, 2025
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Dec 4, 2025
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Dec 4, 2025
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 8, 2025
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 8, 2025
@ricky-rav
ricky-rav force-pushed the nooverlay branch 2 times, most recently from 0e03f16 to 6c1691c Compare December 8, 2025 11:27
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Dec 8, 2025
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Dec 15, 2025
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Dec 15, 2025
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
zhaozhanqi pushed a commit to zhaozhanqi/client-go that referenced this pull request Dec 24, 2025
zhaozhanqi pushed a commit to zhaozhanqi/client-go that referenced this pull request Dec 24, 2025
zhaozhanqi added a commit to zhaozhanqi/client-go that referenced this pull request Dec 24, 2025
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Jan 7, 2026
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
@ricky-rav ricky-rav changed the title [WIP] Regenerate apply configurations for OVN no-overlay mode CORENET-6390:[WIP] Regenerate apply configurations for OVN no-overlay mode Jan 7, 2026
@openshift-ci-robot

openshift-ci-robot commented Jan 7, 2026

Copy link
Copy Markdown

@ricky-rav: This pull request references CORENET-6390 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 "4.22.0" version, but no target version was set.

Details

In response to this:

Vendor openshift/api changes that add no-overlay mode support to the Network operator API. This regenerates the apply configurations to include:

  • DefaultNetworkTransport field
  • DefaultNetworkNoOverlayOptions field
  • BGPManagedConfig field
  • NoOverlayOptions struct
  • BGPManagedConfig struct

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 7, 2026
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 7, 2026
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 7, 2026
@ricky-rav
ricky-rav force-pushed the nooverlay branch 2 times, most recently from 8a9d607 to 36567df Compare January 7, 2026 18:09
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Jan 23, 2026
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Jan 26, 2026
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
@ricky-rav
ricky-rav force-pushed the nooverlay branch 2 times, most recently from dc1e789 to fa73906 Compare January 28, 2026 11:41
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Jan 28, 2026
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Feb 3, 2026
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Feb 4, 2026
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 24, 2026
@ricky-rav
ricky-rav force-pushed the nooverlay branch 2 times, most recently from db9b47e to ad1e6b6 Compare February 24, 2026 18:20
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 24, 2026
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Feb 24, 2026
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Feb 25, 2026
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Feb 27, 2026
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Mar 5, 2026
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
ricky-rav pushed a commit to ricky-rav/cluster-network-operator that referenced this pull request Mar 5, 2026
openshift/api#2537
openshift/client-go#349

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
@openshift-ci-robot

openshift-ci-robot commented Mar 6, 2026

Copy link
Copy Markdown

@ricky-rav: This pull request references CORENET-6100 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 "4.22.0" version, but no target version was set.

Details

In response to this:

Vendor openshift/api changes that add no-overlay mode support to the Network operator API. This regenerates the apply configurations to include:

  • DefaultNetworkTransport field
  • DefaultNetworkNoOverlayOptions field
  • BGPManagedConfig field
  • NoOverlayOptions struct
  • BGPManagedConfig struct

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.

@JoelSpeed

Copy link
Copy Markdown
Contributor

@ricky-rav Did you mean to commit so many empty files? And the claude bits too?

@ricky-rav

Copy link
Copy Markdown
Author

@ricky-rav Did you mean to commit so many empty files? And the claude bits too?

Not really. Let me fix that.

Vendor openshift/api changes that add no-overlay mode support to the
Network operator API. This regenerates the apply configurations to
include:
- Transport field
- NoOverlayConfig field
- BGPManagedConfig field
- NoOverlayConfig struct
- BGPManagedConfig struct

Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
@openshift-ci

openshift-ci Bot commented Mar 19, 2026

Copy link
Copy Markdown
Contributor

@ricky-rav: 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.

@JoelSpeed

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci

openshift-ci Bot commented Mar 19, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, ricky-rav

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:

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

@zhaozhanqi

Copy link
Copy Markdown

/verified by QE pre-merge testing

@openshift-ci-robot

Copy link
Copy Markdown

@zhaozhanqi: This PR has been marked as verified by QE pre-merge testing.

Details

In response to this:

/verified by QE pre-merge testing

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants