Skip to content
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

Core API: ReferenceGrant #477

Closed
kate-osborn opened this issue Mar 17, 2023 · 2 comments
Closed

Core API: ReferenceGrant #477

kate-osborn opened this issue Mar 17, 2023 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@kate-osborn
Copy link
Contributor

kate-osborn commented Mar 17, 2023

As cluster operator and/or application admin, I want to be able to use ReferenceGrant to selectively enable cross-namespace references so that I can ensure secure and controlled access to cross-namespace resources. Specifically, I want to use ReferenceGrants to allow Gateways to reference Secrets and Routes to reference Backend (Services).

Acceptance Criteria

  • The ReferenceGrant should permit Gateways to reference Secrets across namespace boundaries.
  • The ReferenceGrant should permit Routes to reference Backends (Services) across namespace boundaries.
  • Cross-namespace references without a grant should not be permitted.
  • Each ReferenceGrant should represent a unique trust relationship, allowing me to add or remove grants to manage access to cross-namespace resources.
  • When a ReferenceGrant is removed, the access that the grant allowed should be automatically revoked.
  • When a ReferenceGrant is changed, the access that the grant allowed should be automatically recalculated and applied accordingly.
  • If a cross-namespace reference is made without an applicable ReferenceGrant, do NOT expose information about the existence of a resource in another namespace. NKG should only report that the ReferenceGrant does not exist to allow this reference. Do not give hints about whether or not the referenced resource exists.
  • Update the documentation
    • Update the compatibility doc
    • Add an example for both Gateway -> Secret and Route -> Backend cross-namespace routing
  • Make sure all relevant conformance tests would pass

https://gateway-api.sigs.k8s.io/api-types/referencegrant/
https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.ReferenceGrant

Aha! Link: https://nginx.aha.io/features/NKG-61

@kate-osborn kate-osborn changed the title API Surface: ReferenceGrant Core API: ReferenceGrant Mar 17, 2023
@kate-osborn kate-osborn added enhancement New feature or request area/httproute/core Relates to all Core features of HTTPRoute and removed proposal labels Mar 21, 2023
@kate-osborn kate-osborn added this to the v1.0.0 milestone Mar 21, 2023
@kate-osborn kate-osborn self-assigned this Mar 21, 2023
@kate-osborn kate-osborn added the refined Requirements are refined and the issue is ready to be implemented. label Mar 24, 2023
@kate-osborn kate-osborn removed their assignment Mar 24, 2023
@kate-osborn kate-osborn modified the milestones: v1.0.0, v0.4.0 Mar 24, 2023
@mpstefan mpstefan removed the area/httproute/core Relates to all Core features of HTTPRoute label May 10, 2023
@mpstefan mpstefan modified the milestones: v1.0.0, v0.5.0 May 17, 2023
@mpstefan mpstefan removed the refined Requirements are refined and the issue is ready to be implemented. label May 26, 2023
@mpstefan
Copy link
Collaborator

Removed refined tag, as we will definitely need to talk about this one before we start. See #615

@mpstefan
Copy link
Collaborator

Splitting into #694 and #695

@mpstefan mpstefan closed this as not planned Won't fix, can't repro, duplicate, stale May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants