Our current deployment timeout is 120s (enforced by the asyncworker timeout) which might be too small to deploy big applications. We want to make this timeout configurable by adding a timeout property at the container level.
Acceptance criteria
Schema Change to add a new container property for deployment timeout
Modify the code to look at the new property to enforce the timeout. Investigate if this timeout value can be fed into the k8s progress deadline.
Make the asyncworker timeout dynamically configurable such that it is now larger than the timeout specified by the user
There's a work-in progress design doc here that was closed as stale/incomplete. Anyone who wants to pick this work up again could use that document as a starting point (if they feel inclined).
Overview of feature request
Our current deployment timeout is 120s (enforced by the asyncworker timeout) which might be too small to deploy big applications. We want to make this timeout configurable by adding a timeout property at the container level.
Acceptance criteria
Additional context
AB#9424