AK8S-11 Configurar o escalonamento automático de pods e pools de nós avaliações

Anastasia D. · Revisado há about 5 years

Fabio C. · Revisado há about 5 years

i

Camilo A. · Revisado há about 5 years

Manuel I. · Revisado há about 5 years

Camilo A. · Revisado há about 5 years

The hpa could not get the cpu metrics of the pods of my web deployment

Vincent M. · Revisado há about 5 years

Krishnapriya V. · Revisado há about 5 years

This lab contains multiple bugs and cannot be finished correctly. I thoght of troubleshooting but dont wanna get my account blocked, Please fix this since coursera class needs this lab to be completed. Errors First: web node fails to report cpu usage thus autoscalling cannot be achieved. Warning FailedComputeMetricsReplicas 6m23s (x12 over 9m13s) horizontal-pod-autoscaler failed to compute desired number of replicas based on listed metrics for Deployment/default/web: invalid metrics (1 invalid out of 1), first error is: failed to get cpu utilization: missing request for cpu Warning FailedGetResourceMetric 4m3s (x21 over 9m13s) horizontal-pod-autoscaler missing request for cpu Second: When trying the pooling part, resources related error arise. message: "Instance 'gke-standard-cluster-1-temp-pool-1-76d7d0fc-3xrg' creation failed: The zone 'projects/qwiklabs-gcp-01-1855828413e8/zones/us-central1-a' does not have enough resources available to fulfill the request. '(resource type:compute)'.">, <StatusCondition

Luis F. · Revisado há about 5 years

"After a few minutes, inspect the HorizontalPodAutoscaler again. kubectl get hpa The autoscaler has increased the web deployment to four replicas." The steps above did NOT work even after almost 7-9 mins!! Also, why suddenly not give instructions on how to edit the yaml file? You're providing every step in every lab and then suddenly just say edit the yaml file with no steps provided on how to edit. I managed to find the yaml file and edited it but it failed. Instructions "Control scheduling with taints and tolerations" are horrible! Please update them properly, have to redo the lab hoping it'll work next time. 2nd attempt: cloud shell disconnected multiple times! Had to login twice to reconnect.

Rupa K. · Revisado há about 5 years

"After a few minutes, inspect the HorizontalPodAutoscaler again. kubectl get hpa The autoscaler has increased the web deployment to four replicas." The steps above did NOT work even after almost 7-9 mins!! Also, why suddenly not give instructions on how to edit the yaml file? You're providing every step in every lab and then suddenly just say edit the yaml file with no steps provided on how to edit. I managed to find the yaml file and edited it but it failed. Instructions "Control scheduling with taints and tolerations" are horrible! Please update them properly, have to redo the lab hoping it'll work next time.

Rupa K. · Revisado há about 5 years

Error in the first web.yaml. It misses some properties: requests: cpu: "250" (or any other value) otherwise autoscaler won't be able to fetch the cpu metric

Fabien L. · Revisado há about 5 years

Francesco S. · Revisado há about 5 years

Damian S. · Revisado há about 5 years

Magdalena K. · Revisado há about 5 years

Ernest C. · Revisado há about 5 years

pods where pending to be created.

Marcus M. · Revisado há about 5 years

Ritesh T. · Revisado há about 5 years

creation failed because of not enough resources

Marcus M. · Revisado há about 5 years

Rassokhin S. · Revisado há about 5 years

Pilar G. · Revisado há about 5 years

Niranjan M. · Revisado há about 5 years

Victor G. · Revisado há about 5 years

Could not get HPA to ever work, always had an <Unknown> CPU status even though metric server was running on the cluster. My pods never autoscaled. Looks like the Taints forces the pod to never run on cluster. I get the same describe output but my pods are never scheduled. stuck in pending. perhaps version issues

Ryan Z. · Revisado há about 5 years

Andreas D. · Revisado há about 5 years

Rana K. · Revisado há about 5 years