Talos Cluster

ArgoCD

I'm using ArgoCD for deploying my services to my cluster the GitOps way and keeping the k8s state in sync.

MetalLB

MetalLB works as my LoadBalancer for my home setup and let's me "spawn" IPs in an extra defined Subnet in my local server network. The first IP is being used by the main public Ingress Controller and published via an Wireguard tunnel between my Firewall and a Hetzner VPS. Additional IPs are being used for local testing and game servers.

Contour

Contour was my current choice of Ingress Operators when setting this up as it allowed me to use the IngressAPI but be open to the new standart GatewayAPI. Also it provides nice metrics. And it's supported by Knative which I was experimenting with at the time. Might migrate this to Envoy Gateway.

Ceph CSI

As my proxmox Node provides me with a ceph backend it kinda was the obvious choice to also use it as my CSI Provider and it's working great. I once had the VMs also booting from Ceph but ran into some performance issues and switched to an dedicated NVME SSD - solved.

S3

What should I say. I already had my Kubernetes Volumes running on my Ceph Cluster. So let's also use it was a minor step to install RadosGW on my Hypervisor and add a proxy for tls termination to my existing Ingress Controller. Currently this is mostly used by my Mastodon server but I'm looking forward to migrate other services as well. One thing I'm not so happy about is that I currently have to manage Buckets and Secrets myself. I tested various Operators and a Crossplane Provider for managing the external state, but wasn't satisfied.

source

• infra github