rancher-desktop icon indicating copy to clipboard operation
rancher-desktop copied to clipboard

Rancher Desktop UI is "Waiting for Kubernetes API" after update to 1.16.0

Open mreinhart2805 opened this issue 1 year ago • 4 comments

Actual Behavior

Rancher Desktop UI is showing the message "Waiting for Kubernetes API" but all work as expected (Docker and Kubernetes)

Steps to Reproduce

Just run Rancher Desktop after update to 1.16.0

Result

Rancher Desktop is runing all Services like Docker and k8s. But UI is showing up "Waiting for Kubernetes API" in the bottom right corner. image

I've test docker and Kubernetes and it works as expected.

Expected Behavior

The Rancher Desktop UI is hiding the startup indicator and the message "Waiting for Kubernetes API"

Additional Information

I've also applyed factory reset. But this have no effect to this issue.

Rancher Desktop Version

1.16.0

Rancher Desktop K8s Version

1.28.14

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 10 Enterprise 22H2 Build: 19045.4412

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

N/A

mreinhart2805 avatar Oct 04 '24 15:10 mreinhart2805

@mreinhart2805 , Would you be able to share application logs from your machine please?

gunamata avatar Oct 04 '24 16:10 gunamata

same problem ,same version

manondidi avatar Oct 23 '24 06:10 manondidi

@mreinhart2805 Looking at the k3s logs it looks like you are behind a proxy, the logs below indicate that the k3s agent is not able to communicate with the server.

time="2024-10-04T23:47:27+02:00" level=info msg="Connecting to proxy" url="wss://192.168.127.2:6443/v1-k3s/connect"
time="2024-10-04T23:47:27+02:00" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp 192.168.127.2:6443: connect: network is unreachable"
time="2024-10-04T23:47:27+02:00" level=error msg="Remotedialer proxy error; reconnecting..." error="dial tcp 192.168.127.2:6443: connect: network is unreachable" url="wss://192.168.127.2:6443/v1-k3s/connect"
E1004 23:47:27.757014     605 kubelet_node_status.go:701] "Failed to set some node status fields" err="failed to validate nodeIP: node IP: \"192.168.127.2\" not found in the host's network interfaces" node="ki1-r-w-5150"

If your system running behind a proxy, it is crucial to configure the rancher desktop accordingly.

Nino-K avatar Oct 23 '24 17:10 Nino-K

I am facing the same issue. V1.16.0 on windows 11 pro 23H2. Network Status: online Kubernetes:1.30.6 CE:moby. I am not on VPN and do not have proxy configured in my machine. Its stuck on Waiting for Kubernetes API.

On searching i found a related issue which was fixed in older version now surfaced again.

I have networkingMode=mirrored in .wslconfig. This is essential for rancher desktop to work in VPN when i connect to my office enterprise network for daily work.

aaraodeo avatar Dec 01 '24 13:12 aaraodeo

I am facing the same issue. V1.16.0 on windows 11 pro 23H2. Network Status: online Kubernetes:1.30.6 CE:moby. I am not on VPN and do not have proxy configured in my machine. Its stuck on Waiting for Kubernetes API.

On searching i found a related issue which was fixed in older version now surfaced again.

I have networkingMode=mirrored in .wslconfig. This is essential for rancher desktop to work in VPN when i connect to my office enterprise network for daily work.

On search i found this might resolve the issue: https://github.com/rancher-sandbox/rancher-desktop/pull/7577 Hoping fix will be available in next version 1.17.0 planned to release soon in dec 2024 month.

aaraodeo avatar Dec 01 '24 14:12 aaraodeo

I will close this issue since it seems to have been resolved #7577, please feel free to reopen it.

Nino-K avatar Mar 10 '25 20:03 Nino-K