certificate signed by unknown authority

[attardi]

Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT

What happened: $ kubeless get-server-config FATA[0000] Unable to read the configmap: Error while fetching config location: Get https://90.147.161.27:443/apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/functions.kubeless.io: x509: certificate signed by unknown authority

What you expected to happen: return the configuration

How to reproduce it (as minimally and precisely as possible): See above.

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version): Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T21:07:38Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.1", GitCommit:"b1b29978270dc22fecc592ac55d903350454310a", GitTreeState:"clean", BuildDate:"2018-07-17T18:43:26Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

• Kubeless version (use kubeless version): Kubeless version: v1.0.0-alpha.7

• Cloud provider or physical cluster: physical cluster

[andresmgot]

Hi @attardi, apparently the configured certificate-authority data set in the default ~/.kube/config is not recognized. It may an issue related to K8s 1.11, right now the supported versions are 1.9 and 1.10, would you mind sending the structure of your ~/.kube/config to try to isolate the issue?

[benatkin]

I was able to solve this w/ microk8s by running microk8s.config > ~/.kube/config instead of kubectl config view > ~/.kube/config - it turns out there's another way which is to add --raw, as in kubectl config view --raw > ~/.kube/config, but microk8s.config is shorter