Issue with the installation of Airbyte on AWS EKS ( 1.32 ) using Helm 1.6.2

[ricardozd]

Helm Chart Version

1.6.2

What step the error happened?

On deploy

Relevant information

Hello, team!
We are currently experiencing an issue with the installation of Airbyte on AWS EKS using Helm.
Although we have installed the latest version, we’re encountering an internal error related to the creation of the airbyte-auth-secrets Kubernetes secret. We have verified all relevant permissions, roles, and service accounts, but so far have been unable to identify the root cause.
The error appears intermittently and is triggered by the bootloader pod. Eventually, after several retries, the bootloader does succeed, allowing us to proceed. Once it completes successfully, we disable the bootloader to prevent it from interfering with any future infrastructure changes.

File main_eks.txt --> instalation of AWS EKS
File main_helm --> installation helm airbyte
File values.txt --> airbyte config

values.txt

main_eks.txt

main_helm.txt

Relevant log output

2025-05-14 19:54:58,872 [main] ERROR i.a.b.ApplicationKt(main):28 - Unable to bootstrap Airbyte environment.
io.fabric8.kubernetes.client.KubernetesClientException: The timeout period of 10000ms has been exceeded while executing PUT /api/v1/namespaces/airbyte/secrets/airbyte-auth-secrets for server null
...
Caused by: io.vertx.core.impl.NoStackTraceTimeoutException: The timeout period of 10000ms has been exceeded while executing PUT /api/v1/namespaces/airbyte/secrets/airbyte-auth-secrets for server null

[slate71]

@ricardozd Could this be due to an under-resourced cluster?

We're also curious about why/how you're disabling the bootloader.

[ricardozd]

At the moment, I don't believe it's a resource issue. The node is currently idle in AWS, and the instance type is c7g.2xlarge.

To disable the bootloader, I set it to false in the values.yaml file like this:

airbyte-bootloader: enabled: false image: repository: airbyte/bootloader # The pull policy for the Airbyte bootloader image pullPolicy: IfNotPresent

I'm disabling it because, after many attempts, I finally managed to get past that step. However, if I need to make changes in the Helm chart (especially resource-related), I can't afford to have the bootloader failing every time it runs.