Live data from Hacker News

Kubernetes V1 Released

googlecloudplatform.blogspot.com

91–100 of 110 posts

Re: Kubernetes V1 Released

#91

Earlier quoted context omitted.

Except: "Sorry, you aren't eligible for a free trial at this time. The free trial is for new customers only." Apparently, the fact that I've been curious enough to experiment with other Google developer products in the past means I'm not part of the target audience.

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

Got a fairly quick response from Google Cloud Billing Support:

"Unfortunately, the system is developed by design to only apply the free trial credit to new email address creating a new billing account and we can't apply it for already existing emails." Bummer.

Re: Kubernetes V1 Released

#92
post #38

Getting started with Kubernetes is pretty easy and I wrote a guide to quickly run it on your local machine: https://www.cloudgear.net/blog/2015/5-minutes-kubernetes-set... It's not up to date with Kubernetes 1.0.0 but I'll update the images as soon as the final version 1 is tagged.

I definitely don't want this to come off as a sales pitch, but you can get started in one click using Google Container Engine (and $300 in free credit) as well. Full disclosure: I work at Google on Kubernetes

Well, it's certainly not a sales pitch anymore, given the brilliant customer support on display here.

Re: Kubernetes V1 Released

#93
post #51

Earlier quoted context omitted.

We were looking at this, but noticed that you have to one run cluster per availability zone. Any plans for being able to run a cluster across an entire region within GCE?

Yes, we've heard from a number of people who want that and will improve regional support. Current ideas are either a single regional cluster or via federation of multiple zonal clusters. See eg https://github.com/GoogleCloudPlatform/kubernetes/blob/maste... for an proposal on the latter.

FWIW, I'd love to have Kubernetes clusters spanning a region with multiple regions/providers managed by Ubernetes. That would be the sweet spot for our particular usage case.

This is only one point of data for you, of course.

Re: Kubernetes V1 Released

#94
post #9

I've found that Kubernetes is a big hammer. If your problem can be backed by a web app, you should start with AppEngine. If you need specialty library support or wider computational space per instance, you can move your AppEngine app to ManagedVMs (which uses Kubernetes under the covers). If you need special, "grid-like" services where you need exquisite control over the entire stack, only then does it make sense to…

ManagedVMs don't use k8s under the covers afaik. However there's GKE (Google Container Engine), which goes on top of (at least 3) MVMs and that one does use k8s. While it is true that going with a PaaS(-like) solution like AppEngine or Heroku is easy in the beginning it can get pretty expensive pretty fast and it limits you in the choice of languages, frameworks, and data stores you can use. This can in some instance…

I've worked on what is ostensibly a Heroku competitor (Cloud Foundry).

I don't see where the limits on languages, frameworks or data stores comes in.

Languages are extensible in buildpacks, data stores are ordinary services. Heroku pioneered the 12-factor app model, Cloud Foundry lets people run it themselves.

Re: Kubernetes V1 Released

#95

Interesting to see IBM placing a bet each way by joining the new foundation, seeing as they're already in the Cloud Foundry Foundation. Edit: and I see the Cloud Foundry Foundation logo on the Cloud Native Foundation homepage. It's Foundations all the way down. (Disclaimer: I work for another CFF member, Pivotal).

Its pretty orthogonal to cloud foundry, which is a composite infrastructure, while these are lower level products that can be used to build PaaS.

Right -- the analogous component is Diego.

I guess I got caught up by the inside baseball.

Re: Kubernetes V1 Released

#96
post #51

Earlier quoted context omitted.

I definitely don't want this to come off as a sales pitch, but you can get started in one click using Google Container Engine (and $300 in free credit) as well. Full disclosure: I work at Google on Kubernetes

We were looking at this, but noticed that you have to one run cluster per availability zone. Any plans for being able to run a cluster across an entire region within GCE?

Agreed. That's the only reason we're not on Kubernetes right now. It really dramatically increases the amount of infrastructure we need to run when we're forced to run three Kubernetes clusters to run a single MongoDB replica set. But I love everything else Kubernetes is doing and so I'm very anxious to see that be addressed.

Re: Kubernetes V1 Released

#97

Earlier quoted context omitted.

A couple things I've found when evaluating these: Docker Swarm seems to be the only one that supports one-off interactive containers that bind a TTY, like a Rails console (i.e. does the cluster support `docker run -it --rm busybox sh`). But its scheduling strategies[1] aren't as sophisticated as the others. Marathon doesn't support linked containers[2], so if you're using Mesos and need linked containers, you probabl…

I've been playing with Swarm and like what I've seen so far. WRT Kubernetes, on a platform other than GCE, is Flannel required for networking?

As others have mentioned there are multiple options. If you want micro-segmentation (one network per app-tier) with fine-grain access control you can use the OpenContrail plugin https://github.com/Juniper/contrail-kubernetes. It has the added advantage that you have a tenant network span k8s, openstack, vlans, or anything else you can plug into a reasonable mid-tier router.

[Disclosure: i'm currently working on this project]

Re: Kubernetes V1 Released

#98

Earlier quoted context omitted.

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

There should be several types of free trials

1. Current type for new customers. Here's $500. Do whatever you want

2. For old customers who haven't ever used a free trial, give credit without limits (same as new customers)

3. For old customers who have used a free trial give credit only for services they haven't used

Re: Kubernetes V1 Released

#99
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?

It's the cadence of the etcd read cycle chosen for kubernetes. They could do it much faster, but I guess there are engineering tradeoffs based on the size of the cluster and the speed of the network.

Re: Kubernetes V1 Released

#100

Earlier quoted context omitted.

Any suggestions for incentive systems that would be motivational for you? We want to help! Full Disclosure: I work at Google on da Cloudz

There should be several types of free trials 1. Current type for new customers. Here's $500. Do whatever you want 2. For old customers who haven't ever used a free trial, give credit without limits (same as new customers) 3. For old customers who have used a free trial give credit only for services they haven't used

And #3 can give the positive effect of converting existing paying customers on one product into paying customers on new products.
Post reply on HN