Enhance custom waiting behavior.

[rohitagg2020]

Describe the problem/challenge you have
There are certain scenarios where a custom resource moves to the FAILED state before coming to the SUCCESSFUL state. e.g. if a resource has external dependency as part of its readiness criteria, and this external dependency itself takes time to come, then resource moves to FAILED state and kapp deploy exits with error. But once the external service comes up, custom resource readiness criteria is fulfilled and it moves to the SUCCESSFUL state.

Describe the solution you'd like
I would like kapp deploy to not fail aggressively and rather it should fail only if the app has been in FAILED state for lets say 5 min.

Anything else you would like to add:
[Additional information that will assist in solving the issue.]

---

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.