Aakcht opened a new pull request, #31865: URL: https://github.com/apache/airflow/pull/31865
Global pod security context (`.Values.securityContexts.pod` parameter) is not propagated to statsd deployment when statsd security context is not specified. However at the same time container security context is propagated(`.Values.securityContexts.containers` parameter). According to documentation looks like it should be propagated, see https://github.com/apache/airflow/blob/main/chart/values.schema.json#L4806 and https://github.com/apache/airflow/blob/main/chart/values.yaml#L1588 . I think it would be convinient to be able to propagate global security context to statsd deployment, so instead of changing documentation I added the propagation of global pod security context to statsd deployment. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+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 a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments). -- 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]
