Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade from 2.2.0 to 2.2.1 is broken #25

Closed
brewsteropsdev opened this issue Oct 5, 2020 · 3 comments
Closed

Upgrade from 2.2.0 to 2.2.1 is broken #25

brewsteropsdev opened this issue Oct 5, 2020 · 3 comments
Labels

Comments

@brewsteropsdev
Copy link
Contributor

Running a helm upgrade from 2.2.0 to 2.2.1 results in the following error:

Error: UPGRADE FAILED: cannot patch "nextcloud-dev" with kind Deployment: Deployment.apps "nextcloud-dev" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/component":"app", "app.kubernetes.io/instance":"nextcloud-dev", "app.kubernetes.io/name":"nextcloud"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable
@somerandow
Copy link
Contributor

Hi there! You will need to delete the existing nextcloud-dev deployment before running helm upgrade.
Something like kubectl delete deployment nextcloud-dev.
The changes in 2.2.1 do not require modifying your values.yaml or changing how you install the chart, which is why the major/minor versions were not bumped.
This is just an unfortunate restriction around modifying existing deployments in kubernetes.

@jessebot
Copy link
Collaborator

If this is still an issue, perhaps it should go into the documentation? I am currently rounding up issues related to upgrades to better review and help with creating an upgrade section of our documentation. Anything I find, I put an upgrades label on, so that we can easily find them all.

@jessebot
Copy link
Collaborator

I'm going to close this as stale since it's been a few years without a reply from the original poster and it concerns a chart version that is several major versions behind. If you're still having trouble with an upgrade from a more recent version to latest, we'd love to help you further.

@jessebot jessebot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants