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....
Over the years I have dabbled with Kubernetes on-and-off a bit, and mostly learned theoretical stuff surrounding it. I also managed and deployed few of the EKS based clusters on AWS at work, so I know certain operational things as well. To be honest, I haven’t really done any “cool and amazing” things with it. Those were mostly bare Amazon EKS setups, no ArgoCD or something fancy like that. Fanciest things I managed were Horizontal Pod Autoscaler and AWS ALB ingress controller on those clusters....
For the past few weeks, and over the next few weeks, I have been playing with my local network setup and am hoping to migrate most of the self-hosted services I use and have scattered throughout the various server providers to my local network. Except of those that should be on the web obviously (Mastodon instance, Email server, and similar). This is a slow effort that I do in-between job and personal duties so some days I might do a lot, and others not so much....