ansible-role-k3s/documentation
Alejo Diaz 410a5bf009
Rename `k3s_become_for_all` for `k3s_become`.
2022-01-07 13:34:40 -03:00
..
configuration feat: check for etcd-s3-bucket config and added ipv6 documentation 2021-09-08 19:12:33 +01:00
operations Updated documentation to remove deprecated playbook structures #115 2021-05-15 18:47:27 +01:00
README.md feat: check for etcd-s3-bucket config and added ipv6 documentation 2021-09-08 19:12:33 +01:00
quickstart-cluster.md Rename `k3s_become_for_all` for `k3s_become`. 2022-01-07 13:34:40 -03:00
quickstart-ha-cluster.md Rename `k3s_become_for_all` for `k3s_become`. 2022-01-07 13:34:40 -03:00
quickstart-single-node.md Rename `k3s_become_for_all` for `k3s_become`. 2022-01-07 13:34:40 -03:00

README.md

ansible-role-k3s

This document describes a number of ways of consuming this Ansible role for use in your own k3s deployments. It will not be able to cover every use case scenario but will provide some common example configurations.

Requirements

Before you start you will need an Ansible controller. This can either be your workstation, or a dedicated system that you have access to. The instructions in this documentation assume you are using ansible CLI, there are no instructions available for Ansible Tower at this time.

Follow the below guide to get Ansible installed.

https://docs.ansible.com/ansible/latest/installation_guide/index.html

Quickstart

Below are quickstart examples for a single node k3s server, a k3s cluster with a single control node and HA k3s cluster. These represent the bare minimum configuration.

Example configurations and operations

Configuration

Operations