Book Image

Mastering Kubernetes - Second Edition

By : Gigi Sayfan
Book Image

Mastering Kubernetes - Second Edition

By: Gigi Sayfan

Overview of this book

Kubernetes is an open source system that is used to automate the deployment, scaling, and management of containerized applications. If you are running more containers or want automated management of your containers, you need Kubernetes at your disposal. To put things into perspective, Mastering Kubernetes walks you through the advanced management of Kubernetes clusters. To start with, you will learn the fundamentals of both Kubernetes architecture and Kubernetes design in detail. You will discover how to run complex stateful microservices on Kubernetes including advanced features such as horizontal pod autoscaling, rolling updates, resource quotas, and persistent storage backend. Using real-world use cases, you will explore the options for network configuration, and understand how to set up, operate, and troubleshoot various Kubernetes networking plugins. In addition to this, you will get to grips with custom resource development and utilization in automation and maintenance workflows. To scale up your knowledge of Kubernetes, you will encounter some additional concepts based on the Kubernetes 1.10 release, such as Promethus, Role-based access control, API aggregation, and more. By the end of this book, you’ll know everything you need to graduate from intermediate to advanced level of understanding Kubernetes.
Table of Contents (16 chapters)

Creating a multinode cluster using kubeadm

In this section, I'll introduce you to kubeadm, the recommended tool for creating Kubernetes clusters on all environments. It is still under active development, but it is the way to go because it is part of Kubernetes, and will always embody best practices. To make it accessible for the entire cluster, we will base it on VMs. This section is for readers who want a hands-on experience of deploying a multi-node cluster.

Setting expectations

Before embarking on this journey, I want to make it clear that it might not be a smooth ride. kubeadm has a difficult task: It has to follow the evolution of Kubernetes itself, which is a moving target. As a result, it is not always stable...