Description: I am doing testing to deploy airbyte with default values to AWS EKS via helm chart by terraform (helm_release).
default values: airbyte 0.45.8 · airbytehq/airbyte
TF code:
resource “helm_release” “cluster_airbyte” {
name = “airbyte”
repository = “Usage | helm-charts”
chart = “airbyte”
version = var.helm_version
lint = true
namespace = var.namespace
create_namespace = true
force_update = true
dependency_update = true
values = [file(“values.yaml”)]
timeout = 600
}
deployment failed with error: ╷ │ Error: failed pre-install: pod airbyte-airbyte-bootloader failed
pods status are:
NAME READY STATUS RESTARTS AGE
airbyte-airbyte-bootloader 0/1 Error 0 7m3s
airbyte-db-0 0/1 Pending 0 7m5s
airbyte-minio-0 0/1 Pending 0 7m4s
Error message within pod airbyte-airbyte-bootloader :
ERROR i.a.d.c.DatabaseAvailabilityCheck(lambda$isDatabaseConnected$1):78 - Failed to verify database connection.
events message for airbyte-db and airbyte-minio are: running PreBind plugin “VolumeBinding”: binding volumes: timed out waiting for the condition
Please help to provide some suggestion about fixing.
thanks
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