helmfile: failed to replace object: Service "NNN" is invalid: spec.clusterIP: Invalid value: "": field is immutable

After running helmfile sync the first time, the release was installed successfully.

However, a second run generates this error.

FAILED RELEASES:
NAME
frontend
in ./helmfile.yaml: failed processing release frontend: helm exited with status 1:
  client.go:399: Replaced "frontend-nginx-ingress-controller" with kind Deployment for kind Deployment
  client.go:399: Replaced "frontend-nginx-ingress-default-backend" with kind Deployment for kind Deployment
  client.go:399: Replaced "frontend-nginx-ingress-controller" with kind Deployment for kind Deployment
  client.go:399: Replaced "frontend-nginx-ingress-default-backend" with kind Deployment for kind Deployment
  Error: UPGRADE FAILED: an error occurred while rolling back the release. original upgrade error: failed to replace object: Service "frontend-nginx-ingress-controller" is invalid: spec.clusterIP: Invalid value: "": field is immutable && failed to replace object: Service "frontend-nginx-ingress-default-backend" is invalid: spec.clusterIP: Invalid value: "": field is immutable: failed to replace object: Service "frontend-nginx-ingress-controller" is invalid: spec.clusterIP: Invalid value: "": field is immutable && failed to replace object: Service "frontend-nginx-ingress-default-backend" is invalid: spec.clusterIP: Invalid value: "": field is immutable

I suspect it might be realted to the fact that I’m using helm v3. Could this be part of the incompatibility? My cluster is not running tiller ever since I migrated to helm v3.

EDIT: Using

helmfile version v0.93.2
helm v3.0.0

About this issue

Original URL
State: open
Created 5 years ago
Reactions: 2
Comments: 17 (8 by maintainers)

Most upvoted comments

It is problem with 90% charts inherited from Helm 2. @juliohm1978 are you *ing jocking ? Fix Helm2 to Helm3 Chart migration then. Don’t close eyes on very commented and top issue of Helm 3. Migration should be smooth. It’s reasonable to display deprication message or something like that. Not “error: fuck you all Helm 2 users!”. Just silencing issue won’t help. We will open 10 new issues like that.

antonakv on Jan 1, 2020

Probably setting force to false will help. It helped us, for instance.

andrewnazarov on Jan 23, 2020

Very late apologies, everyone. This clearly seems to also be related to helm3 for some use other cases than the one I mentioned originally. I’m reopening for the sake of everyone else. But I’m not at all sure how to reproduce this right now. I have long moved to helm3 by either fixing charts or just plain helm del && helm install all over.

Any reproducible examples are welcome.

juliohm1978 on Feb 25, 2020