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

   ### Description
   
   When we use `KubernetesPodOperator`, we need to create `KubernetesHook` in 
order to connect to Kubernetes services. There are currently 3 supported 
methods for creating `KubernetesHook`: 
   1、environment variable method, 
   2、kubeconfig_path method, 
   3、db connection variable method. 
   
![image](https://github.com/apache/airflow/assets/28948186/45518f2e-bca7-4ada-a310-814473873228)
   
   
   However, these methods are all from the perspective of the airflow system 
owner. The airflow owner can change the variables of the airflow_worker, create 
and modify files in the airflow_worker, and operate the airflow_db. However, in 
many cases, the users of airflow are not The owner of airflow, The user does 
not have the authority to make changes to the airflow_worker, nor does it have 
read and write permissions to the db, nor should it see the data stored in the 
db by other users.
   
   Therefore, it is best for users to manage their own data rather than hosting 
it on the airflow system. Therefore, in this case, it is a relatively 
reasonable choice to add an optional parameter to receive the kubeconfig text.
   
   ### Use case/motivation
   
   add an optional parameter to receive the kubeconfig text
   
![image](https://github.com/apache/airflow/assets/28948186/231bebb0-3342-45b2-8760-3d990d2a5229)
   
   
   If this proposal is accepted, I will happily submit a PR to support this 
feature
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] 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