Steven Hardy d39a88d63f Allow setting --bind-address for apiserver hyperkube (#1985) ... * Allow setting --bind-address for apiserver hyperkube This is required if you wish to configure a loadbalancer (e.g haproxy) running on the master nodes without choosing a different port for the vip from that used by the API - in this case you need the API to bind to a specific interface, then haproxy can bind the same port on the VIP: root@overcloud-controller-0 ~]# netstat -taupen | grep 6443 tcp 0 0 192.168.24.6:6443 0.0.0.0:* LISTEN 0 680613 134504/haproxy tcp 0 0 192.168.24.16:6443 0.0.0.0:* LISTEN 0 653329 131423/hyperkube tcp 0 0 192.168.24.16:6443 192.168.24.16:58404 ESTABLISHED 0 652991 131423/hyperkube tcp 0 0 192.168.24.16:58404 192.168.24.16:6443 ESTABLISHED 0 652986 131423/hyperkube This can be achieved e.g via: kube_apiserver_bind_address: 192.168.24.16 * Address code review feedback * Update kube-apiserver.manifest.j2		2017-11-29 15:24:02 +00:00
..
defaults	Allow setting --bind-address for apiserver hyperkube (#1985)	2017-11-29 15:24:02 +00:00
handlers	Revert "Support for disabling apiserver insecure port" (#1974)	2017-11-14 13:41:28 +00:00
tasks	Merge pull request #1972 from chadswen/master-static-pod-flush	2017-11-28 11:36:38 -05:00
templates	Allow setting --bind-address for apiserver hyperkube (#1985)	2017-11-29 15:24:02 +00:00
vars	Address standalone kubelet config case	2016-12-13 16:35:53 +01:00