kubecolor VS devtron

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?

Give it a try - https://github.com/devtron-labs/devtron

Devtron is entirely open-source with no freemium caveats. https://github.com/devtron-labs/devtron

look at Devtron. made in India with love

Hey man, I agree with the fact that it needs to run in a k8s cluster and is not a 100% k8s client. If you want to see Devtron as purely k8s client, please upvote the issue - https://github.com/devtron-labs/devtron/issues/2884

since my org has started using Devtron pipelines are smooth as silk. now a days pipeline should be the least of a worry for people. only thing that breaks is the code.