We can see that its targeting our deployment, and that CPU usage is currently at 0% of our 50% target that we specified earlier. Noobernetes-hpa Deployment/noobernetes /50% 1 10 1 2m23s NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE If you’d like to just use a pre-tweaked file, you can find it at applications/metrics-server/metrics.yaml The official repository provides a quick way to install the metrics server, but we’ll need to tweak it a little bit to get it to work with Docker for Mac It is generally installed by default in most Kubernetes clusters, however with Docker for Mac we’re going to have to install it ourselves. The metrics-server provides information about the CPU and Memory Usage of containers running in your cluster. (optional) You should have the watch command installed.You should have the noobernetes deployment and service applied to your Kubernetes cluster.For example, if you have one pod serving traffic and it’s CPU usage begins to blow up, Kubernetes can automatically create more pods to handle work for you! In this section we’re going to look at a horizontal pod autoscaler and watch as it scales our application. One exciting feature of Kubernetes is the ability to horizontally scale a workload. Horizontal Pod Autoscaling | Noobernetes Noobernetes Kubernetes tutorials for Noobs View on GitHub Horizontal Pod Autoscaling Introduction
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |