Bitzu

Associate Cloud Engineer ยท Operating GKE clusters

What is a node pool and what do you manage in Standard vs Autopilot?

Adding, editing and deleting node pools, autoscaling a node pool, upgrades and surge settings, machine types per pool, Autopilot vs Standard responsibilities.

Key points

  • A node pool is a set of nodes sharing one configuration (machine type, disk, upgrade settings).
  • In Standard you create, resize, autoscale, upgrade and delete pools yourself: gcloud container node-pools create/update/delete.
  • Use separate pools for different machine types.
  • In Autopilot, Google manages the nodes and you only declare Pod requests.

Source: https://docs.cloud.google.com/kubernetes-engine/docs/how-to/node-pools

Practice questions

Single choice

Which command adds a node pool to an existing Standard cluster?

  1. gcloud container clusters create-pool
  2. gcloud container node-pools add
  3. gcloud container node-pools create
  4. gcloud container clusters create --append
Show answer

Answer: C. gcloud container node-pools create

node-pools create is the dedicated command. clusters create would make a new cluster, and the other two are not gcloud verbs for this task.

Select all that apply

Which tasks are your responsibility in a Standard cluster?

  1. Choosing the machine type of each node pool
  2. Configuring node pool autoscaling limits
  3. Choosing the node upgrade strategy and surge settings
  4. Patching and operating the control plane
  5. Letting Google decide node count from Pod requests alone
Show answer

Answer: A. Choosing the machine type of each node pool, B. Configuring node pool autoscaling limits, C. Choosing the node upgrade strategy and surge settings

In Standard you pick machine types, configure autoscaling and choose upgrade behavior per pool. Billing by Pod requests is an Autopilot model, and the control plane is operated by Google in both modes.

True or false

By default, deleting a node pool waits for PodDisruptionBudgets to be honored.

Show answer

Answer: False

False. By default GKE does not respect PodDisruptionBudgets when a node pool is deleted; you must opt in with --respect-pdb-during-node-pool-deletion on the pool.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More Associate Cloud Engineer topics in this module