Table of Contents
You can find all of the config files on the GitHub page.
Install HAproxy
I’m using HAproxy as a load balancer for my controller nodes. There isn’t much to it. I used Ubuntu 14.04 LTS and installed it with the following command:
apt-get install haproxy
I used the default config and items after # My edits.
/etc/haproxy/haproxy.cfg
global log /dev/log local0 log /dev/log local1 notice chroot /var/lib/haproxy stats socket /run/haproxy/admin.sock mode 660 level admin stats timeout 30s user haproxy group haproxy daemon maxconn 2048 # Default SSL material locations ca-base /etc/ssl/certs crt-base /etc/ssl/private tune.ssl.default-dh-param 2048 # Default ciphers to use on SSL-enabled listening sockets. # For more information, see ciphers(1SSL). This list is from: # https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/ ssl-default-bind-ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS ssl-default-bind-options no-sslv3 defaults log global mode http option forwardfor option forwardfor option httplog option dontlognull timeout connect 5000 timeout client 50000 timeout server 50000 errorfile 400 /etc/haproxy/errors/400.http errorfile 403 /etc/haproxy/errors/403.http errorfile 408 /etc/haproxy/errors/408.http errorfile 500 /etc/haproxy/errors/500.http errorfile 502 /etc/haproxy/errors/502.http errorfile 503 /etc/haproxy/errors/503.http errorfile 504 /etc/haproxy/errors/504.http # My edits stats enable stats uri /stats stats realm Haproxy\ Statistics stats auth admin:VMware1! frontend kube-api-http bind 192.168.3.201:80 reqadd X-Forwarded-Proto:\ http default_backend www-backend frontend kube-api-https bind 192.168.3.201:6443 ssl crt /etc/ssl/private/kubernetes.pem reqadd X-Forwarded-Proto:\ https default_backend www-backend backend www-backend redirect scheme https if !{ ssl_fc } option httpchk get /healthz http-check expect string ok server kube-controller0 192.168.3.176:8080 check server kube-controller1 192.168.3.177:8080 check server kube-controller2 192.168.3.178:8080 check