k3s-ansible
k3s-ansible copied to clipboard
k3s-io
https://github.com/rancher/k3s-ansible/blob/b508c721ad9de096cc073b8c80bfbaa8ddf6daab/roles/prereq/tasks/main.yml#L35 ``` name: "{{ items }}" ``` should be ``` name: "{{ item }}" ```
Similar to my work in reset.yml (#158), I implemented many of the install flags that are available when using the install script from [https://get.k3s.io](https://get.k3s.io). These are all found in **inventory/sample/group_vars/all.yml**....
The current **reset** role does not remove all network artifacts (#159). I updated the **reset** role to perform the same actions in the same order as **k3s-uninstall.sh** as provided by...
When using **reset.yml**, the **reset** role does not remove: - CNI namespaces - CNI interfaces - flannel interfaces - KUBE iptables rules - CNI iptables rules This issue is similar...
The ~/.kube/config copied from /etc/rancher/k3s/k3s.yaml on the master node remains after a reset.
Symbolic links (to k3s) for kubectl, crictl, and ctr will create a copy of the k3s state under /var/lib/rancher/k3s (the default) if k3s_server_location is set to some other location. This...
**k3s_server_location** was introduced in #133 and can be used to change the location of the data directory (default: /var/lib/rancher/k3s). In **roles/reset/tasks/main.yml**, pkill is used to kill k3s processes with a...
**k3s_server_location** was introduced in #133 but is only used during the installation (**site.yml** playbook). The same location should also be used during uninstallation (**reset.yml** playbook).
