AK8S-11 Configuring Pod Autoscaling and NodePools Ulasan
6534 ulasan
Anastasia D. · Diulas sekitar 5 tahun lalu
Fabio C. · Diulas sekitar 5 tahun lalu
i
Camilo A. · Diulas sekitar 5 tahun lalu
Manuel I. · Diulas sekitar 5 tahun lalu
Camilo A. · Diulas sekitar 5 tahun lalu
The hpa could not get the cpu metrics of the pods of my web deployment
Vincent M. · Diulas sekitar 5 tahun lalu
Krishnapriya V. · Diulas sekitar 5 tahun lalu
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. · Diulas sekitar 5 tahun lalu
"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. · Diulas sekitar 5 tahun lalu
"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. · Diulas sekitar 5 tahun lalu
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. · Diulas sekitar 5 tahun lalu
Francesco S. · Diulas sekitar 5 tahun lalu
Damian S. · Diulas sekitar 5 tahun lalu
Magdalena K. · Diulas sekitar 5 tahun lalu
Ernest C. · Diulas sekitar 5 tahun lalu
pods where pending to be created.
Marcus M. · Diulas sekitar 5 tahun lalu
Ritesh T. · Diulas sekitar 5 tahun lalu
creation failed because of not enough resources
Marcus M. · Diulas sekitar 5 tahun lalu
Rassokhin S. · Diulas sekitar 5 tahun lalu
Pilar G. · Diulas sekitar 5 tahun lalu
Niranjan M. · Diulas sekitar 5 tahun lalu
Victor G. · Diulas sekitar 5 tahun lalu
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. · Diulas sekitar 5 tahun lalu
Andreas D. · Diulas sekitar 5 tahun lalu
Rana K. · Diulas sekitar 5 tahun lalu
Kami tidak dapat memastikan bahwa ulasan yang dipublikasikan berasal dari konsumen yang telah membeli atau menggunakan produk terkait. Ulasan tidak diverifikasi oleh Google.