Your terminal is a war zone. Containers, contexts, and YAMLs everywhere. Then someone suggests editing Kubernetes manifests directly from Sublime Text while running a local Microk8s cluster. It sounds easy. Until it isn’t. That’s where a little structure—and a bit of common sense—saves you from debugging your own editor.
Microk8s is the lightweight Kubernetes that thinks it’s a heavyweight. It runs on a laptop, boots fast, and behaves like production-grade K8s without needing a whole ops department watching it. Sublime Text is the fast, quiet editor that never asks for much yet always opens instantly. Together, they make a formidable combo for prototyping K8s workloads without waiting for the CI pipeline to catch its breath.
When you wire Sublime Text to your local Microk8s, you gain direct insight into the pod definitions and service files you’re tweaking. The loop shortens. No more switching to a terminal, applying configs, and realizing your indenting crime too late. The goal is not just integration, but flow. Edit, apply, observe—fast enough to stay focused.
The logic is simple: configure Sublime Text to run lightweight build or deploy commands on save, using Microk8s as the local cluster target. Keep your kubeconfig readable only to you. Use service accounts with the least privileges for quick validation, not admin-level keys for testing hello-world pods. Store cluster credentials through your OS’s keychain, not in plain YAMLs. Kubernetes won’t save you from yourself.
Bugs usually come down to mismatched contexts or permission errors. Microk8s uses its own kubeconfig path, so tell Sublime Text or any build plugin which file to reference. If you see “forbidden,” it’s probably RBAC reminding you that “developer” doesn’t mean “root.” Rotate tokens every so often, even locally. It sets habits that translate to production safety later.