← ClaudeAtlas

kindctllisted

Use repo/worktree-scoped kind clusters without touching the global kubeconfig. Trigger when users mention kind cluster, local k8s, local Kubernetes, spin up a cluster, Kubernetes-in-Docker, multi-repo kind, or multi-worktree cluster work.
orka-agents/orka · ★ 18 · DevOps & Infrastructure · score 74
Install: claude install-skill orka-agents/orka
# kindctl Use this skill whenever work involves a local `kind` cluster, local k8s/Kubernetes, Kubernetes-in-Docker, or repo/worktree-specific test clusters. ## Mental model - `kind` clusters are global to the Docker daemon. - `~/.kube/config` is a shared mutable global and must not be used for kindctl-managed clusters. - `kindctl` derives a cluster name from the current repo/worktree path and stores its kubeconfig in `~/.kube/kind/<name>.kubeconfig`. - The current directory is enough: random repos and git worktrees do not need to know anything special. ## Golden rule for agents Never run bare `kubectl` or `helm` against a kindctl-managed cluster. Prefer: ```sh .agents/skills/kindctl/bin/kindctl kubectl get nodes .agents/skills/kindctl/bin/kindctl exec -- helm list ``` Do not run: ```sh kubectl get pods kubectl config use-context kind-something kind create cluster ``` ## Installation This skill is vendored into the repo at `.agents/skills/kindctl/`. If another harness needs to expose it, create an external `skills/kindctl` symlink that points back to this canonical directory; this repo does not keep `.codex` or `.copilot` mirrors. Invoke the wrapper by its repo-relative path: ```sh .agents/skills/kindctl/bin/kindctl <command> ``` The skill itself should invoke `bin/kindctl` by absolute path or by resolving the skill directory. Do not rely on shell aliases. ## Commands ```sh kindctl create [--config F] [--tag T] [--k8s-version vX.Y.Z] kindctl delete [--tag T] ki