You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After deploying the Bitnami redis chart with helm v2, and then migrating that deployment to helm v3 using the methods recommended by the Helm team, and then attempting to run helm upgrade on that deployment with helm v3, it fails with this error:
Error: UPGRADE FAILED: cannot patch "redis-deployment-name" with kind StatefulSet: StatefulSet.apps "redis-deployment-name" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden
Looks like this issue is causing problems for the GitLab team as well as they use this chart to deploy redis. They have a blocker issue for it and even a comment about this chart as to where the issue might be.
I've also run into this on various redis deployments using this chart.
The text was updated successfully, but these errors were encountered:
./helm2 install bitnami/redis --name redis --version 10.4.0
./helm3 plugin install https://github.com/helm/helm-2to3
./helm3 2to3 convert redis
./helm3 upgrade redis bitnami/redis --version 10.7.16
Error: UPGRADE FAILED: cannot patch "redis-master" with kind StatefulSet: StatefulSet.apps "redis-master" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden && cannot patch "redis-slave" with kind StatefulSet: StatefulSet.apps "redis-slave" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden
You will need to delete the statefulset and run the helm upgrade again:
Note that by setting --cascade=false, the pods are not being deleted with kubectl delete and they are deleted in the rolling update when executing the helm upgrade command.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Which chart:
redis - seems like all versions
Describe the bug
After deploying the Bitnami redis chart with helm v2, and then migrating that deployment to helm v3 using the methods recommended by the Helm team, and then attempting to run helm upgrade on that deployment with helm v3, it fails with this error:
To Reproduce
Steps to reproduce the behavior:
helm upgrade
on that deployment with Helm v3Expected behavior
The chart should be able to be converted to helm v3 and future updates to that deployment should work without error in v3
Version of Helm and Kubernetes:
helm version
:kubectl version
:Additional context
Looks like this issue is causing problems for the GitLab team as well as they use this chart to deploy redis. They have a blocker issue for it and even a comment about this chart as to where the issue might be.
I've also run into this on various redis deployments using this chart.
The text was updated successfully, but these errors were encountered: