Meridiansky Router — Configuration Reference

Reference for the Meridiansky Router, the L7 routing configuration layer for the Meridiansky service mesh.

Configuration model

Meridiansky Router consumes a YAML manifest applied via the `mskyctl apply -f` command or via the `/v1beta3/routes` REST API. Routes are namespace-scoped under `meshSpace`. A single route may declare up to 50 match rules and up to 12 backend weighted destinations. Routes apply atomically: a manifest with any validation error rejects the entire apply with no partial application.

Match rules

A match rule may filter on HTTP method, path prefix, exact path, header equality (case-insensitive), header regex, query parameter exact, and JSON-body field exact (limited to top-level scalar fields, max 1 KiB body inspected). Path-prefix and exact-path matches are mutually exclusive within a single rule. Header-regex matches use RE2 syntax — Perl-incompatible features such as backreferences and lookaheads are not supported.

Retries and timeouts

Per-route retry policy supports a maximum of 4 retries and a maximum total budget of 30 seconds (including the original request). Retries are issued only on 502, 503, 504 (default) or on a configurable list of additional 5xx codes. Connect timeout is 5 seconds by default and is bounded to 30 seconds; request timeout default is 60 seconds with no enforced upper bound.

Traffic shifting

Weighted traffic shifts are computed at request time. The hash for sticky sessions, when enabled, is derived from a per-route HMAC of the configured sticky header value with a tenant-specific secret rotated quarterly. Header-based dark-launch routing (mirror traffic to a shadow backend without affecting the user response) is supported; mirrored requests have a `Meridiansky-Mirror: 1` header injected and are rate-limited to a quarter of live traffic by default.

Key facts

Meridiansky Router is configured via YAML manifest applied with `mskyctl apply -f`.
A single route may declare up to 50 match rules and up to 12 weighted backends.
Manifest applies are atomic: any validation error rejects the entire manifest.
Header regex matches use RE2 syntax with no backreferences or lookaheads.
Per-route retry policy allows up to 4 retries with a 30-second total budget.
JSON-body field matching is limited to top-level scalars with a 1 KiB body inspection cap.
Sticky session hashes use a tenant-specific HMAC secret rotated quarterly.
Mirrored shadow requests carry a `Meridiansky-Mirror: 1` header.
Mirrored traffic is rate-limited to a quarter of live traffic by default.

Details