devopsleigh/k3s-lab

Raspberry Pi Kubernetes Cluster

Configures a Raspberry Pi Kubernetes (K3S) cluster using Ansible.

Prerequisites

• A Linux host to use as an Ansible server, separate to the cluster
  • This example uses Ubuntu - this is important because installing Ansible differs by distro
  • Tested using Ubuntu 18.04 on WSL
• Basic configuration of the RPi boards
  • Flash Raspbian Lite
  • Add ssh to the root
  • Add a configured wpa_supplicant.conf to the root
  • Set a static IP for each node

Installation

All tasks are to be performed on the Ansible server host.

1. Download the repository:

   git clone https://github.com/devopsleigh/k3s-lab.git
   cd k3s-lab

2. Edit the Ansible inventory:

   nano hosts.ini

    [master]
    k3s-master ansible_host=10.0.0.10
   
    [node]
    k3s-node1 ansible_host=10.0.0.11
    k3s-node2 ansible_host=10.0.0.12
    k3s-node3 ansible_host=10.0.0.13
   
    [cluster:children]
    master
    node
   
    [cluster:vars]
    ansible_user=ansible

3. Set up SSH keys and get the timezone:

   sudo bash config.sh

4. Create the 'ansible' user and set some basic config:

   ansible-playbook baseline.yml -e 'ansible_user=pi' --extra-vars "TZ=$timezone"

5. Configure K3S

   ansible-playbook kubernetes.yml

Uninstall K3S

ansible cluster -a "/usr/local/bin/k3s-uninstall.sh" -b

k3s-lab's Issues

hosts.ini contains hosts irrelevant to this project

omv is not part of the lab

config.sh needs conditional check for keys

Currently commented out, the generation of a key should be conditional on whether it already exists

Need to restart nodes if firmware or distro is upgraded

copy-ssh-keys.sh expects 10. IP range

Parametise, or assume the 10 range from the active host

Latest firmware not config managed

No latest state specified