Airbyte in Kubernetes with S3 Log Storage

Summary

Using Airbyte in Kubernetes with S3 as log storage and encountering error 500 when configuring sources or destinations.


Question

Hello friends, does anyone use airbyte in Kubernetes using S3 as log storage? Have you ever faced any problems? When I configure it, I face error 500 when trying to enter any source or destination.



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["airbyte", "kubernetes", "s3", "log-storage", "error-500", "source", "destination"]

<@U03FNJGED7D>, Hello again.

I’m working to deploy Airbyte on Kubernetes using EKS, but I’m having a lot of difficulty finding documentation informing about the possible values.yaml configurations.
Could you give me your values.yaml, removing all the information you don’t want to share?

i’d recommend just using the chart itself as a source. https://github.com/airbytehq/airbyte-platform/tree/main/charts. i usually start with the main values.yaml file, but sometimes there are values supported that aren’t documented there. my usual strategy is to start with a template for the item i’m trying to change and see if there are any explicit references to .Values.___ that are the missing clues. good luck!

Thank you, I’m going to need luck, you’re helping me a lot

yes, we do. i recall docs being incomplete, but you can get it to work

can you help me? According to the documentation, an error always occurs!

always the same error

if you’re able to share the relevant section of your helm values file, I can compare to ours and see if there’s something obviously off.

https://pastebin.com/kxLRFNMj

what version of the helm chart are you using? if its something recent, there’s quite a bit you’re missing. (it’s a lot simpler though - replaces all the extraEnv nonsense you used to need!)

take a look at this sample values.yaml - you’ve got a lot more to populate in your global.storage section https://github.com/airbytehq/airbyte-platform/blob/7eea81d81ff3c39c540f9511596a40333ec0491c/configs/airbyte.sample.yml#L27-L39

if you’re only trying to get logs working, then you only need to configure bucket.log I’d imagine. we only have log and state there, not all 4

Could you give me the relevant part of your values?

  image:
    tag: ${airbyte_version}
  storage:
    type: s3
    bucket:
      log: ${s3_logs_bucket}
      state: ${state_bucket}
    s3:
      authenticationType: instanceProfile
      region: ${aws_region}```

the first example I sent was setup for that from the look of it.

i’m a user like you - i don’t know about the state of documentation.

When I started using Airbyte, I thought the documentation would be magic :joy:

I’m going to do some tests here, thank you very much, you’re helping me a lot!

hey, have you setup an external db? I no longer trust the documentation. If you can pass it on to me I would appreciate it

i’m not on the latest helm chart and I think I saw that it changed recently, so I wouldn’t use anything I have for that. I tend to use the helm chart itself as the source of truth for these sorts of questions