Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Hi. We are having issues accessing the config API in our airbyte deployment on Kube. We are trying to hit the `/api/v1/jobs/get` but we get a 404. Is that the right path?

We want to use this API our orchestration tool to monitor the execution of a job and also capture the errors. How can we expose it?

Just to repeat myself, we are trying to hit the Config API endpoint because the new api doesn't provide the same info but we get a 404. Is it possible to fix this?

<@U05320A3JJF> From your description my guess is that you’re still hitting the new API server but trying to call the config API server endpoint. Not sure how you’re exposing the new API server via kube, but if you’re port forwarding, you’re likely hitting `localhost:8006` and I believe the config API is actually `localhost:8001`. Can you give that a try and let us know if that lets you hit the endpoint?

I’m assuming you’re including a post body with the request with an appropriate ID since you mention that the new API doesn’t provide the same info which makes it seem like you’re able to access the job but just want more data about it. If not, it’s also possible that you’re getting a 404 because the job in question isn’t being found.

Let us know if either of these resolve your issue. Thanks!

I think our problem is that - in kube - this APIs are exposed by different services and our solution to make calls from github actions is only exposing the new API. Is there any plan to align the new api with the config api for things like job status - error logs, better metrics that are missing,...?