-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
OCPBUGS#42701: Updated the disableMultiNetwork parameter in Network A… #86936
base: main
Are you sure you want to change the base?
Conversation
@dfitzmau: This pull request references Jira Issue OCPBUGS-42701, 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. |
@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. |
699ea1f
to
e430d39
Compare
🤖 Wed Jan 15 17:09:55 - Prow CI generated the docs preview: |
ae1507f
to
9986c5d
Compare
9986c5d
to
fb75a2e
Compare
@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. |
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.
Considering we do not modify API descriptions -- LGTM
| disableMultiNetwork specifies whether or not multiple pod network | ||
support should be disabled. If unset, this property defaults to | ||
'false' and multiple network support is enabled. | ||
| "disableMultiNetwork defaults to 'false' and this setting enables the pod multi-networking capability. disableMultiNetwork when set to 'true' at cluster install time does not install the components, typically the Multus CNI and the network-attachment-definition CRD, that enable the pod multi-networking capability. Setting the parameter to 'true' might be useful when you need install third-party CNI plugins, but these plugins are not supported by Red Hat. Changing the parameter value as a postinstallation cluster task has no effect. |
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.
Changing the parameter value as a postinstallation cluster task has no effect.
I prefer is not allowed.
@dougbtv PTAL |
I'm good with "is not allowed", too. It is certainly more direct. "Has no effect" is also true, but, Peng has a point. |
PEER REVIEWER: THIS IS AN UNUSUAL UPDATE FOR THE DOCS TEAM AS THE UPDATE HAPPENS IN AN ENGINEERING REPO BUT FOR REVIEW PURPOSES I CREATED THIS PR. IDEALLY REVIEW THE CONTENT ON openshift/api#2143
Version(s):
4.12+
Issue:
OCPBUGS-42701
Link to docs preview:
disableMultiNetwork
Resources: