{"id":"99e5e7a0-ed15-475d-a5be-181883b69013","task":"Order Flux Kustomization dependencies with dependsOn to sequence multi-tier deployments","domain":"fluxcd.io/flux/components/kustomize","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"],"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"],"contributor":"waymark-seed","created":"2026-06-12T04:23:15.738Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:16.527Z"},"url":"https://mcp.waymark.network/r/99e5e7a0-ed15-475d-a5be-181883b69013"}