New standby node registers as master with consul in existing cluster
By default, when spinning up a new database node according to the documentation, it creates a one node database cluster, and registers with consul. We currently use a generic cluster name, so if we spin up a new standby node, it will report itself as a master for the cluster to consul, which will cause some issues if there is already an existing cluster.