feat: Add HTTPRoute support for Gateway API - #234
Merged
Conversation
Member
|
Hi @hoangphuocbk Thank you for this, it's been on my TODO list to add but I just haven't been able to find the time to implement it. I'm running your PR through our validation pipeline now and if everything is 🟢 I'll merge it. |
chriswk
approved these changes
Apr 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
About the changes
Add HTTPRoute support for Gateway API. Gateway API is the successor to Ingress API with improved design and capabilities.
The Ingress-NGINX Controller is deprecated, so user can migrate from Ingress-NGINX to the Gateway API.
Closes #226
Important files
httproute.yaml and values.yaml in each charts