Policies · Mesh* policies

MeshMetric

Metrics exposure for selected proxies (Prometheus or OpenTelemetry).

Kuma

Behaviour per target

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

Output: MeshMetric

  • default.sidecar.regex → default.sidecar.profiles.exclude (auto-fixed).
  • An inline openTelemetry.endpoint is reported (deprecated in 2.14, removed in 3.0).
--to-latest v3 (3.0) rewritten

Output: MeshMetric, MeshOpenTelemetryBackend

v2 fix, plus the inline OTel endpoint is replaced by a backendRef and a generated MeshOpenTelemetryBackend.

prometheus.tls.mode: ActiveMTLSBackend is reported: on 3.0 a scraper connecting from another address must present a client certificate the mesh trusts. Give each remote scraper one, or set the mode to Disabled. A MeshMetric generated from Mesh.metrics gets this mode under v3 when the legacy endpoint required a mesh client certificate.

Timeline

VersionChange
2.7sidecar.regex replaced by sidecar.profiles.exclude.
2.14Inline openTelemetry.endpoint deprecated.
3.0Inline OpenTelemetry endpoint removed. ActiveMTLSBackend requires a client certificate from remote scrapers.

Source files