1. Proposed title of this feature request

Cover initContainers waiting reasons with alerts

2. What is the nature and description of the request?

Current KubePodCrashLooping and KubeContainerWaiting alerting consumes kube_pod_container_status_waiting_reason which is based on containerStatuses. But we have no alerting today that consumes kube_pod_init_container_status_waiting_reason to cover initContainerStatuses. This RFE proposes we grow alert coverage there, whether that's expanding the expr in the existing alerts, or adding new alerts like KubeInitContainerWaiting.

3. Why does the customer need this? (List the business requirements here)

Currently there is no alert signal when a pod struggles with init containers, e.g. with the SignatureValidationFailed reason because it violates a ClusterImagePolicy. That can leave admins unaware that core cluster functionality is blocked because of signature validation issues.

4. List any affected packages or components.

Monitoring. Upstream alerts are here, but they don't cover initContainerStatuses yet either.