OpsBurger opened a new issue, #47161: URL: https://github.com/apache/airflow/issues/47161
### Apache Airflow Provider(s) airbyte ### Versions of Apache Airflow Providers airbyte provider version == 5.0.0 ### Apache Airflow version 2.10.5 ### Operating System linux-arm64 ### Deployment Official Apache Airflow Helm Chart ### Deployment details We're using the official helm chart with the Airflow `2.10.5` image in an `EKS 1.31.0` environment (arm based) with the Airbyte operator version `5.0.0` installed. Airbyte OSS is also deployed on the same cluster **with auto disabled**. ### What happened When trying to access Airbyte using the Airbyte sync operator using the default connection set as follows: `airbyte://http://<svc name>.<namespace>.svc.cluster.local/api/public/` (by following [this manual](https://airflow.apache.org/docs/apache-airflow-providers-airbyte/stable/connections.html)) we get error 415 (unsupported media type), which basically means there is an issue with the headers being set to Airbyte. The Airbyte connection requires a client key and secret, as stated in the manual I attached above, but Airflow is set to `no auth`. Could this be the issue? ### What you think should happen instead The Airbyte operator should send the right headers and sync the connector successfully. ### How to reproduce 1. Install the official helm chart with the Airflow `2.10.5` image in an `EKS 1.31.0` environment (arm based) with the Airbyte operator version `5.0.0` installed. 2. Deploy Airbyte OSS version `1.2.0` and set it to "no auth" 3. Create a basic connector of any kind in Airbyte and copy its ID. 4. Create a default connection for Airbyte in the airflow environment by setting the appropriate env var. 5. Write a sync dag for Airbyte. 6. Trigger the dag and watch the results. ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
