From 2c49ccbd03903488420686fa7b48528a762086c1 Mon Sep 17 00:00:00 2001 From: Colin McCarthy Date: Sun, 16 Feb 2020 14:38:18 -0500 Subject: [PATCH] updated Readme K3s install and added Ingress section --- Readme.md | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/Readme.md b/Readme.md index dc58d5f..51d4f09 100644 --- a/Readme.md +++ b/Readme.md @@ -66,7 +66,25 @@ To deploy the monitoring stack on your K3s cluster, there are three parameters t 3. Edit `suffixDomain` to have your node IP with the `.nip.io` suffix. This will be your ingress URL suffix. 4. Set _traefikExporter_ `enabled` parameter to `true` to collect Traefik metrics and deploy dashboard. -After changing these values, run `make` to build the manifests and `kubectl apply -f manifests/` to apply the stack to your cluster. In case of errors on some resources, re-run the command. +After changing these values, to simply deploy the stack, run: +```bash +$ make deploy + +# Or manually: + +$ kubectl apply -f manifests/ + +# It can take a few seconds for the above 'create manifests' command to fully create the following resources, so verify the resources are ready before proceeding. +$ until kubectl get customresourcedefinitions servicemonitors.monitoring.coreos.com ; do date; sleep 1; echo ""; done +$ until kubectl get servicemonitors --all-namespaces ; do date; sleep 1; echo ""; done + +$ kubectl apply -f manifests/ # This command sometimes may need to be done twice (to workaround a race condition). +``` + + +If you get an error from applying the manifests, run the `make deploy` or `kubectl apply -f manifests/` again. Sometimes the resources required to apply the CRDs are not deployed yet. + +## Ingress Now you can open the applications: