config set-context is not working

inspection-report-20190204_171917.tar.gz Please run microk8s.inspect and attach the generated tarball to this issue.

When I run following command

$ microk8s.kubectl config set-context qqq-staging --kubeconfig="/home/www/admin.conf"

Context "qqq-staging" modified.

and running following does not list created context:

$ microk8s.kubectl config get-contexts
CURRENT   NAME       CLUSTER            AUTHINFO   NAMESPACE
*         microk8s   microk8s-cluster   admin

Am I missing something here, or is it a known issue?

[ktsakalozos]

Hi @reyou,

Here is what I tried. First I moved the kubeconfig file that you need to access MicroK8s in the default location that is also read/write:

microk8s.kubectl config view > ~/.kube/config

Then I made sure I have a kubectl (other than the kubectl you get with microk8s):

sudo snap install kubectl --classic

At this point you should be able to access the MicroK8s cluster with kubectl. For example:

> kubectl get no
NAME               STATUS   ROLES    AGE    VERSION
jackal-vgn-fz11m   Ready    <none>   8m2s   v1.13.2

Adding the context with kubectl now works:

> kubectl config set-context qqq-staging 
Context "qqq-staging" created.

> kubectl config get-contexts
CURRENT   NAME          CLUSTER            AUTHINFO   NAMESPACE
*         microk8s      microk8s-cluster   admin      
          qqq-staging                             

microk8s.kubectl uses always the kubeconfig of microk8s stored on a read only location this is why you need a non-microk8s kubectl.

[reyou]

OK, I had to follow below;

https://blog.ubuntu.com/2017/01/28/ubuntu-core-how-to-enable-aliases-for-your-snaps-commands

snap aliases

snap unalias kubectl