DevSpace — Developer-First Kubernetes Workflow Tool

What it is

DevSpace is an open-source CLI tool that transforms any code repository into a Kubernetes development environment. It handles image building, deployment, port-forwarding, file synchronization, and log streaming from a single devspace.yaml configuration file.

The tool targets developers who work with Kubernetes daily and want to iterate faster without manually running kubectl commands, rebuilding images, and restarting pods. It supports Helm charts, Kustomize, and raw manifests.

How it saves time or tokens

DevSpace replaces a multi-step workflow of building Docker images, pushing to a registry, updating deployments, setting up port-forwards, and tailing logs with a single devspace dev command. File sync means code changes appear in the running container without a full image rebuild, cutting iteration cycles from minutes to seconds.

The profile system lets you reuse the same configuration across development, staging, and production with environment-specific overrides.

How to use

1. Install DevSpace with brew install devspace or npm install -g devspace.
2. Run devspace init in your project to generate a devspace.yaml configuration.
3. Run devspace dev to start the full development loop: build, deploy, port-forward, sync, and log streaming.

Example

# Install DevSpace
brew install devspace

# Initialize in your project
devspace init

# Start the dev loop
devspace dev

# Open a shell in the running container
devspace enter

# Deploy to production with a profile
devspace deploy -p production

# Clean up resources
devspace purge

Related on TokRepo

• DevOps tools -- Kubernetes and infrastructure development tools
• Automation tools -- CLI tools for development workflow automation

Common pitfalls

• DevSpace requires a running Kubernetes cluster. For local development, use minikube, kind, or Docker Desktop with Kubernetes enabled before running devspace dev.
• File sync watches for changes and copies files into the container. Large repositories with many files can cause high CPU usage during the initial sync. Use the excludePaths option to skip node_modules, .git, and build artifacts.
• The devspace init wizard detects your project type automatically, but the generated configuration may need manual tuning for monorepo setups or projects with multiple services.