An HTTP router and reverse proxy for service composition, designed to handle large-scale routing definitions and Kubernetes Ingress.
Skipper is an HTTP router and reverse proxy designed for service composition in large-scale environments. It handles complex routing with detailed conditions and filters, supports dynamic updates from multiple sources, and can act as a Kubernetes Ingress controller. It solves the problem of managing high volumes of HTTP routes while enabling flexible traffic shaping and augmentation.
Platform engineers, SREs, and DevOps teams building microservices architectures who need a performant, extensible router for Kubernetes ingress, API gateways, or custom proxy logic.
Developers choose Skipper for its ability to handle massive route definitions with zero-downtime updates, deep Kubernetes integration, and extensibility via custom filters and predicates. Its streaming architecture and production-ready features make it a reliable choice for high-traffic environments.
An HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Handles over 300,000 HTTP route definitions with detailed matching conditions, as stated in the README, making it suitable for large-scale microservices.
Supports live routing rule updates from sources like etcd and Kubernetes Ingress without restarts, enabling seamless configuration changes.
Acts as a production-ready ingress controller without reloads, with documented examples for AWS integration and route management.
Allows custom filters and predicates written in Go, with built-in eskip language and plugin support for flexible traffic shaping.
Creating custom filters or predicates requires Go programming knowledge, which may limit teams unfamiliar with Go, as extensions are not language-agnostic.
Uses eskip, a custom DSL for route definitions, adding a learning curve compared to more common standards like YAML or JSON used in other proxies.
No graphical interface for monitoring or managing routes is included, relying on command-line tools or external dashboards, which can hinder operational visibility.