failed to access from outside VM: Unable to connect to the server: x509: certificate is valid for 127.0.0.1...
See original GitHub issuePlease run microk8s.inspect
and attach the generated tarball to this issue.
inspection-report-20190405_143043.tar.gz
Hi, as the issue subject said, i failed to access microk8s installed on my VM, the host OS is Mac.
I tried to install it by getting the config using microk8s.config
and copy it to the host machine.
and i got this
ibk:~
$ KUBECONFIG=~/microk8s_kubeconfig kubectl get pods
Unable to connect to the server: x509: certificate is valid for 127.0.0.1, 10.152.183.1, 10.0.2.15, not 192.168.33.10
I’m aware about #110, but it is my local network, so it should be safe.
The solution seems to be to regenerate the certificate, but i’m not sure how to do it on microk8s.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Unable to connect to the server: x509: certificate is valid for ...
Hi, as the issue subject said, i failed to access microk8s installed on my VM, the host OS is Mac. I tried to...
Read more >microk8s, DEVOPS : Unable to connect to the server: x509
The microk8s documentation has a troubleshooting guide for this error: I get "Unable to connect to the server: x509" on a multi-node cluster....
Read more >Troubleshoot backend health issues in Application Gateway
Cause: This error occurs when Application Gateway can't verify the validity of the certificate. Solution: To resolve this issue, verify that the ...
Read more >PKI certificates and requirements - Kubernetes
Kubernetes requires PKI certificates for authentication over TLS. If you install Kubernetes with kubeadm, the certificates that your cluster ...
Read more >The Definitive Debugging Guide for the cert-manager ...
This guide helps you debug communication issues between the Kubernetes API server and the cert-manager webhook pod. The error messages ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @iwanbk, could you try the
microk8s.config -l
(note the-l
flag) to produce the config. If this is no good for you, could you try the--edge
channel (sudo snap install microk8s --classic --edge
)? The issue you are reporting is already addressed and is released to edge, we will soon release it to the rest of the channels.I also have this issue, I’m running micro8ks inside a VM configured with two interfaces, one NATed and one host-only, to give host->guest access while also giving the VM internet access without exposing it to the world (which bridging would).
It seems to me that the problem is that the code assumes only the default interface is external, and includes only that in the certificate instead of including both external interfaces as it should. Apparently it still binds to both interfaces so why shouldn’t it include both addresses in the certificate?