-
Notifications
You must be signed in to change notification settings - Fork 8
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
e2e: default policy test #1007
e2e: default policy test #1007
Conversation
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.
Please also proof-read your code comments.
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.
Please make sure to also push your changes when you're resolving review comments.
728f791
to
6f53e36
Compare
I'm sorry, i was working on the issue right now and resolved the conflicts while adapting the changes to the code base. Won't happen again. |
6f53e36
to
077b95a
Compare
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.
LGTM, but please address outstanding comments.
Take a look at the requirements of https://github.com/edgelesssys/contrast/actions/runs/11934103702/workflow?pr=1007#L18-L24, too. Tests are usually |
077b95a
to
de5ae95
Compare
e2e: Add waiting mechanism and correct event watching/listing to default policy test Structure changes to deploy.go e2e: rework and fetch event from the watch.Event directly e2e: Add default policy into policy test package
de5ae95
to
4b88361
Compare
Podvms come with a default policy, which should usually be a "SetPolicy only" policy. The implemented e2e test ensures that no wrong default policy (i.e. allow-all) is included, by starting a container without any policy annotation and waiting for the Kata runtime event FailedCreatePodSandBox, which indicates that the container start failed as expected.