AK8S-11 Configuring Pod Autoscaling and NodePools Reviews

The activities in this lab does not relate to the topics that were covered in the previous lessons (Nodes AutoScaling using gcloud and GCP console)

Ayman Q. · Reviewed about 6 years ago

Nice

David G. · Reviewed about 6 years ago

Jesus I. · Reviewed about 6 years ago

Víctor M. · Reviewed about 6 years ago

alex k. · Reviewed about 6 years ago

Chung W. · Reviewed about 6 years ago

Bibhuti N. · Reviewed about 6 years ago

Alex L. · Reviewed about 6 years ago

Jiahao J. · Reviewed about 6 years ago

Yinghao L. · Reviewed about 6 years ago

Xiaobo L. · Reviewed about 6 years ago

Momoi H. · Reviewed about 6 years ago

Murilo Z. · Reviewed about 6 years ago

Amar Y. · Reviewed about 6 years ago

Michel Rafael P. · Reviewed about 6 years ago

Carlos R. · Reviewed about 6 years ago

Denys N. · Reviewed about 6 years ago

Pokutnia D. · Reviewed about 6 years ago

andrei t. · Reviewed about 6 years ago

Fredrik J. · Reviewed about 6 years ago

Sharadraj H. · Reviewed about 6 years ago

Initial cluster was too weak to accomplish lab tasks. When I scaled load deployment up to 4 replicas, 3 additional pods for web deployment were not able to be scheduled. I got the following errors: "Pod errors: Unschedulable", "0/2 nodes are available: 2 Insufficient cpu". Only after I scaled load deployment to 0 replicas, web deployment pods were scheduled properly. That is why logically it would be much better to do task 3 at the beginning of the lab, as cluster with 4 nodes was able to schedule all pods correctly. The second bad aspect is connected to theoretical part. We don't have enough theory about settings in spec.containers.resources.limits section. And we don't have knowledge about how to monitor resources consumption properly. But this information is crucial for understanding how autoscaling works.

Alexey I. · Reviewed about 6 years ago

Akilan S. · Reviewed about 6 years ago

Mariia K. · Reviewed about 6 years ago

Andrii P. · Reviewed about 6 years ago