This message was deleted.
# rancher-desktop
a
This message was deleted.
👍 1
a
I have the same problem!
c
@future-keyboard-11621 what platform is this happening on?
also, what is causing that error? is it coming from when you do
kubectl ...
?
f
This is not really a rancher desktop ISSUE per se, its more about how to configure it proprely I am running rancher-desktop on ubuntu 22.0.4 Trying to access it over the network on my macOS with Lens
I removed the
certificate-authority-data
and added
insecure-skip-tls-verify: true
This makes it work with lens. But its not really the proper solution
c
I figured it’s related to kubectl configuration by looking at this: https://github.com/kubernetes/kubectl/blob/65805ae28084bd77a0d7b2f10d34fe87e1d45c93/pkg/proxy/proxy_server.go#L147 I was also going to suggest
insecure-skip-tls-verify: true
to see if that suppresses it. It looks like a misconfiguration, I will try to see what is causing this.
f
I think its working as intended? I am trying to access the cluster on a different IP than the host computer. That is what the error tells me also.
p
Yeah, we never really thought about accessing the internal Kubernetes cluster (running k3s) from outside the host machine; you'll probably need to tell the client to ignore the cert issues.
c
I have created an enhancement request that should address this scenario https://github.com/rancher-sandbox/rancher-desktop/issues/3186
🙌 1