Policies · Mesh* policies

MeshAccessLog

Access logging for inbound and outbound traffic to file, TCP or OpenTelemetry backends.

Kuma

Behaviour per target

--to-latest v2 (2.x) rewritten

Output: MeshAccessLog

  • from[] → rules[], with a <name>-outbound split when to[] is also present.
  • An inline openTelemetry.endpoint is reported: deprecated in 2.14, removed in 3.0. Define a MeshOpenTelemetryBackend and reference it with backendRef (labels only, system namespace). The warning says not to switch while any control plane or data plane runs below 2.14.
  • openTelemetry.attributes[].key values that 2.14 rejects (reserved otel. prefix, non-lowercase, placeholders) are reported.
--to-latest v3 (3.0) rewritten

Output: MeshAccessLog, MeshOpenTelemetryBackend

v2 rewrites, plus each inline openTelemetry.endpoint is replaced by backendRef: {kind: MeshOpenTelemetryBackend, labels: {kuma.io/display-name: <name>-otel}} and a matching MeshOpenTelemetryBackend is generated (in the system namespace on Kubernetes, see Meshes; protocol grpc). Apply the backend before the policy. Allowed to[].targetRef.kind: Mesh, MeshService, MeshExternalService, MeshMultiZoneService, MeshHTTPRoute.

Timeline

VersionChange
2.10rules[] API added; from[] deprecated.
2.14Inline openTelemetry.endpoint deprecated; attribute keys validated.
3.0from and the inline OpenTelemetry endpoint removed.

Source files