From 0075da0491933f373f813bfd9ae6b1cab9b1d70a Mon Sep 17 00:00:00 2001 From: Himanshu Kiran Date: Mon, 27 May 2024 01:31:01 +0530 Subject: [PATCH 1/6] Why kubeEdge updated Signed-off-by: Himanshu Kiran --- docs/welcome/why-kubeedge.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/welcome/why-kubeedge.md b/docs/welcome/why-kubeedge.md index 600f4ceee1..64ad7bbcbf 100644 --- a/docs/welcome/why-kubeedge.md +++ b/docs/welcome/why-kubeedge.md @@ -3,7 +3,7 @@ title: Why KubeEdge sidebar_position: 1 slug: / --- -**KubeEdge** is an open source system extending native containerized application orchestration and device management to hosts at the Edge. It is built upon Kubernetes and provides core infrastructure support for networking, application deployment and metadata synchronization between cloud and edge. It also supports MQTT and allows developers to author custom logic and enable resource constrained device communication at the Edge. KubeEdge consists of a cloud part and an edge part. Both edge and cloud parts are now open-sourced. +**KubeEdge** is an open-source system that enhances Kubernetes by extending its capabilities to manage and orchestrate containerized applications and devices to host at the Edge.It is built upon Kubernetes and provides core infrastructure support for networking, application deployment and metadata synchronization between cloud and edge. It also supports MQTT, a lightweight messaging protocol, and allows developers to write custom logic and enable resource constrained device communication at the Edge.KubeEdge consists of a cloud part and an edge part. Both edge and cloud parts are now open-sourced. ## Advantages @@ -11,7 +11,7 @@ The advantages of KubeEdge include mainly: * **Edge Computing** - With business logic running at the Edge, much larger volumes of data can be secured & processed locally where the data is produced. This reduces the network bandwidth requirements and consumption between Edge and Cloud. This increases responsiveness, decreases costs, and protects customers' data privacy. + KubeEdge enables applications to run at edge, securing larger volumes of data and processing data closer to the data source which reduces the latency effectively. So, processing near the data sources reduces the network bandwidth requirements and consumption between Edge and Cloud.This also increases responsiveness, decreases costs, and protects customers' data privacy. * **Simplified development** @@ -37,7 +37,7 @@ KubeEdge is composed of these components: - **[MetaManager](./architecture/edge/metamanager):** the message processor between edged and edgehub. It is also responsible for storing/retrieving metadata to/from a lightweight database (SQLite). - **[ServiceBus](./architecture/edge/servicebus)**: a HTTP client to interact with HTTP servers (REST), offering HTTP client capabilities to components of cloud to reach HTTP servers running at edge. - **[DeviceController](./architecture/cloud/device_controller)**: an extended kubernetes controller which manages devices so that the device metadata/status data can be synced between edge and cloud. - +- **MQTT Broker**: A server that handles MQTT messages for efficient communication with IoT devices. ## Architecture ![KubeEdge Architecture](/img/kubeedge_arch.png) From b0c3153ef2f8c353ce1936bd819007d0b1076156 Mon Sep 17 00:00:00 2001 From: Himanshu Kiran Date: Mon, 27 May 2024 20:22:06 +0530 Subject: [PATCH 2/6] Unsuitable part removed Signed-off-by: Himanshu Kiran --- docs/welcome/why-kubeedge.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/welcome/why-kubeedge.md b/docs/welcome/why-kubeedge.md index 64ad7bbcbf..08e9ee8a4e 100644 --- a/docs/welcome/why-kubeedge.md +++ b/docs/welcome/why-kubeedge.md @@ -37,7 +37,7 @@ KubeEdge is composed of these components: - **[MetaManager](./architecture/edge/metamanager):** the message processor between edged and edgehub. It is also responsible for storing/retrieving metadata to/from a lightweight database (SQLite). - **[ServiceBus](./architecture/edge/servicebus)**: a HTTP client to interact with HTTP servers (REST), offering HTTP client capabilities to components of cloud to reach HTTP servers running at edge. - **[DeviceController](./architecture/cloud/device_controller)**: an extended kubernetes controller which manages devices so that the device metadata/status data can be synced between edge and cloud. -- **MQTT Broker**: A server that handles MQTT messages for efficient communication with IoT devices. + ## Architecture ![KubeEdge Architecture](/img/kubeedge_arch.png) From 7b02aab61bafc0591de1af63d40363e984292b8a Mon Sep 17 00:00:00 2001 From: Himanshu Kiran Date: Mon, 27 May 2024 20:39:56 +0530 Subject: [PATCH 3/6] Resolved Signed-off-by: Himanshu Kiran --- docs/welcome/why-kubeedge.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/welcome/why-kubeedge.md b/docs/welcome/why-kubeedge.md index 08e9ee8a4e..be3e0782d2 100644 --- a/docs/welcome/why-kubeedge.md +++ b/docs/welcome/why-kubeedge.md @@ -37,7 +37,6 @@ KubeEdge is composed of these components: - **[MetaManager](./architecture/edge/metamanager):** the message processor between edged and edgehub. It is also responsible for storing/retrieving metadata to/from a lightweight database (SQLite). - **[ServiceBus](./architecture/edge/servicebus)**: a HTTP client to interact with HTTP servers (REST), offering HTTP client capabilities to components of cloud to reach HTTP servers running at edge. - **[DeviceController](./architecture/cloud/device_controller)**: an extended kubernetes controller which manages devices so that the device metadata/status data can be synced between edge and cloud. - ## Architecture ![KubeEdge Architecture](/img/kubeedge_arch.png) From 3645afdef8db86ac76b5ca77d4d07f37410dd597 Mon Sep 17 00:00:00 2001 From: Himanshu Kiran Date: Fri, 31 May 2024 13:18:12 +0530 Subject: [PATCH 4/6] Spacing fixed Signed-off-by: Himanshu Kiran --- docs/welcome/why-kubeedge.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/welcome/why-kubeedge.md b/docs/welcome/why-kubeedge.md index be3e0782d2..9011d901f5 100644 --- a/docs/welcome/why-kubeedge.md +++ b/docs/welcome/why-kubeedge.md @@ -3,7 +3,7 @@ title: Why KubeEdge sidebar_position: 1 slug: / --- -**KubeEdge** is an open-source system that enhances Kubernetes by extending its capabilities to manage and orchestrate containerized applications and devices to host at the Edge.It is built upon Kubernetes and provides core infrastructure support for networking, application deployment and metadata synchronization between cloud and edge. It also supports MQTT, a lightweight messaging protocol, and allows developers to write custom logic and enable resource constrained device communication at the Edge.KubeEdge consists of a cloud part and an edge part. Both edge and cloud parts are now open-sourced. +**KubeEdge** is an open-source system that enhances Kubernetes by extending its capabilities to manage and orchestrate containerized applications and devices to host at the Edge. It is built upon Kubernetes and provides core infrastructure support for networking, application deployment, and metadata synchronization between cloud and edge. It also supports MQTT, a lightweight messaging protocol, and allows developers to write custom logic and enable resource-constrained device communication at the Edge. KubeEdge consists of a cloud part and an edge part. Both edge and cloud parts are now open-sourced. ## Advantages From b42b463f623371335f81871fbef4b52fafcaad82 Mon Sep 17 00:00:00 2001 From: Himanshu Kiran Date: Fri, 31 May 2024 14:25:52 +0530 Subject: [PATCH 5/6] Spacing fixed Signed-off-by: Himanshu Kiran --- docs/welcome/why-kubeedge.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/welcome/why-kubeedge.md b/docs/welcome/why-kubeedge.md index 9011d901f5..2bb9cbef76 100644 --- a/docs/welcome/why-kubeedge.md +++ b/docs/welcome/why-kubeedge.md @@ -3,7 +3,7 @@ title: Why KubeEdge sidebar_position: 1 slug: / --- -**KubeEdge** is an open-source system that enhances Kubernetes by extending its capabilities to manage and orchestrate containerized applications and devices to host at the Edge. It is built upon Kubernetes and provides core infrastructure support for networking, application deployment, and metadata synchronization between cloud and edge. It also supports MQTT, a lightweight messaging protocol, and allows developers to write custom logic and enable resource-constrained device communication at the Edge. KubeEdge consists of a cloud part and an edge part. Both edge and cloud parts are now open-sourced. +**KubeEdge** is an open source system that enhances Kubernetes by extending its capabilities to manage and orchestrate containerized applications and devices to host at the Edge. It is built upon Kubernetes and provides core infrastructure support for networking, application deployment, and metadata synchronization between cloud and edge. It also supports MQTT, a lightweight messaging protocol, and allows developers to write custom logic and enable resource constrained device communication at the Edge. KubeEdge consists of a cloud part and an edge part. Both edge and cloud parts are now open sourced. ## Advantages From 10e10ef48526ad26e8210dbac27c0dbe1be504a3 Mon Sep 17 00:00:00 2001 From: Himanshu Kiran Date: Mon, 3 Jun 2024 14:42:02 +0530 Subject: [PATCH 6/6] more simplified Signed-off-by: Himanshu Kiran --- docs/welcome/why-kubeedge.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/welcome/why-kubeedge.md b/docs/welcome/why-kubeedge.md index 2bb9cbef76..475f16196c 100644 --- a/docs/welcome/why-kubeedge.md +++ b/docs/welcome/why-kubeedge.md @@ -11,7 +11,7 @@ The advantages of KubeEdge include mainly: * **Edge Computing** - KubeEdge enables applications to run at edge, securing larger volumes of data and processing data closer to the data source which reduces the latency effectively. So, processing near the data sources reduces the network bandwidth requirements and consumption between Edge and Cloud.This also increases responsiveness, decreases costs, and protects customers' data privacy. + KubeEdge enables applications to run at the edge, securing larger volumes of data and processing it closer to the data source, which effectively reduces latency. This minimizes network bandwidth requirements and consumption between Edge and Cloud. By keeping sensitive data on local edge devices rather than a central cloud server, the risk of data interception, unauthorized access, and breaches is reduced. This also increases responsiveness, decreases costs, and protects customers' data privacy. * **Simplified development**