This repo contains the ansible scripts to bootstrap a CAPI cluster using kind as the jump point to get it started.
This is based on Kubernetes Cluster API Provider OpenStack under the getting started link.
terraform
These are the terraform files used to provision the base kind compute instance to bootstrap the CAPI cluster
Make a copy of terraform.tfvars.example and rename it to terraform.tfvars and fill in the requried parameters
tenant_name = "NeSI_RDC_PROJECT_NAME"
key_pair = "NeSI_RDC_KEYPAIR_NAME"
key_file = "/path/to/nesi_rdc/private_key"
kind_flavor_id = "6b2e76a8-cce0-4175-8160-76e2525d3d3d" # balanced1.2cpu4ram
kind_image_id = "1a0480d1-55c8-4fd7-8c7a-8c26e52d8cbd" # Ubuntu 22.04
vm_user = "IMAGE_USER" # Ubuntu is `ubuntu` as an exxample
kind_security_groups = ["6443_Allow_ALL", "SSH Allow All", "default"]
kind_security_groups need to allow SSH from your ansible host so that the playbooks can run.
clouds.yaml
You will need to ensure you have downloaded the clouds.yaml from the NeSI RDC dashboard and placed it in ~/.config/openstack/clouds.yaml
It is recommended that you use Application Credentials rather then your own credentials.
deployment.sh
To bootstrap the new CAPI cluster run the command
./deployment.sh bootstrap
This will run 3 playbooks.
ansible-playbook setup-infra.yml -e operation=create
This first creates the kind compute instance inside the NeSI RDC
ansible-playbook -i host.ini ansible-kind.yml -u ubuntu --key-file '~/.ssh/id_flexi'
Runs the ansible play ansible-kind.yml that installs kind onto the compute instance, installs the required dependencies to get it setup as a CAPI cluster, Creates a new workload cluster and promotes that to the management cluster.
You will need to update the values in group_vars/servers/servers.yaml with the main value being clouds_yaml_local_location
ansible-playbook setup-infra.yml -e operation=destroy
The final playbook to run is the terraform destroy, this will tear down the kind instance after the new CAPI Management cluster has been created.
If running this outside of the NeSI RDC then you will need to adjust your values based on your cloud proivder. This also all based on the cloud provider running an openstack base