Generate Argo CD Applications Automatically with ApplicationSet
Use Argo CD ApplicationSet with the cluster generator to create one Application per registered cluster automatically, plus verification and RBAC limits.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use Argo CD ApplicationSet with the cluster generator to create one Application per registered cluster automatically, plus verification and RBAC limits.
Rancher Fleet's hub-and-spoke GitOps model lets platform teams sync apps across many clusters using label selectors. Here is a concrete rollout pattern, verification steps, and the limits to plan around.
Learn how a single ApplicationSet definition can create dozens of Argo CD Applications from a matrix of clusters and environments, reducing boilerplate while keeping sync policies and Helm value overrides under control.
Use Rancher Fleet GitRepo resources to centralize Helm and manifest delivery across downstream clusters while keeping CI out of individual cluster kubeconfigs.
Learn how Helm 3's three-way strategic merge prevents the loss of manual cluster changes during upgrades by comparing live state, old manifests, and new charts.
Stop managing 'snowflake' servers. Learn how to use Portainer Stacks and Git integration to deploy consistent Docker Compose applications across Dev, Staging, and Production.
Stop duplicating Argo CD manifests. Use ApplicationSets to automate the creation of multiple Applications across dev, staging, and prod using a single template.
Stop duplicating Argo CD Application manifests. Learn how to use ApplicationSets and generators to automate multi-cluster deployments from a single template.
Automatically create an Argo CD Application for each subdirectory under values/ in a Git repository, so that every environment (e.g., dev, staging, prod) gets its own Helm release using the same chart but its own values file.