changed location

Author: Harsh Arora

deploy/README.md

@@ -67,12 +67,12 @@ Apart from "citrix-node-controller" deployment, some other resources are also cr
     - For each worker node, a "kube-cnc-router" pod.
     - A configmap "kube-cnc-router".
 
-<img src="images/kube_cnc_router.png" width="600" height="300">
+<img src="../images/kube_cnc_router.png" width="600" height="300">
 
 On each of the worker nodes, a interface "cncvxlan<hash-of-namespace>" and iptables rule will get created.
 
-<img src="images/slave-1.png" width="600" height="300">
-<img src="images/slave-2.png" width="600" height="300">
+<img src="../images/slave-1.png" width="600" height="300">
+<img src="../images/slave-2.png" width="600" height="300">
 
 
 # Delete the Citrix K8s node controller 

deploy/troubleshoot.md

@@ -25,7 +25,7 @@ We can verify few things to debug the issue of services being in DOWN state.
 
    Look for any ERROR in node configuration. A typical router pod log would look like:
 
-   <img src="images/router-pod-log.png" width="600" height="300">
+   <img src="../images/router-pod-log.png" width="600" height="300">
 
 3. Verify kube-cnc-router configmap output using:
 
@@ -34,7 +34,7 @@ We can verify few things to debug the issue of services being in DOWN state.
    ```
    Look for Empty field in the data section of configmap. A typical 2 node data section would look like:
 
-   <img src="images/router-cmap-data.png" width="600" height="300">
+   <img src="../images/router-cmap-data.png" width="600" height="300">
 
 4. Verify Node config:
    - CNC interface "cncvxlan<md5_of_namespace>" should getcreated
@@ -44,7 +44,7 @@ We can verify few things to debug the issue of services being in DOWN state.
        - port should be same as that of vxlan created on ADC
 
 
-   <img src="images/slave-1.png" width="600" height="300">
+   <img src="../images/slave-1.png" width="600" height="300">
 
 
 ### Service status UP but ping from ADC not working