Skip to content

Commit 1ffb557

Browse files
committed
OSDOCS-14323: updates day 2 operation limitation
1 parent 1de0f04 commit 1ffb557

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

modules/nw-udn-limitations.adoc

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ While user-defined networks (UDN) offer highly customizable network configuratio
1111
//Check on the removal of the DNS limitation for 4.18 or 4.17.z.
1212
* *DNS limitations*:
1313
** DNS lookups for pods resolve to the pod's IP address on the cluster default network. Even if a pod is part of a user-defined network, DNS lookups will not resolve to the pod's IP address on that user-defined network. However, DNS lookups for services and external entities will function as expected.
14-
** When a pod is assigned to a primary UDN, it can access the Kubernetes API (KAPI) and DNS services on the cluster's default network.
14+
** When a pod is assigned to a primary UDN, it can access the Kubernetes API (KAPI) and DNS services on the cluster's default network.
1515
1616
* *Initial network assignment*: You must create the namespace and network before creating pods. Assigning a namespace with pods to a new network or creating a UDN in an existing namespace will not be accepted by OVN-Kubernetes.
1717
@@ -20,4 +20,6 @@ While user-defined networks (UDN) offer highly customizable network configuratio
2020

2121
* *Health check limitations*: Kubelet health checks are performed by the cluster default network, which does not confirm the network connectivity of the primary interface on the pod. Consequently, scenarios where a pod appears healthy by the default network, but has broken connectivity on the primary interface, are possible with user-defined networks.
2222
23-
* *Network policy limitations*: Network policies that enable traffic between namespaces connected to different user-defined primary networks are not effective. These traffic policies do not take effect because there is no connectivity between these isolated networks.
23+
* *Network policy limitations*: Network policies that enable traffic between namespaces connected to different user-defined primary networks are not effective. These traffic policies do not take effect because there is no connectivity between these isolated networks.
24+
25+
* *Creation and modification limitation*: The `ClusterUserDefinedNetwork` CR and the `UserDefinedNetwork` CR cannot be modified after being created.

0 commit comments

Comments
 (0)