Ingress/nginx batch updates


I’ve the following question, hopefully someone can shed some light on this.

When you create an ingress, Nginx will update its configuration, reload and starve the process (worker) to drain outstanding connections.

I wonder what happens if you create bunch of ingress rules (e.g. kubectl apply) in a row. The K8s API only allows for creating an ingress rule at a time. So the updates are send one at a time. Is nginx smart enough to buffer some config updates? Or is there a likely chance that it will quickly run out of memory if there are a lot of changes and/or long lasting connections?

Any insights shared are appreciated,