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

Allow the 'updateStrategy' of the Daemonset to be configured in Helm #285

Merged
merged 2 commits into from
Oct 28, 2020

Conversation

chrisamert
Copy link
Contributor

Reason for Change:

This PR enables the 'updateStrategy' of the Daemonset to be configured by Helm parameters. The default values are the same as the current defaults; RollingUpdate strategy with maxUnavailable set to 1, so behavior will change only if the user specifies a custom value.

Requirements

  • squashed commits
  • included documentation
  • added unit tests and e2e tests (if applicable).

Issue Fixed:

Fixes #283 283
Please answer the following questions with yes/no:

  • Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution? No

Special Notes for Reviewers:

@aramase
Copy link
Member

aramase commented Oct 23, 2020

/azp run pr-e2e-azure

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@aramase aramase left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chrisamert These changes need to be made in the manifest_staging dir where we currently host the staging charts. All the chart changes are then tagged with the release. Could you make the changes only in manifest_staging/charts instead

@chrisamert
Copy link
Contributor Author

Ahh I missed that. I'll get these changes moved over

This PR enables the 'updateStrategy' of the Daemonset to be configured by Helm parameters.  The default values are the same as the current defaults; RollingUpdate strategy with maxUnavailable set to 1, so behavior will change only if the user specifies a custom value.
@chrisamert chrisamert force-pushed the addUpdateStrategyToHelmParameters branch from a51a325 to 422edb4 Compare October 23, 2020 19:37
@aramase
Copy link
Member

aramase commented Oct 27, 2020

Adding the default values from docs here for future reference-

RollingUpdate: This is the default update strategy.
With RollingUpdate update strategy, after you update a DaemonSet template, old DaemonSet pods will be killed, and new DaemonSet pods will be created automatically, in a controlled fashion. At most one pod of the DaemonSet will be running on each node during the whole update process.
You may want to set .spec.updateStrategy.rollingUpdate.maxUnavailable (default to 1) and .spec.minReadySeconds (default to 0) as well.

Ref docs:
https://kubernetes.io/docs/tasks/manage-daemon/update-daemon-set/#daemonset-update-strategy
https://kubernetes.io/docs/tasks/manage-daemon/update-daemon-set/#performing-a-rolling-update

@aramase
Copy link
Member

aramase commented Oct 27, 2020

/azp run pr-e2e-azure

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@aramase aramase left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@aramase aramase added the helm label Oct 27, 2020
@aramase aramase merged commit 760d326 into Azure:master Oct 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support configuring updateStrategy.rollingUpdate.maxUnavailable in Helm charts
2 participants