Calico uses the loadbalancer to reach etcd if 'loadbalancer_address' is defined. The loadbalancer has to be configured first
This commit is contained in:
parent
1568cbe8e9
commit
3cbcd6f189
2 changed files with 2 additions and 2 deletions
|
@ -12,7 +12,7 @@
|
|||
- name: Calico | Configure calico-node desired pool
|
||||
shell: calicoctl pool add {{ kube_pods_subnet }}
|
||||
environment:
|
||||
ETCD_AUTHORITY: "{{ groups['kube-master'][0] }}:2379"
|
||||
ETCD_AUTHORITY: "{{ loadbalancer_address | default(groups['kube-master'][0]) }}:2379"
|
||||
run_once: true
|
||||
|
||||
- name: Calico | Write calico-node systemd init file
|
||||
|
|
|
@ -10,7 +10,7 @@ KUBERNETES_MASTER={{ groups['kube-master'][0] }}
|
|||
|
||||
# Location of etcd cluster used by Calico. By default, this uses the etcd
|
||||
# instance running on the Kubernetes Master
|
||||
ETCD_AUTHORITY={{ groups['kube-master'][0] }}:2379
|
||||
ETCD_AUTHORITY={{ loadbalancer_address | default(groups['kube-master'][0]) }}:2379
|
||||
|
||||
# The kubernetes-apiserver location - used by the calico plugin
|
||||
KUBE_API_ROOT=http://{{ groups['kube-master'][0] }}:{{kube_apiserver_insecure_port}}/api/v1/
|
||||
|
|
Loading…
Reference in a new issue