Add support for Gateway API (HTTPRoute) to Helm chart #5401
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.
Summary
Gateway API provides more-modern support for HTTP Routing and GRPC routing compared with Ingress API. Since we (Stacklok) have rolled out https://gateway.envoyproxy.io/, add support for loading GRPC and HTTP routes to Minder, as well as the old Ingress model (which is much longer, and less helpful).
Change Type
Mark the type of change your PR introduces:
Testing
I manually loaded these routes into a test cluster with Envoy Gateway installed, and verified that the routes were "accepted". Will do more testing in staging once the chart is deployed.
Note that this does not yet remove the old
Ingress
objects -- both can be deployed at once in a cluster.Review Checklist: