fix images path

johandry · Oct 23, 2018 · fdb382e · fdb382e
1 parent 0bf0bf1
commit fdb382e
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/Ch02.md b/Ch02.md
@@ -20,7 +20,7 @@ Other solutions to Kubernetes are:
 
 **Kubernetes Architecture:**
 
-![Kubernetes Architecture](/Users/johandry/Workspace/src/github.com/johandry/CKA/images/02-01-Kubernetes_Architecture.png)
+![Kubernetes Architecture](./images/02-01-Kubernetes_Architecture.png)
 
 Kubernetes is made of a central manager (master) and some worker nodes, although both can run in a single machine or node. The manager runs an API server (`kube-apiserver`), a scheduler (`kube-scheduler`), controllers and a storage system (`etcd`).
 

diff --git a/Ch04.md b/Ch04.md
@@ -4,7 +4,7 @@ A Kubernetes cluster is made of by 2 type of nodes: **Masters** and **Workers**
 
 There are many agents in the master nodes, the primary one and central to the cluster is the **kube-apiserver**. The cluster is all driven by API calls to controllers (internal and external). All other agents send the requests to the API server which authenticate and authorize, and sends them where they need to go. It's also responsible for the persisten state of the DB (**etcd**). Only kube-apiserver talks to etcd.
 
-![Kubernetes Architecture](/Users/johandry/Workspace/src/github.com/johandry/CKA/images/02-01-Kubernetes_Architecture.png)
+![Kubernetes Architecture](./images/02-01-Kubernetes_Architecture.png)
 
 The **kube-scheduler** uses an algorithm to determine which node will host a pod, then try to deploy the pod bsed on availability and success. Here is the code of the [scheduler](https://github.com/kubernetes/kubernetes/blob/master/pkg/scheduler/scheduler.go) on Github for more information.
 
@@ -22,7 +22,7 @@ There isn't a centralized logging for Kubernetes but **Fluentd** can be used/imp
 
 A **Pod** is the smallest unit in a cluster. A Pod is contain one or more containers but Kubernetes does not interact with them, just with the Pod. The Pod follows the architectural design of having one process per container.
 
-![Pod](/Users/johandry/Workspace/src/github.com/johandry/CKA/images/04-01-Pod.png)
+![Pod](./images/04-01-Pod.png)
 
 The picture have 2 containers (A & B) and 2 volumes (1 & 2). There is a 3rd container named **Pause container** used to get the IP address of the Pod.