From 9893b6b7a1c128f95ab3d07f9f4df84fc0e7326c Mon Sep 17 00:00:00 2001 From: Stefan Reimer Date: Fri, 5 Jun 2020 17:09:42 +0100 Subject: [PATCH] Update Quickstart docs --- Quickstart.md | 24 +++++++++++++++++++++++- 1 file changed, 23 insertions(+), 1 deletion(-) diff --git a/Quickstart.md b/Quickstart.md index 477a532..06cce91 100644 --- a/Quickstart.md +++ b/Quickstart.md @@ -31,7 +31,7 @@ - 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``` +`cloudbender outputs config/kube-control-plane.yaml` ## Deploy KubeZero Helm chart `./deploy.sh` @@ -50,5 +50,27 @@ Currently it is very likely that you need to manually trigger sync runs for `cer eg. `argocd app cert-manager sync` +# Only proceed any further if all Argo Applications show healthy !! + + +## WIP not yet integrated into KubeZero + +### EFS CSI +To deploy the EFS CSI driver the backing EFS filesystem needs to be in place ahead of time. This is easy to do by enabling the EFS functionality in the worker CloudBender stack. + +- retrieve the EFS: `cloudbender outputs config/kube-control-worker.yaml` and look for *EfsFileSystemId* +- update values.yaml in the `aws-efs-csi` artifact folder as well as the efs_pv.yaml +- execute `deploy.sh` + +### Istio +Istio is currently pinned to version 1.4.X as this is the last version supporting installation via helm charts. + +Until Istio is integrated into KubeZero as well as upgraded to 1.6 we have to install manually. + +- adjust values.yaml +- update domain in `ingress-certificate.yaml` +- update.sh +- deploy.sh + # Demo / own apps - Add your own application to ArgoCD via the cli \ No newline at end of file