This usually happens when the state of the resources (e.g.
Namespaces, etc) in the kubernetes cluster does not match what Helm knows about. In the example above, the namespace had been deleted without first deleting the helm releases. So
helm attempted to perform an upgrade on a non-existent resource.
This is a companion discussion topic for the original entry at https://docs.cloudposse.com/troubleshooting/helm-upgrade-failed-to-create-resource/