Skip to content

Conversation

@jherrman
Copy link
Contributor

@jherrman jherrman commented Sep 4, 2025

@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Sep 4, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Sep 4, 2025

@jherrman jherrman force-pushed the virt_bridge-mapping-updates-4.18_CNV-43771 branch from 7ecf7ae to 146ea4c Compare September 16, 2025 13:02
<6> Optionally, for more fine-grained network management, you can configure a virtual LAN (VLAN) ID for the NAD. VMs that use this NAD have an interface that can communicate only with devices that use the same VLAN ID (`200` in this example).
<7> The value of the `namespace` and `name` fields in the `metadata` stanza of the `NetworkAttachmentDefinition` object.
<5> The name of the host's physical network interface, to which the pod's new network interface will be attached. This setting can be reused by multiple NADs. Note that `physicalNetworkName` must match the value of the `spec.desiredState.ovn.bridge-mappings.localnet` field of the `NodeNetworkConfigurationPolicy` object that defines the OVS bridge mapping.
<6> Optional: The maximum transmission unit (MTU) value. If you do not set a value, the Cluster Network Operator (CNO) sets a default MTU value by calculating the difference among the underlay MTU of the primary network interface, the overlay MTU of the pod network, and byte capacity of any enabled features, such as IPsec.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] Vale.Terms: Use '(?<!.*-)operator' instead of 'Operator'.

@sjhala-ccs sjhala-ccs added CNV Label for all CNV PRs branch/enterprise-4.18 labels Sep 16, 2025
@sjhala-ccs sjhala-ccs added this to the Continuous Release milestone Sep 16, 2025
Copy link
Contributor

@sjhala-ccs sjhala-ccs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of suggestions for your consideration. Looks good otherwise. In your PR description, it says this applies to 4.15-4.18. I am not sure if it is possible to cherry pick the changes to 4.15-4.17 if your feature branch is based off enterprise-4.18.

Applying SME review

Kudos to Juan Orti for the feedback

Apply suggestions from code review

Co-authored-by: Shikha Jhala <sjhala@redhat.com>
@jherrman jherrman force-pushed the virt_bridge-mapping-updates-4.18_CNV-43771 branch from 27773ba to e763efe Compare September 18, 2025 13:49
@openshift-ci
Copy link

openshift-ci bot commented Sep 18, 2025

@jherrman: all tests passed!

Full PR test history. Your PR dashboard.

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.

@jherrman
Copy link
Contributor Author

@sjhala-ccs , thank you for the review and the suggestions, they definitely improved the content. I applied them and re-squashed, hopefully the changes are now merge-ready.

As for the cherry-picks to 4.15-4.17, the impacted files look reasonably same-y across those versions, but if the automatic cherry-pick fails, I'll make separate PRs.

Thanks again,
J.

@sjhala-ccs sjhala-ccs merged commit 0499ecc into openshift:enterprise-4.18 Sep 18, 2025
2 checks passed
@sjhala-ccs
Copy link
Contributor

/cherrypick enterprise-4.17

@sjhala-ccs
Copy link
Contributor

/cherrypick enterprise-4.16

@sjhala-ccs
Copy link
Contributor

/cherrypick enterprise-4.15

@openshift-cherrypick-robot

@sjhala-ccs: new pull request created: #99338

In response to this:

/cherrypick enterprise-4.17

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.

@openshift-cherrypick-robot

@sjhala-ccs: #98488 failed to apply on top of branch "enterprise-4.15":

Patch is empty.
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To record the empty patch as an empty commit, run "git am --allow-empty".
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"

In response to this:

/cherrypick enterprise-4.15

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.

@openshift-cherrypick-robot

@sjhala-ccs: new pull request created: #99339

In response to this:

/cherrypick enterprise-4.16

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.

@sjhala-ccs
Copy link
Contributor

/cherrypick enterprise-4.15

@openshift-cherrypick-robot

@sjhala-ccs: new pull request created: #99340

In response to this:

/cherrypick enterprise-4.15

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.

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

Labels

branch/enterprise-4.15 branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 CNV Label for all CNV PRs size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants