Policies · Legacy policies
Timeout
Legacy connection and request timeouts between services, selected with sources and destinations.
Behaviour per target
Output: MeshTimeout
Outbound shape: sources becomes spec.targetRef, destinations becomes to[].
A policy with several specific sources is split into one MeshTimeout per source.
conf is rewritten field by field:
Legacy conf |
MeshTimeout to[].default |
|---|---|
connectTimeout |
connectionTimeout |
tcp.idleTimeout, http.idleTimeout |
idleTimeout (tcp wins on conflict, with a warning) |
http.requestTimeout, http.streamIdleTimeout, http.maxStreamDuration |
same path |
grpc.streamIdleTimeout, grpc.maxStreamDuration |
http.* (no grpc section exists) |
Any conf leaf no rule consumed is reported as a warning. A kuma.io/service: '*'
selector becomes kind: Mesh. A specific service becomes
kind: Dataplane, labels: {app: <name>, k8s.kuma.io/namespace: <ns>} at the top level
(app is a best guess, warned) and kind: MeshService in to[];
<name>_<ns>_svc_<port> values are decoded into name and namespace. Reserved tags that
are not labels (kuma.io/protocol, …) are dropped from label selectors, with a warning.
A selector with only non-service tags stays a MeshSubset.
Output: MeshTimeout
Same conf conversion as v2. Every generated reference uses labels: the top-level
Dataplane gets labels: {app: <service>} (a best guess, reported as a warning) and a
to[] MeshService gets kuma.io/display-name plus k8s.kuma.io/namespace.
A destination selector with no kuma.io/service tag is an error: 3.0 accepts no tag
selector in to[]. The original is copied to _manual/ and you pick the real
destination by hand. The report lists the source Timeout under
"Delete Before Upgrading to 3.0".
Timeline
| Version | Change |
|---|---|
| 3.0 | No longer affects generated Envoy configuration. |
| 3.0 | Removed from the resource registry with the other 11 legacy policies. Stored objects are not migrated. |
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.