test/conformance: generate testdata for adding probe exec timeout tests

Signed-off-by: Andrew Sy Kim <kim.andrewsy@gmail.com>
This commit is contained in:
Andrew Sy Kim 2020-12-30 15:23:09 -05:00
parent af3e118b1f
commit 2242d0ffc4

View File

@ -335,6 +335,14 @@
restart count to 1.
release: v1.9
file: test/e2e/common/container_probe.go
- testname: Pod liveness probe, container exec timeout, restart
codename: '[k8s.io] Probing container should be restarted with an exec liveness
probe with timeout [NodeConformance] [Conformance]'
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.
release: v1.9
file: test/e2e/common/container_probe.go
- testname: Pod liveness probe, using http endpoint, multiple restarts (slow)
codename: '[k8s.io] Probing container should have monotonically increasing restart
count [NodeConformance] [Conformance]'
@ -347,6 +355,14 @@
everytime health check fails, measure upto 5 restart.
release: v1.9
file: test/e2e/common/container_probe.go
- testname: Pod readiness probe, container exec timeout, not ready
codename: '[k8s.io] Probing container should not be ready with an exec readiness
probe timeout [NodeConformance] [Conformance]'
description: A Pod is created with readiness probe with a Exec action on the Pod.
If the readiness probe call does not return within the timeout specified, readiness
probe MUST not be Ready.
release: v1.20
file: test/e2e/common/container_probe.go
- testname: Pod readiness probe, with initial delay
codename: '[k8s.io] Probing container with readiness probe should not be ready before
initial delay and never restart [NodeConformance] [Conformance]'