Kelsey Hightower
Engineer and teacher; wrote Kubernetes the Hard Way, was a distinguished engineer at Google Cloud, and retired from full-time work in 2023.
Kelsey Hightower did not write this page. What is this?
It collects the places they publish and what they have said there, each linked to the source. They have no account here. Is this you? Claim it, correct it, or ask us to remove it from ppll.
Where they publish
Beliefs
Korrents What they believe 28 beliefs — each backed by an exact quote.
Each is a — compiled by korrents.com, not by them: the one-line wordings are korrents', the quotes are theirs.
Recent
Entrepreneurship is over-glorified: a parts-and-service business has none of the upside people imagine, because it does not grow the way a software company does.
and it turns out people kind of over glorify entrepreneurship. I think a lot of people believe there is tremendous upside, right? the type of entrepreneurship we talk about with software companies, the the upside is crazy. But when you're doing like selling parts or service business, unless you plan to open lots of stores and you know grow a larger employee base, it's not the same growth trajectory as software companies.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Being an all-star at the activity is not impact: the measure is whether the team's queue is empty, not how many calls you personally took.
And it's the first time I learned the difference between activities and impact. activity is you being an all-star answering a bunch of calls, but the ticket queue for the team is still high.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Every talk you give is a job interview, because an audience is reading what you are as much as what you are saying.
And what I learned from the puppet days, every presentation is an interview. I don't think a lot of people think about it that way cuz people are looking at you on stage and they get to see what you're about.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Show 25 more
Kubernetes won because Docker had already won: it inherited the one container runtime the whole industry had agreed on, instead of shipping another.
I think the number one success criteria was docker so remember there was mos and msosphere and they had their own runtime corp had come out with nomad and they had their own runtime but the biggest runtime that had already got global consensus was docker
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Docker Swarm lost because it stretched a single-node API across a cluster, and no amount of bolted-on storage and networking could repair that choice.
They tried to take the Docker API which worked really well for one node and expand it across multiple systems and it was not the right API to scale to another type of thing that we needed. And so they kept trying. They tried to add storage. They tried to add networking but the Docker API was never meant for that.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
The real shift Kubernetes made was from infrastructure as code to infrastructure as data: you declare the object and control loops reconcile it, instead of running a program.
we went from infrastructure is code to infrastructure is data and infrastructure is code is like if this do that um bring in this module for loops all this stuff and Kubernetes is like no no no you have to specify exactly the containers you want how much memory that they need and then we have the status field to tell you if they were running or not
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
What makes Kubernetes powerful is that it gave infrastructure a type system, and types are what finally made automating infrastructure safe.
The thing that makes Kubernetes powerful, there's a data model. We gave infrastructure a type system. So instead of imperative shell scripts, you finally had types.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
The hardest problem a company full of brilliant engineers has is not how to build something — it is what to build.
So you have a lot of smart Googlers. These people are brilliant. I mean extremely brilliant to the point where the hardest problem Google had in my opinion was what to build. Not how to build it, what to build.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
A launch is a party; a landing is customers paying for the thing, and only the landing is worth measuring a career by.
So launches is we ship the thing, people have a big celebration. I know that doesn't matter as much as the landing. People are actually paying for it.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
The moment somebody offers you more, that is what you are worth — it is market evidence, and you cannot unsee it.
At that moment, you are actually worth $120,000. Cuz you now have evidence from the market. The $100,000 you currently make doesn't look so good anymore. You can't unsee a job offer for 120.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Money is worth having as freedom tokens: the point of it is being able to leave the game, not what it buys.
So the money started to become like freedom tokens. This money means I can get out of the game.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Raise the number all you like, but never raise the lifestyle with it — you can make a lot of money and still be broke.
But the thing I was careful not to do was to change the lifestyle because I I watched people around me change the lifestyle so you can make a lot of money and still be broke.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Optimising for productivity costs you the experience, the hard parts and your colleagues — you are a human, not a computer.
if you just do productivity, you're going to miss everything. You're going to miss the experience. You're going to miss this part that are hard. You're going to miss the collaboration with your team.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Going slowly is a luxury: the busier you are, the more of your own life you have to pay somebody else to live for you.
It is a luxury to be able to afford to go slow because when you're really, really busy, you need an admin because you can't afford to book your own tickets. When you're really busy, you cannot afford to clean your own house.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Crypto's real question was never how transactions settle: changing the currency is something that happens to retired people who have no way of making new money.
There have been countries that have gone through currency resets. This is not a nice experience because if you had a little bit of money, a currency reset can mean you have now no money. If you had no money, it may feel like it's impossible to ever get any more money. If you're retired, what do you do during a currency reset?
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
The alternative to burning tokens is a zero-token architecture: learn the thing, think for yourself, and finish the task.
Now, I post things like, "Hey, I'm adopting the zero token architecture." People like, "What's zero token architecture?" as like instead of burning tokens, you learn things and you think for yourself and just complete tasks.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
A model may have a worldview of its own, but it can never be placed above a person under any circumstance.
Maybe it's arguable that they have their own worldview based on that. And maybe it's slightly different, but I can never put the machine over a person under any circumstance.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
The job has always been to solve human problems, and software is not required for every human endeavour.
It's like maybe you don't understand what the job has always been. We are trying to solve human problems and we use whatever technology is required. In some cases, the technology happens to be software and software ain't required for every human endeavor.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Ban the word AI from a pitch and the founder is forced to show you the actual problem — the word is an umbrella people hide the details under.
do not say AI because what we don't want to do is use a big umbrella to describe what you're doing. Let's get concrete details. These are computers. These are computer programs.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
A whole industry pivoting to AI is children's soccer: everyone runs to the ball and nobody plays a position.
If you all pivot to AI, then you all will have a problem. It's like kids learning to play soccer. They all run to the ball. No strategy. Spread out, figure where you add value and play your position.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Having a model regenerate the same block of code over and over is insane however fast it feels — that is what functions and libraries were invented for.
So if you find yourself generating the same blocks of code over and over, even though it feels fast or convenient, it is still insane.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
MCP is not a new foundation for anything — it is API design, and Kubernetes was already turning one intention into seven calls a decade ago.
So I'm looking at this like guys the fundamentals of this isn't like everything is going to change because of MCP. What the hell? A whole conference guys? This is just API design.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Seven API calls to get a virtual machine was never an intention, it was a procedure — most of our APIs were designed wrong even for humans.
You have to call like seven APIs to get a VM in the cloud. Create a VM, a network, a storage device connected to a VPC and then attach credentials. Like that's not intent based. I want a VM.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
If you will write a huge markdown file so an agent has context, you should have written the documentation that gives a human the same context.
I'm watching people write these huge markdown files to give the agent context. How about you write documentation to give me context so I can have fully working examples.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Software developers spent thirty years automating other people's industries away, so they should not expect sympathy now that it is their turn.
And so you have been part of the change to other industries and other people yourself. What did you think about that? Did you even think about it at all? So let's not be surprised if you find no sympathy from all the other professions that you've helped force change upon.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
Developers who defined the job as being the only person who could write code have just watched the only thing they were good at get commoditised.
All you had to do was write code and you were safe. And you probably made more money than everybody and you were fine with that. Now you got caught. The only thing you were good at is now been commoditized.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
You do not have to know how it works underneath, but depth is where invention comes from — nobody who only knows the surface invents a programming language.
But if you ever want to get better at anything, and sometimes that depth, that nuance is the thing that leads to an invention, right? If you know how a compiler works, if you know how memory management works, that might give you enough information to say, "Oh, I can make a new programming language."
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
If this much effort goes into training the model, you had better be willing to keep training your own.
But make no mistake, if we put this much effort in training the model so that it can spit things out, you better make sure that you are willing to train your own model.
Kubernetes and retiring at the top with Kelsey Hightower Said 3 Jun 2026
What is a korrent?
A korrent is a belief a person has stated in their own words: one sentence stating the claim, backed by a quote and a source, kept at korrents.com.
Under a name here, the quoted block is what they actually said. The korrent beneath it is the claim those words support, in korrents' wording — tap it to see the record, its source, and who else holds it.
Nobody here wrote their own korrents. They are compiled from public statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they do, this site shows a machine translation beneath the post, in this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the serif above is exactly what the person published, and it is what to quote them on. A translation can be wrong in ways that matter, especially about tone.
Only the post's own words are translated. A quoted post, a linked article and a belief on korrents.com are left in their original language.