Trouble deploying Airbyte on Kubernetes with S3 storage configuration

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

The user is facing issues deploying Airbyte on Kubernetes with S3 storage configuration. They are encountering an ‘Internal Server Error’ related to connecting to the MinIO service. The user has shared their values.yaml file and Terraform configuration.


Question

Guys, I need help.

I’ve been trying to deploy Airbyte in a productive Kubernetes environment for two days now and I’m not succeeding.

I have already faced several challenges, now I am trying to configure MiniO as it is not working. So, I decided to go for the approach of using S3, but I configure everything and simply when testing a destination or source this error message appears.

I’m using chart version “0.50.13”

Internal Server Error: Unable to execute HTTP request: Connect to airbyte-minio-svc:9000 [airbyte-minio-svc/ip-private] failed: Connection refused

Could anyone help me?

values.yaml

  storage:
    type: "S3"
    storageSecretName: airbyte-config-secrets
    bucket:
      log: airbyte-workload-bucket
      state: airbyte-workload-bucket
      workloadOutput: airbyte-workload-bucket
    s3:
      region: "us-east-1"
      authenticationType: credentials```

terraform
```resource "helm_release" "airbyte" {
  
  count   = var.is_airbyte ? 1 : 0

  chart            = "airbyte"
  name             = var.name
  namespace        = var.namespace
  create_namespace = true
  repository       = "<https://airbytehq.github.io/helm-charts>"
  version          = var.airbyte_version
  values           = [file("airbyte.yaml")]
  set {
    name  = "externalDatabase.host"
    value = module.postgresql.db_instance_address
  }
  set {
    name  = "externalDatabase.password"
    value = var.password == "" ? join("", random_password.password.*.result) : var.password
  }

  set {
    name  = "minio.enabled"
    value = "false"
  }

  set {
    name  = "s3.enabled"
    value = "true"
  }

  set {
    name  = "storage.type"
    value = "S3"
  }

  depends_on       = [module.postgresql]
}```

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1723496766609629) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["kubernetes", "s3-storage", "airbyte", "minio", "internal-server-error", "helm-chart", "terraform"]
</sub>
2

just checked my values.yaml and i’ve got lower case s3, not upper case S3 as you have.

    type: s3```
I'd also recommend not using both values and terraform `set` blocks - that can get really confusing! you can remove the last two sets you have for sure - s3.enabled doesn't exist in the helm chart and storage.type is global.storage.type (which you already set in your values.yaml)
3

Perfect <@U03FNJGED7D>. I’ll try here

4

I tried here, but it keeps giving an error when I test a destionation or source:

Internal Server Error: Unable to execute HTTP request: Connect to airbyte-minio-svc:9000 [airbyte-minio-svc/ip-internal] failed: Connection refused

5

you might need to restart the worker after changing things - i don’t know if it’ll pick up the changes automatically

6

It seems that you are not considering S3 as storage for logs, state…

7

also, i don’t know if you’re on a new enough helm chart version. The older versions of the helm chart did not work for S3 state by default - they required setting some extra env vars in the worker to pass things through. that has been fixed, but you’re using a really old helm chart version.

8

I understood. Could you tell which version already has this as default?

9

I’m just another user like yourself. You can go through git history just as easily as I can if you need an answer to that. I can tell you what version I’m using. I haven’t updated in a few months, but it is working with s3 for state and logs. we’ve got helm chart version "0.64.185"

10

Yes, I did that here hehe

I’m looking at the values.yaml of a very recent one and I’m going to compare it with the one you mentioned.

Thanks for the help.