58 lines
3.1 KiB
Markdown
58 lines
3.1 KiB
Markdown
# Scene prompt - Course II scene B: the control plane (four processes and a filing cabinet)
|
|
|
|
v2 diagram: kube-apiserver (the only door), etcd (consensus truth), scheduler
|
|
(filter -> score -> bind), controller-manager (the loops). Five parts.
|
|
Generate ~4 at 16:9, curate with the reject checklist, save to disk for pickup.
|
|
|
|
---
|
|
|
|
Dark technical exploded-view illustration in a cinematic sci-fi engineering style.
|
|
Solid near-black deep void background, hex #070b14 - completely clean: no stars, no grid,
|
|
no texture, no particles behind or around the objects. Matte dark metal-and-glass surfaces
|
|
with glowing neon edge lighting: primary cyan #3fbaf5, secondary magenta #e879f9 accents,
|
|
cool white rim highlights. Camera: fixed 30-degree isometric angle, subject perfectly
|
|
centered with generous empty margins on all sides. Even studio lighting, no vignette,
|
|
no lens flare, no depth-of-field blur. ABSOLUTELY NO text, no letters, no numbers, no
|
|
words, no code, no glyphs, no labels, no arrows, no callout lines, no UI elements
|
|
anywhere in the image - every surface marking must be an abstract geometric pattern
|
|
only. Every component is fully separated from its neighbours by generous gaps of pure
|
|
void - nothing touching, nothing overlapping, and no beams, cables, or connectors
|
|
spanning between the separated parts.
|
|
|
|
The subject: five distinct machines floating apart in the void, the internals of one
|
|
control room pulled apart for inspection.
|
|
|
|
Front and centre: a tall imposing gateway block - a monolithic dark metal doorframe with
|
|
a single bright cyan glowing vertical slot down its middle, clearly the only entrance to
|
|
the scene, the most commanding object in the frame.
|
|
|
|
Behind and below the gateway: a heavy squat vault - a dark armoured strongbox with
|
|
layered horizontal plates like sealed drawers and a deep cyan glow escaping from its
|
|
seams, visibly the most protected object in the scene.
|
|
|
|
To the left of the gateway: a precise instrument block - a slim dark machine with a
|
|
tilted glass top face showing an abstract geometric sorting pattern of cyan facets,
|
|
elegant and analytical.
|
|
|
|
To the right of the gateway: a compact engine block with several small circular recesses
|
|
on its face, each recess holding a glowing magenta ring, like a bank of idling rotary
|
|
mechanisms.
|
|
|
|
Above the gateway, small and off to one side: a little drifting cluster of three tiny
|
|
identical dark chips with faint cyan edges, minor satellites of the bigger machines.
|
|
|
|
---
|
|
|
|
## Build-side notes (not part of the prompt)
|
|
|
|
- **Slice plan:** 5 polygons - apiserver gate, etcd vault, scheduler instrument,
|
|
controller-manager ring bank, the chip cluster (spawned pods motif). Collapse draws
|
|
everything in toward the gate (everything watches the api-server, nothing talks
|
|
sideways); scrub opens to the hero. Clamp at hero.
|
|
- **Legend mapping (v2 terms):** kube-apiserver "the only door - authn, authz, admission,
|
|
persistence" / etcd "consensus truth - quorum or nothing" / scheduler
|
|
"filter -> score -> bind" / controller-manager "the reconciliation loops" / chips =
|
|
Deployment -> ReplicaSet -> pods lineage.
|
|
- **Watermark:** Gemini sparkle bottom-right - strip with
|
|
`bztmon-site/scripts/dewatermark.mjs` before slicing.
|