Understanding and Combining GKE Autoscaling Strategies Reviews

18905 reviews

Reema A. · Reviewed about 3 years ago

Vins S. · Reviewed about 3 years ago

Task 8 issues: Fix: apiVersion: scheduling.k8s.io/v1beta1 to apiVersion: scheduling.k8s.io/v1 Ref: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#priorityclass-v122 Cannot schedule pods: Preemption is not helpful for scheduling. PodUnschedulable Reason Cannot schedule pods: Preemption is not helpful for scheduling. Learn more Source overprovisioning-6785bcc4d7-gttkc

Bruno L. · Reviewed about 3 years ago

In step 1 of the last section the contents of the pause-pod.yaml file are missing. I had to scour the internet for the commands and build the yaml file myself.

Sam A. · Reviewed about 3 years ago

Agustin S. · Reviewed about 3 years ago

Jose Daniel U. · Reviewed about 3 years ago

CHIHABEDDINE F. · Reviewed about 3 years ago

Vishal K. · Reviewed about 3 years ago

I could not finish point 8 due to deprecated API error: resource mapping not found for name: "overprovisioning" namespace: "" from "pause-pod.yaml": no matches for kind "PriorityClass" in version "scheduling.k8s.io/v1beta1"

Francesca D. · Reviewed about 3 years ago

Phu V. · Reviewed about 3 years ago

Rajiv G. · Reviewed about 3 years ago

venkata jagadeesh k. · Reviewed about 3 years ago

Instructions should mention that if we have to wait before executing the next step. It unnecessary create panic in mind.

Pradip G. · Reviewed about 3 years ago

Herzam V. · Reviewed about 3 years ago

Anna T. · Reviewed about 3 years ago

Evandro V. · Reviewed about 3 years ago

Hemant S. · Reviewed about 3 years ago

David H. · Reviewed about 3 years ago

David C. · Reviewed about 3 years ago

nice

Mazza A. · Reviewed about 3 years ago

Rachid O. · Reviewed about 3 years ago

帅 刘. · Reviewed about 3 years ago

great lab,learnt a lot

Dilli C. · Reviewed about 3 years ago

Link L. · Reviewed about 3 years ago

unable to apply php-apache.yaml : returns The connection to the server localhost:8080 was refused - did you specify the right host or port?

Dinkar G. · Reviewed about 3 years ago

We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.