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

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"]

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

I have success only with the health endpoint