Arpad Ryszka
Arpad Ryszka
the HTTPS redirect feature was implemented before the custom predicates from the ingress annotations. In the redirect route we apply an assumption about the number of predicates: ``` // the...
@jonathanbeber showed me this project: https://github.com/knqyf263/cob We could potentially use it, but of course other solutions, too, to catch small performance regressions between old and new versions of Skipper. We...
- [x] implement converter logic - [x] test with Kubernetes with and without host validation - [x] integrate the temporary command with the existing eskip supplementary tool as a subcommand...
The filters are applied first to the requests in normal order, then a backend request, a shunt, rate limiting, or loopback happens. Then in the case of a response received...
This set of routes should return "It works!": ``` main: * -> logHeader() -> setRequestHeader("Host", "www.example.org") -> ; org: Host("www.example.org") -> inlineContent("It works!") -> ; ``` But it ends up...
Consider supporting https backends in routes generated for Kubernetes ingress. Questions: - how should the ingress spec indicate when a service expects to receive the requests via https? - Skipper...
Invalid route configuration, e.g. a typo in a filter's name or invalid arguments are currently detected only in the last phase of the route updates, and it's not possible to...
**Describe the bug** The documentation states that the valid levels for the compress filter are [0..9], while the validation logic allows a wider range, see: https://github.com/zalando/skipper/pull/1515 **Expected behavior** The safest...