Hi, I would like to discuss parsing YAML for the Kubernetes worker configuration instead of the current process of programmatically generating the YAML from the Pod and PodRequest Factory as is done currently.
*Motivation:* Kubernetes configuration is quite complex. Instead of using the configuration system that is offered natively by Kubernetes (YAML),the current method involves programmatically recreating this YAML file. Fully re-implementing the configuration in Airflow is taking a lot of time, and at the moment many features available through YAML configuration are not available in Airflow. Furthermore, as the Kubernetes API evolves, the Airflow codebase will have to change with it, and Airflow will be in a constant state of catching up with missing features available. This can all be solved by simply parsing the YAML file. *Idea:* Either pass in the YAML as string or have a path to the YAML file.
