EKS cluster and Karpenter components were created, but have error messages in Karpenter controller log:
2022-09-05T12:16:18.813Z ERROR controller.aws.pricing updating spot pricing, UnauthorizedOperation: You are not authorized to perform this operation.
status code: 403, request id: 8f99fa14-175e-48a5-bfc9-747616e81ded, using existing pricing data from 2022-08-17T00:19:52Z {"commit": "3d87474"}
...
2022-09-05T12:16:19.227Z ERROR controller.aws.pricing updating on-demand pricing, AccessDeniedException: User: arn:aws:sts::269621987045:assumed-role/eksctl-cluster-with-karpenter-iamservice-role/1662380178445292353 is not authorized to perform: pricing:GetProducts because no identity-based policy allows the pricing:GetProducts action
status code: 400, request id: ca453ae3-e67e-4d3f-9c9a-a1b54958a6e6; AccessDeniedException: User: arn:aws:sts::269621987045:assumed-role/eksctl-cluster-with-karpenter-iamservice-role/1662380178445292353 is not authorized to perform: pricing:GetProducts because no identity-based policy allows the pricing:GetProducts action
status code: 400, request id: 4976ddb4-3943-4f34-ba76-d647e638d2f6, using existing pricing data from 2022-08-17T00:19:52Z {"commit": "3d87474"}
What were you trying to accomplish?
Create EKS cluster with Karpenter support.
What happened?
EKS cluster and Karpenter components were created, but have error messages in Karpenter controller log:
How to reproduce it?
Create EKS cluster with following config file:
Logs
Log of Karpenter controller:
Anything else we need to know?
The IAM policy for Karpenter lacks of some actions when compared to Karpenter CloudFormation: Karpenter IAM policy in eksctl: https://github.com/weaveworks/eksctl/blob/main/pkg/cfn/builder/karpenter.go#L112 Karpenter IAM policy in Karpenter Cloudformation: https://github.com/aws/karpenter/blob/main/website/content/en/v0.15.0/getting-started/getting-started-with-eksctl/cloudformation.yaml#L43
Versions