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.

Sign up for GitHub

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

Jump to bottom

Chore: Improve the high availability level in large-scale cluster deployment. #787

Open
fanfan-yu opened this issue Feb 9, 2025 · 0 comments · May be fixed by #794
Open

Chore: Improve the high availability level in large-scale cluster deployment. #787

fanfan-yu opened this issue Feb 9, 2025 · 0 comments · May be fixed by #794
Assignees
@fanfan-yu
Labels
area/syncer priority/important-soon P1 Must be staffed and worked on either currently,or very soon,ideally in time for the next release
Milestone
v0.7.0

Comments

@fanfan-yu
Copy link
Collaborator

What would you like to be added?

  1. Split Syncer as Agent in user cluster, and support two modes:
    1.1 Agent in user cluster watch hub cluster custom resources like syncrule, and sync info into es directly. In this mode, hub cluster will not invade the user cluster.
    1.2 Syncer in hub cluster will dispatch crds and custom resources into user cluster, and Agent in user cluster watch self apiserver. in this mode, Agent completely self-looping within the user cluster, and sre could deploy Agent independently.

  2. Support more kubernetes versions.

Why is this needed?

  1. Syncer takes up too much memory resource as the number of clusters increases, so a high availability solution is urgently needed.

  2. Better compatibility.
@elliotxx elliotxx added priority/important-soon P1 Must be staffed and worked on either currently,or very soon,ideally in time for the next release area/syncer labels Feb 9, 2025
@elliotxx elliotxx added this to the v0.7.0 milestone Feb 9, 2025
@github-actions github-actions bot mentioned this issue Feb 9, 2025
Open
40 tasks
@fanfan-yu fanfan-yu linked a pull request Feb 12, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fanfan-yu fanfan-yu

Labels
area/syncer priority/important-soon P1 Must be staffed and worked on either currently,or very soon,ideally in time for the next release
Projects
None yet
Milestone
v0.7.0
Development

Successfully merging a pull request may close this issue.

wip: improve the high availability level in large-scale cluster deployment fanfan-yu/karpor
2 participants
@elliotxx @fanfan-yu