Network Mapping Tools Open Source Kubernetes Pod Deployment

Tech architecture infographic titled "Kubernetes Pod Deployment" using REQUEST FLOW archetype. Show a precise client-to-server deployment and runtime flow for Kubernetes pod deployment in a production-like cluster, arranged left-to-right with labeled boxes and directional arrows. Include these boxes with icons, canonical English names, and one-line English role descriptions: Developer Workstation — "Defines and applies deployment manifests"; Browser / kubectl Client — "Sends API requests to the cluster control plane"; Kubernetes API Server — "Validates and stores cluster resource definitions"; Authentication / Authorization — "Checks identity and RBAC permissions"; etcd — "Stores cluster state and desired configuration"; Scheduler — "Selects a suitable worker node for the Pod"; Controller Manager — "Reconciles desired state with actual state"; Worker Node — "Runs node services and hosts Pods"; kubelet — "Creates and manages Pod containers on the node"; Container Runtime — "Pulls images and starts containers"; Container Registry — "Provides versioned container images"; Pod — "Smallest deployable unit containing one or more containers"; Service — "Provides stable virtual access to Pod endpoints"; Ingress / Load Balancer — "Routes external HTTP traffic to Services"; CoreDNS — "Resolves service names inside the cluster"; ConfigMap / Secret — "Provides configuration and sensitive runtime values". Connect every component with arrows showing accurate data direction and short English arrow labels such as: "HTTPS REST request", "Bearer token", "Admission check", "Write desired state", "Watch Deployment", "Schedule Pod", "Bind Pod to node", "Pull image", "Start container", "Pod status update", "ClusterIP traffic", "DNS query", "TCP connection", "HTTP 201 Created", "HTTP 200 OK". Make the request flow technically accurate: Browser / kubectl Client sends HTTPS REST request to Kubernetes API Server; API Server calls Authentication / Authorization and persists Deployment object to etcd; Controller Manager watches desired state and creates ReplicaSet / Pod intent; Scheduler watches unscheduled Pod and binds it to Worker Node; kubelet on Worker Node watches API Server, requests image from Container Registry via Container Runtime, mounts ConfigMap / Secret, creates Pod, and reports status back to API Server; Service and Ingress / Load Balancer expose the running Pod for client traffic; CoreDNS resolves service discovery internally. Include small callouts for Deployment, ReplicaSet, and Pod relationship near the control-plane-to-node path, with concise English labels. Add a numbered legend 1-7 in English walking through lifecycle: 1. Client submits Deployment manifest to the Kubernetes API Server over HTTPS. 2. API Server authenticates the request, checks authorization, and stores desired state in etcd. 3. Controller Manager detects the Deployment and creates or updates ReplicaSet and Pod definitions. 4. Scheduler selects a Worker Node and binds the Pod based on available resources. 5. kubelet instructs the Container Runtime to pull the image and start the Pod containers. 6. Pod status is reported back to the API Server, while Service and CoreDNS enable stable discovery. 7. External traffic reaches the Pod through Ingress or Load Balancer to Service, then to the running Pod, returning HTTP 200 OK. Style: cyberpunk neon with warm beige and navy palette, subtle glowing edges, dark navy background, warm beige panels, neon cyan and magenta accent lines, high contrast but readable enterprise diagram aesthetics. Mood: advanced, technical, staff-engineer level, futuristic but disciplined, not a marketing poster. Use editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Include a small subtle note in English: "Illustrative architecture flow, not an audited reference design." Do not include any real cloud-vendor logos; use only generic cloud, server, container, 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).