Nginx Ingress returns 413 Entity Too Large
Quote from moshe on 10/01/2023, 4:11 pmProblem
User gets the following error from NGINX ingress configured on kubernetes cluster
Nginx Ingress returns 413 Entity Too Large
Solution
metadata:
annotations:
nginx.ingress.kubernetes.io/proxy-body-size: “0”
nginx.ingress.kubernetes.io/proxy-read-timeout: “600”
nginx.ingress.kubernetes.io/proxy-send-timeout: “600”
name: harbor-registry
namespace: harbor-registry
spec:
Problem
User gets the following error from NGINX ingress configured on kubernetes cluster
Nginx Ingress returns 413 Entity Too Large
Solution
metadata:
annotations:
nginx.ingress.kubernetes.io/proxy-body-size: “0”
nginx.ingress.kubernetes.io/proxy-read-timeout: “600”
nginx.ingress.kubernetes.io/proxy-send-timeout: “600”
name: harbor-registry
namespace: harbor-registry
spec:
Quote from moshe on 17/01/2023, 3:54 pmnginx.ingress.kubernetes.io/client-max-body-size: “0”
nginx.ingress.kubernetes.io/proxy-body-size: “0”
nginx.ingress.kubernetes.io/proxy-connect-timeout: 600s
nginx.ingress.kubernetes.io/proxy-read-timeout: 600s
nginx.ingress.kubernetes.io/ssl-redirect: “true”
nginx.org/client-max-body-size: “0”
nginx.org/proxy-connect-timeout: 600s
nginx.org/proxy-read-timeout: 600s
nginx.ingress.kubernetes.io/client-max-body-size: “0”
nginx.ingress.kubernetes.io/proxy-body-size: “0”
nginx.ingress.kubernetes.io/proxy-connect-timeout: 600s
nginx.ingress.kubernetes.io/proxy-read-timeout: 600s
nginx.ingress.kubernetes.io/ssl-redirect: “true”
nginx.org/client-max-body-size: “0”
nginx.org/proxy-connect-timeout: 600s
nginx.org/proxy-read-timeout: 600s