<p>Inside my cluster, there is a service that returns 413 when requested via POST with a large request client body size, > 10MB. Since this service should not be reachable from outside the cluster I am wondering how to increase this setting in order to prevent the above error.</p>

<p>Sure, when using an ingress configuration on the service I can stick to the <code>proxy-body-size</code> annotation, but how is it when not using an ingress configuration?</p>

leidenheit
<p>It seems there is no limitation on request-body-size when a service has not defined an ingress resource.</p>

<p>Edit: Exemplary, we got two services hosted in our cluster A and B. 
Service A will be reachable from outside the cluster which will be achieved by defining an <code>nginx ingress</code> resource which exposes to the url <code>my.service.a</code>.</p>

<pre><code>apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/proxy-body-size: "0"
  ...
spec:
  rules:
    - host: my.service.a
    http:
      paths:
      ...
</code></pre>

<p>Please take note of the annotation <code>nginx.ingress.kubernetes.io/proxy-body-size: "0"</code> which disables the limitation of client request body size (not recommended!).</p>

<p>Service B will only be requested by Service A within its internal cluster address <code>my-service-b.svc.cluster.local</code> and therefore no <code>nginx ingress</code> resource has been defined for Service B.</p>

<p>My assumption was, that Service B has by default a <code>client_request_body_size</code> limitation too. But after testing, it seems that there is no limitation.</p>
