Evidence · How close AWS is
reference-eks
hand-written reference shape kept in this repository (live/e2e/reference-eks/estate.sh): VPC, EKS cluster, one managed node group, an access entry and a pod identity association, with provider “kubernetes” configured from aws_eks_cluster.this and an exec token, and a four-object cluster leg; one estate across AWS and the cluster it creates (#1113), certified on real AWS by live/live-cert/reference-eks.sh
Set: growing. Lane: reference.
Not clear yet.
Unverified: whether live/e2e/reference-eks or live/e2e/lib has changed since the run recorded above cannot be told from this checkout - this row has recorded no run, so there is nothing to compare the script against. The verdicts above may describe an earlier version of the script (#1264, #1292).
| Stage | Verdict | Duration | Detail |
|---|---|---|---|
| Cold deploy | not run | ||
| Migrate | not run | ||
| Replan from nothing | not run | ||
| No-op apply | not run | ||
| Drift and reconverge | not run | ||
| Rename | not run | ||
| Remove a block | not run | ||
| Change count | not run | ||
| Replace with create_before_destroy | not run | ||
| Crash mid-apply | not run | ||
| Teardown | not run | ||
| Plan, review, apply | not run | ||
| Greenfield apply | not run | ||
| Strict profile (not a headline stage) | not run | ||
| Plan with no local state (not a headline stage) | not run |
Verdicts were recorded from this estate’s crossing script by hand before the script spoke the gauntlet protocol; the next run that does will replace them.
Reproduce it
go run ./tools/gauntlet run reference-eks
Needs Docker (the emulator is pulled at the pinned digest), the AWS CLI, and a
stock terraform or tofu binary on PATH for the cold deploy. The script is
live/e2e/reference-eks/run.sh; BREAK=1 corrupts its assertions to show they are load-bearing.