Contract

• Input: application architecture, traffic patterns, availability target, resource constraints.
• Output: Kubernetes manifests + architecture documentation + monitoring rules.
• Side effects: may create resources when executed (deployment, service, configmap).
• Dependencies: Kubernetes cluster access (if execution required).
• Stop condition: manifests saved; architecture documented.
• Risk: medium — production deployment can cause outages; design-only by default.
• Boundary: produces manifests and design; deployment only when explicitly executed.

Kubernetes Orchestration Design

Design a Kubernetes deployment — architecture, deployment strategy, service mesh, observability — with reproducible manifests.

Process