menu

Optimize Costs for Google Kubernetes Engine: Challenge Lab

Acessar o laboratório

1264 Resenhas

Wahyu S. · Revisado há aproximadamente 8 horas

Omar M. · Revisado há 5 dias

Barbara S. · Revisado há 5 dias

Fabulous

MIHIR K. · Revisado há 5 dias

Ernesto C. · Revisado há 6 dias

BOLISHETTY R. · Revisado há 6 dias

Victson L. · Revisado há 7 dias

tanisha b. · Revisado há 7 dias

D R. · Revisado há 9 dias

Rhutuja S. · Revisado há 9 dias

lig g. · Revisado há 9 dias

Lee Chuan, G. · Revisado há 10 dias

Awesome

Nagamalli A. · Revisado há 10 dias

godd

Beverlee U. · Revisado há 10 dias

Sheetal A. · Revisado há 10 dias

Great quest and this challenge as well. Few things to fix in this challenge: 1. These paragraphs are confusing and they contradict each other with the values. Was the second paragraph supposed to mention another deployment? ``` Apply horizontal pod autoscaling to your frontend deployment in order to handle the traffic surge. Scale based off a target cpu percentage of 50 and set the pod scaling between 1 minimum and 13 maximum. Of course, you want to make sure that users won’t experience downtime while the deployment is scaling. To make sure the scaling action occurs without downtime, set the deployment to scale with a target cpu percentage of 50%. This should allow plenty of space to handle the load as the autoscaling occurs. Set the deployment to scale between 1 minimum and 10 maximum pods. ``` 2. loadgenerator doesn't contain `loadgen.sh` file in its "main" container in image version v0.2.4 so the given command to run load tests fails. But rolling back image's version to v0.2.3 fixed the issue for me.

Pavel K. · Revisado há 11 dias

Ehsan A. · Revisado há 12 dias

Holger S. · Revisado há 13 dias

Joel B. · Revisado há 14 dias

Holger S. · Revisado há 14 dias

Majhhol A. · Revisado há 15 dias

Tyler J. · Revisado há 15 dias

thanks

kejh i. · Revisado há 15 dias

thanks

kejh i. · Revisado há 16 dias

Krishna P. · Revisado há 17 dias