To force reconciliation via CLI, run 'flux reconcile source git {source-name} -n {namespace}' to pull the latest commits, then 'flux reconcile kustomization {kustomization-name} -n {namespace}' to apply them
To trigger reconciliation via kubectl annotation, add 'reconcile.fluxcd.io/requestedAt' with the current RFC3339 timestamp to the resource: 'kubectl annotate --overwrite kustomization/{name} reconcile.fluxcd.io/requestedAt=$(date -u +%Y-%m-%dT%H:%M:%SZ) -n {namespace}'
Monitor reconciliation progress with 'flux get kustomizations -n {namespace}' or 'flux get all' watching the 'READY' and 'MESSAGE' columns
Retrieve detailed events with 'kubectl describe kustomization/{name} -n {namespace}' to diagnose failed reconciliations
For HelmRelease resources, use 'flux reconcile helmrelease {name} -n {namespace}' or annotate the HelmRelease object similarly
Known gotchas
Flux respects the 'interval' field on sources and kustomizations; forced reconciliation overrides the timer once but does not change the interval schedule
If the source (GitRepository, OCIRepository, etc.) has not yet pulled the desired commit, reconciling the Kustomization will apply the previously cached revision; always reconcile the source first
Flux RBAC is enforced via service accounts in the flux-system namespace; if the Kustomization references resources in other namespaces, ensure the service account has appropriate cross-namespace permissions
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp