5 Tips to Be More Productive with Kubernetes
Published on

5 Tips to Be More Productive with Kubernetes

Written by Peter Jausovec
I like to read about and see how people set up their environments and any tools, tips, and tricks they use to be more productive when working with Kubernetes and Istio. What follows is a collection of 5 tips and tools that I use daily, and I think it makes me more productive with Kubernetes and Istio.

1. Switching between Kubernetes contexts

If you're working with a local Kubernetes instance and one or more cloud instances of Kubernetes, you will at some point need to switch between contexts. Kubernetes CLI (kubectl) has commands available that allow you to work with different contexts:
  • current-context
  • get-contexts
  • rename-context
  • delete-context
  • set-context – use-context
Assuming you know the name of the Kubernetes context you want to switch to, you can use the following command:
kubectl use-context [CONTEXT-NAME]
In case you are working with multiple clusters and you don't know the context names, you would need to list the contexts first, and then run the use-context command like this:
$ kubectl get-contexts
*         docker-desktop  docker-desktop  docker-desktop
          minikube        minikube        minikube
          cloudc          crdambvg43d     user-crdambvg43d

$ kubectl use-context minikube
Luckily, there's an easier way to do this. I am using a tool called kubectx that allows you to list and switch to different Kubernetes context quickly. To list the context, you can run kubectx like this:
$ kubectx
Switching to another context is as simple as this:
$ kubectx [CONTEXT-NAME]

2. Switching between Kubernetes namespaces

Another quite common thing you do when working with Kubernetes is to work with resources from multiple namespaces. For example, you might want to list pods in one namespace, check on services in another etc. My workflow here is to use the --namespace flag that is supported on the Kubernetes CLI. For example, to get all pods in the namespace called test , you can run kubectl get pods -n test. By default, if you don't provide the namespace flag, the default Kubernetes namespace is used  -  which is appropriately named default.
This default value can be changed in the kubeconfig file  -  you could, for example, set the default namespace to be test or kube-system or any other namespace. That way you don't need to use --namespace flag when querying for resources. However, the command to change this is awkward:
$ kubectl config set contexts.my-context.namespace my-namespace
The command above modifies namespace field in the my-context context and changes it to my-namespace. This means if you switch to my-context and run kubectl get pods for example, you would only see pods from the my-namespace namespace.
Together with the kubectx tool, you also get a tool called kubens -  it helps you list and switch to different namespaces.
$ kubens
Setting a default namespace for selected context is also quick and easy:
$ kubens default
Context "docker-desktop" modified.
Active namespace is "default".

3. Alias the Kubernetes CLI 

This is a straightforward tip. If you are working with Kubernetes you will be typing kubectl a lot, and you will get tired of typing the whole name at some point. You might be thinking it's only seven characters, but it adds up.
The tip here is to alias kubectl to something shorter, k for example:
$ alias k=kubectl
$ k get po
mypod   1/1     Running   18         43h
Ideally, you would put the alias k=kubectl in your bash_profile, so it gets set each time you open your terminal.

4. Get a terminal inside the Kubernetes cluster

When accessing services and pods running inside the cluster, you either need to expose them, so they are accessible from the public internet or you run a kube proxy or forward ports between your local machine and services running inside the cluster.
However, sometimes you want to run plain curl command without exposing any services or forwarding ports. To do so, I use a function that gets loaded as part of my bash profile that runs a pod with radial/busyboxplus:curl image inside the cluster and gives me access to the terminal. That way, I can run curl against services and IPs inside the cluster. I call the function kbash and use it like this:
$ kbash
If you don't see a command prompt, try pressing enter.
[ root@curl:/ ]$
From the prompt, I can run curl against internal Kubernetes DNS names or IP addresses. To exit, just type exit and if you want to attach back to the pod, run kbash and it will attach to the existing pod. I have this function defined as part of my dotfiles as well.

5. Quickly open Grafana/Jaeger/Kiali (or anything else)

If you plan on working with Istio service mesh you will probably use Grafana/Jaeger/Kiali at some point. With older versions of kubectl, accessing these services required you to get the pod name first and then set up a port forward to that pod and finally open the browser to the forwarded address. With the latest kubectl versions you can port forward to the service itself and you don't need to figure out what the pod name is anymore. Regardless, the commands are quite long to type out each time:
$ kubectl --namespace istio-system port-forward svc/grafana 3000:3000
$ open http://localhost:3000
The easier and faster way is to create functions or aliases for each of the services. For example, I have the following set up for Grafana/Jaeger/Kiali in one of the files that get loaded as part of my bash profile:
alias grafana="kubectl --namespace istio-system port-forward svc/grafana 3000:3000 & open http://localhost:3000"
alias jaeger="kubectl --namespace istio-system port-forward svc/jaeger 16686:16686 & open http://localhost:16686"
alias kiali="kubectl --namespace istio-system port-forward svc/kiali 20001:20001 & open http://localhost:20001"
Now if I want to open Jaeger, I can run jaeger and it will set up the port-forward and open the browser.
If you have other services running inside the cluster you are frequently opening, you can set up the aliases the same way.
Join the discussion
Peter Jausovec

Peter Jausovec

Peter Jausovec is a platform advocate at Solo.io. He has more than 15 years of experience in the field of software development and tech, in various roles such as QA (test), software engineering and leading tech teams. He's been working in the cloud-native space, focusing on Kubernetes and service meshes, and delivering talks and workshops around the world. He authored and co-authored a couple of books, latest being Cloud Native: Using Containers, Functions, and Data to Build Next-Generation Applications.

Related posts