kubecmd

Run commands easily on dedicated deployment's pods.

It creates a job based on your deployment, it runs the command on the job's pod, and deletes it after it's done.

But why?

You could run your commands directly on a deployment's pod but have in mind that it's the same pod that is currently running your app, probably processing lots of requests already, any deployment update can terminate the pod in the middle of your script's execution plus you have to figure out the pod's name.

kubecmd makes easier to run any command on your kubernetes apps creating a dedicated job to do it, it won't go away if something like a deployment update happens but until it's done with your command. The job gets destroyed after the command finishes.

Instalation

• You need kubectl of course.
• Install jq.

brew install jq

• Install kubecmd

curl -fsSL https://raw.githubusercontent.com/versus-systems/kubecmd/master/kubecmd > /usr/local/bin/kubecmd
chmod +x /usr/local/bin/kubecmd

Usage

Run any command as: kubecmd -d <deployment-name> -n <namespace> <command>

kubecmd -d my-rails-app rails console          # it opens a rails console on a pod based on my-rails-app deployment on the default namespace
kubecmd -d my-rails-app -n production rails c  # same as above but under the production namespace

If you just want to ssh into it, you can run /bin/sh or /bin/bash.

kubecmd -d my-app -n namespace /bin/sh
kubecmd -d my-app -n namespace /bin/bash

Tested on:

• GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin16)