ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #argocd
Learn how to let a single Git repo drive application creation across multiple clusters with Argo CD’s ApplicationSet and Git Generator. Follow a step‑by‑step guide, see example manifests, and know how to verify and recover from common pitfalls.
Argo CD’s Sync Waves let you order resources in a GitOps deployment, ensuring that dependencies like ConfigMaps or CRDs are created before the objects that need them. Learn how to configure, test, and balance waves in this practical guide.
Guide to choosing between Automated and Manual sync policies in Argo CD. Compare trade-offs between self-healing and manual control to prevent configuration drift or accidental deletions.
Deciding between Automatic and Manual sync in Argo CD involves balancing deployment speed against stability. This guide compares the trade-offs of self-healing, pruning, and manual gates.
Maintaining Consistency Across Clusters In a microservices architecture, Argo CD is often used to deploy the same application stack to several Kubernetes clusters. The core challenge is ensuring that every cluster receives identical configuration while still allowing cluster‑specific overrides. Two Documented Approaches Plain GitOps manifests – raw YAML file
I am setting up Argo CD on a Kubernetes cluster and want to understand the end‑to‑end process: after installing the Argo CD manifests, how should I expose the API server, retrieve the initial admin password, log in via the CLI, register a target cluster (if needed), create an application from a Git repository, and finally sync it to deploy the workloads? Ple
An Argo CD application should transition to Synced after a successful sync, but it can stay OutOfSync when the manifest path or revision is incorrect, the destination cluster is unreachable, the argocd-manager service account lacks necessary RBAC permissions, or repository credentials are invalid. Diagnosing the issue requires inspecting sync logs and verify
Credential Lifecycle Management Argo CD implements least-privilege access by mapping external identity provider groups to internal roles via RBAC policies. For OIDC-based authentication, the API server validates the exp claim on every request, resulting in an HTTP 401 response once the token expires, which necessitates a client-side re-authentication flow. S
Managing alert volume in a large-scale Argo CD deployment requires balancing visibility with notification noise. The Argo CD Notifications controller allows for trigger definitions based on application status changes, but default configurations often emit redundant messages during the reconciliation process. The goal is to ensure that notifications are only
kubernetes
helm