Policies · Legacy policies
ProxyTemplate
Legacy raw Envoy resource and modification injection for selected proxies.
Behaviour per target
Output: MeshProxyPatch
Selector shape: selectors → spec.targetRef. conf.modifications →
spec.default.appendModifications, with every operation recased to the
MeshProxyPatch enum: add, remove, patch, addFirst, addLast, addBefore,
addAfter → Add, Remove, Patch, AddFirst, AddLast, AddBefore, AddAfter.
httpFilter and networkFilter have no plain Add, so add there becomes AddLast
with a warning; cluster, listener and virtualHost keep Add. A positional
operation on a kind that does not accept it is warned.
conf.imports and conf.resources have no MeshProxyPatch equivalent and are
reported, not converted.
Output: MeshProxyPatch
Same as v2, with labels-only top-level references (kind: Dataplane,
labels: {app: <service>}). The source object is listed for deletion.
Timeline
| Version | Change |
|---|---|
| 3.0 | No longer affects generated Envoy configuration; profile imports are 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.