docs: add branded diagram design guidance (#3316)
This commit is contained in:
@@ -17,6 +17,14 @@ Kandev ships example Kubernetes YAML in `k8s/`. The control-plane files are a si
|
||||
|
||||
To run task sessions as Pods, follow [Configure the Kubernetes executor](#configure-the-kubernetes-executor) after the control plane is reachable. That is a separate cluster-authority decision.
|
||||
|
||||

|
||||
|
||||
[Open full-size SVG diagram][k8s-diagram]
|
||||
|
||||
[k8s-diagram]: ../../docs/screenshots/k8s.svg
|
||||
|
||||
The control-plane Pod owns the persistent home and API identity. Task-session Pods are a separate, opt-in workload path with their own service-account permissions.
|
||||
|
||||
## Architecture and limitations
|
||||
|
||||
The example creates:
|
||||
|
||||
Reference in New Issue
Block a user