Deploy releases/k8s-manifests be630dc#153
Merged
Merged
Conversation
…er gatewayHTTPRoute solver Phase 3 of the ingress-nginx → Envoy Gateway migration. Adds HTTPS on the *.sandbox.k8s.phl.io hostnames by giving each app its own Gateway resource and switching cert-manager's HTTP-01 solver from the ingress-nginx solver to the new Gateway-API-native gatewayHTTPRoute solver. Structural changes: - _httproutes/ folded into _gateways/ — each app gets one file holding its Gateway (HTTPS listener with cert-manager annotation) + its HTTPRoute (parentRefs both main-gateway for HTTP/ACME and the local Gateway for HTTPS). One unit-of-work per app for eventual upstream migration. - cert-manager.issuers.yaml moved under _infra/cert-manager/ following the underscore-prefix convention for non-workload top-level dirs. - ClusterIssuers (letsencrypt-prod, letsencrypt-staging) updated to use the gatewayHTTPRoute solver pointing at main-gateway. cert-manager now creates short-lived HTTPRoutes (instead of Ingresses) for ACME challenges. Per-app cert Secrets use the suffix `-gw-tls` to avoid collision with the existing Ingress-managed Certs in each app's namespace. Old Ingress + Cert can be removed by the project when they migrate upstream. mergeGateways: true on the EnvoyProxy keeps all per-project Gateways collapsed onto one Envoy data-plane + one LoadBalancer. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
feat(gateway-tls): per-app HTTPS via per-project Gateway + gatewayHTTPRoute solver
Author
|
|
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
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.
kubectl diffreports that applying be630dc will change: