Configuring state storage to s3?

Platform, Deploy & Infra Issues
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: AWS EKS
  • Memory / Disk: 1TB
  • Deployment: Kubernetes
  • Airbyte Version: 0.40.2

I am trying to configure the state storage to push data to s3 instead of storing them on the local minio pod. I’ve tried doing something similar to configuring the custom s3 bucket where I set the STATE_STORAGE_MINIO_BUCKET_NAME to the same bucket name as my s3 logs and set STATE_STORAGE_MINIO_ENDPOINT to nothing. Additionally, I’ve also set MINIO_ACCESS_KEY to be the same as my AWS_ACCESS_KEY_ID and MINIO_SECRET_ACCESS_KEY to match AWS_SECRET_ACCESS_KEY.

image
image1152×198 26.1 KB

image
image868×112 15.1 KB

When I deploy these changes, I notice that all my pods successfully runs except airbyte-cron and airbyte-worker which ends up in CrashLoopBackOff. I checked the logs of airbyte-cron and it errored for the following reason.

image
image2354×540 138 KB

How do I go about sending all of the state storage to s3 for my kubernetes deployment?

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

Bump to see if anybody has found a solution

4

Hey @taskrabbit, thanks for your patience! We are at an offsite this week; I am looking into this for you and hope to have some ideas for you early next week!

1 Like
5

Thanks for the help Nataly. Let me know if there’s anything you’ve discovered. Otherwise I’m thinking of adding a script that regularly wipes the “state” folder. Let me know if there are any issues with that.

6

Are you using Kustomize or Helm?

7

We’re using Kustomize

8

I don’t believe this is possible at this point. Please open up a feature request on GitHub and we can look into implementing this!

9

Gotcha, is it possible if I were to use helm?