Hello, i’m trying to implement dremio for a customer using the helm chart to install on EKS. i have configured a PVC and PV which are mounted on the statefulsets.
The issue is after creating an account using the URL from the dremio ingress and restarting the master pod, the user doesn’t persist and it requires me to create a new one.
Thus i concluded that in the event of the dremio master pod crashes and restart, any data i started using with dremio will be lost.
I have went over the helm chart and dremio software documentation but found nothing of help.
I’ll be happy to answer any questions regarding our setup.
Please suggest ways to troubleshoot this issue.
Thanks.
@arielrahamim IT does look like your “db” folder on the coordinator is not on a PVC. Can you please validate that. Usually /opt/dremio/data is what defaults to the PVC
Hello Balaji, thank you it worked! I didn’t find any kind of mention to a “db” folder in the kubernetes documentation, might be worth adding, unless its there and i missed it ofc.
Another question i have, does dremio support secret manager on eks if i’m using IRSA?
@arielrahamim
Will create an internal doc request for “db” folder.
There seems to be an internal document for the IRSA requirement, let me get back to you on that
@balaji.ramaswamy Thank you, waiting for your reply about the IRSA.
@arielrahamim
Empty directory volume for /opt/dremio/aws
Create an init container that reads the values from the env AWS_WEB_IDENTIY_TOKEN_FILE and AWS_ROLE_ARN and creates a file in /opt/dremio/aws/credentials file that contains:
[profile aws_irsa]
web_identity_token_file = <Value of AWS_WEB_IDENTITY_TOKEN_FILE>
role_arn = <Value of AWS_ROLE_ARN>
Use the AWS credentials profile option and set it to use the profile "aws_irsa".