You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Old kubeconfig for docker-desktop got regenerated and it doesn't allow you do add new cluster with same name and no option to remove old cluster
To Reproduce
Steps to reproduce the bug:
[Go to '...']
[Click on '....']
[Scroll down to '....']
[See error]
Environment (please provide info about your environment):
Installation type: [e.g. Linux-Flatpak/Linux-Tarball/Linux-AppImage/Windows//Windows-Chocolatey/Windows-Winget/WSL/Mac/Mac-Homebrew/... or Container-Image/In-Cluster/Helm/...]
Headlamp Version: [X.Y.Z]
Other: [e.g. any other relevant info]
Are you able to fix this issue?
[Yes (I will propose a PR) / No.]
Do you want to help fix this issue? Please see our contribution docs. For any non-trivial contributions, we advise you to join our our slack channel to discuss the implementation with Headlamp's core developers.
Additional Context
[If needed, add any other info or screenshots about the bug here.]
[Is it a regression? What version of Headlamp did not have this bug?]
The text was updated successfully, but these errors were encountered:
Yeah. This was a choice we made a while ago with the goal of not touching the user's kubeconfig, however, this is so confusing that I believe we should just warn the user and proceed with deleting.
Let's make this available in the next release!
Describe the bug
Old kubeconfig for docker-desktop got regenerated and it doesn't allow you do add new cluster with same name and no option to remove old cluster
To Reproduce
Steps to reproduce the bug:
Environment (please provide info about your environment):
Are you able to fix this issue?
[Yes (I will propose a PR) / No.]
Additional Context
[If needed, add any other info or screenshots about the bug here.]
[Is it a regression? What version of Headlamp did not have this bug?]
The text was updated successfully, but these errors were encountered: