-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: nginx config for request size and timeouts #129
Conversation
Hi @abuchanan-airbyte. When will this be merged in? |
@abuchanan-airbyte does this merge mean we can repull airbyte using abctl and have the fix? |
@niveditabaliga-payroc we'll cut a release soon that will include this change. |
hi @abuchanan-airbyte . We downloaded the new version of abctl (v0.18.0 by running the curl command curl -LsfS https://get.airbyte.com | bash -), ran abctl local install and when we opened up Airbyte, we still faced the HTTP 413 error when setting up a connection to a source DB with over 100 tables. Are you able to guide us on why that would still happen? |
@niveditabaliga-payroc Perhaps you could join the Slack channel, so we can debug the issue https://docs.airbyte.com/community/getting-support |
adding annotation to
then add under metadata (50m = 50 mb, if you need more add higher number, etc..)... metadata:
annotations:
nginx.ingress.kubernetes.io/proxy-body-size: "50m" Should work momentarily.. Just a temporarily fix though, I don't know if this is best method, but works for me. |
thank you for the input @japerry911 . I will remember this in case we run into this issue again. For the time being, the fix released the day before worked after we ran the following commands
|
Set up some nginx config for request body size and timeouts.
Related issues:
Unfortunately, I think this will only work on new installs or uninstall + reinstall. In my tests, I couldn't get this to update my existing ingress.
The request body size is fairly easy to test by creating a postgres source with lots of tables/columns:
after:
I'm not sure how to test the timeout setting yet.