agoat/routing-mesh-controller Docker 镜像 - 轩辕镜像 | Docker 镜像高效稳定拉取服务

The controller for the ingress routing mesh network to forward web traffic to the backend service containers.

This is one of the two needed containers to establish a routing mesh in a docker swarm installation.

The purpose of this setting (and different to Traefik) is to have the manager with direct Access to the docker instance isolated from the routing container, which is only getting the configuration written by the manager.

Installation

Run docker stack deploy with the following deploy stack:

yaml
Version: "3.8"

services:
  controller:
    image: agoat/routing-mesh-controller:latest
    deploy:
      mode: global
    labels:
      routing.mesh.controller: "true"
    networks:
      controller:
    ports:
      - target: 80
        published: 80
        mode: host
      - target: 443
        published: 443
        mode: host
    volumes:
      - "config:/etc/nginx/conf.d:ro"
      - "challenges:/var/www/letsencrypt:ro"
      - "certs:/etc/letsencrypt:ro"

  manager:
    image: agoat/routing-mesh-manager:latest
    deploy:
      mode: global
    environment:
      ROUTING_NETWORK: "routingmesh"
      LETSENCRYPT_*** "***"
      NODE_ID: '{{.Node.ID}}'
    networks:
      manager:
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock"
      - "config:/etc/nginx/conf.d"
      - "challenges:/var/www/letsencrypt"
      - "certs:/etc/letsencrypt"

volumes:
  config:
  challenges:
  certs:

networks:
  controller:
    attachable: true
    name: "routingmesh"
  manager:
    name: "routingmesh_manager"