Files
k8scd/gateway/envoyproxy.yaml
Ruben Hensen 009b8ce510 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.
2026-10-23 21:02:52 +02:00

31 lines
934 B
YAML

# How Envoy Gateway runs the proxy: a DaemonSet that takes the node's ports
# 80 and 443 directly, the way the microk8s ingress-nginx addon did. Gateway
# listeners below 1024 run on port + 10000 inside the container (80 becomes
# 10080).
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
name: hostport
namespace: envoy-gateway-system
spec:
provider:
type: Kubernetes
kubernetes:
# No cloud load balancer here; a LoadBalancer Service would stay pending.
envoyService:
type: ClusterIP
envoyDaemonSet:
patch:
type: StrategicMerge
value:
spec:
template:
spec:
containers:
- name: envoy
ports:
- containerPort: 10080
hostPort: 80
- containerPort: 10443
hostPort: 443