What problem does it solve? Operating a KubeStellar multi-cluster control plane involves non-obvious failure modes—PostgreSQL install deadlocks, PostCreateHook drift, missing status upsync—that stall installations and leave workloads never reaching execution clusters. This Skill encodes the lab's proven install, registration, and troubleshooting procedures. ## Core Features & Use Cases - GitOps Install & Upgrade: Reconcile PostgreSQL, KubeStellar core, and Console child Applications in the correct order through ArgoCD, avoiding the postgres hook deadlock and PostCreateHook drift. - WEC Registration & Smoke Testing: Register workload execution clusters with clusteradm via the register-wec WorkflowTemplate and validate downsync plus status upsync with the kubestellar-smoke-test acceptance gate. - BindingPolicy Authoring & Diagnostics: Write BindingPolicies with correct clusterSelectors, objectSelectors, and wantSingletonReportedState, and diagnose failures like empty downsynced namespaces or missing status upsync. - Use Case: A new edge cluster must join the fleet. Submit the register-wec workflow, confirm the ManagedCluster reports Joined and Available, author a BindingPolicy targeting its labels, and run the smoke test to prove end-to-end downsync and status upsync. ## Quick Start Ask the assistant to verify KubeStellar health by checking the kubestellar-applications ArgoCD app, the its1 and wds1 control planes, and then running the kubestellar smoke test workflow.