Go to file
Radar231 c6fe8607f5 renamed inventory file
restructured to support more generic k3s single host or cluster deployment
2023-01-07 20:51:52 +00:00
README.md cleanup: removed centos code, cleaned up debian & ubuntu references 2022-01-03 10:08:36 -05:00
ex-inv_k3s.yml renamed inventory file 2023-01-07 20:51:52 +00:00
k3s.yml renamed inventory file 2023-01-07 20:51:52 +00:00

README.md

k3s playbook

Introduction

This is the top level playbook for the 'k3s' role and will install a k3s cluster to three or more target hosts.

This playbook requires at least three target hosts, previously deployed. Each host should have at least 4GB of RAM and at least a 20GB disk.

It is also assumed that the user running the playbook has SSH key access set up for the root user on the target hosts.

NOTE: If you are installing in a proxied environment, make sure that you have either 'HTTP_PROXY' or 'HTTPS_PROXY' (case is not important) defined in your env variables (usually via ~/.bashrc). In addition to that, you also need to have 'NO_PROXY' (again, case is not important) also defined. This is where the k3s installer will retrieve the relevant proxy configuration values.

This playbook can be run using the following command line;

ansible-playbook -i <inventory file> -e "username=<username>" k3s.yml

ie,
ansible-playbook -i k3s_inventory.yml -e "username=someuser" k3s.yml