fix: Allow upload limit increase in kubernetes deployment #7664
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For kubernetes deployments, the maximum filesize for e.g. File Components is capped at 1MB due to the Nginx default limit
Since the Nginx service is started via a start-nginx.sh file, adding annotations to the ingress part of the values.yaml does not work
e.g.
or
The workaround described in the helm repo also does not work (for me) since the ingress.yaml template sets the service name and port for every path identically:
The proposed change would allow the configuration of the client_max_body_size for the nginx configuration while using the existing environment variable
LANGFLOW_MAX_FILE_SIZE_UPLOAD
. Reusing this variable makes sense as it's purpose is to configure the maximum upload size.