Book Image

Introduction to DevOps with Kubernetes

By : Onur Yılmaz, Süleyman Akba≈ü
Book Image

Introduction to DevOps with Kubernetes

By: Onur Yılmaz, Süleyman Akba≈ü

Overview of this book

Kubernetes and DevOps are the two pillars that can keep your business at the top by ensuring high performance of your IT infrastructure. Introduction to DevOps with Kubernetes will help you develop the skills you need to improve your DevOps with the power of Kubernetes. The book begins with an overview of Kubernetes primitives and DevOps concepts. You'll understand how Kubernetes can assist you with overcoming a wide range of real-world operation challenges. You will get to grips with creating and upgrading a cluster, and then learn how to deploy, update, and scale an application on Kubernetes. As you advance through the chapters, you’ll be able to monitor an application by setting up a pod failure alert on Prometheus. The book will also guide you in configuring Alertmanager to send alerts to the Slack channel and trace down a problem on the application using kubectl commands. By the end of this book, you’ll be able to manage the lifecycle of simple to complex applications on Kubernetes with confidence.
Table of Contents (11 chapters)

Monitoring

In the previous chapter, Troubleshooting Applications in Kubernetes, we explored ways to troubleshoot our applications quickly in the event of a problem. Now we're moving one step further in detecting any potential problems before they occur with the help of monitoring, which is about observing and determining the behavior of a system.

Nowadays, companies need to ensure high levels of customer satisfaction in order to stay competitive in the market. Particularly for websites, it is important to be functional and provide an excellent service 24/7. In spite of this, many companies still embrace a reactive approach in order to tackle any issues that may occur; that is, they wait for problems to occur before attempting to tackle and fix them. This causes system downtime and can lead to customer frustration.

Formerly, the source code of an application was mostly static; that's why sophisticated tools were not necessary to monitor applications in real time. Instead...