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

[GitBox <gi...@apache.org>]

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


   Hi @jedcunningham, @potiuk,
   
   Thanks for the quick reply.
   
   I assumed that using standard persistent volume approach was the easiest (I am still a k8s novice) I did not expect that setting up one using azure-file-storage-class (SC) was this easy. These mounts can be set up using 777 rights from the SC yaml file, not sure if this is the sole cure as I also set the uid/gid in the SC mount options. Anyhow, all seems to be working perfectly.
   
   As a reference for otheres here my azure-file-sc.yaml:
   ```
   kind: StorageClass
   apiVersion: storage.k8s.io/v1
   metadata:
     name: airflow-logs
   provisioner: kubernetes.io/azure-file
   mountOptions:
     - dir_mode=0777
     - file_mode=0777
     - uid=50000
     - gid=0
     - mfsymlinks
     - cache=strict
     - actimeo=30
   parameters:
     skuName: Standard_LRS
   ```
   My azure-file-pvc.yaml:
   ```
   apiVersion: v1
   kind: PersistentVolumeClaim
   metadata:
     name: airflow-logs
     namespace: airflow
     labels:
       app: airflow-logs
   spec:
     accessModes:
       - ReadWriteMany
     storageClassName: airflow-logs
     resources:
       requests:
         storage: 20Gi
   ```
   The values.yaml is unchanged.
   
   @potiuk: I have not changed any particular settings regarding uid/gid. Here the PVC mount did not have any permission to create new files, so there is definitely something wrong in the mount options. Are there any similar mountOptions such as with the storage class?
   
   I am closing the bug as it is not really a bug I guess. It probably is some misconfiguration on my side using PV.
   
   Thanks again for the great help, read suggestions, and pointing out the final solution!
   


-- 
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