The method to stop kubelet in worker nodes varies depending on the host configuration.

Host configuration without Bastion

Stop kubelet when the host configuration does not include Bastion.

  1. Using SSH, log in to the VMware Integrated OpenStack with Kubernetes VM.

  2. Run the command: docker exec -it app-api bash

  3. Knowing the cluster ID, change to the directory: cd /var/lib/vrs/terraform/<cluster_id>

  4. For each worker node IP, run:

    • ssh -i private.key ubuntu@<node_ip>

    • systemctl stop kubelet

Host Configuration with Bastion

Stop kubelet when the host configuration includes Bastion.

  1. Using SSH, log in to the VMware Integrated OpenStack with Kubernetes VM.

  2. Run the command: docker exec -it app-api bash

  3. Knowing the cluster ID, change to the directory: cd /var/lib/vrs/terraform/<cluster_id>

  4. Perform the following steps for each worker node IP.

    • On the Bastion host, run:

      ssh -i private.key ubuntu@<node_ip>

    • On other working nodes, run:

      ssh -i private.key -F ssh-bastion.conf ubuntu@<node_ip>

    • Run: systemctl stop kubelet

Without Bastion Host

Stop kubelet without a Bastion host.

  1. Using SSH, log in to the VMware Integrated OpenStack with Kubernetes VM.

  2. Use the OpenStack client to assign a floating IP to each worker node.

  3. Follow the procedure for Host configuration without Bastion.

  4. Use the OpenStack client to unassign the floating IP assigned to each worker node.