Skip to content

Explore provider-specific patching for Helm templates #2840

@beraldoleal

Description

@beraldoleal

Provider configuration and secrets are already isolated per provider under providers/. What we're missing is a way to patch base templates per provider without adding conditionals to them.

With kustomize we had patches.... for instance provider-specific changes to the DaemonSet (volume mounts, labels, annotations) were applied as patches from the overlay. The base templates stayed clean.

In Helm, for now... those had to become conditionals inside shared templates like daemonset.yaml, which gets noisy as providers grow.

This issue is to us discuss and explore ways to apply provider-specific template modifications without polluting the base templates.

Some constraints to consider:

  • values.yaml and secrets templates are auto-generated from cloud-providers source, we should respect this as much as possible
  • Solution should be self-contained in the chart, not require external tooling at install time as we can use this chart as a dependency in other charts.
  • Users should not need to pass multiple -f flags or manage post-renderer scripts. Ideally selecting a provider (--set provider=azure) is enough to get the right patches applied automatically

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions