Policies · Legacy policies
Retry
Legacy HTTP, gRPC and TCP retry settings for a destination service.
Behaviour per target
Output: MeshRetry
Outbound shape. conf changes:
tcp.maxConnectAttempts→tcp.maxConnectAttempt(singular).http.retryOnenum values are recased (gateway_error→GatewayError,5xxstays).http.retriableMethods→ extrahttp.retryOnentries (GET→HttpMethodGet).http.retriableStatusCodes→ extrahttp.retryOnentries, one per code (503→"503").MeshRetryaccepts any HTTP status code inretryOnon 2.14 and 3.0. Theretriable_status_codescondition is implied by the codes and dropped.- gRPC
retryOncancelled→Canceled. numRetries,perTryTimeout,backOff.*keep their paths.
retryOn: retriable_headers has no MeshRetry equivalent and is dropped with a warning.
Output: MeshRetry
Same conversion with labels-only references. A destination with no kuma.io/service
tag is an error (original in _manual/). The source object is listed for deletion.
Timeline
| Version | Change |
|---|---|
| 3.0 | Removed from the resource registry. Meshes created on 3.0 also no longer get the default mesh-retry-all-<mesh> policy. |
Related topics
- Legacy policies — The twelve source/destination policies Kuma 3.0 removes, how kuma-migrator maps their selectors and conf to the Mesh* successors, and the two it leaves to you.
- Policy targeting — Which targetRef kinds each policy accepts at each position on 2.14 and 3.0, labels-only selection, policy roles, and control-plane-owned labels.