SUSE Support

Here When You Need Us

How to set the maximum client body size for nginx ingress controller

This document (000021309) is provided subject to the disclaimer at the end of this document.


Rancher 2.6.x , 2.7.x, 2.8.x


NGINX Ingress in Kubernetes may encounter a 413 error (Request Entity Too Large) when attempting to upload or send large files. This error occurs because NGINX Ingress imposes a default limit on the request body size.
Date [warn] 146749#146749: *2157831389 a client request body is buffered to a temporary file /tmp/nginx/client-body/0046932384,



Adjust the proxy-body-size setting using the annotation in their Ingress resource. This setting determines the maximum allowed size for the request body.

Applying the Annotation:

At the Ingress Level: Add the following annotation to your Ingress resource: "4096m"



The NGINX Ingress controller imposes a limit on the size of the client request body it can handle. When a client attempts to send a request with a body larger than this limit, NGINX responds with a 413 Request Entity Too Large error.


Top Issue

Additional Information


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:000021309
  • Creation Date: 27-Mar-2024
  • Modified Date:27-Mar-2024
    • SUSE Rancher

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.