Consider extending default status check timeout #5106
Labels
internal
kind/friction
Issues causing user pain that do not have a workaround
kind/todo
implementation task/epic for the skaffold team
priority/p1
High impact feature/bug.
Milestone
Consider extending default status check timeout
After discussing some deployments that (due to automatic cluster scaling) often took longer than the two minute status-check timeout, @tejal29 mentioned that because status checks now fail deployments immediately if they encounter an irrecoverable error, it may be desirable to extend the default status check timeout. Creating this issue for further discussion.
The text was updated successfully, but these errors were encountered: