Where Does kubie Store Contexts?
kubie kubeconfig contexts and shell sessions on desktop OSes, isolated per shell.
Last updated
kubie wraps kubectl contexts with per shell isolation. It reads the standard kubeconfig at ~/.kube/config and tracks session state under its own data directory. No cluster data persists locally beyond cache.
Unlike kubectx it never mutates the global current context. Each shell carries its pick. Lose the state dir and shells just respawn clean.
Where kubie stores this, by platform
%USERPROFILE%\.kube\config
Reads contexts from kubeconfig. State dir holds ephemeral shell sessions. Back up kubeconfig, not the state folder.
~/.kube/config
Same kubeconfig layout. Install through package managers keeps the binary in PATH. Session isolation works per terminal.
~/.kube/config
Respects KUBECONFIG env for split files. State under the XDG state home clears safely on odd behavior.
Frequently asked questions
What needs backing up for kubie?
Back up ~/.kube/config. Kubie reads contexts from there and spawns isolated shells per context. Session files under its state dir are disposable.
How do kubie shells stay isolated?
Run kubie ctx to list contexts from kubeconfig, then kubie ns for namespaces. Each shell gets its own context without touching the global current.
Notice an outdated path? Let us know.