Everything open source
May 16–17, 2016: Training & Tutorials
May 18–19, 2016: Conference
Austin, TX

Containers at scale thanks to Kubernetes

Brandon Philips (CoreOS, Inc)
9:00am–12:30pm Monday, 05/16/2016
Location: Ballroom F Level: Intermediate
Average rating: ***..
(3.52, 23 ratings)

Prerequisite knowledge

Attendees should understand the basics of Kubernetes, as well as general container concepts, and be interested in the finer points of operating a cluster for a production use case.

Materials or downloads needed in advance

You'll need a laptop to follow along.

All attendees should come prepared with a AWS account and AWS CLI with billing hooked up if they plan on following along.


Security, easy scaling, and high availability are essential needs for real-world application infrastructure. Using examples drawn from Tectonic’s use of Kubernetes to host CoreOS SaaS products and recommendations given to Tectonic customers, Brandon Philips offers a how-to talk and tutorial demonstrating how to set up a production-ready cluster with full Transport Layer Security (TLS), manage the cluster through scaling and upgrade, and build the cluster for high availability. Brandon also addresses TLS management, managing your machine’s over time, and upgrading Kubernetes itself while keeping availability. After bootstrapping a securely configured Kubernetes cluster, you’ll learn how to manage the cluster through a variety of production situations like etcd member host failure, worker node failures, and cluster scaling.

Photo of Brandon Philips

Brandon Philips

CoreOS, Inc

Brandon Philips is CTO of CoreOS, where he helps build modern Linux server infrastructure. Prior to CoreOS, Brandon worked at Rackspace hacking on cloud monitoring and was a Linux kernel developer at SUSE. As a graduate of Oregon State’s Open Source Lab, he is passionate about open source technologies.

Comments on this page are now closed.


Chris Linstid
05/16/2016 5:05am CDT

The description of pre-requisite knowledge was woefully inadequate and the instructions for pre-installed requirements were missing a few steps. I tried to follow along but I was tripping over some of the initial setup while Brandon sprinted through the setup, using different values than those shown in his documentation. I had to ditch following along. I hope to come back later and give it another try, but for a tutorial, that was disappointing.

Once I stopped trying to follow along, the talk was really good, but honestly I think this would be better as a normal session and not as a follow along tutorial.

Dan Finn
05/16/2016 4:04am CDT

It might have been nice if you had included the link to your repositories and the full setup instructions in the email that went out yesterday. All that it had listed for requirements was an AWS account and awscli but in reality there’s much more than that that is needed to be ready for this.