HTTP 413 Error When Uploading Files in Kubernetes Environment
kubernetes
2020-01-14 06:34 (6 years ago)

When you upload a file to a web application running under Kubernetes Ingress,
you might encounter a
413 Payload Too Large
error.
In such cases, you should modify the Ingress settings as follows:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: torico-tools-ingress
namespace: torico
annotations:
# Against http413
nginx.ingress.kubernetes.io/proxy-body-size: "0"
If you want to completely ignore the size limit, set nginx.ingress.kubernetes.io/proxy-body-size: "0"
Reference: https://imti.co/413-request-entity-too-large/ (Note: The hero image on the site might be a bit graphic)
Please rate this article (No signup or login required)
Currently unrated
Related posts
Return Custom Response Headers with Kubernetes Ingress
Fix: no matches for kind "CronJob" in version "batch/v1beta1" on Kubernetes 1.25 — switch to batch/v1
I reinstalled the DNS plugin because name resolution stopped working in Kubernetes (Microk8s)
Items to Check to Prevent Timeout for Slow Responses in Kubernetes Ingress + Uwsgi Configuration
The author runs the application development company Cyberneura.
We look forward to discussing your development needs.
We look forward to discussing your development needs.