search

kubernetes-sigs / wg-policy-prototypes

A place for policy work group related proposals and prototypes.
Apache License 2.0
64 stars 39 forks source link

Checklist for writing PolicyReport KEP #112

Closed anusha94 closed 8 months ago

anusha94 commented 1 year ago

The Policy WG presented to SIG-Auth on 7th Dec, 2022 and we have their approval and support to submit a KEP to promote the Policy Report CRD to an official Kubernetes API! :tada:

We want to cleanup on the APIs and make any other changes that are needed before we write and submit the KEP. The below checklist (not final) is to track all such items. Feel free to update this list or comment if there are any concerns.

Tasks

Stakeholders

gparvin commented 1 year ago

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

sunstonesecure-robert commented 1 year ago

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

fjogeleit commented 1 year ago

Current state of api/client forks

k8s-triage-robot commented 1 year ago

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

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

You can:

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

/lifecycle stale

k8s-triage-robot commented 9 months ago

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:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 8 months ago

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:

You can:

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

/close not-planned

k8s-ci-robot commented 8 months ago

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

In response to [this](https://github.com/kubernetes-sigs/wg-policy-prototypes/issues/112#issuecomment-1963682467): >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][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
Ais8Ooz8 commented 7 months ago

@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?

Ais8Ooz8 commented 7 months ago

/reopen /remove-lifecycle rotten

k8s-ci-robot commented 7 months ago

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

In response to [this](https://github.com/kubernetes-sigs/wg-policy-prototypes/issues/112#issuecomment-2001951859): >/reopen >/remove-lifecycle rotten Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.