[test-operator] Add option to set networkAttachments #1622
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This will allow attaching secondary nics to the tempest pods and use that for the egress traffic to the respective network. Without this all egress traffic flows through the default OCP cluster network and can trigger mtu specific issues for non cluster n/w traffic as cluster n/w force lower MTU based on network backend used. Default is empty list so no secondary interfaces will be attached by default. Related-Issue: OSPRH-6546
karelyatin
added a commit
to karelyatin/nova-operator
that referenced
this pull request
May 3, 2024
Depends-On: openstack-k8s-operators/ci-framework#1622 Related-Issue: OSPRH-6546
karelyatin
added a commit
to karelyatin/nova-operator
that referenced
this pull request
May 3, 2024
Requires to add networkAttachment to tempest pod so it uses ctlplane network for egress traffic instead of the default cluster network which has lower mtu forced(100 less than primary interface for OVNKubernetes backend). Depends-On: openstack-k8s-operators/ci-framework#1622 Related-Issue: OSPRH-6546
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cjeanner The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-bot
bot
merged commit 82ee463
into
openstack-k8s-operators:main
10 of 12 checks passed
openshift-merge-bot bot
pushed a commit
to openstack-k8s-operators/nova-operator
that referenced
this pull request
May 6, 2024
Requires to add networkAttachment to tempest pod so it uses ctlplane network for egress traffic instead of the default cluster network which has lower mtu forced(100 less than primary interface for OVNKubernetes backend). Depends-On: openstack-k8s-operators/ci-framework#1622 Related-Issue: OSPRH-6546
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will allow attaching secondary nics to the tempest pods and use that for the egress traffic to the respective network.
Without this all egress traffic flows through the default OCP cluster network and can trigger mtu specific
issues for non cluster n/w traffic as cluster n/w force lower MTU based on network backend used.
Default is empty list so no secondary interfaces will be attached by default.
Related-Issue: OSPRH-6546
As a pull request owner and reviewers, I checked that: