i am working on a contribution to let Airflow pods...
# connector-contributions
j
i am working on a contribution to let Airflow pods deployed on Azure kubernetes AKS authenticate to Azure Storage (for logging) using federated identity, rather than connection string as a secret in the cluster. So far much is going well, including the
server
logs showing its getting an id token as intended... i have problems with the job kube labels on source check ... 🧵
in my helm chart i set values
global.jobs.kube.labels
for the azure identity stuff
but when i run a source check i do not see the provided label on the pod thats running
i am trying setting
podLabels
some other places, but wondering if there is the same behaviour for source/destination checks as for sync jobs, regarding the use of jobs.kube to set labels, annotations, tolerations, etc ?
adding podLabels to worker and workload-launcher seems not to help ....
anyone have some time to help with pod labels source/destination checks?