Time skew across city racks breaks certificate validation during kubeadm join. What infrastructure practice prevents that class of failure?
Select an answer to reveal the explanation.
Short Explanation
Certificates are sticklers for punctuality. If one rack thinks it is yesterday, join TLS looks expired or not-yet-valid. NTP—or solid time sync—keeps every node’s watch aligned with the control plane.
Full Explanation
TLS certificate validation depends on accurate system time. Skewed clocks cause kubeadm join and other mTLS steps to fail even when certificates are correctly issued. Operating NTP or another reliable time source across racks is a standard prerequisite. Skipping TLS verification or forging odd validity windows is not an acceptable admin practice.