Kubernetes Ingress backend

Træfɪk can be configured to use Kubernetes Ingress as a backend configuration:

  1. ################################################################
  2. # Kubernetes Ingress configuration backend
  3. ################################################################
  4. # Enable Kubernetes Ingress configuration backend
  5. #
  6. # Optional
  7. #
  8. [kubernetes]
  10. # Kubernetes server endpoint
  11. #
  12. # When deployed as a replication controller in Kubernetes,
  13. # Traefik will use env variable KUBERNETES_SERVICE_HOST
  14. # and KUBERNETES_SERVICE_PORT_HTTPS as endpoint
  15. # Secure token will be found in /var/run/secrets/kubernetes.io/serviceaccount/token
  16. # and SSL CA cert in /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
  17. #
  18. # Optional
  19. #
  20. # endpoint = "http://localhost:8080"
  21. # namespaces = ["default","production"]
  22. #
  23. # See: http://kubernetes.io/docs/user-guide/labels/#list-and-watch-filtering
  24. # labelselector = "A and not B"
  25. #

Annotations can be used on containers to override default behaviour for the whole Ingress resource:

  • traefik.frontend.rule.type: PathPrefixStrip: override the default frontend rule type (Default: PathPrefix).
    Annotations can be used on the Kubernetes service to override default behaviour:

  • traefik.backend.loadbalancer.method=drr: override the default wrr load balancer algorithm

  • traefik.backend.loadbalancer.sticky=true: enable backend sticky sessions
    You can find here an example ingress and replication controller.

Additionally, an annotation can be used on Kubernetes services to set the circuit breaker expression for a backend.

  • traefik.backend.circuitbreaker: <expression>: set the circuit breaker expression for the backend (Default: nil).