...
- m3operatorScript - This script has to run first as it deploys the m3operator. M3operator is a pre-requisite for the m3 cluster deployment.
Make necessary changes in the script as per the cluster details at your end. Helm charts and profile can be found at : operatorHelmChartsAndProfile - m3dbInstallerScript - This script shall install m3db nodes. Helm charts and profile : m3dbHelmCharts
- CollectD-PrometheusScript - This script shall install collectd and prometheus. Helm charts for collectd and prometheus : collectd and prometheus
- Once all pods are deployed correctly, the topology should be like below:
Manual steps for getting the m3db up and running:
As pointed out earlier, we working on some steps which are not automated for the deployment of the stack.
In due course of time, these might as well be automated. But these are steps till then :
1. 3 node cluster on which m3db needs to be deployed have to be labelled . The commands :
| Info |
|---|
| NODES=($(kubectl get nodes --output=jsonpath={.items..metadata.name})) kubectl label node/${NODES[0]} failure-domain.beta.kubernetes.io/region=us-west1 kubectl label node/${NODES[1]} failure-domain.beta.kubernetes.io/region=us-west1 kubectl label node/${NODES[2]} failure-domain.beta.kubernetes.io/region=us-west1 kubectl label node/${NODES[0]} failure-domain.beta.kubernetes.io/zone=us-west1-a --overwrite=true kubectl label node/${NODES[1]} failure-domain.beta.kubernetes.io/zone=us-west1-b --overwrite=true kubectl label node/${NODES[2]} failure-domain.beta.kubernetes.io/zone=us-west1-c --overwrite=true |
Related articles
| Content by Label | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...