Enabling API calls for triggering syncs in Airbyte on K8s using Helm

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

Summary

Upgraded Airbyte on K8s using helm to enable API calls for triggering syncs, encountering 404 errors, seeking help to configure the necessary parameters in values.yaml file.


Question

Hi Everyone! Hopefully this is a simple question.

Our data team deploys Airbyte on K8s using helm. We just upgraded to the version that allows for API calls to trigger syncs. However, I think we’re missing some magic parameter to enable this API in our values.yaml file because I keep getting 404s when testing these out. Does anyone have experience with this?


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

["enabling-api-calls", "triggering-syncs", "airbyte", "k8s", "helm", "404-error", "values.yaml"]
2

I am facing the same problem, except that I am using just docker. Some API calls work, so do not.

3

I have success only with the health endpoint

4

Hi

Hopefully not to late for this. I’m also facing the same issue. I’m able to trigger sync whenever I use a pod, but unable to do it i Airflow (my final goal)

With respect to the API, in Kuberntes, the host airbyte-airbyte-api-server-svc:80 (if you’re requesting it from Airbyte itself and haven’t changed the chart paramter)

5

i moved on from Airbyte after i didn’t find any support

6

I’m facing issues using Airflow only. I’ll give it a shot on Monday using custom triggers, but using this endpoint seems to do the trick