Performance test for GardenerCluster controller

[tobiscr]

Description

Goal of this issue is to measure and improve the performance of KIM related to the GardenerClusterCR controller.

We are currently facing on PROD a processing time of around 30min for a full reconciliation of all GardenerClusterCR s which is too long.During this period, new created or adjusted GardenerClusterCR s are not processed immediately which leads to bad user experience and noticeable increase of our average processing time.

AC:

• Run a performance test for the GardenerCluster controller simulating 1.500, 5.000 and 10.000 SKRs. Reuse the test-setup and approach we were using in [QG] Perform load and stress test to verify operator's behaviour under load #14.
• Goal is to shorten the processing time as much as possible (optimal: <30sec for a reconciliation of all GardenerClusterCRs)

Reasons

Improve user experience and average processing time for reconciling the GardenerClusterCRs.

Attachments