Deployment shell commands

Quick reference

CONTEXT

$kubectl config current-context
$kubectl config get-contexts
$kubectl config use-context prod-eu
$kubectl get ns api -o name
$kubectl cluster-info

ROLLOUT

$kubectl rollout status deploy/api
$kubectl rollout history deploy/api
$kubectl rollout restart deploy/api
$kubectl set image deploy/api api=api:v2
$kubectl get pods -n api -w

LOGS

$kubectl logs -f deploy/api -n api
$kubectl logs --tail=100 deploy/api
$kubectl logs -p deploy/api -n api
$kubectl describe pod -n api -l app=api
$kubectl get events -n api

ROLLBACK

$kubectl rollout undo deploy/api
$kubectl rollout undo deploy/api -n api
$kubectl rollout status deploy/api -n api
$kubectl get rs -n api
$kubectl get pods -n api

Explained

Context

kubectl config current-context prints the name the rest of your commands will use. get-contexts lists what is available; use-context switches. get ns proves the namespace exists before you apply into it.

Rollout

kubectl rollout status blocks until the Deployment is done, and it is the line that should end a pipeline. rollout history lists revisions, restart cycles the pods without a manifest change, set image updates one container, and get pods -w watches the replacements arrive.

Logs

kubectl logs -f follows one Deployment; --tail=100 gives the last hundred lines without the scroll; -p reads the previous container after a crash. describe pod shows events and exit codes, and get events shows the cluster's own story.

Rollback

kubectl rollout undo returns to the previous revision; add --to-revision N when you know the target. rollout status confirms the undo landed, get rs shows the old ReplicaSets still available, and get pods proves what is running.

In one line

Check the context

$kubectl config current-context