DerekHeldtWerle opened a new pull request #14152:
URL: https://github.com/apache/airflow/pull/14152


   This PR builds off of and supersedes @jaydesl's work on his 
[PR](https://github.com/apache/airflow/pull/11769) to move forward with 
properly following [helm's rbac best 
practices](https://helm.sh/docs/chart_best_practices/rbac/). This PR updates 
every potential pod that can be deployed to include the option to either create 
or use an existing service account. This is the first step towards supporting 
environments where users have the 
[PodSecurityPolicy](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#podsecuritypolicy)
 admission controller enabled without forcing such users to provide any 
additional permissions to the default service account in the namespace this is 
deployed to.
   
   closes: https://github.com/apache/airflow/issues/11755
   related: https://github.com/apache/airflow/issues/13643 
   
   
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.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.

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


Reply via email to