From e5024e3fc8edb47c760ff7f64b272b05768763e6 Mon Sep 17 00:00:00 2001 From: Stefan Reimer Date: Fri, 5 Jun 2020 16:38:46 +0100 Subject: [PATCH] Update Quickstart docs --- Quickstart.md | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/Quickstart.md b/Quickstart.md index 67f5bafa..477a532b 100644 --- a/Quickstart.md +++ b/Quickstart.md @@ -20,6 +20,9 @@ ## Deploy Worker group - cloudbender sync kube-workers +## Verify all nodes +- Verify all nodes incl. workers have the expected version and are *Ready*, eg via: `kubectl get nodes` + --- # KubeZero @@ -27,17 +30,25 @@ ## Prepare Config - check values.yaml +Easiest way to get the ARNs for various IAM roles is to use the CloudBender output command: +```cloudbender outputs config/kube-control-plane.yaml``` + ## Deploy KubeZero Helm chart `./deploy.sh` ## Verify ArgoCD -At this stage we there is no support for any kind of Ingress yet. Therefore in order to reach the Argo API you port forwarding. -`kubectl port-forward svc/argocd-server -n argocd 8080:443` +At this stage we there is no support for any kind of Ingress yet. To reach the Argo API port forward from localhost via: +`kubectl port-forward svc/kubezero-argocd-server -n argocd 8080:443` -Next we to download the argo-cd cli, see https://argoproj.github.io/argo-cd/cli_installation/ +Next download the argo-cd cli, details for different OS see https://argoproj.github.io/argo-cd/cli_installation/ Finally login into argo-cd via `argocd login localhost:8080` using the *admin* user and the password set in values.yaml earlier. +List all Argo applications via: `argocd app list`. +Currently it is very likely that you need to manually trigger sync runs for `cert-manager`as well as `kiam`. +eg. `argocd app cert-manager sync` + + # Demo / own apps - Add your own application to ArgoCD via the cli \ No newline at end of file