-
Bug
-
Resolution: Unresolved
-
Normal
-
4.17.z, 4.18.z
-
Quality / Stability / Reliability
-
False
-
-
3
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The following release note is inaccurate: Previously, a pod with an IP address in an OVN-Kubernetes Localnet network was unreachable by other pods that ran on the same node but used the default network for communication. Communication between pods on different nodes was not impacted by this communication issue. With this release, communication between a Localnet pod and a default network pod that both run on the same node is possible. This note exists in the 4.19, 4.18, and 4.17 release notes document. See the following bugs for the original text: * 4.19 bug = https://issues.redhat.com/browse/OCPBUGS-43004 * 4.18 bug = https://issues.redhat.com/browse/OCPBUGS-55016 * 4.17 bug = https://issues.redhat.com/browse/OCPBUGS-56244 See https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html-single/release_notes/index
Version-Release number of selected component (if applicable):
4.17 to 4.19
Expected results:
"Previously, a pod with an IP address in an OVN-Kubernetes `Localnet` network plugged into br-ex was unreachable by other pods that ran on the same node but used the default network for communication. Communication between pods on different nodes was not impacted. With this release, communication between a `Localnet` pod and a default network pod that both run on the same node is possible, with a caveat: the IP addresses used in the localnet must be within the same subnet as the host network. (link:https://issues.redhat.com/browse/OCPBUGS-43004[OCPBUGS-43004])"