Use DaemonSet MaxSurge for stability and availability #78
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.
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
The text was updated successfully, but these errors were encountered: