Deploying patched container images is difficult

[jrosser]

We needed to patch capo, so took the 0.8.0 code, applied our fix, rebuilt the container, tagged it 0.8.0-fix and put it into our registry.

On the surface it looks possible to override variables in the cluster_api role to pick up a different tag of the image, but in practice this does not work as the version is strongly coupled to the directory name for the 'provider', and the image tag is also specified directly within the provider data.

It would be nice if there was some more decoupling between the release version of capo, the provider data and the specific image tag being referenced in the provider data, then it would be straightforward to apply a bugfix without editing the ansible role.

[okozachenko1203]

clusterctl role has a variable clusterctl_config which allows overrides of clusterctl configuration. Here is how we use in atmosphere.
https://github.com/vexxhost/atmosphere/blob/main/roles/magnum/meta/main.yml#L34-L36
https://github.com/vexxhost/atmosphere/blob/main/roles/magnum/defaults/main.yml#L27-L40
https://github.com/vexxhost/ansible-collection-kubernetes/blob/main/roles/cluster_api/tasks/init.yml#L20
https://github.com/vexxhost/ansible-collection-kubernetes/blob/main/roles/cluster_api/meta/main.yml#L32-L46