-
Notifications
You must be signed in to change notification settings - Fork 42
genpolicy: Introduce UpdateInterfaceRequest rules in genpolicy-settings + tests #329
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
Conversation
2b796a4 to
7e00311
Compare
|
small genpolicy |
9c782e9 to
6172c64
Compare
2d5a839 to
fe06a2b
Compare
fe06a2b to
caf6b58
Compare
caf6b58 to
dc85a8c
Compare
dc85a8c to
05a1609
Compare
| "IPAddresses": [ | ||
| { | ||
| "family": 0, | ||
| "address": "10.244.0.14", |
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.
Our main goal here is to guard Guest's loopback interface, if needed. I don't think it's worth trying to hard-code non-loopback IP addresses.
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.
Okay, I removed the policy checks for IPAddresses
Introduce rules for UpdateInterfaceRequest and genpolicy tests for them. Signed-off-by: Cameron Baird <[email protected]>
Make corresponding updates to sample pod yamls for UpdateInterfaceRequest rules Signed-off-by: Cameron Baird <[email protected]>
05a1609 to
2a9c385
Compare
| metadata: | ||
| name: dummy | ||
| spec: | ||
| runtimeClassName: kata-cc-isolation |
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.
why are we doing kata-cc-isolation here?
|
Dead branch, duplicate of this change: #333 |
Introduce rules for UpdateInterfaceRequest and genpolicy tests for them.