[kubernetes_generate_dag_yaml] - Fix dag yaml generate func in version 1.10.14

[Lord-Y]

Signed-off-by: Lord-Y [email protected]

When trying to debug the generated yaml pod to see why I'm not having the right docker image I got this error:

airflow kubernetes generate-dag-yaml DAG_NAME 2021-01-19T20:00:00+00:00

[2021-01-21 09:52:56,314] {{__init__.py:50}} INFO - Using executor KubernetesExecutor
[2021-01-21 09:52:56,317] {{dagbag.py:417}} INFO - Filling up the DagBag from /opt/airflow/dags/airflow-dags.git
Traceback (most recent call last):
  File "/home/airflow/.local/bin/airflow", line 37, in <module>
    args.func(args)
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/utils/cli.py", line 233, in wrapper
    func(args)
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/utils/cli.py", line 81, in wrapper
    return f(*args, **kwargs)
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/bin/cli.py", line 1367, in kubernetes_generate_dag_yaml
    pod = PodGenerator.construct_pod(
TypeError: construct_pod() got an unexpected keyword argument 'kube_executor_config'

After fixing kube_executor_config, I got the same error for worker_config parameter and also kube_image was missing.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (flake8, pylint and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it’s a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

[Lord-Y]

@kaxil Can you get some time to have a look on SQL part :)

[kaxil]

LGTM -- @dimberman any final thoughts ??

[github-actions]

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest master at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.

[boring-cyborg]

Awesome work, congrats on your first merged pull request!