Description
Describe the bug
When adding a microk8s cluster to Headlamp, if there is a connectivity issue (such as "bad gateway" or "Request timed-out" during authentication), the delete option is unavailable in the UI. The expected outcome is that even with connectivity issues, the delete option should still be accessible to allow removal of the problematic cluster.
To Reproduce
Steps to reproduce the bug:
Steps to reproduce the bug:
Go to the Headlamp dashboard.
Add a microk8s cluster that has connectivity issues (e.g., "bad gateway" or "Request timed-out").
Observe that the cluster shows an error status but remains in the cluster list.
Attempt to delete the cluster from the UI; note that the delete option is not available.
Environment (please provide info about your environment):
Installation type: Linux
Headlamp Version: 0.26.0
Other: Using microk8s for Kubernetes cluster setup
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Queued