Book Image

Docker Orchestration

By : Randall Smith
Book Image

Docker Orchestration

By: Randall Smith

Overview of this book

Docker orchestration is what you need when transitioning from deploying containers individually on a single host to deploying complex multi-container apps on many machines. This book covers the new orchestration features of Docker 1.12 and helps you efficiently build, test, and deploy your application using Docker. You will be shown how to build multi-container applications using Docker Compose. You will also be introduced to the building blocks for multi-host Docker clusters such as registry, overlay networks, and shared storage using practical examples. This book gives an overview of core tools such as Docker Machine, Swarm, and Compose which will enhance your orchestration skills. You’ll learn how to set up a swarm using the decentralized building block. Next, you’ll be shown how to make the most out of the in-built orchestration feature of Docker engine and you’ll use third-party tools such as Kubernetes, Mesosphere, and CoreOS to orchestrate your existing process. Finally, you will learn to deploy cluster hosts on cloud services and automate your infrastructure.
Table of Contents (17 chapters)
Docker Orchestration
About the Author
About the Reviewer
Customer Feedback

Getting to know Kubernetes

Kubernetes is a complicated piece of software. As such, there are a number of components that an administrator needs to be aware of. Some will be used everyday while others will work quietly in the background to keep everything running.

Command-line tools

Following are the command-line tools:

  • kubeadm: This tool was added in Kubernetes 1.4, as of this writing, still considered an alpha tool. It is the new installer for Kubernetes on Linux hosts.

  • kubectl: This is the main tool used to interact with a running cluster. It is used to add pods and services, perform rolling updates, and much more. Nearly everyone who interacts with Kubernetes will use kubectl.

Master components

These components run on the master node. They are responsible for all of the high level controls of the cluster. Following are the master components:

  • etcd: This is where Kubernetes keeps its cluster configuration. Make sure this is backed up or you will be unable to recover your cluster in the event...