Boosting your kubectl productivity @ KubeCon 19 NA
Download as PPTX, PDF0 likes329 views
The document discusses various tips and tricks for improving productivity with the kubectl command line tool for managing Kubernetes clusters. It recommends setting aliases like k=kubectl and using tab completion, and provides commands for efficiently switching contexts and namespaces. Plugins are described as a way to extend kubectl functionality, and Krew is recommended as a plugin manager. Overall, the tips aim to help users work faster in Kubernetes by streamlining common kubectl tasks.
Boosting your kubectl productivity @ KubeCon 19 NA
- 1. Mauricio Salatino @Salaboy / @ZeebeHQ / @Learnk8s Boosting your `kubectl` productivity
- 2. Where am I?
- 4. bash or zsh? alias k = kubectl ~/.bashrc or ~/.zshrc
- 5. bash or zsh? Completion > source <(kubectl completion bash) > source <(kubectl completion zsh)
- 6. Switching Contexts/Namespaces Stored in: ~/.kube/config
- 7. Switching • kubectl config get-contexts: list all contexts • kubectl config use-context: change the current context
- 8. Switching Efficiently alias kcc='kubectl config use-context "$(klc | fzf -e | sed "s/^..//")"'
- 9. Doing it with style Kubectx & Kubens
- 11. A break for your TAB key kgpooyaml -> (k get pods -oyaml)
- 12. Plugins ● Your own extensions to kubectl ● kubectl-kcon: V1 announcement and release party! ○ https://github.com/salaboy/kubectl-kcon
- 13. A Plugin to Rule them All ● Krew (https://github.com/kubernetes-sigs/krew) ○ Package Manager for kubectl plugins ■ Krew is a plugin itself!!
- 14. Summing up ● k ● k get p<TAB> ● kgpooyaml (no poo) ● Plugins / kubectl-kcon ● krew Big kudos to Daniel Weibel ! https://learnk8s.io/blog/kubectl-productivity/
- 15. Summing up ● k ● k get p<TAB> ● kgpooyaml (no poo) ● Plugins / kubectl-kcon ● krew Big kudos to Daniel Weibel ! https://learnk8s.io/blog/kubectl-productivity/
Editor's Notes
- #2: My name is mauricio salatino @salaboy in twitter and github and I do work for a company called camunda, we do microservices orchestration with ZeebeHQ and I also collaborate with @learnk8s as a kubernertes instructor. LearnK8s provides kubernetes trainings. Big shout to Daniel who wrote a blog post about this subject which would take more than 5 mins to go over it.
- #3: A little bit of context first, when we talk about kubectl, we need to position ourselves on the client side. You will be interacting against an HTTP server which is exposing Restful endpoints which will expect different payloads to execute different commands. Kubectl will craft these HTTP commands based on the parameters that you type and then send it to the currently configured kubernetes master.
- #4: Before we start with the tips, I want to share this number with you.. It is a really really important number for me, it represents the number of hours that we can all save if we follow the tips presented in this session. If you take away something from this session is this number, so don’t forget it. This number is based on long hours of research and calculations and to understand more about how these number was calculated let’s start with the tips. If you want to save time and money to your employers then we can apply the first tip
- #5: With this simple trick you can multiply by 7 your productivity.. Instead of 7 characters you will just type 1. Be careful of not sharing this with your employer or your salary might go down. Notice that this can be automated to be the default in your shell if you add this command to your .bashrc or .zshrc file. You can follow the research link in the bottom for more information about how this technique saved 100 million dollars to a very big local company.
- #6: Next step is go crazy on your TAB key, be careful because this can damage your keyboard if you abuse of this tip. With completion we use a set of scripts to automatically give us options and speed up writing long commands, where sometimes we don’t actually know what we want to get. Example here.. K get p plus tab gives us all the available resources that start with p.
- #7: A little bit of more context. When working heavily with Kubernetes you will end up with multiple cluster and tons of namespaces. Knowing how to navigate between them is important Two main concepts: Context -> Which Kubernetes Master are you connected to. Namespaces -> Kubectl will filter all the resourced listed based on the current namespace.
- #8: Now if you want to switch between different contexts (different kubernetes clusters) you can use the following commands. And you can see in the screen here how many tabs do I need in order to craft this very long command. This is not efficient.. Even with auto completion it get tedious quite fast.
- #9: We can do this more efficiently by creating a more advanced alias, which use command line fuzzy finder, (a shell utility) in order to provide you the options and then selection using our arrows.
- #10: If you want to avoid creating your own aliases and not using tools that other people is using, you can use kubectx and kubens to switch with style. You can see here that you have some extra features such as going back to the previous one with dash, and also creating aliases to long names.
- #11: Going back to aliases.. Why creating our own if we can just get 800+ autogereated ones based on conventions? With this one.. We save time or we just go crazy. These aliases work based on taking pieces of information from the different parts of your command. Let’s see an example
- #12: So k g poo what? I am not getting any poo here.. You can see my head exploding while creating the GIF here.. But really I’ve seen people using this efficiently, and when you are issuing tons of complex commands this might be worth the brain investment.
- #13: Finally, plugins.. If you are already using these tips and you want to go an extra step forward you can write your own custom plugins to kubectl These are shell scripts that are going to be invoked on top of kubectl, you can add more complex rules or defaults in your own plugins.
- #14: Finally, why creating your own plugin if you can look the most popular plugins out there using Krew. Krew itself is a plugin, which is nice and interesting. And if you don’t find what you are looking for and you decide to write your own plugin, make sure that you publish it in Krew for other people to find it.
- #15: In summary we went through the journey of aliases, completion, getting poo.. Not poo.. Just 800+ generated aliases following conventions and we ended up with with plugins inception with Krew.
- #16: In summary we went through the journey of aliases, completion, getting poo.. Not poo.. Just 800+ generated aliases following conventions and we ended up with with plugins inception with Krew.