Charts: [stable/openldap] Helm3 fails with "ClusterIP is immutable" error

[Morishiri]

Describe the bug
When updating the release with helm3 it throws an error about ClusterIP not being mutable.

Version of Helm and Kubernetes:

$  helm version  
version.BuildInfo{Version:"v3.1.0", GitCommit:"b29d20baf09943e134c2fa5e1e1cab3bf93315fa", GitTreeState:"clean", GoVersion:"go1.13.7"}

$  kubectl version           
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2+k3s1", GitCommit:"cdab19b09a84389ffbf57bebd33871c60b1d6b28", GitTreeState:"clean", BuildDate:"2020-01-27T18:09:26Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}



md5-d4b868dfd1cdcca8bed21a3883bb5c11



Error: UPGRADE FAILED: cannot patch "ldap-openldap" with kind Service: Service "ldap-openldap" is invalid: spec.clusterIP: Invalid value: "": field is immutable: cannot patch "ldap-openldap" with kind Service: Service "ldap-openldap" is invalid: spec.clusterIP: Invalid value: "": field is immutable

What you expected to happen:
Upgrade goes without issues because the field was not actually mutated

How to reproduce it (as minimally and precisely as possible):
helm install ldap stable/openldap

helm upgrade ldap stable/openldap --set replicaCount=2

Anything else we need to know:
I will provide the PR with solution.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[Morishiri]

remove lifecycle stale

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[Morishiri]

remove lifecycle stale

[chirangaalwis]

I am experiencing this error as well. Every time before a Helm upgrade, I am forced to delete the Kubernetes Service exposing the OpenLDAP Kubernetes Pod (as I am using this OpenLDAP chart as a sub chart).

I am using Helm version 3.1.2 with GKE based Kubernetes Server version: 1.14+, Git Version: v1.14.10-gke.27.

Hopefully this would be fixed soon.

[kyounger]

Bump. Issue for me, too.

[kyounger]

I tested by pulling the repo, checking out the PR, and using the chart locally to install. Using helm 3.2.0. Fix seems to work fine.

[chirangaalwis]

I tested by pulling the repo, checking out the PR, and using the chart locally to install. Using helm 3.2.0. Fix seems to work fine.

@kyounger it seems the chart source in this repository has not been updated for quite a while (at least 5 months as of now). The relevant chart of version 1.2.3 had been pushed during this month to the chart repository.

Shouldn't this change be merged if appropriate and made available in the chart artifact available at the stable chart repository?

[chirangaalwis]

It seems that this has been fixed in version 1.2.4 and is available at the Helm Hub.

LGTM!!! Thanks @Morishiri