diff --git a/docs/reference/backends.md b/docs/reference/backends.md index 9f138122a7..d3800d88d1 100644 --- a/docs/reference/backends.md +++ b/docs/reference/backends.md @@ -261,6 +261,8 @@ Current implemented algorithms: - `powerOfRandomNChoices`: backend is chosen by powerOfRandomNChoices algorithm with selecting N random endpoints and picking the one with least outstanding requests from them. (http://www.eecs.harvard.edu/~michaelm/postscripts/handbook2001.pdf) - __TODO__: https://github.com/zalando/skipper/issues/557 +All algorithms except `powerOfRandomNChoices` support [fadeIn](filters.md#fadein) filter. + Route example with 2 backends and the `roundRobin` algorithm: ``` r0: * -> ; diff --git a/docs/reference/filters.md b/docs/reference/filters.md index 9046a409a0..e5b0f7c502 100644 --- a/docs/reference/filters.md +++ b/docs/reference/filters.md @@ -2903,7 +2903,8 @@ Some filters influence how load balancing will be done ### fadeIn -When this filter is set, and the route has a load balanced backend, then the newly added endpoints will receive +When this filter is set, and the route has a load balanced backend using [supported algorithm](backends.md#load-balancer-backend), +then the newly added endpoints will receive the traffic in a gradually increasing way, starting from their detection for the specified duration, after which they receive equal amount traffic as the previously existing routes. The detection time of an load balanced backend endpoint is preserved over multiple generations of the route configuration (over route changes). This