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.

Sign up for GitHub

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

Jump to bottom

Consider making GRPCRoute a required informer now that it is v1 #6432

Open
sunjayBhatia opened this issue May 10, 2024 · 0 comments
Open

Consider making GRPCRoute a required informer now that it is v1 #6432

sunjayBhatia opened this issue May 10, 2024 · 0 comments
Labels
kind/decision Categorizes issue as a decision to be voted on. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor.

Comments

@sunjayBhatia
Copy link
Member

As of Gateway API v1.1.0, GRPCRoute is GA and has moved to the v1 API group version

When using Gateway API it is not currently required, i.e. it can be disabled via the --disable-feature flag

Should we make this a required resource to reconcile now that it is GA? Making it required will mean operators will need the CRD to be installed, RBAC to be set up, etc. It is potentially non-essential since there is a required Route type (HTTPRoute) when using Gateway API
@sunjayBhatia sunjayBhatia added lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. kind/decision Categorizes issue as a decision to be voted on. labels May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/decision Categorizes issue as a decision to be voted on. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sunjayBhatia