Technical
Basic K8s Architecture template
Ingress, service, deployment, pods, storage and config
What’s inside
- Nodes
- 8
- Packs
- CoreKubernetes
- Category
- Technical
Works on the Free plan: 15 diagram nodes + 150 notes, text, stickers & mind map topics per diagram.
This template is a minimal Kubernetes architecture for a production API: an Ingress routes traffic to a Service, the Service exposes a Deployment, the Deployment runs two Pods, and the Pods store data in a PersistentVolumeClaim and read settings from a ConfigMap.
Each element is a real Kubernetes node from the Kubernetes pack, not a generic box with an icon, and every edge is labelled with what it does: routes_to, exposes, runs, stores_in, config_from. Use it as the starting point for your own cluster diagram, add namespaces, secrets, or autoscalers, and keep the picture next to the manifests it describes.
When to use it
- Documenting a service before or after it moves to Kubernetes.
- Explaining the request path from ingress to pods to a new team member.
- Reviewing storage and configuration dependencies before a migration.
- Adding a clear architecture picture to a design document or runbook.
How to use it
Rename the Service, Deployment, and ConfigMap to match your workload.
Add the replicas, namespaces, secrets, and other resources your service actually uses from the Kubernetes pack.
Keep the edge labels accurate so the diagram reads like the request and data flow.
Share a link with the team, or export SVG or PNG for documentation, and save a revision whenever the architecture changes.
Questions
Can I import my Kubernetes manifests?
Yes. Paste manifests or kubectl get -o yaml output into the free Kubernetes YAML to diagram tool, or use Import YAML in the editor. Namespaces become frames, and Ingress, Services, workloads, ConfigMaps, and volumes are drawn as Kubernetes nodes connected the way the YAML wires them, ready to edit. Docker Compose files import the same way.
Which Kubernetes resources are available?
The Kubernetes pack has 33 resource types: namespaces, nodes, pods, deployments, stateful sets, daemon sets, replica sets, jobs, cron jobs, services, ingresses, ingress classes, Gateway API gateways and routes, network policies, config maps, secrets, persistent volumes and claims, storage classes, service accounts, roles, cluster roles and their bindings, horizontal and vertical pod autoscalers, pod disruption budgets, resource quotas, limit ranges, webhooks, custom resource definitions, and custom resources.
Can I combine Kubernetes with cloud or C4 diagrams?
Yes. Cloud, C4, network, and other packs work on the same canvas, so you can show the cluster inside its cloud region or next to the C4 container it implements.
Open a canvas in a minute
Sign in with Google or GitHub. Free for a single seat. Upgrade when the team joins.