Bug 1932781 - NetworkPolicies are not enforced immediately upon creation
Summary: NetworkPolicies are not enforced immediately upon creation
Keywords:
Status: CLOSED DUPLICATE of bug 1950283
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.8.0
Assignee: Andrew Stoycos
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-25 09:09 UTC by Andy Bartlett
Modified: 2021-05-07 14:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-07 14:10:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andy Bartlett 2021-02-25 09:09:01 UTC
Description of problem:

My customer is seeing the following:

Our customer is experiencing a delay (of sometimes 10 minutes) between the creation of a NetworkPolicy and its enforcement. For example, when they create a NetworkPolicy and immediately a Pod thereafter, the Pod is not affected by a default deny egress rule. They're wondering whether Red Hat knows about this and/or has seen similar cases?

This cluster has 

Version-Release number of selected component (if applicable):

OCP 4.6.16

How reproducible:

less than 100%

Steps to Reproduce:
1.
2.
3.

Actual results:

As mentioned above:

when they create a NetworkPolicy and immediately a Pod thereafter, the Pod is not affected by a default deny egress rule this can sometimes be up to 10 minutes.

Expected results:


Additional info:

Comment 5 Andrew Stoycos 2021-05-07 14:10:46 UTC

*** This bug has been marked as a duplicate of bug 1950283 ***


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