These duplicate entries cause validation errors when deploying with flux helm-controller
Helm install failed: error while running post render on files: map[string]interface {}(nil): yaml: unmarshal errors:
line 35: mapping key "sideEffects" already defined at line 20
After correcting this issue perhaps another issue should be created to add a strict linter action to prevent this from happening again.
Something that would run helm template, followed by kubeconform -strict -ignore-missing-schemas which currently produces
MutatingWebhookConfiguration kube-enforcer-me-injection-hook-config failed validation: error unmarshalling resource: error converting YAML to JSON: yaml: unmarshal errors:
line 33: key "sideEffects" already set in map
ValidatingWebhookConfiguration kube-enforcer-admission-hook-config failed validation: error unmarshalling resource: error converting YAML to JSON: yaml: unmarshal errors:
line 48: key "sideEffects" already set in map
Mutating and Validating webhook configurations have duplicate entries for sideEffects, introduced in https://github.com/aquasecurity/aqua-helm/commit/0081cbcbfa69b8859244c7b1930804f65c26f497
These duplicate entries cause validation errors when deploying with flux helm-controller
This isn't the first occurrence, similar issues have been reported and fixed before, see: https://github.com/aquasecurity/aqua-helm/issues/608 https://github.com/aquasecurity/aqua-helm/issues/483
After correcting this issue perhaps another issue should be created to add a strict linter action to prevent this from happening again. Something that would run
helm template
, followed bykubeconform -strict -ignore-missing-schemas
which currently produces