Add docs

Closes #11

roles/index.md

@@ -39,14 +39,20 @@ the way to use these roles is this.
    ansible-playbook -t join site.yml
    ```
 
-4. Copy your updated {term}`kubeconfig` from the init role's file folder to
+4. Enable Kube-VIP on the control planes.
+
+   ```{code-block} shell
+   ansible-playbook -t kv site.yml
+   ```
+
+5. Copy your updated {term}`kubeconfig` from the init role's file folder to
    the appropriate directory.
 
    ```{code-block} shell
    cp roles/init/files/admin.conf $HOME/.kube/config
    ```
 
-5. Verify that your connection works and the cluster is up.
+6. Verify that your connection works and the cluster is up.
 
    ```{code-block} shell
    kubectl get nodes

roles/kv/index.md

@@ -14,10 +14,9 @@ which is best for bare metal deployments.
 
 ## Tasks
 
-The role uses {term}`kubeadm` to handle the initialization of the primary
-control plane.
+This role enables {term}`kube-vip` for cluster networking.
 
-```{literalinclude} /roles/init/tasks/main.yml
+```{literalinclude} /roles/kv/tasks/main.yml
 :language: yaml
 ```
 

roles/kv/tasks/main.yml

@@ -1,3 +1,4 @@
+---
 - name: Ensure manifests directory
   ansible.builtin.file:
     state: directory

roles/reset/index.md

@@ -9,6 +9,9 @@ title: Reset Cluster
 
 ## Reset Role Usage
 
+This role should generally be executed first to attempt to create a fresh
+environment.
+
 ```{literalinclude} /roles/reset/tasks/main.yml
 :language: yaml
 ```

roles/reset/tasks/main.yml

@@ -33,3 +33,11 @@
   ansible.builtin.file:
     dest: /root/reset.md
     state: absent
+- name: Stop containerd
+  ansible.builtin.service:
+    state: stopped
+    name: containerd
+- name: Start containerd
+  ansible.builtin.service:
+    state: started
+    name: containerd