kaxil commented on a change in pull request #18974: URL: https://github.com/apache/airflow/pull/18974#discussion_r771010011
########## File path: docs/helm-chart/production-guide.rst ########## @@ -283,3 +283,52 @@ In order to enable the usage of SCCs, one must set the parameter :ref:`rbac.crea In this chart, SCCs are bound to the Pods via RoleBindings meaning that the option ``rbac.create`` must also be set to ``true`` in order to fully enable the SCC usage. For more information about SCCs and what can be achieved with this construct, please refer to `Managing security context constraints <https://docs.openshift.com/container-platform/latest/authentication/managing-security-context-constraints.html#scc-prioritization_configuring-internal-oauth/>`_. + +Environment variables and secrets +--------------------------------- + +The Helm Chart by default uses Kubernetes Secrets to store secrets that are needed by Airflow. +Content of those secrets is by default turned into environment variables that are read by +Airflow (some of the environment variables have several variants to support older versions of Airflow). + ++------------------------------------------+------------------------------------------------+ +| Secret name in configuration | Airflow Environment Variable | ++==========================================+================================================+ +| ``.Values.data.metadataSecretName`` | ``AIRFLOW_CONN_AIRFLOW_DB`` | ++------------------------------------------+------------------------------------------------+ +| ``.Values.fernetKeySecretName`` | ``AIRFLOW__CORE__FERNET_KEY`` | ++------------------------------------------+------------------------------------------------+ +| ``.Values.data.metadataSecretName`` | ``AIRFLOW__CORE__SQL_ALCHEMY_CONN,`` | Review comment: ```suggestion | ``.Values.data.metadataSecretName`` | ``AIRFLOW__CORE__SQL_ALCHEMY_CONN`` | ``` -- 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]
