-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Updates UDN docs to include required NS label #86845
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
🤖 Fri Feb 14 14:45:26 - Prow CI generated the docs preview: |
8efc2db
to
89ee31b
Compare
addab0b
to
961e164
Compare
961e164
to
717c5cd
Compare
Developers and administrators can create a user-defined network that is namespace scoped using the custom resource. An overview of the process is as follows: |
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 pod created in the UDN namespace can be configured to have a default, primary, or secondary network. What does statement "This provides the flexibility of a secondary network to the primary network" (line 16) mean?
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.
@weliang1 I didn't write this content. I did contact the original author, but he also wasn't sure exactly what we meant by this. We have a PR (https://github.com/openshift/openshift-docs/pull/87260/files) that expands on L2 and L3 information. I can get this sentence removed in a separate PR because it doesn't make sense.
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.
@weliang1 I didn't write this content. I did contact the original author, but he also wasn't sure exactly what we meant by this. We have a PR (https://github.com/openshift/openshift-docs/pull/87260/files) that expands on L2 and L3 information. I can get this sentence removed in a separate PR because it doesn't make sense.
@stevsmit Agree to remove line 16.
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.
Otherwise, LGTM!
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.
I notice that there are two commits. Please squash to one.
a34b8b7
to
823060f
Compare
823060f
to
26da726
Compare
/assign @ormergi |
f7971a8
to
b74fdcd
Compare
Addresses ocpbugs48423--commit two
b74fdcd
to
ad0e1d0
Compare
@stevsmit: 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. |
/cherry-pick enterprise-4.18 |
@stevsmit: new pull request created: #88638 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.17+
Issue:
https://issues.redhat.com/browse/OCPBUGS-48218 (addresses ovn-kubernetes/ovn-kubernetes#4912),
https://issues.redhat.com/browse/OCPBUGS-49676 (addresses openshift/cluster-network-operator#2619 )
Link to docs preview:
https://86845--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/multiple_networks/primary_networks/about-user-defined-networks.html#considerations-for-udn_about-user-defined-networks
QE review:
Additional information: