kubesphere-devops-argocdlisted

# 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.kubesphere.io/v1alpha1) │ │ │ │ - Created by tenant via KubeSphere API │ │ │ │ - Label: gitops.kubesphere.io/argocd-location: argocd │ │ │ └──────────────────┬───────────────────────────┘ │ └──