feat(gateway-api): add creation of ReferenceGrant objects for cross-namespace Gateway API support #1736
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 andHTTPRoute
. It addresses scenarios where anHTTPRoute
needs to route traffic to aService
in a different namespace, which requires aReferenceGrant
to function correctly.Issue Reference
This PR resolves fluxcd/flagger#1718.
Implementation Details
ReferenceGrant
is only triggered if anHTTPRoute
is configured to route traffic to aService
in a different namespace. If theService
resides in the same namespace as theHTTPRoute
, noReferenceGrant
is generated, ensuring minimal and precise resource management.Service
and dynamically creates theReferenceGrant
only when necessary, adhering to the Gateway API requirements.