Bug 1790440: Fix reinitialization of deny-all NetworkPolicy state on restart #96
Conversation
|
/retitle Bugzilla 1790440: Fix reinitialization of deny-all NetworkPolicy state on restart |
openshift-ci-robot
changed the title
openshift-ci-robot
added
the
size/XS
|
/bugzilla refresh |
|
@juanluisvaladas: No Bugzilla bug is referenced in the title of this pull request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/retitle Bug 1790440: Fix reinitialization of deny-all NetworkPolicy state on restart |
openshift-ci-robot
changed the title
|
@juanluisvaladas: This pull request references Bugzilla bug 1790440, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci-robot
added
the
bugzilla/valid-bug
|
/hold |
openshift-ci-robot
added
the
do-not-merge/hold
juanluisvaladas
force-pushed
the
fix-netpol-init
branch
from
0c8da77
to
df77416
Compare
openshift-ci-robot
added
size/M
juanluisvaladas
force-pushed
the
fix-netpol-init
branch
2 times, most recently
from
79a8743
to
acc2d80
Compare
|
/hold cancel |
openshift-ci-robot
removed
the
do-not-merge/hold
juanluisvaladas
force-pushed
the
fix-netpol-init
branch
2 times, most recently
from
1661e9d
to
a97ba8b
Compare
|
/retest |
If a project has only a deny-all rule and pods running on it, npNameSpace.inUse was set to false, this commit sets it to true. If inUse is set to false, the node will not update the npNamespace if new rules are created until new pods are created. More details on BZ#1790440
juanluisvaladas
force-pushed
the
fix-netpol-init
branch
from
a97ba8b
to
d66eead
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, juanluisvaladas The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
/test e2e-aws-upgrade |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@juanluisvaladas: All pull requests linked via external trackers have merged. Bugzilla bug 1790440 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherry-pick release-4.3 |
|
@juanluisvaladas: new pull request created: #98 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherry-pick release-4.2 |
|
@palonsoro: new pull request created: #99 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
If a project has only a deny-all rule and pods running on it,
npNameSpace.inUse was set to false, this commit sets it to true.
If inUse is set to false, the node will not update the
npNamespace if new rules are created until new pods are created.
More details on BZ#1790440