CloudNative

for now we have been focused on stateful and stateless web app hosting; lots of our customers use the platform for scale out testing, and build their devops pipelines on the platform too.

Next up for #kubernetes will be running scale out batch workloads on the same basic infrastructure as the app hosting.

@cmcluck the microservices architectures haven't focused much on stateful data (to date). do you see that expanding with k8r going forward, or should that be solved at the container layer?

via @jeffsussna - Go directly to your nearest @kelseyhightower preso :)

I would look at the examples in the GKE docs, they have a networking and storage story, there may be similar examples on the kubernetes site.

Yes; this is critical. inside Google we run all our stateful services on the same clusters as everything else. Even today we have pretty solid volumes support for local and network attached storage. I expect more intelligence around state to come.

https://cloud.google... has a pretty gentle "how to" for Node.js developers

It the Google container optimized VM (https://cloud.google...) based on Debian with latest Docker and Kubelet installed

damn, forgot to switch accounts again.

This is kind of my point. There is a difference in relevance and demand.

busted

@cloud_opinion Um... Not buying it. ;)

there's lots of different aspects to the Google Cloud, if all you want a virtual machine running Windows or Linux you can use Google Compute Engine. If all you want is reliable storage, Google Cloud Storage, or Cloud DNS, etc.

I am cloud opinion

@furrier No, I am @cloud_opinion

We are all @cloud_opinion

@stu I'll take that for a dollar.

we all *have* cloud opinions

weird; I just circumnavigated in 8 days for #GCPNext, talked to 10k+ folks, and the demand is real. Use cases range from complex to simple, but value prop stands up across oldschool and #cloudnative

You say science like it's a bad thing :) But in all seriousness, we want to do two things - meet customers where they are today and help them with the transition to cloud native, at their own pace.

We are working hard to change this. A lot of Google technology has gone mainstream (bigtable -> nosql; mapreduce -> hadoop; cgroups -> Docker). We decided to build this one in the open with the community to make it immediately relevant to business.

> I don't know. Know a few people who spend more time in fly over country instead of flying over
@ImAmyO @Schmarzo

@cloud_opinion is your mum

@njoneja science is a bad thing to a lot of people, don't shoot the messenger :) I am an admirer of Google, met some of their team tonight, but it doesn't mean I'm blind or lacking critique

ReplicationControllers can scale any set of pods, but the policy of how you scale (e.g. how quickly) may be something custom that you want to build.

@brendandburns Are we able to run custom ReplicationControllers on GKE and if so are there any examples?

There are not any examples, but it's definitely possible. Just create your application that talks to the Kubernetes API and creates/deletes Pods. Moving toward the future, we would like to enable the API be extensible for custom user-defined types

If they did, does the market need it? (mass market vs. corner cases)

we have a commercial offering called GKE (google container engine). we don't plan to offer an on-premises version directly, but are working closely with the community and OpenStack Foundation to take Kubernetes on-prem.

Kismatic supports a number of exciting scale-bound production Kubernetes deployments that demand support SLAs for OSS K8S.

great question: how does your average enterprise way this up?

Does Google have to become more than a corporate sponsor to #OpenStack and join the foundation to make on-prem k8s happen sooner?

We see a lot of enterprise customer looking at linux containers & kubernetes as a way to bring #cloudnative apps to market

We want to help our customer succeed in #cloudnative apps with #kubernetes & linux containers

i would like #kubernetes to be as stable and ubiquitous as the linux kernel. and just like the linux kernel i would like to see a whole ecosystem emerge to enrich and support it.

we need to move to a world where developers can rely on a set of standard distributed systems services that have very few semantic differences between environments.

#kubernetes and the linux kernel - they both start k

and i hope that #kubernetes stays focused on its mission of scheduling and orchestration and has as strong a sense of what it isn't as what it is.

Resisting the temptation to be all things to all people is tough.

Yes. We want to get more mileage on SLAs and have people on final production bits for a while

We also want Container Engine to take over the Kubernetes launch - we wanted separate events

We're considering using GCE Beta in production and accepting the risks are there others testing in production? Thoughts?

we have a number of production users, but at this time the product does not have a formal support program or a formal SLA. our developers try our best to support the community (and do a good job), but more will be coming for GA.

(just to clarify I think you meant GKE beta; GCE - Google Compute Engine - is GA)

When will GCE be upgraded to 1.01?

@njoneja You are correct GKE, Thanks...

new GKE clusters are already 1.0.1, but the 1.0.1 binary removes the v1beta3 Kubernetes API, so we need to give customers time to migrate their YAML/JSON configs, we expect to role the upgrade in 3 weeks or so, earlier if customers opt-in to the upgrade

@KitMerker Correcting Kit's post: We didn't want Container Engine taking over the Kubernetes launch. We are working hard to keep them separate.

ha! typo, my bad #blush

@cmcluck The Kubernetes team has been extremely transparent and professional. I would say this has been one of the best OSS releases I've witnessed in some time.

@cmcluck It was your candor about the relationship between Container Engine and Kubernetes that lead to chose Container Engine for our first production deployment.

aw, shucks

aw, schucks you guys are too nice #blushes. More concretely, it's really important to be open to meeting the community where they are and listening to the problems that they want to solve.

When/where will the k8s v1 docker image be available? I've heard it's hard to find, myself included.

uh @brendandburns needs to stop tweeting and start coding :-)

@KitMerker I'm working on this today... The image itself is described here: http://kubernetes.io... but it's currently on 0.21.2