-
Notifications
You must be signed in to change notification settings - Fork 486
x509: certificate signed by unknown authority #969
Comments
@joschi36 I've not seen this before. I'll take a look at how kubectl is dealing with unknown authority for certificates and model that behavior in Octant, probably as a flag like |
Just to confirm, |
Yes exactly, same computer and even same shell session. |
I am facing a similar issue.
This happens when I copied over the kubeconfig from a remote machine running Linux to my local machine and ran
|
Thank you for adding info, more cases and logging helps us out here. I'll be sure to update as soon as I get a fix for this. |
Determine what the standard practice is here ignore vs. set custom CA |
If the CA cert is not in the kubeconfig, I could see this happening. To test this theory out, we could create a way to set up verification skips for insecure certs. |
Yup. I am facing the same issue as well. It used to work before. I upgraded to kubectl Now, kubectl works great but octant fails with this error: UPDATE: Interestingly, using helm also fails if I don't prefix with the HTTPS_PROXY flag. Ideally it should be picked up from the kubeconfig. I get |
What steps did you take and what happened:
Started
octant
on local machine with kubeconfig which points to internal domain.What did you expect to happen:
Started ocant web ui without certificate error as ca certificate is imported in debian (
/etc/ssl/certs/ca-certificates.crt
) and working in every other server.Anything else you would like to add:
Environment:
octant version
): 0.13.0kubectl version
): v1.16.3The text was updated successfully, but these errors were encountered: