When there is a pod (and a svc) with a NP allowing access from a namespace with a give label, and another namespace label is updated to have the allowed label, the NP SG rules that are applied to the initial pod are updated to allow the updated namespace but not the rules on the loadbalancers, so the traffic does not go through.
Verified on an OCP 4.2 cluster (4.2.0-0.nightly-2019-10-02-001405) with Kuryr-controller image from OCP 4.3 (4.3.0-0.ci-2019-10-02-101344), which includes the fix. Verified that the fix does not add new regressions as well. $ oc get pods -n openshift-kuryr kuryr-controller-5744b8d79d-wpdjl -o yaml | grep image image: registry.svc.ci.openshift.org/ocp/4.3-2019-10-02-101344@sha256:313a91b60fb5f49ece7e351ffee86e6f799b4399025d07cff9df8fec5adb5d06 It was not possible to verify on OCP 4.3 cluster as there are no nightly builds available at the moment.
Verified on OCP 4.3.0-0.nightly-2019-10-17-061631 build on top of OSP 13 2019-10-01.1 puddle. release image: registry.svc.ci.openshift.org/ocp/release@sha256:2cafe25ec1ed2dfdec361cde13b4461d2a30194d0b41fbd1c6d3fad5ab34ca05 Related K8s NP upstream test -should allow ingress access from updated namespace- test passed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062