Kubernetes Deployment Flowchart: Ingress to Pods

Mermaid code

flowchart TD
    C[Client] --> I[Ingress<br/>api.example.com]
    subgraph NS["Namespace: shop"]
        I --> S[Service<br/>ClusterIP :80]
        subgraph DEP["Deployment: api (3 replicas)"]
            P1[Pod api-1]
            P2[Pod api-2]
            P3[Pod api-3]
        end
        S --> P1
        S --> P2
        S --> P3
        CM[ConfigMap<br/>app settings] -.-> P1
        SEC[Secret<br/>database credentials] -.-> P1
        P1 --> PV[(PersistentVolume<br/>uploads)]
    end

Paste this into any tool that renders Mermaid, or into the editor to change the theme and export PNG or SVG. Syntax reference: Flowchart guide.

What this diagram shows

Follow the request from Client to the Ingress, into the Namespace: shop subgraph, through the Service to one of three pods inside the Deployment subgraph. Dotted edges from ConfigMap and Secret show configuration mounted into the pods, and the cylinder PersistentVolume holds uploaded files. Only Pod api-1 is wired to the mounts to keep the picture readable; the other two are identical.

Nested subgraphs are what make this a flowchart job. They map directly onto the namespace and deployment boundaries that Kubernetes itself uses.

How to adapt it

• Rename Namespace: shop and Deployment: api to your real namespace and workload names.
• Add a second deployment subgraph, for example a worker, and connect it to a Queue node instead of the service.
• Replace Service<br/>ClusterIP :80 with Service<br/>LoadBalancer if you expose the workload without an ingress.
• Add a HPA[HorizontalPodAutoscaler] node with a dotted edge into the deployment subgraph to show autoscaling.
• Draw the Secret and ConfigMap edges to all three pods if you want to stress that every replica gets the same configuration.

FAQ