, , _______________________________
,-----------|'------'| | |
/. '-' |-' |_____________________________|
|/| | |
| .________.'----' _______________________________
| || | || | |
\__|' \__|' |_____________________________|
|‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾|
|________________________________________________________|
|‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾|
|________________________________________________________|
RKE2, also known as RKE Government, is Rancher's next-generation Kubernetes distribution. This Ansible playbook installs RKE2 for both the control plane and workers.
See the docs more information about RKE Government.
The RKE2 Ansible playbook supports all RKE2 Supported Operating Systems
Supported Operating Systems:
SLES:
- 15 SP2 (amd64)
CentOS:
- 7.8 (amd64)
- 8.2 (amd64)
Red Hat:
- 7.8 (amd64)
- 8.2 (amd64)
Ubuntu:
- bionic/18.04 (amd64)
- focal/20.04 (amd64)
Deployment environment must have Ansible 2.9.0+
Server and agent nodes must have passwordless SSH access
First create a new directory based on the sample
directory within the inventory
directory:
cp -R inventory/sample inventory/my-cluster
Second, edit inventory/my-cluster/hosts.ini
to match the system information gathered above. For example:
[server]
192.16.35.12
[agent]
192.16.35.[10:11]
[rke2_cluster:children]
server
agent
If needed, you can also edit inventory/my-cluster/group_vars/all.yml
to match your environment.
Start provisioning of the cluster using the following command:
ansible-playbook site.yml -i inventory/my-cluster/hosts.ini
Added the neeed files to the tarball_install directory.
Further info can be found here
To get access to your Kubernetes cluster just
ssh ec2-user@kubernetes_api_server_host "sudo /var/lib/rancher/rke2/bin/kubectl --kubeconfig /etc/rancher/rke2/rke2.yaml get nodes"
Variables should be set in inventory/cluster/group_vars/rke2_agents.yml
and inventory/cluster/group_vars/rke2_servers.yml
. See sample variables in inventory/sample/group_vars
for reference.
Note: Uninstalling RKE2 deletes the cluster data and all of the scripts.
The offical documentation for fully uninstalling the RKE2 cluster can be found in the RKE2 Documentation.
If you used this module to created the cluster and RKE2 was installed via yum, then you can attempt to run this command to remove all cluster data and all RKE2 scripts.
Replace ec2-user
with your ansible user.
ansible -i 18.217.113.10, all -u ec2-user -a "/usr/bin/rke2-uninstall.sh"
If the tarball method was used then you can attempt to use the following command:
ansible -i 18.217.113.10, all -u ec2-user -a "/usr/local/bin/rke2-uninstall.sh"
On rare occasions you may have to run the uninstall commands a second time.