Merge pull request #3044 from jerryrelmore/patch-4
Clarify etcd deployment script failure mechanism
This commit is contained in:
commit
9172150966
1 changed files with 5 additions and 1 deletions
|
@ -32,7 +32,11 @@ floating IP addresses or not.
|
||||||
- Kubernetes worker nodes
|
- Kubernetes worker nodes
|
||||||
|
|
||||||
Note that the Ansible script will report an invalid configuration if you wind up
|
Note that the Ansible script will report an invalid configuration if you wind up
|
||||||
with an even number of etcd instances since that is not a valid configuration.
|
with an even number of etcd instances since that is not a valid configuration. This
|
||||||
|
restriction includes standalone etcd nodes that are deployed in a cluster along with
|
||||||
|
master nodes with etcd replicas. As an example, if you have three master nodes with
|
||||||
|
etcd replicas and three standalone etcd nodes, the script will fail since there are
|
||||||
|
now six total etcd replicas.
|
||||||
|
|
||||||
### GlusterFS
|
### GlusterFS
|
||||||
The Terraform configuration supports provisioning of an optional GlusterFS
|
The Terraform configuration supports provisioning of an optional GlusterFS
|
||||||
|
|
Loading…
Reference in a new issue