Adding Hosts to an Existing Cluster

You are viewing documentation for a release that is no longer supported. The latest supported version of version 3 is [3.11]. For the most recent version 4, see [4]

You are viewing documentation for a release that is no longer supported. The latest supported version of version 3 is [3.11]. For the most recent version 4, see [4]

Adding hosts

You can add new hosts to your cluster by running the scaleup.yml playbook. This playbook queries the master, generates and distributes new certificates for the new hosts, and then runs the configuration playbooks on only the new hosts. Before running the scaleup.yml playbook, complete all prerequisite host preparation steps.

The scaleup.yml playbook configures only the new host. It does not update NO_PROXY in master services, and it does not restart master services.

You must have an existing inventory file,for example /etc/ansible/hosts, that is representative of your current cluster configuration in order to run the scaleup.yml playbook.

See the cluster limits section for the recommended maximum number of nodes.

Procedure

  1. Ensure you have the latest playbooks by updating the atomic-openshift-utils package:

    1. # yum update atomic-openshift-utils

  2. Edit your /etc/ansible/hosts file and add new_<host_type> to the [OSEv3:children] section:

    For example, to add a new node host, add new_nodes:

    1. [OSEv3:children]
    2. masters
    3. nodes
    4. new_nodes

    To add new master hosts, add new_masters.

  3. Create a [new_<host_type>] section to specify host information for the new hosts. Format this section like an existing section, as shown in the following example of adding a new node:

    1. [nodes]
    2. master[1:3].example.com
    3. node1.example.com openshift_node_group_name='node-config-compute'
    4. node2.example.com openshift_node_group_name='node-config-compute'
    5. infra-node1.example.com openshift_node_group_name='node-config-infra'
    6. infra-node2.example.com openshift_node_group_name='node-config-infra'
    8. [new_nodes]
    9. node3.example.com openshift_node_group_name='node-config-infra'

    See Configuring Host Variables for more options.

    When adding new masters, add hosts to both the [new_masters] section and the [new_nodes] section to ensure that the new master host is part of the OpenShift SDN.

    1. [masters]
    2. master[1:2].example.com
    4. [new_masters]
    5. master3.example.com
    7. [nodes]
    8. master[1:2].example.com
    9. node1.example.com openshift_node_group_name='node-config-compute'
    10. node2.example.com openshift_node_group_name='node-config-compute'
    11. infra-node1.example.com openshift_node_group_name='node-config-infra'
    12. infra-node2.example.com openshift_node_group_name='node-config-infra'
    14. [new_nodes]
    15. master3.example.com

    If you label a master host with the node-role.kubernetes.io/infra=true label and have no other dedicated infrastructure nodes, you must also explicitly mark the host as schedulable by adding openshift_schedulable=true to the entry. Otherwise, the registry and router pods cannot be placed anywhere.

  4. Run the scaleup.yml playbook. If your inventory file is located somewhere other than the default of /etc/ansible/hosts, specify the location with the -i option.

    • For additional nodes:

      1. # ansible-playbook [-i /path/to/file] \
      2.     /usr/share/ansible/openshift-ansible/playbooks/openshift-node/scaleup.yml

    • For additional masters:

      1. # ansible-playbook [-i /path/to/file] \
      2.     /usr/share/ansible/openshift-ansible/playbooks/openshift-master/scaleup.yml

  5. Set the node label to logging-infra-fluentd=true, if you deployed the EFK stack in your cluster.

    1. # oc label node/new-node.example.com logging-infra-fluentd=true

  6. After the playbook runs, verify the installation.

  7. Move any hosts that you defined in the [new_<host_type>] section to their appropriate section. By moving these hosts, subsequent playbook runs that use this inventory file treat the nodes correctly. You can keep the empty [new_<host_type>] section. For example, when adding new nodes:

    1. [nodes]
    2. master[1:3].example.com
    3. node1.example.com openshift_node_group_name='node-config-compute'
    4. node2.example.com openshift_node_group_name='node-config-compute'
    5. node3.example.com openshift_node_group_name='node-config-compute'
    6. infra-node1.example.com openshift_node_group_name='node-config-infra'
    7. infra-node2.example.com openshift_node_group_name='node-config-infra'
    9. [new_nodes]

Adding etcd Hosts to existing cluster

You can add new etcd hosts to your cluster by running the etcd scaleup playbook. This playbook queries the master, generates and distributes new certificates for the new hosts, and then runs the configuration playbooks on the new hosts only. Before running the etcd scaleup.yml playbook, complete all prerequisite host preparation steps.

