feat(chart): add HTTPRoute configuration#1935
Merged
benmcclelland merged 2 commits intoversity:mainfrom Mar 6, 2026
Merged
Conversation
Collaborator
|
This won't automatically run in continuous integration without approval. A member of the Versity organization must allow it. |
jacksgt
approved these changes
Mar 6, 2026
Contributor
jacksgt
left a comment
jacksgt
left a comment
There was a problem hiding this comment.
Looks good to me, thanks for adding this!
benmcclelland
approved these changes
Mar 6, 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
4 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.
Adds HTTPRoute configuration to the chart in place of ingress for those who have adopted the Gateway API.
NOTE: In a HTTPRoute you're unable to route to separate backends with separate hostnames in a single resource like you can with ingress. I chose to add
webui.httpRouteandadmin.httpRoute, however that may lead to some confusion since there are no ingress fields under the same keys. I considered adding a globalhttpRouteskey with each route under that but thought this was better ux reading through the chart values. Let me know if you would prefer that or another approach.Thanks!