Track reconciliation attempts over time in .status.history
#1502
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With
.status.history
the kustomize-controller tracks the reconciliation attempts over time, providing insightsinto the Kustomization's behavior which can be used for audit, anomaly detection and debugging purposes.
The history is stored as a list of snapshots, ordered by last reconciliation time. Each snapshot contains:
digest
: A SHA256 digest of the Kubernetes manifests being applied on the clusterfirstReconciled
: The timestamp when this particular configuration was first reconciledlastReconciled
: The timestamp of the most recent reconciliation attempt for this configurationlastReconciledDuration
: How long the most recent reconciliation attempt tooklastReconciledStatus
: The status of the most recent reconciliation (e.g.,ReconciliationSucceeded
,HealthCheckFailed
,ReconciliationFailed
)totalReconciliations
: The total number of reconciliations for this configurationmetadata
: Additional information about the reconciliation, including the source revision and the source origin revision if availableThe kustomize-controller deduplicates entries based on the digest and status.
The history is automatically truncated to keep only the 5 most recent entries.
Example: