You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Update the default PeerTimeout value to a higher, safer value (e.g., 7 seconds).
- added a validating admission webhook that issues a warning if the configured PeerTimeout is less than APIServerTimeout + MinimumBuffer (e.g., 2 seconds).
- if the configured PeerTimeout is less than APIServerTimeout + MinimumBuffer, the operator will internally use APIServerTimeout + MinimumBuffer for the peer check.
- added Unit tests
Signed-off-by: Michael Shitrit <[email protected]>
c.config.Log.Info("PeerRequestTimeout is too low, using adjusted value for safety",
295
+
"configuredTimeout", c.config.PeerRequestTimeout,
296
+
"apiServerTimeout", c.config.ApiServerTimeout,
297
+
"minimumBuffer", v1alpha1.MinimumBuffer,
298
+
"effectiveTimeout", minimumSafeTimeout)
299
+
events.WarningEventf(c.config.Recorder, &v1alpha1.SelfNodeRemediationConfig{ObjectMeta: metav1.ObjectMeta{Name: v1alpha1.ConfigCRName}}, eventReasonPeerTimeoutAdjusted, "PeerRequestTimeout (%s) was too low compared to ApiServerTimeout (%s), using safe value (%s) instead", c.config.PeerRequestTimeout, c.config.ApiServerTimeout, minimumSafeTimeout)
300
+
returnminimumSafeTimeout
301
+
}
302
+
303
+
returnc.config.PeerRequestTimeout
304
+
}
305
+
278
306
// getHealthStatusFromPeer issues a GET request to the specified IP and returns the result from the peer into the given channel
0 commit comments