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

   ### Under which category would you file this issue?
   
   Helm chart
   
   ### Apache Airflow version
   
   Any airflow version
   
   ### What happened and how to reproduce it?
   
   Hello, I dont know if it has been asked or what but couldn't find what I 
wanted.
   
   in Airflow since sensitive credentials are stored via environment variables 
(meaning they are pulled securely during build but while it's already running), 
end users can have bashoperator and run `printenv` command and get all 
sensitive credentials regarding database, logging backends, secret backends etc 
which shouldnt be available for end users but admins only. Even if printenv is 
limited there are still other ways to get those credentials from environment.
   
   I want to know what can I do in this scenario ?
   
   ### What you think should happen instead?
   
   Any command could potentially get sensitive credentials should be hidden or 
shouldnt have privilege to run specific list of commands
   
   ### Operating System
   
   Linux
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Apache Airflow Provider(s)
   
   _No response_
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Official Helm Chart version
   
   1.21.0
   
   ### Kubernetes Version
   
   1.34.3
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   _No response_
   
   ### 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