microk8s.kubectl does not respect `$KUBECONFIG` var

I know from https://github.com/ubuntu/microk8s/issues/180 that currently we cannot edit the default config file used by microk8s.kubectl, however the output of microk8s.kubectl config -h says that:

2. If $KUBECONFIG environment variable is set, then it is used as a list of paths (normal path delimitting rules for
your system). These paths are merged. When a value is modified, it is modified in the file that defines the stanza. When
a value is created, it is created in the first file that exists. If no files in the chain exist, then it creates the
last file in the list.

This is not happening however. Even when this env var is set, microk8s.kubectl is still referring to /snap/microk8s/current/client.config

It would be great if we could specify this in an ENV var as I work with a lot of existing CI scripts where it would not be feasible to add --kubeconfig /xxx/xxx/config to each. It would be great to be able to set this in a config var in lieu of being able to edit the default config file

[ktsakalozos]

Hi @nicja

Thank you for opening this issue.

The problem we are facing is because the kubectl wrapper has the path to kubeconfig file hard coded https://github.com/ubuntu/microk8s/blob/master/microk8s-resources/wrappers/microk8s-kubectl.wrapper#L9 . Instead we should have an arguments file under https://github.com/ubuntu/microk8s/tree/master/microk8s-resources/default-args and have the kubectl wrapper append any arguments to the command. This is aligned with what we do for the rest of the MicroK8s daemons and would allow users to define their own location of the kubeconfig file. If no location is set kubectl should use the $KUBECONFIG environment variable.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.