kubernetes-ingress-controller icon indicating copy to clipboard operation
kubernetes-ingress-controller copied to clipboard

Efficient Kong upstream slots allocation

Open ludovic-pourrat opened this issue 8 months ago • 0 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues

Does this enhancement require public documentation?

  • [X] I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

Problem Statement

When setting up an upstream and using the ingress.kubernetes.io/service-upstream to true the number of allocated slots should be set to 1 instead of 10000. The benefit of this refinement leads to a lower Kong memory consumption when a large set of upstream are configured (over 1k).

Proposed Solution

  • When the ingress.kubernetes.io/service-upstream is to true then set the number of slots in the KongUpstreamPolicy to 1 otherwise leave it to default.

Additional information

No response

Acceptance Criteria

  • [ ] The Kong memory usage is lower when using the ingress.kubernetes.io/service-upstream feature.

ludovic-pourrat avatar Jun 14 '24 07:06 ludovic-pourrat