mik-laj opened a new issue #8970:
URL: https://github.com/apache/airflow/issues/8970


   Hello,
   
   A better guide that describes how to use KubernetesPodOperator would be 
useful. This is one of the most frequently used Airflow operators, so many 
users have problems with this operator. 
   https://airflow.readthedocs.io/en/latest/howto/operator/kubernetes.html
   We currently have a guide that does not describe all the basic concepts.  It 
is not very useful for the end user.
   
   It would be fantastic if the following topics were discussed. 
   
   - [ ] How does KubernetesPodOperator work?  Send request via Kubernetes API 
and waiting for the end. Airlfow uses labels to identity pod.
   - [ ] How to define env/configmap/image pull secrets?
   - [ ] How to define limit/requests resources?
   - [ ] How to use KubernetesPodOperaotrs with Private Docker Image Registry?
   - [ ] How does XCOM work and how to use it?
   - [ ] How to debug problems with this operator? kubectl/kubernetes 
logs/kubernetes events 
   - [ ] How to use KubernetesPodOperator with GKE? GKEStartPodOperator
   - [ ] What is the difference between KubernetesPodOperator and 
KubernetesExecutor?
   - [ ] How to deal with common problems? FAQ section
   
   If anyone is interested in this task, I am willing to provide all the 
necessary tips and information. If you are interested in writing a guide, you 
do not have to describe all the sections. Even one section will be very helpful 
and easier to learn about Airflow.
   
   If anyone wants to learn more about this operator, I invite you to read the 
following articles.
   
https://cloud.google.com/composer/docs/how-to/using/using-kubernetes-pod-operator
   https://www.astronomer.io/docs/kubepodoperator/
   https://www.astronomer.io/docs/cli-kubepodoperator/
   
https://medium.com/bluecore-engineering/were-all-using-airflow-wrong-and-how-to-fix-it-a56f14cb0753
   
   


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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to