Ordering Rollouts in Argo CD with Sync Waves and Selective Sync
Use Argo CD sync waves to order resource rollout inside one Application and selective sync to recover a single failed resource without re-applying everything.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use Argo CD sync waves to order resource rollout inside one Application and selective sync to recover a single failed resource without re-applying everything.
Use an Argo CD PreSync hook to run an idempotent database migration Job before your application manifests are applied, so new code never starts against an old schema.
Talos Linux replaces SSH with a secure, gRPC/HTTP API for node configuration. This guide explains how the API works, demonstrates a GitOps workflow, walks through practical verification steps, and highlights trade‑offs such as network exposure and certificate management.
ApplicationSets generate Argo CD Applications from one template plus a generator. Learn how the mechanism works, see a cluster-generator example, and avoid orphaned apps and broad selectors.
Deciding between Traefik's Docker and File providers depends on whether you prioritize auto-discovery or version-controlled governance. Learn how to implement a hybrid approach for maximum flexibility.
Learn how Portainer’s Git‑based Stacks let you version‑control Docker Compose files and automate redeploys on Docker hosts, with a concrete example, trade‑offs, and verification steps.
Use Argo CD ApplicationSet to generate many Applications from one template driven by Git data. Covers minimal design, trust boundaries, operational checks, failure modes and when to split the design.
Rancher 2.7+ ships a built‑in GitOps controller that syncs Helm charts from Git to Kubernetes. Learn how to enable it, deploy a chart in a single workflow, and understand the trade‑offs before you roll it out.
Talos Linux replaces SSH-and-pray node management with a single declarative YAML applied over an mTLS API. Here's how talosctl apply-config works, with a real GitOps example and the trade-offs.