Book Image

50 Kubernetes Concepts Every DevOps Engineer Should Know

By : Michael Levan
5 (1)
Book Image

50 Kubernetes Concepts Every DevOps Engineer Should Know

5 (1)
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)
Part 1: First 20 Kubernetes Concepts – In and Out of the Cloud
Part 2: Next 15 Kubernetes Concepts – Application Strategy and Deployments
Part 3: Final 15 Kubernetes Concepts – Security and Monitoring

Troubleshooting on-prem Kubernetes clusters

If you come from a systems administration/infrastructure background, troubleshooting Kubernetes clusters is going to come to you pretty naturally. At the end of the day, a Kubernetes cluster consists of servers, networking, infrastructure, and APIs, which are essentially what infrastructure engineers are working on day to day.

If you’re a developer, some of these concepts may be new to you, such as troubleshooting networks. However, you’ll be very familiar with a few troubleshooting techniques as well, such as looking at and analyzing logs.

The whole idea of troubleshooting a Kubernetes cluster is to look at two pieces:

  • The cluster itself
  • The Pods running inside the cluster

The cluster itself, including networking, servers, operating systems, and scalability, is going to be thought of from more of an infrastructure perspective, where something such as the Certified Kubernetes Administrator (CKA) comes...