- Powered by
- WordPress
-
Why Is It v1 for a Namespace but apps/v1 for a Deployment?
If you’ve written more than a couple of Kubernetes manifests, you’ve probably copy-pasted these lines without thinking too hard about them:
-
Why a thousand containers weigh almost nothing
Docker can run a hundred copies of the same image without storing it a hundred times. The trick is copy-on-write — and once you see the layer stack, it stops feeling like magic.
-
Multi-Tenant ERPNext on a Local Kubernetes Cluster
Running three independent businesses on one homelab K8s deployment — with replicated storage, automated cloud backups, and zero vendor lock-in.
-
Longhorn on MicroK8s: Replicated Storage for a 4-Node Homelab Cluster
Skip NFS-in-a-pod, skip Ceph. Longhorn gives you distributed, replicated storage on bare metal in under 10 minutes.
-
Building the Observability Stack for my 4-Node Homelab Kubernetes Cluster with Headlamp and Beszel
No Prometheus. No Grafana. No YAML hell. Just two lightweight tools that give you everything you need to monitor a homelab cluster.
-
Secure GitLab Runners on a Local 4-Node K8s Cluster Through GCP Secret Manager and External Secrets Operator v2
A complete guide to running GitLab CI/CD on your homelab Kubernetes cluster without ever putting a secret in a file.
-
SSH Over the Internet Without Exposing Your Server — Cloudflare Tunnels + Zero Trust Access
You want SSH access to your home server from anywhere in the world. The naive approach — opening port 22 on your router — works, but it exposes your machine directly to the internet. Every automated scanner, brute-force bot, and opportunistic attacker can reach it.