Issue with adding additional clusters using different kubeconfigIDs

[mrCherry97]

Description

When a user already has a connected cluster, the system does not allow connecting an additional cluster using a different kubeconfigID. The existing kubeconfigID appears to block or override the ability to register another cluster, even when valid credentials are provided.

This issue occurs during the cluster connection flow and prevents users from managing multiple clusters as expected.

Expected result

Users should be able to connect multiple clusters using different kubeconfigID clusters.
Each cluster connection should be handled independently without conflicts.

Actual result

When one cluster is already connected, attempting to connect another cluster fails.
The system does not accept the new kubeconfigID and prevents the second cluster from being added.

Steps to reproduce

1. Connect a cluster using a valid kubeconfigID.
2. Verify the cluster is successfully connected.
3. Attempt to connect a second cluster using a different kubeconfigID.
4. Observe that the connection fails or is blocked.

Troubleshooting

• Verified that the second kubeconfigID is valid.
• Retried the connection using different kubeconfig files.
• Logged out and logged back in.
• Cleared browser cache.
• Checked logs for authentication or authorization errors.