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 cluster level lock instead of global lock for cluster accessor initialization #6380

Closed
wants to merge 2 commits into from

Commits on May 26, 2022

  1. cluster-level lock for workload cluster client initialization

    Before this commit, workload cluster client initialization required
    a global lock to be held. If initialization of a single workload cluster
    client took time, all other reconcile-loops who require a workload cluster
    connection were blocked until initialization finished. Initialization
    of a workload cluster client can take a significant amount of time,
    because it requires to initialize the discovery client, which sends
    multiple request to the API-server.
    
    With this change initialization of a workload cluster client only
    requires to hold a lock for the specific cluster. This means
    reconciliation for other clusters is not affected by a long running
    workload cluster client initialization.
    Florian Gutmann committed May 26, 2022
    Configuration menu
    Copy the full SHA
    e1dff72 View commit details
    Browse the repository at this point in the history

Commits on Jul 5, 2022

  1. Update log messages

    Co-authored-by: Vince Prignano <vince@vincepri.com>
    fgutmann and vincepri committed Jul 5, 2022
    Configuration menu
    Copy the full SHA
    dea643a View commit details
    Browse the repository at this point in the history