Experiment: Detect and roll back from pending-upgrade status
If a prior helm install/upgrade is interrupted for a variety of reasons (control-c'd, some kind of communication problem with the Kubernetes API server, whatever), it is very likely that the next attempt to perform a helm install/upgrade will result in the following error:
Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress
This situation can be resolved by rolling back the prior failed operation. The simplest way to do this is with: helm rollback