feat: migrate manifests from Ingress to Gateway API (HTTPRoute)#482
Open
TineoC wants to merge 8 commits intoCodeForPhilly:developfrom
Open
feat: migrate manifests from Ingress to Gateway API (HTTPRoute)#482TineoC wants to merge 8 commits intoCodeForPhilly:developfrom
TineoC wants to merge 8 commits intoCodeForPhilly:developfrom
Conversation
This change migrates the Gateway API configuration to use ListenerSets instead of attaching HTTPRoutes directly to the Gateway. This enables the self-service TLS model where the application manages its own listeners and certificates.
This updates the sandbox and production overlays to correctly patch the hostnames on both the ListenerSet and the HTTPRoute.
This adds a redirect HTTPRoute targeting the port 80 listener of the ListenerSet, ensuring all HTTP traffic is upgraded to HTTPS. The main HTTPRoute is now pinned to the port 443 listener.
Updates the sandbox and production overlays to ensure the hostname is also patched on the new balancer-redirect HTTPRoute.
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
1 participant
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.
Description
Migrate the existing Ingress resources to the Gateway API (HTTPRoute) as part of the transition to Envoy Gateway.
Related Issue
Closes #481
Manual Tests
The configuration has been structured according to the Envoy Gateway and Gateway API specifications. Overlays for
dev,sandbox, andproductionhave been created to handle environment-specific hostnames.Automated Tests
N/A - This is a configuration change for Kubernetes manifests.
Documentation
Updated
deploy/manifests/balancer/structure.Reviewers
@sahilds1
Notes
IngresswithHTTPRouteinbalancer/base.HTTPRoutetomain-gatewayin theenvoy-gateway-systemnamespace.balancerService port to 80 (withtargetPort: 8000).sandboxandproductionoverlays with their respective hostnames.devoverlay patches to uselocalhost.Disclosed AI usage
main-gatewayconfiguration for TLS termination and namespace visibility.