GKE Workload Optimization Reviews

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

Lennin A. · Reviewed yaklaşık 2 yıl ago

YUQUAN W. · Reviewed yaklaşık 2 yıl ago

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. · Reviewed yaklaşık 2 yıl ago

selvam p. · Reviewed yaklaşık 2 yıl ago

Ratan v. · Reviewed yaklaşık 2 yıl ago

Jonny N. · Reviewed yaklaşık 2 yıl ago

Akshay L. · Reviewed yaklaşık 2 yıl ago

Ka Yin C. · Reviewed yaklaşık 2 yıl ago

Alex B. · Reviewed yaklaşık 2 yıl ago

youssef o. · Reviewed yaklaşık 2 yıl ago

Igor M. · Reviewed yaklaşık 2 yıl ago

Kris H. · Reviewed yaklaşık 2 yıl ago

Leticia S. · Reviewed yaklaşık 2 yıl ago

NISHU T. · Reviewed yaklaşık 2 yıl ago

Erion B. · Reviewed yaklaşık 2 yıl ago

oguzhan.toy o. · Reviewed yaklaşık 2 yıl ago

Aliaksei H. · Reviewed yaklaşık 2 yıl ago

Ruben O. · Reviewed yaklaşık 2 yıl ago

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. · Reviewed yaklaşık 2 yıl ago

Joko S. · Reviewed yaklaşık 2 yıl ago

Russ S. · Reviewed yaklaşık 2 yıl ago

ABHISHEK K. · Reviewed yaklaşık 2 yıl ago

RANA SUJEET S. · Reviewed yaklaşık 2 yıl ago

Paweł G. · Reviewed yaklaşık 2 yıl ago

Irfan M. · Reviewed yaklaşık 2 yıl ago