Policies · Other resources
MeshService
A service in the mesh, selecting its proxies and declaring its ports and identities.
Behaviour per target
Output: MeshService
spec.ports[].protocol→appProtocol(auto-fixed).spec.selector.dataplaneTagsis 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: kafkais reported: 3.0 rejects it.- Names that are not RFC 1035 labels are reported.
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 reservedkuma.io/key (such askuma.io/service) or one that conflicts with existingmatchLabelsis not converted; 3.0 rejects it as an unknown field, so the MeshService is written to_manual/.identities[]entries oftype: ServiceTagremoved; addtype: SpiffeIDentries if clients need them.ports[].appProtocol: kafka→tcp. 3.0 accepts onlytcp,http,http2andgrpc(kumahq/kuma#17831). On 2.x Kafka is a TCP proxy plus Envoy'skafka_brokerfilter, which only emits stats, so the traffic handling does not change.- Control-plane-owned labels removed.
Timeline
| Version | Change |
|---|---|
| 2.8 | ports[].protocol renamed to appProtocol. |
| 2.10 | Names that are not RFC 1035 labels deprecated. |
| 3.0 | dataplaneTags removed; identities accepts SPIFFE IDs only; appProtocol: kafka rejected; non-RFC 1035 names rejected. |
Related topics
- MeshService — Moving policies, routes and workload addresses from kuma.io/service tags to MeshService, and setting meshServices.mode before Kuma 3.0.