This request follows up on a previously closed issue where it was clarified that the current behavior is expected:
As mentioned there, kubechecks only generates diffs for existing, long-lived resources, and ArgoCD hooks do not appear in diff previews.
Problem / Limitation
In our setup, PreSync hooks are used for critical deployment logic, including:
- Backend database migration jobs
- Frontend asset build jobs
ExternalSecret resources to fetch secrets before application sync
Any change in these resources can have a direct production impact. However, since diffs for hook resources are not shown, these changes are currently invisible during reviews.
Feature Request
Please consider adding an optional configuration to include diffs for hook resources (at least PreSync) based on their manifests, even if they are not continuously running resources.
This would significantly improve the visibility.
This request follows up on a previously closed issue where it was clarified that the current behavior is expected:
As mentioned there, kubechecks only generates diffs for existing, long-lived resources, and ArgoCD hooks do not appear in diff previews.
Problem / Limitation
In our setup,
PreSynchooks are used for critical deployment logic, including:ExternalSecretresources to fetch secrets before application syncAny change in these resources can have a direct production impact. However, since diffs for hook resources are not shown, these changes are currently invisible during reviews.
Feature Request
Please consider adding an optional configuration to include diffs for hook resources (at least
PreSync) based on their manifests, even if they are not continuously running resources.This would significantly improve the visibility.