Manage Edge Nodes with KubeEdge and Case Studycommunication • … • Edge special characters • Edge node running in private network • connect to Cloud behind NAT • Edge node’s connect to Cloud through Internet • Low bandwidth/High latency • Unstable connectivity K8S Node2 KubeEdge VPN KubeBus • Scenario • Edge Nodes have no external IP and running behind NAT • One VM in Cloud Cluster has EIP • No direct connection between Edge nodes • Goal • Cloud VM and Edge0 码力 | 11 页 | 1.42 MB | 1 年前3
Handle Edge Cloud Network with KubeBusEdge network characteristics • Edge Nodes running at private network • Connect to Cloud behind NAT gateway • Mightn’t have direct connection between Edges • Edge Nodes connect to Cloud with Internet Summary • Edge network characters (Vs data center network) • Topology: Edge nodes running behind NAT • Performance: Connect to Cloud through Internet • Low throughput • High latency • Edge Scenario:0 码力 | 10 页 | 1.17 MB | 1 年前3
Handle Edge Cloud Network with KubeBusEdge network characteristics • Edge Nodes running at private network • Connect to Cloud behind NAT gateway • Mightn’t have direct connection between Edges • Edge Nodes connect to Cloud with Internet Summary • Edge network characters (Vs data center network) • Topology: Edge nodes running behind NAT • Performance: Connect to Cloud through Internet • Low throughput • High latency • Edge Scenario:0 码力 | 10 页 | 1.17 MB | 1 年前3
共 3 条
- 1













