sub-mod · December 29, 2019 23:45 · Jun 2, 2017 · Jun 2, 2017 · Jun 2, 2017 · Jun 2, 2017
diff --git a/Reflector.md b/Reflector.md
@@ -20,7 +20,7 @@ It should be noted that the **reflect.Type** is usually a Kind of Kubernetes Obj
 
 
 ### Toy Example Usage of Reflector ###
-Before going deeper into the implementation of Reflector, let's have a look at how Reflector can be used from a example.
+Before going deeper into the implementation of Reflector, let's have a look at how Reflector can be used from a [example](https://github.com/songbinliu/KubeReflectorTest).
 This example will watch the changes(including ADD, DELETE, MODIFY) of all the Pods in the Kubernetes cluster. According to the changes, it will add(or update) Pod object into the *Store* if a Pod is created(or updated), and delete a Pod object from the *Store* if the Pod is killed in the Kubernetes.  In addition, it will also print all the Pod names every 30 seconds: If a Pod is deleted, then its name won't appear; if a Pod is created, its name will appear.
 
 ```go

diff --git a/Reflector.md b/Reflector.md
@@ -10,7 +10,7 @@ Here is the definition of Reflector.
 As shown in the definition, there are two important compoents of a Reflector:
  - **ListerWatcher**
 
-   It provides two functions: *List* and *Watch*. These two functions will call API-server, and get the Events.
+   It provides two functions: *List* and *Watch*. These two functions will talk with Kubernetes API-server, and get the Events.
 
  - **Store**
 

diff --git a/Reflector.md b/Reflector.md
@@ -1,7 +1,7 @@
 ## Kubernetes Reflector ##
 
 Reflector is a key component for Kubernetes clients, kube-scheduler and Replication Controller.
-Reflector is in the middle between client and Kubernetes API-server.
+Reflector is in the middle between client and Kubernetes API-server. It provides a framework to monitor the changes of the Kubernetes cluster.
 
 ### Definition of Reflector ###
 Here is the definition of Reflector.

diff --git a/Reflector.md b/Reflector.md
@@ -3,7 +3,7 @@
 Reflector is a key component for Kubernetes clients, kube-scheduler and Replication Controller.
 Reflector is in the middle between client and Kubernetes API-server.
 
-#### Definition of Reflector ####
+### Definition of Reflector ###
 Here is the definition of Reflector.
 ![reflector define](https://cloud.githubusercontent.com/assets/27221807/26737893/1bc26ccc-479a-11e7-8291-f3551d5c2e6c.png)
 
@@ -19,7 +19,7 @@ As shown in the definition, there are two important compoents of a Reflector:
 It should be noted that the **reflect.Type** is usually a Kind of Kubernetes Object, such as Pod, Node.
 
 
-#### Example Usage of Reflector ####
+### Toy Example Usage of Reflector ###
 Before going deeper into the implementation of Reflector, let's have a look at how Reflector can be used from a example.
 This example will watch the changes(including ADD, DELETE, MODIFY) of all the Pods in the Kubernetes cluster. According to the changes, it will add(or update) Pod object into the *Store* if a Pod is created(or updated), and delete a Pod object from the *Store* if the Pod is killed in the Kubernetes.  In addition, it will also print all the Pod names every 30 seconds: If a Pod is deleted, then its name won't appear; if a Pod is created, its name will appear.
 
@@ -60,7 +60,7 @@ func main() {
 From this example, we can see that Reflector uses Kube-client to list and watch all the Pods, and store the changes in the *Store*.
 ![reflector](https://cloud.githubusercontent.com/assets/27221807/26739964/d1db6246-47a1-11e7-8639-49699e75132e.png)
 
-#### Implementation of Reflector ####
+### Implementation of Reflector ###
 The implementation of Reflector is in [Kubernetes Go Client](https://github.com/kubernetes/client-go/blob/master/tools/cache/reflector.go) tools/cache/ package. **Reflector.RunUntil()** function will periodly call **Reflector.ListAndWatch()** function. 
 
 As the name suggests, **Reflector.ListAndWatch()** will first list all the Objects and store them in the *Store*; then it will *watch* the changes and handle the changes with **Reflector.watchHandler()** function.Following is the skech of the **Reflector.ListAndWatch()** and **Reflector.watchHandler()** functions.
@@ -78,6 +78,6 @@ Second, the Reflector will call *kubeclient.Watch()*. As this *Watch()* call has
 As shown in the definition of *Reflector.watchHandler()*, Reflector keeps a connection to the *APIserver*, and receives changes(*Events*) from this connection. It will update the content of the *Store* according to the *Event.Type*. The content  of the *Store* will be consumed by other components.
 
 
-#### Usage of Reflector ####
+### Usage of Reflector ###
 **Reflector** provides an efficient framework to monitor the changes of the Kubernetes cluster. Many other tools are build base on **Reflector**, by consuming the content of the *Reflector.Store*. For example, *ReplicationController* will watch the number of living Pods, and create or kill Pod as necessary.
 
diff --git a/Reflector.md b/Reflector.md
@@ -34,12 +34,11 @@ func main() {
 	stopCh := make(chan struct{})
 	store := cache.NewStore(cache.MetaNamespaceKeyFunc)
 
-	//selector := fields.SelectorFromSet(nil)
 	selector := fields.Everything()
-	namespace := ""
+	namespaceAll := ""
 	listWatch := cache.NewListWatchFromClient(client.CoreV1Client.RESTClient(),
 		"pods",
-		namespace,
+		namespaceAll,
 		selector)
 
 	r := cache.NewReflector(listWatch, &v1.Pod{}, store, 0)
@@ -76,5 +75,9 @@ Second, the Reflector will call *kubeclient.Watch()*. As this *Watch()* call has
 **Reflector.watchHandler()** 
 ![handlewatch](https://cloud.githubusercontent.com/assets/27221807/26740995/c2eefa00-47a5-11e7-8203-4d8e6efdb21d.png)
 
-As shown in the definition of *Reflector.watchHandler()*, Reflector keeps a connection to the *APIserver*, and receives changes(Events) from this connection. It will update the content of the *Store* according to the *Event.Type*. Other components may consume the content of the *Store*. For example, *ReplicationController* will watch the number of living Pods, and create or kill Pod as necessary.
+As shown in the definition of *Reflector.watchHandler()*, Reflector keeps a connection to the *APIserver*, and receives changes(*Events*) from this connection. It will update the content of the *Store* according to the *Event.Type*. The content  of the *Store* will be consumed by other components.
+
+
+#### Usage of Reflector ####
+**Reflector** provides an efficient framework to monitor the changes of the Kubernetes cluster. Many other tools are build base on **Reflector**, by consuming the content of the *Reflector.Store*. For example, *ReplicationController* will watch the number of living Pods, and create or kill Pod as necessary.
 
diff --git a/Reflector.md b/Reflector.md
@@ -76,4 +76,5 @@ Second, the Reflector will call *kubeclient.Watch()*. As this *Watch()* call has
 **Reflector.watchHandler()** 
 ![handlewatch](https://cloud.githubusercontent.com/assets/27221807/26740995/c2eefa00-47a5-11e7-8203-4d8e6efdb21d.png)
 
+As shown in the definition of *Reflector.watchHandler()*, Reflector keeps a connection to the *APIserver*, and receives changes(Events) from this connection. It will update the content of the *Store* according to the *Event.Type*. Other components may consume the content of the *Store*. For example, *ReplicationController* will watch the number of living Pods, and create or kill Pod as necessary.
 
diff --git a/Reflector.md b/Reflector.md
@@ -21,7 +21,8 @@ It should be noted that the **reflect.Type** is usually a Kind of Kubernetes Obj
 
 #### Example Usage of Reflector ####
 Before going deeper into the implementation of Reflector, let's have a look at how Reflector can be used from a example.
-This example will watch the changes(including ADD, DELETE, MODIFY) of all the Pods in the Kubernetes cluster, and store all the existing Pods into the *Store*, and delete the deleted Pods from the *Store*.  In addition, it will also print all the Pod names every 30 seconds: If a Pod is deleted, then its name won't appear; if a Pod is created, its name will appear.
+This example will watch the changes(including ADD, DELETE, MODIFY) of all the Pods in the Kubernetes cluster. According to the changes, it will add(or update) Pod object into the *Store* if a Pod is created(or updated), and delete a Pod object from the *Store* if the Pod is killed in the Kubernetes.  In addition, it will also print all the Pod names every 30 seconds: If a Pod is deleted, then its name won't appear; if a Pod is created, its name will appear.
+
 ```go
 func main() {
 	client := getKubeClient()

diff --git a/Reflector.md b/Reflector.md
@@ -21,7 +21,7 @@ It should be noted that the **reflect.Type** is usually a Kind of Kubernetes Obj
 
 #### Example Usage of Reflector ####
 Before going deeper into the implementation of Reflector, let's have a look at how Reflector can be used from a example.
-This example will watch the changes(including ADD, DELETE, MODIFY) of all the Pods in the Kubernetes cluster, and store all the existing Pods into the *Store*.  In addition, it will also print all the Pod names every 30 seconds: If a Pod is deleted, then its name won't appear; if a Pod is created, its name will appear.
+This example will watch the changes(including ADD, DELETE, MODIFY) of all the Pods in the Kubernetes cluster, and store all the existing Pods into the *Store*, and delete the deleted Pods from the *Store*.  In addition, it will also print all the Pod names every 30 seconds: If a Pod is deleted, then its name won't appear; if a Pod is created, its name will appear.
 ```go
 func main() {
 	client := getKubeClient()

diff --git a/Reflector.md b/Reflector.md
@@ -1,6 +1,6 @@
 ## Kubernetes Reflector ##
 
-Reflector is a key components for Kubernetes clients, kube-scheduler and Replication Controller.
+Reflector is a key component for Kubernetes clients, kube-scheduler and Replication Controller.
 Reflector is in the middle between client and Kubernetes API-server.
 
 #### Definition of Reflector ####
@@ -21,7 +21,7 @@ It should be noted that the **reflect.Type** is usually a Kind of Kubernetes Obj
 
 #### Example Usage of Reflector ####
 Before going deeper into the implementation of Reflector, let's have a look at how Reflector can be used from a example.
-This example will watch the changes(including ADD, DELETE, MODIFY) of all the Pods in the Kubernetes cluster, and print out the changes.  In addition, it will also print all the Pod names every 30 seconds.
+This example will watch the changes(including ADD, DELETE, MODIFY) of all the Pods in the Kubernetes cluster, and store all the existing Pods into the *Store*.  In addition, it will also print all the Pod names every 30 seconds: If a Pod is deleted, then its name won't appear; if a Pod is created, its name will appear.
 ```go
 func main() {
 	client := getKubeClient()
@@ -69,7 +69,6 @@ As the name suggests, **Reflector.ListAndWatch()** will first list all the Objec
 ![listwatch](https://cloud.githubusercontent.com/assets/27221807/26740901/65b646f4-47a5-11e7-9e2b-24e78d3bb65e.png)
 
 As shown in the definition of *Reflctor.ListAndWatch()*, Reflector first call *kubeclient.List()* to get all the Objects (in the previous example, they are Pods), and add all these Objects into the *Store* by **Reflector.syncWith()**. 
-
 Second, the Reflector will call *kubeclient.Watch()*. As this *Watch()* call has timeout, it will call *kubeclient.Watch()* repeatedly.
 
 

diff --git a/Reflector.md b/Reflector.md
@@ -68,7 +68,10 @@ As the name suggests, **Reflector.ListAndWatch()** will first list all the Objec
 **Reflctor.ListAndWatch()**
 ![listwatch](https://cloud.githubusercontent.com/assets/27221807/26740901/65b646f4-47a5-11e7-9e2b-24e78d3bb65e.png)
 
-As shown in the definition of *Reflctor.ListAndWatch()*, Reflector first call *kubeclient.List()* to get all the Objects (in the previous example, they are Pods), and add all these Objects into the *Store* by **Reflector.syncWith()**. Then Reflector will call *kubeclient.Watch()*. As this *Watch()* call has timeout, it will call *kubeclient.Watch()* repeatedly.
+As shown in the definition of *Reflctor.ListAndWatch()*, Reflector first call *kubeclient.List()* to get all the Objects (in the previous example, they are Pods), and add all these Objects into the *Store* by **Reflector.syncWith()**. 
+
+Second, the Reflector will call *kubeclient.Watch()*. As this *Watch()* call has timeout, it will call *kubeclient.Watch()* repeatedly.
+
 
 **Reflector.watchHandler()** 
 ![handlewatch](https://cloud.githubusercontent.com/assets/27221807/26740995/c2eefa00-47a5-11e7-8203-4d8e6efdb21d.png)

diff --git a/Reflector.md b/Reflector.md
@@ -68,6 +68,8 @@ As the name suggests, **Reflector.ListAndWatch()** will first list all the Objec
 **Reflctor.ListAndWatch()**
 ![listwatch](https://cloud.githubusercontent.com/assets/27221807/26740901/65b646f4-47a5-11e7-9e2b-24e78d3bb65e.png)
 
+As shown in the definition of *Reflctor.ListAndWatch()*, Reflector first call *kubeclient.List()* to get all the Objects (in the previous example, they are Pods), and add all these Objects into the *Store* by **Reflector.syncWith()**. Then Reflector will call *kubeclient.Watch()*. As this *Watch()* call has timeout, it will call *kubeclient.Watch()* repeatedly.
+
 **Reflector.watchHandler()** 
 ![handlewatch](https://cloud.githubusercontent.com/assets/27221807/26740995/c2eefa00-47a5-11e7-8203-4d8e6efdb21d.png)
 

diff --git a/Reflector.md b/Reflector.md
@@ -69,6 +69,6 @@ As the name suggests, **Reflector.ListAndWatch()** will first list all the Objec
 ![listwatch](https://cloud.githubusercontent.com/assets/27221807/26740901/65b646f4-47a5-11e7-9e2b-24e78d3bb65e.png)
 
 **Reflector.watchHandler()** 
-![handlewatch](https://cloud.githubusercontent.com/assets/27221807/26740908/6b837ab6-47a5-11e7-8327-acfb0387e652.png)
+![handlewatch](https://cloud.githubusercontent.com/assets/27221807/26740995/c2eefa00-47a5-11e7-8203-4d8e6efdb21d.png)
 
 
diff --git a/Reflector.md b/Reflector.md
@@ -65,5 +65,10 @@ The implementation of Reflector is in [Kubernetes Go Client](https://github.com/
 
 As the name suggests, **Reflector.ListAndWatch()** will first list all the Objects and store them in the *Store*; then it will *watch* the changes and handle the changes with **Reflector.watchHandler()** function.Following is the skech of the **Reflector.ListAndWatch()** and **Reflector.watchHandler()** functions.
 
+**Reflctor.ListAndWatch()**
+![listwatch](https://cloud.githubusercontent.com/assets/27221807/26740901/65b646f4-47a5-11e7-9e2b-24e78d3bb65e.png)
+
+**Reflector.watchHandler()** 
+![handlewatch](https://cloud.githubusercontent.com/assets/27221807/26740908/6b837ab6-47a5-11e7-8327-acfb0387e652.png)
 
 
diff --git a/Reflector.md b/Reflector.md
@@ -61,8 +61,9 @@ From this example, we can see that Reflector uses Kube-client to list and watch
 ![reflector](https://cloud.githubusercontent.com/assets/27221807/26739964/d1db6246-47a1-11e7-8639-49699e75132e.png)
 
 #### Implementation of Reflector ####
-The implementation of Reflector is in [Kubernetes Go Client](https://github.com/kubernetes/client-go/blob/master/tools/cache/reflector.go) tools/cache/ package. **Reflector.RunUntil()** function will periodly call **Reflector.ListAndWatch()** function. As the name suggests, **Reflector.ListAndWatch()** will first list all the Objects and store them in the *Store*; then it will *watch* the changes and handle the changes with **Reflector.watchHandler()** function.
+The implementation of Reflector is in [Kubernetes Go Client](https://github.com/kubernetes/client-go/blob/master/tools/cache/reflector.go) tools/cache/ package. **Reflector.RunUntil()** function will periodly call **Reflector.ListAndWatch()** function. 
+
+As the name suggests, **Reflector.ListAndWatch()** will first list all the Objects and store them in the *Store*; then it will *watch* the changes and handle the changes with **Reflector.watchHandler()** function.Following is the skech of the **Reflector.ListAndWatch()** and **Reflector.watchHandler()** functions.
 
-Following is the skech of the **Reflector.ListAndWatch()** and **Reflector.watchHandler()** functions.
 
 
diff --git a/Reflector.md b/Reflector.md
@@ -58,8 +58,11 @@ func main() {
 ```
 
 From this example, we can see that Reflector uses Kube-client to list and watch all the Pods, and store the changes in the *Store*.
-![reflector](https://cloud.githubusercontent.com/assets/27221807/26739964/d1db6246-47a1-11e7-8639-49699e75132e.png){:height="50%" width="50%"}
+![reflector](https://cloud.githubusercontent.com/assets/27221807/26739964/d1db6246-47a1-11e7-8639-49699e75132e.png)
 
 #### Implementation of Reflector ####
-The implementation of Reflector is in [Kubernetes Go Client](https://github.com/kubernetes/client-go/blob/master/tools/cache/reflector.go) tools/cache/ package.
+The implementation of Reflector is in [Kubernetes Go Client](https://github.com/kubernetes/client-go/blob/master/tools/cache/reflector.go) tools/cache/ package. **Reflector.RunUntil()** function will periodly call **Reflector.ListAndWatch()** function. As the name suggests, **Reflector.ListAndWatch()** will first list all the Objects and store them in the *Store*; then it will *watch* the changes and handle the changes with **Reflector.watchHandler()** function.
+
+Following is the skech of the **Reflector.ListAndWatch()** and **Reflector.watchHandler()** functions.
+
 
diff --git a/Reflector.md b/Reflector.md
@@ -58,7 +58,7 @@ func main() {
 ```
 
 From this example, we can see that Reflector uses Kube-client to list and watch all the Pods, and store the changes in the *Store*.
-![reflector](https://cloud.githubusercontent.com/assets/27221807/26739964/d1db6246-47a1-11e7-8639-49699e75132e.png | width=200)
+![reflector](https://cloud.githubusercontent.com/assets/27221807/26739964/d1db6246-47a1-11e7-8639-49699e75132e.png){:height="50%" width="50%"}
 
 #### Implementation of Reflector ####
 The implementation of Reflector is in [Kubernetes Go Client](https://github.com/kubernetes/client-go/blob/master/tools/cache/reflector.go) tools/cache/ package.

diff --git a/Reflector.md b/Reflector.md
@@ -58,7 +58,7 @@ func main() {
 ```
 
 From this example, we can see that Reflector uses Kube-client to list and watch all the Pods, and store the changes in the *Store*.
-![reflector](https://cloud.githubusercontent.com/assets/27221807/26739964/d1db6246-47a1-11e7-8639-49699e75132e.png =300x200)
+![reflector](https://cloud.githubusercontent.com/assets/27221807/26739964/d1db6246-47a1-11e7-8639-49699e75132e.png | width=200)
 
 #### Implementation of Reflector ####
 The implementation of Reflector is in [Kubernetes Go Client](https://github.com/kubernetes/client-go/blob/master/tools/cache/reflector.go) tools/cache/ package.

diff --git a/Reflector.md b/Reflector.md
@@ -58,7 +58,7 @@ func main() {
 ```
 
 From this example, we can see that Reflector uses Kube-client to list and watch all the Pods, and store the changes in the *Store*.
-![reflector](https://cloud.githubusercontent.com/assets/27221807/26739964/d1db6246-47a1-11e7-8639-49699e75132e.png)
+![reflector](https://cloud.githubusercontent.com/assets/27221807/26739964/d1db6246-47a1-11e7-8639-49699e75132e.png =300x200)
 
 #### Implementation of Reflector ####
 The implementation of Reflector is in [Kubernetes Go Client](https://github.com/kubernetes/client-go/blob/master/tools/cache/reflector.go) tools/cache/ package.

diff --git a/Reflector.md b/Reflector.md
@@ -60,4 +60,6 @@ func main() {
 From this example, we can see that Reflector uses Kube-client to list and watch all the Pods, and store the changes in the *Store*.
 ![reflector](https://cloud.githubusercontent.com/assets/27221807/26739964/d1db6246-47a1-11e7-8639-49699e75132e.png)
 
+#### Implementation of Reflector ####
+The implementation of Reflector is in [Kubernetes Go Client](https://github.com/kubernetes/client-go/blob/master/tools/cache/reflector.go) tools/cache/ package.
 
diff --git a/Reflector.md b/Reflector.md
@@ -58,6 +58,6 @@ func main() {
 ```
 
 From this example, we can see that Reflector uses Kube-client to list and watch all the Pods, and store the changes in the *Store*.
-![reflector](https://cloud.githubusercontent.com/assets/27221807/26739834/5e8d4f5c-47a1-11e7-830c-4201aa32098f.png)
+![reflector](https://cloud.githubusercontent.com/assets/27221807/26739964/d1db6246-47a1-11e7-8639-49699e75132e.png)
 
 
diff --git a/Reflector.md b/Reflector.md
@@ -58,5 +58,6 @@ func main() {
 ```
 
 From this example, we can see that Reflector uses Kube-client to list and watch all the Pods, and store the changes in the *Store*.
+![reflector](https://cloud.githubusercontent.com/assets/27221807/26739834/5e8d4f5c-47a1-11e7-830c-4201aa32098f.png)
 
 
diff --git a/Reflector.md b/Reflector.md
@@ -16,12 +16,12 @@ As shown in the definition, there are two important compoents of a Reflector:
 
    It is usually a in-memory storage, such as HashMap, or Queue(for FIFO). Reflector will add the Events into this Store.
 
-   
-Also, It should be noted that the **reflect.Type** is usually a Kind of Kubernetes Object, such as Pod, Node.
+It should be noted that the **reflect.Type** is usually a Kind of Kubernetes Object, such as Pod, Node.
+
 
 #### Example Usage of Reflector ####
 Before going deeper into the implementation of Reflector, let's have a look at how Reflector can be used from a example.
-This example will watch the changes(including ADD, DELETE, MODIFY) of all the Pods in the Kubernetes cluster, and print out the changes.  In addition, it will also print all the names every 30 seconds.
+This example will watch the changes(including ADD, DELETE, MODIFY) of all the Pods in the Kubernetes cluster, and print out the changes.  In addition, it will also print all the Pod names every 30 seconds.
 ```go
 func main() {
 	client := getKubeClient()
@@ -57,3 +57,6 @@ func main() {
 
 ```
 
+From this example, we can see that Reflector uses Kube-client to list and watch all the Pods, and store the changes in the *Store*.
+
+
diff --git a/Reflector.md b/Reflector.md
@@ -56,28 +56,4 @@ func main() {
 }
 
 ```
-.gist-highlight {
-    border-left: 3ex solid #eee;
-    position: relative;
-}
-
-.gist-highlight pre {
-    counter-reset: linenumbers;
-}
-
-.gist-highlight pre div:before {
-    color: #aaa;
-    content: counter(linenumbers);
-    counter-increment: linenumbers;
-    left: -3ex;
-    position: absolute;
-    text-align: right;
-    width: 2.5ex;
-    -webkit-touch-callout: none;
-    -webkit-user-select: none;
-    -khtml-user-select: none;
-    -moz-user-select: none;
-    -ms-user-select: none;
-    user-select: none;
-}
 
diff --git a/Reflector.md b/Reflector.md
@@ -56,5 +56,28 @@ func main() {
 }
 
 ```
+.gist-highlight {
+    border-left: 3ex solid #eee;
+    position: relative;
+}
+
+.gist-highlight pre {
+    counter-reset: linenumbers;
+}
 
+.gist-highlight pre div:before {
+    color: #aaa;
+    content: counter(linenumbers);
+    counter-increment: linenumbers;
+    left: -3ex;
+    position: absolute;
+    text-align: right;
+    width: 2.5ex;
+    -webkit-touch-callout: none;
+    -webkit-user-select: none;
+    -khtml-user-select: none;
+    -moz-user-select: none;
+    -ms-user-select: none;
+    user-select: none;
+}
 
diff --git a/Reflector.md b/Reflector.md
@@ -41,7 +41,6 @@ func main() {
 		namespace,
 		selector)
 
-	//cycle := time.Millisecond * 800
 	r := cache.NewReflector(listWatch, &v1.Pod{}, store, 0)
 
 	r.RunUntil(stopCh)