[lkozloff]

I love k9s and use it for most everything... but the unintended result is that I've lost my fluency in kubectl, which is occasionally a hinderance.

But maybe that's what you want from a tool - something so good it essentially replaces the previous way you were doing something?

[madduci]

I use OpenLens and this is exactly my sentiment. For someone who isn't fluent with kubectl, these tools are a wonderful way to approach the matter, but if you have learnt kubectl first, which is my case, then this brings you to "unlearn" it

[ytjohn]

Same here. I started with k8slens, but moved to k9s when k8slens started requiring the login. I didn't know about Openlens, which seems to be a fork of the open source portion of k8slens. But I've gotten pretty good at k9s now, so I'll probably stick with it.

In either case, both tools have made me less proficient with kubectl. Now I mostly use kubectl to apply yaml manifests. Editing a manifest in k9s is not as straightforward as I would like, and it's nicer to have a local copy of the file.