kubecolor VS dotfiles

To anyone visiting here, I got a lot of feedback for new tools (which I haven't tried yet), both on Youtube and here, so I compiled it into a list: A comment on Lens: Initially I wanted to include Lens in the video but decided it's a bit different in that it's not a CLI / TUI. Many users shared bad experience with Lens, mainly around performance and a large amount of requests it shoots at the cluster API to a point where some companies banned it. These are the tools (I may add a video review on if anyone thinks it's worth it): * https://github.com/kubermatic/fubectl - for an improved kubectl experience * https://github.com/particledecay/kconf - for those with complex kubeconfig changes requirements * https://github.com/MuhammedKalkan/OpenLens - an open version of Lens (note the above before using) * https://github.com/hidetatz/kubecolor - colored kubectl output :) * https://github.com/astefanutti/kubebox - the K9s little brother? * https://github.com/bergerx/kubectl-status - human friendly resource status output

Hey all, I'm using this kubecolor.exe binary to colorize the output of kubectl. The way it works on other shells is that you simply create an alias for kubectl -> kubecolor. However, doing this in powershell breaks the autocomplete of first argument, second on-wards work totally fine.

How about https://github.com/dty1er/kubecolor?

My dotfiles are at - https://github.com/omerxx/dotfiles Specifically the terminal I'm currently using is Alacritty, but for the video I used iTerm (looks cleaner with transparency for the video). Regardless of terminal I always attach myself my Tmux session (also in the dotfiles). You're probably also wondering about the command line which is set with ohmyzssh + powerlevel (https://github.com/romkatv/powerlevel10k)