New generation agent weapon - traefik

traefik Introduce

traefik- Modern reverse agent , It can also be called modern edge routing ;traefik Soundtrack compatible with mainstream clusters ,Kubernetes,Docker,AWS etc. . Official positioning traefik It is a function that allows developers to spend their time on system development and deployment , Not configuration and maintenance . also traefik Officials also provide their own service grid solutions

As a modern edge router ,traefik Have and envoy Similar characteristics

• be based on go Language development , The purpose is to simplify the configuration and maintenance of developers
• tcp/udp Support
• http L7 Support
• GRPC Support
• Service discovery and dynamic configuration
• front/ edge prory Support
• Observability
• Traffic management
• …

traefik The term

To understand trafik, First of all, we need to understand of trafik Some terms in .

• EntryPoints entry point , Is a named network location that can be connected by downstream clients , Be similar to envoy Of listener and nginx Of listen
• services service , Load balancing , The upstream host receives from traefik Connect and request and return a response . Be similar to nginx upstream envoy Of clusters
• Providers Provider , Provides the backend of the configuration file , Such as file ,consul,redis,etcd etc. , Can make traefik Auto update
• routers Router , Analysis request , Transfer the request processing of the downstream host to services
• middlewares: middleware , Transfer the request of the downstream host to services Flow adjustment at

traefik Deployment installation

traefik by go Language development , You can download and run it directly . Here is how to run binary programs directly

Back end environment preparation , Here is docker Two back ends running .

version: '3'
services:
  webserver1:
    image: sealloong/envoy-end:latest
    ports:
    - 91:90
    networks:
      envoymesh:
        aliases:
        - v1_server
        - default_server
    environment: 
    - VERSION=v1
    - COLORFUL=blue
    expose:
    - 90
  webserver2:
    image: sealloong/envoy-end:latest
    ports:
    - 92:90
    networks:
      envoymesh:
        aliases:
        - v1_server
        - default_server
    environment: 
    - VERSION=v1
    - COLORFUL=blue
    expose:
    - 90
networks:
  envoymesh: {
    }

traefik Configuration instructions

Traefik The configuration in can reference two different contents ：

• Fully dynamic routing configuration （ Dynamic configuration ）
• Configure at startup （ Static configuration ）

Static configuration is generally defined traefik Of endpoints And providers, These don't change very often
General definition of dynamic configuration traefik The part that handles browsing , Such as middleware , route , Browse management, etc .

• traefik1 And traefik2 Your configuration file is not compatible

The configuration here is mainly based on file How to explain .

Static configuration part ：

entryPoints:
  web:
    address: :8081
[api]
    dashboard = true
    insecure  = true
providers:
  file:
    filename: ./root.yaml
[accessLog]
  filePath = "/root/access.log"
  format = "json"

Dynamic configuration part

http:
  routers:
    router0:
      rule: "Host(`test.com`)"
      service: "service-foo"
      entryPoints:
      - web
    router1:
      rule: "Path(`/`)"
      service:  "baidu"
      entryPoints:
      - web
  services:
    service-foo:
      loadBalancer:
        servers:
        - url: "http://10.0.0.4:91/"
        - url: "http://10.0.0.4:92/"
    baidu:
      loadBalancer:
        servers:
        - url: http://www.baidu.com/