Unrecognized Name issues with HomeAssistant

Wed, 20 Mar 2024 11:00:00 -0600

Recently I ran into an issue while trying to create a new instance of HomeAssistant on a K3s install of Kubernetes. Getting HomeAssistant up and running and connected to an MQTT server within the same cluster worked as expected. However, the issue came up when I attempted to get it to connect to NabuCasa or make connections out to any TLS/SSL (HTTPS) addresses. Viewing the HomeAssistant logs from the Settings->System->Logs area, I noticed I was getting a very vague error of tlsv1 unrecognized name. Searching around the internet for the issue affecting HomeAssistant just kept turning up people having issues with DNS but no actual “What the DNS issue was”. That was until I came across a Kubernetes StackOverflow Question where the person was getting the same issue but with a completely different application.

Exposing Kubernetes Services with CoreDNS

Thu, 28 Dec 2023 14:30:00 -0600

ℹ️ Note

Originall this article only made mention of the ori-edge/k8s_gateway project. This project is now no longer maintained and development as switched over to k8s-gateway/k8s_gateway.

In my efforts to run a self-hosted Kubernetes cluster(s) in my lab. I needed a way to easily expose services outside of the cluster for easy use by me and the family/friends. In my research, I stumbled upon the Kubernetes Sig ExternalDNS. Its goal is to leverage K8 Service Annotates to provide the desired external DNS entry values and the respective configs to go along with it. However, in my attempt to make this work in a self-hosted environment with minimal deployment in a small footprint on small hardware (RPis mostly), I came across many challenges. Many of the integrations that ExternalDNS supports are focused on Cloud Provider DNS services rather than self-hosted one. Of the self-hosted DNS options, many have large footprints in their deployments. Such as the need for Databases or other services. This left me looking at my favorite DNS service, CoreDNS. However, in an attempt to get the CoreDNS ExternalDNS integration to work. I found out that it requires an etcd service to be available. As well as that the plugins the integration relies on at both the ExternalDNS and CoreDNS sides appear to not be maintained much anymore. Yet alone, the etcd approach is seen as a deprecated one in its own right.

HomeLab on NerdyNik

Unrecognized Name issues with HomeAssistant

Exposing Kubernetes Services with CoreDNS