AK8S-11 Configuring Pod Autoscaling and NodePools のレビュー

Derzhanskaya Anastasia · 約5年前にレビュー済み

Cabras Fabio · 約5年前にレビュー済み

i

Alessandro Camillo Camilo · 約5年前にレビュー済み

Iaderosa Manuel · 約5年前にレビュー済み

Alessandro Camillo Camilo · 約5年前にレビュー済み

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

Mahe Vincent · 約5年前にレビュー済み

Veleeparambil Raghavan Krishnapriya · 約5年前にレビュー済み

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

F. Iniguez Luis · 約5年前にレビュー済み

"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.

Kramadhati Rupa · 約5年前にレビュー済み

"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.

Kramadhati Rupa · 約5年前にレビュー済み

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

Locquet Fabien · 約5年前にレビュー済み

Silletta Francesco · 約5年前にレビュー済み

Szwed Damian · 約5年前にレビュー済み

Kwiotek Magdalena · 約5年前にレビュー済み

Chan Ernest · 約5年前にレビュー済み

pods where pending to be created.

Marcus Marcus · 約5年前にレビュー済み

Talati Ritesh · 約5年前にレビュー済み

creation failed because of not enough resources

Marcus Marcus · 約5年前にレビュー済み

Stanislav Rassokhin · 約5年前にレビュー済み

Garcia Vicente Pilar · 約5年前にレビュー済み

Mandal Niranjan · 約5年前にレビュー済み

Garcia Victor · 約5年前にレビュー済み

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

Zambrotta Ryan · 約5年前にレビュー済み

Durst Andreas · 約5年前にレビュー済み

Karmakar Rana · 約5年前にレビュー済み