-
Notifications
You must be signed in to change notification settings - Fork 31
Open
Description
Problem Statement
From the design docs:
The one-to-many translation (e.g., a single HTTPRoute creating multiple Kong CRDs) could dramatically increase the total number of resources in the cluster. In large-scale environments, this resource amplification would increase the number of reconciliation loops, placing higher pressure on the Kubernetes API server and etcd. While not a fully verified problem, it is a key scalability consideration to keep in mind during implementation.
We need to investigate if high amounts of KongRoutes and KongServices can affect the cluster's and operator's performance.
Additional notes
Evaluate external tools to use, such as K6 (https://github.com/grafana/k6)
Proposed Solution
Create a testing environment and test the following:
- create a high number (thousands, tens of thousands) of
KongRoutes, all at once - measure the API server, etcd, and operator performance
- measure the average amount of time needed by a
KongRouteto get programmed in Konnect.