-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add conformance test for .spec.Priority
field in ANP
#113
Add conformance test for .spec.Priority
field in ANP
#113
Conversation
✅ Deploy Preview for kubernetes-sigs-network-policy-api ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/test network-policy-api-crd-e2e |
@tssurya: The specified target(s) for
Use 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. |
/test pull-network-policy-api-crd-e2e |
}, clientPod) | ||
framework.ExpectNoError(err, "unable to fetch the server pod") | ||
// draco-malfoy-0 is our client pod in slytherin namespace | ||
// ensure ingress is PASSED to gryffindor from slytherin - the baseline admin network policy ALLOW should take effect |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we really tell the difference here between PASS and ALLOW?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i.e there's not really a way to verify wether it was
- an Explicit ANP Allow ||
- an Explicit BANP Allow ||
- an full pass through to Allow
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess you could eliminate 3. with a large-scale baseline deny
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah measuring pass and allow has been tricky actually.. good point here.
if there is something to catch this underneath like we do in the integration tests:
t.Run("Should support a 'pass-egress' policy for ANP and respect the match for network policy", func(t *testing.T) { |
be3456e
to
459b858
Compare
This commit adds tests that check if the .spec.Priority field is respected and works as expected. Note that we use `Pods` field to express Subject and Peers so that we test that aspect unlike the rest of the tests so far which have always used `Namespaces` aspect. Signed-off-by: Surya Seetharaman <suryaseetharaman.9@gmail.com>
459b858
to
c43707a
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: astoycos, 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 |
This commit adds tests that check if the
.spec.Priority
field is respected and worksas expected.
Note that we use
Pods
field to expressSubject and Peers so that we test that aspect
unlike the rest of the tests so far which
have always used
Namespaces
aspect.Looking good here: