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

XDS client(Local) used to sync the databases #804

Closed
nickolaev opened this issue Jun 3, 2020 · 0 comments · Fixed by #857
Closed

XDS client(Local) used to sync the databases #804

nickolaev opened this issue Jun 3, 2020 · 0 comments · Fixed by #857
Assignees

Comments

@nickolaev
Copy link
Contributor

nickolaev commented Jun 3, 2020

Summary

When Local CP receives a new set of Kuma resources, it should sync it with Local storage.

Process of syncing:

  1. Retrieve all policies from Local CP storage
  2. Remove all that are not in received set
  3. Add all that are in received set but not in Local CP
  4. Compare the existing one by their spec and update if needed.

Do not sync ingress from the same cluster as your local CP

The simpler implementation would be to wipe out all resources from Local CP and replace them with set of received resources. This however has two disadvantages:

  • more I/O operation on Local Storage
  • you need to lock the XDS/SDS reconciliation loop for this process.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants