How to set connection string

[jeff-cook]

I have an existing secret in the airflow namespace with

• endpoint
• password
• port
• username

When I do the following the

  extraEnv: |
    - name: rds_username
      valueFrom:
        secretKeyRef:
          name: airflow-v3-base-rds-access
          key: username
    - name: rds_password
      valueFrom:
        secretKeyRef:
          name: airflow-v3-base-rds-access
          key: password
    - name: rds_address
      valueFrom:
        secretKeyRef:
          name: airflow-v3-base-rds-access
          key: endpoint
    - name: rds_port
      valueFrom:
        secretKeyRef:
          name: airflow-v3-base-rds-access
          key: port
    - name: connection
      value: "postgresql://${rds_username}:${rds_password@$(rds_endpoint):${rds_port}/airflow?sslmode=disable"

I get

env | grep conn
connection=postgresql://${rds_username}:${rds_password@$(rds_endpoint):${rds_port}/airflow?sslmode=disable

How can I get airflow to use the existing secret values?

[jeff-cook]

In our bitnami based airflow we were able to use the following env vars. But that looks to only be supported by bitnami

• AIRFLOW_DATABASE_HOST
• AIRFLOW_DATABASE_USERNAME
• AIRFLOW_DATABASE_PASWORD
• AIRFLOW_DATABASE_PORT

[potiuk]

You could likely use the _CMD version of the connection variable - it should point to a bash script that would combine the variables.

[potiuk]

Just make sure your _CMD script does not produce value with \n (use echo -n). Common issue when you are dealing with this .

[jeff-cook]

The answer was to

• use the _CMD variables
• Set the non _CMD vars to false under enableBuiltInSecretEnvVars
• Use extraConfigMaps to add the script
• volumes and volumeMounts to add the script/configmap to the pods
• Add extraEnvFrom to load the whole existing secret to the env