using envFrom clears env

[btrepp]

Am using argocd to try to deploy, so want to seperate the secrets out of the helm file.
As such I have,

helm:
      values: |
        authentik:
        envFrom:
        - secretRef:
            name: authentik-secrets

Which seems to be read, but I think this is having the unfortunate effect of clearing all the config from the authentiik server.

Deployment ends up looking like

spec:
      containers:
        - args:
            - server
          env: null
          envFrom:
            - secretRef:
                name: authentik-secrets

and the authentik server pod logs.

{"event": "PostgreSQL connection failed, retrying... (could not connect to server: Connection refused\n\tIs the server running on host \"localhost\" (::1) and accepting\n\tTCP/IP connections on port 5432?\ncould not connect to server: Connection refused\n\tIs the server running on host \"localhost\" (127.0.0.1) and accepting\n\tTCP/IP connections on port 5432?\n)", "level": "info", "logger": "__main__", "timestamp": 1648550029.4643047}``

So it strikes me as a ending up in a very 'default' state. 

Is there an examples of using secrets along with the default config?. I could possibly retype it all in env, but there should be a way to just specify the key as a secret and use the sane defaults for the rest.

[btrepp]

No. It doesn't. It seems the empty authentik: block was killing the templating. Removing that and variables appeared. So not an issue if you get the values.yaml correct