Purpose

When kube-snapshot commits an image and attempts to push it to the registry, failures during the push step should be clearly detectable—not just in logs, but via an explicit condition or metric—so platform teams can reliably alert on push failures.

What’s missing

Currently, if the image push fails (e.g., due to registry auth issues or unreachable host), the task fails—but there's no dedicated signal reflecting that push failure. This makes integration with observability and alerting systems fragile.

Why it matters

• It’s critical for operational reliability to explicitly know when snapshot image push fails—not inferred from logs or generic status.
• We want to alert immediately on push failures to resolve issues like broken registry credentials, rate-limits, or network problems.
• An explicit signal (e.g., a condition or metric) allows automation to retry, teams to be notified, and dashboards to show failure rates.

Proposal (simple wording)

Please expose a clear, machine-readable indicator when the registry push fails. For example, a status field like PushFailed or a metric push_failure_total. This will allow easy alerting based on push outcomes.

Thank you for making kube-snapshot more observable and production-ready!