EliMor opened a new issue #17740: URL: https://github.com/apache/airflow/issues/17740
<!-- Welcome to Apache Airflow! For a smooth issue process, try to answer the following questions. Don't worry if they're not all applicable; just try to include what you can :-) If you need to include code snippets or logs, please put them in fenced code blocks. If they're super-long, please use the details tag like <details><summary>super-long log</summary> lots of stuff </details> Please delete these comment blocks before submitting the issue. --> **Description** <!-- A short description of your feature --> I may be the only one with this use-case but I would love it if I could specify the rules for pod-launcher (give it extra permissions on kube) **Use case / motivation** I'd like to give pod-launcher permission to create and monitor Job type as well as regular pod type. Currently in my deployment I just apply a post-deploy patch to the ClusterRole with the added perms I want but this feels hacky to me. If there's a way to do this better please let me know! <!-- What do you want to happen? Rather than telling us how you might implement this solution, try to take a step back and describe what you are trying to achieve. --> **Are you willing to submit a PR?** <!--- We accept contributions! --> **Related Issues** <!-- Is there currently another issue associated with this? --> -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
