# 14_interactive_prod#4 — FAILED | field | value | |---|---| | campaign | RELIABILITY (mongodb × aws) | | archetype | generative | | date | 2026-10-10T19:58Z | | gate version | v1.1 | | deployment | dep-2d297609 | | deploy status | failed (5686s) | | gate | healthz=— connection=— logs=— metrics=— | | teardown clean | True | ## Attribution - **bucket:** AGENT - **class:** eks-render-chain (policy ARN path → EBS CSI without IRSA → helm chart schema) - **evidence:** Five distinct errors in one slot on a production EKS render: a managed-policy ARN missing its service-role/ path, then the EBS CSI add-on stuck CREATING for 40 minutes because the controller fell back to IMDS without IRSA (evidence lived only in the add-on's pod logs), then a Helm chart values-schema mismatch; the ladder declared thrashing and stopped. - **resolution:** Four nets shipped the same day: exemplar now carries the EBS CSI add-on via IRSA and exact managed-policy paths; a hard rule forbids the psmdb-db chart; an evidence sensor pulls an add-on's health issues and controller-pod cause from Container Insights into the repair turn. Scenario 14 then passed 4/4. ## Recorded reason (scrubbed) ``` (none recorded) ```