Policies · Legacy policies
VirtualOutbound
Legacy virtual hostnames and ports rendered from Dataplane tags.
Behaviour per target
No output kind.
Not converted. conf.host and conf.port are templates over arbitrary Dataplane tags
(parameters[].tagKey), and no single successor reproduces them:
VirtualOutbound |
HostnameGenerator |
|
|---|---|---|
| selects | Dataplanes by tags | MeshService/MeshExternalService/MeshMultiZoneService by labels |
| template variables | any Dataplane tag | .Name, .DisplayName, .Namespace, .Mesh, .Zone, label |
| port | templatable | not templatable |
The error names both halves: a HostnameGenerator for the
hostname and a MeshHTTPRoute/MeshTCPRoute for the routing. The original stays in the
output tree.
No output kind.
Same error. The original is copied to _manual/ and listed for deletion.
Timeline
| Version | Change |
|---|---|
| 3.0 | No longer affects generated Envoy configuration; the legacy DNS VIP allocator is removed. |
| 3.0 | Removed from the resource registry. |
Related topics
- Legacy policies — The twelve source/destination policies Kuma 3.0 removes, how kuma-migrator maps their selectors and conf to the Mesh* successors, and the two it leaves to you.