Feature cross lan communication #22
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Welcome @ZBoIsHere! It looks like this is your first PR to kubeedge/edgemesh 🎉 |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubeedge-bot
added
the
size/XXL
ZBoIsHere
force-pushed
the
feature-cross-lan-communication
branch
2 times, most recently
from
609581d
to
4002044
Compare
|
/hold |
kubeedge-bot
added
the
do-not-merge/hold
7 tasks
|
/assign @ZBoIsHere |
kubeedge-bot
added
the
needs-rebase
ZBoIsHere
force-pushed
the
feature-cross-lan-communication
branch
from
4002044
to
53ef614
Compare
kubeedge-bot
removed
the
needs-rebase
ZBoIsHere
force-pushed
the
feature-cross-lan-communication
branch
10 times, most recently
from
39c9f8d
to
ac66fa8
Compare
kubeedge-bot
added
the
needs-rebase
ZBoIsHere
force-pushed
the
feature-cross-lan-communication
branch
2 times, most recently
from
82da759
to
d2d4a59
Compare
kubeedge-bot
removed
the
needs-rebase
ZBoIsHere
force-pushed
the
feature-cross-lan-communication
branch
3 times, most recently
from
610bf06
to
0fe62f2
Compare
ZBoIsHere
force-pushed
the
feature-cross-lan-communication
branch
from
0fe62f2
to
4b1d449
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
edgemesh have two parts: edgemesh-server and edgemesh-agent.
edgemesh-server is usually deployed in the cloud and acts as a relay server in the LibP2P mode or assist the agent to establish p2p hole punching. It is specifically responsible for forwarding data across subnets. It is internally divided into the following modules:
tunnelserver: receive establish connection request from agents and forward message or stream between agents.
edgemesh-agent is usually deployed in the edge to act as an agent for communication between pods at different locations. It is internally divided into the following modules:
DNS: Built-in DNS resolver, which resolves the DNS request in the node into a service cluster IP.
proxy: Responsible for configuring the kernel's iptables rules, and intercepting requests to the EdgeMesh process.
gateway: gateway provides a ability to access services in external edge nodes.
tunnelagent: receive proxy request form other agents and send proxy request to other request for crossing subnet communication.