Open talhakhan119 opened 1 year ago
Can you post this to the troubleshooting slack channel so that people running into similar problems might be able to help?
Can you post this to the troubleshooting slack channel so that people running into similar problems might be able to help?
Sure, Can you please provide the relevant channel link?
Running into the similar issue. Is controller supposed to use serviceaccount when making calls to S3?
@wahab-io - Could you try the workaround suggested here ? https://apache-pinot.slack.com/archives/C011C9JHN7R/p1694409197833749
@swaminathanmanish the above link is not working, can you please share the workaround here?
@swaminathanmanish the above link is not working, can you please share the workaround here?
@xiangfu0 had suggested the following in that slack thread to the problem described in this issue -
<<Can you check IAM Role Trust Relationship: Make sure that your EKS nodes (or the EKS service itself) can assume the IAM role arn:aws:iam::333870179331:role/pinot. If the trust relationship is not configured correctly, then your nodes won’t be able to assume this role.
Also check the Annotations: You’ve annotated your service account with eks.amazonaws.com/role-arn. Make sure that this service account is actually being used by your pod. You can check this by describing the pod or statefulset (kubectl describe pod
I am unable to start my pinot controller pod in AWS EKS environment.
For that I have added configurations in values.template.yaml for pinot to connect it from aws s3
As I have confirmed my serviceaccount have correct permissions and policies to access AWS S3
As I have tested it while exec into another pod using the same service account:
Configurations:
The data directory for aws s3 bucket is:
The following Error logs I am facing:
As I am using a service account to access aws in my pinot-controller pod as the specs of service account are as:
This is the policy for pinot :