2.0 KiB

Raw Blame History

TuDatTr IaC

I do not recommend this project being used for ones own infrastructure, as this project is heavily attuned to my specific host/network setup The Ansible Project to provision fresh Debian VMs for my Proxmox instances. Some values are hard coded such as the public key both in ./scripts/debian_seed.sh and ./group_vars/all/vars.yml.

Prerequisites

secrets.yml in the root directory of this repository. Skeleton file can be found as ./secrets.yml.skeleton.
IP Configuration of hosts like in ./host_vars/*
Setup ~/.ssh/config for the respective hosts used.
Install passlib for your operating system. Needed to hash passwords ad-hoc.

Improvable Variables

group_vars/k3s/vars.yml:
- k3s.server.ips: Take list of IPs from host_vars k3s_server*.yml.
- k3s_db_connection_string: Embed this variable in the k3s.db.-directory. Currently causes loop.

Run Playbook

To run a first playbook and test the setup the following command can be executed.

ansible-playbook -i production -J k3s-servers.yml

This will run the ./k3s-servers.yml playbook and execute its roles.

After successful k3s installation

To access our Kubernetes cluster from our host machine to work on it via flux and such we need to manually copy a k3s config from one of our server nodes to our host machine. Then we need to install kubectl on our host machine and optionally kubectx if we're already managing other Kubernetes instances. Then we replace the localhost address inside of the config with the IP of our load balancer. Finally we'll need to set the KUBECONFIG variable.

mkdir ~/.kube/
scp k3s-server00:/etc/rancher/k3s/k3s.yaml ~/.kube/config
chown $USER ~/.kube/config
sed -i "s/127.0.0.1/192.168.20.22/" ~/.kube/config
export KUBECONFIG=~/.kube/config

Install flux and continue in the flux repository.