mirror of
https://github.com/rqlite/rqlite.git
synced 2022-10-30 02:37:32 +03:00
Update KUBERNETES.md
This commit is contained in:
@@ -21,6 +21,6 @@ kubectl apply -f rqlite-3-nodes.yaml
|
||||
Note the `args` passed to rqlite in the YAML file. The arguments tell rqlite to use `dns` discovery mode, and to resolve the DNS name `rqlite-svc-internal` to find the IP addresses of other nodes in the cluster. Furthermore it tells rqlite to wait until three nodes are available (counting itself as one of those nodes) before attempting to form a cluster.
|
||||
|
||||
## Scaling the cluster
|
||||
You can grow the cluster at anytime, simply by setting **both** the replica count **and** `bootstrap-expect` argument to the desired cluster size. Shrinking the cluster, however, will require some manual intervention. As well reducing `replicas` and `bootstrap-expect`, you also need to [explicitly remove](https://github.com/rqlite/rqlite/blob/master/DOC/CLUSTER_MGMT.md#removing-or-replacing-a-node) the deprovisioned nodes, or the Leader will continually attempt to contact those nodes.
|
||||
You can grow the cluster at anytime, simply by setting the replica count to the desired cluster size. Shrinking the cluster, however, will require some manual intervention. As well reducing `replicas`, you will also need to [explicitly remove](https://github.com/rqlite/rqlite/blob/master/DOC/CLUSTER_MGMT.md#removing-or-replacing-a-node) the deprovisioned nodes, or the Leader will continually attempt to contact those nodes.
|
||||
|
||||
> :warning: **Be careful that you don't reduce the replica count such that there is no longer a quorum of nodes available. If you do this you will render your cluster unusable, and need to perform a manual recovery.** The manual recovery process is [fully documented](https://github.com/rqlite/rqlite/blob/master/DOC/CLUSTER_MGMT.md#dealing-with-failure).
|
||||
|
||||
Reference in New Issue
Block a user