Our take
- Activity
- 41
- Community
- 15
- Issues
- 21
- Pull requests
- 21
+2 stars in the last 16 days
- Fewer contributors than 82% of the projects we track
Overview
Middleware Manager is a Go service with a web UI for managing Traefik configuration through Pangolin or Traefik as its data source. It addresses the gap between a deployment's existing resources and custom middleware or service configuration, exposing those controls in one interface.
It is most useful when you already operate Traefik and want a UI to inspect and change its routing resources. The service must remain running for its override middleware configuration to stay deployed, so it is an additional component in the Traefik stack rather than a one-time configuration editor.
Key Features
- Discover and inspect routers, services, and middleware from Pangolin or Traefik.
- Create middleware and assign it to resources, with priorities and templates.
- Override routers and manage custom services, including load balancer, weighted, mirroring, and failover configurations.
- Manage Traefik plugins by updating static configuration.
- Configure mTLS rules per resource through the
mtlswhitelistplugin. - Generate dynamic Traefik configuration through an HTTP provider endpoint.
Use Cases
- Pangolin operators who need to attach custom middleware without replacing their existing deployment workflow.
- Traefik administrators who prefer a UI for examining routers and services and managing overrides.
- Platform teams defining custom service routing, such as weighted or failover services.
- Operators who need to configure plugin-based mTLS rules for selected resources.
Getting Started
The project provides a Docker image. Add the service to your Compose stack, configure its data source and mounted configuration paths, and point Traefik's HTTP provider at its configuration endpoint. See the README for deployment examples and configuration details.
Considerations
- Requires a reachable Traefik v2/v3 instance or Pangolin API, plus a Docker runtime for the provided container deployment.
- Traefik must use the Middleware Manager HTTP provider endpoint to load its generated dynamic configuration.
- Middleware Manager must stay running to keep its override middleware deployed.
- Plugin installation and removal depend on mounting Traefik's static configuration and setting the correct in-container file path.
- The repository has 9 open issues, so check the issue tracker for current limitations before relying on it for a particular setup.
Found this useful?
Share it with someone who would like middleware-manager.