Kelsey Hightower

Like blocks.

Like blocks.

Now, instead of like, you have to open the entry point to see what we're going to do versus full lifecycle management independent.

So it solves that number one problem.

The other big one that I think that they solved, number one, we went from infrastructure as code to infrastructure as data.

And infrastructure as code is like, if this, do that, bring in this module, for loops, all of 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.

And you would take this data object that you could write by hand, give it to an API, and then the control loops would operate on this state.

So that means it didn't matter if you had Ruby, Python, or anything.

You can just take your IDE, write some YAML, give it to another tool, manipulate the YAML,

and then pass it down to the API servers.

You can build any combination that you want it without having to be a compiler first.

That to me was a fundamental game changer that I don't know if a lot of people understood why it felt very easy to onboard to Kubernetes.

kubectl apply object.

Off you go.

And the last thing I think, credit to Brendan Burns, the ability to extend Kubernetes in a first-class way.

OpenStack didn't have it.

Mesos didn't really have it.

In Mesos, you have a scheduler and you built the other part of the scheduler so you can have Spark, Hadoop, Marathon, but you had all these other tools sitting on top of a thing.