lens VS k9s

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.

The most important thing for me about Kubernetes is that it makes things fun again. (YMMV) The Kubernetes Slack is super friendly and helpful! (also YMMV ;) )

The article is factually accurate and the mental model is consistent with other K8s docs, but I'm not sure I've seen it put so concisely from an outside perspective before.

The ¹ footnote should have been in-line, because "front-loading" complexity is a great explanation: distributed systems are hard, and require a whole bunch of decisions. It's intimidating to be faced will all of those decisions up front, but at least they're all visible, and it forces you to be very clear on what you want, or you get nothing. I'd rather be surprised and confused (which is to say, have to think) now rather than in 6 months when I realize I had not accounted for some something.

Finally ... I would be lost without k9s: https://k9scli.io/

2) I don't see startup logs for the CloudSQL Proxy. Are you sure it's actually starting? Consider using k9s to live debug your cluster, or use the GCP console to see if the container actually started.

Bootkube - bootkube - Launch a self-hosted Kubernetes cluster kubectx + kubens - Switch faster between clusters and namespaces in kubectl kube-shell - Kubernetes shell: An integrated shell for working with the Kubernetes kuttle: kubectl wrapper for sshuttle without SSH - Kubernetes wrapper for sshuttle kubectl sudo - Run kubernetes commands with the security privileges of another user K9s - Kubernetes CLI To Manage Your Clusters In Style! Ktunnel - A cli that exposes your local resources to kubernetes KubeOperator - Run kubectl command in Web Browser. https://kubeoperator.io/ Vimkubectl - Manage any Kubernetes resource from Vim https://www.vim.org/scripts/script.ph KubeHelper - KubeHelper - simplifies many daily Kubernetes cluster tasks through a web interface.

Fair enough. I would recommend Kubernetes up and Running book, was following it at the beginning and it was quite helpful. Kubectl is not super complex, mostly just a bit annoying and takes a bit of time to get used to. There is also a middle ground that quite handy and uses no resources of your cluster - k9s.

(i didn't test it, i use k9s to do that for me).

So k9s (not dogs)