One missing name, a Kubernetes namespace full of restarts

Compare these two commands:

kubectl delete deployment -n prod # error: resource(s) were provided, but no name was specified

kubectl rollout restart deployment -n prod # deployment.apps/api restarted # deployment.apps/billing restarted # deployment.apps/checkout restarted # ...

Enter fullscreen mode

Exit fullscreen mode

The first refuses to run. The second attempts to restart every Deployment in the namespace, without confirmation or an explicit --all . It's documented behavior .

That makes this a surprisingly dangerous bit of shell:

kubectl rollout restart deployment $SERVICE -n prod

Enter fullscreen mode

Exit fullscreen mode

If SERVICE is empty, the command gets a much bigger audience than intended.

Each Deployment still follows its own update strategy. But with rolling updates, those rollouts can overlap across the namespace. Caches warm up, connections reconnect, and replacement pods compete for capacity together.…