zalando/skipper

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

View on GitHub ↗Jump to charts ↓Open shareable report →

zalando/skipper has 3k+ stars and 400+ forks on GitHub, is written in Go, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 13 minutes ago
Added to GitGenius on September 20th, 2026
Created on July 9th, 2015
Open Issues & Pull Requests: 299 (+0)
GitHub issues: Enabled
Number of forks: 408
Total Stargazers: 3,332 (+0)
Total Subscribers: 67 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 35.5 hours
Mean response time: 94.1 days
90th percentile: 260.1 days
Tracked items: 173

Maintainer activity

10 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

About 11% of issues opened in the past year have never received a reply. 41% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "bug" is answered fastest, typically in about 4 hours, while "kubernetes" waits about 13 days. 65% of issues opened in the past year have been closed, leaving a working backlog. Three people close 92% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 66
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 650 days
Stale 30+ days: 56
Stale 90+ days: 44

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 1

Top labels

  • enhancement (40)
  • flakytest (32)
  • good first issue (19)
  • bug (18)
  • help wanted (18)
  • documentation (10)
  • kubernetes (10)
  • open-policy-agent (8)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Skipper is an HTTP router and reverse proxy for service composition that can handle over 300,000 route definitions with detailed lookup conditions and flexible request augmentation through filters.

The tool solves the problem of routing HTTP traffic across distributed services while maintaining high performance and flexibility. It identifies routes based on request properties such as path, method, host, and headers, then applies filters to modify requests and responses independently for each route. Skipper streams incoming requests and backend responses simultaneously and can update routing rules without downtime by pulling configuration from multiple sources including etcd, Kubernetes Ingress resources, static files, and custom data sources. It can also act as a final endpoint for static file serving or mock backends.

Skipper suits organizations running Kubernetes clusters that need a powerful ingress controller with advanced routing capabilities beyond basic path and host matching. It works well for teams that require custom filters, predicates, or data sources since the tool is designed primarily for extension through Go code. The project includes built-in support for HTTP/1.1, HTTP/2, and H2C, along with features like cluster rate limiting, authentication and authorization without external dependencies, and tiered caching. It ships with eskip, a descriptive configuration language for routing rules, plus additional utilities like routesrv for reducing kube-apiserver load and a Kubernetes validation webhook.

The project maintains steady development activity with regular updates to core functionality and documentation. The maintainers actively support multiple deployment patterns and data sources, indicating responsiveness to different operational needs. The codebase includes comprehensive examples and plugins that demonstrate extension patterns, suggesting the team values practical guidance for customization. Development focuses on production-grade features like cluster rate limiting and remote storage support for caching and certificate management.