Description
The sandbox cluster is migrating away from ingress-nginx as it reaches EOL at the end of March 2026. This migration is being handled by adopting Envoy Gateway and the Gateway API.
This repository (balancer-main) provides the base manifests consumed by the cluster. To support this migration, the current Ingress resources should be replaced with HTTPRoute resources.
This migration is tracked in CodeForPhilly/cfp-sandbox-cluster#130.
Proposed Changes
- Replace
deploy/manifests/balancer/base/ingress.yaml with an equivalent httproute.yaml.
- The
HTTPRoute should define the routing logic (e.g., targeting the balancer service on port 80).
- For the sandbox environment, the
HTTPRoute will need to be attached to the main-gateway in the envoy-gateway-system namespace.
References
Description
The sandbox cluster is migrating away from
ingress-nginxas it reaches EOL at the end of March 2026. This migration is being handled by adopting Envoy Gateway and the Gateway API.This repository (
balancer-main) provides the base manifests consumed by the cluster. To support this migration, the currentIngressresources should be replaced withHTTPRouteresources.This migration is tracked in CodeForPhilly/cfp-sandbox-cluster#130.
Proposed Changes
deploy/manifests/balancer/base/ingress.yamlwith an equivalenthttproute.yaml.HTTPRouteshould define the routing logic (e.g., targeting thebalancerservice on port 80).HTTPRoutewill need to be attached to themain-gatewayin theenvoy-gateway-systemnamespace.cfp-sandbox-cluster, we've already prepared thebalancer/kustomization.yamlto consume this new file (see CodeForPhilly/cfp-sandbox-cluster#132).References