Bug 1828387 - NPs on svc not enforced when exposed port and target are different
Summary: NPs on svc not enforced when exposed port and target are different
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.5.0
Assignee: Luis Tomas Bolivar
QA Contact: Jon Uriarte
URL:
Whiteboard:
Depends On:
Blocks: 1828388
TreeView+ depends on / blocked
 
Reported: 2020-04-27 16:05 UTC by Luis Tomas Bolivar
Modified: 2020-07-13 17:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1828388 (view as bug list)
Environment:
Last Closed: 2020-07-13 17:31:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift kuryr-kubernetes pull 221 0 None closed Bug 1828387: Ensure NP are enforced on SVC with different port and target port 2020-06-24 01:22:39 UTC
Launchpad 1875428 0 None None None 2020-04-27 16:05:02 UTC
OpenStack gerrit 723592 0 None MERGED Ensure NP are enforced on SVC with different port and target port 2020-06-24 01:22:39 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:32:09 UTC

Description Luis Tomas Bolivar 2020-04-27 16:05:03 UTC
NP rules are not properly updated on LoadBalancer security groups when the exposed port and the target port does not match

Comment 3 Jon Uriarte 2020-05-07 13:49:17 UTC
Verified in 4.5.0-0.nightly-2020-05-06-003431 on top of OSP 16 compose RHOS_TRUNK-16.0-RHEL-8-20200427.n.0 (with OVS and amphora-driver).

After creating a service that exposes a different port than the one in the pod behind, if a network policy is created for blocking the ingress
traffic to the pod, the security rules are now applied in the load balancer and the service is not reachable.

Comment 4 errata-xmlrpc 2020-07-13 17:31:52 UTC
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:2409


Note You need to log in before you can comment on or make changes to this bug.