Failed to get kubeconfig for seed

[vitality411]

Hello and thank you for starting this project!

I am currently also working on how to automatically add KKP UserClusters to ArgoCD. I first thought of using Argo Events and Argo Workflow. During my research, however, I came across this project and wanted to try it out.

I have ArgoCD and KKP on different clusters. I have installed the bridge on the ArgoCD cluster. On the KKP cluster I added the RBAC rules and the SA and generated a kubeconfig, which I configured in the ArgoCD cluster in the bridge.

The bridge is able to connect to the KKP and detect the seed, but it cannot find the kubeconfig of the seed:

kubermatic-argocd-bridge-bridge-547c87b997-pnccm kubermatic-argocd-bridge 2025/06/05 10:51:24 Syncing Clusters
kubermatic-argocd-bridge-bridge-547c87b997-pnccm kubermatic-argocd-bridge 2025/06/05 10:51:24 Failed to get kubeconfig for seed seed-1: secrets "kubeconfig-seed-1" not found

After I manually created the seed kubeconfig on the ArgoCD cluster in the namespace kubermatic, the bridge is able to sync the clusters:

kubermatic-argocd-bridge-bridge-547c87b997-pnccm kubermatic-argocd-bridge 2025/06/05 10:52:24 Syncing Clusters
kubermatic-argocd-bridge-bridge-547c87b997-pnccm kubermatic-argocd-bridge 2025/06/05 10:52:24 Got 2 UserClusters
kubermatic-argocd-bridge-bridge-547c87b997-pnccm kubermatic-argocd-bridge 2025/06/05 10:52:24 Reconciled Argo Secrets for 2 UserClusters
kubermatic-argocd-bridge-bridge-547c87b997-pnccm kubermatic-argocd-bridge 2025/06/05 10:52:24 Sync took 52046201

I assumed that the bridge would automatically fetch the seed kubeconfig on the KKP cluster. I assume it is automatically fetched when ArgoCD and KKP are running on the same cluster? Was the intention that this would work the same way if the components are running on different clusters?

Unfortunately I have no experience with go development, but I believe the problem should be here:

kubermatic-argocd-bridge/pkg/kkp_connector.go

Lines 63 to 65 in a504a14

	kubeconfigSecret, err := connector.staticClient.CoreV1().Secrets(kubeconfigNamespace).Get(context.TODO(), kubeconfigName, metav1.GetOptions{})
	if err != nil {
	log.Printf("Failed to get kubeconfig for seed %s: %s\n", name, err)

[4ch3los]

Hey there!
Thank you for opening the issue and your interest. You are totally right and its intended to work on seperate clusters. Apparently there was a issue, that the wrong kubeconfig was used to access Standard Resources like Secrets. But this is now fixed in https://github.com/svalabs/kubermatic-argocd-bridge/releases/tag/v1.3.2 :)