Skip to content

Commit

Permalink
linter 2
Browse files Browse the repository at this point in the history
  • Loading branch information
jchua99 committed Feb 2, 2024
1 parent 3c4e384 commit 717d5b1
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions scripts/openyurt-deployer/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,13 +13,13 @@ It support setting up a Kubernetes cluster using kubeadm and then deploy `OpenYu
#### 1. Powerful edge autonomy capability
`OpenYurt` addresses this issue by implementing a per-node proxy (`YurtHub`) along with local storage to cache the state of the cloud apiserver. Consequently, when a node loses its connection, the cached states remain accessible to Kubelet, `KubeProxy`, and any user Pods.

#### 2. Cross NodePool network communication capability
#### 2. Cross `NodePool` network communication capability

In an edge computing Kubernetes cluster, nodes are often distributed across various geographical regions. Consequently, when relying on a native Container Network Interface (CNI) solution, Pods within different `NodePools` may be unable to communicate using Pod IP, Service IP, or Node IP, particularly if each `NodePool` resides within its own isolated LAN. Raven offers a networking solution that enables `cross-NodePool` communication within an `OpenYurt` cluster.

#### 3. Multi-NodePool Management
#### 3. `Multi-NodePool` Management

In order to manage applications and traffic in multiple nodepools conveniently, `YurtAppSet` and `YurtAppDaemon` are introduced for managing workloads in multi-nodepool, and service topology capability for routing traffic in nodepool.
In order to manage applications and traffic in multiple node pools conveniently, `YurtAppSet` and `YurtAppDaemon` are introduced for managing workloads in `multi-nodepool`, and service topology capability for routing traffic in node pool.

## 2. Brief overview

Expand Down

0 comments on commit 717d5b1

Please sign in to comment.