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
I think we should consider using the ClusterCacheTracker from core CAPI which caches Clients and RESTConfig for a cluster across reconciles. The main advantage is that we don't have to construct a client on each reconcile.
Currently we have a few places where we are using remote.NewClusterClient instead:
The text was updated successfully, but these errors were encountered:
sbueringer
changed the title
Consider using ClusterCacheTracker instead of remote.NewClusterClient, ...
Consider using ClusterCacheTracker instead of remote.NewClusterClient
Jul 20, 2023
I think we should consider using the ClusterCacheTracker from core CAPI which caches Clients and RESTConfig for a cluster across reconciles. The main advantage is that we don't have to construct a client on each reconcile.
Currently we have a few places where we are using remote.NewClusterClient instead:
An example on how to setup the ClusterCacheTracker can be seen here: https://github.com/kubernetes-sigs/cluster-api/blob/main/main.go#L372-L395
The text was updated successfully, but these errors were encountered: