respect ExecProbeTimeout
This commit is contained in:
@@ -246,6 +246,26 @@ var _ = SIGDescribe("Probing container", func() {
|
||||
runReadinessFailTest(f, pod, time.Minute)
|
||||
})
|
||||
|
||||
/*
|
||||
Release: v1.21
|
||||
Testname: Pod liveness probe, container exec timeout, restart
|
||||
Description: A Pod is created with liveness probe with a Exec action on the Pod. If the liveness probe call does not return within the timeout specified, liveness probe MUST restart the Pod. When ExecProbeTimeout feature gate is disabled and cluster is using dockershim, the timeout is ignored BUT a failing liveness probe MUST restart the Pod.
|
||||
*/
|
||||
ginkgo.It("should be restarted with a failing exec liveness probe that took longer than the timeout", func() {
|
||||
// The ExecProbeTimeout feature gate exists to allow backwards-compatibility with pre-1.20 cluster behaviors using dockershim, where livenessProbe timeouts were ignored
|
||||
// If ExecProbeTimeout feature gate is disabled on a dockershim cluster, timeout enforcement for exec livenessProbes is disabled, but a failing liveness probe MUST still trigger a restart
|
||||
// Note ExecProbeTimeout=false is not recommended for non-dockershim clusters (e.g., containerd), and this test will fail if run against such a configuration
|
||||
cmd := []string{"/bin/sh", "-c", "sleep 600"}
|
||||
livenessProbe := &v1.Probe{
|
||||
Handler: execHandler([]string{"/bin/sh", "-c", "sleep 10 & exit 1"}),
|
||||
InitialDelaySeconds: 15,
|
||||
TimeoutSeconds: 1,
|
||||
FailureThreshold: 1,
|
||||
}
|
||||
pod := busyBoxPodSpec(nil, livenessProbe, cmd)
|
||||
RunLivenessTest(f, pod, 1, defaultObservationTimeout)
|
||||
})
|
||||
|
||||
/*
|
||||
Release: v1.14
|
||||
Testname: Pod http liveness probe, redirected to a local address
|
||||
|
Reference in New Issue
Block a user