This bug was caused because a bad parsing of the kubeconfig.
The token should be the secret from k8s for the created service
account.
When adding a k8s cluster, a clusterrole, clusterrolebinding, and
serviceaccounts are created.
Tests are needed for oauth2 and userpass kubeconfigs.
Change-Id: I6a4a2834bd6477f255e8ca48e7f53cd3a0d3fddf
Signed-off-by: David Garcia <david.garcia@canonical.com>