I am seeing the following error when configuring helm with the curated repo.
helm init --client-only
Creating /Users/xxxxx/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: x509: certificate signed by unknown authority
I am able to download this file using curl and then I get the same error using helm repo update.
I've been looking around the electric inter-webs and I see this issue has been coming & going. Is there a viable workaround for this issue?
More Information;
macOS 10.13.5
docker 18.03.1-ce-mac65
go 1.10.3
Output of helm version:
helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Output of kubectl version:
kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T15:22:13Z", GoVersion:"go1.9.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-28T20:13:43Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Amazon EKS
Ready to close. Discovered that our corporate IT department had auto-magically installed the Netskope umberella agent on our Macs and it was re-writing the signing authority in the certificate chain. Have disabled it and all is now well.
Most helpful comment
Ready to close. Discovered that our corporate IT department had auto-magically installed the Netskope umberella agent on our Macs and it was re-writing the signing authority in the certificate chain. Have disabled it and all is now well.