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

chore: add another verification step

Browse Source
This commit is contained in:
Devin Buhl authored and GitHub committed 2022-05-07 05:02:16 -04:00
1 parent 2b8753631c
commit 08b05b0e31
1 file changed
+10 -5
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+10 -5
View File
@@ -322,7 +322,7 @@ If Terraform was ran successfully you can log into Cloudflare and validate the D
### 🎤 Verification Steps ### 🎤 Verification Steps
_Mic check, 1, 2_ _Mic check, 1, 2_ - In a few moments applications should be spinning up in your cluster, give it a few minutes for everything to light up like a Christmas tree 🎄
1. View the Flux kustomizations 1. View the Flux kustomizations
@@ -342,6 +342,13 @@ _Mic check, 1, 2_
kubectl --kubeconfig=./provision/kubeconfig get pods --all-namespaces kubectl --kubeconfig=./provision/kubeconfig get pods --all-namespaces
``` ```
4. View all the certificates and certificate requests
```sh
kubectl --kubeconfig=./provision/kubeconfig get certificates --all-namespaces
kubectl --kubeconfig=./provision/kubeconfig get certificaterequests --all-namespaces
```
🏆 **Congratulations** if all goes smooth you'll have a Kubernetes cluster managed by Flux, your Git repository is driving the state of your cluster. 🏆 **Congratulations** if all goes smooth you'll have a Kubernetes cluster managed by Flux, your Git repository is driving the state of your cluster.
☢️ If you run into problems, you can run `task ansible:nuke` to destroy the k3s cluster and start over. ☢️ If you run into problems, you can run `task ansible:nuke` to destroy the k3s cluster and start over.
@@ -376,8 +383,7 @@ To enable Renovate on your repository, click the 'Configure' button over at thei
Flux is pull-based by design meaning it will periodically check your git repository for changes, using a webhook you can enable Flux to update your cluster on `git push`. In order to configure Github to send `push` events from your repository to the Flux webhook receiver you will need two things: Flux is pull-based by design meaning it will periodically check your git repository for changes, using a webhook you can enable Flux to update your cluster on `git push`. In order to configure Github to send `push` events from your repository to the Flux webhook receiver you will need two things:
1. Webhook URL 1. Webhook URL - Your webhook receiver will be deployed on `https://flux-receiver.${BOOTSTRAP_CLOUDFLARE_DOMAIN}/hook/:hookId`. In order to find out your hook id you can run the following command:
Your webhook receiver will be deployed on `https://flux-receiver.${BOOTSTRAP_CLOUDFLARE_DOMAIN}/hook/:hookId`. In order to find out your hook id you can run the following command:
```sh ```sh
kubectl -n flux-system get receiver/github-receiver --kubeconfig=./provision/kubeconfig kubectl -n flux-system get receiver/github-receiver --kubeconfig=./provision/kubeconfig
@@ -391,8 +397,7 @@ Flux is pull-based by design meaning it will periodically check your git reposit
https://flux-receiver.k8s-at-home.com/hook/12ebd1e363c641dc3c2e430ecf3cee2b3c7a5ac9e1234506f6f5f3ce1230e123 https://flux-receiver.k8s-at-home.com/hook/12ebd1e363c641dc3c2e430ecf3cee2b3c7a5ac9e1234506f6f5f3ce1230e123
``` ```
2. Webhook secret 2. Webhook secret - Your webhook secret can be found by decrypting the `secret.sops.yaml` using the following command:
Your webhook secret can be found by decrypting the `secret.sops.yaml` using the following command:
```sh ```sh
sops -d ./cluster/apps/flux-system/webhooks/github/secret.sops.yaml | yq .stringData.token sops -d ./cluster/apps/flux-system/webhooks/github/secret.sops.yaml | yq .stringData.token