helm upgrade issue on AWS EKS

Jackie
2 min readJun 8, 2020

--

Have been continuous receiving this error message during the ` helm upgrade` even with several retry

UPGRADE FAILED Error: kind StorageClass with the name "..." already exists in the cluster and wasn't defined in the previous release. Before upgrading, please either delete the resource from the cluster or remove it from the chart Error: UPGRADE FAILED: kind StorageClass with the name ".." already exists in the cluster and wasn't defined in the previous release. Before upgrading, please either delete the resource from the cluster or remove it from the chart

Have tried two solutions, (the 1st doesn’t work out)

  1. as the helm upgrade error message, I did a helm delete the storageclass, then run the helm upgrade, even though on the internet some claim this work, but actually no, it fails again with same error message
  2. did a helm rollback to a previous working release, then run the helm upgrade again, then worked
helm history <release> helm rollback <release> <a-previous-working-revision> helm upgrade --install <release> .....

At the same time, for helm 2, all helm release information are stored in configmap

## use this command to get the release info kubectl get configmaps -n kube-system <release> -o jsonpath='{.data.release}' | base64 -d | gzip -cd

as for helm 3, it’s stored in secrets.

Published

Originally published at https://lwpro2.dev on June 8, 2020.

--

--

No responses yet