Fix critical bug: use correct context when connecting to remote clusters

The operator was using the current-context from the kubeconfig instead of
selecting the context that matches the cluster name. This caused all remote
clusters to connect to whichever cluster was set as current-context.

Now we explicitly set the CurrentContext to match the cluster name before
creating the REST config, ensuring each remote cluster uses its own context.

This fixes the issue where ottawa cluster was showing 0 routes because it
was actually querying the robbinsdale cluster.

Author: rajsinghtech

internal/controller/cluster_manager.go

@@ -193,10 +193,18 @@ func (m *ClusterManager) createClusterClient(ctx context.Context, dashboard *hom
 		return nil, fmt.Errorf("key %q not found in secret %s", key, clusterCfg.SecretRef.Name)
 	}
 
-	// Parse kubeconfig
-	restConfig, err := clientcmd.RESTConfigFromKubeConfig(kubeconfigData)
+	// Parse kubeconfig and use the context matching the cluster name
+	config, err := clientcmd.Load(kubeconfigData)
 	if err != nil {
-		return nil, fmt.Errorf("failed to parse kubeconfig: %w", err)
+		return nil, fmt.Errorf("failed to load kubeconfig: %w", err)
+	}
+
+	// Override current-context to match the cluster name
+	config.CurrentContext = clusterCfg.Name
+
+	restConfig, err := clientcmd.NewDefaultClientConfig(*config, &clientcmd.ConfigOverrides{}).ClientConfig()
+	if err != nil {
+		return nil, fmt.Errorf("failed to create REST config for context %s: %w", clusterCfg.Name, err)
 	}
 
 	// Create client for the remote cluster