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

# Version Of `HorizontalPodAutoscaler`

Please note that we used `autoscaling/v2beta1` version of `HorizontalPodAutoscaler`. At the time of this writing, only `v1` is stable and production-ready. However, `v1` is so limited (it can use only CPU metrics) that it's almost useless. The Kubernetes community is working on new (`v2`) `HPA` for a while and, in my experience, it works reasonably well. The main problem is not stability but potential changes in the API that might not be backward compatible. If you're running Kubernetes 1.11+, you might want to switch to `v2beta2`. If you do so, remember that you'll need to make a few changes to the `HPA` definitions we explored. The logic is still the same, and it behaves in the same way. The only visible difference is in the API.

> 🔍 Please consult <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.12/#horizontalpodautoscaler-v2beta2-autoscaling">HorizontalPodAutoscaler v2beta2 autoscaling</a> for the changes from <code>v2beta1</code> we used to <code>v2beta2</code> available in Kubernetes 1.11+

# Remove the previous resources

That's it. Destroy the cluster if it's dedicated to this chapter, or keep it if it's not or if you're planning to jump to the next chapter right away. If you're keeping it, please delete the `go-demo-5` resources by executing the commands that follow.

```shell
helm delete go-demo-5 \
    --namespace go-demo-5

kubectl delete ns go-demo-5
```

In this lesson, we will revise and test the concepts we have learned in this chapter through a small quiz.

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

Revise and Test the Concepts

Version Of `HorizontalPodAutoscaler` #

Revise and Test the Concepts

Version Of HorizontalPodAutoscaler #

Version Of `HorizontalPodAutoscaler` #