Kubernetes Admission Webhook Language Collocations
Practise the standard verbs for configuring Kubernetes admission webhooks safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ a validating admission webhook for every namespace so a manifest missing required labels is rejected at the API server, not caught later in an audit.'
We 'register a webhook' — the standard, established Kubernetes collocation for wiring an admission controller into the API server. The other options aren't the recognised term here.
2 / 5
Fill in: 'Deploying an admission webhook without a failurePolicy of Fail can ___ a malformed resource silently admitted whenever the webhook itself happens to be down.'
We say a missing failure policy will 'leave' bad resources admitted — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every admission webhook against a wide range of sample manifests in CI, so a bug in the validation logic doesn't start blocking every legitimate deployment.'
We 'test' a webhook — the standard, simple collocation for validating its behaviour before it gates real cluster traffic. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ a strict timeout on the webhook call itself, so a slow or hung admission service doesn't block every single resource creation across the cluster.'
We 'set a timeout' — the standard, simple collocation for bounding how long the API server waits on an external call. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a misbehaving webhook immediately during an incident, rather than letting it keep blocking every deployment while we debug it live.'
We 'disable a webhook' — the standard, established collocation for quickly removing a faulty gate from the admission chain. The other options aren't the recognised term here.