How to Restart All Pods in a Kubernetes Namespace

Where I work we use a repo-per-namespace setup and so it is often the case that I want to restart all the pods and deployments in a single Kubernetes namespace. Maybe I want to see the startup logs, maybe I want to take down production for a few seconds, don’t question my motivations. Anyhow, what does matter is that bouncing all the deployments one-by-one is really obnoxious and I don’t like typing.

Before we move on, if you’re interested in learning Go in a hands-on format, check out the Go Mastery course I just released. With that shameless plug out of the way, let’s get back to Kubernetes.

The best way to bounce (kubectl >= 1.15)

I recently found out from a friend there is an easier way as of kubectl 1.15+. Restarting all the pods in a namespace is as easy as running the following kubectl command.

kubectl -n {NAMESPACE} rollout restart deploy

The old way (kubectl <= 1.14)

In older versions of kubectl you needed to run a command for each deployment in the namespace. In true lazy-developer-fashion I wrote a little script that will do it for me:

deploys=`kubectl -n $1 get deployments | tail -n +2 | cut -d ' ' -f 1`
for deploy in $deploys; do
  kubectl -n $1 rollout restart deployments/$deploy
done

It’s fairly simple to use. Assuming I named the script kubebounce.sh:

./kubebounce.sh {NAMESPACE}

I made a little open-source repo with installation instructions if you want to add it to your $PATH. Be sure to star the repo if you find it useful.

How It Works

Bash isn’t exactly the easiest language to read. Let’s go over each portion of the script.

deploys=`kubectl -n $1 get deployments | tail -n +2 | cut -d ' ' -f 1`

In bash, $1 refers to the first command-line argument, the namespace in our case. In essence, this line gets all the deployments in the target namespaces and saves them into a deploys variable. We pipe the output of the kubectl get deployments command into a tail -n +2 command, which just strips of the first line of the output. Then we run that output through a cut command which leaves us with a nice list of all the deployment names.

That’s actually the trickier part, next we just loop over all the deployments and restart them one-by-one:

for deploy in $deploys; do
  kubectl -n $1 rollout restart deployments/$deploy
done

Thanks for reading, now take a course!

Interested in a high-paying job in tech? Land interviews and pass them with flying colors after taking my hands-on coding courses.

Questions?

Follow and hit me up on Twitter @q_vault if you have any questions or comments. If I’ve made a mistake in the article be sure to let me know so I can get it corrected!

Subscribe to my newsletter for more coding articles delivered straight to your inbox.