Book Image

50 Kubernetes Concepts Every DevOps Engineer Should Know

By : Michael Levan
Book Image

50 Kubernetes Concepts Every DevOps Engineer Should Know

By: Michael Levan

Overview of this book

Kubernetes is a trending topic among engineers, CTOs, CIOs, and other technically sound professionals. Due to its proliferation and importance for all cloud technologies, DevOps engineers nowadays need a solid grasp of key Kubernetes concepts to help their organization thrive. This book equips you with all the requisite information about how Kubernetes works and how to use it for the best results. You’ll learn everything from why cloud native is important to implementing Kubernetes clusters to deploying applications in production. This book takes you on a learning journey, starting from what cloud native is and how to get started with Kubernetes in the cloud, on-premises, and PaaS environments such as OpenShift. Next, you’ll learn about deploying applications in many ways, including Deployment specs, Ingress Specs, and StatefulSet specs. Finally, you’ll be comfortable working with Kubernetes monitoring, observability, and security. Each chapter of 50 Kubernetes Concepts Every DevOps Engineer Should Know is built upon the previous chapter, ensuring that you develop practical skills as you work through the code examples in GitHub, allowing you to follow along while giving you practical knowledge. By the end of this book, you’ll be able to implement Kubernetes in any environment, whether it’s an existing environment, a greenfield environment, or your very own lab running in the cloud or your home.
Table of Contents (14 chapters)
1
Part 1: First 20 Kubernetes Concepts – In and Out of the Cloud
6
Part 2: Next 15 Kubernetes Concepts – Application Strategy and Deployments
9
Part 3: Final 15 Kubernetes Concepts – Security and Monitoring

AWS EKS

When you’re using AWS, you have a few options to choose from when using containers and Kubernetes:

  • EKS
  • EKS with Fargate profiles
  • Elastic Container Service (ECS)

EKS is the primary way to run Kubernetes workloads inside AWS. If you don’t want to go the Kubernetes route but still want scalability, you can use ECS, which gives you the ability to scale and create reliable microservices but without Kubernetes.

As with AKS, you don’t have to worry about managing the Control Plane or API Server when it comes to EKS. You only have to worry about managing and scaling worker nodes. If you want to, you can even take it a step further and implement EKS with Fargate profiles, which abstracts the Control Plane or API Server and the worker nodes to ensure a fully serverless Kubernetes experience.

As with AKS, in the following few sections, you’re going to learn how to create an EKS cluster manually first. After that, you’ll take...