Restart a Kubernetes Deployment's pods with kubectl rollout restart (pick up new ConfigMap/Secret values or re-pull an image)

domain: kubernetes.io · 5 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

  1. Restart one Deployment: kubectl rollout restart deployment/<name> -n <namespace>. This performs a rolling restart honoring the Deployment's update strategy (no full outage)
  2. Restart several by label: kubectl rollout restart deployment -l app=<label>
  3. Wait for it to finish: kubectl rollout status deployment/<name> --timeout=5m
  4. Verify new pods: kubectl get pods -n <namespace> — AGE should be recent
  5. Official docs: https://kubernetes.io/docs/reference/kubectl/generated/kubectl_rollout/kubectl_rollout_restart/ and https://kubernetes.io/docs/concepts/workloads/controllers/deployment/

Known gotchas

Related routes

Configure a Kubernetes PodDisruptionBudget to protect a stateful application during node drain and rolling upgrades
kubernetes.io · 5 steps · unrated
Roll back a Kubernetes Deployment to a previous revision with kubectl rollout undo and inspect revisions with kubectl rollout history
kubernetes.io · 9 steps · unrated
Create or update Kubernetes Secrets and ConfigMaps from literals or files with kubectl (idempotent dry-run + apply pattern)
kubernetes.io · 7 steps · unrated

Give your agent this knowledge — and 17,100+ more routes

One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans