Posts tagged “k3s”

Building Audiobookshelf through GitOps with a ConfigMap, retained storage, a non-root runtime and a Cloudflare Tunnel credential protected by SOPS.

Renaming the homelab repository was straightforward. Moving two live Grafana Secrets between Flux Kustomizations meant handing over ownership without letting pruning delete them.

Renovate's first run offered a Flux upgrade and three overlapping PRs. An hourly job, an encrypted token, and a useful reminder to read what the bot proposes.

I wanted to stop port-forwarding Grafana. Along the way: an overdue chart upgrade, encrypted credentials, and a certificate my browser quite reasonably refused to trust.

Deploying kube-prometheus-stack through Flux and Helm, then tracing a pruning cascade through Git and recovering the cluster from desired state.

Using SOPS, age and Flux to make Kubernetes Secrets encrypted in Git, recoverable by the cluster and useful only where they are needed.

Publishing Linkding through a locally managed Cloudflare Tunnel while keeping the Kubernetes Service private and the tunnel credential out of Git.

Using Flux, K3s local-path storage and Kubernetes security contexts to make Linkding survive pod replacement without leaving its container running as root.

Bootstrapping Flux into my K3s homelab and turning a GitHub repository into the declared source of cluster state.

Installing K3s on the ZBook, investigating two deceptively similar Helm flags and securely managing the cluster from my MacBook.