Where Does k3d Store Clusters and Config?
k3d keeps cluster definitions in ~/.config/k3d with nodes as Docker containers and kubeconfigs merged locally.
Last updated
k3d splits state between a config folder and Docker. Cluster definition files live under .config/k3d in your home directory. The actual nodes run as k3d prefixed containers with volumes for persistence.
Kube access merges into your kubeconfig on creation. Deleting the config folder orphans containers that keep running. Manage everything through k3d commands so both sides stay consistent.
Where k3d stores this, by platform
~/.config/k3d
Cluster definition files live here. Nodes run as Docker containers beside them. Kube entries merge into ~/.kube/config on create.
Frequently asked questions
How do I delete a k3d cluster fully?
Run k3d cluster delete to remove containers, volumes, and kube entries together. Manual Docker deletes leave config behind. Check both sides afterward.
Where is my k3d kubeconfig?
Merged into ~/.kube/config under a k3d context name on creation. k3d kubeconfig get refreshes the file. Contexts expire when clusters delete.
Notice an outdated path? Let us know.