When I rollback a Service, it fails because the Service's ClusterIP field cannot be updated. about helm HOT 3 CLOSED

Can you show the Service objects the chart is creating for the 1.1 and 1.4 releases please.

It is confusing to me why Helm stored e.g the ClusterIP in the 1.4 release manifest. Helm should only be storing the object as rendered by the chart. Unless the chart specified all these fields. Which also is confusing to me as I didn't think Kubernetes allowed changing the ClusterIP (from a client) once created.

Do you see the same on a modern version of Kubernetes?

from helm.

@gjenkins8
In the chart template of openkruise, the definition of Service kruise-webhook-service is as follows:

{{- define "webhookServiceSpec" -}}
{{- $service := lookup "v1" "Service" .Values.installation.namespace "kruise-webhook-service" -}}
{{- if $service -}}
{{ if $service.spec.clusterIP -}}
clusterIP: {{ $service.spec.clusterIP }}
{{- end }}
{{ if $service.spec.clusterIPs -}}
clusterIPs:
  {{ $service.spec.clusterIPs }}
{{- end }}
{{ if $service.spec.ipFamilyPolicy -}}
ipFamilyPolicy: {{ $service.spec.ipFamilyPolicy }}
{{- end }}
{{ if $service.spec.ipFamilies -}}
ipFamilies:
  {{ $service.spec.ipFamilies }}
{{- end }}
{{ if $service.spec.type -}}
type: {{ $service.spec.type }}
{{- end }}
{{ if $service.spec.ipFamily -}}
ipFamily: {{ $service.spec.ipFamily }}
{{- end }}
{{- end -}}
ports:
- port: 443
  targetPort: {{ .Values.manager.webhook.port }}
selector:
  control-plane: controller-manager
{{- end -}}

Pay attention here:{{- $service := lookup "v1" "Service" .Values.installation.namespace "kruise-webhook-service" -}}

The lookup will find the currently existing kruise-webhook-service from the cluster and populate its properties into the template.

So the following happened:

• On first deployment, kruise-webhook-service does not exist in the cluster, so the ClusterIP is not populated.
• On the n-th(n>1) release, kruise-webhook-service already exists in the cluster, so the ClusterIP is populated into the template.

In kubernetes1.28, helm sent the same patch:

{
    "spec": {
        "clusterIP": null,
        "clusterIPs": null,
        "ipFamilies": null,
        "ipFamilyPolicy": null,
        "type": null
    }
}

but no error is returned.

from helm.

I have found that this is a known Kubernetes bug(in 1.21.X): kubernetes/kubernetes#91459 (comment), and has been fixed in version 1.22.0-beta.2:https://github.com/kubernetes/kubernetes/pull/103532/files.

So, let's close this issue.

from helm.