Home > Workload Solutions > Container Platforms > SUSE Containers as a Service > White Papers > Rancher Prime and RKE2 Kubernetes Cluster in APEX Private Cloud with PowerProtect Data Manager > Installing RKE2 cluster’s three nodes manually
Note: All servers must have a valid SLES license and must connect to the SUSE customer center or a local Repository Mirroring Tool (RMT) server. To ensure that the servers have the latest updates, run - zypper update.
To install the three nodes manually, follow these steps.
Note: These steps have been adapted from Quick Start and serve as an example.
$ sudo -i
$ systemctl disable apparmor.service
$ systemctl disable firewalld.service
$ systemctl stop apparmor.service
$ systemctl stop firewalld.service
If swap has not been removed from the disk proposal on the installation, run:
$ systemctl disable swap.target
$ swapoff -a
$ curl -sfL https://get.rke2.io | sh –
In SLES, this script downloads the latest RKE2 tarballs, extracts them in a /tmp directory, and then copies them to their final locations.
Run the following command to download a specific version of RKE2 if needed:
$ curl -sfL https://get.rke2.io |\ INSTALL_RKE2_VERSION=${RKE2_VERSION} sh -
$ mkdir -p /etc/rancher/rke2
$ vi config.yaml
token: my-shared-secret
tls-san:
- rancher.apex.dell.com
- rke2node1.apex.dell.com
- rke2node2.apex.dell.com
- rke2node3.apex.dell.com
Note: RKE2 setup on SLES15 SP4 requires unique hostnames or the node-name parameter set in /etc/rancher/rke2/config.yaml. Multiple nodes require several TCP/UDP ports to be configured properly. For details, see Quick Start.
$ systemctl enable --now rke2-server.service
This command enables the service that was previously installed by running the shell script.
$ mkdir -p /etc/rancher/rke2
$ vi config.yaml
server: https://rancher.apex.dell.com:9345
token: my-shared-secret
tls-san:
- rancher.apex.dell.com
- rke2node1.apex.dell.com
- rke2node2.apex.dell.com
- rke2node3.apex.dell.com
$ systemctl enable --now rke2-server.service
This command enables the service that was previously installed by running the shell script.
$ cp /var/lib/rancher/rke2/bin/kubectl /usr/local/bin
$ export PATH=$PATH:/opt/rke2/bin:/var/lib/rancher/rke2/bin
$ export KUBECONFIG=/etc/rancher/rke2/rke2.yaml
$ kubectl get componentstatuses
$ kubectl get nodes