Breeze / KinD - support earlier k8s versions, fix recreate and kubectl versioning

[bbenzikry]

This PR covers several small issues;

• Locking breeze to v1.18 seems like a mistake as it;
  1. Prevents testing k8s oriented operators that rely on CRDs such as the spark-on-k8s operator
     which is an issue for many projects in 1.18 due to Extended CRD Validation kubernetes/kubernetes#88076
     A few reference issues:
     CRDs don't pass validation on k8s 1.18 kubeflow/spark-operator#921
     CustomResourceDefinition is invalid at kubernetes 1.18  operator-framework/operator-sdk#3235
     Default value not allowed for in x-kubernetes-list-map-keys kubernetes-sigs/controller-tools#444
  2. Prevents testing workloads on earlier, in-use versions ( EKS, for example, just got to 1.17 this month )

I've added the latest versions from kind ( v1.17.5, v1.16.9 ) and updated the default version to v1.18.6

• breeze kind-cluster recreate did not seem to work even though it's mentioned in the breeze docs.

  Currently throws:

ERROR: Unknown Kind Kubernetes cluster operation: 'recreate'
Should be one of:
start stop restart status deploy test shell

• breeze kind-cluster deploy had a typo in perform_kind_cluster_operation

• kind-cluster kubectl version ignored KUBERNETES_VERSION ( typo )

---

Make sure to mark the boxes below before creating PR: [x]

• Description above provides context of the change
• Unit tests coverage for changes (not needed for documentation changes)
• Commits follow "How to write a good git commit message"
• Relevant documentation is updated including usage instructions.
• I will engage committers as explained in Contribution Workflow Example.

---

In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.

[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: dev@airflow.apache.org
  Slack: https://apache-airflow-slack.herokuapp.com/

[potiuk]

Great! Thanks!

[potiuk]

What we also probably want is to run the tests on those different versions of kubernetes. Would you mind also extending matrix of the kubernetes versions in .github/workflows/ci.yml for Kubernetes tests?

[bbenzikry]

Hi @potiuk, added the changes yesterday, let me know if there's anything else missing

[potiuk]

Fantastic! Thanks @bbenzikry

[boring-cyborg]

Awesome work, congrats on your first merged pull request!

[potiuk]

cc: @kaxil @dimberman - we have now three versions of Kubernetes tested. I am cherry-picking all the changes to 1.10 now.