How to set up Skipper as a Kubernetes ingress controller?

Deploy Skipper using provided Helm charts or YAML manifests from the documentation; it integrates directly with Kubernetes Ingress resources and supports dynamic updates without pod restarts.

Skipper vs Nginx for reverse proxy?

Skipper offers dynamic routing updates without reloads and deep Kubernetes integration, while Nginx has a larger ecosystem and broader community support but may require more manual configuration for similar features.

How to write a custom filter in Skipper?

Implement filters in Go by extending the filter interface; the README includes links to examples and tutorials, such as building your own proxy with custom logic.

Does Skipper support WebSocket proxying?

Yes, Skipper supports WebSocket proxying through its streaming architecture, allowing simultaneous request and response handling for low-latency connections.

How to handle authentication with Skipper?

Use built-in filters for Basic auth, OAuth2, or OpenID Connect, as documented in the authentication section, enabling it to act as an authentication proxy with audit logging.

What are Skipper's performance benchmarks?

Skipper is designed for high throughput, capable of handling millions of RPS in production; specific benchmarks are discussed in community blogs and the documentation, though detailed public reports may be limited.

Open-Awesome

Skipper

NOASSERTIONGov0.26.23

An HTTP router and reverse proxy for service composition, designed to handle large-scale routing definitions and Kubernetes Ingress.

Visit Website GitHub

3.3k stars387 forks0 contributors

What is Skipper?

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.

Target Audience

Platform engineers, SREs, and DevOps teams building microservices architectures who need a performant, extensible router for Kubernetes ingress, API gateways, or custom proxy logic.

Value Proposition

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.

Overview

An HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress

Use Cases

Best For

Implementing a Kubernetes Ingress controller without reloads
Building a custom API gateway with dynamic routing rules
Managing authentication and authorization as a reverse proxy
Handling large-scale HTTP routing with over 300k route definitions
Streaming and modifying requests/responses with custom filters
Integrating multiple backend services with complex traffic shaping

Not Ideal For

Teams needing a GUI-based API gateway with visual route management
Projects where the team lacks Go expertise for custom extensions
Environments requiring out-of-the-box service mesh features like mutual TLS or advanced traffic mirroring
Small-scale applications where a simpler proxy like Caddy would suffice without dynamic routing complexity

Pros & Cons

Pros

Massive Route Capacity

Handles over 300,000 HTTP route definitions with detailed matching conditions, as stated in the README, making it suitable for large-scale microservices.

Dynamic Zero-Downtime Updates

Supports live routing rule updates from sources like etcd and Kubernetes Ingress without restarts, enabling seamless configuration changes.

Kubernetes Native Integration

Acts as a production-ready ingress controller without reloads, with documented examples for AWS integration and route management.

Extensible Filter System

Allows custom filters and predicates written in Go, with built-in eskip language and plugin support for flexible traffic shaping.

Cons

Go-Centric Extensibility Barrier

Creating custom filters or predicates requires Go programming knowledge, which may limit teams unfamiliar with Go, as extensions are not language-agnostic.

Proprietary Configuration Language

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.

Lack of Built-in Management UI

No graphical interface for monitoring or managing routes is included, relying on command-line tools or external dashboards, which can hinder operational visibility.

Frequently Asked Questions

Related Projects

Kong

🦍 The API and AI Gateway

Cloud-native high-performance edge/middle/service proxy

A library for building fast, reliable and evolvable network services.

Stars26,795

Forks1,663

Last commit4 days ago

zuul

Zuul is a gateway service that provides dynamic routing, monitoring, resiliency, security, and more.

Stars14,020

Forks2,437

Last commit5 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub