Update the service deployment arch

minikube/kuma/Tutorial/02_kuma_production.md

@@ -2,6 +2,39 @@
 
 <https://kuma.io/docs/2.6.x/production/>
 
-- Deployment topologies
-  - single-zone
-  - multi-zone
+    -  Deployment topologies
+    -  single-zone (one control plane (that can be scaled horizontally) and many data planes connecting directly to it)
+    -  multi-zone (advanced deployment model to support multiple Kubernetes or VM-based zones, or hybrid Service Meshes running on both Kubernetes and VMs combined)
+
+## Control plane and data plane architecture
+
+Use kumactl to configure a multi-zone or single-zone control plane, depending on your organization’s needs. You can deploy either a Kubernetes or Universal data plane.
+
+## Single-zone deployment
+
+    - Zone control plane (kuma-cp)
+    - Data plane proxies (kuma-dp)
+    - Service Connectivity (service - service (via DP))
+
+### zone control plane
+
+    - Accept connections from data plane proxies.
+    - Handle policies -> apply to dataplane (in inventory)
+    - Manage the config of XDS to DP
+
+### Data plane proxies
+
+    - Connect to other data plane proxies and control plane.
+
+## Multi-zone deployment
+
+A zone can be a Kubernetes cluster, a VPC, or any other deployment you need to include in the same distributed mesh environment. The only condition is that all the data planes running within the zone must be able to connect to the other data planes in this same zone.
+
+    Zone-a & Zone-b (with or without Egress)
+
+    service -> service (via Zone Ingress), This ZoneIngress resource is then also synchronized to the global control plane.
+
+The global control-plane will propagate the zone ingress resources and all policies to all other zones over Kuma Discovery Service (KDS), which is a protocol based on xDS.
+
+![alt text](https://kuma.io/assets/images/diagrams/gslides/kuma_multizone_without_egress.svg)
+