-
Notifications
You must be signed in to change notification settings - Fork 39
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
CIS Benchmarks -> Policy Report Generator #29
Comments
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
|
/remove-lifecycle stale. |
|
/assign @mritunjaysharma394 |
|
@JimBugwadia: GitHub didn't allow me to assign the following users: mritunjaysharma394. Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. 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. |
|
@mritunjaysharma394 - please comment on this issue with "/assign @mritunjaysharma394". |
|
/assign @mritunjaysharma394 |
|
/remove-lifecycle stale |
The Policy WG is defining a Policy Report CRD to help unify outputs from multiple policy engines. This helps cluster-admins with managing clusters as policy results can be viewed and managed easily as Kubernetes resources from any Kubernetes management tool (kubectl, dashboard, Octant, etc.)
The project scope is to create a tool that periodically runs a CIS benchmark check like kube-bench and produces a policy report. Additional options could be to integrate the Policy Report into OSS upstream tools like dashboard and/or Octant.
The text was updated successfully, but these errors were encountered: