First class helm support in kpt pipelines

[ciaranjohnston]

Helm is the main way to deploy most applications in Kubernetes. While some applications offer pure KRM, and we would like to also see kpt have the ability to support helm applications alongside pure KRM applications.

From discussions with @kispaljr at Kubecon EU 2026, a solution could look like:

• extend the KRM function API to support non-KRM files
• pass the helm chart in as a .tgz
• internally process the helm file, render to KRM and run the pipelines
• re-render back to a helm chart and write back out to the package

Other solutions may exist - this needs analysis

[NETIZEN-11]

Hi @ciaranjohnston,

I’d like to work on this issue.

I’m thinking of proposing a design where Helm charts (.tgz) are unpacked and rendered using helm template, then the generated KRM manifests are passed through kpt pipeline functions. After processing, the output can either remain as KRM or be repackaged back into a Helm chart.

If this approach sounds reasonable, I can put together a detailed design doc before starting implementation.

Please let me know your thoughts or if you’d prefer a different direction.

Thanks!

[efiacor]

Hi @ciaranjohnston,

I’d like to work on this issue.

I’m thinking of proposing a design where Helm charts (.tgz) are unpacked and rendered using helm template, then the generated KRM manifests are passed through kpt pipeline functions. After processing, the output can either remain as KRM or be repackaged back into a Helm chart.

If this approach sounds reasonable, I can put together a detailed design doc before starting implementation.

Please let me know your thoughts or if you’d prefer a different direction.

Thanks!

Hi @NETIZEN-11 , thanks for your interest on this.
I think it might be best to complete the existing PRs that are already up for review here first.

[efiacor]

https://github.com/krm-functions