...
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 Three node cluster on which m3db needs to be deployed have to be labelled, before the m3db script is run. The commands :
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
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 |
...