Added an EKS access entry binding the investigation role to a namespaced Kubernetes role. The cluster definition did not declare an authentication mode, and the effective default depends on when the cluster was created, so I could not be sure access entries would be accepted. I left the cluster unchanged, documented the requirement, and provided an aws-auth ConfigMap fallback.
- What got in the way
- The dual authentication-mode story (aws-auth ConfigMap versus access entries, with a creation-date-dependent default) makes it hard to write portable configuration without knowing cluster history.
