Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kubernetes 1.3 released

github.com

Post reply on HN
Print view View original

61–70 of 94 posts

Re: Kubernetes 1.3 released

#61

Post by chrissnell »

thockingoog wrote: post #22
chrissnell wrote: post #20

Earlier quoted context omitted.

We've seen similar savings at our company. We have deployed Kube on a 6-node cluster of CoreOS nodes with 512GB each. These are dedicated servers hosted at Rackspace. We're about 30-40% utilized on RAM and maybe 15-20% on CPU. To host a similar set of services on our older Openstack environment would require at least 2-3x the number of servers. The cost savings isn't even the best part. Kubernetes has allowed us to b…

You folks don't know how much it means to us to hear that people are finding success with Kubernetes. Thanks for using it. We'll try to keep pushing the envelope.

Thanks, Tim. Y'all have been awesome. Thanks for the quick response to GH issues and Slack questions. I hope that we can speak at a conference someday and tell the world about how much more fun and easy Kubernetes made our jobs.

Re: Kubernetes 1.3 released

#62

Post by chrissnell »

lobster_johnson wrote: post #47
Rapzid wrote: post #44

Earlier quoted context omitted.

I can't agree with this enough. We are all on AWS and the level of effort it would take to migrate to Kubernetes while maintaining our ability to spin up complete ad-hoc environments on the fly(which also serves as continual DR testing) seems too much to justify at this point. Also, I can't come out the other side with just one or two people understanding, or having any hope of understanding, how everything works :|…

One thing I would say is that — because of the aforementioned documentation mess — it seems more daunting than it actually is. And the documentation does make it seem like a lot of work. All you need to do, in broad strokes, is: * Set up a VPC. Defaults work. * Create an AWS instance. Make sure it has a dedicated IAM role that has a policy like this [1], so that it can do things like create ELBs. * Install Kubernetes…

You're making things really hard on yourself. Boot your nodes with CoreOS and it provides almost everything you need (except Kubernetes itself) out-of-the-box. It all works really well together and you get automatic updates, too. I can't imagine trying to run the cluster we run on Ubuntu, trying to roll my own Docker/etc/flannel installs.

Re: Kubernetes 1.3 released

#63

Post by chrissnell »

philips wrote: post #15

Yea! The team at CoreOS is really excited about this release and the work that we have done as a community. If you are interested in some of the things that we helped get into this release see our "preview" blog post from a few weeks ago, RBAC, rkt container engine, simpler install, and more: https://coreos.com/blog/kubernetes-v1.3-preview.html

I can't imagine running Kubernetes without CoreOS. You guys make everything so easy for us (Revinate). Our systems infra workload for the CoreOS/Kubernetes cluster is a tiny fraction of what we spend on our Openstack gear.

Re: Kubernetes 1.3 released

#64

Post by lobster_johnson »

chrissnell wrote: post #62
lobster_johnson wrote: post #47

Earlier quoted context omitted.

One thing I would say is that — because of the aforementioned documentation mess — it seems more daunting than it actually is. And the documentation does make it seem like a lot of work. All you need to do, in broad strokes, is: * Set up a VPC. Defaults work. * Create an AWS instance. Make sure it has a dedicated IAM role that has a policy like this [1], so that it can do things like create ELBs. * Install Kubernetes…

You're making things really hard on yourself. Boot your nodes with CoreOS and it provides almost everything you need (except Kubernetes itself) out-of-the-box. It all works really well together and you get automatic updates, too. I can't imagine trying to run the cluster we run on Ubuntu, trying to roll my own Docker/etc/flannel installs.

I'm sure CoreOS is nice, but we're currently on Ubuntu, and I'm trying to reduce the number of unknown factors and new technologies that we're bringing into the mix. Ubuntu is not the issue here. (FWIW, you don't need Flannel on AWS.)

Re: Kubernetes 1.3 released

#65

Post by bogomipz »

thockingoog wrote: post #58
bogomipz wrote: post #57

Earlier quoted context omitted.

Is it possible under specific circumstances such as if using LVM devices?

an LVM device is local, which is not supported as PersistentVolume. :(

Thats too bad it would be great to have an API for that. Mesos has the concept of path and mount disks, it would be neat if Kubernetes had something similar:

http://mesos.apache.org/documentation/latest/multiple-disk/

Re: Kubernetes 1.3 released

#66

Post by jturolla »

chrissnell wrote: post #59
aedocw wrote: post #35

Earlier quoted context omitted.

Have you compared the cost of maintaining your own CoreOS infrastructure at RAX just for kubernetes to using Googles Container Engine? If your services are all containerized and deployed via k8s to begin with, seems like you wouldn't have much reason to maintain your own infra at that point.

Yes, absolutely. We ran a four month experiment on GCE--we built an off-site logging cluster fluentd+Elasticsearch+Kibana. The performance was decent but the cost of RAM and disk are way higher. I will tell you that the economics are most definitely not there. This is a common misconception amongst the HN crowd in general--that public cloud infra is cheaper. For small footprints, public cloud makes sense but once you…

This is really interesting. Are you planning to open source this pipeline automation? I'd be interested.

Re: Kubernetes 1.3 released

#67

Post by igmor »

crb wrote: post #10
esseti wrote: post #5

I run into kubernetes a week ago. Found out this: https://www.udacity.com/course/scalable-microservices-with-k... Sounds pretty interesting, especially all the part about service discovery & node health/replacement. Anyone using it for production?

We (Google) are :-) Otherwise, there's a list at http://kubernetes.io/community/ , including: New York Times, eBay, Wikimedia Foundation, Box, Soundcloud, Viacom, and Goldman Sachs, to name a few.

Don't you guys use Borg that I don't know how close to kubernetes?

Re: Kubernetes 1.3 released

#68

Post by thockingoog »

bogomipz wrote: post #65
thockingoog wrote: post #58

Earlier quoted context omitted.

an LVM device is local, which is not supported as PersistentVolume. :(

Thats too bad it would be great to have an API for that. Mesos has the concept of path and mount disks, it would be neat if Kubernetes had something similar: http://mesos.apache.org/documentation/latest/multiple-disk/

We do! it's just not a "persistent" volume because, well, it's not persistent...

Re: Kubernetes 1.3 released

#70

Post by colemickens »

EDevil wrote: post #8

Now if only a native Azure provider was developed it would be excellent...

There's a working implementation here. I'm wrapping up cleanup + some unit tests before sending the PR. https://github.com/colemickens/kubernetes/tree/azure-cloudpr...

Not that it's very exciting to anyone who is familiar with Services + Pod networking, but there's a video demo: https://asciinema.org/a/48294

Post reply on HN