--replicas 3
flag, so that all data is replicated on three Alpha
servers and forms one Alpha group. You can install a highly available cluster
using:
Zero
, Alpha
, and Ratel UI
:
kubectl logs --follow <POD_NAME>
..
http://localhost:8000
to access Dgraph using the Ratel UI.
<MY-CONFIG-VALUES>
. For more
information about the values, see the latest
configuration settings.
<MY-CONFIG-VALUES>.yaml
:
<MY-CONFIG-VALUES>
.yaml and
then install with Alpha and Zero configuration using:
ClusterIP
.
In order to expose the Alpha service and Ratel service publicly you can use
Kubernetes service type LoadBalancer
or an Ingress resource.
LoadBalancer
.Provider | Documentation Reference | Annotation |
---|---|---|
AWS | Amazon EKS: Load Balancing | service.beta.kubernetes.io/aws-load-balancer-internal: "true" |
Azure | AKS: Internal Load Balancer | service.beta.kubernetes.io/azure-load-balancer-internal: "true" |
Google Cloud | GKE: Internal Load Balancing | cloud.google.com/load-balancer-type: "Internal" |
<MY-CONFIG-VALUES>
.yaml file:
helm upgrade
to update the
configuration values of the cluster. Depending on your change, you may need to
upgrade the configuration in multiple steps.
To upgrade to an HA cluster setup:
zero.shardReplicaCount
. For example, set the shard replica flag on the Zero
node group to 3,zero.shardReplicaCount=3
.
alpha.replicaCount=3
.