From f2069b296c6767324ce78ad5e3476f37b5f7ce94 Mon Sep 17 00:00:00 2001 From: Smaine Kahlouch Date: Tue, 15 Dec 2015 17:16:19 +0100 Subject: [PATCH] BGP peering and loadbalancing vars are managed in a group_vars file --- README.md | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index c0f380039..9e810477f 100644 --- a/README.md +++ b/README.md @@ -106,14 +106,6 @@ In node-mesh mode the nodes peers with all the nodes in order to exchange routes [k8s-cluster:children] kube-node kube-master - -[paris:vars] -peers=[{"router_id": "10.99.0.2", "as": "65xxx"}, {"router_id": "10.99.0.3", "as": "65xxx"}] -loadbalancer_address="10.99.0.24" - -[usa:vars] -peers=[{"router_id": "10.99.0.34", "as": "65xxx"}, {"router_id": "10.99.0.35", "as": "65xxx"}] -loadbalancer_address="10.99.0.44" ``` ### Playbook @@ -161,6 +153,9 @@ the server address has to be present on both groups 'kube-master' and 'kube-node * Almost all kubernetes components are running into pods except *kubelet*. These pods are managed by kubelet which ensure they're always running * One etcd cluster member per node will be configured. For safety reasons, you should have at least two master nodes. + +* Kube-proxy doesn't support multiple apiservers on startup ([#18174]('https://github.com/kubernetes/kubernetes/issues/18174')). An external loadbalancer needs to be configured. +In order to do so, some variables have to be used '**loadbalancer_apiserver**' and '**apiserver_loadbalancer_domain_name**' ### Network Overlay