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

Support multi-instance high availability cloudcore for large-scale cluster #2543

Closed
fisherxu opened this issue Jan 30, 2021 · 5 comments
Closed
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale

Comments

@fisherxu
Copy link
Member

What would you like to be added/modified:
Support multi-instance high availability cloudcore in cloudside, so we can spport large-scale cluster.

Why is this needed:
Cloudcore is the core component of kubeegde in cloud, which is responsible for sending resources of cloud to the edge. Now the cloudcore is running in leader/follower mode, only one instance can run at the same time. For the more larger scale cluster, we need to support multi-instance high availability for cloudcore.

@fisherxu fisherxu added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 30, 2021
@akdanwlf
Copy link

akdanwlf commented Feb 8, 2021

Hello @fisherxu, I came across this issue listed as an LFX Mentorship Project. I am trying to join the kubeedge Slack channel, but it looks like the invitation present in CONTRIBUTING.md is expired. Can I find the link to join elsewhere?

@fisherxu
Copy link
Member Author

fisherxu commented Feb 8, 2021

Hello @fisherxu, I came across this issue listed as an LFX Mentorship Project. I am trying to join the kubeedge Slack channel, but it looks like the invitation present in CONTRIBUTING.md is expired. Can I find the link to join elsewhere?

@akdanwlf Please try this one :) https://join.slack.com/t/kubeedge/shared_invite/enQtNjc0MTg2NTg2MTk0LWJmOTBmOGRkZWNhMTVkNGU1ZjkwNDY4MTY4YTAwNDAyMjRkMjdlMjIzYmMxODY1NGZjYzc4MWM5YmIxZjU1ZDI

@kevin-wangzefeng
Copy link
Member

Previous disscussion #1444

@stale
Copy link

stale bot commented May 9, 2021

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

@stale stale bot added the lifecycle/stale label May 9, 2021
@stale
Copy link

stale bot commented Jul 8, 2021

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗

@stale stale bot closed this as completed Jul 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale
Projects
None yet
Development

No branches or pull requests

3 participants