tazuna state diff
Compares the Build result of each Manager with the State stored in the cluster and outputs per-resource differences. Does not modify the cluster.
tazuna state diff [-f tazuna.yaml]
Behavior
- Load
tazuna.yaml. - For each Manifest, call the Manager’s Build to construct “the resources that should currently be generated from
tazuna.yaml.” - Reconcile with the in-cluster State and classify each resource into one of the following.
| Diff type | Meaning |
|---|---|
added | Present in the Build result, absent from State |
modified | Present in both, but with different content hashes |
removed | Present in State, absent from the Build result |
always-sync | Classification that skips diff computation and is always synchronized. Secrets derived from type: genesissecret go here |
Does not evaluate context_matches. Only read access to the cluster is performed; nothing is modified.
Difference from state drift
Both state diff and state drift show a “diff,” but they compare different things.
| Aspect | state diff | state drift |
|---|---|---|
| Compared against | Build result vs State | State vs live cluster |
| Changes detected | Changes on the tazuna.yaml side | Manual kubectl apply / manual deletion |
| Output categories | added / modified / removed / always-sync | live-drifted / live-missing |
By switching the command you use depending on whether the drift is “an update on the tazuna.yaml side not yet applied” or “the cluster side touched directly,” you can build low-noise monitoring.
Flag
No specific flags besides the global flags.
Examples
tazuna state diff
tazuna state diff -f tazuna.yaml
Related
- To apply, see
tazuna apply --sync - For detecting diffs against the live cluster, see
tazuna state drift - For the full rendering result, see
tazuna build - Terminology: Diff type / ContentHash