traefik VS metallb

UPDATE: ATM this is not possible via traefik. I have openend an issue : https://github.com/containous/traefik/issues/4228

;https://uwsgi-docs.readthedocs.io/en/latest/HTTP.htmlhttp = :8080wsgi-file = main.pycallable = wsgi_applicationprocesses = 2enable-threads = truemaster = truereload-mercy = 30worker-reload-mercy = 30log-5xx = truelog-4xx = truedisable-logging = truestats = 127.0.0.1:1717stats-http = truesingle-interpreter= true;https://github.com/containous/traefik/issues/615http-keepalive=trueadd-header = Connection: Keep-Alive

It's implementation-dependent and implementations offer different features, e.g., Nginx, Traefik, HAProxy, etc.

version: "3" services: influx: image: influxdb:1.7 # or any other recent version labels: # SSL endpoint - "traefik.http.routers.influx-ssl.entryPoints=port8086" - "traefik.http.routers.influx-ssl.rule=host(`influx.mydomain.com`)" - "traefik.http.routers.influx-ssl.tls=true" - "traefik.http.routers.influx-ssl.tls.certResolver=le-ssl" - "traefik.http.routers.influx-ssl.service=influx-ssl" - "traefik.http.services.influx-ssl.loadBalancer.server.port=8086" restart: always container_name: influxdb volumes: - influx-data:/var/lib/influxdb environment: # - INFLUXDB_DB= - INFLUXDB_HTTP_ENABLED=true - INFLUXDB_HTTP_AUTH_ENABLED=true # - INFLUXDB_ADMIN_USER= # - INFLUXDB_ADMIN_PASSWORD= grafana: labels: # SSL redirect requires a separate router (https://github.com/containous/traefik/issues/4688#issuecomment-477800500) - "traefik.http.routers.grafana.entryPoints=port80" - "traefik.http.routers.grafana.rule=host(`grafana.mydomain.com`)" - "traefik.http.middlewares.grafana-redirect.redirectScheme.scheme=https" - "traefik.http.middlewares.grafana-redirect.redirectScheme.permanent=true" - "traefik.http.routers.grafana.middlewares=grafana-redirect" # SSL endpoint - "traefik.http.routers.grafana-ssl.entryPoints=port443" - "traefik.http.routers.grafana-ssl.rule=host(`grafana.mydomain.com`)" - "traefik.http.routers.grafana-ssl.tls=true" - "traefik.http.routers.grafana-ssl.tls.certResolver=le-ssl" - "traefik.http.routers.grafana-ssl.service=grafana-ssl" - "traefik.http.services.grafana-ssl.loadBalancer.server.port=3000" image: grafana/grafana container_name: grafana restart: always volumes: - grafana-data:/var/lib/grafana environment: - GF_SERVER_ROOT_URL=https://grafana.mydomain.com - GF_SERVER_DOMAIN=grafana.mydomain.com - GF_USERS_ALLOW_SIGN_UP=false volumes: traefik-data: influx-data: grafana-data:

Hey guys, I want to share a guide I’m pretty proud of which is talking about setting up kubernetes which leverages https://kubespray.io/#/ and https://metallb.universe.tf/ so you can host this yourself most people when spinning up kubernetes opt for k3s or get stuck with all the options or unable to setup the external ips for their services so these tools will eliminate the problem.

Have a closer look at MetallLB.

To avoid that, you can use a combination of haproxy and keepalived, an enterprise grade load balancer like the one from F5 or Citrix. Besides that you can also work with https://kube-vip.io or https://metallb.universe.tf.

Not sure if klipper is usable in a cluster with multiple nodes, as it binds to one port only. You may want to use MetalLB instead: https://metallb.universe.tf/

Then deploy MetalLB https://metallb.universe.tf/

What issue do you see with the load balancer? For self hosted clusters, one can use MetalLB for example to have such single outfacing IP which will failover to another node keeping the same IP if a node dies.

Quoting from their docs:

metalLB to manage bare-metal LoadBalancer services - WIP - Only L2 configuration can be set-up via playbook.