Dalton Hubble 20b76d6e00 Roll instance template changes to worker managed instance groups ... * When a worker managed instance group's (MIG) instance template changes (including machine type, disk size, or Butane snippets but excluding new AMIs), use Google Cloud's rolling update features to ensure instances match declared state * Ignore new AMIs since Fedora CoreOS and Flatcar Linux nodes already auto-update and reboot themselves * Rolling updates will create surge instances, wait for health checks, then delete old instances (0 unavilable instances) * Instances are replaced to ensure new Ignition/Butane snippets are respected * Add managed instance group autohealing (i.e. health checks) to ensure new instances' Kubelet is running Renames * Name apiserver and kubelet health checks consistently * Rename MIG from `${var.name}-worker-group` to `${var.name}-worker` Rel: https://cloud.google.com/compute/docs/instance-groups/rolling-out-updates-to-managed-instance-groups		2022-08-14 13:06:53 -07:00
..
fedora-coreos/kubernetes	Roll instance template changes to worker managed instance groups	2022-08-14 13:06:53 -07:00
flatcar-linux/kubernetes	Roll instance template changes to worker managed instance groups	2022-08-14 13:06:53 -07:00