fix(post): Fixed ansible docs

Author: timothystewart6

_posts/2022-03-26-k3s-etcd-ansible.md

@@ -10,7 +10,7 @@ tags: k3s rancher etcd ansible cloud-image metallb kube-vip
 
 Setting up k3s is hard.  That's why we made it easy.  Today we'll set up a High Availability K3s cluster using etcd, MetalLB, kube-vip, and Ansible.  We'll automate the entire process giving you an easy, repeatable way to create a k3s cluster that you can run in a few minutes.
 
-A HUGE THANKS to our sponsor, Micro Center! 
+A HUGE THANKS to our sponsor, Micro Center!
 
 New Customers Exclusive – Get a Free 240gb SSD at Micro Center: <https://micro.center/1043bc>
 
@@ -28,28 +28,10 @@ Next, you'll need to fork and clone [the repo](https://github.com/techno-tim/k3s
 git clone https://github.com/techno-tim/k3s-ansible
 ```
 
-Next, you'll want to copy the `sample` directory within the `inventory` directory.
+Next, you'll want to `cd` into the repo and copy the `sample` directory within the `inventory` directory.
 
 ```bash
-cp -R k3s-ansible/inventory/sample inventory/my-cluster
-```
-
-Next, copy the `roles` directory into your playbook directory.
-
-```bash
-cp -R k3s-ansible/roles playbooks/roles
-```
-
-Now copy the `site.yml` to your playbooks directory.
-
-```bash
-cp k3s-ansible/site.yml playbooks/site.yml
-```
-
-For later on, we will also need the `reset.yml` playbook.
-
-```bash
-cp k3s-ansible/reset.yml playbooks/reset.yml
+cp -R inventory/sample inventory/my-cluster
 ```
 
 ## Installing k3s
@@ -92,7 +74,7 @@ extra_agent_args: "--kubelet-arg node-status-update-frequency=5s"
 Start provisioning of the cluster using the following command:
 
 ```bash
-ansible-playbook ./playbooks/site.yml -i ./inventory/my-cluster/hosts.ini
+ansible-playbook ./site.yml -i ./inventory/my-cluster/hosts.ini
 ```
 
 **note: add --ask-pass --ask-become-pass if you are using password SSH login**
@@ -104,7 +86,7 @@ After deployment control plane will be accessible via virtual ip address which i
 To remove k3s from the nodes.  These nodes should be rebooted afterwards due to VIP still being present
 
 ```bash
-ansible-playbook ./playbooks/reset.yml -i ./inventory/my-cluster/hosts.ini
+ansible-playbook ./reset.yml -i ./inventory/my-cluster/hosts.ini
 ```
 
 ## kube config
@@ -132,7 +114,7 @@ kubectl get nodes
 Deploying a sample `nginx` workload
 
 ```bash
-kubectl apply -f k3s-ansible/example/deployment.yml
+kubectl apply -f example/deployment.yml
 ```
 
 Check to be sure it was deployed
@@ -144,7 +126,7 @@ kubectl describe deployment nginx
 Deploying a sample `nginx` service with a `LoadBalancer`
 
 ```bash
-kubectl apply -f k3s-ansible/example/service.yml
+kubectl apply -f example/service.yml
 ```
 
 Check service and be sure it has an IP from metal lb as defined in `inventory/my-cluster/group_vars/all.yml`
@@ -164,8 +146,8 @@ You should see the `nginx` welcome page.
 You can clean this up by running
 
 ```bash
-kubectl delete -f k3s-ansible/example/deployment.yml
-kubectl delete -f k3s-ansible/example/service.yml
+kubectl delete -f example/deployment.yml
+kubectl delete -f example/service.yml
 ```
 
 ## What's next?