Using secretName doesn't pass helm validation

[Edeholland]

I have the following spec for my helmrelease;

apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: devlake
  namespace: devlake
spec:
  releaseName: devlake
  targetNamespace: devlake
  storageNamespace: devlake
  chart:
    spec:
      chart: devlake
      sourceRef:
        kind: HelmRepository
        name: devlake
        namespace: flux-system
  values:
    lake:
      encryptionSecret:
        secretName: devlake-encryption-secret

The secret exists and has content:

kubectl get secrets
NAME                            TYPE                 DATA   AGE
devlake-encryption-secret       Opaque               1      8m51s

However, helm refuses to install because lake.encryptionSecret.secret. isn't set:

kubectl get helmreleases.helm.toolkit.fluxcd.io devlake
NAME      AGE    READY   STATUS
devlake   113m   False   Helm upgrade failed for release devlake/devlake with chart devlake@1.0.1: execution error at (devlake/templates/validate.yaml:2:4): Helm test requires lake.encryptionSecret.secret....

I want to refer to the secret, not set a hardcoded secret. Is this a bug in the validation or am I missing something?

[zjaco13]

If you have the secret already created, set lake.autoCreateSecret to false and it should deploy successfully.