mtulio / ansible-collection-okd-installer Goto Github PK

The cloud_compute Ansible Role does not support to launch spot instances.

Spot is a low-cost option to run resources on AWS, when SNO has been introduced to okd-installer (#24), the deployment used by default with fine tuning on the disk layout, increases the performance of the single node, although we can decrease even more the cost of the compute (almost 2/3) when deploying using spot, instead of on-demand.

Enable the line-length option and fix all occurrences. If it's in the sub modules, we should also fix it for each repository.
It was disabled on the migration process, PR #3

Provide the disconnected profile to provision OKD/OCP clusters in a disconnected environment.

Supported documents:

• https://docs.openshift.com/container-platform/4.12/installing/disconnected_install/index.html

This Collection was created to package all the dependencies to provision the infrastructure resource to create an OCP/OKD cluster on a given provider. Currently, only AWS is supported UPI/Agnostic, but it would be nice to describe the path-to-add the provider using the shared multi-cloud Ansible Roles that manages each stack.

As the model of this Collection was built (delivering only Playbooks and Role, not developing custom modules), it keeps more simple and faster the integration when the Provider already has public Ansible Collections with modules covering all the Stacks, as it is exploring the best of Ansible using community and vendor Collections. On other hand, the Collection will depend on other Collections, which could not be the best approach - design decisions to deliver a solution faster.