You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present all controllers making use of Secret and/or ConfigMap references cache all these resources. Depending on the cluster, this may result in excessive memory usage while only a portion of the resources is actually being used. Especially when the cluster has for example a high number of Helm releases.
To reduce the memory footprint, we have agreed to disable the caching of these resources with an optional opt-in to enable it for clusters where this overhead is acceptable. The opt-in should rely on the same feature flag across controllers (even if they do not make use of both resource kinds), which is CacheSecretsAndConfigMaps.
At present all controllers making use of Secret and/or ConfigMap references cache all these resources. Depending on the cluster, this may result in excessive memory usage while only a portion of the resources is actually being used. Especially when the cluster has for example a high number of Helm releases.
To reduce the memory footprint, we have agreed to disable the caching of these resources with an optional opt-in to enable it for clusters where this overhead is acceptable. The opt-in should rely on the same feature flag across controllers (even if they do not make use of both resource kinds), which is
CacheSecretsAndConfigMaps
.The text was updated successfully, but these errors were encountered: