Leandro Bleda
10/17/2024, 11:57 AMuser
10/17/2024, 11:58 AMserver_url
for the Terraform provider when using Airbyte deployed in Kubernetes EKS should point to the service that exposes the Airbyte API. In the case of Kubernetes, you might use a command like kubectl port-forward
to forward a local port to the service. An example of this can be seen in one of the [knowledge sources](https://github.com/airbytehq/airbyte/issues/33219): shell kubectl port-forward svc/airbyte-airbyte-api-server-svc -n airbyte 8006:80
After running this command, you could access the Airbyte API at <http://localhost:8006/v1/>
. This would be the server_url
you'd use in your Terraform provider configuration: tf provider "airbyte" { password = "airbyte" server_url = "<http://localhost:8006/v1/>" username = "airbyte" }
However, please note that this setup is for local development and testing. For a production environment, you would typically set up an Ingress in your Kubernetes cluster to expose the Airbyte API service, and the server_url
would be the URL of this Ingress. Also, be aware that the Airbyte API server is being phased out in favor of the airbyte-webapp-svc
endpoint. You might need to adjust your setup accordingly, as discussed in another [knowledge source](https://github.com/airbytehq/airbyte/issues/2763).Leandro Bleda
10/17/2024, 12:03 PM