standard
Role-based access control in Kubernetes, invoked as the audit surface that determines an agent's blast radius.
No evidence-backed relationships are recorded.
Justin O'Leary's ConfigConfusion technique turns on the fact that Google's Config Connector makes every cloud call with its own service account, so a tenant who can create one IAMPolicyMember inherits whatever that account is allowed to grant.
Reality
Admission control and RBAC decide who may fetch a Secret object. Neither is in the path once the kubelet has copied the value into a container, and an agent runtime is where that gap gets expensive.
Reality
A clean STS exchange proves only that IAM let the job in. EKS authorizes separately, and that is the half of the migration most walkthroughs skip.
Reality
One team's write-up: four groups did valid local work, deploy state said done, and nothing in the pipeline asked whether an invoice could still be rendered.
Reality
A dev.to translation table maps most agent vocabulary onto control loops, IAM and sandboxes. What is left over is nondeterminism and unbounded runtime cost.
Reality