Unable to connect to the kube cluster: UNABLE_TO_GET_ISSUER_CERT

[mitchellmaler]

Describe the bug Getting error"Unable to connect to the kube cluster: UNABLE_TO_GET_ISSUER_CERT"

My kubeconfig is using a self signed cert to connect to the cluster. The CA and private key exist in the kubeconfig.

To Reproduce

kubelive get pod

Expected behavior

Shows pods

Desktop (please complete the following information):

• OS: [e.g. iOS] MacOS 10.14.6

[ameerthehacker]

@mitchellmaler does your kubectl tool works as expected?

[mitchellmaler]

Yes it does

$ kubectl get pods                                                                                    
NAME                                        READY   STATUS    RESTARTS   AGE
angular-service-sample-6644cdb8db-5224t     2/2     Running   0          3d
angular-service-sample-6644cdb8db-svgm6     2/2     Running   0          3d
aspnetcore-service-sample-b7758cbdb-bhxwx   2/2     Running   0          2d23h
aspnetcore-service-sample-b7758cbdb-rnvbw   2/2     Running   0          3d1h
tiller-deploy-576487998c-sf9zs              1/1     Running   0          3d
$ kubelive get pod
Unable to connect to the kube cluster: UNABLE_TO_GET_ISSUER_CERT

[mitchellmaler]

Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T12:36:28Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:02:58Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

[ameerthehacker]

@mitchellmaler I will investigate the issue and will update you, it should be something to do with the authentication API

[ingshtrom]

Any update on this? I'm seeing this as well in all of my clusters.

[ameerthehacker]

@ingshtrom have you referenced the cert to connect to the cluster in the kubeconfig

[ingshtrom]

I have. I actually think this is an upstream issue as I tried connecting to my cluster via the kubernetes node client directly and I got the same output reported here: https://github.com/kubernetes-client/javascript/issues/327

[ameerthehacker]

Thanks, @ingshtrom keeping this open until the upstream fixes it