10 Kubernetes Aliases for the 1% DevOps Engineer

Stop fighting with verbose commands. Here is my personal .bashrc toolkit.

We all know kubectl is powerful, but it is also incredibly verbose.

How many times a day do you type -n my-namespace?

How many times do you copy a base64 secret string, open a new tab, and decode it?

These micro-frictions add up.

Today, I’m sharing my personal list of 10 aliases that combine kubectl with fzf (fuzzy finder) to turn manual typing into instant, interactive workflows.

Prerequisites

To use these, you need two standard tools installed on your machine:

1. fzf: The command-line fuzzy finder (essential for the interactive selection).

2. jq: For processing JSON output.

   ---

1. Instant Secret Decoder

Problem: Manually copying base64 strings and running base64 -d is slow and error-prone.

Solution: This alias pipes the selected secret directly into jq for instant decoding of all keys at once.

alias ksec='kubectl get secrets | fzf | awk "{print \$1}" | xargs -I {} kubectl get secret {} -o json | jq ".data | map_values(@base64d)"'

2. The Context Jumper

Problem: kubectl config use-context requires typing long, complex context names (e.g., gke_project_zone_cluster).

Solution: Fuzzy search your list of contexts. Essential when juggling Prod, Staging, and Dev clusters daily.

alias kctx='kubectl config get-contexts -o name | fzf | xargs kubectl config use-context'

3. The “Namespace Teleport”

Problem: Typing -n <namespace> on every command is a productivity killer.

Solution: Instantly switch your active namespace. Unlike external tools like kubens, this relies purely on native kubectl commands piped to fzf.

alias kns='kubectl get ns -o name | fzf | cut -d/ -f2 | xargs kubectl config set-context --current --namespace'

4. The “Pod Shell” (Exec made easy)

Problem: Getting a shell requires: get pods, copy name, exec -it <name> -- /bin/bash.

Solution: One command to select and enter. Note: If you use Alpine images often, change /bin/bash to /bin/sh.

alias ksh='kubectl get pods | fzf | awk "{print \$1}" | xargs -I {} kubectl exec -it {} -- /bin/bash'

5. The “Garbage Collector”

Problem: Failed jobs and evicted pods clutter your get pods output, making it hard to see actual issues.

Solution: A surgical strike that only targets Evicted or Error states across all namespaces.

alias kclean='kubectl get pods --all-namespaces | grep -E "(Evicted|Error)" | awk "{print \"-n \" \$1 \" \" \$2}" | xargs -t -L 1 kubectl delete pod'

6. The “Log Tailer” (Current NS)

Problem: Debugging a specific microservice in a busy namespace requires precise pod name matching.

Solution: Interactively pick the pod. The -f flag keeps the connection open so you can watch logs stream in real-time.

alias klogs='kubectl get pods | fzf | awk "{print \$1}" | xargs kubectl logs -f'

7. The “Deployment Bouncer”

Problem: You updated a ConfigMap or Secret, but the pods haven’t picked it up. Or you need to pull the :latest image tag.

Solution: Triggers a rolling restart of the deployment without needing to edit the YAML or scale down/up manually.

alias kbounce='kubectl get deployments | fzf | awk "{print \$1}" | xargs kubectl rollout restart deployment'

8. The “Resource Hog Hunter”

Problem: Cluster performance is degrading, but you don’t know who the culprit is.

Solution: Immediately sorts pods by CPU usage. Great for quick triage before diving into Prometheus/Grafana.

alias ktop='kubectl top pods --sort-by=cpu | sort -r | head -15'

9. The “Inventory Manager”

Problem: Security asks, “What versions of Nginx are we running?”

Solution: Scans the current namespace and outputs a deduplicated, sorted list of every container image version currently running.

alias kimg='kubectl get pods -o jsonpath="{.items[*].spec.containers[*].image}" | tr -s "[[:space:]]" "\n" | sort | uniq'

10. The “Stuck Pod Killer”

Problem: A pod is stuck in Terminating because of a hung volume mount or finalizer issue.

Solution: The nuclear option. It forces deletion immediately. Warning: Use carefully on StatefulSets or database pods to avoid data corruption.

alias kforce='kubectl get pods | fzf | awk "{print \$1}" | xargs -I {} kubectl delete pod {} --grace-period=0 --force'

---

How to use this?

1. Copy these aliases.

2. Paste them into your ~/.zshrc or ~/.bashrc file.

3. Run source ~/.zshrc (or bashrc) to load them.

Which one of these will save you the most time? Let me know in the comments!

P.S. You can get my “IaC & CI/CD from Day Zero” Checklist PDF for free by referring one friend to DecodeOps.

Next Week: 5 Terraform hacks to reduce plan time by caching modules.