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
{{ message }}
Repository navigation
Make the OwnerReferencesPermissionEnforcement admission plugin reusable by external extension API server #133891
This admission controller protects the access to the metadata.ownerReferences of an object
so that only users with delete permission to the object can change it.
This admission controller also protects the access to metadata.ownerReferences[x].blockOwnerDeletion
of an object, so that only users with update permission to the finalizers
subresource of the referenced owner can change it.
The admission plugin is generic. It makes sense for external extension API server to register and enable it. Said with other words, extension API server to forbid users without delete permissions to set ownerReference to a non-existing object and in this want to delete the object.
#93537 - example from the past how the ResourceQuota admission plugin was made reusable by moving it under k8s.io/apiserver.
Why is this needed?
Move the OwnerReferencesPermissionEnforcement to the k8s.io/apiserver module so that it is usable by extension API servers.
changed the title [-]Move the `OwnerReferencesPermissionEnforcement` admission plugin reusable by external extension API server[/-][+]Make the `OwnerReferencesPermissionEnforcement` admission plugin reusable by external extension API server[/+]on Sep 23, 2025
Activity
ialidzhikov commentedon Sep 4, 2025
/sig api-machinery
[-]Move the `OwnerReferencesPermissionEnforcement` admission plugin reusable by external extension API server[/-][+]Make the `OwnerReferencesPermissionEnforcement` admission plugin reusable by external extension API server[/+]BenTheElder commentedon Sep 23, 2025
cc @kubernetes/sig-api-machinery-leads
ialidzhikov commentedon Sep 24, 2025
/assign
yongruilin commentedon Oct 16, 2025
/triage accepted
k8s-triage-robot commentedon Oct 17, 2026
This issue has not been updated in over 1 year, and should be re-triaged.
You can:
/triage accepted(org members only)/closeFor more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted