This is a finding from the dev sandbox performance tests we did for onboarding the Camel K operator.

The Kube ApiServer memory usage jumps from 50Gi to about 90Gi in average (peak up to 104Gi) when the users start to use Camel K integrations on the cluster (600 Camel K users each of them starting an integration out of 2000 total users on the cluster).

We should find out what causes the increased memory usage on the Kube ApiServer.