Hacker News Reader

Comment by brendandburns | Hacker News Reader

Yeah, I think that sadly, there is going to be a little bit of an inevitable equivalent to the unix wars of the early 80s. The sooner we can reach a standard place, the better it's going to be for the container community and developers more generally.

One of the reasons that I pushed hard to get Kubernetes open sourced, is the hope that we could get out in front of this, and allow the developer community to rally around Kubernetes as an open standard, independent of any provider or corporate agenda.

View on HN

Disclosure: co-founder of Kismatic

We've spent a lot of time working with the Kubernetes community. I can only speak to our experience, but Brendan, Craig, and the rest of the team at Google have 100% lived up to the commitment of treating the Kubernetes project as truly open and independent.

Our Kubernetes dashboard was recently merged into Kubernetes [1]. We brought our own vision of a web ui to the project, and we could have gotten bogged down defending technology decisions, and philosophical nits. Instead, the response from Google, RedHat, and others in the community, was basically "Awesome! How soon can we get it in?"

All of the key players have the right approach, and that gives me confidence in the project's longevity.

[1] UI Demo video - https://www.youtube.com/watch?list=PL69nYSiGNLP2FBVvSLHpJE8_...

"allow the developer community to rally around Kubernetes as an open standard, independent of any provider or corporate agenda"

I look forward to Kubernetes becoming an independent project outside of Google then :)

I'm curious, @caniszczyk why would it need to become independant outside of Google? It's already an Apache licensed open-source project hosted on GitHub.

In essence, having diversity in ownership can help the project have a long life instead of being governed by one entity. There's a lot of risk that the main entity in charge will do things in its self interest instead of the self interest of the project (and its constituency) over the long term.

Independent ownership and proper governance will setup the project for long term success and as a small company, you should prefer it to be that way.

Disclosure: co-founder of Kismatic

I'm extremely pleased that Kubernetes has been open sourced by Google. It truly seems to me that the developer community is and will remain to be able to rally around Kubernetes as an open standard both today and in the future without fear of any outside agendas; as Brendan so eloquently stated. I for one applaud Google's level of transparency when it comes to the future of the project and the overall product vision.

I'm wondering if it was intentional or subconsciously accidental that you went with the "I, for one" construction... which is of course usually suffixed with "welcome our new [adjective] overlords".

"I, for one" was a common construction before, and remains common outside of, that text-meme.

What's the largest k8s deployment you guys have observed? You're not using k8s for anything major yet, right?

Thanks for building k8s! Even if it doesn't "win" in the end, it's been an extremely useful and reliable solution for my needs.

There needs to be a compelling way to run it on AWS for this to happen.

You mean like the work that Meteor is doing and hiring for https://www.meteor.com/jobs/core-developer-cloud-systems-eng... ?

Disclaimer: I work on Google Cloud but not Kubernetes or GKE.

Please check out: https://github.com/GoogleCloudPlatform/kubernetes/blob/maste...

for turn up instructions on AWS, it's as easy as:

export KUBERNETES_PROVIDER=aws; wget -q -O - https://get.k8s.io | bash

Ugh, to think people responsible for running large infrastructure installations are still piping random webpages to their shell in 2015.

It's not just them - doing things this way makes it seem like this is in any way acceptable. It's not. Stop it.

No wonder it's so easy for TAO.

What is a better alternative?

Just download the script and check it first before running it then.

It's not me; I don't run scripts written by people who think it's okay to exec shit from the network.

It's for the people who don't know any better and see this anti-pattern everywhere and thereby begin to think it's okay or accepted. It's not.

https://tectonic.com/

https://coreos.com/blog/kubernetes-on-any-platform/

https://coreos.com/docs/running-coreos/cloud-providers/ec2/

Disclaimer: I work on Google Cloud but not Kubernetes or GKE.

Reply on news.ycombinator.com