k3s single-node cost reduction: which bundled components can be safely disabled without an alternative ingress path
I'm consolidating a low-traffic internal workload onto a single small VM and evaluating k3s's single-server, SQLite-backed mode to cut baseline compute cost compared to a multi-node upstream Kubernetes cluster. The single-binary footprint and embedded datastore are documented to lower idle memory, which fits this workload's traffic profile. The documented --
k3s
kubernetes