<p>I noticed that during the <a href="https://github.com/kubernetes/ingress-nginx" rel="nofollow noreferrer">ingress-nginx</a> pod creation/termination, there is a huge number of events created. Further &quot;investigation&quot; showed that each nginx pod creates</p>
<pre><code>42s         Normal    Sync     ingress/name    Scheduled for sync 
</code></pre>
<p>event for each ingress objects.</p>
<p>For perspective, with some approximate imaginary numbers:</p>
<ul>
<li>The moment you <code>kubectl rollout restart ingress-nginx</code> all ingress-nginx pods will terminate (not simultaneously as there is a proper PDB setup).</li>
<li>During restart, each pod will create <code>sync</code> event object for each ingress object in the cluster.</li>
<li>So if there are 100 ingress-nginx pods with 500 ingress objects, that will span 50k sync events.</li>
</ul>
<blockquote>
<p>I could not find any mentions about it in the docs/ingress-nginx issues</p>
</blockquote>
<p><strong>The question</strong>: is it expected behavior?</p>

<p>This is expected behavior.</p>
<p>As we can see <a href="https://github.com/kubernetes/ingress-nginx/blob/6499393772ee786179b006b423e11950912e8295/internal/ingress/controller/store/store.go#L378" rel="nofollow noreferrer">here</a>, this is an informer, which creates the sync event for each valid ingress. In turn, this informer is added to the store on each ingress-controller pod, see more <a href="https://docs.nginx.com/nginx-ingress-controller/intro/how-nginx-ingress-controller-works/" rel="nofollow noreferrer">here</a>.</p>
