Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure UpdateStrategy on CSI Driver #2946

Open
KevinThompsonYCRX opened this issue Mar 29, 2024 · 1 comment
Open

Configure UpdateStrategy on CSI Driver #2946

KevinThompsonYCRX opened this issue Mar 29, 2024 · 1 comment
Labels
helm Changes to helm templates or values file

Comments

@KevinThompsonYCRX
Copy link

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

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

@chrismuellner chrismuellner added the helm Changes to helm templates or values file label Apr 3, 2024
@chrismuellner
Copy link
Collaborator

Thanks for the feature request!

We've created an internal ticket for it and will make this field configurable in the Helm chart in a future release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
helm Changes to helm templates or values file
Projects
None yet
Development

No branches or pull requests

2 participants