korrents
Kelsey Hightower

What Kelsey Hightower thinks about infrastructure

@kelsey-hightower · 28 positions · On ppll ↗

Self-taught software engineer, formerly a distinguished engineer at Google Cloud and one of the most visible voices in the Kubernetes community; retired from full-time work in 2023 and now advises and invests.

Kelsey Hightower did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

2 dated positions, 2026, in their own words. Our reading of what Kelsey Hightower has said — not written or endorsed by them.

2 positions so far — this page is not yet offered to search engines.

  1. 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 Hightoweryoutube.com 6th of 28 in this recording

  2. 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 Hightoweryoutube.com 7th of 28 in this recording