v2.2.1

Improvements

• We now use the kube context of the first master to install the software, then only switch to the load balancer context at the very end, if it’s available. This approach helps because the load balancer might take some time to become healthy, which could otherwise slow down the installation process.
• Added an exponential backoff mechanism for cases where instance creation fails, such as when the selected instance types aren’t available in the chosen locations. This should help handle temporary issues more effectively.
• Added a new --force option to the delete command. If you set it to true, the cluster will be deleted without any prompts. This is really handy for automated operations.

Fixes

• Fixed an issue where the create command would time out before setting up the cluster autoscaler. This happened when there were no static worker node pools configured.

Upgrading from v2.1.0

See instructions for v2.2.0.