diff --git a/images/docs/28A1228621D7AD73.png b/images/docs/28A1228621D7AD73.png new file mode 100644 index 0000000000..5838612564 Binary files /dev/null and b/images/docs/28A1228621D7AD73.png differ diff --git a/images/docs/28A1228621D7AD74.png b/images/docs/28A1228621D7AD74.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/28A1228621D7AD74.png differ diff --git a/images/docs/28A1228621D7AD8C.png b/images/docs/28A1228621D7AD8C.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/28A1228621D7AD8C.png differ diff --git a/images/docs/28A1228621D7AD8D.png b/images/docs/28A1228621D7AD8D.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/28A1228621D7AD8D.png differ diff --git a/images/docs/28A1228621D7AD8F.png b/images/docs/28A1228621D7AD8F.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/28A1228621D7AD8F.png differ diff --git a/images/docs/28A1228621D7AD93.png b/images/docs/28A1228621D7AD93.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/28A1228621D7AD93.png differ diff --git a/images/docs/28A1228621D7AD94.png b/images/docs/28A1228621D7AD94.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/28A1228621D7AD94.png differ diff --git a/images/docs/7DA37D793F2F57B2.png b/images/docs/7DA37D793F2F57B2.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/7DA37D793F2F57B2.png differ diff --git a/images/docs/7DA37D793F2F57B4.png b/images/docs/7DA37D793F2F57B4.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/7DA37D793F2F57B4.png differ diff --git a/images/docs/7DA37D793F2F57B5.png b/images/docs/7DA37D793F2F57B5.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/7DA37D793F2F57B5.png differ diff --git a/images/docs/7DA37D793F2F57B6.png b/images/docs/7DA37D793F2F57B6.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/7DA37D793F2F57B6.png differ diff --git a/images/docs/7DA37D793F2F57B7.png b/images/docs/7DA37D793F2F57B7.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/7DA37D793F2F57B7.png differ diff --git a/images/docs/7DA37D793F2F57BB.png b/images/docs/7DA37D793F2F57BB.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/7DA37D793F2F57BB.png differ diff --git a/images/docs/7DA37D793F2F57BC.png b/images/docs/7DA37D793F2F57BC.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/7DA37D793F2F57BC.png differ diff --git a/images/docs/7DA37D793F2F57BD.png b/images/docs/7DA37D793F2F57BD.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/7DA37D793F2F57BD.png differ diff --git a/images/docs/7DA37D793F2F57BF.png b/images/docs/7DA37D793F2F57BF.png new file mode 100644 index 0000000000..22840360fb Binary files /dev/null and b/images/docs/7DA37D793F2F57BF.png differ diff --git a/images/docs/ha.svg b/images/docs/ha.svg new file mode 100644 index 0000000000..d56d5cff59 --- /dev/null +++ b/images/docs/ha.svg @@ -0,0 +1,2675 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/images/docs/horizontal-pod-autoscaler.svg b/images/docs/horizontal-pod-autoscaler.svg new file mode 100644 index 0000000000..daac660316 --- /dev/null +++ b/images/docs/horizontal-pod-autoscaler.svg @@ -0,0 +1,222 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/v1.1/docs/devel/releasing.svg b/images/docs/releasing.svg similarity index 100% rename from v1.1/docs/devel/releasing.svg rename to images/docs/releasing.svg diff --git a/images/docs/services-detail.svg b/images/docs/services-detail.svg new file mode 100644 index 0000000000..bf5005e46c --- /dev/null +++ b/images/docs/services-detail.svg @@ -0,0 +1,133 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Backend Pod 1 + labels: app=MyApp + port: 9376 + + + + + + Backend Pod 2 + labels: app=MyApp + port: 9376 + + + + + + Backend Pod 3 + labels: app=MyApp + port: 9376 + + + + + + + + + + + + + + + + + Client + + + + + iptables + + + + + kube-proxy + + + + + + + apiserver + + + + 3) connect to 10.0.0.1:1234 + 4) redirect to (random) + proxy port + 1) watch Services + and Endpoints + 2) open proxy port + and set portal rules + 5) proxy to a backend + + diff --git a/images/docs/services-overview.svg b/images/docs/services-overview.svg new file mode 100644 index 0000000000..aaa8777911 --- /dev/null +++ b/images/docs/services-overview.svg @@ -0,0 +1,101 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + Backend Pod 1 + labels: app=MyApp + port: 9376 + + + + + + Backend Pod 2 + labels: app=MyApp + port: 9376 + + + + + + Backend Pod 3 + labels: app=MyApp + port: 9376 + + + + + + + + + + + + + + + + + Client + + + + + + kube-proxy + + + + + + + apiserver + + + + + diff --git a/v1.1/docs/admin/high-availability.md b/v1.1/docs/admin/high-availability.md index 5e0fad0c95..7b81018b71 100644 --- a/v1.1/docs/admin/high-availability.md +++ b/v1.1/docs/admin/high-availability.md @@ -27,7 +27,7 @@ The steps involved are as follows: * [Setting up master-elected Kubernetes scheduler and controller-manager daemons](#master-elected-components) Here's what the system should look like when it's finished: -![High availability Kubernetes diagram](/images/docs/ha.png) +![High availability Kubernetes diagram](/images/docs/ha.svg) Ready? Let's get started. diff --git a/v1.1/docs/admin/high-availability/ha.svg b/v1.1/docs/admin/high-availability/ha.svg deleted file mode 100644 index fc38fb557b..0000000000 --- a/v1.1/docs/admin/high-availability/ha.svg +++ /dev/null @@ -1,4 +0,0 @@ - - - - diff --git a/v1.1/docs/devel/releasing.md b/v1.1/docs/devel/releasing.md index 1d0652d1f9..decbe0a265 100644 --- a/v1.1/docs/devel/releasing.md +++ b/v1.1/docs/devel/releasing.md @@ -237,7 +237,7 @@ others around it will either have `v0.4-dev` or `v0.5-dev`. The diagram below illustrates it. -![Diagram of git commits involved in the release](/images/docs/releasing.png) +![Diagram of git commits involved in the release](/images/docs/releasing.svg) After working on `v0.4-dev` and merging PR 99 we decide it is time to release `v0.5`. So we start a new branch, create one commit to update diff --git a/v1.1/docs/user-guide/horizontal-pod-autoscaler.md b/v1.1/docs/user-guide/horizontal-pod-autoscaler.md index 1d85d0ab30..c3a2bc0b66 100644 --- a/v1.1/docs/user-guide/horizontal-pod-autoscaler.md +++ b/v1.1/docs/user-guide/horizontal-pod-autoscaler.md @@ -17,7 +17,7 @@ to match the observed average CPU utilization to the target specified by user. ## How does Horizontal Pod Autoscaler work? -![Horizontal Pod Autoscaler diagram](/images/docs/horizontal-pod-autoscaler.png) +![Horizontal Pod Autoscaler diagram](/images/docs/horizontal-pod-autoscaler.svg) The autoscaler is implemented as a control loop. It periodically queries CPU utilization for the pods it targets. diff --git a/v1.1/docs/user-guide/horizontal-pod-autoscaler.svg b/v1.1/docs/user-guide/horizontal-pod-autoscaler.svg deleted file mode 100644 index 34d3a8aa05..0000000000 --- a/v1.1/docs/user-guide/horizontal-pod-autoscaler.svg +++ /dev/null @@ -1,4 +0,0 @@ - - - - diff --git a/v1.1/docs/user-guide/services-detail.svg b/v1.1/docs/user-guide/services-detail.svg deleted file mode 100644 index cafaf29eb8..0000000000 --- a/v1.1/docs/user-guide/services-detail.svg +++ /dev/null @@ -1,570 +0,0 @@ - - - - - - - - - - image/svg+xml - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Backend Pod 1 - labels: app=MyAppport: 9376 - - - - - - Backend Pod 2 - labels: app=MyAppport: 9376 - - - - - - Backend Pod 3 - labels: app=MyAppport: 9376 - - - - - - - - - - - - - - - Client - - - - - iptables - - - - - kube-proxy - - - - - - - apiserver - - - - 3) connect to 10.0.0.1:1234 - 4) redirect to (random)proxy port - 1) watch Services and Endpoints - 2) open proxy port and set portal rules - 5) proxy to a backend - - diff --git a/v1.1/docs/user-guide/services-overview.svg b/v1.1/docs/user-guide/services-overview.svg deleted file mode 100644 index 8b45677ad0..0000000000 --- a/v1.1/docs/user-guide/services-overview.svg +++ /dev/null @@ -1,417 +0,0 @@ - - - - - - - - - - image/svg+xml - - - - - - - - - - - - - - - - - - - - - - - Backend Pod 1 - labels: app=MyAppport: 9376 - - - - - - Backend Pod 2 - labels: app=MyAppport: 9376 - - - - - - Backend Pod 3 - labels: app=MyAppport: 9376 - - - - - - - - - - - - - - - Client - - - - - - kube-proxy - - - - - - - apiserver - - - - - diff --git a/v1.1/docs/user-guide/services.md b/v1.1/docs/user-guide/services.md index 7906aacd08..13f6ffa601 100644 --- a/v1.1/docs/user-guide/services.md +++ b/v1.1/docs/user-guide/services.md @@ -160,7 +160,7 @@ The net result is that any traffic bound for the `Service` is proxied to an appropriate backend without the clients knowing anything about Kubernetes or `Services` or `Pods`. -![Services overview diagram](/images/docs/services-overview.png) +![Services overview diagram](/images/docs/services-overview.svg) By default, the choice of backend is round robin. Client-IP based session affinity can be selected by setting `service.spec.sessionAffinity` to `"ClientIP"` (the @@ -523,7 +523,7 @@ This means that `Service` owners can choose any port they want without risk of collision. Clients can simply connect to an IP and port, without being aware of which `Pods` they are actually accessing. -![Services detailed diagram](/images/docs/services-detail.png) +![Services detailed diagram](/images/docs/services-detail.svg) ## API Object