Why it exists
A place to keep Helm charts for the tools I run on my own Kubernetes
cluster, packaged and versioned the same way I'd expect a chart to be
packaged anywhere else: helm repo add, helm repo update, install.
Not a learning exercise so much as removing the excuse to hand-apply
YAML on a homelab cluster just because it's not production.
What I learned
Publishing a chart repo is a good forcing function for actually versioning changes instead of editing manifests in place. It's a small amount of extra ceremony that pays for itself the first time something needs to roll back.
Status
Active. Still the place new charts land before anything gets deployed to the cluster.