Fix firewall to allow etcd client traffic between controllers

* Broaden internal-etcd firewall rule to allow etcd client
traffic (2379) from other controller nodes
* Previously, kube-apiservers were only able to connect to their
node's local etcd peer. While master node outages were tolerated,
reaching a healthy peer took longer than neccessary in some cases
* Reduce time needed to bootstrap a cluster
This commit is contained in:
Dalton Hubble
2018-08-21 23:21:05 -07:00
parent b8eeafe4f9
commit e58b424882
4 changed files with 6 additions and 3 deletions

View File

@ -9,7 +9,7 @@ Provisioning times vary based on the operating system and platform. Sampling the
| AWS | 6 min | 5 min |
| Bare-Metal | 10-15 min | NA |
| Digital Ocean | 3 min 30 sec | 20 sec |
| Google Cloud | 10 min | 4 min 30 sec |
| Google Cloud | 6 min | 4 min 30 sec |
Notes: