lucaslorentz/caddy-docker-proxy
Caddy Docker Proxy
caddy-docker-proxy ist ein dynamischer HTTP-Reverse-Proxy und Docker-Netzwerk-Ingress-Controller, der automatisch Routing-Konfigurationen generiert, indem er Labels aus Docker-Containern liest. Er dient als Service-Discovery-Tool, das Container-IP-Adressen in Echtzeit erkennt, um eingehenden Web-Traffic an die korrekten Backend-Ziele weiterzuleiten.
Das Projekt fungiert als verteilter Proxy-Orchestrator, der in der Lage ist, generierte Konfigurationen von einem zentralen Controller an mehrere Remote-Server-Instanzen zu pushen, um die Request-Verarbeitung zu skalieren. Es automatisiert die Ausstellung und Erneuerung von TLS-Sicherheitszertifikaten für proxied Domains und koordiniert gemeinsam genutzte Zertifikate über Server-Replikate hinweg.
Das System unterstützt die label-basierte Konfigurationsgenerierung unter Verwendung von Templates und Docker-Secrets, um Metadaten und globale Einstellungen in die Serverkonfiguration zu injizieren. Es behält die Synchronisierung bei, indem es auf Container-Lebenszyklusereignisse lauscht und einen In-Process-Lademechanismus verwendet, um das Serververhalten zu aktualisieren.
Die Traffic-Management-Funktionen umfassen das Definieren von Request-Routing-Regeln, Pfad-Matching und URI-Rewriting, um Traffic an containerisierte Ressourcen zu leiten.
Features
- Container Label Routing - Generates reverse proxy routing rules automatically by reading metadata labels from Docker containers.
- Reverse Proxy Configurations - Maps external domains to backend containers via metadata labels to automate reverse proxy routing.
- Dynamic Reverse Proxy Config Generators - Automatically generates reverse proxy configuration files from Docker container labels and metadata.
- Event-Driven Configuration Synchronization - Synchronizes server settings automatically by listening for Docker container creation, modification, or stop events.
- Event-Driven Triggers - Automatically triggers server configuration updates by listening to Docker container lifecycle events.
- Configuration via Labels - Uses container metadata labels to define operational behavior and automated routing rules.
- Service Discovery - Detects container IP addresses in real time via the Docker API to enable dynamic routing.
- Proxy Node Orchestrators - Coordinates multiple proxy server instances from a central controller to scale request handling across a cluster.
- Ingress Controllers - Maps external domain names to backend containers using Docker metadata and ingress networks.
- Label-Based Reverse Proxies - Automates the routing of incoming web traffic to Docker containers by using labels to define domain mappings.
- Dynamic Service Discovery - Automatically detects container IP addresses in real time to route traffic to active backend services.
- Container Traffic Forwarding - Maps incoming network requests to running containers using ingress networks and task-level proxying.
- Ingress-Based Routing - Routes external HTTP/HTTPS traffic to internal containerized services using host and path matching rules.
- Service Address Resolution - Translates logical container service names into real-time IP addresses for accurate traffic routing.
- Container Traffic Proxies - Routes incoming web traffic to specific Docker containers based on labels and network connectivity.
- Automated TLS Reverse Proxies - Deploys a reverse proxy that automatically provisions and renews TLS certificates for all proxied services.
- Upstream Proxy Relaying - Forwards incoming network traffic to backend Docker containers using dynamic IP resolution.
- TLS Certificate Management - Automates the provisioning, renewal, and management of SSL and TLS security certificates for proxied domains.
- Automated Certificate Management - Handles the complete lifecycle of TLS certificates, including issuance and renewal, without manual intervention.
- Push-Based Controller Topologies - Implements a central controller that pushes generated configurations to a fleet of remote proxy nodes.
- Distributed Configuration - Synchronizes server settings across multiple remote proxy instances using a central controller.
- In-Process Loading - Applies configuration changes directly to the running process to update server behavior without an external API.
- Container Metadata Injection - Passes dynamic container and service metadata into configuration labels using standard templates.
- Metadata Templates - Uses templates within labels to dynamically inject container names and resource information into configurations.
- Distributed Cluster Management - Provides the ability to orchestrate shared computing resources across a pool of proxy nodes.
- Proxy Cluster Deployments - Deploys multiple server instances coordinated by a central controller to scale request handling.
- Configuration Injection - Injects dynamic cluster settings into the server configuration based on metadata labels.
- Proxy Configuration Synchronization - Scales request handling across multiple server instances by syncing configurations across a network of proxy nodes.
- Fleet Configuration Updates - Propagates configuration updates across a distributed fleet of proxy servers.
- Dynamic Reverse Proxies - Provides a reverse proxy that updates its routing configuration in real-time based on container lifecycle events.
- Configuration Application - Updates server behavior by applying configuration settings directly to the running process.
- Request Routing - Implements path matching and URI rewriting to direct incoming requests to the correct backend service.
- Networking And Proxies - Caddy-based reverse proxy with label-based configuration.
- Networking and Proxying - Caddy-based proxy with automatic label-based service discovery.
