kubecfg VS OpenLens

kubecfg does add some features, like https:// imports, oci:// imports (oci bundles in OCI registries, transitively bundling all imported files with jsonnet-deps).

But yes, I strive to keep the "one file, one target, import whatever you need but explicitly" as much as possible.

I'm pouring some more time into the project and trying to implement some ideas I had for a long time but never managed to get them out. For example "Flags From Files" (https://github.com/kubecfg/kubecfg/blob/flagspec/docs/rfcs/r...) or "Caching + optional vendoring of immutable external deps".

You shouldn't write those manifests by hand in any non-hobby project. https://github.com/kubecfg/kubecfg

Should kubecfg be used instead (having active development)?

We use kubecfg and it is what I would recommend to anyone looking to create a sustainable GitOps workflow at work.

To support visual feedback for the users who are using tools like Openlens, we can add a +kubebuilder:printcolumn annotation to the MyApp struct. To do so, add the following code to the MyApp struct:

There is also OpenLens (https://github.com/MuhammedKalkan/OpenLens). And for anyone switching from Lens, pod shell and logs functionality can be found as an extension.

`openlens` is now preferred over `Lens`, it has everything you need and none of the fluff that Lens wants to charge you for.

It's actually called OpenLens: https://github.com/lensapp/lens#readme but I don't think the official repo offers binary builds of it. Someone does here though: https://github.com/MuhammedKalkan/OpenLens

It's already at OpenLens readme file: https://github.com/MuhammedKalkan/OpenLens

You can use Lens which also offers a free license. I would also take a look at OpenLens. You stated that you were looking for something GUI-centric, but I would also take a look at k9s to help you dig deep into your cluster, quickly.

For managing clusters via Windows, check out WSL2 + k9s and OpenLens

Yep Rancher or K3s is a good start. As is OpenLens.