-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DNM] Pre merge testing server side apply; Unblock QE #2116
[DNM] Pre merge testing server side apply; Unblock QE #2116
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tssurya 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 |
@tssurya This PR did not help. Looking at the code I believe the change is in rule of policy YAML specifically use of namespaceSelector. egress: - name: "deny-ns-test1" action: "Deny" to: - namespaces: namespaceSelector: matchLabels: kubernetes.io/metadata.name: test1 I modified the policy to have rule to see it work. ingress: - name: "default-allow-ns" action: "Allow" from: - namespaces: matchLabels: kubernetes.io/metadata.name: test1 Is getting rid of namespaceSelector intended change? What is the reason for change? |
@asood-rh : correct see commit3 511e583#diff-492a3f7092344236a03a5163bb32140d721866486dfb3bf62326153f1bf292de See kubernetes-sigs/network-policy-api#196 for the why did we have to do this/reason. So this PR actually helps bring us in parity with CNO. (it helps except you need to adjust the yamls) Is getting rid of namespaceSelector intended change?: yes it is intended |
@JoeAldinger : we also need to update our 4.16 docs to reflect the breaking API change compared to 4.15 and 4.14 |
2e86e24
to
b1b3c90
Compare
Signed-off-by: Surya Seetharaman <[email protected]>
b1b3c90
to
2944dc9
Compare
@tssurya: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
cc @asood-rh : this should unblock you.