devopshivehq/kubech

Set kubectl context/namespace per shell/terminal to manage multi Kubernetes clusters at the same time (it's parallel kubectx/kubens)

kubech's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update luizm/action-sh-checker action to v0.8.0

Detected dependencies

github-actions

.github/workflows/ci.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• luizm/action-sh-checker v0.3.0@7f44869033b40ee4ffe7dc76c87a1bc66e3d025a

---

• Check this box to trigger a request for Renovate to run again on this repository

Kubech does not work with Helm commands

Hi,

If you try to run this tool with helm commands, helm will give you an error of the cluster not being responsive.

Regards,
Hamza Masood

Unable to switch context because of directory not found error.

Firstly, Thanks for your effort to give the utility to mange multi-cluster at same time.
When I executed the change context command, the below error occurs.

aliver@dev-server:~$ kubechc arn:aws:eks:us-east-1:xxxxxx:cluster/MyCluster
touch: cannot touch '/home/aliver/.kube/config.dest.d/arn:aws:eks:us-east-1:xxxxxx:cluster/MyCluster-default': No such file or directory
chmod: cannot access '/home/aliver/.kube/config.dest.d/arn:aws:eks:us-east-1:xxxxxx:cluster/MyCluster-default': No such file or directory
-bash: /home/aliver/.kube/config.dest.d/arn:aws:eks:us-east-1:xxxxxx:cluster/MyCluster-default: No such file or directory

Seem it should mkdir -p xxx firstly to touch the new configuration.

Failed to switch context when using separate kubeconfig files

I am using the $KUBECONFIG environment variables to provide path for kubeconfig files (kubeconfig file per cluster)

example:

I have 3 different kubeconfig files: sandbox, staging and production

it seems running kubechc is able to list the context, but then it fails to switch.

$ kubechc
sandbox
staging
production

but then trying to switch context

$kubechc production
W0505 17:04:28.166764   49998 loader.go:223] Config not found: /Users/islamshehata/.kube/config
error: cannot locate context production
error: no context exists with the name: "production"

kubectx works fine with that setup.

find: -printf: unknown primary or operator

Firstly, thank you for writing this and making this widely available. This is a boon for managing multiple clusters.

The installation steps as described in the documentation worked just fine.

I can use kubech just fine and kubechc lets we switch the clusters just fine as well. Everytime i switch context in a new terminal i see the below message.

find: -printf: unknown primary or operator
find: -printf: unknown primary or operator

My workstation is Intel Mac OS.

Not sure about the cause of this and if its a me problem. Have you run into this by any chance ?

ZSH _kube_config:3: = not found error

I'm using ZSH while trying to run kubech commands I got an error.

Installation steps:

git clone https://github.com/aabouzaid/kubech ~/.kubech
echo 'source ~/.kubech/kubech' >> ~/.zshrc

I can see kubechc and kubechn commands available, however.

(⎈|eks-develop:monitoring)➜  ~ kubechc
arn:aws:eks:eu-west-2:xxx:cluster/eks-stable
arn:aws:eks:us-east-2:xxx:cluster/prod-eks-qAZZREu2
docker-desktop
eks-develop
kind-ckad
kind-monitoring
rancher-desktop

(⎈|eks-develop:monitoring)➜  ~ kubechn
calico-apiserver
calico-system
default
kube-node-lease
kube-public
kube-system
monitoring
tigera-operator

changes to namespace or cluster .

(⎈|eks-develop:monitoring)➜  ~ kubechc eks-develop
_kube_config:3: = not found

(⎈|eks-develop:monitoring)➜  ~ kubechn kube-system
_kube_config:3: = not found