As remarkable as Docker containers are, they still need to be heavily scheduled and orchestrated to run efficiently, and seamlessly replaced and re-balanced when they fail. It’s a big job, well beyond the abilities of Chef, Puppet, and similar tools. This O'Reilly report introduces you to Kubernetes, a cluster management system from Google that’s capable of scheduling and launching roughly 7,000 containers a second.
Dave Rensin, who directs Global Cloud Support and Services at Google, explains piece-by-piece how this system works. If you’ve created at least one simple container with Docker, you’ll understand how to get started with Kubernetes by using one of several options.
- Examine pods, a collection of containers bundled and scheduled together
- Run through volumes, the filesystems your container can see and use
- Create and organize pods with labels and annotations
- Use replication controllers to manage replicas: multiple copies of a pod
- Set up services, long-lived endpoints that identify a set of pods in your cluster
- Get started using your own servers, VMs from the public cloud, or a managed offering from a major cloud provider
- Find examples on GitHub of Kubernetes in use, including WordPress and Guestbook
Table of contents
- 1. In The Beginning…
- 2. Go Big or Go Home!
3. Organize, Grow, and Go
- Better Living through Labels, Annotations, and Selectors
- Replication Controllers
- Health Checking
- Moving On
- 4. Here, There, and Everywhere
- Title: Kubernetes
- Release date: September 2015
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9781491931875
You might also like
Software Engineering at Google
Today, software engineers need to know not only how to program effectively but also how to …
Building Event-Driven Microservices
Organizations today often struggle to balance business requirements with ever-increasing volumes of data. Additionally, the demand …
Python for DevOps
Much has changed in technology over the past decade. Data is hot, the cloud is ubiquitous, …
Designing Distributed Systems
Without established design patterns to guide them, developers have had to build distributed systems from scratch, …