Azure Express Route Diagram: Kubernetes Request Flow Infographic

Tech architecture infographic titled "Kubernetes Architecture" using archetype REQUEST FLOW (client → server → DB), tailored for a mid-level developer. Show a technically accurate Kubernetes request path as a clean left-to-right flow with labeled boxes and directional arrows. Include these boxes: 1) Client Browser — icon: browser window — role: "User sends HTTPS requests to the application"; 2) Ingress / Load Balancer — icon: network gateway — role: "Accepts external traffic and routes requests into the cluster"; 3) Kubernetes Ingress Controller — icon: traffic router — role: "Applies host and path routing rules for Services"; 4) Kubernetes Service — icon: service mesh / endpoint box — role: "Provides stable virtual IP and load balances to Pods"; 5) Application Pods — icon: container stack — role: "Run stateless application containers that process requests"; 6) Cache — icon: lightning database — role: "Stores hot data for low-latency reads"; 7) Queue — icon: message queue — role: "Buffers asynchronous jobs between services"; 8) Database — icon: cylinder database — role: "Persists application data with durable storage"; 9) Kubernetes API Server — icon: control plane node — role: "Exposes the Kubernetes control API"; 10) Scheduler — icon: decision node — role: "Assigns Pods to worker nodes"; 11) Controller Manager — icon: control loops — role: "Reconciles desired and actual cluster state"; 12) Worker Node — icon: server rack — role: "Hosts Pods and kubelet runtime components". Connect boxes with arrows showing data direction and short English labels: Browser to Ingress / Load Balancer: "HTTPS request"; Ingress / Load Balancer to Ingress Controller: "TCP 443 / HTTPS"; Ingress Controller to Kubernetes Service: "HTTP route"; Kubernetes Service to Application Pods: "Load-balanced request"; Application Pods to Cache: "GET / SET cache"; Application Pods to Queue: "Publish job"; Queue to Application Pods: "Consume job"; Application Pods to Database: "SQL query / INSERT row"; Database to Application Pods: "Query result". Also show dashed control-plane arrows: Kubernetes API Server to Scheduler: "Watch Pod state"; API Server to Controller Manager: "Cluster state"; Scheduler to Worker Node: "Bind Pod"; API Server to Worker Node: "PodSpec via kubelet". Make the Kubernetes cluster visually grouped inside a bordered container labeled "Kubernetes Cluster", with a separate "Control Plane" zone and "Worker Nodes" zone. Use editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Visual style: cyberpunk neon with warm beige and navy palette, accented by electric cyan and magenta glows, dark navy background, warm beige panels, subtle grid, high contrast, futuristic but readable, polished developer-education mood. Add a numbered legend (1-7) in English walking through the lifecycle: 1. "The client sends an HTTPS request to the external endpoint." 2. "Ingress receives the connection and forwards traffic using host or path rules." 3. "The Kubernetes Service selects healthy Pods and load balances the request." 4. "The application container processes the request and may read from cache first." 5. "If needed, the application writes or reads persistent data from the database." 6. "Long-running work is published to the queue for asynchronous processing." 7. "Kubernetes control-plane components continuously schedule, monitor, and reconcile Pods on worker nodes." Include small callouts for reliability concepts: "Pod replica", "Service discovery", "Desired state", and "Rolling update". Do not present the diagram as an audited or vendor-specific reference architecture. No real cloud-vendor logos; use only generic cloud and network icons. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real cloud-vendor logos (AWS, GCP, Azure) beyond generic cloud icons. Common protocol names (HTTPS, TCP, JWT, OAuth, REST, GraphQL) stay in canonical English form. No security-claim overstatements (do not present diagrams as audited reference architectures).