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
Is your feature request related to a problem? Please describe.
In some very large clusters, it can take a very long time to roll out the CSI pods one-by-one during an update.
Describe the solution you'd like
Add a field csidriver.updateStrategy.rollingUpdate.maxUnavailable (or something more concise) to set the value for the daemonset
Describe alternatives you've considered
N/A, without being able to configure this to speed up the rollout, we are forced to either delete & recreate the whole DS, or raise the timeout on our helm releases to an unreasonable time range
Is your feature request related to a problem? Please describe.
In some very large clusters, it can take a very long time to roll out the CSI pods one-by-one during an update.
Describe the solution you'd like
Add a field
csidriver.updateStrategy.rollingUpdate.maxUnavailable
(or something more concise) to set the value for the daemonsetDescribe alternatives you've considered
N/A, without being able to configure this to speed up the rollout, we are forced to either delete & recreate the whole DS, or raise the timeout on our helm releases to an unreasonable time range
Additional context
To be clear, this is the line I'd like to see variablized:
https://github.com/Dynatrace/dynatrace-operator/blob/v1.0.0/config/helm/chart/default/templates/Common/csi/daemonset.yaml#L283
The text was updated successfully, but these errors were encountered: