Skip to content

Commit

Permalink
Updated with proper location of GlusterFS gotchas
Browse files Browse the repository at this point in the history
  • Loading branch information
mrlesmithjr committed May 2, 2018
1 parent f8586a1 commit 3929787
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@
- [Gotchas](#gotchas)
- [sshpass error](#sshpass-error)
- [SSH Key Missing](#ssh-key-missing)
- [Fixing Broken GlusterFS Repo](#fixing-broken-glusterfs-repo)
- [Managing WI-FI On First Node](#managing-wi-fi-on-first-node)
- [Routing](#routing)
- [Adding Static Route On macOS](#adding-static-route-on-macos)
Expand All @@ -52,7 +53,6 @@
- [Heapster](#heapster)
- [InfluxDB/Grafana](#influxdbgrafana)
- [Resetting The Kubernetes Cluster](#resetting-the-kubernetes-cluster)
- [Fixing Broken GlusterFS Repo](#fixing-broken-glusterfs-repo)
- [License](#license)
- [Author Information](#author-information)

Expand Down Expand Up @@ -425,6 +425,12 @@ The key's randomart image is:
+----[SHA256]-----+
```

##### Fixing Broken GlusterFS Repo
If you experience the following [issue](https://github.com/mrlesmithjr/ansible-rpi-k8s-cluster/issues/7) you can
run the playbook [fix_glusterfs_repo.yml](playbooks/fix_glusterfs_repo.yml) which
will remove the broken `3.10` repo. Once that is done you should be good to go
and be able to run [deploy.yml](playbooks/deploy.yml) once again.

### Managing WI-FI On First Node

To manage the WI-FI connection on your first node. You can create a `wifi.yml`
Expand Down Expand Up @@ -873,12 +879,6 @@ run the following `Ansible` playbook which will take care of that for you.
ansible-playbook -i inventory/ playbooks/reset_cluster.yml
```

## Fixing Broken GlusterFS Repo
If you experience the following [issue](https://github.com/mrlesmithjr/ansible-rpi-k8s-cluster/issues/7) you can
run the playbook [fix_glusterfs_repo.yml](playbooks/fix_glusterfs_repo.yml) which
will remove the broken `3.10` repo. Once that is done you should be good to go
and be able to run [deploy.yml](playbooks/deploy.yml) once again.

## License

MIT
Expand Down

0 comments on commit 3929787

Please sign in to comment.