Policies · Other resources
Dataplane
A data plane proxy's inbounds, outbounds, gateway role and transparent-proxy settings.
Behaviour per target
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.redirectPortInboundV6is reported (removed in 2.9).transparentProxying.reachableServicesis reported: inExclusivemode the names must be MeshService display names, and 3.0 removes the field.reachableBackends.refs[]usingname/namespaceare reported (3.0 selects by labels).- Named entries in
transparentProxying.directAccessServicesare reported: 3.0 honours only*and ignores names silently. - Inbound protocol
kafka(field orkuma.io/protocoltag) is reported: 3.0 rejects it.
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/protocoltag →inbound[].protocol. -
inbound[].tags→ top-levellabels;kuma.io/andk8s.kuma.io/keys are dropped (reserved prefixes). -
reachableServices→reachableBackendswhere the name resolves;reachableBackendsname refs → labels. AMeshServiceref also getskuma.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 thekuma.io/servicevalue 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 thebackendRefto fill in. -
Inbound
protocol: kafka→tcp. 3.0 accepts onlytcp,http,http2andgrpc(kumahq/kuma#17831). On 2.x Kafka is a TCP proxy plus a stats-only filter, so only the Kafka stats are lost. -
directAccessServiceswith*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
| Version | Change |
|---|---|
| 2.9 | transparentProxying.redirectPortInboundV6 removed. |
| 3.0 | inbound[].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. |
Related topics
- Dataplanes — Universal Dataplane fields and Kubernetes Pod annotations that change or disappear between 2.x and 3.0, and what kuma-migrator rewrites.
- MeshService — Moving policies, routes and workload addresses from kuma.io/service tags to MeshService, and setting meshServices.mode before Kuma 3.0.