Policies · Other resources

MeshService

A service in the mesh, selecting its proxies and declaring its ports and identities.

Kuma

Behaviour per target

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

Output: MeshService

  • spec.ports[].protocol → appProtocol (auto-fixed).
  • spec.selector.dataplaneTags is reported: a 3.0 control plane rejects the MeshService on write (spec.selector.dataplaneTags: unknown field), and one already stored loses its selector and matches no proxies. Not rewritten on v2: on 2.14 a labels selector also matches same-named services synced from other zones.
  • ports[].appProtocol: kafka is reported: 3.0 rejects it.
  • Names that are not RFC 1035 labels are reported.
--to-latest v3 (3.0) rewritten

Output: MeshService

  • ports[].protocol → appProtocol.
  • selector.dataplaneTags → selector.dataplaneLabels.matchLabels. The keys must exist as labels on the Dataplanes (Pod labels on Kubernetes, top-level labels on Universal). A selector with a reserved kuma.io/ key (such as kuma.io/service) or one that conflicts with existing matchLabels is not converted; 3.0 rejects it as an unknown field, so the MeshService is written to _manual/.
  • identities[] entries of type: ServiceTag removed; add type: SpiffeID entries if clients need them.
  • ports[].appProtocol: kafka → tcp. 3.0 accepts only tcp, http, http2 and grpc (kumahq/kuma#17831). On 2.x Kafka is a TCP proxy plus Envoy's kafka_broker filter, which only emits stats, so the traffic handling does not change.
  • Control-plane-owned labels removed.

Timeline

VersionChange
2.8ports[].protocol renamed to appProtocol.
2.10Names that are not RFC 1035 labels deprecated.
3.0dataplaneTags removed; identities accepts SPIFFE IDs only; appProtocol: kafka rejected; non-RFC 1035 names rejected.

Source files