You have a cluster running on Digital Ocean. You edit manifests in Sublime Text. Then you spend half your day switching terminals, reauthenticating, and guessing which context is active before pushing a tiny change to Kubernetes. There has to be a cleaner way.
Digital Ocean Kubernetes gives you a managed control plane that behaves like any other upstream cluster, just stripped of infrastructure noise. Sublime Text is the fast, distraction-free editor you actually enjoy using. Putting the two together means getting local speed with cloud-native consistency. The trick is connecting them without getting tangled in kubeconfig files or stale tokens.
The real workflow starts with identity. Instead of juggling multiple kubeconfigs, you authenticate to Digital Ocean using an API token or external OIDC provider like Okta. Once authenticated, the Kubernetes cluster issues a short-lived client certificate. Sublime Text can trigger this workflow through command-line tools or build systems. When you save, it applies your YAML through kubectl or a wrapper that runs behind the scenes. You stay in the editor, the cluster stays secure, and no one copies credentials to random laptops.
To make this smooth, create a small script or plugin that maps your Sublime build system to the appropriate cluster context. Each project folder can hold its own kubeconfig path, making it impossible to accidentally deploy staging configs to production. Add a light RBAC policy in Kubernetes so developers get only the namespaces they need. Keep secrets out of the repo by reading them from Digital Ocean secrets storage instead of embedding them.
When something feels off—a denied request or missing role—check the kubelet event logs first. Most hiccups come from expired tokens or wrong contexts. Rotate API tokens periodically and rely on short-lived credentials rather than long-lived access keys. It’s a tiny change that buys real safety.