gateway: take over ports 80 and 443 from ingress-nginx

Envoy moves from the test ports to 80 and 443, and Let's Encrypt HTTP-01 challenges go through an HTTPRoute on the Gateway. Push only after sudo microk8s disable ingress, since both want the same host ports.
This commit is contained in:
Ruben Hensen committed 2026-10-23 21:02:52 +02:00
1 parent 23aaf5ab26
commit 009b8ce510
2 files changed
+10 -9

No files matched your search

+5 -2
View File
@@ -14,5 +14,8 @@ spec:
# Enable the HTTP-01 challenge provider # Enable the HTTP-01 challenge provider
solvers: solvers:
- http01: - http01:
ingress: gatewayHTTPRoute:
ingressClassName: nginx parentRefs:
- name: homelab
namespace: envoy-gateway-system
sectionName: http
+5 -7
View File
@@ -1,9 +1,7 @@
# How Envoy Gateway runs the proxy: a DaemonSet that takes the node's ports # How Envoy Gateway runs the proxy: a DaemonSet that takes the node's ports
# directly, the way the microk8s ingress-nginx addon does. Gateway listeners # 80 and 443 directly, the way the microk8s ingress-nginx addon did. Gateway
# below 1024 run on port + 10000 inside the container (80 becomes 10080). # listeners below 1024 run on port + 10000 inside the container (80 becomes
# # 10080).
# While ingress-nginx still owns 80 and 443, the host ports are 10080 and
# 10443 so both can be tested side by side.
apiVersion: gateway.envoyproxy.io/v1alpha1 apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy kind: EnvoyProxy
metadata: metadata:
@@ -27,6 +25,6 @@ spec:
- name: envoy - name: envoy
ports: ports:
- containerPort: 10080 - containerPort: 10080
hostPort: 10080 hostPort: 80
- containerPort: 10443 - containerPort: 10443
hostPort: 10443 hostPort: 443