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

Backport to 5.7: setting upgrade job restartPolicy to never #586

Merged
merged 1 commit into from Mar 22, 2021

Conversation

nimrod-becker
Copy link
Contributor

  • setting to never will keep failed pods around so we can examine the failures
  • set backoffLimit to 4 (default is 6) to reduce the number of pods that can potentially stay in the NS
  • one thing to notice is that failed runs will leave a pod (not running) with ERROR state

Signed-off-by: Danny Zaken dannyzaken@gmail.com
(cherry picked from commit 5838aa6)

* setting to never will keep failed pods around so we can examine the failures
* set backoffLimit to 4 (default is 6) to reduce the number of pods that can potentially stay in the NS
* one thing to notice is that failed runs will leave a pod (not running) with ERROR state

Signed-off-by: Danny Zaken <dannyzaken@gmail.com>
(cherry picked from commit 5838aa6)
@nimrod-becker nimrod-becker merged commit 2e09b81 into noobaa:5.7 Mar 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants