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

[OSPP] Edge node batch join #5590

Open
Catherine-monk opened this issue May 7, 2024 · 0 comments
Open

[OSPP] Edge node batch join #5590

Catherine-monk opened this issue May 7, 2024 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@Catherine-monk
Copy link

What would you like to be added/modified:

  1. Provide detailed scheme design documents
  2. Implement batch node access
  3. Related Pr submissions, supplementary unit testing, and e2e testing, demonstration demos, and usage documents

Why is this needed:
KubeEdge extends the capabilities of Kubernetes to edge scenarios, providing infrastructure support for networking, application deployment, and metadata synchronization between the cloud and the edge. In an edge scenario, the edge node may be in a private network and cannot be accessed from the cloud. Therefore, it is necessary to access the cloud from the edge node and establish a two-way communication link in reverse. Currently, kubeedge only supports single node access. However, in actual business scenarios, there may be a large number of edge nodes. Single access is very troublesome, so batch access nodes need to be supported. What needs to be done: to be done: Support batch access to nodes, which can be achieved with the help of scripts or other methods.

Refer:
https://github.com/kubeedge/kubeedge

@Catherine-monk Catherine-monk added the kind/feature Categorizes issue or PR as related to a new feature. label May 7, 2024
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.
Projects
None yet
Development

No branches or pull requests

1 participant