Error HTTP 413 when clicking Finish & Sync

Summary

Unknown error HTTP 413 occurs when clicking Finish & Sync from SQL Server to BigQuery using Airbyte 0.64.7 and Helm 1.0.0-alpha


Question

Hi all

An unknown error occurred. (HTTP 413)
When clicking Finish & Sync

Source: SQL Server 4.1.14
Destination: BigQuery 2.9.0
Airbyte: 0.64.7
Helm: 1.0.0-alpha



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

["error", "http-413", "sql-server", "bigquery", "airbyte", "helm"]

it looks like you need annotation like this in your values.yaml file

  ingress:
    annotations:
      <http://nginx.ingress.kubernetes.io/proxy-body-size|nginx.ingress.kubernetes.io/proxy-body-size>: 16m```
<https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#custom-max-body-size>

Thanks for help. Still encountering same error

An unknown error occurred. (HTTP 413)

webapp:
  ingress:
    annotations:
      nginx.ingress.kubernetes.io/proxy-body-size: 16m```
Deployment command
```abctl local install --values ./values.yaml --insecure-cookies                                                                              ✔ │ 23:27:50 ```

Try this:
docker exec -it airbyte-abctl-control-plane kubectl -n airbyte-abctl annotate ingress ingress-abctl <http://nginx.ingress.kubernetes.io/proxy-body-size=16m|nginx.ingress.kubernetes.io/proxy-body-size=16m>

That worked, thank you

We’re working on adding these configs (e.g. request size and timeout) to abctl by default

<@U07FH2Y34A1> can you add solution for HTTP 413 to troubleshooting?
https://docs.airbyte.com/deploying-airbyte/troubleshoot-deploy

Is it possible to configure <http://nginx.ingress.kubernetes.io/proxy-body-size|nginx.ingress.kubernetes.io/proxy-body-size>: 16m with values.yaml?
I realized that my previous message was for helm charts deployment on regular k8s, but abctl uses separate ingress-nginx chart and it couldn’t work for webapp.

It’s not possible yet to configure nginx via values.yaml. Perhaps we could allow a --nginx-values flag though