You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 14, 2023. It is now read-only.
Now after removing the VM, the cluster waits another 5 minutes for the node to return. Since this wait is meaningless, we can immediately notify the cluster about this by running node deletion. In the same way as a reboot is called for nodes with accelerators.
The text was updated successfully, but these errors were encountered:
GKE autoscaling may recreate instance with the same hostname (and most of parameters), so that actually may not be a best solution.
My point is, that in best case scenario from master point of view the node was rebooted, while in worst case the node is lost forever.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Now after removing the VM, the cluster waits another 5 minutes for the node to return. Since this wait is meaningless, we can immediately notify the cluster about this by running node deletion. In the same way as a reboot is called for nodes with accelerators.
The text was updated successfully, but these errors were encountered: