Understanding and Combining GKE Autoscaling Strategies Reviews

Sergio Enrique T. · Reviewed over 3 years ago

Pierre C. · Reviewed over 3 years ago

Bruno T. · Reviewed over 3 years ago

SHOAIB S. · Reviewed over 3 years ago

Caden N. · Reviewed over 3 years ago

Karwan S. · Reviewed over 3 years ago

Thoko M. · Reviewed over 3 years ago

Eduardo R. · Reviewed over 3 years ago

Some instructions need to be updated (reference to beta features which is no longer valid + some pdbs are missing for new system services)

Tomislav P. · Reviewed over 3 years ago

I got an error: resource mapping not found for name: "overprovisioning" namespace: "" from "pause-pod.yaml": no matches for kind "PriorityClass" in version "scheduling.k8s.io/v1beta1" which I fixed by replacing v1beta1 to v1

Martin M. · Reviewed over 3 years ago

Frédéric A. · Reviewed over 3 years ago

Faced with issue, k8s was provisioned without --runtime-config=scheduling.k8s.io/v1alpha1=true argument that leads to a problem on the latest challenge

Dmitry D. · Reviewed over 3 years ago

Easy

David M. · Reviewed over 3 years ago

Filippo F. · Reviewed over 3 years ago

Ricardo E. · Reviewed over 3 years ago

It needs to be checked, for pod pause it needs to change the apiVersion from scheduling.k8s.io/v1beta to scheduling.k8s.io/v1

Pau R. · Reviewed over 3 years ago

Sujay P. · Reviewed over 3 years ago

Jacek K. · Reviewed over 3 years ago

Sanan A. · Reviewed over 3 years ago

Mulkiah G. · Reviewed over 3 years ago

Dario B. · Reviewed over 3 years ago

no matches for kind "PriorityClass" in version "scheduling.k8s.io/v1beta1"

Jean-Jacques C. · Reviewed over 3 years ago

uable to create pause pod: error: resource mapping not found for name: "overprovisioning" namespace: "" from "pause-pod.yaml": no matches for kind "PriorityClass" in version "scheduling.k8s.io/v1beta1" ensure CRDs are installed first

Andras B. · Reviewed over 3 years ago

Luis C. · Reviewed over 3 years ago

Jameel M. · Reviewed over 3 years ago