Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ Use uncached client and partial metadata for secret and configmaps #4023

Merged

Commits on Jan 4, 2021

  1. Use uncached client and partial metadata for secret and configmaps

    These changes allow the current stable Cluster API release to reduce its
    memory footprint by a large margin.
    
    Currently, we have multiple controllers that are either watching (like
    ClusterResourceSet) or querying (get/list) corev1.Secret and
    corev1.ConfigMap resources.
    
    When these kinds go through the case, all of the objects in the cluster
    end up being cached, not just the ones we're interested in.
    
    In production environments, there might be a large number of ConfigMap
    or Secret resources that we end up caching and watching for little gain.
    
    Signed-off-by: Vince Prignano <vincepri@vmware.com>
    vincepri committed Jan 4, 2021
    Configuration menu
    Copy the full SHA
    1ac7896 View commit details
    Browse the repository at this point in the history