If you changed config referenced by a deployment (configmap/secret)
and you need a controlled restart, rollout restart is
often the cleanest option. It's explicit and leaves an audit trail.
kubectl -n <ns> rollout restart deploy/<name>
kubectl -n <ns> rollout status deploy/<name>If your goal is to "poke it and see", prefer checking health first. Restarting masks root causes. Use it when you already know why you need a new process image or fresh config load.