-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
helm chart to allow for configuration of updateStrategy #13031
Comments
What workloads does this apply to? You reference DaemonSets, so I assume this is specific to the linkerd-cni chart? |
Yes that is correct the linkerd-cni chart daemonset |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
Can you please leave this as not stale. |
If you will accept a PR for this I can put that in fairly trivially |
Sorry for the late reply @sstarcher ; yes, we'd be glad to review a PR for this 👍 |
* For users with large clusters rollout of the cni can take a bit of time. This will allow them to configure a faster rollout of the cni resources. linkerd#13031
* For users with large clusters rollout of the cni can take a bit of time. This will allow them to configure a faster rollout of the cni resources. linkerd#13031 Signed-off-by: Shane Starcher <[email protected]>
* For users with large clusters rollout of the cni can take a bit of time. This will allow them to configure a faster rollout of the cni resources. linkerd#13031 Signed-off-by: Shane Starcher <[email protected]>
* For users with large clusters rollout of the cni can take a bit of time. This will allow them to configure a faster rollout of the cni resources. linkerd#13031 Signed-off-by: Shane Starcher <[email protected]>
* [feat] allow cni updateStrategy to be configurable * For users with large clusters rollout of the cni can take a bit of time. This will allow them to configure a faster rollout of the cni resources. #13031 Signed-off-by: Shane Starcher <[email protected]> * add update strategy for cli Signed-off-by: Shane Starcher <[email protected]> --------- Signed-off-by: Shane Starcher <[email protected]> Co-authored-by: Shane Starcher <[email protected]>
What problem are you trying to solve?
Large amount of daemonsets can take a long time to update unless rolling update strategy can not be changed to a percent
How should the problem be solved?
Allow update strategy to be configurable.
Any alternatives you've considered?
No
How would users interact with this feature?
They would be able to configure the setting themselves without patching.
Would you like to work on this feature?
maybe
The text was updated successfully, but these errors were encountered: