I went through the install and usage instructions, only to find that KUBECONFIG was being set in /etc/environment. Also noticed k8s-tew creates a systemd service where its installed. I find this a bit intrusive since no other Kubernetes commands/apps do such a thing. Its too forceful. Makes assumptions this is what I wanted. I do not see a reason why this cannot be a free standing cli that can be executed from anywhere as long as its in the user's PATH.
As is, I cannot use this anywhere other than a homelab since it makes too many undesirable changes to the system. No other Kubernetes cli tools does this: kubectl, istioctl, etc, and all manage to work with Kube clusters just fine. I cannot raise a PR since I do not know if these changes are absolute requirements for k8s-tew to work. If so, that would be unfortunate.
I went through the install and usage instructions, only to find that KUBECONFIG was being set in
/etc/environment
. Also noticed k8s-tew creates a systemd service where its installed. I find this a bit intrusive since no other Kubernetes commands/apps do such a thing. Its too forceful. Makes assumptions this is what I wanted. I do not see a reason why this cannot be a free standing cli that can be executed from anywhere as long as its in the user's PATH.As is, I cannot use this anywhere other than a homelab since it makes too many undesirable changes to the system. No other Kubernetes cli tools does this: kubectl, istioctl, etc, and all manage to work with Kube clusters just fine. I cannot raise a PR since I do not know if these changes are absolute requirements for k8s-tew to work. If so, that would be unfortunate.