Migrating the Reports API from Kubernetes working group #2
Conversation
Copy the PolicyReport API definition from the Kubernetes working group repository to this one. Signed-off-by: José Guilherme Vanz <[email protected]>
In order to allow a more broard usage of the Reports CRDs rename from from (Cluster)PolicyReport to (Cluster)Report. Signed-off-by: José Guilherme Vanz <[email protected]>
|
Thanks @jvanz! Enjoy your vacation. |
Yes, we should create a new openreports.io group.
yes, we can exclude these for now. |
|
I will merge this PR and then create a new one for the API group change. |
This PR is the first step in migrating the API definition from the Kubernetes Policy Working Group repository to this organization.
After copying the original files, I renamed
ClusterPolicyReporttoClusterReportandPolicyReporttoReport. I made these changes in theapis/reports.x-k8s.io/v1beta2version. However, I’m wondering if we should instead implement this renaming in a new API version and take this opportunity to also change the name toapis/reports.openreports.io/v1beta2. What are your thoughts on this?In this PR, I have not copied some directories, such as
falco-adapter,kube-bench-adapter,kubearmor-adapter,oscal-transformer, andtrivy-adapter. I decided to exclude them because the PR is already quite large, and I would like to review the documentation more carefully to ensure they are right (I have to familiarize with the projects use of the reports 😉 ) . For this reason, I’ll add new subtasks in issue #1 to address these components.Important
I'll be on vacations for several days. Therefore, I'll not be able to respond in that period. Therefore, feel free to take over the PR. Maintainers should be able to change it if necessary.