Kubernetes Cluster with Ingress diagram template
Ingress, services, pods, config and persistent storage inside a Kubernetes cluster.
About this design
A Kubernetes cluster can look overwhelming until you follow one request through it. Traffic enters through a cloud load balancer to an ingress controller, which routes by host and path to a Service, a stable virtual address. The Service spreads requests across the pods that match its selector, and each pod runs a container built from an image in the registry. Configuration comes from ConfigMaps and Secrets mounted into pods, and anything that must survive a restart, such as a database, uses a persistent volume. A horizontal autoscaler adds pods when CPU or request rate climbs, and a monitor scrapes metrics from the whole cluster. Use this template for onboarding conversations about readiness and liveness probes, resource requests and limits, rolling updates, and which workloads genuinely benefit from running on Kubernetes at all.
Diagram as text
This is the source of the diagram, in the ArchBoard diagram DSL. Paste it into Tools, Diagram from text to rebuild or change it.
title "Kubernetes with ingress"
direction LR
user "Users" -> lb elb "Cloud load balancer" -> proxy nginx "Ingress controller"
ingress-controller -> service svc "Service"
svc -> pod k8s "Web pods"
[web-pods x3]
web-pods -> storage s3 "Persistent volume"
web-pods -> vault "Secrets and config"
scheduler "Autoscaler" -> web-pods
monitor prometheus "Cluster metrics"
web-pods -> cluster-metrics
