Deployment is stuck at RUNNING state if it unable to rollback in case of failure

[khanhtc1202]

What happened:

When the deployment of kind k8s got errors (because of kubectl version mismatch - for instance), the ROLLBACK stage will be started. If the ROLLBACK is failed as well, the deployment is stuck at RUNNING state.

What you expected to happen:

In case of k8s failure error, piped should be able to finish the deployment regardless k8s issue.

How to reproduce it:

Environment:

• piped version: 0.26.0
• control-plane version: 0.27.1
• Others:

[knanao]

Check whether setting timeout for command (etc kubectl...) or not

[knanao]

/assign @khanhtc1202