Understanding and Combining GKE Autoscaling Strategies Reviews

Callum C. · Reviewed over 2 years ago

mehdi p. · Reviewed over 2 years ago

sergio c. · Reviewed over 2 years ago

Navin S. · Reviewed over 2 years ago

Leonardo C. · Reviewed over 2 years ago

carsten P. · Reviewed over 2 years ago

Diwakar K. · Reviewed over 2 years ago

Gaëtan A. · Reviewed over 2 years ago

Rodrigo E. · Reviewed over 2 years ago

christopher a. · Reviewed over 2 years ago

Thien N. · Reviewed over 2 years ago

BOMMISETTY S. · Reviewed over 2 years ago

Shahril R. · Reviewed over 2 years ago

Nirmal P. · Reviewed over 2 years ago

better -- lots of specific commands, I would have not though of myself

Tim B. · Reviewed over 2 years ago

Matthew S. · Reviewed over 2 years ago

Leticia R. · Reviewed over 2 years ago

Completed

Gabriel P. · Reviewed over 2 years ago

Uchechukwu A. · Reviewed over 2 years ago

Kunal P. · Reviewed over 2 years ago

Ebj H. · Reviewed over 2 years ago

PRASHANTH.G.L G. · Reviewed over 2 years ago

Ayush K. · Reviewed over 2 years ago

There are some mistakes w.r.t. the previous CPU requests (it's 450, not 100 nor 400). Additionally, the 450 request is blocking the way to get another replica to get VPA to work. One needs to downscale manually anyways. Furthermore, the various upscaling behaviours are not exactly functioning in the way described. Finally, the lab is extra lengthy because of the time it takes to reconfigure the cluster and observe the changes. I suggest simplifying it. One could already run the cluster with autoscaler and NAP enabled. Oh, and cluster autoscaler is out of beta already. No need to configure it using the beta subcommand.

Radosław P. · Reviewed over 2 years ago