Marques Johansson

@recipedude 8192/8191 can actually be derived from the image min size, (but should likely be padded with a few gb) https://www.terraform.io/docs/providers/linode/d/image.html ```hcl data "linode_image" "k8_master" { id = "linode/containerlinux" }...

This could be `pod-eviction-timeout` https://kubernetes.io/docs/concepts/architecture/nodes/#condition or taint-based eviction policies: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/#taint-based-evictions

I'm adding another context hint on this topic, Non-Graceful shutdowns. * https://kubernetes.io/blog/2022/05/20/kubernetes-1-24-non-graceful-node-shutdown-alpha/ * https://kubernetes.io/docs/concepts/architecture/nodes/#non-graceful-node-shutdown * https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/2268-non-graceful-shutdown/README.md I don't see any conversations about how a cloud-provider implementation would be expected to...

Once complete, we may wish to create a new issue for performing Anthos specific testing (per #91).

In a terraform module, these examples should be provided in `examples/name-of-example/main.tf` It would be interesting to use one of these examples for testing, rather than using the `git pull` for...

I ran into a similar error on equinix/terraform-metal-vsphere#19 caused by having 1 ESXI compute noted.

@dfong this data might be best tracked as a Terraform variable. We could track these as two separate variables, supported versions and latest version. If this is data that you...

> alternatively, branching or tagging would work for me. that is, if each anthos version had a tag like "tested-with-VERSION" . This particular format of tags would not be unique...

Do we understand why this error is happening? https://vkernelblog.com/vcenter-failed-to-set-the-time-via-ntp-details/ suggests that port 123 may be blocked. https://kb.vmware.com/s/article/59729 suggests that if the target NTP service does not respond to ICMP, the...

Closed based on #120. Reopening for @mattsday follow-up: > This is not a permanent fix, as ideally the deployment would fail at this stage instead of continuing until a timeout....