This is the documentation page of Skipper. Skipper is an HTTP router and reverse proxy for service composition. It’s designed to handle large amounts of dynamically configured HTTP route definitions (>800000 routes) with detailed lookup conditions, and flexible augmentation of the request flow with filters. It can be used out of the box or extended with custom lookup, filter logic and configuration sources.
Skipper identifies routes based on the requests’ properties, such as path, method, host and headers using the predicates. It allows the modification of the requests and responses with filters that are independently configured for each route. Learn here more about how it works.
Skipper can be used to run as a Kubernetes Ingress controller. Details with examples of Skipper’s capabilities and an overview you will can be found in the ingress-controller deployment docs.