Make run eases local interactive tests

[josvazg]

Using make run RUN_YAML=my-k8s-ako-sample-here.yml you get:

• A local kind cluster to run...
• A freshly compiled manager with latest changes in the current terminal process.
• The RUN_YAML file applied after the CRDs are installed and the manager is started, so it will try to enforce the given state.
  No need for ad-hoc scripts to get the same.

It relies on:

• make install-crds to install the latest versions of the CRDs.
• make install-credentials to create the root Atlas Operator credentials secret off your MCLI_ env vars. Remember to have those setup in advance in your terminal.
  • The set-namespace rule ensures the namespace set by $(OPERATOR_NAMESPACE) is in place.

If RUN_YAML is not passed in, make run will only launch the manager binary without any initial Kubernetes definitions in place. You should go to another terminal to apply Kubernetes YAMLs.

You can call make run ... several times in a row but, depending on your testing state, you might find issues with leftover state in Kubernetes or Atlas. To wipe prior Kubernetes state you can do 'make stop-kindandmake run` will relaunch kind on its own.

All Submissions:

• Have you signed our CLA?

[helderjs]

It's a simple and smart way to approach the problem, great idea!
Why not include a clean-up, even as simple as stop kind, to avoid conflicts with leftovers? Do you think is better to deal with it manually?

[josvazg]

It's a simple and smart way to approach the problem, great idea! Why not include a clean-up, even as simple as stop kind, to avoid conflicts with leftovers? Do you think is better to deal with it manually?

We already have make stop-kind which effectively wipes it all clean, at least from the Kubernetes side of things. I use it all the time.

Cleaning up the YAML as well is a bit more tricky, and just an apply away for the developer. Most of interactive tests will require several steps and kubectl apply/delete even before the cleanup.