Bumped updateCh limit to fix #2022

[azweb76]

What this PR does / why we need it:
For larger clusters, updateCh with 1024 is not enough and prevents nginx from starting. I bumped updateCh limit to 99999. Ideally this will be auto sized or adjusted to start popping items off during original startup.

Which issue this PR fixes (optional, in fixes #(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #2022

Special notes for your reviewer:
Ideally a longer term solution should exist to support even larger clusters.

[k8s-reviewable]

This change is 

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: azweb76
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: bprashanth

Assign the PR to them by writing /assign @bprashanth in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these OWNERS Files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[aledbf]

@azweb76 can you share the number of services and endpoints in your cluster?

[azweb76]

496 services, 499 endpoints

[azweb76]

486 ingress objects

[azweb76]

This is likely a ticking time bomb for those that are about to exceed the 1024 limit. Once their object count exceeds that limit, the pod will fail to start. This will at least extend the time to provide a long term fix.

[aledbf]

@azweb76 I am fixing this issue right now using a ring buffer to never block writes. I will open the PR and a temporal image in a couple of minites

[azweb76]

sweet! I can help test if you'd like.

[aledbf]

@azweb76 please use quay.io/aledbf/nginx-ingress-controller:0.325 to test the fix

[azweb76]

That appears to have fixed it.