Skip to content

docs(routes): retry-policy parser landed; fix circuit-breaker scope notes #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
raffaelschneider wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs(routes): retry-policy parser landed; fix circuit-breaker scope notes #12

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5299445
docs(routes): retry-policy parser landed; correct circuit-breaker sco…
raffaelschneider Jun 16, 2026
537bf14
docs(routes): correct upstream circuit-breaker attribution (#267, not…
raffaelschneider Jun 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/configuration/routes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -748,7 +748,7 @@ Buffering is required for body inspection by agents. Be mindful of memory usage

## Retry Policy

> **Not yet implemented at route scope.** The route-level `retry-policy` block is documented but currently dropped by the KDL parser (the proxy logs `Unrecognized directive in route block (will be ignored)` for it). Tracked in [zentinelproxy/zentinel#262](https://github.com/zentinelproxy/zentinel/issues/262). Until the parser lands, this section describes the intended configuration only.
> **Behavior partially implemented.** As of [zentinelproxy/zentinel#267](https://github.com/zentinelproxy/zentinel/pull/267) the route-level `retry-policy` block is parsed. `max-attempts` is honored — it bounds the number of upstream peer-selection attempts. `timeout-ms`, `backoff-base-ms`, `backoff-max-ms`, and `retryable-status-codes` are parsed but **not yet applied at runtime** (the proxy logs that each setting is "parsed, but not implemented"). The remaining behavior is tracked in [zentinelproxy/zentinel#279](https://github.com/zentinelproxy/zentinel/issues/279).

```kdl
route "api" {
Expand All @@ -775,7 +775,7 @@ Backoff uses exponential delay: `min(base * 2^attempt, max)`

## Circuit Breaker

> **Not yet implemented at route scope.** The route-level `circuit-breaker` block is documented but currently dropped by the KDL parser (the proxy logs `Unrecognized directive in route block (will be ignored)` for it). Tracked in [zentinelproxy/zentinel#262](https://github.com/zentinelproxy/zentinel/issues/262). Upstream-level configuration via the `circuit-breaker` block inside `upstream { ... }` is in flight in [zentinelproxy/zentinel#260](https://github.com/zentinelproxy/zentinel/pull/260). Until the route-level parser lands, this section describes the intended configuration only.
> **Not supported at route scope.** The route-level `circuit-breaker` block is dropped by the KDL parser (the proxy logs `Unrecognized directive in route block (will be ignored)` for it). Configure circuit breaking at the **upstream** level instead — the `circuit-breaker` block inside `upstream { ... }` is parsed and configurable as of [zentinelproxy/zentinel#267](https://github.com/zentinelproxy/zentinel/pull/267). The block below describes the intended route-scope configuration only. (Note: recovery from the open state has a known bug — see [zentinelproxy/zentinel#261](https://github.com/zentinelproxy/zentinel/issues/261).)

```kdl
route "api" {
Expand Down
Loading