t3: name the service port so istio keeps the external endpoint #218

Merged

alex merged 1 commit from wiring-guru/t3-port-name into main

2026-11-11 09:04:08 -07:00

AGit

wiring-guru commented

2026-11-10 21:15:13 -07:00

Contributor

Istio matches an endpoint to a service port by name (svcPort.Name !=
ep.ServicePortName filters the endpoint out), so an unnamed service port against
the slice's http port left the gateway cluster with no instances and a 503 no
healthy upstream, while the tailscale ingress kept working because kube-proxy
matches by number. The slice already names its port http.

Istio matches an endpoint to a service port by name (svcPort.Name != ep.ServicePortName filters the endpoint out), so an unnamed service port against the slice's http port left the gateway cluster with no instances and a 503 no healthy upstream, while the tailscale ingress kept working because kube-proxy matches by number. The slice already names its port http.

wiring-guru added 1 commit

2026-11-10 21:15:13 -07:00

t3: name the service port so istio keeps the external endpoint bf1d026f95

Istio matches an endpoint to a service port by name (svcPort.Name !=
ep.ServicePortName filters the endpoint out), so an unnamed service port against
the slice's http port left the gateway cluster with no instances and a 503 no
healthy upstream, while the tailscale ingress kept working because kube-proxy
matches by number. The slice already names its port http.