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

Upgrading nodes and their critical components

Simplifying the upgrade process is one of the key reasons for using managed node groups. If we want to upgrade a single worker node in an active cluster manually, we would need to perform the following actions:

  1. Add a new worker that can run the Pods that will be evicted from the node running the old version of the Kubernetes agents (kubelet, and so on) we are upgrading, if we want to maintain the overall cluster capacity (the overall number of worker nodes that can run active Pods) during the upgrade.
  2. Drain the Pods from the node we are working on and remove them from the scheduling process so that no new Pods are allocated.
  3. Upgrade the operating system binaries and apply patches if needed.
  4. Update and configure the Kubernetes agents (kubelet, and so on).
  5. Once the upgraded node has registered and is ready, add it back to the scheduler.
  6. Update any critical components such as kube-proxy, coreDNS, and so on.
...