Continental Innovates with Rancher and Kubernetes
In this tutorial, you will learn one way to set up Linux nodes for the Rancher management server. These nodes will fulfill the node requirements for OS, Docker, hardware, and networking.
If the Rancher server will be installed on an RKE Kubernetes cluster, you should provision three instances.
If the Rancher server will be installed on a K3s Kubernetes cluster, you only need to provision two instances.
If the Rancher server is installed in a single Docker container, you only need one instance.
ami-0d1cd67c26f5fca19 (64-bit x86)
t2.medium
Result: You have created Rancher nodes that satisfy the requirements for OS, hardware, and networking. Next, you will install Docker on each node.
sudo ssh -i [path-to-private-key] ubuntu@[public-DNS-of-instance]
sudo usermod -aG docker ubuntu
curl https://releases.rancher.com/install-docker/18.09.sh | sh
To find out whether a script is available for installing a certain Docker version, refer to this GitHub repository, which contains all of Rancher’s Docker installation scripts.
Result: You have set up Rancher server nodes that fulfill all the node requirements for OS, Docker, hardware and networking.
If you are going to install an RKE cluster on the new nodes, take note of the IPv4 Public IP and Private IP of each node. This information can be found on the Description tab for each node after it is created. The public and private IP will be used to populate the address and internal_address of each node in the RKE cluster configuration file, rancher-cluster.yml.
address
internal_address
rancher-cluster.yml
RKE will also need access to the private key to connect to each node. Therefore, you might want to take note of the path to your private keys to connect to the nodes, which can also be included in the rancher-cluster.yml under the ssh_key_path directive for each node.
ssh_key_path