Kubernetes Liveness Readiness Probe Language Collocations
Practise the standard verbs for configuring Kubernetes liveness and readiness probes.
0 / 5 completed
1 / 5
Fill in: 'We ___ a readiness probe on every pod so the service only routes traffic once the app has actually finished starting up.'
We 'define a probe' — the standard, established Kubernetes collocation for declaring a health check on a container. The other options aren't the recognised term here.
2 / 5
Fill in: 'Using the same lightweight check for both liveness and readiness can ___ a pod stuck restarting instead of just being taken out of rotation.'
We say a conflated check will 'cause' an unnecessary restart loop — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a generous initial delay on the liveness probe so a slow-starting app isn't killed before it even gets a chance to boot.'
We 'set a delay' — the standard, simple collocation for configuring a probe's startup grace period. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ readiness probe failures in the event log so a pod repeatedly failing to become ready is easy to spot during a rollout.'
We 'track' failures — the standard collocation for monitoring a recurring event over time. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ a separate startup probe for slow-booting apps so the liveness probe doesn't begin checking before initialisation finishes.'
We 'add a probe' — the standard, simple collocation for introducing an additional health check type. The other options are less idiomatic here.