Skip to content

feat: migrate manifests from Ingress to Gateway API (HTTPRoute)#482

Open
TineoC wants to merge 4 commits intoCodeForPhilly:developfrom
TineoC:migrate-to-envoy-gateway
Open

feat: migrate manifests from Ingress to Gateway API (HTTPRoute)#482
TineoC wants to merge 4 commits intoCodeForPhilly:developfrom
TineoC:migrate-to-envoy-gateway

Conversation

@TineoC
Copy link
Collaborator

@TineoC TineoC commented Mar 21, 2026

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, and production have 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

  • Replaces Ingress with HTTPRoute in balancer/base.
  • Attaches HTTPRoute to main-gateway in the envoy-gateway-system namespace.
  • Updates balancer Service port to 80 (with targetPort: 8000).
  • Adds sandbox and production overlays with their respective hostnames.
  • Migrates dev overlay patches to use localhost.

Disclosed AI usage

  • Special notes: Changes generated using Gemini CLI. Verified application port (8000) and Gateway API specs. Verified main-gateway configuration for TLS termination and namespace visibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: migrate manifests from Ingress to Gateway API (HTTPRoute) for Envoy Gateway support

1 participant