Flux Depends on With a wildcard pattern or namespace

[jeevanragula]

We have a use case one of the Helm Relase depends on Multiple Helm Releases which follow a pattern and they gets created dynamically in single namespace.

So we are looking for a feature where we either specify a pattern to match the helm release names or specify namespace and keep the name as optional so that if all the helm releases under that namespace or that pattern matches then the reconcile will happen.

Can some one tell if this is currently supported or Is this a new feature we can introduce in Flux?

apiVersion: helm.toolkit.fluxcd.io/v2beta2
kind: HelmRelease
metadata:
  name: test-application
  namespace: test
spec:
  chart:
    spec:
      version: 1.0.0
  dependsOn:
    - name: *-another-application
      namespace: anothernamespace

[jeevanragula]

@stefanprodan Can we make it as feature request?

[stefanprodan]

Using a wildcard would break the whole functionality because at creation time (when dependsOn matters), releases are created in parallel, a wildcard will prevent the controller from reconciling in the desired order because some releases may not be present in etcd.

[jeevanragula]

@stefanprodan Can we keep checking all helm releases with that pattern during the installation or upgrade?
Do you have any suggestions on how to solve my usecase?

[stefanprodan]

You can't use pattern matching because there is nothing to match on if the releases that a release dependsOn are not present in etcd.

[stefanprodan]

What you can do is group HelmReleases in different Kustomizations and use dependsOn between the Kustomizations. Example here: https://github.com/fluxcd/flux2-kustomize-helm-example/blob/main/clusters/staging/infrastructure.yaml