Otimização de cargas de trabalho do GKE avaliações

Brando P. · Revisado há almost 3 years

Andrej O. · Revisado há almost 3 years

the draining demo did not work even after setting up the disruption budgets.

Lennin A. · Revisado há almost 3 years

YUQUAN W. · Revisado há almost 3 years

On the last step, I see 5 available pods and not 4 as stated in the lab: Replicas: 5 desired | 5 updated | 5 total | 5 available | 0 unavailable

Sandro G. · Revisado há almost 3 years

selvam p. · Revisado há almost 3 years

Ratan v. · Revisado há almost 3 years

Jonny N. · Revisado há almost 3 years

Akshay L. · Revisado há almost 3 years

Ka Yin C. · Revisado há almost 3 years

Alex B. · Revisado há almost 3 years

youssef o. · Revisado há almost 3 years

Igor M. · Revisado há almost 3 years

Kris H. · Revisado há almost 3 years

Leticia S. · Revisado há almost 3 years

NISHU T. · Revisado há almost 3 years

Erion B. · Revisado há almost 3 years

oguzhan.toy o. · Revisado há almost 3 years

Aliaksei H. · Revisado há almost 3 years

Ruben O. · Revisado há almost 3 years

The instructions are missing the login step to the GKE cluster: $ gcloud container clusters get-credentials test-cluster if you don't do so, you'll get this error: "error: You must be logged in to the server (the server has asked for the client to provide credentials)" Also, in the last section, you need to include the flag: "--delete-emptydir-data" The final command would be: $ for node in $(kubectl get nodes -l cloud.google.com/gke-nodepool=default-pool -o=name); do kubectl drain --force --ignore-daemonsets --delete-emptydir-data --grace-period=10 "$node"; done

Josue V. · Revisado há almost 3 years

Joko S. · Revisado há almost 3 years

Russ S. · Revisado há almost 3 years

ABHISHEK K. · Revisado há almost 3 years

RANA SUJEET S. · Revisado há almost 3 years