infra/home-cluster
2
0 Fork 0
Code Issues Pull Requests 40 Actions Packages Projects Releases Wiki Activity

feat: move kubeconfig to provision folder during ansible k3s-install (#91)

Browse Source 
* feat: move kubeconfig to provision folder during ansible k3s-install

Signed-off-by: Devin Buhl <devin.kray@gmail.com>

* fix: update kubeconfig refereces

Signed-off-by: Devin Buhl <devin.kray@gmail.com>
This commit is contained in:
Devin Buhl authored and GitHub committed 2021-09-30 14:52:00 -04:00
1 parent 925a541ae0
commit 7f406b8d39
4 files changed
+14 -9
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

README.md
+2 -4
View File
@@ -207,7 +207,7 @@ In order to use Terraform and `cert-manager` with the Cloudflare DNS challenge y
### :sailboat:&nbsp; Installing k3s with Ansible
:round_pushpin: Here we will be running a Ansible Playbook to install [k3s](https://k3s.io/) with [this](https://galaxy.ansible.com/xanmanning/k3s) wonderful k3s Ansible galaxy role. After completion, Ansible will drop a `kubeconfig` in `/tmp/kubeconfig` for use with interacting with your cluster with `kubectl`. This file should be manually copied to the root of your repository.
:round_pushpin: Here we will be running a Ansible Playbook to install [k3s](https://k3s.io/) with [this](https://galaxy.ansible.com/xanmanning/k3s) wonderful k3s Ansible galaxy role. After completion, Ansible will drop a `kubeconfig` in `./provision/kubeconfig` for use with interacting with your cluster with `kubectl`.
1. Verify Ansible can view your config by running `task ansible:list`
@@ -217,9 +217,7 @@ In order to use Terraform and `cert-manager` with the Cloudflare DNS challenge y
4. If everything goes as planned you should see Ansible running the k3s install Playbook against your nodes.
5. Copy the `kubeconfig` file from `/tmp` to your repository.
6. Verify the nodes are online
5. Verify the nodes are online
```sh
kubectl --kubeconfig=./provision/kubeconfig get nodes