Annotation in an Ingress resource overwriting default value defined in ConfigMap for all Ingresses (and perhaps vice versa)

[juissi-t]

Our ConfigMap for nginx-ingress-controller looks like this:

apiVersion: v1
data:
  proxy-body-size: "10m"
kind: ConfigMap
metadata:
  name: nginx-load-balancer-conf
  labels:
    app: nginx-ingress-lb

We use an annotation in one of our Ingress resources to use a different value for proxy-body-size:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: api
  annotations:
    ingress.kubernetes.io/proxy-body-size: "5500m"
spec:
  rules:
  - host: api.example.com
    http:
      paths:
      - path: /
        backend:
          serviceName: api
          servicePort: 8000

When using nginx-0.9.0-beta.11, the value looks like this in nginx.conf:

# grep client_max_body_size /etc/nginx/nginx.conf
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";
            client_max_body_size                    "5500m";
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";

We upgraded to nginx-0.9.0-beta.14 and the result was this:

# grep client_max_body_size /etc/nginx/nginx.conf
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";
            client_max_body_size                    "10m";

I then re-applied the Ingress resource, and now it looks like this:

# grep client_max_body_size /etc/nginx/nginx.conf
            client_max_body_size                    "5500m";
            client_max_body_size                    "5500m";
            client_max_body_size                    "5500m";
            client_max_body_size                    "5500m";
            client_max_body_size                    "5500m";
            client_max_body_size                    "5500m";

So, it looks like the default value from the configmap was used regardless of the annotation when upgrading to the new container and nginx.tmpl, and when applying an annotation to a single Ingress, the value is seen in all Ingresses.

[juissi-t]

More info: I tried to reproduce this in another cluster, and can't get the annotation to be seen in any of the ingresses. All of them have 10m as the client_max_body_size and deleting and applying or re-applying the Ingress resource doesn't do anything.

[aledbf]

Please post the nginx.conf file from the container

[juissi-t]

Anonymized nginx.conf

I removed most of the redundant custom error locations.