Breeze: Running K8S tests with Kind with Breeze

[potiuk]

There is the whole "kind" set of commands that should be implemented in the new Breeze.

There are few sub-commands there that can be implemented gradually.

[edithturn]

@potiuk I would like to take this issue gradually.

[potiuk]

Feel free

[edithturn]

Just adding some context:

"They cover the whole liffecycle of "kubernetes" development:

• deploying and installing kind -> which is greate "Kubernetes-in-docker" solution that allows you to set-up development-grade K8S instances if you have Docker running (very good to master kind if you want to do anythoing K8S)
• Building and deploying Airflow on the kind cluster using Production Image and Helm Chart of Airflow
• Running tools that allow you to debug running Airflow instance (In particular fantastic k9s tool)
• Running tests using Airflow deployed in the Kind cluster" --Jarek

[edithturn]

@potiuk I understand, could I start with this one ./breeze kind-cluster start

I will check how kind is working with Breeze legacy and then try to make it with the breeze.

[potiuk]

Cool

[potiuk]

Hey @edithturn - how is it going :) ? I am reaching the end of my other changes and might pick it up too.

[edithturn]

@potiuk I am so sorry :(, I was thinking to take it today. If I don't make any progress today please feel free to retake it 🙏🏼

[potiuk]

No problem at all :). You are doing that in your free time so no pressure.

[edithturn]

@potiuk let me know if I am going for the right path:

1. In the Developer tools section, I am adding kind-cluster as a command (./breeze --help)

• As options of kind-cluster, I am adding just for now "start", "stop" and "restart".

2. I added a new class in dev/breeze/src/airflow_breeze/utils/kind_command_utils.py, it will contain validations to start/stop...etc kind with airflow version for this: ./breeze-legacy kind-cluster start

Now, --start, --stop, --restart, should they be commands and not options, right? In ./breeze kind-cluster start <-- kind-cluster is a command and start should be a command too

[potiuk]

Yeah "start", "stop", "restart" should be sub-commands rather than flags. They should be multi-level structure (using click.group) as described in https://mauricebrg.com/article/2020/08/advanced_cli_structures_with_python_and_click.html for example

So the user should run:

• breeze kind-cluster start
• breeze kind-cluster stop

etc.

[edithturn]

Thanks, Jarek! :)

[potiuk]

Ey Edith. I wen ahead and implemented it almost from the scratch - with much renewed command line and I am just about to submit PR. This is a mammoth of a change BTW :)