Helm Dashboard UI not accessible if cluster name contains slash

[sunnyar]

Description

Since I updated to the latest version, my helm dashboard UI has stopped working and I'm getting an error which I'm not able to understand.

It's giving a 500 error for the /api/helm/releases GET API call. But when I use the REST API calls through the swagger docs, it is working as expected. Also, not sure why is it not referencing to the default set cluster arn:aws:eks:us-east-2:xxxxxxxxxxx:cluster/xyz-cluster, instead just referring arn:aws:eks:us-east-2:xxxxxxxxxxxxx:cluster

Attaching screenshots for more reference

Can you please look into this issue and help. Thanks

Screenshots

Additional information

No response

[undera]

Try erasing whatever you have in your URL from local experiments and start with clean URL.

[sunnyar]

I've tried that also. If I clean-up the url and just have http://localhost:8080/ and enter, I observe two behaviours

1. It redirects to the url specifying one of the clusters installed, but still not the current one
   http://localhost:8080/#/arn:aws:eks:us-east-2:xxxxxxxxxxxx:cluster/abc-cluster/installed

2. Still throws the same error as shown in the screenshots

Have also tried Reset Cache option, but no help

[undera]

The way it works inside is: it tries to get the default cluster from your kubeconfig, or takes the first one.
In case it does not work, you can close the error message and choose different kubecontext from the left pane.

[undera]

Also mind the browser cache, which sometimes is a bit stubborn after change

[sunnyar]

I have tried clearing all cookies and cache, but nothing worked.
And when I close the error and select the clusters from the list of clusters on the left panel, only the url changes and nothing else happens. So stuck there also

[undera]

Fairly, I ran out of ideas what can be wrong there. Feel free to use older version if 2.x does not work for you.

[sunnyar]

Using v1.3.3 binary, the issue no longer exists on my end and I'm able to see all the list of clusters in the expected manner.

[yuma-brendan]

I'm running into the same issue, and I think that the helm-dashboard isn't parsing the cluster name properly since there's a slash in it.

Error #01: failed to get list of releases, cause: Kubernetes cluster unreachable: context "arn:aws:eks:us-east-2:XXXXXXXXXX:cluster" does not exist

The correct context name is: arn:aws:eks:us-east-2:XXXXXXXXXX:cluster/my-cluster

[yuma-brendan]

Renaming the context fixes the issue.

kubectl config rename-context arn:aws:eks:us-east-2:XXXXXXXXXX:cluster/my-cluster my-cluster

[sunnyar]

Renaming the context fixes the issue.

kubectl config rename-context arn:aws:eks:us-east-2:XXXXXXXXXX:cluster/my-cluster my-cluster

@yuma-brendan Thanks for the update. Will try this approach.

[undera]

This needs a fix, definitely