Immutable solution version
Anyscale on EKS: the Operator pod needs its own IAM identity, not the node role
Complete solution
the Operator runs as a pod, not an EC2 instance, so it cannot reuse the node group's IAM role: that role's trust policy only allows ec2.amazonaws.com to assume it, not pods.eks.amazonaws.com.
[anyscale/terraform-provider-anyscale]: the Operator runs as a pod, not an EC2 instance, so it cannot reuse the node group's IAM role: that role's trust policy only allows ec2.amazonaws.com to assume it, not pods.eks.amazonaws.com. The fix is an EKS Pod Identity association with a dedicated role trusted by pods.eks.amazonaws.com, bound to the Operator's namespace and service account. That role also needs permission to read and write the object storage bucket the cloud registers, because the Operator checks it during its own startup verification.
Context: The Anyscale Operator fails to start with an IMDS or credentials error that has nothing obviously to do with IAM trust policies.
Evidence
Source: The Anyscale Operator fails to start with an IMDS or credentials error that has nothing obviously to do with IAM trust policies.
Verified resolution: [anyscale/terraform-provider-anyscale]: the Operator runs as a pod, not an EC2 instance, so it cannot reuse the node group's IAM role: that role's trust policy only allows ec2.amazonaws.com to assume it, not pods.eks.amazonaws.com. The fix is an EKS Pod Identity association with a dedicated role trusted by pods.eks.amazonaws.com, bound to the Operator's namespace and service account. That role also needs permission to read and write the object storage bucket the cloud registers, because the Operator checks it during its own startup verification.
Source URL: https://github.com/anyscale/terraform-provider-anyscale/blob/HEAD/docs/guides/create-a-kubernetes-cloud.md
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_dZ2FErTv5TNCgxn4qjRIUA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Anyscale on EKS: the Operator pod needs its own IAM identity, not the node role <span>— Vectle</span></a>