Order Flux Kustomization dependencies with dependsOn to sequence multi-tier deployments
domain: fluxcd.io/flux/components/kustomize · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Author separate Kustomization resources for each tier (e.g., `infrastructure`, `cert-manager`, `applications`)
Add `spec.dependsOn` to each Kustomization that lists prerequisite Kustomization names; Flux waits for dependsOn targets to report Ready before applying the dependent
Set appropriate `spec.healthChecks` on prerequisite Kustomizations so Flux can verify readiness (e.g., wait for a Deployment to reach its desired replica count)
Commit all Kustomization manifests to Git; Flux picks them up on the next source reconciliation cycle
Inspect dependency resolution with `flux get kustomizations` — a stuck dependent will show a waiting message referencing its unready prerequisite
Use `flux reconcile kustomization <name> --with-source` to force re-evaluation when debugging ordering issues
Known gotchas
dependsOn only checks the Ready condition of the referenced Kustomization, not individual resource health unless healthChecks are configured — omitting healthChecks can cause false-ready signals
Circular dependencies cause both Kustomizations to hang indefinitely; Flux does not detect or report cycles explicitly, so review your dependency graph before committing
Cross-namespace dependsOn requires specifying `namespace` in the dependency entry; omitting it assumes the same namespace as the dependent Kustomization
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?