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

Monitoring Kubernetes resources

In the previous section, you learned all about monitoring from an overall observability perspective, in particular setting up certain tools and ensuring that they work for you. Now it’s time to go underneath the Kubernetes hood and begin to think about what can be monitored from a resource perspective. Remember, a Kubernetes resource (sometimes called an object) can be anything, from Services, to Ingress controllers, to Pods. Because of that, there’s a lot to monitor.

Think about it from this perspective. You’re running a Pod that’s running a container inside of the Pod. The Pod itself is running great. The container image works, with no CPU or memory issues, and all of the events state that the Pod is up and running successfully. However, there’s a problem – the binary (the app entry point) running inside of the container may be down, or not working as expected. Because of this, you need a way to truly see...