To add an etcd host to an existing cluster:

  1. Ensure you have the latest playbooks by updating the openshift-ansible package:

    1. $ yum update openshift-ansible

  2. Edit your /etc/ansible/hosts file, add new_<host_type> to the [OSEv3:children] group and add hosts under the new_<host_type> group:

    For example, to add a new etcd, add new_etcd:

    1. [OSEv3:children]
    2. masters
    3. nodes
    4. etcd
    5. new_etcd
    7. [etcd]
    8. etcd1.example.com
    9. etcd2.example.com
    11. [new_etcd]
    12. etcd3.example.com

  3. Run the etcd scaleup.yml playbook. If your inventory file is located somewhere other than the default of /etc/ansible/hosts, specify the location with the -i option.

    1. $ ansible-playbook [-i /path/to/file] \
    2.   /usr/share/ansible/openshift-ansible/playbooks/openshift-etcd/scaleup.yml

  4. After the playbook completes successfully, verify the installation.

Replacing existing masters with etcd colocated

Follow these steps when you are migrating your machines to a different data center and the network and IPs assigned to it will change.

  1. Back up the primary etcd and master nodes.

    Ensure that you back up the /etc/etcd/ directory, as noted in the etcd backup instructions.

  2. Provision as many new machines as there are masters to replace.

  3. Add or expand the cluster. for example, if you want to add 3 masters with etcd colocated, scale up 3 master nodes.

In the initial release of OKD version 3.11, the scaleup.yml playbook does not scale up etcd. This will be fixed in a future release on BZ#1628201.

  1. Add a master. In step 3 of that process, add the host of the new data center in [new_masters] and [new_nodes] and run the master scaleup.yml playbook.

  2. Put the same host in the etcd section and run the etcd scaleup.yml playbook.

  3. Verify that the host was added:

    1. # oc get nodes

  4. Verify that the master host IP was added:

    1. # oc get ep kubernetes

  5. Verify that etcd was added. The value of ETCDCTL_API depends on the version being used:

    1. # source /etc/etcd/etcd.conf
    2. # ETCDCTL_API=2 etcdctl --cert-file=$ETCD_PEER_CERT_FILE --key-file=$ETCD_PEER_KEY_FILE \
    3.   --ca-file=/etc/etcd/ca.crt --endpoints=$ETCD_LISTEN_CLIENT_URLS member list

  6. Copy /etc/origin/master/ca.serial.txt from the /etc/origin/master directory to the new master host that is listed first in your inventory file. By default, this is /etc/ansible/hosts.

    1. Remove the etcd hosts.

  7. Copy the /etc/etcd/ca directory to the new etcd host that is listed first in your inventory file. By default, this is /etc/ansible/hosts.

  8. Remove the old etcd clients from the master-config.yaml file:

    1. # grep etcdClientInfo -A 11 /etc/origin/master/master-config.yaml

  9. Restart the masters:

    1. # master-restart api
    2. # master-restart controllers

  10. Remove the old etcd members from the cluster. The value of ETCDCTL_API depends on the version being used:

    1. # source /etc/etcd/etcd.conf
    2. # ETCDCTL_API=2 etcdctl --cert-file=$ETCD_PEER_CERT_FILE --key-file=$ETCD_PEER_KEY_FILE \
    3.  --ca-file=/etc/etcd/ca.crt --endpoints=$ETCD_LISTEN_CLIENT_URLS member list

  11. Take the IDs from the output of the command above and remove the old members using the IDs:

    1. # etcdctl --cert-file=$ETCD_PEER_CERT_FILE --key-file=$ETCD_PEER_KEY_FILE \
    2.  --ca-file=/etc/etcd/ca.crt --endpoints=$ETCD_LISTEN_CLIENT_URL member remove 1609b5a3a078c227

  12. Stop the etcd services on the old etcd hosts by removing the etcd pod definition:

    1. # mkdir -p /etc/origin/node/pods-stopped
    2. # mv /etc/origin/node/pods/* /etc/origin/node/pods-stopped/

    1. Shut down old master API and controller services by moving definition files out of the static pods dir /etc/origin/node/pods:

      1. # mkdir -p /etc/origin/node/pods/disabled
      2. # mv /etc/origin/node/pods/controller.yaml /etc/origin/node/pods/disabled/:

    2. Remove the master nodes from the HA proxy configuration, which was installed as a load balancer by default during the native installation process.

    3. Decommission the machine.

  13. Stop the node service on the master to be removed by removing the pod definition and rebooting the host:

    1. # mkdir -p /etc/origin/node/pods-stopped
    2. # mv /etc/origin/node/pods/* /etc/origin/node/pods-stopped/
    3. # reboot

  14. Delete the node resource:

    1. # oc delete node

Migrating the nodes

You can migrate nodes individually or in groups (of 2, 5, 10, and so on), depending on what you are comfortable with and how the services on the node are run and scaled.

  1. For the migration node or nodes, provision new VMs for the node’s use in the new data center.

  2. To add the new node, scale up the infrastructure. Ensure the labels for the new node are set properly and that your new API servers are added to your load balancer and successfully serving traffic.

  3. Evaluate and scale down.

    1. Mark the current node (in the old data center) unscheduled.

    2. Evacuate the node, so that pods on it are scheduled to other nodes.

    3. Verify that the evacuated services are running on the new nodes.

  4. Remove the node.

    1. Verify that the node is empty and does not have running processes.

    2. Stop the service or delete the node.