Delve into advanced Kubernetes features like monitoring, alerting, logging, and auto-scaling. Gain insights into creating resilient, self-adaptive clusters and applications with minimal manual intervention.

The world of DevOps has exploded with the help of technologies like Kubernetes and Docker.  
In this course, you will learn about more advanced Kubernetes features such as monitoring, alerting, logging, and scaling - crucial concepts for any DevOps professional. You will learn how to monitor clusters, how to send alerts when potential issues arise, and how to query the whole system’s metrics and logs. 
By the end of this course, you will have the required knowledge to make your clusters and applications truly dynamic and resilient, so that they require minimal manual involvement and are self-adaptive.

Advanced Kubernetes Techniques: Monitoring, Logging, Auto-Scaling

# Pulling the code

We'll continue using definitions from the [vfarcic/k8s-specs](https://github.com/vfarcic/k8s-specs) repository. To be on the safe side, we'll pull the latest version first.

> 🔍 All the commands from this chapter are available in the <a href="https://gist.github.com/9fcc214b5b7c380aef2feed3f686c08f">03-monitor.sh</a> Gist.

```shell
cd k8s-specs

git pull
```

## Additional necessary things

In this chapter, we'll need a few things that were not requirements before, even though you have probably already used them.

We'll start using UIs so we'll need **NGINX Ingress Controller** that will route traffic from outside the cluster. We'll also need the environment variable **LB_IP** with the IP through which we can access worker nodes. We'll use it to configure a few Ingress resources.

# Gists and specifications

Choose the flavor you want and run the commands from its `.sh` file to create the cluster and the required specifications needed in this chapter. Due to new requirements (Ingress and `LB_IP`), all the cluster setup **Gists** are new.

> **NOTE:** In the end, you will see a command to `DELETE` the cluster too. Don't execute that command. Use the `DELETE` command only when you need to delete the cluster, preferably at the end of the chapter. 

> # A note to Docker for Desktop users
> 🔍 You'll notice <code>LB_IP=[...]</code> command at the end of the Gist. You'll have to replace <code>[...]</code> with the IP of your cluster. Probably the easiest way to find it is through the <code>ifconfig</code> command. Just remember that it cannot be <code>localhost</code>, but the IP of your laptop (e.g., <code>192.168.0.152</code>).

> # A note to minikube and Docker  for Desktop users
> 🔍 We have to increase memory to 3GB. Please have that in mind in case you were planning only to skim through the <b>Gist</b> that matches your Kubernetes flavor.



This lesson focuses on creating a cluster and the necessary requirements and gists for this chapter.

Before Getting Started

Autoscaling Deployments and StatefulSets

Auto-Scaling Nodes Of A Kubernetes Cluster

Collecting and Querying Metrics and Sending Alerts

Debugging Issues Discovered Through Metrics and Alerts

Extending HorizontalPodAutoscaler With Custom Metrics

Visualizing Metrics And Alerts

Collecting And Querying Logs

Conclusion

Create a Cluster

Pulling the code #

Additional necessary things