adding kustomize transformers: causes breakage

[travisghansen]

adding kustomize transformers: causes breakage

[travisghansen]

Can you send to full output of the helmfile template command with/without the transformers? I'm interested to see what the product is.

I've never used transformers but on the surface I don't see any reason why they wouldn't work. Any chance of differences of versions of helm, helmfile, kustomize, etc?

[jjungnickel]

I'm currently in the process of investigating a similar issue. This appears to be caused by the --api-versions that are passed to helm template by way of helmfile template --args <...> not being passed to chartify which is only being involved once you specify patches/transformers.

If the templates use .Capabilities.APIVersions the resources will not be in included.

It appears that those versions defined in the state file via apiVersions will get passed on, so I was able to work around this by defining in my helmfile:

apiVersions:
  {{ env "KUBE_API_VERSIONS" | splitList "," | toYaml | nindent 2 }}

[travisghansen]

Wow good find. Here is a base file all my files include.

# note that helm currently *appends* these values vs replaces them
# https://github.com/helm/helm/pull/10108
apiVersions:
- networking.k8s.io/v1/IngressClass
#- networking.k8s.io/v1beta1/IngressClass
{{- if (env "KUBE_API_VERSIONS") }}
{{- range $apiV := ( requiredEnv "KUBE_API_VERSIONS" | split "," ) }}
- {{ $apiV }}
{{- end }}
{{- end }}