Argocd on Thomas Peters

Multi-Tenant Kubernetes with Kustomize Templates and ApplicationSets

thomas@tnepeters.com (Thomas Peters) — Mon, 10 Aug 2026 00:00:00 +0000

The Problem

I’ve been building a platform that runs the same application for multiple clients, with multiple users per client. Every instance needs its own config, its own storage, and its own hostname. Client A must never be able to reach client B, and that one has to be a guarantee rather than a convention. Users inside a client are a softer boundary, which is a distinction worth making early because the design treats them very differently. The naive approach is copy-pasting a pile of YAML per tenant, which works right up until you need to change one field across twenty instances.

One Repo, Many Clusters: ArgoCD ApplicationSets and the Root App Pattern

thomas@tnepeters.com (Thomas Peters) — Mon, 03 Aug 2026 00:00:00 +0000

The Problem

I run several Kubernetes clusters: bare-metal prod (talos-metal), legacy prod on VMs (talos-02), plus dev and edge clusters that come and go. Every cluster needs roughly the same infrastructure: Cilium, cert-manager, external-dns, storage, monitoring. On top of that, each one has its own set of apps. Managing that by hand, or even with per-cluster ArgoCD Application manifests, turns into copy-paste drift almost immediately.

What I want: adding an app to a cluster is mkdir + git push, and bootstrapping an entire new cluster is one kubectl apply plus one label.