-
Notifications
You must be signed in to change notification settings - Fork 8
Open
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/from-migrationIndicates that this issue is a copy of a corresponding issue mentioned in the description.Indicates that this issue is a copy of a corresponding issue mentioned in the description.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Description
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
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/from-migrationIndicates that this issue is a copy of a corresponding issue mentioned in the description.Indicates that this issue is a copy of a corresponding issue mentioned in the description.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.