场景
平台团队正在上线新集群：default 与 payments 两个 namespace、一个公网 Ingress、两个 Deployment，以及一个 HPA。值班需要一张站会之后还能开着的地图，而不是白板照片。
把 Kubernetes 节点放到与云、网络包相同的无限画布上。端口会连上。拓扑就绪后分享带品牌的公开链接，或导出 SVG/PNG。Pro 增加嵌入与无水印 PDF/JPEG。
已经有 YAML 了？
把清单粘贴到免费的“Kubernetes YAML 转图表”工具中，开始绘制之前就能先看到图表。
你画什么
Kubernetes 架构图
- 作为框架的 Namespace
- Node、Pod、Deployment、StatefulSet、DaemonSet、Job、CronJob
- Service、Ingress 与 Gateway API 路由
- ConfigMap、Secret、PVC、PersistentVolume、StorageClass
- HPA、PodDisruptionBudget、NetworkPolicy 与 RBAC 角色
- 当地图跨账户时，在工作负载旁放 cloud.k8s-cluster
为什么选 Archboard
Archboard 是托管的 Kubernetes 架构画布：节点看起来像控制平面，端口像流量一样连接，同一块板还能放云区域或 C4 上下文视图。用 Kubernetes 包免费开始；订阅 Pro 以获得无限节点、嵌入与无水印导出。
此画布上的节点包
Kubernetes · 云 · 网络 · Docker
所有内置节点包都在 Free 中（3 张图，每张 15 个图表节点 + 150 个便签、文本、贴纸和思维导图主题，带品牌的公开分享，与您的 AI 智能体实时编辑）。Pro 增加无限图表与节点、让队友实时编辑的席位、嵌入和无水印导出（$10/席/月）。
一次会话怎么走
用 Google 或 GitHub 登录并打开画布
放下 Namespace 框架，再在其中放入 Deployment、Service 与 Ingress
连接南北向流量的端口；故事需要时加上 HPA 与 NetworkPolicy
分享带品牌的公开链接，或升级到 Pro 以嵌入和无水印导出
Kubernetes diagrams that survive the sprint
Most Kubernetes architecture diagrams die as whiteboard photos. Someone sketches Namespace boxes during planning, the photo goes stale before the next deploy, and the on-call is left reading YAML to answer a simple question: what talks to what. A Kubernetes canvas fixes this by making the diagram the map the team keeps open. Namespace frames hold Deployments, Services, and Ingress the way the cluster holds them; ports connect like traffic; labels carry the names kubectl shows. When the topology changes, the same canvas changes, and nobody redraws it from a photo.
Start with one namespace and the public path into it: Ingress, then the Service behind it, then the Deployment and its Pods. Add ConfigMaps, Secrets, and PersistentVolumeClaims only where the story needs them, because a diagram that shows everything shows nothing. HorizontalPodAutoscalers and NetworkPolicies belong on the same board because scaling and policy are the questions reviewers actually ask. Keep cloud region frames next to the cluster when workloads span accounts; the canvas holds Kubernetes, cloud, and network packs together, so the map never splits across tools.
From cluster map to design review
A good Kubernetes diagram earns its keep in reviews. Share a branded public link when the topology is ready and let reviewers pan and zoom instead of squinting at a screenshot. Save a revision snapshot before each rollout so the previous shape is one click away, and export structured JSON when the platform team wants the model, not just the picture. SVG and PNG snapshots cover tickets and docs; Pro adds embed for runbooks plus watermark-free PDF and JPEG.
The same board can carry the C4 context view above the cluster: Person and Software System at the top, Namespace frames below, so product and platform point at one picture. That is the difference between a drawing file and an architecture workspace: the Kubernetes canvas stays current because it is where the conversation already happens. Sign in with Google or GitHub, open the Kubernetes pack on Free, and draw the namespace you are shipping this week.
Open a published example
- Kubernetes MicroservicesIngress, Service, Deployment, Pod, PVC, and Postgres on one board.
- Docker Runtime MeshContainers, networks, and volumes behind a load balancer.
- Multi-Region Cloud HAThe same workloads mapped across two cloud regions.
Questions
Do I need a running cluster to draw Kubernetes diagrams?
No. The Kubernetes pack is a drawing surface with 33 resource types, from Namespace, Pod, Deployment, StatefulSet, Service, and Ingress to Gateway API routes, RBAC roles, persistent volumes, and custom resources. Draw first, or paste your manifests into the Kubernetes YAML to diagram tool, then compare against the live cluster during review.
How is a Kubernetes canvas different from a whiteboard?
Whiteboards are wiped. An Archboard canvas autosaves, keeps revision snapshots, exports JSON plus SVG, PNG, JPEG, and PDF, and shares branded public links, so the map survives the meeting it was drawn in.
Can platform and product teams share one diagram?
Yes. Put the C4 context or a wireflow next to the Namespace frames on the same infinite canvas. Organizations, seats, and roles keep the workspace shared without sharing a whiteboard photo.