lens VS operator

Okteto: A Tool for Cloud Native Developers - Build better applications by developing and testing your code directly in Kubernetes Tilt: Tilt manages local development instances for teams that deploy to Kubernetes - Local Kubernetes development with no stress Garden: Kubernetes from source to finish - Development orchestrator for Kubernetes, containers and functions. KuberNix - Single dependency Kubernetes clusters for local testing, experimenting and development Copper - A configuration file validator for Kubernetes ko - Build and deploy Go applications on Kubernetes Dekorate - Java annotation processors for Kubernetes Lens IDE The Kubernetes IDE Kosko - Organize Kubernetes manifests in JavaScript Telepresence - Fast, local development for Kubernetes and Openshift microservices Monokle - Desktop UI for managing Kubernetes manifests Kr8s - Desktop application made for developers that need to monitor and visualize their Kubernetes clusters in a user friendly GUI

Lens is great and runs outside the cluster, https://github.com/lensapp/lens

You can also run helm or kubectl from the jumpbox, which will allow you to interact with kubernetes API and deploy applications to it. I would also suggest using something like https://k8slens.dev/ to start getting familiar with what's inside a cluster. You can see logs and even exec into pods/nodes. However, try using kubectl whenever possible so you aren't depending on tooling.

I definitely understand the sentiment of wanting a GUI for people at a Windows shop. I had a similar experience to what you're describing at my last company. We had a lot of success with AKS and we ran Rancher as a dashboard for developers and SREs to access the cluster with Azure AD SSO. If you're looking for just a quick client GUI, check out lens https://k8slens.dev/

Lens maybe?

I've been hitting this too, it's rather random and annoying. There's an open bug report for it though, and looks like they might be getting to the bottom of it.

If you are looking for just an alternative to kubectl, you could look at https://k8slens.dev/

https://k8slens.dev/ solves this exact issue via a feature called Spaces... Long story short, Cluster admin can give specific access to a Kubernetes cluster without sharing the KubeConfig file... You can create specific teams for your "Space" and give different access to each team via role bindings etc... It's pretty neat. Here's a blog that explains this in depth and how to do it... https://medium.com/k8slens/how-to-give-developers-secure-access-to-kubernetes-clusters-c6025f0dd288

Navigate to the Lens website (https://k8slens.dev/) and download the latest version of Lens for your preferred OS. Once you have downloaded and installed, open the application, Lens IDE will automatically add your Kubeconfig (if done correctly, you will see a cluster icon on the left-hand-side). Lens works with any certified CNCF Kubernetes distro.

If you are new to Kuberenetes, check out lens IDE to check all the K8 components without knowing Kubectl.

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.