|
| 1 | +Usage: |
| 2 | + |
| 3 | +1. Create dedicated namespace for ZDM Proxy. |
| 4 | + |
| 5 | + ```kubectl create ns zdm-proxy``` |
| 6 | + |
| 7 | +2. Update `values.yaml` file to reflect configuration of your ZDM proxy environment. All files should be placed |
| 8 | + in the same directory as values file. Helm chart will automatically create Kubernetes secrets for passwords, |
| 9 | + TLS certificates and Secure Connection Bundle. |
| 10 | + |
| 11 | +3. Install Helm chart in desired Kubernetes namespace. |
| 12 | + |
| 13 | + ```helm -n zdm-proxy install zdm-proxy zdm``` |
| 14 | + |
| 15 | + The default resource allocations (memory and CPU) are designed for production environment, |
| 16 | + if you see PODs pending due to not enough resources, try to use the following commands instead: |
| 17 | + |
| 18 | + ``` |
| 19 | + helm -n zdm-proxy install --set resources.requests.cpu=1000m --set resources.requests.memory=2000Mi \ |
| 20 | + --set resources.limits.cpu=1000m --set resources.limits.memory=2000Mi zdm-proxy zdm |
| 21 | + ``` |
| 22 | + |
| 23 | +4. Verify that all components are up and running. |
| 24 | + |
| 25 | + ```kubectl -n zdm-proxy get svc,ep,po,secret -o wide --show-labels``` |
| 26 | + |
| 27 | + You can also run `kubectl -n zdm-proxy logs pod/zdm-proxy-0` to see if there are the following entries in the log, |
| 28 | + which means ZDM Proxy is working as expected: |
| 29 | + |
| 30 | + ``` |
| 31 | + time="2022-12-14T21:19:57Z" level=info msg="Proxy connected and ready to accept queries on 172.25.132.116:9042" |
| 32 | + time="2022-12-14T21:19:57Z" level=info msg="Proxy started. Waiting for SIGINT/SIGTERM to shutdown." |
| 33 | + ``` |
| 34 | +
|
| 35 | +5. Optionally you can install monitoring components defined in `monitoring` subfolder. |
| 36 | +
|
| 37 | +6. To generate example load, you can use [NoSQLBench](https://docs.nosqlbench.io/) tool. Check out deployment scripts in `nosqlbench` subfolder. |
| 38 | +
|
| 39 | +7. Basic ZDM Proxy operations. |
| 40 | +
|
| 41 | + - Switch primary cluster to target (all proxy pods will automatically roll-restart after the change). |
| 42 | +
|
| 43 | + ```helm -n zdm-proxy upgrade zdm-proxy zdm --set primaryCluster=TARGET``` |
| 44 | +
|
| 45 | + - Scale to different number of proxy pods. |
| 46 | +
|
| 47 | + ```helm -n zdm-proxy upgrade zdm-proxy ./zdm --set count=5``` |
| 48 | +
|
| 49 | + Note: if you've already switched primary cluster to target, make sure you add `--set primaryCluster=TARGET` |
| 50 | + in this command line as well. An alternative is to directly edit `zdm/values.yaml` then run Helm upgrade. |
| 51 | +
|
| 52 | +8. When you're done, run helm uninstall to remove all objects. |
| 53 | +
|
| 54 | + ```helm -n zdmproxy uninstall zdm-proxy``` |
| 55 | +
|
| 56 | + |
0 commit comments