k8s-locallisted

# Local Kubernetes Cluster Management Bootstrap and manage lightweight local Kubernetes clusters with **k3d** (default, Docker-based K3s) or **kind**, plus the local dev-tool ecosystem (kubectl, helm, helmfile, skaffold, k9s). ## Global vs Project-Scoped Setup When designing project local environments, choose the appropriate isolation scope: 1. **Project-Scoped Setup (Recommended for important/complex projects)**: Important projects must remain independent, self-contained, and reproducible across hosts. Do not rely on the global `k3d-local` cluster or default configs. Instead, declare all dependencies (like `k3d`, `kubectl`, `helm`, `flux2`) under the `[tools]` section of the project's mise.toml, store cluster engine configurations within the repository, and isolate active workloads by generating temporary, process-scoped `KUBECONFIG` variables. Author a project-scoped skill at `.agents/skills/local-cluster/SKILL.md` to guide agents to use your local task vocabulary instead of global `dot cluster` commands. 1. **Global Setup (Optional fallback for small/simple projects)**: Simple projects or quick experiments without custom orchestration needs can rely on the global cluster configuration managed here. Use the unified `dot cluster` CLI or manually bootstrap using the global templates. ## Templates & Resources - **k3d Configuration**: Deployed at `~/.config/k3d/local.yaml` (source: `dot_config/k3d/local.yaml`). - **kind Configuration**: [kind-config.yaml](resources/kind-c