You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/07/02 17:59:16 UTC

[GitHub] [airflow] jedcunningham commented on issue #16777: Official Helm chart - unable to get persistent logs using KubernetesExecutor and PV

jedcunningham commented on issue #16777:
URL: https://github.com/apache/airflow/issues/16777#issuecomment-873167223


   Using a hostpath pv almost certainly isn't what you want. You'll want a "real" ReadyWriteMany pv that'll work across nodes too. What you use will depend on your environment, in your case, try Azure Files. I think you can get the volume with the right permissions automatically via StorageClass, but I haven't actually tried it and it sounds like the default is 777 anyways?
   https://docs.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv
   
   If you still have permissions issues (e.g. writable by root only by default) with your new storage provider, then you do have some options. My favorite is to deploy a temporary pod that mounts the pvc to adjust the permissions. This has the benefit of being a one time setup step instead of an init container needing to run with every new pod.
   
   Lastly, `1.0.0` doesn't have support for `extraInitContainers` but it is coming in the next chart release (which should be happening in the next couple weeks).


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org