Felix Nehrke
d96523a071
This changes makes it easier to differentiate and understand the different parts of the kubernetes setup. On one hand we have the bare infrastructure (servers, network, etc), on the other hand we have the software (k3s in this case). In the future we'll have a few more parts, like the minimal configuration of the kubernetes cluster, e.g. with a cert-manager. This is easier to manage with helm or terraform than with ansible. Therefore it makes even more sense to split the responsibilities into dedicated directories.
27 lines
769 B
Plaintext
27 lines
769 B
Plaintext
= k3s
|
|
:icons: font
|
|
|
|
This project is responsible for setting up a k3s installation.
|
|
|
|
== Setup
|
|
|
|
The setup requires a `inventory.ini` this should be provided by a previous step.
|
|
|
|
// tag::setup[]
|
|
[source,bash]
|
|
----
|
|
ansible-galaxy install -r requirements.yml # <1>
|
|
ansible-playbook k3s.orchestration.site -i inventory.ini # <2>
|
|
ansible-playbook download-kube-config.yml -i inventory.ini # <3>
|
|
ansible-playbook k3s.orchestration.upgrade -i inventory.ini # <4>
|
|
----
|
|
|
|
<1> Install required ansible collections to create a k3s-cluster (can be omitted in subsequent runs)
|
|
<2> Install k3s
|
|
<3> Download the kube-config to .kube/config
|
|
<4> Update k3s when necessary
|
|
|
|
[IMPORTANT]
|
|
Step 3 will override any existing kube config this might destroy any existing settings!
|
|
// end::setup[]
|