From 983ba00cc6f6e50d0a08b31aaae49f44e497b144 Mon Sep 17 00:00:00 2001 From: Devin Buhl Date: Sat, 15 Jul 2023 14:58:00 -0400 Subject: [PATCH] chore: clean up readme Signed-off-by: Devin Buhl --- README.md | 20 +------------------- bootstrap/vars/addons.sample.yaml | 2 ++ 2 files changed, 3 insertions(+), 19 deletions(-) diff --git a/README.md b/README.md index 52529b52..72fe00cc 100644 --- a/README.md +++ b/README.md @@ -503,15 +503,7 @@ Flux is pull-based by design meaning it will periodically check your git reposit https://flux-webhook.onedr0p.com/hook/12ebd1e363c641dc3c2e430ecf3cee2b3c7a5ac9e1234506f6f5f3ce1230e123 ``` -2. Webhook secret - Your webhook secret can be found by decrypting the `secret.sops.yaml` using the following command: - - ```sh - sops -d ./kubernetes/apps/flux-system/addons/webhooks/github/secret.sops.yaml | yq .stringData.token - ``` - - **Note:** Don't forget to update the `bootstrap_flux_github_webhook_token` variable in the `config.yaml` file so it matches the generated secret if applicable - -Now that you have the webhook url and secret, it's time to set everything up on the Github repository side. Navigate to the settings of your repository on Github, under "Settings/Webhooks" press the "Add webhook" button. Fill in the webhook url and your secret. +Now that you have the webhook url and secret, it's time to set everything up on the Github repository side. Navigate to the settings of your repository on Github, under "Settings/Webhooks" press the "Add webhook" button. Fill in the webhook url and your `bootstrap_flux_github_webhook_token` secret. ### 💾 Storage @@ -614,16 +606,6 @@ The benefits of a public repository include: -### 💨 Kubernetes Dashboard - -Included in your cluster is the [Kubernetes Dashboard](https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/). Inorder to log into this you will have to get the secret token from the cluster using the command below. - -```sh -kubectl -n monitoring get secret kubernetes-dashboard -o jsonpath='{.data.token}' | base64 -d -``` - -You should be able to access the dashboard at `https://kubernetes.${SECRET_DOMAIN}` - ## 🐛 Debugging Below is a general guide on trying to debug an issue with an resource or application. For example, if a workload/resource is not showing up or a pod has started but in a `CrashLoopBackOff` or `Pending` state. diff --git a/bootstrap/vars/addons.sample.yaml b/bootstrap/vars/addons.sample.yaml index 46419a28..8c6bb684 100644 --- a/bootstrap/vars/addons.sample.yaml +++ b/bootstrap/vars/addons.sample.yaml @@ -19,6 +19,8 @@ kube_prometheus_stack: # https://github.com/kubernetes/dashboard kubernetes_dashboard: enabled: false + # Password can be obtained by running the following command once it is deployed: + # kubectl -n monitoring get secret kubernetes-dashboard -o jsonpath='{.data.token}' | base64 -d # https://github.com/weaveworks/weave-gitops weave_gitops: