You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Flagger with the Gateway API to create HTTPRoutes, users must currently create a ReferenceGrant manually to allow cross-namespace references between the HTTPRoute and the relevant resources (such as Gateways). This manual step adds overhead, and missing a ReferenceGrant can lead to configuration issues and delays in setup.
Proposed solution
Implement functionality in Flagger to automatically create a ReferenceGrant whenever an HTTPRoute is created with a cross-namespace reference requirement. This automation would simplify the process, minimize manual configuration, and reduce the likelihood of errors due to missing permissions.
Considered drawbacks
This approach may add complexity to the Flagger codebase.
Any alternatives you've considered?
Manual Creation: Users can continue to create ReferenceGrants manually, but this approach is prone to user error and slows down deployment workflows.
CLI Tool: Providing a CLI tool or script to generate necessary ReferenceGrants could help, but it lacks the seamless experience of automated creation within Flagger itself.
The text was updated successfully, but these errors were encountered:
Describe the feature
What problem are you trying to solve?
When using Flagger with the Gateway API to create HTTPRoutes, users must currently create a ReferenceGrant manually to allow cross-namespace references between the HTTPRoute and the relevant resources (such as Gateways). This manual step adds overhead, and missing a ReferenceGrant can lead to configuration issues and delays in setup.
Proposed solution
Implement functionality in Flagger to automatically create a ReferenceGrant whenever an HTTPRoute is created with a cross-namespace reference requirement. This automation would simplify the process, minimize manual configuration, and reduce the likelihood of errors due to missing permissions.
Considered drawbacks
Any alternatives you've considered?
The text was updated successfully, but these errors were encountered: