batulziiy opened a new issue, #29429:
URL: https://github.com/apache/airflow/issues/29429

   ### Official Helm Chart version
   
   1.8.0 (latest released)
   
   ### Apache Airflow version
   
   2.4.1
   
   ### Kubernetes Version
   
   v1.25.5+k3s2
   
   ### Helm Chart configuration
   
   workers:
     extraVolumes:
       - name: sshkey
         secret:
           secretName: airflow-ssh-keys
           defaultMode: 0400
     extraVolumeMounts:
       - mountPath: /home/airflow/.ssh
         name: sshkey
         readOnly: true
   
   
   ### Docker Image customizations
   
   _No response_
   
   ### What happened
   
   Upgraded the helm chart to mount ssh private key as a volume. However, the 
keys mounted with rwx permission for all user. I tried all the ways. But it 
always mounts with 777 permission. 
   - Changed the airflow version to 2.2.5
   - Tried binary, hex syntax of defaultMode
   - added readOnly: true option
   
![image](https://user-images.githubusercontent.com/76592232/217571831-226b5e09-97cf-4d14-ba05-60a705bf16bf.png)
   
   
   
   ### What you think should happen instead
   
   It should be mounted with 0400 permission. 
   
   ### How to reproduce
   
   Deploy the airflow latest version with helm chart with below values. 
   ##value.yaml
   workers:
     extraVolumes:
       - name: sshkey
         secret:
           secretName: airflow-ssh-keys
           defaultMode: 0400
     extraVolumeMounts:
       - mountPath: /home/airflow/.ssh
         name: sshkey
         readOnly: true
   
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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

Reply via email to