Error: UPGRADE FAILED: kind ... already exists in the cluster and wasn't defined in the previous release

• Error: UPGRADE FAILED: kind CronJob with the name "your-cronjob" in "your-env" already exists in the cluster
• Error: UPGRADE FAILED: kind ConfigMap with the name "you-configmap-name" in "your-env" 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

Related

• Error: kind CronJob with the name "your-cronjob" in "your-env" already exists in the cluster .../...
• helm upgrade
• helm install . --dry-run --debug --generate-name
• kubectl get configmap
• helm upgrade --atomic

See also

• AWS IAM Authenticator for Kubernetes: aws-auth, kubectl edit -n kube-system configmap/aws-auth, eksctl create iamidentitymapping, mapUsers:, mapRoles:, mapAccounts:
• ConfigMaps: kubectl [ get | edit | describe | create | delete ] configmaps, aws-auth, Kustomize, kind: ConfigMap, ConfigMapRef, envFrom
• Kubectl information commands: cluster-info | view | pods | nodes | services | version | describe | logs