Policies · Other resources
MeshMultiZoneService
A service that groups same-named MeshServices across zones.
Behaviour per target
Output: MeshMultiZoneService
Copied unchanged. A name that is not a lowercase RFC 1035 label, or longer than 63
characters, is reported. ports[].appProtocol: kafka is reported: 3.0 rejects it.
Output: MeshMultiZoneService
Same name check (a hard error on 3.0). Control-plane-owned labels removed.
ports[].appProtocol: kafka → tcp, as for MeshService.
Timeline
| Version | Change |
|---|---|
| 2.10 | Names that are not RFC 1035 labels deprecated. |
| 2.14 | Names longer than 63 characters deprecated. |
| 3.0 | Non-RFC 1035 names rejected. appProtocol: kafka rejected. Cross-zone routing needs a MeshZoneAddress. |
Related topics
- Multizone — Control plane modes, which control plane to extract from, zone proxies, MeshMultiZoneService and cross-zone load balancing across 2.x and 3.0.
- MeshService — Moving policies, routes and workload addresses from kuma.io/service tags to MeshService, and setting meshServices.mode before Kuma 3.0.