How k3s-io/k3s-ansible works
This Ansible collection provisions and upgrades K3s clusters from an operator-supplied inventory. Its documented workflow invokes the site playbook, which installs K3s on managed hosts and can retrieve kubeconfig; separate capabilities include airgap deployment, server/agent roles, and upgrades. No source excerpts were provided, so role-to-playbook wiring is omitted; edges show only relationships stated in the README.
Main entry points: site.yml Site playbook · inventory-sample.yml Cluster inventory · main.yml Airgap preparation · upgrade.yml Upgrade playbook
Components 14
Provisioning entrypoints
- Cluster inventory
inventory-sample.yml - Site playbook
playbooks/site.yml
Cluster installation
- K3s server role
roles/k3s_server/tasks/main.yml - K3s agent role
roles/k3s_agent/tasks/main.yml - Host prerequisites
roles/prereq/tasks/main.yml - Raspberry Pi setup
roles/raspberrypi/tasks/main.yml - Airgap preparation
roles/airgap/tasks/main.yml
Cluster operations
- Upgrade playbook
playbooks/upgrade.yml - K3s upgrade role
roles/k3s_upgrade/tasks/main.yml - Kubeconfig output
Other components
- Operator
- Managed hosts
- K3s cluster
- External database
Connections 11
- Operator → Site playbook: runs
README.md - Operator → Cluster inventory: configures
README.md - Cluster inventory → Site playbook: configures
README.md - Site playbook → Managed hosts: provisions
README.md - Site playbook → K3s cluster: brings up
README.md - Site playbook → Kubeconfig output: copies
README.md - Operator → Upgrade playbook: runs
README.md - Upgrade playbook → K3s cluster: upgrades
README.md - Operator → Airgap preparation: runs
README.md - Airgap preparation → Managed hosts: prepares
README.md - K3s cluster → External database: uses optionally
README.md