I have looked into the issue and found some clues, regarding setting the client_max_body_size and client_body_buffer_size, either with the nginx configmap: apiVersion: v1 This suggests to me that the issue lies with the ingress-nginx-controller in my cluster. When looking in my ingress-nginx-controller logs in my k8s cluster, I see the following message: 371#371: *1004283 client intended to send too large body: 9930410 bytes, client: 127.0.0.1, server:, request: "PATCH /v2//blobs/uploads/ HTTP/1.1", host: "."Īnd looking at my kube-registry logs, I don't see the PATCH request at all. In this case I get a 413 with the following error in my host nginx logfile (redacted for privacy reasons): - "PATCH /v2//blobs/uploads/?_state=%3D HTTP/1.1" 413 183 "-" "docker/19.03.12 go/go1.13.10 git-commit/48a66213fe kernel/4.19.114 os/linux arch/amd64 UpstreamClient(Docker-Client/19.03.12 \x5C(windows\x5C))"
There however is an issue when I try to push larger images (about 32mb).
Inside the cluster I also have a kube-registry with kube-registry-proxy running to store my docker images. Outside of the cluster requests are exposed to the internet through an nginx that runs on the host machine. The cluster has an nginx ingress controller to expose services to outside of the cluster. vi /etc/nginx/nginx.I have a minikube K8S cluster running on a hyperv vm. The below example sets a global value of 50MB for all sites. For example, you can add it to your main config file to ensure than any site can upload the value you set. You can add the client_max_body_size attribute to your configuration files in multiple places to control what sites or locations the attribute affects. You can increase the allowed maximum with the client_max_body_size attribute. The error is presented because a request being sent to the server contains more data than Nginx allows by default.
0 kommentar(er)
