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

Kubernetes V1 Released

googlecloudplatform.blogspot.com

Post reply on HN
Print view View original

81–90 of 110 posts

Re: Kubernetes V1 Released

#81

Post by davidooo »

tlrobinson wrote: post #50
ninkendo wrote: post #42

Earlier quoted context omitted.

I'm afraid answers like this actually make the confusion problem worse (nothing against your comment, just an observation in general.) If you're confused about the differences between similar-sounding products X and Y, the fact that "X runs on Y" or "Y supports X" has never made the situation any better, it only makes the line between X and Y even more blurred. I think this is especially true of Mesos, because people…

"X runs on Y" at least implies Y is "lower level" than X. As I understand it, Mesos is analogous to an operating system kernel for your cluster, while Kubernetes is a CaaS (containers-as-a-service) layer on top.

When Kubernetes runs on Mesos, that's correct.

Kubernetes can also run directly on VMs or physical machines.

Re: Kubernetes V1 Released

#84

Post by bkeroack »

SEJeff wrote: post #79
bkeroack wrote: post #39

Earlier quoted context omitted.

To add to the others, in a nutshell: - Mesos is a generalized, low level framework for distributing workloads over multiple nodes. It provides mechanism not policy. Therefore it requires quite a bit of up-front work to build something usable for any given application. - Kubernetes is an opinionated cluster execution tool. It provides tools and a curated workflow for running distributed containerized applications. It'…

Mesosphere is a company, not a piece of software. I think you're referring to Mesosphere's dcos[1]. DCOS is some really nice packaging for marathon, chronos, etc, with a nice cli tool for downloading and installing new frameworks onto mesos. Personally, I find using Aurora a lot nicer. That being said, I do think the kubernetes-mesos gives you far and above the best of both worlds. You get the developer story of kube…

> I was actually shocked when I found out after bringing a new kubelet (worker node) online, you have to also update a service on the master

On AWS that has not been my experience. Nodes can be brought up dynamically and they register themselves with the master.

Re: Kubernetes V1 Released

#85

Post by ecnahc515 »

rjusher wrote: post #24

I might come across as ignorant but what is the relationship between Kubernetes and Docker, because when I was reading the article I tought of it as a Docker competitor, but further down in the comments, there is one that says they do different jobs. And that confused me.

Docker as an organization, is a competitor to Google and Kubernetes, but Docker as a tool is complemented by Kubernetes.

This is because Docker is building it's own scheduling/orchestration tools, which is what Kubernetes is for. However, as a container runtime, Kubernetes works great with Docker.

Re: Kubernetes V1 Released

#86

Post by miles932 »

teraflop wrote: post #73
TheIronYuppie wrote: post #61

Earlier quoted context omitted.

Sorry about that! Free trials have a timeout :( Can you submit a support request and we'll see what we can do? Also, spinning up a cluster should be incredibly cheap if you just want to mess around for a little bit - we do billing by the minute :) Full disclosure: I work on Google on Kubernetes

Yeah, sorry if that came off as snarky; I appreciate the suggestion. I guess I can understand the cost-cutting mentality that drives Google, AWS, etc. to limit these kinds of offers to "new customers" only. Just remember to consider what kind of incentives you're creating. By effectively punishing developers for being early adopters/experimenters, you're making them wary of signing up early for whatever new and inter…

Any suggestions for incentive systems that would be motivational for you? We want to help!

Full Disclosure: I work at Google on da Cloudz

Re: Kubernetes V1 Released

#87

Post by [deleted] »

bkeroack wrote: post #84
SEJeff wrote: post #79

Earlier quoted context omitted.

Mesosphere is a company, not a piece of software. I think you're referring to Mesosphere's dcos[1]. DCOS is some really nice packaging for marathon, chronos, etc, with a nice cli tool for downloading and installing new frameworks onto mesos. Personally, I find using Aurora a lot nicer. That being said, I do think the kubernetes-mesos gives you far and above the best of both worlds. You get the developer story of kube…

> I was actually shocked when I found out after bringing a new kubelet (worker node) online, you have to also update a service on the master On AWS that has not been my experience. Nodes can be brought up dynamically and they register themselves with the master.

[deleted]

Re: Kubernetes V1 Released

#88

Post by cjcullen »

smegel wrote: post #76

> containers scheduled That seems awfully slow for a fancy chroot. I use KVM to bring up WinXP snapshot VMs in around 2s to a running state...maybe they mean 5ms?

5s is the right number, but it leaves out that it is 99%ile, on a 100-node, 3000-pod cluster. See https://github.com/GoogleCloudPlatform/kubernetes/issues/395....

Re: Kubernetes V1 Released

#89

Post by andybak »

andybak wrote: post #64
pestaa wrote: post #59

Earlier quoted context omitted.

Or they assume your wallet is already open.

Then they are wrong. I actually find this a common issue with a presumed sales pipeline I encounter. They think: 1. He finds us. 2. He's interested and signs up for a trial 3. We hopefully convert before the trial is over What actually tends to happen 1. I find something that looks interesting 2. I sign up 3. Real work intervenes 4. Several months later I have some time to look again but my trial has expired. To be f…

(this would be more readable if Markdown was less idiotic)

Re: Kubernetes V1 Released

#90

Post by bcbroussard »

davidooo wrote: post #77
bcbroussard wrote: post #72

Earlier quoted context omitted.

Here's the doc for resource constraints, called "limits" in Kubernetes. https://github.com/GoogleCloudPlatform/kubernetes/blob/maste... The Kubernetes scheduler looks at "fit" and "resource availability" to determine the node a pod will run on. Nodes can also have labels like "high-mem" or "ssd", so you can request a particular type of server (via the the nodeSelector field). More details are in the link above.

The page you linked to describes a slightly different feature, namely the ability to restrict and override the resource requirements of Pods at the time they are submitted to the system. So it's part of the admission control system, not part of the scheduling. The documentation on resource-based scheduling is at https://github.com/GoogleCloudPlatform/kubernetes/blob/maste...

Thanks davidooo - I was specifically referring to the section on "limits at the point of creation" which gives a practical example of using limits in a multi-namespace (multi-tenant) environment. (https://github.com/GoogleCloudPlatform/kubernetes/blob/maste...).

The new documentation you linked to has good explanations in it as well.

Post reply on HN