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
The current version of the adapter uses an in-memory ODS, which stores the API, rate limit, API policy, etc., to determine whether a reconcile event should be processed. Ideally, we should use status.observedGeneration and metadata.generation to decide if a reconcile event should proceed. Removing the ODS could help save CPU resources as well.
We might need to maintain a local cache to store the processed CR by caching the name and namespace. This cache would handle adapter restarts where status.observedGeneration equals metadata.generation. In the event of adapter restart, it should reconcile all the APIs regardless of the status.observedGeneration and metadata.generation.
The text was updated successfully, but these errors were encountered:
The current version of the adapter uses an in-memory ODS, which stores the API, rate limit, API policy, etc., to determine whether a reconcile event should be processed. Ideally, we should use status.observedGeneration and metadata.generation to decide if a reconcile event should proceed. Removing the ODS could help save CPU resources as well.
We might need to maintain a local cache to store the processed CR by caching the name and namespace. This cache would handle adapter restarts where status.observedGeneration equals metadata.generation. In the event of adapter restart, it should reconcile all the APIs regardless of the status.observedGeneration and metadata.generation.
The text was updated successfully, but these errors were encountered: