aru-trackunit opened a new issue, #66579:
URL: https://github.com/apache/airflow/issues/66579

   ### Under which category would you file this issue?
   
   Helm chart
   
   ### Apache Airflow version
   
   Latest airflow helm chart 1.21.0
   
   ### What happened and how to reproduce it?
   
   1. Set the following values:
   
   ```
   executor: KubernetesExecutor
   workers:
     kubernetes:
       serviceAccount:
         create: false
         name: airflow
   ```
   
   2. Execute commands
   ```
   helm dependency build
   helm template airflow .
   ```
   
   3. Observe in the rendered output:
   `worker-kubernetes-serviceaccount.yaml` correctly does not create a 
ServiceAccount (respects create: false)
   `worker-serviceaccount.yaml` still creates an airflow-worker ServiceAccount
   The worker Deployment uses serviceAccountName: "airflow-worker" instead of 
"airflow"
   
   ### What you think should happen instead?
   
   IMO service account should not be created.
   Looks like this PR hasn't included it 
https://github.com/apache/airflow/pull/64730/changes
   
   ### Operating System
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Apache Airflow Provider(s)
   
   _No response_
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Official Helm Chart version
   
   Not Applicable
   
   ### Kubernetes Version
   
   1.33
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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