Skip to content
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

RFC: how to provide a list of policies to Rancher Manager #7

Closed
flavio opened this issue Jul 15, 2022 · 0 comments · Fixed by #11 or #12
Closed

RFC: how to provide a list of policies to Rancher Manager #7

flavio opened this issue Jul 15, 2022 · 0 comments · Fixed by #11 or #12
Assignees
Labels
enhancement New feature or request

Comments

@flavio
Copy link
Member

flavio commented Jul 15, 2022

While working on the Rancher Manager integration, we need to find a way to show a list of the Kubewarden policies that exist.

Right now there's an hard-coded list of policies as a temporary workaround, but this is not a viable solution.

The data needed by Rancher manager is:

  • List of available policies
  • For each policy:
    • Name, version, description, validation/mutation, types of operations (CREATE, DELETE, ...), types of resources (Pod, Service, ...), ... basically all the information that is inside of the policy metadata
    • URL of the policy: where the policy is found
    • "Questions raw data": this is a yaml object that describes the settings a policy takes. Using this data the UI builds a tailor-made html form that is used by the user to configure the policy.
    • Signature status: is the policy signed or not

Right now the hard coded values can be found here.

Acceptance criteria

  • Write a RFC that shows possible solution(s) about how to make this data available to Rancher Manager
  • The solution must take into consideration air-gapped environments
  • Bonus: it would be nice to have a way to group related policies together. For example, have a "PSP best practices" group that allows users to easily find all the policies that are related to PSP. The same could be done for "Security best practices", which could include some PSPs, signature verification and some other conformance policies.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
2 participants