Okteto — Kubernetes Development Environments

What it is

Okteto is a development platform that lets you code locally while your application runs on a real Kubernetes cluster. Instead of maintaining Docker Compose stacks or local Kubernetes setups that drift from production, Okteto synchronizes your local file changes to a remote pod with sub-second latency and hot-reloads your application automatically.

It targets backend and full-stack developers who deploy to Kubernetes in production but find the local development loop slow and unreliable. Platform engineering teams use Okteto to give developers self-service development environments that mirror production.

How it saves time or tokens

Local Kubernetes development setups (Minikube, Kind, Docker Desktop) consume significant CPU and RAM, and their configurations inevitably diverge from production clusters. Okteto eliminates this drift by running your code on the actual target cluster. The okteto up command replaces your running pod with a development container that syncs files from your local editor, meaning you get the same networking, service discovery, and configuration as production.

This cuts the inner dev loop from minutes (build container, push, deploy) to seconds (save file, see change).

How to use

1. Install the Okteto CLI:

brew install okteto

1. Connect to your cluster:

okteto context use https://your-cluster.okteto.com

1. Start a development session in your project directory:

okteto up

Your local code now syncs and hot-reloads on the cluster. Edit files in your editor and see changes reflected in the remote pod instantly.

Example

An okteto.yml manifest for a Node.js service:

dev:
  api:
    image: node:20
    command: npm start
    sync:
      - .:/app
    forward:
      - 3000:3000
    environment:
      - NODE_ENV=development

This tells Okteto to sync the current directory to /app in the container, forward port 3000, and run npm start with development environment variables.

Related on TokRepo

• DevOps Tools -- Infrastructure and deployment tools for Kubernetes workflows
• Automation Tools -- CI/CD pipelines that complement Okteto dev environments

Common pitfalls

• File sync can miss changes if your project has a large node_modules or build directory. Use the ignore field in okteto.yml to exclude these directories from synchronization.
• Network policies on the cluster may block Okteto's syncthing port. Ensure port 22100 is accessible between your machine and the cluster.
• Resource limits on the cluster namespace can prevent the dev container from starting. Check your namespace quotas if okteto up hangs.