Aakcht commented on PR #24496:
URL: https://github.com/apache/airflow/pull/24496#issuecomment-1159277582

   @dstandish For me the issue is mostly related to airflow helm 
chart/kubernetes: I have the same problem as described in #18283 - I want to 
use the same pre-created secret for both metadata and resultBackendConnection 
in helm chart, see 
https://github.com/apache/airflow/blob/main/chart/values.yaml#L322 .  Currently 
it's not possible because one of the secrets has to start with "db+".
   
   I suppose using sql_alchemy_conn when result_backend is not configured would 
work, but in this case some changes will be required in the helm chart too, 
will it be ok?
   
   For example currently with celery executor [this secret for result_backend 
connection](https://github.com/apache/airflow/blob/main/chart/templates/secrets/result-backend-connection-secret.yaml#L21)
 is created every time when custom result backend secret is not provided and 
the [env for the 
connection](https://github.com/apache/airflow/blob/main/chart/templates/_helpers.yaml#L76)
 is always defined.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to