Skip to content

nemonik/k3s-server-role

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

44 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

K3s Server Ansible role

Basic role syntax check

An Ansible role for ensuring the configuration of a master K3s server node.

Requirements

Requires Docker installed.

The role installs on CentOS 7, Alpine 3.10 and Ubuntu Bionic.

Role Variables

Variable Required Default Choices Comments
default_retries yes 60 Integer value default number of retries
default_delay yes 60 Integer value default delay in seconds between retries
k3s_version yes v1.19.4+k3s1 matches release tag k3s version to install
k3s_flannel_iface no not defined String Either provide (e.g., eth0) or the role will
vault_k3s_cluster_secret yes String Please, set via Ansible vault
images_cache_path no not defined Path Path to folder used to cache saved Docker images
cache_container_timeout no 300 seconds Integer value Number of seconds before Ansible times out

Example Playbook

An example can be found used in my Hands-on DevOps course's ansible/master-playbook.yml.

- hosts: masters
  remote_user: vagrant
  roles:
    - common
    - docker
    - k3s-server

The above Ansible playbook uses my

  • Common role to configure the instance past the base CentOS 7, Alpine 3.10 or Ubuntu Bionic image
  • Docker role to install and configure Docker
  • K3s-server role to install Lightweight Kubernetes (K3s)

For more information and to see this role put into action checkout my Hands-on DevOps class project.

Setting the k3s cluster secret

The K3s cluster secret is set by vault_k3s_cluster_secret. Please, ansible vault this variable.

License

3-Clause BSD License

Author Information

Michael Joseph Walsh [email protected]

Releases

No releases published

Packages

No packages published