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

Support KongCustomEntity to refer to resource in other namespace in spec.parentRef #6288

Closed
4 tasks done
randmonkey opened this issue Jul 4, 2024 · 0 comments · Fixed by #6289
Closed
4 tasks done
Assignees
Labels
area/CRD Changes in existing CRDs or introduction of new ones
Milestone

Comments

@randmonkey
Copy link
Contributor

randmonkey commented Jul 4, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Does this enhancement require public documentation?

  • I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

Problem Statement

Currently KongCustomEntity does not support referring to KongPlugin in other namespaces. We should enable KongCustomEntity to refer to resource (including but not limited to KongPlugin) in other namespaces.

Proposed Solution

  • Allow KongCustomEntity to refer to KongPlugins in other namespaces if ReferenceGrant allows
  • Reject in webhook or generate a translation failure if KongCustomEntity refers to resources in other namespaces without permission of ReferenceGrant

Additional information

No response

Acceptance Criteria

  • KongCustomEntity referring to KongPlugin in another namespace with permission of ReferenceGrant can be accepted and translated
  • ``KongCustomEntityreferring toKongPlugin` in another namespace without permission of `ReferenceGrant` is rejected by webhook or generate a translation failure
@randmonkey randmonkey added the area/CRD Changes in existing CRDs or introduction of new ones label Jul 4, 2024
@randmonkey randmonkey added this to the KIC v3.3.x milestone Jul 4, 2024
@randmonkey randmonkey self-assigned this Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CRD Changes in existing CRDs or introduction of new ones
Projects
None yet
1 participant