When we try to navigate to Cluster Explorer, we are getting a prompt which says, Cluster Explorer fails with HTTP Error 500
Here is the ROUTE table info:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 102 0 0 em1
10.42.224.192 0.0.0.0 255.255.255.192 U 0 0 0 *
10.42.224.193 0.0.0.0 255.255.255.255 UH 0 0 0 calidc58853bb1d
10.42.224.194 0.0.0.0 255.255.255.255 UH 0 0 0 cali870b65cd0c4
10.42.224.195 0.0.0.0 255.255.255.255 UH 0 0 0 cali1b52c46736d
10.42.224.196 0.0.0.0 255.255.255.255 UH 0 0 0 cali68c1f09b709
10.42.224.197 0.0.0.0 255.255.255.255 UH 0 0 0 cali6671c04c2b5
10.42.224.200 0.0.0.0 255.255.255.255 UH 0 0 0 cali69e13da5b62
Kindly let me know the fix for this issue.
Can you confirm the cluster you’re trying to view is up and reachable, for instance can kubectl contact it directly?
Cluster is created, up and reachable. But I am not able to get the kubectl terminal access.
Ok, I think we’re flicking around concepts here.
- This is a Rancher 2.x issue
- Can you view the target cluster as normal in Cluster Manager (apart from terminal access)?
- Can you access the target cluster from where Rancher is hosted via other tools such as the
kubectl cli tool
- Is it possible to confirm the rancher agent is running correctly in the target cluster?
I have the same issue with rancher v2.5.9
I can see the target cluster via Cluster Manager.
I can reach the cluster using kubectl cli.
The rancher agent is up and working properly; looking at the logs.
I’m also facing the same problem, any update on this issue?
Same issue here. Any ideas?
I am facing the same issue. It was working, but suddenly it stopped working. The cluster can be accessed by kubectl, and everything there is up and running (pods, services, etc). The only thing failing is the cluster explorer. Any ideas?
