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

Helm - Use Pod Disruption Budget to ensure Dapr remains up #3148

Closed
tomkerkhove opened this issue May 10, 2021 · 3 comments · Fixed by #3170
Closed

Helm - Use Pod Disruption Budget to ensure Dapr remains up #3148

tomkerkhove opened this issue May 10, 2021 · 3 comments · Fixed by #3170
Assignees
Labels
kind/bug Something isn't working P1
Milestone

Comments

@tomkerkhove
Copy link
Contributor

In what area(s)?

/area runtime
/area operator
/area placement

/area docs
/area test-and-release

Describe the feature

Use Pod Disruption Budget to survive voluntary removal such as node update, rollout of new version, etc which defines how many % of instances can be removed at the same time.

This could potentially only be enabled when running in HA is enabled.

Release Note

RELEASE NOTE: ADD Use Pod Disruption Budget to ensure Dapr remains up

@tomkerkhove
Copy link
Contributor Author

Happy to help where I can by sending a PR or so.

@yaron2
Copy link
Member

yaron2 commented May 12, 2021

A PR for this would be great and most welcomed.

@tomkerkhove
Copy link
Contributor Author

I'll work on this!

@artursouza artursouza added this to the v1.3 milestone May 27, 2021
@artursouza artursouza added the P1 label May 27, 2021
@msfussell msfussell added the kind/bug Something isn't working label May 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working P1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants