#k3s

I Wanted Kubernetes Without an Always On EKS Bill

I wanted a persistent Kubernetes environment without an always-on managed-cluster bill or compromising the Docker workloads already running on my Debian home server. I chose k3s, defined explicit resource boundaries, disabled components that conflicted with the host, and validated the design through deployment, networking, rollout, rollback, and desired-state checks.