You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/12/04 06:16:45 UTC

[GitHub] [airflow] XD-DENG commented on issue #28086: Add support to KPO to manage secrets passing Connection-derived credentials

XD-DENG commented on issue #28086:
URL: https://github.com/apache/airflow/issues/28086#issuecomment-1336331268

   >  The best idea is to assign a fixed name to the secret (either connection or dag/task based)
   
   Thinking of a possible case:
   
   What if TWO different Airflow instances are creating Pods (via KPO) in the same Kubernetes namespace? And then it's possible that we have connections in the two Airflow instances with the same connection name, but different values.
   
   This would cause conflict and the job from either Airflow instance would get wrong information.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org