-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
k8s.io Group Protection #2337
Comments
#2331 created for migrating the old keps into new template. |
/sig api-machinery |
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. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. 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. |
Enhancement Description
API groups are organized by namespace, similar to java packages.
authorization.k8s.io
is one example. When users createCRDs, they get to specify an API group and their type will be injected into that group by the kube-apiserver.
The
*.k8s.io
or*.kubernetes.io
groups are owned by the Kubernetes community and protected by API review (see What APIs need to be reviewed,to ensure consistency and quality. To avoid confusion in our API groups and prevent accidentally claiming a
space inside of the kubernetes API groups, the kube-apiserver needs to be updated to protect these reserved API groups.
This KEP proposes adding an
api-approved.kubernetes.io
annotation to CustomResourceDefinition. This is only needed ifthe CRD group is
k8s.io
,kubernetes.io
, or ends with.k8s.io
,.kubernetes.io
. The value should be a link to ato a URL where the current spec was approved, so updates to the spec should also update the URL.
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: