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

provide more intelligent waiting strategy for resources that have associated failed pods #5

Closed
cppforlife opened this issue Mar 22, 2019 · 2 comments
Closed

provide more intelligent waiting strategy for resources that have associated failed pods #5

cppforlife opened this issue Mar 22, 2019 · 2 comments
Labels
enhancement This issue is a feature request

Comments

@cppforlife
Copy link
Contributor

example: if there are Jobs/CronJobs that have failed jobs, currently kapp will indicate that error has occurred as it tries to wait for the system to converge. this behaviour is useful for Deployments for example because pods are actively being cycled, but in other cases it may not be helpful. decide what to do and come up with a generic way to handle this...
@cppforlife cppforlife added the enhancement This issue is a feature request label Mar 22, 2019
@cppforlife
Copy link
Contributor Author

@bmaynard mentioned related concern in slack [1]:

I was wondering if its possible to wait for a job to complete before the deploy command finishes?

[1] https://kubernetes.slack.com/archives/CH8KCCKA5/p1561579918257400

@cppforlife
Copy link
Contributor Author

since then we no longer wait for associated resources by default so this is not a problem.

@renuy renuy mentioned this issue Jul 20, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement This issue is a feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cppforlife