AK8S-11 Configurer l'autoscaling des pods et des pools de nœuds avis
6534 avis
Anastasia D. · Examiné il y a environ 5 ans
Fabio C. · Examiné il y a environ 5 ans
i
Camilo A. · Examiné il y a environ 5 ans
Manuel I. · Examiné il y a environ 5 ans
Camilo A. · Examiné il y a environ 5 ans
The hpa could not get the cpu metrics of the pods of my web deployment
Vincent M. · Examiné il y a environ 5 ans
Krishnapriya V. · Examiné il y a environ 5 ans
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. · Examiné il y a environ 5 ans
"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. · Examiné il y a environ 5 ans
"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. · Examiné il y a environ 5 ans
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. · Examiné il y a environ 5 ans
Francesco S. · Examiné il y a environ 5 ans
Damian S. · Examiné il y a environ 5 ans
Magdalena K. · Examiné il y a environ 5 ans
Ernest C. · Examiné il y a environ 5 ans
pods where pending to be created.
Marcus M. · Examiné il y a environ 5 ans
Ritesh T. · Examiné il y a environ 5 ans
creation failed because of not enough resources
Marcus M. · Examiné il y a environ 5 ans
Rassokhin S. · Examiné il y a environ 5 ans
Pilar G. · Examiné il y a environ 5 ans
Niranjan M. · Examiné il y a environ 5 ans
Victor G. · Examiné il y a environ 5 ans
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. · Examiné il y a environ 5 ans
Andreas D. · Examiné il y a environ 5 ans
Rana K. · Examiné il y a environ 5 ans
Nous ne pouvons pas certifier que les avis publiés proviennent de consommateurs qui ont acheté ou utilisé les produits. Les avis ne sont pas vérifiés par Google.