-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OCPBUGS#38352: Updated the Supported network plugin feature matrix table #80365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@dfitzmau: This pull request references Jira Issue OCPBUGS-38352, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
|
🤖 Wed Sep 04 08:50:54 - Prow CI generated the docs preview: |
82c18e8 to
86b8f65
Compare
86b8f65 to
7ec0c4e
Compare
7ec0c4e to
d9a482a
Compare
2a1ddd1 to
fa2b247
Compare
47f3f64 to
6614031
Compare
dbc0328 to
5cd534d
Compare
|
@dfitzmau: No Jira issue is referenced in the title of this pull request. In response to this:
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. |
| 1. Egress router for OVN-Kubernetes supports only redirect mode. | ||
| 2. IPv6 is supported only on bare metal, vSphere, {ibm-power-name}, {ibm-z-name}, and Red Hat OpenStack clusters. | ||
| 2. IPv6 single-stack networking is only supported on bare metal, {ibm-power-name}, {ibm-z-name}, and {rh-openstack-first} clusters. You must enable IPv6 access for your image registry to prevent network connectivity issues when you need to pull images from the registry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not equivalent. I think the intent of the "IPv6" support was actually dual stack. Single stack only works on baremetal right now.
I think this needs to be rewritten to say this section is for dual stack and then the point below should be changed to say that IPv6 single stack is supported only on baremetal, instead of the exclusion list (which is technically not even complete now since IPv6 isn't supported on the cloud platforms either at this point).
c4c2d48 to
16dc10b
Compare
|
/lgtm |
|
/label merge-review-needed |
jeana-redhat
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few tiny things caught my eye while scanning. Nothing crucial, lmk whether you want to address at this time.
/remove-label merge-review-in-progress
/remove-label merge-review-needed
16dc10b to
c91e14f
Compare
|
New changes are detected. LGTM label has been removed. |
|
@dfitzmau: 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. |
|
/cherrypick enterprise-4.17 |
|
/cherrypick enterprise-4.16 |
|
@dfitzmau: new pull request created: #81417 In response to this:
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. |
|
/cherrypick enterprise-4.15 |
|
/cherrypick enterprise-4.14 |
|
/cherrypick enterprise-4.13 |
|
/cherrypick enterprise-4.12 |
|
@dfitzmau: #80365 failed to apply on top of branch "enterprise-4.16": In response to this:
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. |
|
@dfitzmau: #80365 failed to apply on top of branch "enterprise-4.15": In response to this:
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. |
|
@dfitzmau: #80365 failed to apply on top of branch "enterprise-4.14": In response to this:
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. |
|
@dfitzmau: #80365 failed to apply on top of branch "enterprise-4.13": In response to this:
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. |
|
@dfitzmau: #80365 failed to apply on top of branch "enterprise-4.12": In response to this:
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. |
Version(s):
4.12+
Issue:
OCPBUGS-38352
Link to docs preview:
Supported network plugin feature matrix - OVNK
Add info: