Kubernetes StatefulSet Scaling Language Collocations
Practise the standard verbs for scaling Kubernetes StatefulSets safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ a StatefulSet up one ordinal at a time so a newly joining replica always finds its predecessor already ready before it starts up itself.'
We 'scale a StatefulSet' — the standard, established Kubernetes collocation for changing the replica count of an ordered workload. The other options aren't the recognised term here.
2 / 5
Fill in: 'Scaling a StatefulSet down without draining connections first can ___ in-flight requests to the terminating replica simply dropped mid-response.'
We say an abrupt scale-down will 'leave' requests dropped — the standard, natural collocation for the resulting failure. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the pod management policy to Parallel only for stateless-enough workloads, since ordered startup matters precisely for the workloads StatefulSets exist to serve.'
We 'set a policy' — the standard, simple collocation for configuring how replicas of a StatefulSet start and terminate. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ each replica's persistent volume claim survives a scale-down and reattaches correctly on scale-up, rather than assuming storage just follows the ordinal automatically.'
We 'verify' behaviour — the standard, simple collocation for confirming storage persists correctly across a scaling event. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a scale-down in staging against a simulated quorum loss before trusting it against a production database cluster's real replica count.'
We 'test' a scale-down — the standard, simple collocation for validating a risky operation before running it against production. The other options are less idiomatic here.