Policies · Other resources

Dataplane

A data plane proxy's inbounds, outbounds, gateway role and transparent-proxy settings.

Kuma

Behaviour per target

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

Output: Dataplane

Skipped on Kubernetes (CP-generated). On Universal it is scanned and copied unchanged; a Dataplane with a finding is labelled SCANNED, one without SKIP:

  • transparentProxying.redirectPortInboundV6 is reported (removed in 2.9).
  • transparentProxying.reachableServices is reported: in Exclusive mode the names must be MeshService display names, and 3.0 removes the field.
  • reachableBackends.refs[] using name/namespace are reported (3.0 selects by labels).
  • Named entries in transparentProxying.directAccessServices are reported: 3.0 honours only * and ignores names silently.
  • Inbound protocol kafka (field or kuma.io/protocol tag) is reported: 3.0 rejects it.
--to-latest v3 (3.0) rewritten

Output: Dataplane

Universal only. The file is labelled SCANNED ("rewritten by the deprecation scan") on stdout and listed under Scanned Non-Policy Resources in the report. Rewrites:

  • networking.gateway (any type) removed; its non-reserved tags move to labels.

  • Inbound kuma.io/protocol tag → inbound[].protocol.

  • inbound[].tags → top-level labels; kuma.io/ and k8s.kuma.io/ keys are dropped (reserved prefixes).

  • reachableServices → reachableBackends where the name resolves; reachableBackends name refs → labels. A MeshService ref also gets kuma.io/zone (the Dataplane's zone), because on 3.0 a labels selector without it matches same-named services from other zones and an outbound binds the oldest one.

  • Control-plane-owned labels (e.g. k8s.kuma.io/service-account) removed.

  • outbound[].tags → backendRef (kind: MeshService, labels, port) when the kuma.io/service value is <name>_<ns>_svc_<port>. Otherwise the MeshService port is not in the manifest: 3.0 rejects the Dataplane (networking.outbound[0].backendRef: must be defined), so it is written to _manual/ with the backendRef to fill in.

  • Inbound protocol: kafka → tcp. 3.0 accepts only tcp, http, http2 and grpc (kumahq/kuma#17831). On 2.x Kafka is a TCP proxy plus a stats-only filter, so only the Kafka stats are lost.

  • directAccessServices with * and names → ["*"] (the names were redundant). Names without * are reported, not rewritten: 3.0 ignores them and the proxy loses direct access to those services. Use * or drop direct access.

Reported, not rewritten: advertisedAddress, redirectPortInbound/redirectPortOutbound (removed in 3.1), ipFamilyMode, and transparent proxying without reachableBackends (no outbounds on 3.0).

Timeline

VersionChange
2.9transparentProxying.redirectPortInboundV6 removed.
3.0inbound[].tags, outbound[].tags, advertisedAddress, networking.gateway, reachableServices and ipFamilyMode removed; the protocol is no longer read from kuma.io/protocol; proxies without reachableBackends get no outbounds. Protocol kafka rejected. Only * honoured in directAccessServices.

Source files