edits

.github/workflows/openyurt-unit-test.yml

@@ -34,8 +34,12 @@ jobs:
       run: 
         pushd scripts/openyurt-deployer && go build -o oy_deploy && popd
 
-    - name: Run Unit Test on OpenYurt helper function 
+    - name: Run Unit Test set up 
       run: | 
         cd scripts/openyurt-deployer
         chmod +x unit_test_workflow.sh
         ./unit_test_workflow.sh
+
+    - name: Run Unit Test on OpenYurt helper function 
+      run: |
+        go test -timeout 5m

scripts/openyurt-deployer/README.md

@@ -1,11 +1,26 @@
 # Quick set-up `OpenYurt`
 
-## 1. Introduction
+## 1.1 Introduction
 
 This program extends [`EasyOpenyurt`](https://github.com/flyinghorse0510/easy_openyurt) to automate the set up process of an `OpenYurt` cluster. 
 
 It support setting up a Kubernetes cluster using kubeadm and then deploy `OpenYurt` and Knative on it. It is compatible with vHive stock-only mode.
 
+## 1.2 About [`OpenYurt`](https://openyurt.io/docs/#:~:text=Furthermore%2C%20OpenYurt%20enhances%20node%20reliability,node%20heartbeats%20to%20the%20cloud.)
+
+### Key Features
+
+#### 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
+
+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
+
+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.
+
 ## 2. Brief overview
 
 **Prerequisite of nodes:**

scripts/openyurt-deployer/main_test.go

@@ -102,10 +102,6 @@ func TestParsingNodeDependencyVersion(t *testing.T) {
 	// Mock NodesInfo
 	mockNodesInfo := NodesInfo{
 		Master: "[email protected]",
-		// Workers: Workers{
-		// 	Cloud: []string{"cloud@host"},
-		// 	Edge:  []string{"edge@host"},
-		// },
 	}
 
 	// Define a table of criteria

scripts/openyurt-deployer/node.go

@@ -662,11 +662,6 @@ func (node *Node) InstallKnativeServing() {
 	_, err = node.ExecShellCmd("kubectl get pods -n knative-serving")
 	utils.CheckErrorWithMsg(err, "Verification Failed!")
 
-	// // Configure DNS
-	// logs.WaitPrintf("Configuring DNS")
-	// _, err = node.ExecShellCmd("kubectl apply -f https://github.com/knative/serving/releases/download/knative-v%s/serving-default-domain.yaml", node.Configs.Knative.KnativeVersion)
-	// logs.CheckErrorWithTagAndMsg(err, "Failed to configure DNS!")
-
 	// enable node selector
 	utils.WaitPrintf("Enable node selector in knative serving")
 	_, err = node.ExecShellCmd(`kubectl patch cm config-features -n knative-serving \

scripts/openyurt-deployer/unit_test_workflow.sh

@@ -24,5 +24,3 @@ sudo service ssh restart
 ssh-add ~/.ssh/id_rsa 
 
 chmod og-rw ~/.ssh
-
-go test -timeout 5m