Description
The EKS capture environment exists, but it is not reproducible: it lives in rkps-awsinfra alongside an unrelated long-lived estate, and the capture path that produced the corpus entries tagged substrate: eks from gcx_live_readback was assembled by hand.
Port it into synthkit-terraform in the frozen module shape, so all four substrates stand up the same way and the EKS capture can be re-run rather than remembered. Re-running it is what turns the corpus from a one-off snapshot into something that can be refreshed when k8s-monitoring or EKS changes.
Leave the deployed synthkit instance in rkps-awsinfra where it is. That is a long-lived demonstration deployment, not a capture environment, and the two have opposite lifecycles.
Acceptance Criteria
- #1 The EKS capture environment stands up from synthkit-terraform in the frozen module shape
- #2 The eks corpus capture can be re-run from that environment rather than reproduced by hand
- #3 The long-lived synthkit deployment in rkps-awsinfra is left in place and unaffected
Definition of Done
- #1 terraform validate and fmt -check pass
- #2 The environment applies and destroys cleanly, verified post-destroy
Implementation Notes
2026-09-06 per-AC evidence map: AC1 is RKSY-0002 plus the live-estate capture provenance and frozen environment source. AC2 is capture-v2-c01efa82a07645a295e8a810ee6ca004f4a3628cac8a78813eb2e1727c3a1a9f.json with source kind synthkit_terraform_capture and substrate eks, plus the documented capture recipe. AC3 is the current long-lived deployment read-back after the authorized rollback and restore: Synced, Healthy, desired/ready/updated/available 1, zero restarts, and all five Beyla-native families present again. Task remains To Do because its apply/destroy DoD lacks a historical post-destroy sweep and current Terraform validation is pending.
Final reconciliation supersedes the earlier pending-validation note: synthkit-terraform just check passed at 04a228971deef87c11235ff3caddf38d64f1b86d, with hosted validate run 34028703857 successful. Validation DoD is now checked. The historical clean apply/destroy and post-destroy-sweep boundary remains open.
2026-09-06 managed lifecycle proof, via the environment repository recipes:
Scoped aws result: standing=0 unknown=0
Apply complete! Resources: 10 added, 0 changed, 0 destroyed.
Apply complete! Resources: 115 added, 0 changed, 0 destroyed.
Destroy complete! Resources: 125 destroyed.
Scoped aws result: standing=0 unknown=0Capture exit 0 after two-hour loaded soak. New capture remains a protected candidate pending exact producer/configuration routing review; existing corpus acceptance is historical and unchanged.