Unable to use nginx gateway fabric in front of docker registry service (need to set client_max_body_size) #1245
Description
Describe the bug
We are trying to use the nginx gateway fabric to expose a container registry running the docker registry image. While the basic configuration works fine, pushing images into the registry generally fails with:
$ podman push exampleimage registry.apps.example.com/exampleimage:latest
Error: writing blob: uploading layer chunked: StatusCode: 413, <html>
<head><title>413 Request Entity Too Large<...
The solution is to increase client_max_body_size; but I've been unable to find any documentation that describes how to set custom nginx configuration options via the gateway api.
Expected behavior
I expected to be able to use nginx gateway fabric to expose an internal registry service.
Your environment
- Version of the NGINX Gateway Fabric: v1.0.0
- Version of Kubernetes: v1.27
- Kubernetes platform (e.g. Mini-kube or GCP): kind
- Details on how you expose the NGINX Gateway Fabric Pod: NodePort
- Logs of NGINX container: nginxlog.txt
- NGINX Configuration:
nginxconf.txt