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
We are proposing a change to the behavior of maxSurge. Currently, if maxSurge cannot be satisfied due to capacity constraints or other issues during an upgrade, the operation fails immediately. With this change, we will instead surge based on the available capacity.
For example, if maxSurge is set to 5 but only 3 nodes are available for surging, the upgrade will proceed with those 3 nodes rather than failing outright.
Additionally, a minimum threshold for capacity-based surging will be introduced to balance upgrade speed and improve the overall upgrade experience.
We’d love to hear your feedback on this proposal.
The text was updated successfully, but these errors were encountered:
We are proposing a change to the behavior of maxSurge. Currently, if maxSurge cannot be satisfied due to capacity constraints or other issues during an upgrade, the operation fails immediately. With this change, we will instead surge based on the available capacity.
For example, if maxSurge is set to 5 but only 3 nodes are available for surging, the upgrade will proceed with those 3 nodes rather than failing outright.
Additionally, a minimum threshold for capacity-based surging will be introduced to balance upgrade speed and improve the overall upgrade experience.
We’d love to hear your feedback on this proposal.
The text was updated successfully, but these errors were encountered: