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

Reduce adapter memory consumption #1904

Open
Tharsanan1 opened this issue Dec 13, 2023 · 0 comments
Open

Reduce adapter memory consumption #1904

Tharsanan1 opened this issue Dec 13, 2023 · 0 comments

Comments

@Tharsanan1
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant