Stephen Taylor 426c71f753 Initialize registry_namespaces unconditionally if not initialized
The deploy-env playbook can fail with an error stating that
registry_namespaces is not defined in some cases. This change moves
the initialization of registry_namespaces so that buildset_registry
is not required for it to be set when other conditions are not met.

Change-Id: I160e7d479008fd3afd460382691673b92bd042c9
2023-12-06 12:15:57 -07:00
..
2023-11-24 19:06:08 -06:00
2023-11-24 19:06:08 -06:00
2023-11-24 19:06:08 -06:00

This role is used to deploy test environment which includes

  • install necessary prerequisites including Helm
  • deploy Containerd and a container runtime for Kubernetes
  • deploy Kubernetes using Kubeadm with a single control plain node
  • install Calico as a Kubernetes networking

The role works both for singlenode and multinode inventories and assumes the inventory has the node called primary and the group called nodes.

See for example:

all:
  children:
    ungrouped:
      hosts:
        primary:
          ansible_port: 22
          ansible_host: 10.10.10.10
          ansible_user: ubuntu
          ansible_ssh_private_key_file: /home/ubuntu/.ssh/id_rsa
          ansible_ssh_extra_args: -o StrictHostKeyChecking=no
    nodes:
      hosts:
        node-1:
          ansible_port: 22
          ansible_host: 10.10.10.11
          ansible_user: ubuntu
          ansible_ssh_private_key_file: /home/ubuntu/.ssh/id_rsa
          ansible_ssh_extra_args: -o StrictHostKeyChecking=no
        node-2:
          ansible_port: 22
          ansible_host: 10.10.10.12
          ansible_user: ubuntu
          ansible_ssh_private_key_file: /home/ubuntu/.ssh/id_rsa
          ansible_ssh_extra_args: -o StrictHostKeyChecking=no