kubesphere-devops-argocd
Use when configuring ArgoCD in KubeSphere DevOps, including GitOps deployments, application management, SSO setup, or troubleshooting ArgoCD issues
npx skills add kubesphere/kubesphere --skill kubesphere-devops-argocd --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Instructs the agent to configure ArgoCD integrated with KubeSphere DevOps, covering GitOps deployments, Application and ApplicationSet management, SSO setup with Dex, multi-cluster scenarios, and troubleshooting ArgoCD sync issues.
How it works
Describes how ArgoCD v2.11.7 is used as a bundled subchart and follows declarative GitOps. Explains two creation methods:
- Direct ArgoCD Application in the argocd namespace (admin-only access)
- KubeSphere GitOps Application created in a tenant namespace, with KubeSphere automatically creating a corresponding ArgoCD Application in argocd
It outlines the architecture flow from tenant Application CRs to ArgoCD Applications, and from ArgoCD syncing to deployed resources. It lists ArgoCD components and their Pod name patterns, the namespace argocd, and how to verify status and access the UI.
Also specifies configuration blocks to enable ArgoCD, customize ArgoCD settings, and how to manage applications and ApplicationSets, including examples for creating and managing applications via Kubernetes manifests and KubeSphere GitOps API. It covers repository management, SSO with Dex, CLI installation, and common ArgoCD CLI tasks. It includes warnings about required labels and avoiding manual ArgoCD Application creation when using the KubeSphere GitOps flow.
When to use it
Use when setting up GitOps continuous deployment, configuring ArgoCD applications and ApplicationSets, enabling Dex-based SSO, managing multi-cluster deployments, troubleshooting ArgoCD sync issues, or configuring repository credentials as part of the ArgoCD integration.
What it can touch
The skill references commands and manifests that touch:
- Namespace argocd and various ArgoCD resources
- Secrets in argocd (for Dex credentials)
- Secrets for repository credentials (repo-github-example) and Helm repos
- The KubeSphere GitOps API at /kapis/gitops.kubesphere.io/v1alpha1/
- The ArgoCD CLI (argocd) and related Kubernetes resources
Caveats
Notes emphasize the critical label gitops.kubesphere.io/argocd-location: argocd must be present on Applications; without it the controller ignores the Application and ArgoCD Application is not created. It also warns not to manually create an ArgoCD Application when using the KubeSphere GitOps flow due to potential conflicts. The method requires the KubeSphere GitOps controller to be running. No licensing details beyond NOASSERTION are provided in this summary.
# KubeSphere DevOps ArgoCD Configuration ## Overview KubeSphere DevOps includes **ArgoCD v2.11.7** as a bundled subchart for GitOps continuous deployment. ArgoCD follows the declarative GitOps pattern, automatically syncing application state with Git repositories. ## When to Use - Setting up GitOps continuous deployment - Configuring ArgoCD applications and ApplicationSets - Enabling SSO authentication via Dex - Managing multi-cluster deployments - Troubleshooting ArgoCD sync issues - Configuring repository credentials ## KubeSphere GitOps Integration ### Two Ways to Create Applications **1. Direct ArgoCD Application (Admin Only)** - Created in `argocd` namespace - Requires access to ArgoCD namespace - Full control over ArgoCD configuration **2. KubeSphere GitOps Application (Tenant-Friendly)** - Created via `/kapis/gitops.kubesphere.io/v1alpha1/` - Application CR created in tenant namespace - KubeSphere automatically creates corresponding ArgoCD Application - Tenant doesn't need direct ArgoCD access ### Architecture ``` ┌─────────────────────────────────────────────────────────────┐ │ Tenant Namespace │ │ ┌──────────────────────────────────────────────┐ │ │ │ Application (gitops.k
- Overview
- When to Use
- KubeSphere GitOps Integration
- Two Ways to Create Applications
- Architecture
- Key Differences
- ArgoCD Components
- Installation & Verification
- Check ArgoCD Status
- Access ArgoCD UI
- Configuration
- Enable/Disable ArgoCD
- Custom ArgoCD Configuration
- Managing Applications
Verify ArgoCD namespace exists kubectl get ns argocd Check all ArgoCD pods kubectl get pods -n argocd Check ArgoCD services kubectl get svc -n argocd Get ArgoCD server service kubectl get svc devops-agent-argocd-server -n argocd Port-forward for local access kubectl port-forward svc/devops-agent-argocd-server -n argocd 8080:443
What does the kubesphere-devops-argocd skill do?
Use when configuring ArgoCD in KubeSphere DevOps, including GitOps deployments, application management, SSO setup, or troubleshooting ArgoCD issues
How do I install it?
Run `npx skills add kubesphere/kubesphere --skill kubesphere-devops-argocd --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kubesphere/kubesphere, a repository with 17,016 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.