From a10dbecc94e37a5d66d363da0c2edeac31afc3c8 Mon Sep 17 00:00:00 2001 From: Ruben Hensen Date: Thu, 22 Oct 2026 11:03:19 +0200 Subject: [PATCH] home-assistant: replace the ExternalName service with an EndpointSlice After the microk8s ingress addon went from ingress-nginx 1.8.0 to 1.13.8, ha.rubenhensen.nl returned 503: the controller now resolves externalName as a DNS name and "192.168.1.202" fails the lookup. A selector-less Service with an EndpointSlice pointing at the IP is the supported way to route to an address outside the cluster. --- home-assistant/service.yaml | 26 ++++++++++++++++++++++---- 1 file changed, 22 insertions(+), 4 deletions(-) diff --git a/home-assistant/service.yaml b/home-assistant/service.yaml index 913ef47..09835e8 100644 --- a/home-assistant/service.yaml +++ b/home-assistant/service.yaml @@ -1,10 +1,28 @@ +# Home Assistant runs outside the cluster on 192.168.1.202. ingress-nginx +# 1.13 resolves an ExternalName as a DNS name and fails on a bare IP, so +# point a selector-less Service at it with a hand-written EndpointSlice. apiVersion: v1 kind: Service metadata: name: home-assistant-external spec: - type: ExternalName - externalName: 192.168.1.202 ports: - - port: 8123 - protocol: TCP \ No newline at end of file + - name: http + port: 8123 + protocol: TCP + targetPort: 8123 +--- +apiVersion: discovery.k8s.io/v1 +kind: EndpointSlice +metadata: + name: home-assistant-external-1 + labels: + kubernetes.io/service-name: home-assistant-external +addressType: IPv4 +ports: + - name: http + port: 8123 + protocol: TCP +endpoints: + - addresses: + - 192.168.1.202