Efficient Kong upstream slots allocation

[ludovic-pourrat]

Is there an existing issue for this?

• I have searched the existing issues

Does this enhancement require public documentation?

• 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.