If a pod has the schedulerName value set to a non-existing scheduler, the pod will be created and stuck on "Pending" indefinitely with no additional information.

There will not be any event nor log in the entire cluster warning about this issue.

Expected result:

Having an event on the pod namespace that warns of the wrong schedulerName assigned to the pod each time the pod tries to be scheduled, and also logs in the kube-scheduler pod warning about the wrong schedulerName configured.

KCS explaining that : https://access.redhat.com/solutions/4652171