-
Notifications
You must be signed in to change notification settings - Fork 28
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
[Policy Assistant] explain command: support setting (B)ANPs via CLI arg #201
Comments
/assign |
Hey, @huntergregory can you share more details about the task? Is it about reading (B)ANPs from a cluster or file path? Is there a weekly meeting about this project where I can join and ask these kinds of questions? |
Hey Nikola, thanks for looking to pick this up. Just fixed this issue's description, let me know if you have any questions.
Yes! Would be great to have you. We meet every other Tuesday (some more details at this link) |
I think the CLI already has the arguments we need (code is in analyze.go). I think they are like To create the CLI binary:
|
Thanks for the info Hunter.I already started working on this, but more questions arose. Should cyclonus always work with the (B)ANPs or they should be enabled/disabled via an arguments? What is the expected behavior if one of the request fail while trying to get info from the api-server? |
ideally, we would just log a warning message that ANP isn't defined instead of saying there's an error. |
Successor to #153. Child issue of #150.
Right now we have AdminNetworkPolicies hard-coded (referenced in analyze.go). A user should be able to specify NetworkPolicy, AdminNetworkPolicy, and the BaselineAdminNetworkPolicy by:
Code in question:
network-policy-api/cmd/policy-assistant/pkg/cli/analyze.go
Lines 96 to 128 in 669dfbc
The text was updated successfully, but these errors were encountered: