Book Image

The DevOps 2.5 Toolkit

By : Viktor Farcic
Book Image

The DevOps 2.5 Toolkit

By: Viktor Farcic

Overview of this book

Building on The DevOps 2.3 Toolkit: Kubernetes, and The DevOps 2.4 Toolkit: Continuous Deployment to Kubernetes, Viktor Farcic brings his latest exploration of the Docker technology as he records his journey to monitoring, logging, and autoscaling Kubernetes. The DevOps 2.5 Toolkit: Monitoring, Logging, and Auto-Scaling Kubernetes: Making Resilient, Self-Adaptive, And Autonomous Kubernetes Clusters is the latest book in Viktor Farcic’s series that helps you build a full DevOps Toolkit. This book helps readers develop the necessary skillsets needed to be able to operate Kubernetes clusters, with a focus on metrics gathering and alerting with the goal of making clusters and applications inside them autonomous through self-healing and self-adaptation. Work with Viktor and dive into the creation of self-adaptive and self-healing systems within Kubernetes.
Table of Contents (9 chapters)
8
What Did We Do?

Alerting on latency-related issues

We'll use the go-demo-5 application to measure latency, so our first step is to install it.

 1  GD5_ADDR=go-demo-5.$LB_IP.nip.io
2 3 helm install \ 4 https://github.com/vfarcic/go-demo-5/releases/download/
0.0.1/go-demo-5-0.0.1.tgz \
5 --name go-demo-5 \ 6 --namespace go-demo-5 \ 7 --set ingress.host=$GD5_ADDR

We generated an address that we'll use as Ingress entry-point, and we deployed the application using Helm. Now we should wait until it rolls out.

 1  kubectl -n go-demo-5 \
 2      rollout status \
 3      deployment go-demo-5

Before we proceed, we'll check whether the application is indeed working correctly by sending an HTTP request.

 1  curl "http://$GD5_ADDR/demo/hello"

The output should be the familiar hello, world! message.

Now, let's see whether we can, for example, get the...