ZeroDownTime/KubeZero
3
0
Fork 0
Code Issues 1 Pull Requests 25 Packages Projects Releases Wiki Activity

more doc updates

Browse Source
This commit is contained in:
Stefan Reimer 2020-07-07 18:51:27 +01:00
parent 0fba2029ea
commit 61f570e207
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Quickstart.md
View File

@ -21,13 +21,15 @@
--- ---
# KubeZero # KubeZero
All configs and scriptss are normally under:
`artifacts/<ENV>/<REGION>/kubezero`
## Prepare Config ## Prepare Config
check values.yaml check values.yaml for your cluster
## Get CloudBender kubezero config ## Get CloudBender kubezero config
Cloudbender creates a kubezero config file, which incl. all outputs from the Cloudformation stacks in `outputs/kube/kubezero.yaml`. Cloudbender creates a kubezero config file, which incl. all outputs from the Cloudformation stacks in `outputs/kube/kubezero.yaml`.
Copy or link that file *next* to the values.yaml for kubezero named as `cloudbender.yaml` - copy kubezero.yaml *next* to the values.yaml named as `cloudbender.yaml`.
## Deploy KubeZero Helm chart ## Deploy KubeZero Helm chart
`./deploy.sh` `./deploy.sh`
@ -72,6 +74,9 @@ To deploy fluentbit only required adjustment is the `fluentd_host=<LOG_HOST>` in
Only adjustment required is the ingress routing config in istio-service.yaml. Adjust as needed before executing: Only adjustment required is the ingress routing config in istio-service.yaml. Adjust as needed before executing:
`deploy.sh` `deploy.sh`
### EFS CSI
- add the EFS fs-ID from the worker cloudformation output into values.yaml and the efs-pv.yaml
- `./deploy.sh`
# Demo / own apps # Demo / own apps
- Add your own application to ArgoCD via the cli - Add your own application to ArgoCD via the cli