design-proposals-archive VS k9s

The destination is a pod IP address, and since Kubernetes guarantees that any pod can talk to any other pod in the cluster, the traffic can flow to the brown pod.

I wonder who will raise the glove and take that approach to use to post Metrics API resources instead of metrics-server.

Relatedly, the design proposals archive: https://github.com/kubernetes/design-proposals-archive/

[0] https://github.com/kubernetes/design-proposals-archive/blob/main/architecture/declarative-application-management.md

I will point out that the shortcomings of parameterized templates are actually very well-understood by the Kubernetes community: see Declarative application management in Kubernetes and The Rationale behind kpt. Helm has significant mindshare because it was first to the scene / has network effects, it solves real problems, and presents a decent UX for chart users. It sits in this obnoxious local optimum of "good enough on Day 1, hot garbage nightmare on Day 100".

Pierre: The first tool I recommend is K9s. It's not just a time-saver but a productivity booster. With its intuitive interface, you can speed up all the usual kubectl commands, access logs, edit resources and configurations, and more. It's like having a personal assistant for your cluster management tasks.

The last thing you really need is a common set of tools that you want fingertip access to. I really commonly use LazyGit and K9s in my day job so those are the tools I will show off in this article.

K9s is your best friend (get it? 🐶) when exploring your cluster via the terminal. It shares commonality with Vim for its interaction style using shortcuts and starting commands with: but don’t let that discourage you. K9s keeps a vigilant eye on Kubernetes activities, providing real-time information and intuitive commands for resource interaction.

k9s: brew install k9s

I would like to put in a vote for k9s, which is also on the list at Terminal Trove. [0] It's the most convenient tool I've ever found for Kubernetes management. Based on that experience I'll definitely be checking out Harlequin.

[0] https://k9scli.io/

$ wget https://github.com/derailed/k9s/releases/download/v0.29.1/k9s_Darwin_amd64.tar.gz $ tar -xzf k9s_Darwin_amd64.tar.gz $ sudo mv k9s /usr/local/bin/

All in all, run things, do some kubectl apply -f something.yml every day, install k9s, and try to configure a big one cluster at some point.

(K9s is one of my favorite tools for navigating Kubernetes clusters through the CLI).

K9s is an open-source, terminal-based UI for interacting with your Kubernetes clusters, making navigating, observing, and managing your apps easier. If you use Kubectl but wish it was easier and faster to use, K9s might be just what you're looking for!

k9s