Update Quickstart docs

This commit is contained in:
Stefan Reimer 2020-06-05 16:38:46 +01:00
parent 80ab077733
commit e5024e3fc8

View File

@ -20,6 +20,9 @@
## Deploy Worker group ## Deploy Worker group
- cloudbender sync kube-workers - 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 # KubeZero
@ -27,17 +30,25 @@
## Prepare Config ## Prepare Config
- check values.yaml - 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 KubeZero Helm chart
`./deploy.sh` `./deploy.sh`
## Verify ArgoCD ## 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. 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/argocd-server -n argocd 8080:443` `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. 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 # Demo / own apps
- Add your own application to ArgoCD via the cli - Add your own application to ArgoCD via the cli