Book Image

The Kubernetes Book

By : Nigel Poulton, Pushkar Joglekar
Book Image

The Kubernetes Book

By: Nigel Poulton, Pushkar Joglekar

Overview of this book

Kubernetes is the leading orchestrator of cloud-native apps. With knowledge of how to work with Kubernetes, you can easily deploy and manage applications on the cloud or in your on-premises data center. The book begins by introducing you to Kubernetes and showing you how to install it. You’ll learn how to use Kubernetes Services and bring stable and reliable networking to apps that are deployed on Kubernetes. You'll delve deep into the powerful storage subsystem of Kubernetes and learn how to leverage the variety of external storage backends in your applications. As the book progresses, it shows you how to use features such as DaemonSets, Helm, and RBAC to enhance your Kubernetes applications. You'll explore the six categories of identifying vulnerabilities and look at a few ways to prevent and mitigate them. You'll also look at ways to secure the software delivery pipeline by discussing some image-related best practices. The book ends by sharing with you some resources that’ll help take your Kubernetes knowledge to the next level. By the end of the book, you’ll have the confidence and skills to leverage all the features of Kubernetes to develop scalable applications.
Table of Contents (23 chapters)
Free Chapter
1
Chapter 1
3
Chapter 2
5
Chapter 3
7
Chapter 4
9
Chapter 5
11
Chapter 6
13
Chapter 7
15
Chapter 8
17
Chapter 9
19
Chapter 10
21
Chapter 11

Infrastructure and Networking

In this section, we'll look at some of the ways in which we can isolate workloads.

We'll start at the cluster level, switch to the runtime level, and then look outside the cluster at supporting infrastructure, such as network firewalls.

Cluster-Level Workload Isolation

Cutting straight to the chase, Kubernetes does not support secure multi-tenant clusters. The only cluster-level security boundary in Kubernetes is the cluster itself.

Let's look a bit closer...

The only way to divide a Kubernetes cluster is by creating namespaces. A Kubernetes namespace is not the same as a Linux kernel namespace. It is a logical partition of a single Kubernetes cluster. In fact, it's little more than a way of grouping resources and applying things such as:

  • Limits
  • Quotas
  • RBAC rules
  • More...

The take-home point is that Kubernetes namespaces cannot guarantee that a Pod in one namespace will not impact a Pod in another...