-
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
OwnerReference Resource Field #2336
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
OwnerReference Resource Field
OwnerReferences are used to track garbage collection references. Today they use
kind
. This is a serialization formatnot a URL to access on the kube-apiserver. To find a URL, a series of upwards of 20 discovery calls are made to find
every resource in the cluster to find a list of potential resources (URLs more or less). This approximates user intent
and mostly works, but it is inefficient and unnecessarily vulnerable to network outages.
This KEP proposes adding an optional
resource
field to OwnerReferences. If provided, this will be the authoritative value andno lookup or approximation of user intent will be required. If not provided, the
kind
will be used as it is today.If both are provided, old clusters continue to work and new clusters will be more efficient and resilient.
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: