Policies · Other resources

ZoneIngress

Standalone zone ingress proxy that receives cross-zone traffic.

Kuma

Behaviour per target

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

Output: ZoneIngress

Skipped on Kubernetes (CP-managed). On Universal it is copied unchanged (file labelled SCANNED) with an advisory: 3.0 removes ZoneIngress; move to mesh-scoped zone proxies, which 2.14 already supports (Helm meshes[].ingress/meshes[].egress, or a Universal Dataplane with a ZoneIngress 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 mesh-scoped zone proxies (a regular Dataplane with a ZoneIngress listener, token reissued without --proxy-type) before upgrading the zone control plane. A second warning gives the MeshZoneAddress to apply with the old advertisedAddress/advertisedPort; without it cross-zone traffic to the zone stops. Listed under "Delete Before Upgrading to 3.0".

Timeline

VersionChange
3.0Removed (CRD, API, KDS sync); zone proxies are Dataplanes with listeners; the zone's public address comes from MeshZoneAddress.

Source files