This project is a proof of concept meant to show the viability of the next generation of ReferenceGrant. As a POC, this project provides absolutely no stability, and should never be used in a production environment. If this ever becomes production ready, it will do so exclusively within a kubernetes or kubernetes-sigs repo.
- Show how ReferenceGrant could become part of kubernetes/kubernetes via sig-auth.
- Enable ReferenceGrant to be used more generically, defining the specific reference paths that should be followed.
- Provide a means of authorizing controllers to only access the resources that are directly referenced by resources they are implementing. (For example, a Gateway controller should only be reading from the secrets referenced by a Gateway).
- Provide the foundation for a backfill that could be used to provide similar functionality in earlier Kubernetes versions.
With SIG-Storage adopting ReferenceGrant for cross-namespace storage data sources, it became important for us to transition ReferenceGrant to a more neutral home. This project explores what a transition to a more generic, auth-first approach could look like.
This has been a point of discussion at previous KubeCons, resulting in both a KEP and a more recent doc showing how this could all work.
Learn how to engage with the Kubernetes community on the community page.
You can reach the maintainers of this project at:
Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.