Book Image

Mastering Elastic Kubernetes Service on AWS

By : Malcolm Orr, Yang-Xin Cao (Eason)
5 (1)
Book Image

Mastering Elastic Kubernetes Service on AWS

5 (1)
By: Malcolm Orr, Yang-Xin Cao (Eason)

Overview of this book

Kubernetes has emerged as the de facto standard for container orchestration, with recent developments making it easy to deploy and handle a Kubernetes cluster. However, a few challenges such as networking, load balancing, monitoring, and security remain. To address these issues, Amazon EKS offers a managed Kubernetes service to improve the performance, scalability, reliability, and availability of AWS infrastructure and integrate with AWS networking and security services with ease. You’ll begin by exploring the fundamentals of Docker, Kubernetes, Amazon EKS, and its architecture along with different ways to set up EKS. Next, you’ll find out how to manage Amazon EKS, encompassing security, cluster authentication, networking, and cluster version upgrades. As you advance, you’ll discover best practices and learn to deploy applications on Amazon EKS through different use cases, including pushing images to ECR and setting up storage and load balancing. With the help of several actionable practices and scenarios, you’ll gain the know-how to resolve scaling and monitoring issues. Finally, you will overcome the challenges in EKS by developing the right skill set to troubleshoot common issues with the right logic. By the end of this Kubernetes book, you’ll be able to effectively manage your own Kubernetes clusters and other components on AWS.
Table of Contents (28 chapters)
1
Part 1: Getting Started with Amazon EKS
7
Part 2: Deep Dive into EKS
13
Part 3: Deploying an Application on EKS
20
Part 4: Advanced EKS Service Mesh and Scaling
24
Part 5: Overcoming Common EKS Challenges

Using EBS volumes with your application

Kubernetes has three main kinds that are used for persistent storage. The PersistentVolume (PV) represents the actual storage in the attached storage system, in our case, an EBS volume. The other components are a StorageClass (SC), which defines the characteristics of the storage, and a PersistentVolumeClaim (PVC), which represents a request for storage that is fulfilled by a PV based on an SC.

The reason a PVC exists is that different Pods may require different types of storage, for example, storage shared between many Pods or dedicated to just one. The PVC provides an abstraction between what a developer or DevOps engineer needs for their application and the type of storage provided by the cluster administrator.

The following diagram illustrates the relationship between an EBS volume, PV, PVC, and a Pod:

Figure 12.1 – EBS volumes

Figure 12.1 – EBS volumes

It’s important to know that an EBS volume is specific to a Region...