Current Behavior
When Wave detects that a pod’s referenced resources (e.g. a ConfigMap or Secret) are missing or incomplete, it disables scheduling for the pod. The pod remains in Pending. However, there is no Kubernetes Event (or other visible feedback attached to the pod) indicating why scheduling was blocked. This makes it difficult to diagnose why a pod stays pending.
Requested Enhancement
When Wave prevents scheduling of a pod due to missing or invalid referenced resources, it should create a Kubernetes Event attached to the affected pod. The Event should include details on what resource is missing or invalid (for example: “ConfigMap ‘foo’ not found”, “Secret ‘bar’ invalid/missing”, etc.).
Current Behavior
When Wave detects that a pod’s referenced resources (e.g. a ConfigMap or Secret) are missing or incomplete, it disables scheduling for the pod. The pod remains in
Pending. However, there is no Kubernetes Event (or other visible feedback attached to the pod) indicating why scheduling was blocked. This makes it difficult to diagnose why a pod stays pending.Requested Enhancement
When Wave prevents scheduling of a pod due to missing or invalid referenced resources, it should create a Kubernetes Event attached to the affected pod. The Event should include details on what resource is missing or invalid (for example: “ConfigMap ‘foo’ not found”, “Secret ‘bar’ invalid/missing”, etc.).