openstack-helm-infra/roles/deploy-env
Vladimir Kozhukalov 05f2f45971 Add 2024.1 overrides to some charts
- Add 2024.1 overrides to those charts where
  there are overrides for previous releases.
- Update some jobs to use 2024.1 overrides.
- Update default images in  grafana, postgresql,
  nagios, ceph-rgw, ceph-provisioners,
  kubernetes-node-problem-detector
- Install tzdata package on K8s nodes. This
  is necessary for kubernetes-node-problem-detector
  chart which mounts /etc/localtime from hosts.

Change-Id: I343995c422b8d35fa902d22abf8fdd4d0f6f7334
2024-07-23 07:35:50 -05:00
..
defaults Add Flannel deployment to deploy-env role 2024-07-15 12:12:48 -05:00
files Setup passwordless ssh from primary to cluster nodes 2024-06-25 12:32:41 -05:00
handlers Add license headers to deploy-env tasks files 2023-12-13 14:19:50 -06:00
tasks Add 2024.1 overrides to some charts 2024-07-23 07:35:50 -05:00
README.md Update deploy-env role to support root user 2024-06-13 15:05:54 -05: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 plane node
  • install Calico as a Kubernetes networking
  • establish tunnel between primary node and K8s control plane ndoe

The role works both for single-node and multi-node inventories. The role totally relies on inventory groups. The primary and k8s_control_plane groups must include only one node and this can be the same node for these two groups.

The primary group is where we install kubectl and helm CLI tools. You can consider this group as a deployer's machine.

The k8s_control_plane is where we deploy the K8s control plane.

The k8s_cluster group must include all the K8s nodes including control plane and worker nodes.

In case of running tests on a single-node environment the group k8s_nodes must be empty. This means the K8s cluster will consist of a single control plane node where all the workloads will be running.

See for example:

all:
  vars:
    ansible_port: 22
    ansible_user: ubuntu
    ansible_ssh_private_key_file: /home/ubuntu/.ssh/id_rsa
    ansible_ssh_extra_args: -o StrictHostKeyChecking=no
  hosts:
    primary:
      ansible_host: 10.10.10.10
    node-1:
      ansible_host: 10.10.10.11
    node-2:
      ansible_host: 10.10.10.12
    node-3:
      ansible_host: 10.10.10.13
  children:
    primary:
      hosts:
        primary:
    k8s_cluster:
      hosts:
        node-1:
        node-2:
        node-3:
    k8s_control_plane:
      hosts:
        node-1:
    k8s_nodes:
      hosts:
        node-2:
        node-3: