Overview
Overview
Overview of the KDC CLI (Kubernetes Docker Commander).
KDC stands for Kubernetes Docker Commander.
It is a project-centric DevOps terminal application for managing Docker, Docker Compose, Kubernetes, Helm, deployments, monitoring, and environment checks from a keyboard-first terminal dashboard.
KDC scans a project, understands which DevOps files are present, checks whether Docker and Kubernetes are available on the local machine, and then shows only the commands and menus that are useful for that project.
For example:
- Presence of a
Dockerfileenables Docker actions. - A
docker-compose.ymlenables Compose actions. - Kubernetes manifests enable Kubernetes and deployment actions.
- If Docker is installed but not running, KDC reports that state and disables runtime-dependent actions where needed.
Why We Use KDC
Docker and Kubernetes projects often require many repeated commands:
docker build
docker run
docker logs
docker compose up
docker compose down
kubectl get pods
kubectl apply
kubectl rollout status
kubectl rollout undo
KDC brings those workflows into one terminal-based interface.
Use KDC to:
- Quickly understand a project's deployment setup.
- Avoid manually remembering every Docker, Compose, and Kubernetes command.
- See what capabilities a project currently has.
- Detect missing files like
Dockerfile, Compose files, or Kubernetes manifests. - Run health checks before deploying.
- Generate project-aware menus and actions.
- Execute a deployment pipeline after checking blockers.
- Keep deployment history under the local KDC config directory.
How KDC Works
KDC follows this flow when it starts:
Project detection
KDC scans the selected project directory and looks for known project, Docker, Compose, Kubernetes, and Helm files.
Stack detection
KDC detects the app stack based on known files:
File Detected Stack package.jsonNode.js pom.xmlSpring Boot Cargo.tomlRust go.modGo requirements.txtPython Capability detection
KDC converts discovered files into project capabilities:
File Capability DockerfileDocker docker-compose.yml,docker-compose.yaml,compose.yml,compose.yamlDocker Compose deployment.yaml,deployment.ymlKubernetes deployment service.yaml,service.ymlKubernetes service ingress.yaml,ingress.ymlKubernetes ingress kustomization.yaml,kustomization.ymlKustomize Chart.yamlHelm Runtime detection
KDC checks whether required local tools are available:
- Docker daemon with
docker info - Kubernetes cluster with
kubectl cluster-info - Minikube fallback with
minikube status
- Docker daemon with
Menu and action generation
Based on detected files and runtime state, KDC builds the dashboard menus and command-palette actions.
Execution
When an action runs, KDC uses standard Docker, Docker Compose, and
kubectlcommands behind the scenes.