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.

Sign up for GitHub

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

Jump to bottom

Drop old Pods in deep ImagePullBackoff or CrashLoopBackoff states #165

Open
distorhead opened this issue Mar 10, 2020 · 0 comments
Open

Drop old Pods in deep ImagePullBackoff or CrashLoopBackoff states #165

distorhead opened this issue Mar 10, 2020 · 0 comments

Comments

@distorhead
Copy link
Member

When a Pod is in the ImagePullBackoff state and pull retry period is too high to be awaited right now, during deploy process, then werf should drop this old Pod to reinitiate pull process immediately during current deploy process.
@distorhead distorhead mentioned this issue Mar 10, 2020
Open
@distorhead distorhead changed the title Drop old Pods in deep ImagePullBackoff state Drop old Pods in deep ImagePullBackoff or CrashLoopBackoff states Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@distorhead