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

feat(gateway-api): add creation of ReferenceGrant objects for cross-namespace Gateway API support #1736

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

kahirokunn
Copy link

@kahirokunn kahirokunn commented Dec 11, 2024

Add Automation for ReferenceGrant Creation with Gateway API and HTTPRoute

This PR is a feature to automatically create ReferenceGrant resources when using Flagger with Gateway API and HTTPRoute. It addresses scenarios where an HTTPRoute needs to route traffic to a Service in a different namespace, which requires a ReferenceGrant to function correctly.

Issue Reference

This PR resolves fluxcd/flagger#1718.

Implementation Details

  • Conditional Automation: The creation of ReferenceGrant is only triggered if an HTTPRoute is configured to route traffic to a Service in a different namespace. If the Service resides in the same namespace as the HTTPRoute, no ReferenceGrant is generated, ensuring minimal and precise resource management.
  • Namespace Awareness: The implementation checks the namespace of the target Service and dynamically creates the ReferenceGrant only when necessary, adhering to the Gateway API requirements.

…amespace Gateway API support

Signed-off-by: kahirokunn <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature Request: Automate ReferenceGrant Creation When Using HTTPRoute with Gateway API in Flagger
1 participant