Configuring M3DB

By default the operator will apply a configmap with basic M3DB options and settings for the coordinator to direct Prometheus reads/writes to the cluster. This template can be found here.

To apply custom a configuration for the M3DB cluster, one can set the configMapName parameter of the cluster spec to an existing configmap.

Environment Warning

If providing a custom config map, the env you specify in your config must be $NAMESPACE/$NAME, where $NAMESPACE is the Kubernetes namespace your cluster is in and $NAME is the name of the cluster. For example, with the following cluster:

  1. apiVersion: operator.m3db.io/v1alpha1
  2. kind: M3DBCluster
  3. metadata:
  4.   name: cluster-a
  5.   namespace: production
  6. ...

The value of env in your config MUST be production/cluster-a. This restriction allows multiple M3DB clusters to safely share the same etcd cluster.