297 karma · joined December 18, 2014
YC Badge: 0x1ad37a71e445562ce1a8d57a90facf5a4bb4d0c4
I wrote a blog post that breaks down basic Kube architecture, if you're interested: https://blog.redspread.com/2015/12/31/basic-kubernetes-vocab...
A little history - it's an open source project by Google, modeled after Google's infrastructure (Borg/Omega). Many of the engineers who designed Borg/Omega are chief architects of Kubernetes.
For us, we see the big use case for full deployment versioning when there are multiple kube objects and config files to track. Already this is introducing some complication into developer workflows - ex: I have a bunch of services, rc's, and secrets. They are parameterized by this configuration. Now I've updated the configuration. I want to propagate that configuration to my cluster "with no downtime” - right now there isn't an easy way to do this.
Our mission is to enable people to own their own deployment processes and infrastructure, and we're very passionate about that (see our philosophy.md).
Would love your angry bug reports, feature requests, and feedback!
Curious to hear from those with an expertise in robotics
"When he wrote 'Man will sooner will nothingness than not will,' Nietzsche was exposing the destructive side of humanity’s meaning-making drive. That drive is so powerful, Nietzsche’s saying, that when forced to the precipice of nihilism, we would choose meaningful self-annihilation over meaningless bare life. This insight was horrifically borne out in the Götterdämmerung of Nazi Germany, just as it’s being borne out today in every new suicide attack by jihadi terrorists — even as it’s being borne out here at home in our willfully destructive politics of rage."
"Our drive to make meaning is more powerful than oil, the atom, and the market, and it’s up to us to harness that power to secure the future of the human species."
Seems like most of the tooling now focuses on automating small parts of dev and ops teams' workflows, instead of looking at the larger picture of organizational tooling. I would guess that in a few years we'll see a lot more PaaS-workflow solutions focused on abstracting away a lot of the operational complexity of microservice architectures, reducing the barrier to entry for "maturity" of dev/ops teams, just like AWS & co reduced the need for people to really understand server hardware.