lens VS operator

Intentional. As you called out, they're moving to a more premium model. https://github.com/lensapp/lens/issues/6823

Improve Extension loading capabilities #6749

I think this thread is a little less flame-y: https://github.com/lensapp/lens/issues/6819

Hey, so I thought I remembered your username. This isn’t the first interaction we’ve had, or I’ve seen you have, that follows this similar pattern. In fact it’s the third example from you under this post!

It’s not a particularly pleasant experience to discuss anything with you, as after you make a particularly vapid and usually ice-cold take that is rebuffed, you seem to just try to make snarky replies rather than engage.

Understand that if you post your takes here they may be discussed and challenged, and if you don’t want this then I would refrain from initially commenting.

In response to your comment: They do. All Kubernetes resources are typed with JSON-schema definitions. Because of course they are, how else would kubernetes validate anything. https://kubernetesjsonschema.dev/

Anyone who’s used k8s at all knows this, if only from the error messages. From this you get autocompletion and a wide ecosystem of gui configuration tools. I like lens (https://k8slens.dev/).

Lens is no longer free but the upstream openlens is free see https://github.com/lensapp/lens

Surprised none of y'all mentioned Lens

The issue he’s complaining about has been fixed: https://github.com/lensapp/lens/issues/1588

There are many ways you can see if instances are underutilized, using some open source tools such as k9s cli or Lens (if measuring the utilization of VMs which are part of Kubernetes clusters). Or the cloud providers console to see the memory and compute consumption of the provisioned VMs.

With some experience and a user interface like Lens, debugging becomes easier. And there are great monitoring solutions for production use. But this is still a big hurdle for beginners taking their first steps with Kubernetes.

Try VictoriaMetrics operator for k8s, which would store data to VictoriaMetrics DBaaS at AWS.

For metrics there is VictoriaMetrics operator and helm chart, which can be used for monitoring Kubernetes. See this guide.

will fit both bare metals and k8s environment;

There is also https://github.com/VictoriaMetrics/operator

Just use Grafana Loki for logs and victoriametrics operator for metrics.

There is also victoriametrics operator - https://github.com/VictoriaMetrics/operator . It can simplify monitoring of Kubernetes clusters.

was designed to run on premise, but also can run in k8s via k8s operator.