Skip to content

Latest commit

 

History

History
89 lines (68 loc) · 3.1 KB

README.md

File metadata and controls

89 lines (68 loc) · 3.1 KB
Raw

vagrant-rke2-airgap

An attempt to install and play with Rancher RKE2 air-gapped installation

Usage

What How
IDK just do it vagrant up
skip provisioning and only bring up the VMs VAGRANT_TRIGGER=false vagrant up
use box of my choice VM_BOX="some/name" vagrant up
provision without the airgap ANSIBLE_AIRGAP=false vagrant up
disable airgap on existing VMs ansible-playbook vagrant-site.yml -t airgap -e "airgap=off"
enable airgap back on existing VMs ansible-playbook vagrant-site.yml -t airgap -e "airgap=on"

Requirements

  • vagrant
  • virtualbox
  • ansible

TLDR;

Vagrant will perform the following:

  • provision VMs as defined in vagrant.yaml
  • execute ansible on your machine:
    • pre-onfigure vagrant VMs
    • prepare RKE2 airgap install with rke2 linux images
    • generate my-cluster inventory for rke2-ansible
  • execute ansible on air-gapped controller machine:
    • install rke2 on all air-gapped cluster VMs

Accessing RKE2 from your host

  1. An alias to kubectl is created on a master server

    alias kubectl='sudo /var/lib/rancher/rke2/bin/kubectl --kubeconfig /etc/rancher/rke2/rke2.yaml'

  2. Port 6443 is forwarded by default from master-01 to localhost

  3. RKE2's /etc/rancher/rke2/rke2.yaml kubeconfig file is saved to /tmp/rke2-ansible.yaml
    Using this file is sufficient to connect from localhost with your favourite k8s tool.

TODOS:

  1. Support more linux os
  2. Add docker registry
  3. Support private repository install method

Stuff used

  • intel OSX ventura (my host OS) - should easily run on your Linux laptop (or maybe even on Windows)
  • vagrant 2.3.4
  • virtualbox 7.04
  • ansible 2.14.1

Vargant Linux distros tested so far

Notes

  1. Vagrant trigger is set to execute after the last machine defined in Vagantfile
    Should you choose to provision VMs selectively the trigger for vagrant.sh is not going to execute.

  2. Since there's a config.yaml bug in rancherfederal/rke2-ansible at present the git repo being pulled is using my rke2-ansible fork

  3. Virtualbox on OSX by default might not allow you to create required interfaces.
    Try creating the following file /etc/vbox/networks.conf

    * 10.0.0.0/8 192.168.0.0/16

  4. There might be funky things going on if you use M1/M2 Apples

  5. Completion time: ~22mins (on my laptop 😉)

Testing

./vagrant-test.sh
  1. Destroy all current VMs
  2. Run and save log to ./testing for all supported Linux distros
  3. Completion time for 6 tested distros so far ~2h