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

Observability practices

Now, let’s define what observability truly is by looking at logs, traces, and metrics. When you use tools such as Prometheus, you’re doing a piece of observability. When you use other tools such as or another log aggregator, you’re using another piece of observability.


Logging is aggregating and storing logged event messages written by programs and systems. As you can imagine, depending on how verbose the logs are set in an application, there will be a lot of events. A sysadmin’s favorite tool is a log because it literally shows everything and anything that could happen from an event’s perspective. However, it’s not efficient to simply comb through all of it with your eyes. Instead, using observability practices, you can send the logs to a log aggregator and ensure that a specific type of log that occurs can trigger an alert or some type of automation to go in and fix the issue.