-
Notifications
You must be signed in to change notification settings - Fork 1.9k
OSDOCS-14822 UDN NetObserv Content #94271
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
419cf1d to
04eb90b
Compare
|
🤖 Wed Jun 11 19:43:10 - Prow CI generated the docs preview: |
|
/assign @jpinsonneau @jotak |
|
I dont know if we have to explain in detail about creating UDN/CUDN here. Could we link to the networking docs for UDN? |
+1 to that. If we can avoid maintaining their CRs in our doc it would be easier |
|
/label qe-approved |
285973b to
501522c
Compare
|
/label peer-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.
Nice work! Some minor stuff here to look at.
/remove-label peer-review-in-progress
/remove-label peer-review-needed
/label peer-review-done
| [id="network-observability-user-defined-networks_{context}"] | ||
| = User-defined networks | ||
|
|
||
| User-defined networks (UDN) improve the flexibility and segmentation capabilities of the default Layer 3 topology for a Kubernetes pod network by enabling custom Layer 2 and Layer 3 network segments, where all these segments are isolated by default. These segments act as either primary or secondary networks for container pods and virtual machines that use the default OVN-Kubernetes CNI plugin. |
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.
| User-defined networks (UDN) improve the flexibility and segmentation capabilities of the default Layer 3 topology for a Kubernetes pod network by enabling custom Layer 2 and Layer 3 network segments, where all these segments are isolated by default. These segments act as either primary or secondary networks for container pods and virtual machines that use the default OVN-Kubernetes CNI plugin. | |
| User-defined networks (UDN) improve the flexibility and segmentation capabilities of the default Layer 3 topology for a Kubernetes pod network by enabling custom Layer 2 and Layer 3 network segments, where all these segments are isolated by default. These segments act as primary or secondary networks for container pods and virtual machines that use the default OVN-Kubernetes CNI plugin. |
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.
Someone will probably want to update that here then, too, so it's consistent: https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/networking/multiple-networks#about-user-defined-networks
|
/label merge-review-needed |
c51924f to
a5e2cab
Compare
|
Squashed commit. Checks running again. |
|
@gwynnemonahan: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
OSDOCS-14822 UDN NetObserv Content
Version(s):
Merge to only the
no-1.9branch - no cherrypicks are required.I will open one PR against main to incorporate all of the NetObserv content just before its GA.
Cherry-pick to OCP 4.12, 4.14, 4.16+
Issue:
https://issues.redhat.com/browse/OSDOCS-14822
Link to docs preview:
QE review:
Additional information: