As noted in the previous article on this blog, in the next episode of the “Self-Hosted Kubernetes Adventures” sitcom, I’ll explain how I configured HAProxy as an Ingress Controller, and how I issue TLS certificates within the cluster using cert-manager. I’ll also mention some plans for the future, because future is always more exciting than the past. When you deploy a pod into the cluster, it gets assigned with its own networking component....
After setting up Intel NUC with Debian 12 on top of it, I have decided to configure Nextcloud as my first application on this new setup. In order to have a successful setup for my needs, I have decided on the following: DNS name for accessing the installation (static DNS entry on the network + valid TLS certificate) HAProxy for terminating TLS and forwarding traffic to the Nextcloud installation Nextcloud and required services in the container Above noted requirements came from the experimentation, but I somewhat knew what I want to do with the setup, and how to make it more clean for the new services....