[deprecated] Initial ansible proof of concept

[ventifus]

What this PR does / why we need it:

We have been running smoketests in regions manually. This is error-prone and needs to be automated. As a first step here is the minimum viable Ansible playbook that creates a cluster, waits for it to become healthy via kube api, runs az aro update, then deletes the cluster. This is designed to run Ansible from a container so that users' development hosts don't need to have Ansible installed and will facilitate running smoketests in an automated fashion in the future.

This will allow us to evaluate the following questions:

• Do we want an Ansible dependency in our codebase?
• What smoke tests do we want? (see https://docs.google.com/document/d/1K9Qffl5CuRr_PpeAKI4ik6Rl4je1p-rdf6_xZXJZzVM)

Test plan for issue:

To test, make sure you've got a valid az login session. This is passed through to the container via your ~/.azure directory.

Then run

$ make smoketest

This will first build the required aro-smoketest container image if it doesn't exist, then it will execute ansible-playbook in the container. By default, the /smoketest files are baked into the container image to ensure when this is automated in the future the ansible playbook is in a known state. To test local changes, use the

$ make smoketest-dev

target; this will mount your /smoketest tree into the container.

To personalize the resulting resource groups, set the CLUSTERPREFIX as desired. For example

$ make smoketest CLUSTERPREFIX=${USER}

The default region used is eastus. Set the REGION parameter to choose a different region:

$ make smoketest REGION=centraluseuap

To choose one or more cluster configurations, set the CLUSTERPATTERN parameter to a wildcard string that matches the cluster scenarios you wish to test:

$ make smoketest CLUSTERPATTERN=smoketest-udr

Currently implemented cluster configurations are:

• smoketest-basic: Simplest cluster, nothing fancy
• smoketest-private: Simple cluster with apiserver and ingress visibility set to private
• smoketest-enc: Encryption-at-host enabled
• smoketest-udr: UserDefinedRouting with a blackhole Route Table
• smoketest-byok: Disk encryption using bring-your-own-key

Is there any documentation that needs to be updated for this PR?

Yes

How do you know this will function as expected in production?

[github-actions]

Please rebase pull request.

[github-actions]

Please rebase pull request.

[pepedocs]

Looks good, I ran make smoketest and I was getting the following error.

docker run --rm -t -v ${AZURE_CONFIG_DIR:-~/.azure}:/opt/app-root/src/.azure:O aro-smoketest:83860bc -i regions/eastus -l smoketest-basic* -e CLUSTERPREFIX=smoketest  smoketest.yaml                                                                                                     
docker: Error response from daemon: invalid mode: O.
See 'docker run --help'.
make: *** [Makefile:304: smoketest] Error 125

I think the error is caused by docker volume mount mode to O which it doesn't support? I thought it was meant for podman overlay.

I guess this is just a nit: I think it would be helpful if we can run a dry-run and see what's going to be installed or add an interactive option for semi-automated use cases (e.g. just want to run it in my laptop and see what's going to be changed before the actual installation).

[bitoku]

Why is this deprecated?