Policies · Other resources

ZoneEgress

Standalone zone egress proxy for cross-zone and external traffic.

Kuma

Behaviour per target

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

Output: ZoneEgress

Skipped on Kubernetes (CP-managed). On Universal it is copied unchanged (file labelled SCANNED) with an advisory: 3.0 removes ZoneEgress; move to mesh-scoped zone proxies, which 2.14 already supports (Helm meshes[].ingress/meshes[].egress, or a Universal Dataplane with a ZoneEgress listener), before upgrading the zone control plane.

--to-latest v3 (3.0) removed

No output kind.

Universal input is copied to _manual/ (file labelled MANUAL, never in the apply tree) with a blocking warning: deploy a mesh-scoped zone proxy (a regular Dataplane with a ZoneEgress listener) per mesh before upgrading the zone control plane. Listed under "Delete Before Upgrading to 3.0".

Timeline

VersionChange
3.0Removed (CRD, API, KDS sync); egress use is implicit.

Source files