Table of Contents
The showcase demonstrates the multiple sessions per shell feature, selecting items and fuzzy searching for them. The same features apply for handling namespace as well
This BLAZINGLY FAST plugin written in Rust makes it possible to have one context per shell active.
Why isolated context? Typically when you switch context in kubectl (with ex. kubectx), the change happens on all terminal instances. That is because the change is saved in your $HOME/.kube/config file and is read on every interaction with kubectl.
This will lead to the inevitable scenario of working on a local cluster, and needing to do something quickly in production. You open another terminal, switch context, do your work and then go right back to your old terminal. The issue is that the prompt has not visually refreshed to the actual context. Often the following command you type will not be dangerous, and you will notice that you did it in production, but sometimes the damage is severe💥.
We will use the config merge capability of kubectl to override the current-context setting. By creating a file with the correct context and prepend it to the KUBECONFIG environment variable
The program will output the SESSION_CONTEXT and the alias created in Installation will do the prepending
export KUBECONFIG=$SESSION_CONTEXT:$KUBECONFIG
Tool: custom script
| Command | kubesess | kubectx |
|---|---|---|
| 20 runs with no ctx switch and no kubectl calls | .024931342 | 1.744966963 |
| 20 runs with ctx switch and no kubectl calls | .049247181 | 3.775905777 |
| 20 runs with ctx switch and calling kubectl get nodes | 11.167763585 | 15.265837926 |
I am using the input argument variant for both tools, using fzf or tab completion is harder to do.
Tool: hyperfine
| Command | Mean [ms] | Min [ms] | Max [ms] | Relative |
|---|---|---|---|---|
kubesess -v docker-desktop context |
1.3 ± 0.2 | 1.0 | 2.2 | 1.00 |
kubectx docker-desktop |
91.8 ± 3.3 | 85.1 | 100.7 | 71.23 ± 13.64 |
| Command | Mean [ms] | Min [ms] | Max [ms] | Relative |
|---|---|---|---|---|
kubesess -v monitoring namespace |
42.8 ± 1.4 | 41.6 | 46.3 | 1.00 |
kubens monitoring |
914.1 ± 26.4 | 869.2 | 953.2 | 21.35 ± 0.92 |
* Disclaimer * kubectx and kubens are a wonderful tools, been using it allot but my workflow is different and thus this tool was created. Probably most of the speed gains are because I am bypassing kubectl and just editing config files.
- No dependencies
Download and extract the binary.
wget "https://github.com/Ramilito/kubesess/releases/download/1.2.2/kubesess_1.2.2_x86_64-unknown-linux-musl.tar.gz" && \
mkdir -p $HOME/.kube/kubesess && tar zxpf kubesess_1.2.2_x86_64-unknown-linux-musl.tar.gz -C $HOME/.kube/kubesess
A script wrapper called kubesess.sh is provided for easier use, source the script wrapper in your .bashrc, .zshrc.
source ~/.kube/kubesess/kubesess.sh
See the available commands by running kubesess -h, output from the program needs to be added to $KUBECONFIG env variable.
kc #kube_context: Sets session context
kcd #kube_context_default: Sets context across all shells
kn #kube_namespace: Sets namespace
knd #kube_namespace_default: Sets namespace across all shells- List all contexts
- Present it with fzf
- Write selection to file
- Output link to file
- Add alias to handle output
- Cleanup after use
- clean prepended env variable
- output files to $HOME/.cache/kubesess
- Handle different namespaces per context
- Use rust tui instead of fzf
- Add option to make changes stick (default-context)
- Add option to make changes stick (default-namespace)
- Add tests
- Add tab completion - clap-rs/clap#1232
- Add to brew
- Add error handling
A hard reset will fix most issues, to do that just remove the ~/.kube/kubesess/cache folder.
*The downside is that your last visited namespace per context will be lost.