Kuber Help

To add a Kubernetes cluster manually (currently supporting Kubernetes version >= 1.9) to Kuber in order to manage it from your mobile device, you need to collect two parameters. One is the API server address of the Kubernetes cluster, and the other is the authentication information that API server is required.

Typically you can ask these information from the one who set up the cluster. But here are some methods that may help you start quicker by yourself:


If you can access Kubernetes via kubectl, all you need is to invoke kubectl config view --raw(or simply cat ~/.kube/config). The api server address shows as clusters[].cluster.serverin the output.

You are also able to find the authentication information from the output via users[].user. Kubernetes support multiple authentication methods, so the information may vary:

  1. tokenproperty: The authentication method is "Token" and the value of this property is the token.
  2. username&passwordproperties: The authentication method is "Credentials".
  3. client-certificate& client-keyproperties: The authentication method is "Certificate". Kuber requires a P12 format file for security. You can run openssl pkcs12 -export -out keystore.p12 -inkey /path/to/client-key -in /path/to/client-certificateto generate one (Kuber supports password-protected-p12, so you can optionally specify a password in the above command). The generated file "keystore.p12" is what we need. Now get the base64 format of it (echo keystore.p12 | base64) and paste it to Kuber.
  4. client-certificate-data& client-key-dataproperties: This is pretty similar to the above case. The only difference is this case the values are data instead of file paths. You can simply save the data as files and do just like above.
  5. execand the commandis "aws-iam-authenticator": The cluster is likely hosted by AWS EKS. You can get the endpoint & cluster id from the AWS EKS dashboard (see the picture below, cluster id is "test"). And you need to fill with your AWS access ID and secret key.
  6. Other cases. The authentication is not supported by Kuber currently. Send us an email (kuber@nssurge.com) to let us know and we will try to add it as fast as we can. At the same time, you may want to ask the cluster owner to setup other authentications that Kuber supporting.


If you cluster have installed Rancher, you can find Kubeconfig on the rancher dashboard (see the picture below), and then you can follow the instructions above.