Skip to content

Make the OwnerReferencesPermissionEnforcement admission plugin reusable by external extension API server #133891

Open

Description

@ialidzhikov

What would you like to be added?

The OwnerReferencesPermissionEnforcement admission plugin:

Type: Validating.

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.

Activity

  1. added
    needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.
    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
    on Sep 4, 2025
  2. ialidzhikov commented on Sep 4, 2025

    @ialidzhikov
    ContributorAuthor

    /sig api-machinery

  3. added
    sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.
    and removed
    needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.
    on Sep 4, 2025
  4. 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
  5. BenTheElder commented on Sep 23, 2025

    @BenTheElder
    Member

    cc @kubernetes/sig-api-machinery-leads

  6. ialidzhikov commented on Sep 24, 2025

    @ialidzhikov
    ContributorAuthor

    /assign

  7. yongruilin commented on Oct 16, 2025

    @yongruilin
    Contributor

    /triage accepted

  8. added
    triage/acceptedIndicates an issue or PR is ready to be actively worked on.
    and removed
    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
    on Oct 16, 2025
  9. k8s-triage-robot commented on Oct 17, 2026

    @k8s-triage-robot

    This issue has not been updated in over 1 year, and should be re-triaged.

    You can:

    • Confirm that this issue is still relevant with /triage accepted (org members only)
    • Close this issue with /close

    For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

    /remove-triage accepted

  10. added
    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
    and removed
    triage/acceptedIndicates an issue or PR is ready to be actively worked on.
    on Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions