title: helm and kubectl context mismatch
body: <p>I'm having trouble understanding <code>helm</code>'s use of <code>helm --kube-context=microk8s install ...</code> should install into the context <code>microk8s</code> thus into my local microk8s cluster rather than the remote GKE cluster which I once connected to.</p>
  
  <p>This however fails due to <code>Error: could not get Kubernetes config for context "microk8s": context "microk8s" does not exist</code> if I run e.g. <code>helm --kube-context=microk8s install --name mereet-kafka</code> after successfully running <code>helm init</code> and adding necessary repositories.</p>
  
  <p>The context <code>microk8s</code> is present and enabled according to <code>kubectl config current-context</code>. I can even reproduce this by running <code>helm --kube-context=$(kubectl config current-context) install --name mereet-kafka</code> in order to avoid any typos.</p>
  
  <p>Why can't <code>helm</code> use obviously present contexts?</p>