Details
-
Bug
-
Resolution: Unresolved
-
Normal
-
4.15, 4.16
Description
Description of problem:
There is no kubernetes service associated with the kube-scheduler, so it does not require a readiness probe.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
# In the control plane: kubectl get services | grep scheduler kubectl get deploy kube-scheduler | grep readiness
Actual results:
Probe exists, but no service
Expected results:
No probe or service
Additional info: