fix: correct kubeconfig cluster name and enhance control plane readin…

…ess checks in installation workflow

Signed-off-by: Sky Singh <[email protected]>

.github/workflows/installation-chart.yaml

@@ -113,21 +113,23 @@ jobs:
           export CLUSTER_VERSION=kindest/node:${{ matrix.k8s }}
           hack/setup-dev-base.sh
           
-          # Ensure kubeconfig exists
+          # Use correct cluster name 'karmada-host'
           mkdir -p ~/.kube
-          kind get kubeconfig --name=karmada > ~/.kube/karmada.config
+          kind get kubeconfig --name=karmada-host > ~/.kube/karmada.config
           
           export KUBECONFIG=~/.kube/karmada.config
           ct install --charts charts/karmada --debug --helm-extra-set-args '--set components={search,metricsAdapter,descheduler},apiServer.hostNetwork=true' --helm-extra-args "--timeout 800s" --skip-clean-up
           kubectl get pods -A
-      - name: Generate registration command
+      
+      - name: Verify control plane readiness
         run: |
           export KUBECONFIG=~/.kube/karmada.config
-          
-          # Wait for API server to be ready
           kubectl wait --for=condition=Ready pod -l app=karmada-apiserver -n karmada-system --timeout=300s
-          
-          # Generate token and registration command
+          kubectl wait --for=condition=Ready pod -l app=karmada-controller-manager -n karmada-system --timeout=300s
+
+      - name: Generate registration command
+        run: |
+          export KUBECONFIG=~/.kube/karmada.config
           karmadactl token create --print-register-command > register-command.sh
           chmod +x register-command.sh