Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roll instance template changes to worker managed instance groups #1207

Merged
merged 1 commit into from
Aug 15, 2022

Conversation

dghubble
Copy link
Member

@dghubble dghubble commented Aug 14, 2022

  • When a worker managed instance group's (MIG) instance template changes (including worker_type, disk_size, preemptible, or Butane worker_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

* 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
@dghubble
Copy link
Member Author

May change this to health check kube-proxy instead of Kubelet before release

@dghubble dghubble merged commit 20b76d6 into main Aug 15, 2022
@dghubble dghubble deleted the google-rollouts branch August 15, 2022 04:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant