kubestellar

Install, register, and validate KubeStellar multi-cluster control planes via ArgoCD GitOps.

11|9|Updated May 25, 2026
One-click install
npx skills add https://github.com/projectbluefin/lab --skill kubestellar-projectbluefin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kubestellar
Source: https://github.com/projectbluefin/lab/tree/main/docs/skills/kubestellar
Command: npx skills add https://github.com/projectbluefin/lab --skill kubestellar-projectbluefin

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about kubestellar

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install KubeStellar with ArgoCD?▼

Install KubeStellar by letting the kubestellar-applications parent Application reconcile three child Applications in order: PostgreSQL, core, then Console. Set kubeflex-operator.installPostgreSQL to false and use a separate postgres Helm release named postgres to avoid the post-install hook deadlock.

How do I register a workload execution cluster with KubeStellar?▼

Register a WEC by submitting the register-wec WorkflowTemplate with the cluster name parameter. It runs clusteradm get token, join with singleton mode, accept, and labels the ManagedCluster, which BindingPolicies select on.

Why does my KubeStellar ArgoCD sync stay stuck waiting for kubeflex-controller-manager?▼

The sync stalls because the core chart's PostgreSQL post-install hook maps to ArgoCD PostSync, which never fires while the wait-postgresql init container blocks health. Disable the operator's PostgreSQL install and deploy a separate postgres Application first.

Why is my downsynced namespace empty on the WEC?▼

An empty downsynced namespace means the BindingPolicy objectSelectors do not match labels on the objects inside the namespace. Label both the namespace and its contained objects so the selectors match everything intended for downsync.

Why does workload status never upsync back to the WDS?▼

Status upsync requires wantSingletonReportedState set to true on the BindingPolicy, and exactly one cluster must match the clusterSelectors. Without singleton reported state, ArgoCD and the Console only see specs, not real WEC status.

When should I not use this KubeStellar skill?▼

Do not use it for Console UI operations, adding k3s nodes to the shared cluster, or general ArgoCD sync issues; those belong to the console-dashboard, node-lifecycle, and gitops-argocd skills respectively.