Configuring Pod Autoscaling and NodePools Reviews

Tomasz P. · Reviewed about 2 years ago

JOSH ATHAN Y. · Reviewed about 2 years ago

Gustavo O. · Reviewed about 2 years ago

Daren C. · Reviewed about 2 years ago

Daniel Alexander F. · Reviewed about 2 years ago

Lasse W. · Reviewed about 2 years ago

Yang L. · Reviewed about 2 years ago

JULIENNE BEATRICE B. · Reviewed about 2 years ago

Diosemir I. · Reviewed about 2 years ago

Dominik L. · Reviewed about 2 years ago

Maushumee V. · Reviewed about 2 years ago

Vitaliy V. · Reviewed about 2 years ago

Роман Б. · Reviewed about 2 years ago

MOGHAL M. · Reviewed about 2 years ago

Gregorio P. · Reviewed about 2 years ago

Israel Rudyard F. · Reviewed about 2 years ago

MOGHAL M. · Reviewed about 2 years ago

Simon G. · Reviewed about 2 years ago

Shrikant K. · Reviewed about 2 years ago

Vishal K. · Reviewed about 2 years ago

Judicious scope, meaningful examples. ---------- ERRATA [?] [1] > Task 3. Manage node pools > To deploy a new node pool with three preemptible VM instances, execute the following command: Why "three preemptible VM instances"? The instructions have us create two preemptible nodes. -- [2] > Control scheduling with taints and tolerations > 8. Get the list of Pods using the wide output format to show the nodes running the > This shows that the loadgen app is running only on default-pool nodes while the web app is running only the preemptible nodes in temp-pool-1. The output does not have the word "default-pool" for the loadgen app nodes. Example node name: "gke-standard-cluster-standard-cluster-fa8cc4cc-0z2w"

Zachariah V. · Reviewed about 2 years ago

Kevin E. · Reviewed about 2 years ago

Felipe J. · Reviewed about 2 years ago

Robert K. · Reviewed about 2 years ago

Arunkumar A. · Reviewed about 2 years ago