jedcunningham commented on a change in pull request #20630:
URL: https://github.com/apache/airflow/pull/20630#discussion_r777531348
##########
File path: docs/helm-chart/manage-dags-files.rst
##########
@@ -123,19 +123,19 @@ seconds. If you are using the ``KubernetesExecutor``,
Git-sync will run as an in
# by setting the dags.gitSync.* values
# Refer values.yaml for details
-When using ``apache-airflow>=2.0.0``, :ref:`DAG Serialization
<apache-airflow:dag-serialization>` is enabled by default,
+When using ``apache-airflow >= 2.0.0``, :ref:`DAG Serialization
<apache-airflow:dag-serialization>` is enabled by default,
hence Webserver does not need access to DAG files, so ``git-sync`` sidecar is
not run on Webserver.
Mounting DAGs from an externally populated PVC
----------------------------------------------
-In this approach, Airflow will read the DAGs from a PVC which has
``ReadOnlyMany`` or ``ReadWriteMany`` access mode. You will have to ensure that
the PVC is populated/updated with the required DAGs(this won't be handled by
the chart). You can pass in the name of the volume claim to the chart
+In this approach, Airflow will read the DAGs from a PVC which has
``ReadOnlyMany`` or ``ReadWriteMany`` access mode. You will have to ensure that
the PVC is populated/updated with the required DAGs. (this won't be handled by
the chart) You can pass in the name of the volume claim to the chart.
Review comment:
```suggestion
In this approach, Airflow will read the DAGs from a PVC which has
``ReadOnlyMany`` or ``ReadWriteMany`` access mode. You will have to ensure that
the PVC is populated/updated with the required DAGs (this won't be handled by
the chart). You pass in the name of the volume claim to the chart:
```
--
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]
