mirror of
https://github.com/k3s-io/kubernetes.git
synced 2026-07-17 20:00:07 +00:00
62d05adc8b
Despite being called checkReadiness, the function was only performing a liveness check: /healthz was polled over HTTPS without verifying the certificate or authenticating, and any HTTP response was accepted as a signal that the component was up. The only exception was kubelet, where a node readiness check was added on top. Switched to /readyz for kube-apiserver and kube-scheduler, kept /healthz for the rest and require HTTP 200 in all cases. This ensures that the kube-apiserver is fully initialized before dependent components are started.