Best way to patch HelmRelease sub-charts using Kustomization

[shiftychris]

Hoping someone can point me the right direction. I have a HelmRelease chart which has sub charts inside to do multiple deployments for the same container. I need to do some patching to add tolerations/taints to each sub service (servicea, serviceb, servicec, serviced etc). Is there a documented or recommended way to do this without defining an individual patch for each sub service.

apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: service-name
  namespace: default
spec:
  releaseName: servicename-sandbox
  interval: 3m0s
  chart:
    spec:
      chart: ./charts/service-name.tgz
      sourceRef:
        kind: GitRepository
        name: service-repository
        namespace: flux-system
  values:
    global:
      APIKey: aaaabbbbccccc
    sevicea:
      configmap:
        LOG_LEVEL: INFO
        CONFIGVAL: AB
      image:
        repository: repo.io/service.name # {"$imagepolicy": "flux-system:servicename:name"}
        tag: v0.0.1 # {"$imagepolicy": "flux-system:servicename:tag"}
    serviceb:
      configmap:
        LOG_LEVEL: INFO
        CONFIGVAL: AC
      image:
        repository: repo.io/service.name # {"$imagepolicy": "flux-system:servicename:name"}
        tag: v0.0.1 # {"$imagepolicy": "flux-system:servicename:tag"}
    servicec:
        #same as above but with different config
    serviced:
        #same as above but with different config
    servicee:
        #same as above but with different configmap value

If not (from my googling I am at a blank), is there any form of support for patch paths supporting any form of regex/wildcard/list/array of paths for example:

spec:
  patches:
    - patch: |
       - op: add
         path: "/spec/values/*/tolerations" or ["/spec/values/servicea/tolerations", "/spec/values/serviceb/tolerations"]

[shiftychris]

After playing around for a little while, I am guessing my easiest option would be to add a postRenderer to the HelmChart using patch to add the changes to the deployment chart. But love to get other thoughts.

[kingdonb]

Yes, you can use any Kustomize feature including wildcard patches in a post renderer with your HelmReleases – the tricky part is to figure out where your patch went wrong when Kustomize swallows all the output and the patch doesn't seem to be applied, it's not easy testing postRender patches, but it is definitely the solution to your issue. Usually important to review the raw output of helm template in order to ensure you have the right GVKNN (name/namespace) for every resource, since any mismatch can result in patches that simply don't apply, when you've used a wildcard selector as there will be no error if the wildcard didn't match anything.

Edit: Here is an example that does apply a toleration to some pod, no wildcard, but it's 90% of the solution, 100% if you just add the wildcard 👍

[gecube]

@kingdonb Hi! Did something change since 2022 in patches for HR?