Policies · Mesh* policies
MeshTimeout
Connection, idle and request timeouts on inbound (rules[]) and outbound (to[]) traffic.
Behaviour per target
Output: MeshTimeout
from[]→rules[]: eachfrom[i].defaultbecomesrules[i].defaultand the sourcetargetRefis dropped (rules apply to every client).- When
from[]andto[]coexist, the policy is split:<name>carriesrules[]and<name>-outboundcarriesto[]. The validator rejectsrules[]andto[]in one spec. MeshSubsetrefs withkuma.io/servicetags and old<name>_<ns>_svc_<port>MeshServicenames are rewritten: top level toDataplane,to[]toMeshService(labels when the policy and target namespaces differ).spec.targetRef.proxyTypesis reported (removed in 3.0, see Policy targeting). The 2.x defaultmesh-gateways-timeout-all-<mesh>(proxyTypes: [Gateway],streamIdleTimeout: 5s) gets a delete-before-upgrading advisory.
Output: MeshTimeout
Same rewrites as v2, plus the rules every Mesh* policy gets under v3:
-
spec.targetRef.proxyTypesis removed when that keeps the scope or only adds former gateway proxies ([Sidecar], both values, or a kind other thanMesh/MeshSubset).[Gateway]alone is written to_manual/: without the field the policy selects every proxy. -
The default
mesh-gateways-timeout-all-<mesh>is not converted. On 3.0 it sets a 5sstreamIdleTimeouton every sidecar (kumahq/kuma#18857). The original goes to_manual/and is listed under Delete Before Upgrading to 3.0, with theskipCreatingInitialPoliciesstep that keeps 2.14 Kubernetes from recreating it. -
name/namespace/meshonMeshService,MeshExternalService,MeshMultiZoneServiceandMeshHTTPRouterefs become labels (kuma.io/display-name,k8s.kuma.io/namespace, plus the policy'skuma.io/zone). -
to[].targetRef.kindmust beMesh,MeshService,MeshExternalService,MeshMultiZoneServiceorMeshHTTPRoute; anything else is reported. -
Control-plane-owned labels (
kuma.io/origin,kuma.io/zone,kuma.io/policy-role, …) are removed.
Timeline
| Version | Change |
|---|---|
| 2.10 | rules[] API added; from[] deprecated. Dataplane added as a top-level kind; MeshSubset deprecated. |
| 3.0 | from removed. Real resources selected by labels only. Top-level targetRef limited to Mesh and Dataplane. targetRef.proxyTypes removed; the default mesh-gateways-timeout-all-<mesh> then applies to every proxy. |
Related topics
- 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.