Coté's Wunderkammer

Share this post

Kubernetes Service & Distro Usage

newsletter.cote.io

Discover more from Coté's Wunderkammer

My newsletter is mostly software, cloud, DevOps, platform engineering stuff from a culture, process, & business angle. Also, the occasional travel and IRL talk, links & other fun found stuff.
Continue reading
Sign in

Kubernetes Service & Distro Usage

84 pages of Kubernetes analysis, plus links, and peeing in cups.

Coté
Oct 10, 2023
Share this post

Kubernetes Service & Distro Usage

newsletter.cote.io
Share

Just a few things today.

The Network is the Computer

“Sun Microsystems founders (left to right) Bill Joy, Andy Bechtolsheim, Scott McNealy and Vinod Khosla stand in front of their sports cars at the company’s facilities in Palo Alto in 1987”. Posted by readjpeg.raw.

Kubernetes Distro Usage

If you’re interested in marketshare, usage trends, and benefits/problems in Kubernetes-land, Torsten and crew at EMA has a new stack of analysis and charts about Kubernetes out. It’s a packed 84 pages that tries to get it’s hands around the Kubernetes world through many, many different methods: surveys, analyzing GitHub, and even things like finding as many detectable Kubernetes clusters on the public Internet as possible.

Here’s one slide estimating the Kubernetes services/distros in use:

Check out the rest, for free thanks to my work, VMware.

Wastebook

  • “Q: Female artists still have to sometimes use urinals backstage, because clubs weren’t built with women stars in mind. Joan Jett: Oh, I get very friendly with cups. I mean, [expletive] a urinal. That’s not clean. I’m just in my dressing room, with a cup. Quick, easy, you don’t have to go anywhere. Try it next time! Solo cup. Check that Solo cup before you drink. [Laughs]” Here.

  • “Stuffing the prompt.”

  • “Good morning, would you like a breakfast calzone?” On the DTW->AMS flight. (I said, “no, thank you.”)

  • “Reverse sales.”

  • “a group of vicious squirrels”

Relevant to your interests

  • The Musk Algorithm - “Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Always do so, even if the requirement came from me. Then make the requirements less dumb.”

  • Keep track of time in “metric time.” And, more explanation from Mike Olson. I saw him present (announce, I guess) this at Monktoberfest. Fun!

  • Measuring Developer Productivity: Who’s Winning the Debate? - more from this weird nerd-fight about developer productivity metrics.

  • How Dell Claims Apex Smooths out ‘Ground-to-Cloud’ Azure HCI Connections - Dell has a private Azure box.

Upcoming

Talks I’ll be giving, places I’ll be, things I’ll be doing, etc.

Oct 10th, 17th, 24th talk series: Building a Path to Production: A Guide for Managers and Leaders in Platform Engineering Nov 6th to 9th VMware Explore in Barcelona, speaking (twice!).

Log Off

There’s now 700 of you subscribing - thrilling for me, of course!

If you like this newsletter, it’d be cool if you recommended it. I mean, come on, everyone who creates something like this wants as many people looking at it as possible. We all care about the numbers. And, thanks, for bringing some dashboard joy into my life.

Share this post

Kubernetes Service & Distro Usage

newsletter.cote.io
Share
Previous
Next
Comments
Top
New
Community

No posts

Ready for more?

© 2023 Coté
Privacy ∙ Terms ∙ Collection notice
Start WritingGet the app
Substack is the home for great writing