k8s-helm-immutable-field-workaround

To fix immutable field errors in ArgoCD, you can use a PreSync delete-and-recreate hook, degrade the chart resource by managing the immutable field in a separate manifest, or apply ignoreDifferences to suppress drift for non-critical fields.

Helm deployment fails because loadBalancerClass is an immutable field on Kubernetes Services that cannot be patched after creation, requiring you to delete and recreate the resource or manage the field outside the chart.

The best way to change storageClassName on an existing PVC is to use an ArgoCD PreSync hook to delete the resource before sync so Helm can recreate it with the correct values, or manage the PVC independently from the chart.

Yes, you can use ignoreDifferences to suppress drift when the immutable field is cosmetic or non-critical, allowing ArgoCD to ignore the discrepancy without attempting a patch that would fail.

To degrade a Helm chart resource, remove the immutable field from the chart's values and templates, then create a separate manifest managed independently to own that specific field, preventing patch failures during sync.

You should avoid using a PreSync delete hook when the resource has persistent data or cannot tolerate downtime, as deleting and recreating the resource will cause service interruption and potential data loss.