Checklist for writing PolicyReport KEP about wg-policy-prototypes HOT 10 CLOSED

Additional stakeholder:
Open Cluster Management CNCF sandbox project https://open-cluster-management.io/ and Red Hat ACM product https://www.redhat.com/en/resources/advanced-cluster-management-kubernetes-datasheet

from wg-policy-prototypes.

can we change the issue title to mention PolicyReport so in Slack links people see what it refers to? thanks!

from wg-policy-prototypes.

Current state of api/client forks

• Policy Reporter uses its own fork/copy of the PolicyReport Go APIs and Clients
• jsPolicy uses its own fork/copy of the PolicyReport Go APIs and Clients
• trivy-operator-polr-adapter uses its own fork/copy of the PolicyReport Go APIs and Clients
• tracee-polr-adapter uses the Kyverno APIs and Client as dependency
• Falcosidekick uses the API and Client from kube-bench-adapter (outdated)
• kube-bench adapter uses the API and Client from kubernetes-sigs/wg-policy-prototypes
• KubeArmor adapter uses the API and Client from kubernetes-sigs/wg-policy-prototypes
• Trivy Adapter adapter uses the API and Client from kubernetes-sigs/wg-policy-prototypes
• vulnerability-operator uses the API and Client from kubernetes-sigs/wg-policy-prototypes

from wg-policy-prototypes.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

from wg-policy-prototypes.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

from wg-policy-prototypes.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

from wg-policy-prototypes.

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

from wg-policy-prototypes.

@anusha94 @fjogeleit

raise PRs in repositories consuming PolicyReport CRD with any changes

Maybe we should start by creating issues in these repositories and thereby starting discussions?

from wg-policy-prototypes.

/reopen
/remove-lifecycle rotten

from wg-policy-prototypes.

@Ais8Ooz8: You can't reopen an issue/PR unless you authored it or you are a collaborator.

from wg-policy-prototypes.