You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'd like to propose a repo to hold admission policies that we can recommend to users, especially in cases where a in-tree solution would take a long time or is not viable. Having a repo would make these policies more discoverable, than having a reference to them in a KEP somewhere.
We thought of this while coming up with the following KEP: kubernetes/enhancements#5039 (KEP 5040), where we would like to give users a Validating Admission Policy (VAP) that they can install into their clusters.
The text was updated successfully, but these errors were encountered:
New repo, staging repo, or migrate existing
new repository
Is it a staging repo?
no
Requested name for new repository
sigs.k8s.io/admission-policies
Which Organization should it reside
kubernetes-sigs
Who should have admin access?
No response
Who should have write access?
No response
Who should be listed as approvers in OWNERS?
No response
Who should be listed in SECURITY_CONTACTS?
No response
What should the repo description be?
No response
What SIG and subproject does this fall under?
sig-arch
Please provide references to appropriate approval for this new repo
Email thread - https://groups.google.com/g/kubernetes-sig-architecture/c/f-skoro0ZE4/m/L0g6WrknDwAJ
Additional context for request
We'd like to propose a repo to hold admission policies that we can recommend to users, especially in cases where a in-tree solution would take a long time or is not viable. Having a repo would make these policies more discoverable, than having a reference to them in a KEP somewhere.
We thought of this while coming up with the following KEP: kubernetes/enhancements#5039 (KEP 5040), where we would like to give users a Validating Admission Policy (VAP) that they can install into their clusters.
The text was updated successfully, but these errors were encountered: