Can i use ApplicationSet if have mix helm charts and kustomize?

[sipao]

The following structure is assumed.
There is app-A, which is configured with kustomize, and app-B, which is configured with helm charts.

.
├── application-set.yaml
└── apps
    ├── app-A
    │   ├── base
    │   └── overlays
    │       ├── dev
    │       └── prod
    └── app-B
        └── Chart.yaml

[itewk]

same question.

[crenshaw-dev]

Not yet. We need to improve how ApplicationSet does templating first. #9177

[mihaigalos]

Hi @crenshaw-dev, since the issue has been closed, is this now possible?
I'm trying to consume a component.yaml which will indicate a repo containing either values.yaml or kustomization.yaml files to overlay using ArgoCD (2.9.3, latest).

Something like (not yet working):
bootstrap.yaml:

apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: "dev-appset"
  namespace: myproject-argocd
spec:
  goTemplate: true
  goTemplateOptions: ["missingkey=error"]
  generators:
  - git:
      requeueAfterSeconds: 300
      repoURL: 'https://do.main/orga/repo.git'
      revision: HEAD
      files:
      - path: 'core/*/component.yaml'
  template:
    metadata:
      name: '{{.name}}'  
    spec:
      project: 'myproject'
      sources:
        targetRevision: '{{.targetRevision}}'
        repoURL: '{{.repoURL}}'
        path: 'deployment'
        - repoURL: 'https://do.main/orga/repo.git' # For Kustomize
          targetRevision: HEAD
          ref: values
        - repoURL: '{{.repoURL}}' # For Helm
          targetRevision: '{{.targetRevision}}'
          path: deployment
          helm:
            valueFiles:
            - $values/all/accounts/account1.yaml
            - $values/core/{{.name}}/values.yaml
            - $values/core/{{.name}}/stages/account1-dev.yaml
      destination:
        server: https://kubernetes.default.svc
        namespace: '{{.namespace}}'

component.yaml:

name: myproject-dex
namespace: myproject-dex
targetRevision: 2023.50.1
repoURL: https://do.main/orga/myproject-dex-manifest.git

[TechDawg270]

i am attempting to achieve what is described in the OP where one AppSet can use dynamic tool detection and deploy both helm and kustomize applications from one git generator, and unfortunately that does not work. i removed appset.spec.template.spec.source.helm from the AppSet and the new directory with a kustomization.yaml at the base is not recognized. I was able to find a hacky workaround however. If i first add a Chart.yaml to create the application and then later remove that and add a kustomization.yaml to wrap Helm it would pick up the application and work

[TechDawg270]

after further investigation this does seem possible now - https://argo-cd.readthedocs.io/en/stable/operator-manual/applicationset/Generators-Git/#git-generator-directories

not sure what version introduced those enhanced go based templating changes, but my 2.6 seems to be too outdated to include them. i will update once i can upgrade to latest 2.9.x and confirm it is working

[hirenko-v]

is there any way to provide helm values file?

[zackdilan]

@sipao Hi, Were you able to find a solution for this issue?

[zackdilan]

@itewk, Thanks for the reply. How exactly do you do this?
Do you store the rendered templates in the git and patch it with overlays?
How do you automate this? because I don't know how to wrap with environment-specific values file with the later strategy I mentioned above.

PS: I have a private helm chart in my package registry and the helm chart plugin doesn't support private repo as far as I could see in the official customize docu

[itewk]

@itewk, Thanks for the reply. How exactly do you do this?

Do you store the rendered templates in the git and patch it with overlays?

How do you automate this? because I don't know how to wrap with environment-specific values file with the later strategy I mentioned above.

PS: I have a private helm chart in my package registry and the helm chart plugin doesn't support private repo as far as I could see in the official customize docu

When I first posted I didn't include link to doc, now that I did, does that answer your questions?

[zackdilan]

no in the attached doc, it uses the helmcharts plugin and private registry is not supported , its here https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/helmcharts/#long-term-support

[itewk]

no in the attached doc, it uses the helmcharts plugin and private registry is not supported , its here https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/helmcharts/#long-term-support

when you say private registry, do you mean your registry has authenticaiton, or that it is within your network?

I know it works with a custom regristy (never tried authenticated), either helm, or OCI (despite the doc saying you can't use OCI, they fixed that a while back).

Maybe the athenitcated bit works with OCI since its just pulling a container image, I havn't tried. I can ask around though.

How do you automate this? because I don't know how to wrap with environment-specific values file with the later strategy I mentioned above.

to do Kustomize overlays you have two options / scenarios:

1. if you want to "override" a helm value, there isn't really a way to do that, you have to call the helm chart from each overlay BUTTT

2. in some cases you can just use standard kustomize overlay techniques since the helm chart is rendered by kustomize first (as normal if its a base, and even within the same kustomize) before orther resources, so you can use standard kustomize patching to change CRs of the rendered helm chart

Sorry i dont have a good example i can link you to at the moment

[TechDawg270]

for whatever it is worth, you can mount a docker config.json file for the ArgoCD repo server to authenticate with a private OCI helm based registry