Not possible to add more than one cluster in the desktopclient

[VonNao]

Hello,

tried headlamp today and it looks amazing. Sadly i got the following Problem. I added our first cluster, which worked like a charm. After that i tried to add another cluster, from a different kubeconfig with a different context name. Loading the file worked "Clusters successfully set up!"
But the cluster isn't displayed in the ui. After restarting the client the ui displayed the new cluster but removed the old one.

OS: Windows 11
Client-Version: 0.25.0

[joaquimrocha]

Hi @VonNao . This looks like a serious problem. Thanks for reporting. We will prioritize this and get back to you.

[lukas-becker0]

How did you add the new cluster configuration ?

I just started using headlamp and it lets me select from all my clusters, but I did not add them through headlamp.

[VonNao]

@lukas-becker0 Just via the "load cluster" button. How did you add them to headlamp?

[lukas-becker0]

@VonNao by adding them directly to ~/.kube/config e.g. through the azure cli but you can also do this manually with a text editor

[VonNao]

@lukas-becker0 Ah we are working with wsl. So my clusteconfigs are under wsl mount point's ~/.kube/config. Is it possible to point headlamp to a folder so i picks up new configs automatically?

[joaquimrocha]

@VonNao Adding them through the UI should definitely work. Next week we will investigate whether we have a regression here.
Adding them to the .kube/config for now Headlamp reads only that one kubeconfig by default and doesn't read a whole directory (but we want to change it to do that), so you would have to merge your kubeconfigs into that default one.

[MinHyeok90]

I have same issue. I used a windows client. 0.25.1

I added 5 clusters but only one was always visible.
I deleted the one cluster, but there was still one cluster left.
after deleting each single cluster for 4 times more, UI show the empty.

[antonosmond]

Same issue. For some additional context, multiple clusters in a single kubeconfig works just fine. The issue is when you have multiple kubeconfigs. Say I have the following kubeconfigs with the following clusters:

~/.kube/nonprod

• sandbox
• staging

~/.kube/prod

• prod

If I add a cluster in the desktop app, it asks for the kubeconfig. I select the nonprod kubeconfig. It succesfully adds the clusters and now I have both the sandbox and staging clusters available.
I add a new cluster and this time I select my prod kubeconfig.
At this point it seems to get in a pickle. I close and reopen the app and now my prod cluster from the prod kubeconfig is there but the clusters from the nonprod kubeconfig have gone.
It feels like maybe the app is storing the path to the kubeconfig centrally and assumes there will only ever be one kubeconfig for all clusters. But it should be able to handle many clusters in many kubeconfigs i.e. store the relevant kubeconfig path for each cluster.

So basically what @joaquimrocha said:

Adding them to the .kube/config for now Headlamp reads only that one kubeconfig by default and doesn't read a whole directory (but we want to change it to do that), so you would have to merge your kubeconfigs into that default one.

[rk4827]

Same issue on the Mac as well.