关于“AK8S-11 Configuring Pod Autoscaling and NodePools”的评价

评论

Angel G. · 评论almost 5 years之前

Sridharur S. · 评论almost 5 years之前

lwj l. · 评论almost 5 years之前

hans W. · 评论almost 5 years之前

Vaibhav M. · 评论almost 5 years之前

Pieter-Jan S. · 评论almost 5 years之前

Rajesh A. · 评论almost 5 years之前

explained much more to me than the videos

Michael M. · 评论almost 5 years之前

Tomasz A. · 评论almost 5 years之前

Nathan F. · 评论almost 5 years之前

It was good, buy I would like to try node autoscaling also.

Denis S. · 评论almost 5 years之前

Aleksandr S. · 评论almost 5 years之前

Occasional inaccuracy in text.

Bingning D. · 评论almost 5 years之前

harsh s. · 评论almost 5 years之前

Yaron S. · 评论almost 5 years之前

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

Napasin H. · 评论almost 5 years之前

Problem with HPA unable to compute the replica count - missing request for cpu. To fix this issue the web.yaml needed to be updated with the cpu requests. Per documentation: If you want to autoscale based on a resource's utilization as a percentage, you must specify requests for that resource. If you do not specify requests, you can autoscale based only on the absolute value of the resource's utilization, such as milliCPUs for CPU utilization. === Example Error Output === Metrics: ( current / target ) resource cpu on pods (as a percentage of request): <unknown> / 1% Min replicas: 1 Max replicas: 4 Deployment pods: 1 current / 0 desired Conditions: Type Status Reason Message ---- ------ ------ ------- AbleToScale True SucceededGetScale the HPA controller was able to get the target's current scale ScalingActive False FailedGetResourceMetric the HPA was unable to compute the replica count: missing request for cpu Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedComputeMetricsReplicas 47s (x12 over 3m38s) 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 32s (x13 over 3m38s) horizontal-pod-autoscaler missing request for cpu

Ryu K. · 评论almost 5 years之前

Joosung J. · 评论almost 5 years之前

Srikar M. · 评论almost 5 years之前

Jakub M. · 评论almost 5 years之前

Alex d. · 评论almost 5 years之前

No esta descrito bien el enlace simbolico no se puede obetener la metrica del CPU

Christopher C. · 评论almost 5 years之前

Vivek C. · 评论almost 5 years之前

HPA based exercise is broken, CPU request need to be mentioned for HPA to fetch metrics from CPU

Dwarakesh V. · 评论almost 5 years之前

Thomas (. · 评论almost 5 years之前

我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。