flowboard

Architecture in practice

Kubernetes delivery

Open the cluster and distinguish deployment from runtime traffic.

Start from template Download JSON

This opens a separate browser draft; your main draft remains unchanged.

Readable source

The labels explain the system to a reader. Stable identifiers connect the nodes to the flows. Keep a copy of this source, then adjust it to match your own architecture.

# Kubernetes delivery
- CI build {#build type=service x=60 y=100}
- Image registry {#registry type=service x=360 y=100}
- Production cluster {#cluster type=k8s x=680 y=100}
  - Application pod {#pod type=pod x=740 y=190}
## Flows
- build -> registry {#push label="push image"}
- registry -> pod {#pull label="pull image"}

Make one useful change.

Rename a component, explain a connection or add a note about a missing assumption. Export the result as Markdown, JSON or YAML to keep an editable copy.

Learn the import and export workflow