jedcunningham commented on code in PR #62544:
URL: https://github.com/apache/airflow/pull/62544#discussion_r2874684410
##########
chart/docs/manage-logs.rst:
##########
@@ -58,25 +63,28 @@ for details.
.. code-block:: bash
- helm upgrade --install airflow apache-airflow/airflow \
- --set logs.persistence.enabled=true
- # you can also override the other persistence
- # by setting the logs.persistence.* values
- # Please refer to values.yaml for details
+ helm upgrade --install airflow apache-airflow/airflow \
+ --set logs.persistence.enabled=true
+ # You can also override the other persistence
+ # by setting the logs.persistence.* values
+ # Please refer to values.yaml for details
Externally provisioned PVC
--------------------------
-In this approach, Airflow will log to an existing ``ReadWriteMany`` PVC. You
pass in the name of the volume claim to the chart.
+In this approach, Airflow will log to an existing ``ReadWriteMany`` PVC. You
pass in the name of the volume claim to the chart
+by using the ``logs.persistence.existingClaim`` parameter:
.. code-block:: bash
- helm upgrade --install airflow apache-airflow/airflow \
- --set logs.persistence.enabled=true \
- --set logs.persistence.existingClaim=my-volume-claim
+ helm upgrade --install airflow apache-airflow/airflow \
+ --set logs.persistence.enabled=true \
+ --set logs.persistence.existingClaim=my-volume-claim
+
+.. note::
-Note that the volume will need to be writable by the Airflow user. The easiest
way is to ensure GID ``0`` has write permission.
-More information can be found in the :ref:`Docker image entrypoint
documentation <docker-stack:arbitrary-docker-user>`.
+ The volume have to be writable by the Airflow user. The easiest way is to
ensure GID ``0`` has a write permission.
Review Comment:
```suggestion
The volume has to be writable by the Airflow user. The easiest way to do
this is to ensure GID ``0`` has write permission.
```
--
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]
