Added additional instructions for using cloud-init images with Rocky 10 and Alma 10. |
||
|---|---|---|
| .github | ||
| collections | ||
| example | ||
| inventory | ||
| molecule | ||
| roles | ||
| templates | ||
| .ansible-lint | ||
| .editorconfig | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| .yamllint | ||
| LICENSE | ||
| README.md | ||
| ansible.example.cfg | ||
| buildk3s.sh | ||
| deploy.sh | ||
| galaxy.yml | ||
| reboot.sh | ||
| reboot.yml | ||
| requirements.in | ||
| requirements.txt | ||
| reset.sh | ||
| reset.yml | ||
| site.yml | ||
README.md
About this fork
See this issue for where this comes from. This updates a few versions:
- k3s to v1.34.2+k3s1 (also tested with v1.35.0+k3s1)
- Calico to v3.31.0
- Cilium to v1.18.5 (also tested with 1.19.0)
- All playbooks have been modified to reflect this and are working.
- Small disclaimer: the original playbook was tested for Debian, Ubuntu and Rocky. I use Ubuntu 24.04 / 26.04 usually, but it works with Rocky 10, Alma 10 and Debian 13. If you're using (minimal) cloud-init style images for Rocky 10 and Alma 10 you'll need to install extra kernel modules; you can do so by running
sudo dnf install -y kernel-modules kernel-modules-extrafollowed bysudo rebootandsudo modprobe br_netfilterbefore running the whole playbook. More about that can be found on this page.
See the readme in the original repo for more information.
Branches
There is another branch with an added feature of deploying Longhorn in your cluster as part of the playbook, which can be convenient. You can check it out here.
Example deployments
If you're looking for some examples of stuff to run on K3S in a homelab setting, you can check out my other repo.
Thanks 🤝
This repo is really standing on the shoulders of giants. Thank you to all those who have contributed and thanks to these repos for code and ideas: