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

Use DaemonSet MaxSurge for stability and availability #78

Open
mflendrich opened this issue Feb 4, 2025 · 0 comments
Open

Use DaemonSet MaxSurge for stability and availability #78

mflendrich opened this issue Feb 4, 2025 · 0 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@mflendrich
Copy link
Contributor

Issue originally authored by tnozicka as #25

We should use maxSurge in our deploy files to make sure we

a) spin up a new Pod on the node while the old one keeps working
This is important to reduce downtime as say pull time can take long, hit an error, backoff or it may not start

b) to make sure the new pod start far enough (and isn't broken) before we tear down the old Pod

@mflendrich mflendrich added kind/feature Categorizes issue or PR as related to a new feature. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants