Change version selector to retain current page when switching versions (#19470 )

Fixes Hugo error (#18045 )
6:16:23 PM: [FAILURE] The Hugo version set in the Makefile is 0.53 while the version in netlify.toml is 0.57.2 6:16:23 PM: [FAILURE] Please update these versions so that they are same (consider the higher of the two versions as
2020-03-04 16:46:38 -08:00 · 2019-12-09 18:47:28 -08:00 · 2019-12-09 16:15:30 -08:00 · 2019-10-02 07:07:09 -07:00 · 2019-10-01 15:53:08 -07:00 · 2019-09-18 18:19:11 -05:00
763 changed files with 79196 additions and 4504 deletions
@@ -1,5 +1,5 @@
 DOCKER       = docker
-HUGO_VERSION = 0.53
+HUGO_VERSION = 0.57.2
 DOCKER_IMAGE = kubernetes-hugo
 DOCKER_RUN   = $(DOCKER) run --rm --interactive --tty --volume $(CURDIR):/src
 NODE_BIN     = node_modules/.bin
@@ -24,7 +24,9 @@ pygmentsStyle = "emacs"
 enableGitInfo = true

 # Norwegian ("no") is sometimes but not currently used for testing.
-disableLanguages = ["no"]
+# Hindi is disabled because it's currently in development.
+# Italian is disabled until it meets minimum standards for quality.
+disableLanguages = ["it", "no"]

 [blackfriday]
 hrefTargetBlank = true
@@ -64,23 +66,23 @@ time_format_blog = "Monday, January 02, 2006"
 description = "Production-Grade Container Orchestration"
 showedit = true

-latest = "v1.13"
+latest = "v1.17"

-fullversion = "v1.13.0"
+fullversion = "v1.13.12"
 version = "v1.13"
-githubbranch = "master"
-docsbranch = "master"
-deprecated = false
+githubbranch = "v1.13.12"
+docsbranch = "release-1.13"
+deprecated = true
 currentUrl = "https://kubernetes.io/docs/home/"
 nextUrl = "https://kubernetes-io-vnext-staging.netlify.com/"
 githubWebsiteRepo = "github.com/kubernetes/website"
 githubWebsiteRaw = "raw.githubusercontent.com/kubernetes/website"

 [[params.versions]]
-fullversion = "v1.13.0"
-version = "v1.13"
-githubbranch = "v1.13.0"
-docsbranch = "release-1.13"
+fullversion = "v1.17.0"
+version = "v1.17"
+githubbranch = "v1.17.0"
+docsbranch = "release-1.17"
 url = "https://kubernetes.io"

 [params.pushAssets]
@@ -95,32 +97,32 @@ js = [
 ]

 [[params.versions]]
-fullversion = "v1.12.3"
-version = "v1.12"
-githubbranch = "v1.12.3"
-docsbranch = "release-1.12"
-url = "https://v1-12.docs.kubernetes.io"
+fullversion = "v1.16.3"
+version = "v1.16"
+githubbranch = "v1.16.3"
+docsbranch = "release-1.16"
+url = "https://v1-16.docs.kubernetes.io"

 [[params.versions]]
-fullversion = "v1.11.5"
-version = "v1.11"
-githubbranch = "v1.11.5"
-docsbranch = "release-1.11"
-url = "https://v1-11.docs.kubernetes.io"
+fullversion = "v1.15.6"
+version = "v1.15"
+githubbranch = "v1.15.6"
+docsbranch = "release-1.15"
+url = "https://v1-15.docs.kubernetes.io"

 [[params.versions]]
-fullversion = "v1.10.11"
-version = "v1.10"
-githubbranch = "v1.10.11"
-docsbranch = "release-1.10"
-url = "https://v1-10.docs.kubernetes.io"
+fullversion = "v1.14.9"
+version = "v1.14"
+githubbranch = "v1.14.9"
+docsbranch = "release-1.14"
+url = "https://v1-14.docs.kubernetes.io"

 [[params.versions]]
-fullversion = "v1.9.11"
-version = "v1.9"
-githubbranch = "v1.9.11"
-docsbranch = "release-1.9"
-url = "https://v1-9.docs.kubernetes.io"
+fullversion = "v1.13.12"
+version = "v1.13"
+githubbranch = "v1.13.12"
+docsbranch = "release-1.13"
+url = "https://v1-13.docs.kubernetes.io"

 # Language definitions.

@@ -12,9 +12,9 @@ With the help of our growing community of 1,400 plus contributors, we issued mor

 While many improvements have been contributed, we highlight key features in this series of in-depth&nbsp;posts listed below. [Follow along](https://twitter.com/kubernetesio) and see what’s new and improved with storage, security and more.  

-**Day 1:** [5 Days of Kubernetes 1.8](https://kubernetes.io/blog/2017/10/five-days-of-kubernetes-18)  
+**Day 1:** [5 Days of Kubernetes v1.8](https://kubernetes.io/blog/2017/10/five-days-of-kubernetes-18)  
 **Day 2:** [kubeadm v1.8 Introduces Easy Upgrades for Kubernetes Clusters](https://kubernetes.io/blog/2017/10/kubeadm-v18-released)  
-**Day 3:** [Kubernetes v.1.8 Retrospective: It Takes a Village to Raise a Kubernetes](https://kubernetes.io/blog/2017/10/it-takes-village-to-raise-kubernetes)
+**Day 3:** [Kubernetes v1.8 Retrospective: It Takes a Village to Raise a Kubernetes](https://kubernetes.io/blog/2017/10/it-takes-village-to-raise-kubernetes)
 **Day 4:** [Using RBAC, Generally Available in Kubernetes v1.8](https://kubernetes.io/blog/2017/10/using-rbac-generally-available-18)  
 **Day 5:** [Enforcing Network Policies in Kubernetes](https://kubernetes.io/blog/2017/10/enforcing-network-policies-in-kubernetes)  

@@ -252,9 +252,9 @@ The following cloud providers have implemented CCMs:

 * [Digital Ocean](https://github.com/digitalocean/digitalocean-cloud-controller-manager)
 * [Oracle](https://github.com/oracle/oci-cloud-controller-manager)
-* [Azure](https://github.com/kubernetes/kubernetes/tree/master/pkg/cloudprovider/providers/azure)
-* [GCE](https://github.com/kubernetes/kubernetes/tree/master/pkg/cloudprovider/providers/gce)
-* [AWS](https://github.com/kubernetes/kubernetes/tree/master/pkg/cloudprovider/providers/aws)
+* [Azure](https://github.com/kubernetes/cloud-provider-azure)
+* [GCP](https://github.com/kubernetes/cloud-provider-gcp)
+* [AWS](https://github.com/kubernetes/cloud-provider-aws)
 * [BaiduCloud](https://github.com/baidu/cloud-provider-baiducloud)
 * [Linode](https://github.com/linode/linode-cloud-controller-manager)

@@ -471,7 +471,7 @@ Kubelet is checking whether the mounted secret is fresh on every periodic sync.
 However, it is using its local cache for getting the current value of the Secret.
 The type of the cache is configurable using the  (`ConfigMapAndSecretChangeDetectionStrategy` field in
 [KubeletConfiguration struct](https://github.com/kubernetes/kubernetes/blob/{{< param "docsbranch" >}}/staging/src/k8s.io/kubelet/config/v1beta1/types.go)).
-It can be either propagated via watch (default), ttl-based, or simply redirecting
+It can be either propagated via watch, ttl-based (default), or simply redirecting
 all requests to directly kube-apiserver.
 As a result, the total delay from the moment when the Secret is updated to the moment
 when new keys are projected to the Pod can be as long as kubelet sync period + cache
@@ -178,7 +178,18 @@ k8s-apparmor-example-deny-write (enforce)
 First, we need to load the profile we want to use onto our nodes. The profile we'll use simply
 denies all file writes:

-{{< code language="text" file="deny-write.profile" >}}
+```shell
+#include <tunables/global>
+
+profile k8s-apparmor-example-deny-write flags=(attach_disconnected) {
+  #include <abstractions/base>
+
+  file,
+
+  # Deny all file writes.
+  deny /** w,
+}
+```

 Since we don't know where the Pod will be scheduled, we'll need to load the profile on all our
 nodes. For this example we'll just use SSH to install the profiles, but other approaches are
@@ -1,10 +0,0 @@
-#include <tunables/global>
-
-profile k8s-apparmor-example-deny-write flags=(attach_disconnected) {
-  #include <abstractions/base>
-
-  file,
-
-  # Deny all file writes.
-  deny /** w,
-}
@@ -8,7 +8,7 @@ cid: home

 {{< blocks/section id="oceanNodes" >}}
 {{% blocks/feature image="flower" %}}
-### [쿠버네티스 (k8s)]({{< relref "/docs/concepts/overview/what-is-kubernetes" >}})는 컨테이너화된 애플리케이션을 자동으로 배포, 스케일링 및 관리해주는 오픈소스 시스템입니다.
+### [쿠버네티스 (K8s)]({{< relref "/docs/concepts/overview/what-is-kubernetes" >}})는 컨테이너화된 애플리케이션을 자동으로 배포, 스케일링 및 관리해주는 오픈소스 시스템입니다.

 애플리케이션을 구성하는 컨테이너들의 쉬운 관리 및 발견을 위해서 컨테이너들을 논리적인 단위로 그룹화합니다. 쿠버네티스는 [Google에서 15년간 프로덕션 워크로드 운영한 경험](http://queue.acm.org/detail.cfm?id=2898444)을 토대로 구축되었으며, 커뮤니티에서 제공한 최상의 아이디어와 방법들이 결합되어 있습니다.
 {{% /blocks/feature %}}
@@ -26,28 +26,27 @@ quote: >
 <section class="section1">
 <div class="cols">
  <div class="col1">
+<br><br>
    <h2>Challenge</h2>
    After eight years in existence, Pinterest had grown into 1,000 microservices and multiple layers of infrastructure and diverse set-up tools and platforms. In 2016 the company launched a roadmap towards a new compute platform, led by the vision of creating the fastest path from an idea to production, without making engineers worry about the underlying infrastructure.

-<br>
+<br><br>

 <h2>Solution</h2>
    The first phase involved moving services to Docker containers. Once these services went into production in early 2017, the team began looking at orchestration to help create efficiencies and manage them in a decentralized way. After an evaluation of various solutions, Pinterest went with Kubernetes.

-</div>
-
-<div class="col2">
+<br><br>

 <h2>Impact</h2>
  "By moving to Kubernetes the team was able to build on-demand scaling and new failover policies, in addition to simplifying the overall deployment and management of a complicated piece of infrastructure such as Jenkins," says Micheal Benedict, Product Manager for the Cloud and the Data Infrastructure Group at Pinterest. "We not only saw reduced build times but also huge efficiency wins. For instance, the team reclaimed over 80 percent of capacity during non-peak hours. As a result, the Jenkins Kubernetes cluster now uses 30 percent less instance-hours per-day when compared to the previous static cluster."

-
+</div>
 </div>

-</div>
 </section>
-<div class="banner2">
-  <div class="banner2text">
+<div class="banner2" style="text-align:center">
+    <iframe width="500" height="260" src="https://www.youtube.com/embed/I36NNJH1xQY" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+    <div class="banner2text"><br><br>
 "So far it’s been good, especially the elasticity around how we can configure our Jenkins workloads on that Kubernetes shared cluster. That is the win we&nbsp;were&nbsp;pushing&nbsp;for." <span style="font-size:14px;letter-spacing:0.12em;padding-top:20px;text-transform:uppercase;line-height:14px"><br><br>— Micheal Benedict, Product Manager for the Cloud and the Data Infrastructure Group at Pinterest</span>

  </div>
@@ -255,6 +255,7 @@ rules:
 * [GCE](https://github.com/kubernetes/kubernetes/tree/master/pkg/cloudprovider/providers/gce)
 * [AWS](https://github.com/kubernetes/kubernetes/tree/master/pkg/cloudprovider/providers/aws)
 * [BaiduCloud](https://github.com/baidu/cloud-provider-baiducloud)
+* [Linode](https://github.com/linode/linode-cloud-controller-manager)

 ## 클러스터 관리

@@ -6,7 +6,9 @@ weight: 80

 {{% capture overview %}}

-{{< include "federation-current-state.md" >}}
+{{< deprecationfilewarning >}}
+{{< include "federation-deprecation-warning-note.md" >}}
+{{< /deprecationfilewarning >}}

 이 페이지는 여러 쿠버네티스 클러스터를 페더레이션을 통해서 관리해야 하는 이유와 방법을 
 설명한다.
@@ -69,7 +71,6 @@ weight: 80
 쿠버네티스 클러스터의 페더레이션은 다른 클라우드 제공자(예를 들어, Google 클라우드, AWS), 
 그리고 온-프레미스(예를 들어, OpenStack)에서 동작 중인 클러스터를 포함할 수 
 있다. [Kubefed](/docs/tasks/federation/set-up-cluster-federation-kubefed/)는 연합된 클러스터 배치에 권장되는 방법이다. 
-
 그 후에, [API 리소스](#api-리소스)는 서로 다른 클러스터와 클라우드 
 제공자에 걸쳐 확장될 수 있다. 

@@ -181,4 +182,4 @@ zone)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availabi
 * [Kubecon2018 유럽 sig-multicluster 업데이트 내용](https://www.youtube.com/watch?v=vGZo5DaThQU) 보기
 * [Kubecon2018 유럽 Federation-v2 프로토타입 발표](https://youtu.be/q27rbaX5Jis?t=7m20s) 보기
 * [Federation-v2 사용자 가이드](https://github.com/kubernetes-sigs/federation-v2/blob/master/docs/userguide.md) 보기
-{{% /capture %}}
+{{% /capture %}}
@@ -77,7 +77,7 @@ cloud-controller-manager는 클라우드 밴더 코드와 쿠버네티스 코드
 ### 컨테이너 런타임

 컨테이너 런타임은 컨테이너의 동작을 책임지는 소프트웨어다. 
-쿠버네티스는 몇몇의 런타임을 지원하는데 [Docker](http://www.docker.com), [containerd](https://containerd.io), [cri-o](https://cri-o.io/), [rktlet](https://github.com/kubernetes-incubator/rktlet) 그리고 [Kubernetes CRI (Container Runtime Interface)](https://github.com/kubernetes/community/blob/master/contributors/devel/container-runtime-interface.md)를 구현한 모든 런타임이다.
+쿠버네티스는 몇몇의 런타임을 지원하는데 [Docker](http://www.docker.com), [containerd](https://containerd.io), [cri-o](https://cri-o.io/), [rktlet](https://github.com/kubernetes-incubator/rktlet) 그리고 [Kubernetes CRI (Container Runtime Interface)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md)를 구현한 모든 런타임이다.

 ## 애드온

@@ -45,7 +45,7 @@ card:


 ```shell
-$ kubectl create -f https://k8s.io/examples/application/deployment.yaml --record
+kubectl create -f https://k8s.io/examples/application/deployment.yaml --record
 ```

 그 출력 내용은 다음과 유사하다.
@@ -41,7 +41,9 @@ weight: 30
 사용중인 클러스터의 현재 네임스페이스를 나열할 수 있다.

 ```shell
-$ kubectl get namespaces
+kubectl get namespaces
+```
+```
 NAME          STATUS    AGE
 default       Active    1d
 kube-system   Active    1d
@@ -106,19 +106,19 @@ metadata:
    pod.beta.kubernetes.io/init-containers: '[
        {
            "name": "init-myservice",
-            "image": "busybox",
+            "image": "busybox:1.28",
            "command": ["sh", "-c", "until nslookup myservice; do echo waiting for myservice; sleep 2; done;"]
        },
        {
            "name": "init-mydb",
-            "image": "busybox",
+            "image": "busybox:1.28",
            "command": ["sh", "-c", "until nslookup mydb; do echo waiting for mydb; sleep 2; done;"]
        }
    ]'
 spec:
  containers:
  - name: myapp-container
-    image: busybox
+    image: busybox:1.28
    command: ['sh', '-c', 'echo The app is running! && sleep 3600']
 ```

@@ -135,14 +135,14 @@ metadata:
 spec:
  containers:
  - name: myapp-container
-    image: busybox
+    image: busybox:1.28
    command: ['sh', '-c', 'echo The app is running! && sleep 3600']
  initContainers:
  - name: init-myservice
-    image: busybox
+    image: busybox:1.28
    command: ['sh', '-c', 'until nslookup myservice; do echo waiting for myservice; sleep 2; done;']
  - name: init-mydb
-    image: busybox
+    image: busybox:1.28
    command: ['sh', '-c', 'until nslookup mydb; do echo waiting for mydb; sleep 2; done;']
 ```

@@ -176,12 +176,24 @@ spec:
 다음 커맨드들을 이용하여 파드를 시작하거나 디버깅할 수 있다.

 ```shell
-$ kubectl create -f myapp.yaml
+kubectl create -f myapp.yaml
+```
+```
 pod/myapp-pod created
-$ kubectl get -f myapp.yaml
+```
+
+```shell
+kubectl get -f myapp.yaml
+```
+```
 NAME        READY     STATUS     RESTARTS   AGE
 myapp-pod   0/1       Init:0/2   0          6m
-$ kubectl describe -f myapp.yaml
+```
+
+```shell
+kubectl describe -f myapp.yaml
+```
+```
 Name:          myapp-pod
 Namespace:     default
 [...]
@@ -214,18 +226,25 @@ Events:
  13s          13s         1        {kubelet 172.17.4.201}    spec.initContainers{init-myservice}     Normal        Pulled        Successfully pulled image "busybox"
  13s          13s         1        {kubelet 172.17.4.201}    spec.initContainers{init-myservice}     Normal        Created       Created container with docker id 5ced34a04634; Security:[seccomp=unconfined]
  13s          13s         1        {kubelet 172.17.4.201}    spec.initContainers{init-myservice}     Normal        Started       Started container with docker id 5ced34a04634
-$ kubectl logs myapp-pod -c init-myservice # Inspect the first init container
-$ kubectl logs myapp-pod -c init-mydb      # Inspect the second init container
+```
+```shell
+kubectl logs myapp-pod -c init-myservice # Inspect the first init container
+kubectl logs myapp-pod -c init-mydb      # Inspect the second init container
 ```

 `mydb` 및 `myservice` 서비스를 시작하고 나면, 초기화 컨테이너가 완료되고 
 `myapp-pod`가 생성된 것을 볼 수 있다.

 ```shell
-$ kubectl create -f services.yaml
+kubectl create -f services.yaml
+```
+```
 service/myservice created
 service/mydb created
-$ kubectl get -f myapp.yaml
+```
+
+```shell
+kubectl get -f myapp.yaml
 NAME        READY     STATUS    RESTARTS   AGE
 myapp-pod   1/1       Running   0          9m
 ```
@@ -61,7 +61,7 @@ etcd 역시 클라이언트와 피어 간에 상호 TLS 인증을 구현한다.

 | 기본 CN                       | 부모 CA                   | O (주체에서)   | 종류                                   | 호스트  (SAN)                                |
 |-------------------------------|---------------------------|----------------|----------------------------------------|---------------------------------------------|
-| kube-etcd                     | etcd-ca                   |                | server, client [<sup>1</sup>][etcdbug] | `localhost`, `127.0.0.1`                    |
+| kube-etcd                     | etcd-ca                   |                | server, client                         | `localhost`, `127.0.0.1`                        |
 | kube-etcd-peer                | etcd-ca                   |                | server, client                         | `<hostname>`, `<Host_IP>`, `localhost`, `127.0.0.1` |
 | kube-etcd-healthcheck-client  | etcd-ca                   |                | client                                 |                                             |
 | kube-apiserver-etcd-client    | etcd-ca                   | system:masters | client                                 |                                             |
@@ -42,30 +42,50 @@ VM 드라이버를 바꾸기 원하면 적절한 `--vm-driver=xxx` 플래그를
 * none (쿠버네티스 구성요소는 VM이 아닌 호스트상에서 동작한다. 이 드라이버를 사용하기 위해서는 Docker ([docker 설치](https://docs.docker.com/install/linux/docker-ce/ubuntu/))와 리눅스 환경)이 필요하다.

 ```shell
-$ minikube start
+minikube start
+```
+```
 Starting local Kubernetes cluster...
 Running pre-create checks...
 Creating machine...
 Starting local Kubernetes cluster...
-
-$ kubectl run hello-minikube --image=k8s.gcr.io/echoserver:1.10 --port=8080
+```
+```shell
+kubectl run hello-minikube --image=k8s.gcr.io/echoserver:1.10 --port=8080
+```
+```
 deployment.apps/hello-minikube created
-$ kubectl expose deployment hello-minikube --type=NodePort
-service/hello-minikube exposed
+```

+```shell
+kubectl expose deployment hello-minikube --type=NodePort
+```
+```
+service/hello-minikube exposed
+```
+```
 # We have now launched an echoserver pod but we have to wait until the pod is up before curling/accessing it
 # via the exposed service.
 # To check whether the pod is up and running we can use the following:
-$ kubectl get pod
+kubectl get pod
+```
+```
 NAME                              READY     STATUS              RESTARTS   AGE
 hello-minikube-3383150820-vctvh   0/1       ContainerCreating   0          3s
+```
+```
 # We can see that the pod is still being created from the ContainerCreating status
-$ kubectl get pod
+kubectl get pod
+```
+```
 NAME                              READY     STATUS    RESTARTS   AGE
 hello-minikube-3383150820-vctvh   1/1       Running   0          13s
+```
+```
 # We can see that the pod is now Running and we will now be able to curl it:
-$ curl $(minikube service hello-minikube --url)
-
+curl $(minikube service hello-minikube --url)
+```
+```

 Hostname: hello-minikube-7c77b68cff-8wdzq

@@ -91,13 +111,26 @@ Request Headers:

 Request Body:
 	-no body in request-
+```

-
-$ kubectl delete services hello-minikube
+```shell
+kubectl delete services hello-minikube
+```
+```
 service "hello-minikube" deleted
-$ kubectl delete deployment hello-minikube
+```
+
+```shell
+kubectl delete deployment hello-minikube
+```
+```
 deployment.extensions "hello-minikube" deleted
-$ minikube stop
+```
+
+```shell
+minikube stop
+```
+```
 Stopping local Kubernetes cluster...
 Stopping "minikube"...
 ```
@@ -109,7 +142,7 @@ Stopping "minikube"...
 [containerd](https://github.com/containerd/containerd)를 컨테이너 런타임으로 사용하려면, 다음을 실행한다.

 ```bash
-$ minikube start \
+minikube start \
    --network-plugin=cni \
    --enable-default-cni \
    --container-runtime=containerd \
@@ -119,7 +152,7 @@ $ minikube start \
 혹은 확장 버전을 사용할 수 있다.

 ```bash
-$ minikube start \
+minikube start \
    --network-plugin=cni \
    --enable-default-cni \
    --extra-config=kubelet.container-runtime=remote \
@@ -133,7 +166,7 @@ $ minikube start \
 [CRI-O](https://github.com/kubernetes-incubator/cri-o)를 컨테이너 런타임으로 사용하려면, 다음을 실행한다.

 ```bash
-$ minikube start \
+minikube start \
    --network-plugin=cni \
    --enable-default-cni \
    --container-runtime=cri-o \
@@ -143,7 +176,7 @@ $ minikube start \
 혹은 확장 버전을 사용할 수 있다.

 ```bash
-$ minikube start \
+minikube start \
    --network-plugin=cni \
    --enable-default-cni \
    --extra-config=kubelet.container-runtime=remote \
@@ -157,7 +190,7 @@ $ minikube start \
 [rkt](https://github.com/rkt/rkt)를 컨테이너 런타임으로 사용하려면, 다음을 실행한다.

 ```shell
-$ minikube start \
+minikube start \
    --network-plugin=cni \
    --enable-default-cni \
    --container-runtime=rkt
@@ -373,7 +406,7 @@ HTTP 프록시 내부라면, Docker에서 프록시 설정을 해야 한다.
 예를 들어:

 ```shell
-$ minikube start --docker-env http_proxy=http://$YOURPROXY:PORT \
+minikube start --docker-env http_proxy=http://$YOURPROXY:PORT \
                 --docker-env https_proxy=https://$YOURPROXY:PORT
 ```

@@ -381,7 +414,7 @@ $ minikube start --docker-env http_proxy=http://$YOURPROXY:PORT \
 이 IP 주소에 대해 프록시 설정을 지나치게 하려면 no_proxy 설정을 수정해야 한다. 다음과 같이 할 수 있다.

 ```shell
-$ export no_proxy=$no_proxy,$(minikube ip)
+export no_proxy=$no_proxy,$(minikube ip)
 ```

 ## 알려진 이슈
@@ -41,8 +41,16 @@ card:

 ## 로컬 머신 솔루션

+### 커뮤니티 지원 도구
+
 * [Minikube](/docs/setup/minikube/)는 개발과 테스트를 위한 단일 노드 쿠버네티스 클러스터를 로컬에 생성하기 위한 하나의 방법이다. 설치는 완전히 자동화 되어 있고, 클라우드 공급자 계정 정보가 필요하지 않다. 

+* [Kubeadm-dind](https://github.com/kubernetes-sigs/kubeadm-dind-cluster)는 다중 노드 (minikube는 단일 노드인 반면) docker 데몬만 필요로 하는 쿠버네티스 클러스터이다. docker-in-docker 기술을 사용하여 쿠버네티스 클러스터를 생성한다.
+
+* [Kubernetes IN Docker](https://github.com/kubernetes-sigs/kind)는 Docker 컨테이너 "노드"를 사용하여 로컬 쿠버네티스 클러스터를 실행하기 위한 도구이다. 이것은 주로 쿠버네티스 1.11+를 테스트하기 위해 설계되었다. 이를 사용하여 다중 노드 또는 다중 컨트롤 플레인 쿠버네티스 클러스터를 만들 수 있다.
+
+### 생태계 도구
+
 * [Docker Desktop](https://www.docker.com/products/docker-desktop)는
 Mac 또는 Windows 환경에서 쉽게 설치 가능한 애플리케이션이다.
 수 분 내에 단일 노드 쿠버네티스 클러스터에서 컨테이너로 코딩과 배포를 
@@ -56,8 +64,6 @@ Mac 또는 Windows 환경에서 쉽게 설치 가능한 애플리케이션이다

 * [IBM Cloud Private-CE (Community Edition) on Linux Containers](https://github.com/HSBawa/icp-ce-on-linux-containers)는 Terraform/Packer/BASH 기반의 리눅스 호스트 상의 LXD 클러스터에 7개의 노드(부트 1개, 마스터 1개, 관리 1개, 프록시 1개 그리고 워커 3개)를 생성하기 위한 Infrastructure as Code (IaC) 스크립트이다.

-* [Kubeadm-dind](https://github.com/kubernetes-sigs/kubeadm-dind-cluster)는 하나의 docker 데몬이 필요한 멀티 노드 쿠버네티스 클러스터이다.(minikube는 단일 노드이다.) 클러스터 생성을 위해서 docker-in-docker 기술을 사용한다. 
-
 * [Ubuntu on LXD](/docs/getting-started-guides/ubuntu/local/)는 로컬 호스트에서 9개의 인스턴스 배포를 지원한다.

 ## 호스트 된 솔루션
@@ -94,7 +100,7 @@ Mac 또는 Windows 환경에서 쉽게 설치 가능한 애플리케이션이다

 * [OpenShift Online](https://www.openshift.com/features/)은 쿠버네티스 애플리케이션을 위해 호스트 된 무료 접근을 제공한다. 

-* [Oracle Container Engine for Kubernetes](https://docs.us-phoenix-1.oraclecloud.com/Content/ContEng/Concepts/contengoverview.htm)는 컨테이너 애플리케이션을 클라우드에 배포하는 데 사용할 수 있는 완벽하게 관리되고, 확장 가능하며, 가용성이 높은 서비스이다.
+* [Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE)](https://docs.us-phoenix-1.oraclecloud.com/Content/ContEng/Concepts/contengoverview.htm)는 컨테이너 애플리케이션을 클라우드에 배포하는 데 사용할 수 있는 완벽하게 관리되고, 확장 가능하며, 가용성이 높은 서비스이다.

 * [Platform9](https://platform9.com/products/kubernetes/)는 온-프레미스 또는 모든 퍼블릭 클라우드에서 관리형 쿠버네티스를 제공한다. 또한, 24/7 상태 모니터링 및 알람 및 경고 서비스를 제공한다.(Kube2go는 웹 UI 기반의 쿠버네티스 클러스터 배포 서비스인 Platform9가 Platform9 Sandbox에 통합된 형태로 출시되었다.)

@@ -102,6 +108,8 @@ Mac 또는 Windows 환경에서 쉽게 설치 가능한 애플리케이션이다

 * [SysEleven MetaKube](https://www.syseleven.io/products-services/managed-kubernetes/)는 자체 OpenStack 퍼블릭 클라우드 상에서 서비스로써 관리형 쿠버네티스를 제공한다. 라이프사이클 관리, 관리 대시보드, 모니터링, 오토스케일링과 그 밖에 많은 기능을 포함한다.

+* [VEXXHOST](https://vexxhost.com/public-cloud/container-services/kubernetes/) VEXXHOST는 공공 클라우드에서 공인된 쿠버네티스를 제공하며, 캐나다에서 가장 큰 OpenStack 퍼블릭 클라우드이다.
+
 * [VMware Cloud PKS](https://cloud.vmware.com/vmware-cloud-pks)는 사용하기 쉽고, 기본적으로 안전하며, 비용 효율적인 SaaS 기반의 쿠버네티스 클러스터를 제공하는 VMWare 클라우드 서비스 포트폴리오의 엔터프라이즈 Kubernetes-as-a-Service 오퍼링이다.

 ## 턴키 클라우드 솔루션
@@ -127,12 +135,14 @@ Mac 또는 Windows 환경에서 쉽게 설치 가능한 애플리케이션이다
 * [Madcore.Ai](https://madcore.ai/)
 * [Nirmata](https://nirmata.com/)
 * [Nutanix Karbon](https://www.nutanix.com/products/karbon/)
-* [Oracle Container Engine for K8s](https://docs.us-phoenix-1.oraclecloud.com/Content/ContEng/Concepts/contengprerequisites.htm)
+* [Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE)](https://docs.us-phoenix-1.oraclecloud.com/Content/ContEng/Concepts/contengprerequisites.htm)
 * [Pivotal Container Service](https://pivotal.io/platform/pivotal-container-service)
 * [Rancher 2.0](https://rancher.com/docs/rancher/v2.x/en/)
 * [Stackpoint.io](/docs/setup/turnkey/stackpoint/)
-* [Tectonic by CoreOS](https://coreos.com/tectonic)
+* [Supergiant.io](https://supergiant.io/)
+* [VEXXHOST](https://vexxhost.com/private-cloud/)
 * [VMware Cloud PKS](https://cloud.vmware.com/vmware-cloud-pks)
+* [VMware Enterprise PKS](https://cloud.vmware.com/vmware-enterprise-pks)

 ## 온-프레미스 턴키 클라우드 솔루션

@@ -146,7 +156,7 @@ Mac 또는 Windows 환경에서 쉽게 설치 가능한 애플리케이션이다
 * [IBM Cloud Private](https://www.ibm.com/cloud-computing/products/ibm-cloud-private/)
 * [Kontena Pharos](https://kontena.io/pharos/)
 * [Kubermatic](https://www.loodse.com)
-* [Kublr](https://kublr.com/)
+* [Kublr](www.kublr.com/kubernetes.io/setup-hosted-solution)
 * [Mirantis Cloud Platform](https://www.mirantis.com/software/kubernetes/)
 * [Nirmata](https://nirmata.com/)
 * [OpenShift Container Platform](https://www.openshift.com/products/container-platform/) (OCP) by [Red Hat](https://www.redhat.com)
@@ -154,14 +164,14 @@ Mac 또는 Windows 환경에서 쉽게 설치 가능한 애플리케이션이다
 * [Rancher 2.0](https://rancher.com/docs/rancher/v2.x/en/)
 * [SUSE CaaS Platform](https://www.suse.com/products/caas-platform)
 * [SUSE Cloud Application Platform](https://www.suse.com/products/cloud-application-platform/)
+* [VMware Enterprise PKS](https://cloud.vmware.com/vmware-enterprise-pks)
+

 ## 사용자 지정 솔루션

 쿠버네티스는 넓은 범위의 클라우드 공급자와 베어메탈 환경에서, 그리고 많은 기반 운영 체제에서 동작할 수 있다.

-필요에 맞는 가이드를 아래에서 찾았다면, 그것을 사용하자. 약간 구식일 수도 있지만, 처음부터 시작하는 것보다 더 쉬울 것이다. 
-특별한 요구사항이 있기 때문에, 또는 단지 쿠버네티스 클러스터의 아래에 무엇이 있는지를 이해하기 원하기 때문에 
-처음부터 시작하기를 원한다면, [맨 처음부터 시작하기](/docs/setup/scratch/) 가이드를 시도하라. 
+필요에 맞는 가이드를 아래에서 찾았다면, 그것을 사용하자.

 ### 일반

@@ -172,35 +182,34 @@ Mac 또는 Windows 환경에서 쉽게 설치 가능한 애플리케이션이다
 다음 솔루션은 위의 솔루션에서 다루지 않는 클라우드 공급자와 운영체제의 조합이다. 

 * [Cloud Foundry Container Runtime (CFCR)](https://docs-cfcr.cfapps.io/)
-* [CoreOS on AWS or GCE](/docs/setup/custom-cloud/coreos/)
 * [Gardener](https://gardener.cloud/)
-* [Kublr](https://kublr.com/)
+* [Kublr](www.kublr.com/kubernetes.io/setup-hosted-solution)
 * [Kubernetes on Ubuntu](/docs/getting-started-guides/ubuntu/)
 * [Kubespray](/docs/setup/custom-cloud/kubespray/)
 * [Rancher Kubernetes Engine (RKE)](https://github.com/rancher/rke)
+* [VMware Essential PKS](https://cloud.vmware.com/vmware-essential-PKS)

 ### 온-프레미스 VM

 * [Cloud Foundry Container Runtime (CFCR)](https://docs-cfcr.cfapps.io/)
-* [CloudStack](/docs/setup/on-premises-vm/cloudstack/) (Ansible, CoreOS와 flannel를 사용)
-* [Fedora (Multi Node)](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/) (Fedora와 flannel를 사용)
+* [CloudStack](/docs/setup/on-premises-vm/cloudstack/) (uses Ansible)
+* [Fedora (Multi Node)](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/) (uses Fedora and flannel)
 * [Nutanix AHV](https://www.nutanix.com/products/acropolis/virtualization/)
 * [OpenShift Container Platform](https://www.openshift.com/products/container-platform/) (OCP) Kubernetes platform by [Red Hat](https://www.redhat.com)
 * [oVirt](/docs/setup/on-premises-vm/ovirt/)
-* [Vagrant](/docs/setup/custom-cloud/coreos/) (CoreOS와 flannel를 사용)
-* [VMware](/docs/setup/custom-cloud/coreos/) (CoreOS와 flannel를 사용)
-* [VMware vSphere](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/)
-* [VMware vSphere, OpenStack, or Bare Metal](/docs/getting-started-guides/ubuntu/) (Juju, Ubuntu와 flannel를 사용)
+* [VMware Essential PKS](https://cloud.vmware.com/vmware-essential-PKS)
+* [VMware vSphere](https://github.com/kubernetes/cloud-provider-vsphere)
+* [VMware vSphere, OpenStack, or Bare Metal](/docs/getting-started-guides/ubuntu/) (uses Juju, Ubuntu and flannel)

 ### 베어 메탈

-* [CoreOS](/docs/setup/custom-cloud/coreos/)
 * [Digital Rebar](/docs/setup/on-premises-metal/krib/)
 * [Docker Enterprise](https://www.docker.com/products/docker-enterprise)
 * [Fedora (Single Node)](/docs/getting-started-guides/fedora/fedora_manual_config/)
 * [Fedora (Multi Node)](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/)
 * [Kubernetes on Ubuntu](/docs/getting-started-guides/ubuntu/)
 * [OpenShift Container Platform](https://www.openshift.com/products/container-platform/) (OCP) Kubernetes platform by [Red Hat](https://www.redhat.com)
+* [VMware Essential PKS](https://cloud.vmware.com/vmware-essential-PKS)

 ### 통합

@@ -216,59 +225,58 @@ Mac 또는 Windows 환경에서 쉽게 설치 가능한 애플리케이션이다

 IaaS 공급자        | 구성 관리 | OS     | 네트워킹  | 문서                                              | 지원 레벨
 -------------------- | ------------ | ------ | ----------  | ---------------------------------------------     | ----------------------------
+Agile Stacks       | Terraform   | CoreOS | multi-support | [docs](https://www.agilestacks.com/products/kubernetes) | Commercial
+Alibaba Cloud Container Service For Kubernetes | ROS        | CentOS | flannel/Terway       | [docs](https://www.aliyun.com/product/containerservice)                    |  Commercial
 any                  | any          | multi-support | any CNI | [docs](/docs/setup/independent/create-cluster-kubeadm/) | Project ([SIG-cluster-lifecycle](https://git.k8s.io/community/sig-cluster-lifecycle))
-Google Kubernetes Engine |              |        | GCE         | [docs](https://cloud.google.com/kubernetes-engine/docs/) | Commercial
-Docker Enterprise    | custom | [multi-support](https://success.docker.com/article/compatibility-matrix) | [multi-support](https://docs.docker.com/ee/ucp/kubernetes/install-cni-plugin/) | [docs](https://docs.docker.com/ee/) | Commercial
-IBM Cloud Private  | Ansible  | multi-support  | multi-support  | [docs](https://www.ibm.com/support/knowledgecenter/SSBS6K/product_welcome_cloud_private.html) | [Commercial](https://www.ibm.com/mysupport/s/topic/0TO500000001o0fGAA/ibm-cloud-private?language=en_US&productId=01t50000004X1PWAA0) and [Community](https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.2/troubleshoot/support_types.html) |
-Red Hat OpenShift    | Ansible & CoreOS | RHEL & CoreOS   | [multi-support](https://docs.openshift.com/container-platform/3.11/architecture/networking/network_plugins.html) | [docs](https://docs.openshift.com/container-platform/3.11/welcome/index.html) | Commercial
-Stackpoint.io        |              | multi-support       | multi-support   | [docs](https://stackpoint.io/) | Commercial
-AppsCode.com         | Saltstack    | Debian | multi-support | [docs](https://appscode.com/products/cloud-deployment/) | Commercial
-Madcore.Ai           | Jenkins DSL  | Ubuntu | flannel     | [docs](https://madcore.ai)                        | Community ([@madcore-ai](https://github.com/madcore-ai))
-Platform9        |              | multi-support | multi-support | [docs](https://platform9.com/managed-kubernetes/) | Commercial
-Kublr       | custom       | multi-support | multi-support | [docs](http://docs.kublr.com/) | Commercial
-Kubermatic       |              | multi-support | multi-support | [docs](http://docs.kubermatic.io/) | Commercial
-IBM Cloud Kubernetes Service |               | Ubuntu | IBM Cloud Networking + Calico | [docs](https://cloud.ibm.com/docs/containers?topic=containers-container_index#container_index) | Commercial
-Giant Swarm        |              | CoreOS | flannel and/or Calico | [docs](https://docs.giantswarm.io/) | Commercial
-GCE                  | Saltstack    | Debian | GCE         | [docs](/docs/setup/turnkey/gce/)                                    | Project
-Azure Kubernetes Service |              | Ubuntu | Azure       | [docs](https://docs.microsoft.com/en-us/azure/aks/)                    |  Commercial
-Azure (IaaS)    |              | Ubuntu | Azure       | [docs](/docs/setup/turnkey/azure/)                    |  [Community (Microsoft)](https://github.com/Azure/acs-engine)
-Bare-metal           | custom       | Fedora | _none_      | [docs](/docs/getting-started-guides/fedora/fedora_manual_config/)            |  Project
-Bare-metal           | custom       | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/)      |  Community ([@aveshagarwal](https://github.com/aveshagarwal))
-libvirt              | custom       | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/)      |  Community ([@aveshagarwal](https://github.com/aveshagarwal))
-KVM                  | custom       | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/)      |  Community ([@aveshagarwal](https://github.com/aveshagarwal))
-DCOS                 | Marathon   | CoreOS/Alpine | custom | [docs](/docs/getting-started-guides/dcos/)                                   |  Community ([Kubernetes-Mesos Authors](https://github.com/mesosphere/kubernetes-mesos/blob/master/AUTHORS.md))
-AWS                  | CoreOS       | CoreOS | flannel     | [docs](/docs/setup/turnkey/aws/)                                 |  Community
-GCE                  | CoreOS       | CoreOS | flannel     | [docs](/docs/getting-started-guides/coreos/)                                 |  Community ([@pires](https://github.com/pires))
-Vagrant              | CoreOS       | CoreOS | flannel     | [docs](/docs/getting-started-guides/coreos/)                                 |  Community ([@pires](https://github.com/pires), [@AntonioMeireles](https://github.com/AntonioMeireles))
-CloudStack           | Ansible      | CoreOS | flannel     | [docs](/docs/getting-started-guides/cloudstack/)                             |  Community ([@sebgoa](https://github.com/sebgoa))
-VMware vSphere       | any          | multi-support | multi-support     | [docs](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/)  |  [Community](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/contactus.html)
-Bare-metal           | custom       | CentOS | flannel      | [docs](/docs/getting-started-guides/centos/centos_manual_config/)            |  Community ([@coolsvap](https://github.com/coolsvap))
-lxd                  | Juju         | Ubuntu | flannel/canal            | [docs](/docs/getting-started-guides/ubuntu/local/)              |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
-AWS                  | Juju         | Ubuntu | flannel/calico/canal     | [docs](/docs/getting-started-guides/ubuntu/)                    |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
-Azure                | Juju         | Ubuntu | flannel/calico/canal     | [docs](/docs/getting-started-guides/ubuntu/)                    |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
-GCE                  | Juju         | Ubuntu | flannel/calico/canal     | [docs](/docs/getting-started-guides/ubuntu/)                    |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
-Oracle Cloud         | Juju         | Ubuntu | flannel/calico/canal     | [docs](/docs/getting-started-guides/ubuntu/)                    |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
-Rackspace            | custom       | CoreOS | flannel/calico/canal     | [docs](https://developer.rackspace.com/docs/rkaas/latest/)      |  [Commercial](https://www.rackspace.com/managed-kubernetes)
-VMware vSphere       | Juju         | Ubuntu | flannel/calico/canal     | [docs](/docs/getting-started-guides/ubuntu/)                    |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
-Bare Metal           | Juju         | Ubuntu | flannel/calico/canal     | [docs](/docs/getting-started-guides/ubuntu/)                    |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
-AWS                  | Saltstack    | Debian | AWS         | [docs](/docs/setup/turnkey/aws/)                                    |  Community ([@justinsb](https://github.com/justinsb))
-AWS                  | kops         | Debian | AWS         | [docs](https://github.com/kubernetes/kops/)                                  |  Community ([@justinsb](https://github.com/justinsb))
-Bare-metal           | custom       | Ubuntu | flannel     | [docs](/docs/getting-started-guides/ubuntu/)                                 |  Community ([@resouer](https://github.com/resouer), [@WIZARD-CXY](https://github.com/WIZARD-CXY))
-oVirt                |              |        |             | [docs](/docs/setup/on-premises-vm/ovirt/)                                  |  Community ([@simon3z](https://github.com/simon3z))
 any                  | any          | any    | any         | [docs](/docs/setup/scratch/)                                |  Community ([@erictune](https://github.com/erictune))
 any                  | any          | any    | any         | [docs](http://docs.projectcalico.org/v2.2/getting-started/kubernetes/installation/)                                |  Commercial and Community
 any                  | RKE          | multi-support    | flannel or canal         | [docs](https://rancher.com/docs/rancher/v2.x/en/quick-start-guide/)                                |  [Commercial](https://rancher.com/what-is-rancher/overview/) and [Community](https://github.com/rancher/rancher)
 any                  | [Gardener Cluster-Operator](https://kubernetes.io/blog/2018/05/17/gardener/) | multi-support | multi-support | [docs](https://gardener.cloud) | [Project/Community](https://github.com/gardener) and [Commercial]( https://cloudplatform.sap.com/)
-Alibaba Cloud Container Service For Kubernetes | ROS        | CentOS | flannel/Terway       | [docs](https://www.aliyun.com/product/containerservice)                    |  Commercial
-Agile Stacks       | Terraform   | CoreOS | multi-support | [docs](https://www.agilestacks.com/products/kubernetes) | Commercial
-IBM Cloud Kubernetes Service | | Ubuntu | calico | [docs](https://cloud.ibm.com/docs/containers?topic=containers-container_index#container_index) | Commercial
+AppsCode.com         | Saltstack    | Debian | multi-support | [docs](https://appscode.com/products/cloud-deployment/) | Commercial
+AWS                  | CoreOS       | CoreOS | flannel     | [docs](/docs/setup/turnkey/aws/)                                 |  Community
+AWS                  | Saltstack    | Debian | AWS         | [docs](/docs/setup/turnkey/aws/)                                    |  Community ([@justinsb](https://github.com/justinsb))
+AWS                  | kops         | Debian | AWS         | [docs](https://github.com/kubernetes/kops/)                                  |  Community ([@justinsb](https://github.com/justinsb))
+AWS                  | Juju         | Ubuntu | flannel/calico/canal     | [docs](/docs/getting-started-guides/ubuntu/)                    |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
+Azure                | Juju         | Ubuntu | flannel/calico/canal     | [docs](/docs/getting-started-guides/ubuntu/)                    |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
+Azure (IaaS)         |              | Ubuntu | Azure       | [docs](/docs/setup/turnkey/azure/)                    |  [Community (Microsoft)](https://github.com/Azure/acs-engine)
+Azure Kubernetes Service |              | Ubuntu | Azure       | [docs](https://docs.microsoft.com/en-us/azure/aks/)                    |  Commercial
+Bare-metal           | custom       | CentOS | flannel      | [docs](/docs/getting-started-guides/centos/centos_manual_config/)            |  Community ([@coolsvap](https://github.com/coolsvap))
+Bare-metal           | custom       | Fedora | _none_      | [docs](/docs/getting-started-guides/fedora/fedora_manual_config/)            |  Project
+Bare-metal           | custom       | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/)      |  Community ([@aveshagarwal](https://github.com/aveshagarwal))
+Bare Metal           | Juju         | Ubuntu | flannel/calico/canal     | [docs](/docs/getting-started-guides/ubuntu/)                    |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
+Bare-metal           | custom       | Ubuntu | flannel     | [docs](/docs/getting-started-guides/ubuntu/)                                 |  Community ([@resouer](https://github.com/resouer), [@WIZARD-CXY](https://github.com/WIZARD-CXY))
+CloudStack           | Ansible      | CoreOS | flannel     | [docs](/docs/getting-started-guides/cloudstack/)                             |  Community ([@sebgoa](https://github.com/sebgoa))
+DCOS                 | Marathon   | CoreOS/Alpine | custom | [docs](/docs/getting-started-guides/dcos/)                                   |  Community ([Kubernetes-Mesos Authors](https://github.com/mesosphere/kubernetes-mesos/blob/master/AUTHORS.md))
 Digital Rebar        | kubeadm      | any    | metal       | [docs](/docs/setup/on-premises-metal/krib/)                                  | Community ([@digitalrebar](https://github.com/digitalrebar))
-VMware Cloud PKS     |              | Photon OS | Canal | [docs](https://docs.vmware.com/en/VMware-Kubernetes-Engine/index.html) | Commercial
+Docker Enterprise    | custom | [multi-support](https://success.docker.com/article/compatibility-matrix) | [multi-support](https://docs.docker.com/ee/ucp/kubernetes/install-cni-plugin/) | [docs](https://docs.docker.com/ee/) | Commercial
+Giant Swarm          |              | CoreOS | flannel and/or Calico | [docs](https://docs.giantswarm.io/) | Commercial
+GCE                  | CoreOS       | CoreOS | flannel     | [docs](/docs/getting-started-guides/coreos/)                                 |  Community ([@pires](https://github.com/pires))
+GCE                  | Juju         | Ubuntu | flannel/calico/canal     | [docs](/docs/getting-started-guides/ubuntu/)                    |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
+GCE                  | Saltstack    | Debian | GCE         | [docs](/docs/setup/turnkey/gce/)                                    | Project
+Google Kubernetes Engine |              |        | GCE         | [docs](https://cloud.google.com/kubernetes-engine/docs/) | Commercial
+IBM Cloud Kubernetes Service |               | Ubuntu | IBM Cloud Networking + Calico | [docs](https://cloud.ibm.com/docs/containers?topic=containers-container_index#container_index) | Commercial
+IBM Cloud Kubernetes Service | | Ubuntu | calico | [docs](https://cloud.ibm.com/docs/containers?topic=containers-container_index#container_index) | Commercial
+IBM Cloud Private  | Ansible  | multi-support  | multi-support  | [docs](https://www.ibm.com/support/knowledgecenter/SSBS6K/product_welcome_cloud_private.html) | [Commercial](https://www.ibm.com/mysupport/s/topic/0TO500000001o0fGAA/ibm-cloud-private?language=en_US&productId=01t50000004X1PWAA0) and [Community](https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.2/troubleshoot/support_types.html) |
+Kublr                | custom       | multi-support | multi-support | [docs](http://docs.kublr.com/) | Commercial
+Kubermatic           |              | multi-support | multi-support | [docs](http://docs.kubermatic.io/) | Commercial
+KVM                  | custom       | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/)      |  Community ([@aveshagarwal](https://github.com/aveshagarwal))
+libvirt              | custom       | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/)      |  Community ([@aveshagarwal](https://github.com/aveshagarwal))
+lxd                  | Juju         | Ubuntu | flannel/canal            | [docs](/docs/getting-started-guides/ubuntu/local/)              |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
+Madcore.Ai           | Jenkins DSL  | Ubuntu | flannel     | [docs](https://madcore.ai)                        | Community ([@madcore-ai](https://github.com/madcore-ai))
 Mirantis Cloud Platform | Salt | Ubuntu | multi-support | [docs](https://docs.mirantis.com/mcp/) | Commercial
-
-{{< note >}}
-위의 표는 버전 테스트/사용된 노드의 지원 레벨을 기준으로 정렬된다.
-{{< /note >}}
+Oracle Cloud Infrastructure        | Juju         | Ubuntu | flannel/calico/canal     | [docs](/docs/getting-started-guides/ubuntu/)                    |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
+Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) |              |              | multi-support | [docs](https://docs.cloud.oracle.com/iaas/Content/ContEng/Concepts/contengoverview.htm) | Commercial
+oVirt                |              |        |             | [docs](/docs/setup/on-premises-vm/ovirt/)                                  |  Community ([@simon3z](https://github.com/simon3z))
+Platform9            |              | multi-support | multi-support | [docs](https://platform9.com/managed-kubernetes/) | Commercial
+Rackspace            | custom       | CoreOS | flannel/calico/canal     | [docs](https://developer.rackspace.com/docs/rkaas/latest/)      |  [Commercial](https://www.rackspace.com/managed-kubernetes)
+Red Hat OpenShift    | Ansible & CoreOS | RHEL & CoreOS   | [multi-support](https://docs.openshift.com/container-platform/3.11/architecture/networking/network_plugins.html) | [docs](https://docs.openshift.com/container-platform/3.11/welcome/index.html) | Commercial
+Stackpoint.io        |              | multi-support       | multi-support   | [docs](https://stackpoint.io/) | Commercial
+Vagrant              | CoreOS       | CoreOS | flannel     | [docs](/docs/getting-started-guides/coreos/)                                 |  Community ([@pires](https://github.com/pires), [@AntonioMeireles](https://github.com/AntonioMeireles))
+VMware vSphere       | any          | multi-support | multi-support     | [docs](https://github.com/kubernetes/cloud-provider-vsphere/tree/master/docs)  |  [Community](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/contactus.html)
+VMware vSphere       | Juju         | Ubuntu | flannel/calico/canal     | [docs](/docs/getting-started-guides/ubuntu/)                    |  [Commercial](https://www.ubuntu.com/kubernetes) and [Community](https://jujucharms.com/kubernetes)
+VMware Cloud PKS     |              | Photon OS | Canal | [docs](https://docs.vmware.com/en/VMware-Kubernetes-Engine/index.html) | Commercial
+VMware Enterprise PKS     | BOSH       | Ubuntu | VMware NSX-T/flannel | [docs](https://docs.vmware.com/en/VMware-Enterprise-PKS/) | Commercial
+VMware Essential PKS     | any       | multi-support | multi-support | [docs](https://cloud.vmware.com/vmware-essential-PKS) | Commercial

 ### 열 정의

@@ -278,7 +286,6 @@ Mirantis Cloud Platform | Salt | Ubuntu | multi-support | [docs](https://docs.mi
  nodes.
 * **네트워킹**은 [네트워킹 모델](/docs/concepts/cluster-administration/networking/)을 구현하는 것이다. 네트워크 유형이
  _none_인 노드는 단일 노드 이상을 지원하지 않거나, 단일 물리 노드에서 여러 VM 노드를 지원할 수 있다. 
-* **적합성**은 명시된 구성으로 생성된 클러스터가 쿠버네티스 v1.0.0의 API 및 기본 기능을 지원하는지의 프로젝트 적합성 테스트 통과 여부를 나타낸다.
 * **지원 레벨**
  * **프로젝트**: 쿠버네티스 커미터는 현재 구성을 정기적으로 사용하므로, 일반적으로 최신 쿠버네티스 릴리즈와 함께 동작한다. 
  * **상업용**: 자체 지원 계약을 가진 상업용 제품.
@@ -1,872 +0,0 @@
---
-title: 맨 처음부터 사용자 지정 클러스터 생성
---
-
-This guide is for people who want to craft a custom Kubernetes cluster.  If you
-can find an existing Getting Started Guide that meets your needs on [this
-list](/docs/setup/), then we recommend using it, as you will be able to benefit
-from the experience of others.  However, if you have specific IaaS, networking,
-configuration management, or operating system requirements not met by any of
-those guides, then this guide will provide an outline of the steps you need to
-take.  Note that it requires considerably more effort than using one of the
-pre-defined guides.
-
-This guide is also useful for those wanting to understand at a high level some of the
-steps that existing cluster setup scripts are making.
-
-{{< toc >}}
-
-## 설계 및 준비
-
-### 학습 계획
-
-  1. You should be familiar with using Kubernetes already.  We suggest you set
-    up a temporary cluster by following one of the other Getting Started Guides.
-    This will help you become familiar with the CLI ([kubectl](/docs/user-guide/kubectl/)) and concepts ([pods](/docs/user-guide/pods/), [services](/docs/concepts/services-networking/service/), etc.) first.
-  1. You should have `kubectl` installed on your desktop.  This will happen as a side
-    effect of completing one of the other Getting Started Guides.  If not, follow the instructions
-    [here](/docs/tasks/kubectl/install/).
-
-### 클라우드 공급자
-
-Kubernetes has the concept of a Cloud Provider, which is a module which provides
-an interface for managing TCP Load Balancers, Nodes (Instances) and Networking Routes.
-The interface is defined in `pkg/cloudprovider/cloud.go`.  It is possible to
-create a custom cluster without implementing a cloud provider (for example if using
-bare-metal), and not all parts of the interface need to be implemented, depending
-on how flags are set on various components.
-
-### 노드
-
- You can use virtual or physical machines.
- While you can build a cluster with 1 machine, in order to run all the examples and tests you
-  need at least 4 nodes.
- Many Getting-started-guides make a distinction between the master node and regular nodes.  This
-  is not strictly necessary.
- Nodes will need to run some version of Linux with the x86_64 architecture.  It may be possible
-  to run on other OSes and Architectures, but this guide does not try to assist with that.
- Apiserver and etcd together are fine on a machine with 1 core and 1GB RAM for clusters with 10s of nodes.
-  Larger or more active clusters may benefit from more cores.
- Other nodes can have any reasonable amount of memory and any number of cores.  They need not
-  have identical configurations.
-
-### 네트워크
-
-#### 네트워크 연결
-Kubernetes has a distinctive [networking model](/docs/concepts/cluster-administration/networking/).
-
-Kubernetes allocates an IP address to each pod.  When creating a cluster, you
-need to allocate a block of IPs for Kubernetes to use as Pod IPs.  The simplest
-approach is to allocate a different block of IPs to each node in the cluster as
-the node is added.  A process in one pod should be able to communicate with
-another pod using the IP of the second pod.  This connectivity can be
-accomplished in two ways:
-
- **Using an overlay network**
-  - An overlay network obscures the underlying network architecture from the
-    pod network through traffic encapsulation (for example vxlan).
-  - Encapsulation reduces performance, though exactly how much depends on your solution.
- **Without an overlay network**
-  - Configure the underlying network fabric (switches, routers, etc.) to be aware of pod IP addresses.
-  - This does not require the encapsulation provided by an overlay, and so can achieve
-    better performance.
-
-Which method you choose depends on your environment and requirements.  There are various ways
-to implement one of the above options:
-
- **Use a network plugin which is called by Kubernetes**
-  - Kubernetes supports the [CNI](https://github.com/containernetworking/cni) network plugin interface.
-  - There are a number of solutions which provide plugins for Kubernetes (listed alphabetically):
-    - [Calico](http://docs.projectcalico.org/)
-    - [Flannel](https://github.com/coreos/flannel)
-    - [Open vSwitch (OVS)](http://openvswitch.org/)
-    - [Romana](http://romana.io/)
-    - [Weave](http://weave.works/)
-    - [More found here](/docs/admin/networking#how-to-achieve-this/)
-  - You can also write your own.
- **Compile support directly into Kubernetes**
-  - This can be done by implementing the "Routes" interface of a Cloud Provider module.
-  - The Google Compute Engine ([GCE](/docs/setup/turnkey/gce/)) and [AWS](/docs/setup/turnkey/aws/) guides use this approach.
- **Configure the network external to Kubernetes**
-  - This can be done by manually running commands, or through a set of externally maintained scripts.
-  - You have to implement this yourself, but it can give you an extra degree of flexibility.
-
-You will need to select an address range for the Pod IPs.
-
- Various approaches:
-  - GCE: each project has its own `10.0.0.0/8`.  Carve off a `/16` for each
-    Kubernetes cluster from that space, which leaves room for several clusters.
-    Each node gets a further subdivision of this space.
-  - AWS: use one VPC for whole organization, carve off a chunk for each
-    cluster, or use different VPC for different clusters.
- Allocate one CIDR subnet for each node's PodIPs, or a single large CIDR
-  from which smaller CIDRs are automatically allocated to each node.
-  - You need max-pods-per-node * max-number-of-nodes IPs in total. A `/24` per
-    node supports 254 pods per machine and is a common choice.  If IPs are
-    scarce, a `/26` (62 pods per machine) or even a `/27` (30 pods) may be sufficient.
-  - For example, use `10.10.0.0/16` as the range for the cluster, with up to 256 nodes
-    using `10.10.0.0/24` through `10.10.255.0/24`, respectively.
-  - Need to make these routable or connect with overlay.
-
-Kubernetes also allocates an IP to each [service](/docs/concepts/services-networking/service/).  However,
-service IPs do not necessarily need to be routable.  The kube-proxy takes care
-of translating Service IPs to Pod IPs before traffic leaves the node.  You do
-need to allocate a block of IPs for services.  Call this
-`SERVICE_CLUSTER_IP_RANGE`.  For example, you could set
-`SERVICE_CLUSTER_IP_RANGE="10.0.0.0/16"`, allowing 65534 distinct services to
-be active at once.  Note that you can grow the end of this range, but you
-cannot move it without disrupting the services and pods that already use it.
-
-Also, you need to pick a static IP for master node.
-
- Call this `MASTER_IP`.
- Open any firewalls to allow access to the apiserver ports 80 and/or 443.
- Enable ipv4 forwarding sysctl, `net.ipv4.ip_forward = 1`
-
-#### 네트워크 폴리시
-
-Kubernetes enables the definition of fine-grained network policy between Pods using the [NetworkPolicy](/docs/concepts/services-networking/network-policies/) resource.
-
-Not all networking providers support the Kubernetes NetworkPolicy API, see [Using Network Policy](/docs/tasks/configure-pod-container/declare-network-policy/) for more information.
-
-### 클러스터 이름 구성
-
-You should pick a name for your cluster.  Pick a short name for each cluster
-which is unique from future cluster names. This will be used in several ways:
-
-  - by kubectl to distinguish between various clusters you have access to.  You will probably want a
-    second one sometime later, such as for testing new Kubernetes releases, running in a different
-region of the world, etc.
-  - Kubernetes clusters can create cloud provider resources (for example, AWS ELBs) and different clusters
-    need to distinguish which resources each created.  Call this `CLUSTER_NAME`.
-
-### 소프트웨어 바이너리
-
-You will need binaries for:
-
-  - etcd
-  - A container runner, one of:
-    - docker
-    - rkt
-  - Kubernetes
-    - kubelet
-    - kube-proxy
-    - kube-apiserver
-    - kube-controller-manager
-    - kube-scheduler
-
-#### 쿠버네티스 바이너리 다운로드 및 압축 해제
-
-A Kubernetes binary release includes all the Kubernetes binaries as well as the supported release of etcd.
-You can use a Kubernetes binary release (recommended) or build your Kubernetes binaries following the instructions in the
-[Developer Documentation](https://git.k8s.io/community/contributors/devel/).  Only using a binary release is covered in this guide.
-
-Download the [latest binary release](https://github.com/kubernetes/kubernetes/releases/latest) and unzip it.
-Server binary tarballs are no longer included in the Kubernetes final tarball, so you will need to locate and run
-`./kubernetes/cluster/get-kube-binaries.sh` to download and extract the client and server binaries.
-Then locate `./kubernetes/server/bin`, which contains all the necessary binaries.
-
-#### 이미지 선택
-
-You will run docker, kubelet, and kube-proxy outside of a container, the same way you would run any system daemon, so
-you just need the bare binaries.  For etcd, kube-apiserver, kube-controller-manager, and kube-scheduler,
-we recommend that you run these as containers, so you need an image to be built.
-
-You have several choices for Kubernetes images:
-
- Use images hosted on Google Container Registry (GCR):
-  - For example `k8s.gcr.io/hyperkube:$TAG`, where `TAG` is the latest
-    release tag, which can be found on the [latest releases page](https://github.com/kubernetes/kubernetes/releases/latest).
-  - Ensure $TAG is the same tag as the release tag you are using for kubelet and kube-proxy.
-  - The [hyperkube](https://releases.k8s.io/{{< param "githubbranch" >}}/cmd/hyperkube) binary is an all in one binary
-    - `hyperkube kubelet ...` runs the kubelet, `hyperkube apiserver ...` runs an apiserver, etc.
- Build your own images.
-  - Useful if you are using a private registry.
-  - The release contains files such as `./kubernetes/server/bin/kube-apiserver.tar` which
-    can be converted into docker images using a command like
-    `docker load -i kube-apiserver.tar`
-  - You can verify if the image is loaded successfully with the right repository and tag using
-    command like `docker images`
-
-We recommend that you use the etcd version which is provided in the Kubernetes binary distribution.   The Kubernetes binaries in the release
-were tested extensively with this version of etcd and not with any other version.
-The recommended version number can also be found as the value of `TAG` in `kubernetes/cluster/images/etcd/Makefile`.
-
-For the minimum recommended version of etcd, refer to
-[Configuring and Updating etcd](/docs/tasks/administer-cluster/configure-upgrade-etcd/)
-
-The remainder of the document assumes that the image identifiers have been chosen and stored in corresponding env vars.  Examples (replace with latest tags and appropriate registry):
-
-  - `HYPERKUBE_IMAGE=k8s.gcr.io/hyperkube:$TAG`
-  - `ETCD_IMAGE=k8s.gcr.io/etcd:$ETCD_VERSION`
-
-### 보안 모델
-
-There are two main options for security:
-
- Access the apiserver using HTTP.
-  - Use a firewall for security.
-  - This is easier to setup.
- Access the apiserver using HTTPS
-  - Use https with certs, and credentials for user.
-  - This is the recommended approach.
-  - Configuring certs can be tricky.
-
-If following the HTTPS approach, you will need to prepare certs and credentials.
-
-#### 인증서 준비
-
-You need to prepare several certs:
-
- The master needs a cert to act as an HTTPS server.
- The kubelets optionally need certs to identify themselves as clients of the master, and when
-  serving its own API over HTTPS.
-
-Unless you plan to have a real CA generate your certs, you will need
-to generate a root cert and use that to sign the master, kubelet, and
-kubectl certs. How to do this is described in the [authentication
-documentation](/docs/concepts/cluster-administration/certificates/).
-
-You will end up with the following files (we will use these variables later on)
-
- `CA_CERT`
-  - put in on node where apiserver runs, for example in `/srv/kubernetes/ca.crt`.
- `MASTER_CERT`
-  - signed by CA_CERT
-  - put in on node where apiserver runs, for example in `/srv/kubernetes/server.crt`
- `MASTER_KEY `
-  - put in on node where apiserver runs, for example in `/srv/kubernetes/server.key`
- `KUBELET_CERT`
-  - optional
- `KUBELET_KEY`
-  - optional
-
-#### 자격 증명 준비
-
-The admin user (and any users) need:
-
-  - a token or a password to identify them.
-  - tokens are just long alphanumeric strings, 32 chars for example. See
-    - `TOKEN=$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64 | tr -d "=+/[:space:]" | dd bs=32 count=1 2>/dev/null)`
-
-Your tokens and passwords need to be stored in a file for the apiserver
-to read.  This guide uses `/var/lib/kube-apiserver/known_tokens.csv`.
-The format for this file is described in the [authentication documentation](/docs/reference/access-authn-authz/authentication/#static-token-file).
-
-For distributing credentials to clients, the convention in Kubernetes is to put the credentials
-into a [kubeconfig file](/docs/concepts/cluster-administration/authenticate-across-clusters-kubeconfig/).
-
-The kubeconfig file for the administrator can be created as follows:
-
- - If you have already used Kubernetes with a non-custom cluster (for example, used a Getting Started
-   Guide), you will already have a `$HOME/.kube/config` file.
- - You need to add certs, keys, and the master IP to the kubeconfig file:
-    - If using the firewall-only security option, set the apiserver this way:
-      - `kubectl config set-cluster $CLUSTER_NAME --server=http://$MASTER_IP --insecure-skip-tls-verify=true`
-    - Otherwise, do this to set the apiserver ip, client certs, and user credentials.
-      - `kubectl config set-cluster $CLUSTER_NAME --certificate-authority=$CA_CERT --embed-certs=true --server=https://$MASTER_IP`
-      - `kubectl config set-credentials $USER --client-certificate=$CLI_CERT --client-key=$CLI_KEY --embed-certs=true --token=$TOKEN`
-    - Set your cluster as the default cluster to use:
-      - `kubectl config set-context $CONTEXT_NAME --cluster=$CLUSTER_NAME --user=$USER`
-      - `kubectl config use-context $CONTEXT_NAME`
-
-Next, make a kubeconfig file for the kubelets and kube-proxy.  There are a couple of options for how
-many distinct files to make:
-
-  1. Use the same credential as the admin
-    - This is simplest to setup.
-  1. One token and kubeconfig file for all kubelets, one for all kube-proxy, one for admin.
-    - This mirrors what is done on GCE today
-  1. Different credentials for every kubelet, etc.
-    - We are working on this but all the pieces are not ready yet.
-
-You can make the files by copying the `$HOME/.kube/config` or by using the following template:
-
-```yaml
-apiVersion: v1
-kind: Config
-users:
- name: kubelet
-  user:
-    token: ${KUBELET_TOKEN}
-clusters:
- name: local
-  cluster:
-    certificate-authority: /srv/kubernetes/ca.crt
-contexts:
- context:
-    cluster: local
-    user: kubelet
-  name: service-account-context
-current-context: service-account-context
-```
-
-Put the kubeconfig(s) on every node.  The examples later in this
-guide assume that there are kubeconfigs in `/var/lib/kube-proxy/kubeconfig` and
-`/var/lib/kubelet/kubeconfig`.
-
-## 노드의 기본 소프트웨어 구성 및 설치
-
-This section discusses how to configure machines to be Kubernetes nodes.
-
-You should run three daemons on every node:
-
-  - docker or rkt
-  - kubelet
-  - kube-proxy
-
-You will also need to do assorted other configuration on top of a
-base OS install.
-
-Tip: One possible starting point is to setup a cluster using an existing Getting
-Started Guide.   After getting a cluster running, you can then copy the init.d scripts or systemd unit files from that
-cluster, and then modify them for use on your custom cluster.
-
-### Docker
-
-The minimum required Docker version will vary as the kubelet version changes.  The newest stable release is a good choice.  Kubelet will log a warning and refuse to start pods if the version is too old, so pick a version and try it.
-
-If you previously had Docker installed on a node without setting Kubernetes-specific
-options, you may have a Docker-created bridge and iptables rules.  You may want to remove these
-as follows before proceeding to configure Docker for Kubernetes.
-
-```shell
-iptables -t nat -F
-ip link set docker0 down
-ip link delete docker0
-```
-
-The way you configure docker will depend in whether you have chosen the routable-vip or overlay-network approaches for your network.
-Some suggested docker options:
-
-  - create your own bridge for the per-node CIDR ranges, call it cbr0, and set `--bridge=cbr0` option on docker.
-  - set `--iptables=false` so docker will not manipulate iptables for host-ports (too coarse on older docker versions, may be fixed in newer versions)
-so that kube-proxy can manage iptables instead of docker.
-  - `--ip-masq=false`
-    - if you have setup PodIPs to be routable, then you want this false, otherwise, docker will
-      rewrite the PodIP source-address to a NodeIP.
-    - some environments (for example GCE) still need you to masquerade out-bound traffic when it leaves the cloud environment. This is very environment specific.
-    - if you are using an overlay network, consult those instructions.
-  - `--mtu=`
-    - may be required when using Flannel, because of the extra packet size due to udp encapsulation
-  - `--insecure-registry $CLUSTER_SUBNET`
-    - to connect to a private registry, if you set one up, without using SSL.
-
-You may want to increase the number of open files for docker:
-
-   - `DOCKER_NOFILE=1000000`
-
-Where this config goes depends on your node OS.  For example, GCE's Debian-based distro uses `/etc/default/docker`.
-
-Ensure docker is working correctly on your system before proceeding with the rest of the
-installation, by following examples given in the Docker documentation.
-
-### rkt
-
-[rkt](https://github.com/coreos/rkt) is an alternative to Docker.  You only need to install one of Docker or rkt.
-The minimum version required is [v0.5.6](https://github.com/coreos/rkt/releases/tag/v0.5.6).
-
-[systemd](http://www.freedesktop.org/wiki/Software/systemd/) is required on your node to run rkt.  The
-minimum version required to match rkt v0.5.6 is
-[systemd 215](http://lists.freedesktop.org/archives/systemd-devel/2014-July/020903.html).
-
-[rkt metadata service](https://github.com/coreos/rkt/blob/master/Documentation/networking/overview.md) is also required
-for rkt networking support.  You can start rkt metadata service by using command like
-`sudo systemd-run rkt metadata-service`
-
-Then you need to configure your kubelet with flag:
-
-  - `--container-runtime=rkt`
-
-### kubelet
-
-All nodes should run kubelet.  See [Software Binaries](#software-binaries).
-
-Arguments to consider:
-
-  - If following the HTTPS security approach:
-    - `--kubeconfig=/var/lib/kubelet/kubeconfig`
-  - Otherwise, if taking the firewall-based security approach
-  - `--config=/etc/kubernetes/manifests`
-  - `--cluster-dns=` to the address of the DNS server you will setup (see [Starting Cluster Services](#starting-cluster-services).)
-  - `--cluster-domain=` to the dns domain prefix to use for cluster DNS addresses.
-  - `--docker-root=`
-  - `--root-dir=`
-  - `--pod-cidr=` The CIDR to use for pod IP addresses, only used in standalone mode.  In cluster mode, this is obtained from the master.
-  - `--register-node` (described in [Node](/docs/admin/node/) documentation.)
-
-### kube-proxy
-
-All nodes should run kube-proxy.  (Running kube-proxy on a "master" node is not
-strictly required, but being consistent is easier.)   Obtain a binary as described for
-kubelet.
-
-Arguments to consider:
-
-  - If following the HTTPS security approach:
-    - `--master=https://$MASTER_IP`
-    - `--kubeconfig=/var/lib/kube-proxy/kubeconfig`
-  - Otherwise, if taking the firewall-based security approach
-    - `--master=http://$MASTER_IP`
-
-Note that on some Linux platforms, you may need to manually install the
-`conntrack` package which is a dependency of kube-proxy, or else kube-proxy
-cannot be started successfully.
-
-For more details about debugging kube-proxy problems, refer to
-[Debug Services](/docs/tasks/debug-application-cluster/debug-service/)
-
-### 네트워킹
-
-Each node needs to be allocated its own CIDR range for pod networking.
-Call this `NODE_X_POD_CIDR`.
-
-A bridge called `cbr0` needs to be created on each node.  The bridge is explained
-further in the [networking documentation](/docs/concepts/cluster-administration/networking/).  The bridge itself
-needs an address from `$NODE_X_POD_CIDR` - by convention the first IP.  Call
-this `NODE_X_BRIDGE_ADDR`.  For example, if `NODE_X_POD_CIDR` is `10.0.0.0/16`,
-then `NODE_X_BRIDGE_ADDR` is `10.0.0.1/16`.  NOTE: this retains the `/16` suffix
-because of how this is used later.
-
-If you have turned off Docker's IP masquerading to allow pods to talk to each
-other, then you may need to do masquerading just for destination IPs outside
-the cluster network.  For example:
-
-```shell
-iptables -t nat -A POSTROUTING ! -d ${CLUSTER_SUBNET} -m addrtype ! --dst-type LOCAL -j MASQUERADE
-```
-
-This will rewrite the source address from
-the PodIP to the Node IP for traffic bound outside the cluster, and kernel
-[connection tracking](http://www.iptables.info/en/connection-state.html)
-will ensure that responses destined to the node still reach
-the pod.
-
-NOTE: This is environment specific.  Some environments will not need
-any masquerading at all.  Others, such as GCE, will not allow pod IPs to send
-traffic to the internet, but have no problem with them inside your GCE Project.
-
-### 기타
-
- Enable auto-upgrades for your OS package manager, if desired.
- Configure log rotation for all node components (for example using [logrotate](http://linux.die.net/man/8/logrotate)).
- Setup liveness-monitoring (for example using [supervisord](http://supervisord.org/)).
- Setup volume plugin support (optional)
-  - Install any client binaries for optional volume types, such as `glusterfs-client` for GlusterFS
-    volumes.
-
-### 구성 관리 사용
-
-The previous steps all involved "conventional" system administration techniques for setting up
-machines.  You may want to use a Configuration Management system to automate the node configuration
-process.  There are examples of Ansible, Juju, and CoreOS Cloud Config in the
-various Getting Started Guides.
-
-## 클러스터 부트스트랩
-
-While the basic node services (kubelet, kube-proxy, docker) are typically started and managed using
-traditional system administration/automation approaches, the remaining *master* components of Kubernetes are
-all configured and managed *by Kubernetes*:
-
-  - Their options are specified in a Pod spec (yaml or json) rather than an /etc/init.d file or
-    systemd unit.
-  - They are kept running by Kubernetes rather than by init.
-
-### etcd
-
-You will need to run one or more instances of etcd.
-
-  - Highly available and easy to restore - Run 3 or 5 etcd instances with, their logs written to a directory backed
-    by durable storage (RAID, GCE PD)
-  - Not highly available, but easy to restore - Run one etcd instance, with its log written to a directory backed
-    by durable storage (RAID, GCE PD).
-    
-    {{< note >}}May result in operations outages in case of
-    instance outage. {{< /note >}}
-  - Highly available - Run 3 or 5 etcd instances with non durable storage.
-  
-    {{< note >}}Log can be written to non-durable storage
-    because storage is replicated.{{< /note >}}
-
-See [cluster-troubleshooting](/docs/admin/cluster-troubleshooting/) for more discussion on factors affecting cluster
-availability.
-
-To run an etcd instance:
-
-1. Copy [`cluster/gce/manifests/etcd.manifest`](https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/manifests/etcd.manifest)
-1. Make any modifications needed
-1. Start the pod by putting it into the kubelet manifest directory
-
-### API 서버, 컨트롤러 관리자, 스케줄러
-
-The apiserver, controller manager, and scheduler will each run as a pod on the master node.
-
-For each of these components, the steps to start them running are similar:
-
-1. Start with a provided template for a pod.
-1. Set the `HYPERKUBE_IMAGE` to the values chosen in [Selecting Images](#selecting-images).
-1. Determine which flags are needed for your cluster, using the advice below each template.
-1. Set the flags to be individual strings in the command array (for example $ARGN below)
-1. Start the pod by putting the completed template into the kubelet manifest directory.
-1. Verify that the pod is started.
-
-#### API 서버 파드 템플릿
-
-```json
-{
-  "kind": "Pod",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "kube-apiserver"
-  },
-  "spec": {
-    "hostNetwork": true,
-    "containers": [
-      {
-        "name": "kube-apiserver",
-        "image": "${HYPERKUBE_IMAGE}",
-        "command": [
-          "/hyperkube",
-          "apiserver",
-          "$ARG1",
-          "$ARG2",
-          ...
-          "$ARGN"
-        ],
-        "ports": [
-          {
-            "name": "https",
-            "hostPort": 443,
-            "containerPort": 443
-          },
-          {
-            "name": "local",
-            "hostPort": 8080,
-            "containerPort": 8080
-          }
-        ],
-        "volumeMounts": [
-          {
-            "name": "srvkube",
-            "mountPath": "/srv/kubernetes",
-            "readOnly": true
-          },
-          {
-            "name": "etcssl",
-            "mountPath": "/etc/ssl",
-            "readOnly": true
-          }
-        ],
-        "livenessProbe": {
-          "httpGet": {
-            "scheme": "HTTP",
-            "host": "127.0.0.1",
-            "port": 8080,
-            "path": "/healthz"
-          },
-          "initialDelaySeconds": 15,
-          "timeoutSeconds": 15
-        }
-      }
-    ],
-    "volumes": [
-      {
-        "name": "srvkube",
-        "hostPath": {
-          "path": "/srv/kubernetes"
-        }
-      },
-      {
-        "name": "etcssl",
-        "hostPath": {
-          "path": "/etc/ssl"
-        }
-      }
-    ]
-  }
-}
-```
-
-Here are some apiserver flags you may need to set:
-
- `--cloud-provider=` see [cloud providers](#cloud-providers)
- `--cloud-config=` see [cloud providers](#cloud-providers)
- `--address=${MASTER_IP}` *or* `--bind-address=127.0.0.1` and `--address=127.0.0.1` if you want to run a proxy on the master node.
- `--service-cluster-ip-range=$SERVICE_CLUSTER_IP_RANGE`
- `--etcd-servers=http://127.0.0.1:4001`
- `--tls-cert-file=/srv/kubernetes/server.cert`
- `--tls-private-key-file=/srv/kubernetes/server.key`
- `--enable-admission-plugins=$RECOMMENDED_LIST`
-  - See [admission controllers](/docs/reference/access-authn-authz/admission-controllers/) for recommended arguments.
- `--allow-privileged=true`, only if you trust your cluster user to run pods as root.
-
-If you are following the firewall-only security approach, then use these arguments:
-
- `--token-auth-file=/dev/null`
- `--insecure-bind-address=$MASTER_IP`
- `--advertise-address=$MASTER_IP`
-
-If you are using the HTTPS approach, then set:
-
- `--client-ca-file=/srv/kubernetes/ca.crt`
- `--token-auth-file=/srv/kubernetes/known_tokens.csv`
- `--basic-auth-file=/srv/kubernetes/basic_auth.csv`
-
-This pod mounts several node file system directories using the  `hostPath` volumes.  Their purposes are:
-
- The `/etc/ssl` mount allows the apiserver to find the SSL root certs so it can
-  authenticate external services, such as a cloud provider.
-  - This is not required if you do not use a cloud provider (bare-metal for example).
- The `/srv/kubernetes` mount allows the apiserver to read certs and credentials stored on the
-  node disk.  These could instead be stored on a persistent disk, such as a GCE PD, or baked into the image.
- Optionally, you may want to mount `/var/log` as well and redirect output there (not shown in template).
-  - Do this if you prefer your logs to be accessible from the root filesystem with tools like journalctl.
-
-*TODO* document proxy-ssh setup.
-
-##### 클라우드 공급자
-
-Apiserver supports several cloud providers.
-
- options for `--cloud-provider` flag are `aws`, `azure`, `cloudstack`, `fake`, `gce`, `mesos`, `openstack`, `ovirt`, `rackspace`, `vsphere`, or unset.
- unset used for bare metal setups.
- support for new IaaS is added by contributing code [here](https://releases.k8s.io/{{< param "githubbranch" >}}/pkg/cloudprovider/providers)
-
-Some cloud providers require a config file. If so, you need to put config file into apiserver image or mount through hostPath.
-
- `--cloud-config=` set if cloud provider requires a config file.
- Used by `aws`, `gce`, `mesos`, `openstack`, `ovirt` and `rackspace`.
- You must put config file into apiserver image or mount through hostPath.
- Cloud config file syntax is [Gcfg](https://code.google.com/p/gcfg/).
- AWS format defined by type [AWSCloudConfig](https://releases.k8s.io/{{< param "githubbranch" >}}/pkg/cloudprovider/providers/aws/aws.go)
- There is a similar type in the corresponding file for other cloud providers.
-
-#### 스케줄러 파드 템플릿
-
-Complete this template for the scheduler pod:
-
-```json
-{
-  "kind": "Pod",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "kube-scheduler"
-  },
-  "spec": {
-    "hostNetwork": true,
-    "containers": [
-      {
-        "name": "kube-scheduler",
-        "image": "$HYPERKUBE_IMAGE",
-        "command": [
-          "/hyperkube",
-          "scheduler",
-          "--master=127.0.0.1:8080",
-          "$SCHEDULER_FLAG1",
-          ...
-          "$SCHEDULER_FLAGN"
-        ],
-        "livenessProbe": {
-          "httpGet": {
-            "scheme": "HTTP",
-            "host": "127.0.0.1",
-            "port": 10251,
-            "path": "/healthz"
-          },
-          "initialDelaySeconds": 15,
-          "timeoutSeconds": 15
-        }
-      }
-    ]
-  }
-}
-```
-
-Typically, no additional flags are required for the scheduler.
-
-Optionally, you may want to mount `/var/log` as well and redirect output there.
-
-#### 컨트롤러 관리자 템플릿
-
-Template for controller manager pod:
-
-```json
-{
-  "kind": "Pod",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "kube-controller-manager"
-  },
-  "spec": {
-    "hostNetwork": true,
-    "containers": [
-      {
-        "name": "kube-controller-manager",
-        "image": "$HYPERKUBE_IMAGE",
-        "command": [
-          "/hyperkube",
-          "controller-manager",
-          "$CNTRLMNGR_FLAG1",
-          ...
-          "$CNTRLMNGR_FLAGN"
-        ],
-        "volumeMounts": [
-          {
-            "name": "srvkube",
-            "mountPath": "/srv/kubernetes",
-            "readOnly": true
-          },
-          {
-            "name": "etcssl",
-            "mountPath": "/etc/ssl",
-            "readOnly": true
-          }
-        ],
-        "livenessProbe": {
-          "httpGet": {
-            "scheme": "HTTP",
-            "host": "127.0.0.1",
-            "port": 10252,
-            "path": "/healthz"
-          },
-          "initialDelaySeconds": 15,
-          "timeoutSeconds": 15
-        }
-      }
-    ],
-    "volumes": [
-      {
-        "name": "srvkube",
-        "hostPath": {
-          "path": "/srv/kubernetes"
-        }
-      },
-      {
-        "name": "etcssl",
-        "hostPath": {
-          "path": "/etc/ssl"
-        }
-      }
-    ]
-  }
-}
-```
-
-Flags to consider using with controller manager:
-
- - `--cluster-cidr=`, the CIDR range for pods in cluster.
- - `--allocate-node-cidrs=`, if you are using `--cloud-provider=`, allocate and set the CIDRs for pods on the cloud provider.
- - `--cloud-provider=` and `--cloud-config` as described in apiserver section.
- - `--service-account-private-key-file=/srv/kubernetes/server.key`, used by the [service account](/docs/user-guide/service-accounts) feature.
- - `--master=127.0.0.1:8080`
-
-#### API 서버, 스케줄러, 컨트롤러 관리자 시작 및 확인 
-
-Place each completed pod template into the kubelet config dir
-(whatever `--config=` argument of kubelet is set to, typically
-`/etc/kubernetes/manifests`).  The order does not matter: scheduler and
-controller manager will retry reaching the apiserver until it is up.
-
-Use `ps` or `docker ps` to verify that each process has started.  For example, verify that kubelet has started a container for the apiserver like this:
-
-```shell
-$ sudo docker ps | grep apiserver
-5783290746d5        k8s.gcr.io/kube-apiserver:e36bf367342b5a80d7467fd7611ad873            "/bin/sh -c '/usr/lo'"    10 seconds ago      Up 9 seconds                              k8s_kube-apiserver.feb145e7_kube-apiserver-kubernetes-master_default_eaebc600cf80dae59902b44225f2fc0a_225a4695
-```
-
-Then try to connect to the apiserver:
-
-```shell
-$ echo $(curl -s http://localhost:8080/healthz)
-ok
-$ curl -s http://localhost:8080/api
-{
-  "versions": [
-    "v1"
-  ]
-}
-```
-
-If you have selected the `--register-node=true` option for kubelets, they will now begin self-registering with the apiserver.
-You should soon be able to see all your nodes by running the `kubectl get nodes` command.
-Otherwise, you will need to manually create node objects.
-
-### 클러스터 서비스 시작
-
-You will want to complete your Kubernetes clusters by adding cluster-wide
-services.  These are sometimes called *addons*, and [an overview
-of their purpose is in the admin guide](/docs/admin/cluster-components/#addons).
-
-Notes for setting up each cluster service are given below:
-
-* Cluster DNS:
-  * Required for many Kubernetes examples
-  * [Setup instructions](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/dns/)
-  * [Admin Guide](/docs/concepts/services-networking/dns-pod-service/)
-* Cluster-level Logging
-  * [Cluster-level Logging Overview](/docs/user-guide/logging/overview/)
-  * [Cluster-level Logging with Elasticsearch](/docs/user-guide/logging/elasticsearch/)
-  * [Cluster-level Logging with Stackdriver Logging](/docs/user-guide/logging/stackdriver/)
-* Container Resource Monitoring
-  * [Setup instructions](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/cluster-monitoring/)
-* GUI
-  * [Setup instructions](https://github.com/kubernetes/dashboard)
-
-## 문제 해결
-
-### validate-cluster 명령 실행
-
-`cluster/validate-cluster.sh` is used by `cluster/kube-up.sh` to determine if
-the cluster start succeeded.
-
-Example usage and output:
-
-```shell
-KUBECTL_PATH=$(which kubectl) NUM_NODES=3 KUBERNETES_PROVIDER=local cluster/validate-cluster.sh
-Found 3 node(s).
-NAME                    STATUS    AGE     VERSION
-node1.local             Ready     1h      v1.6.9+a3d1dfa6f4335
-node2.local             Ready     1h      v1.6.9+a3d1dfa6f4335
-node3.local             Ready     1h      v1.6.9+a3d1dfa6f4335
-Validate output:
-NAME                 STATUS    MESSAGE              ERROR
-controller-manager   Healthy   ok
-scheduler            Healthy   ok
-etcd-1               Healthy   {"health": "true"}
-etcd-2               Healthy   {"health": "true"}
-etcd-0               Healthy   {"health": "true"}
-Cluster validation succeeded
-```
-
-### 파드와 서비스 검사
-
-Try to run through the "Inspect your cluster" section in one of the other Getting Started Guides, such as [GCE](/docs/setup/turnkey/gce/#inspect-your-cluster).
-You should see some services.  You should also see "mirror pods" for the apiserver, scheduler and controller-manager, plus any add-ons you started.
-
-### 예제 실행하기
-
-At this point you should be able to run through one of the basic examples, such as the [nginx example](/examples/application/deployment.yaml).
-
-### 적합성 테스트 실행
-
-You may want to try to run the [Conformance test](http://releases.k8s.io/{{< param "githubbranch" >}}/test/e2e_node/conformance/run_test.sh).  Any failures may give a hint as to areas that need more attention.
-
-### 네트워킹
-
-The nodes must be able to connect to each other using their private IP. Verify this by
-pinging or SSH-ing from one node to another.
-
-### 도움말 얻기
-
-If you run into trouble, see the section on [troubleshooting](/docs/setup/turnkey/gce/#troubleshooting), post to the
-[Kubernetes Forum](https://discuss.kubernetes.io), or come ask questions on [Slack](/docs/troubleshooting#slack).
-
-## 지원 레벨
-
-
-IaaS Provider        | Config. Mgmt | OS     | Networking  | Docs                                              | Conforms | Support Level
-------------------- | ------------ | ------ | ----------  | ---------------------------------------------     | ---------| ----------------------------
-any                  | any          | any    | any         | [docs](/docs/getting-started-guides/scratch/)                                |          | Community ([@erictune](https://github.com/erictune))
-
-
-For support level information on all solutions, see the [Table of solutions](/docs/getting-started-guides/#table-of-solutions/) chart.
@@ -52,7 +52,9 @@ index.php는 CPU 과부하 연산을 수행한다.
 첫 번째 단계로, 실행 중인 이미지의 디플로이먼트를 시작하고 서비스로 노출시킨다.

 ```shell
-$ kubectl run php-apache --image=k8s.gcr.io/hpa-example --requests=cpu=200m --expose --port=80
+kubectl run php-apache --image=k8s.gcr.io/hpa-example --requests=cpu=200m --expose --port=80
+```
+```
 service/php-apache created
 deployment.apps/php-apache created
 ```
@@ -63,13 +65,18 @@ deployment.apps/php-apache created
 간단히 얘기하면, HPA는 (디플로이먼트를 통한) 평균 CPU 사용량을 50%로 유지하기 위하여 레플리카의 개수를 늘리고 줄인다. ([kubectl run](https://github.com/kubernetes/kubernetes/blob/{{< param "githubbranch" >}}/docs/user-guide/kubectl/kubectl_run.md)으로 각 파드는 200 밀리코어까지 요청할 수 있고, 따라서 여기서 말하는 평균 CPU 사용은 100 밀리코어를 말한다.) 이에 대한 자세한 알고리즘은 [여기](https://git.k8s.io/community/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md#autoscaling-algorithm)를 참고하기 바란다.

 ```shell
-$ kubectl autoscale deployment php-apache --cpu-percent=50 --min=1 --max=10
+kubectl autoscale deployment php-apache --cpu-percent=50 --min=1 --max=10
+```
+```
 horizontalpodautoscaler.autoscaling/php-apache autoscaled
 ```

 실행 중인 오토스케일러의 현재 상태를 확인해본다.
+
 ```shell
-$ kubectl get hpa
+kubectl get hpa
+```
+```
 NAME         REFERENCE                     TARGET    MINPODS   MAXPODS   REPLICAS   AGE
 php-apache   Deployment/php-apache/scale   0% / 50%  1         10        1          18s

@@ -83,17 +90,19 @@ php-apache   Deployment/php-apache/scale   0% / 50%  1         10        1


 ```shell
-$ kubectl run -i --tty load-generator --image=busybox /bin/sh
+kubectl run -i --tty load-generator --image=busybox /bin/sh

 Hit enter for command prompt

-$ while true; do wget -q -O- http://php-apache.default.svc.cluster.local; done
+while true; do wget -q -O- http://php-apache.default.svc.cluster.local; done
 ```

 실행 후, 약 1분 정도 후에 CPU 부하가 올라가는 것을 볼 수 있다.

 ```shell
-$ kubectl get hpa
+kubectl get hpa
+```
+```
 NAME         REFERENCE                     TARGET      CURRENT   MINPODS   MAXPODS   REPLICAS   AGE
 php-apache   Deployment/php-apache/scale   305% / 50%  305%      1         10        1          3m

@@ -102,7 +111,9 @@ php-apache   Deployment/php-apache/scale   305% / 50%  305%      1         10
 CPU 소비가 305%까지 증가하였다. 결과적으로, 디플로이먼트의 레플리카 개수는 7개까지 증가하였다.

 ```shell
-$ kubectl get deployment php-apache
+kubectl get deployment php-apache
+```
+```
 NAME         DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
 php-apache   7         7         7            7           19m
 ```
@@ -117,11 +128,17 @@ php-apache   7         7         7            7           19m
 `busybox` 컨테이너를 띄운 터미널에서, `<Ctrl> + C`로 부하 발생을 중단시킨다. 그런 다음 (몇 분 후에) 결과를 확인한다.

 ```shell
-$ kubectl get hpa
+kubectl get hpa
+```
+```
 NAME         REFERENCE                     TARGET       MINPODS   MAXPODS   REPLICAS   AGE
 php-apache   Deployment/php-apache/scale   0% / 50%     1         10        1          11m
+```

-$ kubectl get deployment php-apache
+```shell
+kubectl get deployment php-apache
+```
+```
 NAME         DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
 php-apache   1         1         1            1           27m
 ```
@@ -143,7 +160,7 @@ CPU 사용량은 0으로 떨어졌고, HPA는 레플리카의 개수를 1로 낮
 첫 번째로, `autoscaling/v2beta2` 형식으로 HorizontalPodAutoscaler YAML 파일을 생성한다.

 ```shell
-$ kubectl get hpa.v2beta2.autoscaling -o yaml > /tmp/hpa-v2.yaml
+kubectl get hpa.v2beta2.autoscaling -o yaml > /tmp/hpa-v2.yaml
 ```

 에디터로 `/tmp/hpa-v2.yaml` 파일을 열면, 다음과 같은 YAML을 확인할 수 있다.
@@ -332,7 +349,9 @@ HorizontalPodAutoscaler의 `autoscaling/v2beta2` 형식을 사용하면, Horizon
 이 조건은 `status.conditions`에 나타난다. HorizontalPodAutoscaler에 영향을 주는 조건을 보기 위해 `kubectl describe hpa`를 사용할 수 있다.

 ```shell
-$ kubectl describe hpa cm-test
+kubectl describe hpa cm-test
+```
+```shell
 Name:                           cm-test
 Namespace:                      prom
 Labels:                         <none>
@@ -370,7 +389,9 @@ HorizontalPodAutoscaler를 생성하기 위해 `kubectl autoscale` 명령어를
 다음 명령어를 실행하여 오토스케일러를 생성할 것이다.

 ```shell
-$ kubectl create -f https://k8s.io/examples/application/hpa/php-apache.yaml
+kubectl create -f https://k8s.io/examples/application/hpa/php-apache.yaml
+```
+```
 horizontalpodautoscaler.autoscaling/php-apache created
 ```

@@ -115,4 +115,19 @@ Windows에 Minikube를 수동으로 설치하려면, [`minikube-windows-amd64`](

 {{% /capture %}}

+## 새롭게 시작하기 위해 모두 정리하기

+이전에 minikube를 설치한 적이 있다면, 실행한다.
+```shell
+minikube start
+```
+
+이 커맨드는 에러를 리턴한다.
+```shell
+machine does not exist
+```
+
+구성 파일을 삭제해야 한다.
+```shell
+rm -rf ~/.minikube
+```
@@ -40,7 +40,7 @@ content_template: templates/concept

 ## 상태 유지가 필요한(stateful) 애플리케이션

-* [StatefulSet Basics](/docs/tutorials/stateful-application/basic-stateful-set/)
+* [스테이트풀셋 기본](/docs/tutorials/stateful-application/basic-stateful-set/)

 * [Example: WordPress and MySQL with Persistent Volumes](/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/)

@@ -36,8 +36,8 @@ weight: 10

                <p>애플리케이션 인스턴스가 생성되면, 쿠버네티스 디플로이먼트 컨트롤러는 지속적으로 이들 인스턴스를
                    모니터링한다. 인스턴스를 구동 중인 노드가 다운되거나 삭제되면, 디플로이먼트 컨트롤러가 인스턴스를
-                    교체시켜준다. <b>이렇게 머신의 장애나 정비에 대응할 수 있는 자동 복구(self-healing) 메커니즘을
-                        제공한다.</b></p>
+                    클러스터 내부의 다른 노드의 인스턴스로 교체시켜준다.<b>이렇게 머신의 장애나 정비에 대응할 수 있는 자동 복구(self-healing) 메커니즘을
+                    제공한다.</b></p>

                <p>오케스트레이션 기능이 없던 환경에서는, 설치 스크립트가 애플리케이션을 시작하는데 종종 사용되곤
                    했지만, 머신의 장애가 발생한 경우 복구를 해주지는 않았다. 쿠버네티스 디플로이먼트는 애플리케이션
@@ -26,10 +26,9 @@ weight: 10

            <div class="col-md-8">
                <h3>애플리케이션을 스케일하기</h3>
-
-                <p>지난 모듈에서 <a
-                        href="/docs/concepts/workloads/controllers/deployment/"> 디플로이먼트</a>,
-                    를 만들고 <a href="/docs/concepts/services-networking/service/">서비스</a>를
+                
+                <p>지난 모듈에서 <a href="/docs/concepts/workloads/controllers/deployment/"> 디플로이먼트</a>를 만들고,
+                    <a href="/docs/concepts/services-networking/service/">서비스</a>를
                    통해서 디플로이먼트를 외부에 노출시켜 봤다. 해당 디플로이먼트는 애플리케이션을 구동하기 위해 단
                    하나의 파드(Pod)만을 생성했었다. 트래픽이 증가하면, 사용자 요청에 맞추어 애플리케이션의 규모를
                    조정할 필요가 있다.</p>
@@ -133,4 +132,4 @@ weight: 10
 </div>

 </body>
-</html>
+</html>
@@ -11,7 +11,7 @@ content_template: templates/concept

 {{% capture body %}}

-* [Certified Kubernetes Administrator 준비 과정 (LinuxAcademy.com)](https://linuxacademy.com/linux/training/course/name/certified-kubernetes-administrator-preparation-course)
+* [Certified Kubernetes Administrator 준비 과정 (Linux Academy)](https://linuxacademy.com/linux/training/course/name/certified-kubernetes-administrator-preparation-course)

 * [Certified Kubernetes Application Developer 준비 과정 및 모의 시험 (KodeKloud.com)](https://kodekloud.com/p/kubernetes-certification-course)

@@ -21,6 +21,8 @@ content_template: templates/concept

 * [쿠버네티스 시작하기 (Pluralsight)](https://www.pluralsight.com/courses/getting-started-kubernetes)

+* [Getting Started with Kubernetes Clusters on OCI Oracle Kubernetes Engine (OKE) (Learning Library)](https://apexapps.oracle.com/pls/apex/f?p=44785:50:0:::50:P50_EVENT_ID,P50_COURSE_ID:5935,256)
+
 * [쿠버네티스 소개 및 실습 (Instruqt)](https://play.instruqt.com/public/topics/getting-started-with-kubernetes)

 * [IBM 클라우드: 쿠버네티스로 마이크로서비스(Microservices) 배포 (Coursera)](https://www.coursera.org/learn/deploy-micro-kube-ibm-cloud)
@@ -33,7 +35,7 @@ content_template: templates/concept

 * [Kubernetes Quick Start (Linux Academy)] (https://linuxacademy.com/linux/training/course/name/kubernetes-quick-start)

-* [쿠버네티스 심화 학습 (LinuxAcademy.com)](https://linuxacademy.com/linux/training/course/name/kubernetes-the-hard-way)
+* [쿠버네티스 심화 학습 (Linux Academy)](https://linuxacademy.com/linux/training/course/name/kubernetes-the-hard-way)

 * [대화식 실습 시나리오를 사용하여 쿠버네티스 배우기 (Katacoda)](https://www.katacoda.com/courses/kubernetes/)

@@ -42,5 +44,4 @@ content_template: templates/concept
 * [쿠버네티스와 확장 가능한 마이크로서비스(Microservices) (Udacity)](https://www.udacity.com/course/scalable-microservices-with-kubernetes--ud615)

 * [Self-paced Kubernetes online course (Learnk8s Academy)](https://learnk8s.io/academy)
-
 {{% /capture %}}
@@ -0,0 +1,5 @@
+---
+title: "상태 유지가 필요한(stateful) 애플리케이션"
+weight: 50
+---
+
@@ -154,7 +154,7 @@ web-1
 확인할 수 있다.

 ```shell
-kubectl run -i --tty --image busybox dns-test --restart=Never --rm /bin/sh 
+kubectl run -i --tty --image busybox:1.28 dns-test --restart=Never --rm  
 nslookup web-0.nginx
 Server:    10.0.0.10
 Address 1: 10.0.0.10 kube-dns.kube-system.svc.cluster.local
@@ -212,7 +212,7 @@ for i in 0 1; do kubectl exec web-$i -- sh -c 'hostname'; done
 web-0
 web-1

-kubectl run -i --tty --image busybox dns-test --restart=Never --rm /bin/sh 
+kubectl run -i --tty --image busybox:1.28 dns-test --restart=Never --rm /bin/sh 
 nslookup web-0.nginx
 Server:    10.0.0.10
 Address 1: 10.0.0.10 kube-dns.kube-system.svc.cluster.local
@@ -223,7 +223,7 @@ Google Compute Engine 또는 Google Kubernetes Engine과 같은 일부 클라우

      ```
      NAME           TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)        AGE
-      frontend       ClusterIP   10.0.0.112   <none>       80:31323/TCP   6s
+      frontend       NodePort    10.0.0.112   <none>       80:31323/TCP   6s
      kubernetes     ClusterIP   10.0.0.1     <none>        443/TCP        4m
      redis-master   ClusterIP   10.0.0.151   <none>        6379/TCP       2m
      redis-slave    ClusterIP   10.0.0.223   <none>        6379/TCP       1m
@@ -0,0 +1,3 @@
+---
+headless: true
+---
@@ -1,14 +1,14 @@
 ---
 title: "生产级别的容器编排系统"
 abstract: "自动化的容器部署、扩展和管理"
-cid: "home"
+cid: home
 ---

 <section id="oceanNodes">
    <main>
        <div class="image-wrapper"><img src="https://d33wubrfki0l68.cloudfront.net/1567471e7c58dc9b7d9c65dcd54e60cbf5870daa/da576/_common-resources/images/flower.png" alt="images/flower.png"></div>
        <div class="content">
-            
+
            <h3><a href="/docs/concepts/overview/what-is-kubernetes/">Kubernetes</a> 是用于自动部署，扩展和管理容器化应用程序的开源系统。</h3>
            <p>它将组成应用程序的容器组合成逻辑单元，以便于管理和服务发现，Kubernetes 构建在 <a href="http://queue.acm.org/detail.cfm?id=2898444"> Google 15 年生产环境经验</a>基础之上,并结合来自社区的最佳创意和实践。</p>
        </div>
@@ -16,7 +16,7 @@ cid: "home"
    <main>
        <div class="image-wrapper"><img src="https://d33wubrfki0l68.cloudfront.net/33a12d8be0bc50be4738443101616e968c7afb8f/2c641/_common-resources/images/scalable.png" alt="images/scalable.png"></div>
        <div class="content">
-            
+
            <h4>全球规模</h4>
            <p>基于允许 Google 每周运行数十亿个容器的原则进行设计，Kubernetes 可以在不增加您的运维团队的情况下进行弹性扩展。</p>
        </div>
@@ -24,7 +24,7 @@ cid: "home"
    <main>
        <div class="image-wrapper"><img src="https://d33wubrfki0l68.cloudfront.net/dbc75a944a909b2d52bf24ad06d485eca12af892/4fb42/_common-resources/images/blocks.png" alt="images/blocks.png"></div>
        <div class="content">
-            
+
            <h4>永不过时</h4>
            <p>无论您应用运行在本地还是运行于全球任何地域，Kubernetes 的灵活性都可以随着您的需求复杂度不断增加，还可以持续、轻松地对外提供服务。</p>
        </div>
@@ -32,7 +32,7 @@ cid: "home"
    <main>
        <div class="image-wrapper"><img src="https://d33wubrfki0l68.cloudfront.net/bc2e475ac5fee0199eb3f4a0879cd559e8929f3a/4a628/_common-resources/images/suitcase.png" alt="images/suitcase.png"></div>
        <div class="content">
-            
+
            <h4>随处运行</h4>
            <p>Kubernetes 是开源的，可以让您自由地部署在企业内部，私有云、混合云或公有云基础架构，使您轻松将应用迁移至任何位置。</p>
        </div>
@@ -40,7 +40,7 @@ cid: "home"
 </section>
 <section id="video">
    <div class="light-text">
-        
+
        <h2>Kubernetes: 最后&hellip; 它是真正的云平台</h2>
        <p>Box 的联合创始人和服务架构师 Sam Ghods 发表了热情洋溢的演讲，随着使用 Kubernetes，我们首次有一个通用接口，可以建立真正的部署工具。</p>
        <button id="desktopShowVideoButton" onclick="kub.showVideo()">观看视频</button>
@@ -49,35 +49,35 @@ cid: "home"
 </section>
 <section id="features">
    <main>
-        
+
        <h3 class="center">Kubernetes 特性</h3>
        <div class="feature-box">
            <div>
-                
+
                <h4><a href="/docs/concepts/configuration/manage-compute-resources-container/">自动包装</a></h4>
                <p>根据资源需求和其他约束自动放置容器，同时不会牺牲可用性，混合关键和最大努力的工作负载，以提高资源利用率并节省更多资源。</p>
            </div>
            <div>
-                
+
                <h4><a href="/docs/concepts/workloads/controllers/replicationcontroller/#what-is-a-replicationcontroller">自我修复</a></h4>
                <p>重新启动失败的容器，在节点不可用时，替换和重新调度节点上的容器，对用户定义的健康检查不响应的容器会被中止，并且在容器准备好服务之前不会把其向客户端广播。</p>
            </div>
        </div>
        <div class="feature-box">
            <div>
-                
+
                <h4><a href="/docs/tasks/run-application/horizontal-pod-autoscale/">横向缩放</a></h4>
                <p>使用简单的命令或 UI，或者根据 CPU 的使用情况自动调整应用程序副本数。</p>
            </div>
            <div>
-                
+
                <h4><a href="/docs/concepts/services-networking/service/">服务发现和负载均衡</a></h4>
                <p>不需要修改您的应用程序来使用不熟悉的服务发现机制，Kubernetes 为容器提供了自己的 IP 地址和一组容器的单个 DNS 名称，并可以在它们之间进行负载均衡。</p>
            </div>
        </div>
        <div class="feature-box">
            <div>
-                
+
                <h4><a href="/docs/concepts/workloads/controllers/deployment/#what-is-a-deployment">自动部署和回滚</a></h4>
                <p>Kubernetes 逐渐部署对应用程序或其配置的更改，同时监视应用程序运行状况，以确保它不会同时终止所有实例。 如果出现问题，Kubernetes会为您恢复更改，利用日益增长的部署解决方案的生态系统。</p>
            </div>
@@ -101,7 +101,7 @@ cid: "home"
 </section>
 <section id="talkToUs">
 <main>
-    
+
    <h3>实例探究</h3>
    <div id="caseStudiesWrapper">
        <div>
@@ -121,29 +121,29 @@ cid: "home"
            <a href="https://www.youtube.com/watch?v=6XGUTu3WhBw">观看视频</a>
        </div>
    </div>
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
-    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    <h5 style="text-align: center"><a href="/case-studies/" style="color: #3371E3; font-weight: 400">探究所有的案例</a></h5>
 </main>
 </section>
@@ -0,0 +1,27 @@
+---
+
+title: " Kubernetes 采集视频 "
+date: 2015-03-23
+slug: kubernetes-gathering-videos
+url: /blog/2015/03/Kubernetes-Gathering-Videos
+---
+
+<!--
+---
+
+title: " Kubernetes Gathering Videos "
+date: 2015-03-23
+slug: kubernetes-gathering-videos
+url: /blog/2015/03/Kubernetes-Gathering-Videos
+---
+-->
+
+<!--
+If you missed the Kubernetes Gathering in SF last month, fear not! Here are the videos from the evening presentations organized into a playlist on YouTube
+
+[![Kubernetes Gathering](https://img.youtube.com/vi/q8lGZCKktYo/0.jpg)](https://www.youtube.com/playlist?list=PL69nYSiGNLP2FBVvSLHpJE8_6hRHW8Kxe)
+-->
+
+如果你错过了上个月在旧金山举行的 Kubernetes 大会，不要害怕!以下是在 YouTube 上组织成播放列表的晚间演示文稿中的视频。
+
+[![Kubernetes Gathering](https://img.youtube.com/vi/q8lGZCKktYo/0.jpg)](https://www.youtube.com/playlist?list=PL69nYSiGNLP2FBVvSLHpJE8_6hRHW8Kxe)
@@ -0,0 +1,186 @@
+---
+title: " Kubernetes 社区每周聚会笔记 - 2015年3月27日 "
+date: 2015-03-28
+slug: weekly-kubernetes-community-hangout
+url: /blog/2015/03/Weekly-Kubernetes-Community-Hangout
+---
+
+<!--
+---
+title: " Weekly Kubernetes Community Hangout Notes - March 27 2015 "
+date: 2015-03-28
+slug: weekly-kubernetes-community-hangout
+url: /blog/2015/03/Weekly-Kubernetes-Community-Hangout
+---
+-->
+
+<!--
+Every week the Kubernetes contributing community meet virtually over Google Hangouts. We want anyone who's interested to know what's discussed in this forum.
+-->
+每个星期，Kubernetes 贡献者社区几乎都会在谷歌 Hangouts 上聚会。我们希望任何对此感兴趣的人都能了解这个论坛的讨论内容。
+
+<!--
+Agenda:
+-->
+日程安排：
+
+<!--
+
+\- Andy - demo remote execution and port forwarding
+
+\- Quinton - Cluster federation - Postponed
+
+\- Clayton - UI code sharing and collaboration around Kubernetes
+
+-->
+
+\- Andy - 演示远程执行和端口转发
+
+\- Quinton - 联邦集群 - 延迟
+
+\- Clayton - 围绕 Kubernetes 的 UI 代码共享和协作
+
+<!--
+Notes from meeting:
+-->
+从会议指出：
+
+<!--
+
+1\. Andy from RedHat:
+
+-->
+
+1\. Andy 从 RedHat：
+
+<!--
+
+* Demo remote execution
+
+-->
+
+* 演示远程执行
+
+<!--
+
+    * kubectl exec -p $POD -- $CMD
+
+    * Makes a connection to the master as proxy, figures out which node the pod is on, proxies connection to kubelet, which does the interesting bit.  via nsenter.
+
+    * Multiplexed streaming over HTTP using SPDY
+
+    * Also interactive mode:
+
+    * Assumes first container.  Can use -c $CONTAINER to pick a particular one.
+
+    * If have gdb pre-installed in container, then can interactively attach it to running process
+
+        * backtrace, symbol tbles, print, etc.  Most things you can do with gdb.
+
+    * Can also with careful flag crafting run rsync over this or set up sshd inside container.
+
+    * Some feedback via chat:
+    
+-->
+
+    * kubectl exec -p $POD -- $CMD
+
+    * 作为代理与主机建立连接，找出 pod 所在的节点，代理与 kubelet 的连接，这一点很有趣。通过 nsenter。
+
+    * 使用 SPDY 通过 HTTP 进行多路复用流式传输
+
+    * 还有互动模式：
+
+    * 假设第一个容器，可以使用 -c $CONTAINER 一个特定的。
+
+    * 如果在容器中预先安装了 gdb，则可以交互地将其附加到正在运行的进程中
+
+        * backtrace、symbol tbles、print 等。  使用gdb可以做的大多数事情。
+
+    * 也可以用精心制作的参数在上面运行 rsync 或者在容器内设置 sshd。
+
+    * 一些聊天反馈：
+
+<!--
+
+* Andy also demoed port forwarding
+* nsenter vs. docker exec
+
+-->
+
+* Andy 还演示了端口转发
+* nnsenter 与 docker exec
+
+<!--
+
+    * want to inject a binary under control of the host, similar to pre-start hooks
+
+    * socat, nsenter, whatever the pre-start hook needs
+    
+-->
+
+    * 想要在主机的控制下注入二进制文件，类似于预启动钩子
+
+    * socat、nsenter，任何预启动钩子需要的
+
+<!--
+
+* would be nice to blog post on this
+* version of nginx in wheezy is too old to support needed master-proxy functionality
+
+-->
+
+* 如果能在博客上发表这方面的文章就太好了
+* wheezy 中的 nginx 版本太旧，无法支持所需的主代理功能
+
+<!--
+
+2\. Clayton: where are we wrt a community organization for e.g. kubernetes UI components?
+
+* google-containers-ui IRC channel, mailing list.
+* Tim: google-containers prefix is historical, should just do "kubernetes-ui"
+* also want to put design resources in, and bower expects its own repo.
+* General agreement
+
+-->
+
+2\. Clayton: 我们的社区组织在哪里，例如 kubernetes UI 组件？
+
+* google-containers-ui IRC 频道，邮件列表。
+* Tim: google-containers 前缀是历史的，应该只做 "kubernetes-ui"
+* 也希望将设计资源投入使用，并且 bower 期望自己的仓库。
+* 通用协议
+
+<!--
+
+3\. Brian Grant:
+
+* Testing v1beta3, getting that ready to go in.
+* Paul working on changes to commandline stuff.
+* Early to mid next week, try to enable v1beta3 by default?
+* For any other changes, file issue and CC thockin.
+
+-->
+
+3\. Brian Grant:
+
+* 测试 v1beta3，准备进入。
+* Paul 力于改变命令行的内容。
+* 下周初至中旬，尝试默认启用v1beta3 ?
+* 对于任何其他更改，请发出文件并抄送 thockin。
+
+<!--
+
+4\. General consensus that 30 minutes is better than 60
+
+-->
+
+4\. 一般认为30分钟比60分钟好
+
+<!--
+
+* Shouldn't artificially try to extend just to fill time.
+
+-->
+
+* 不应该为了填满时间而人为地延长。
@@ -0,0 +1,62 @@
+---
+title: 欢迎来到 Kubernetes 博客!
+date: 2015-03-20
+slug: welcome-to-kubernetes-blog
+url: /blog/2015/03/Welcome-To-Kubernetes-Blog
+---
+
+<!--
+---
+title: Welcome to the Kubernetes Blog! 
+date: 2015-03-20
+slug: welcome-to-kubernetes-blog
+url: /blog/2015/03/Welcome-To-Kubernetes-Blog
+---
+-->
+
+<!--
+Welcome to the new Kubernetes Blog. Follow this blog to learn about the Kubernetes Open Source project. We plan to post release notes, how-to articles, events, and maybe even some off topic fun here from time to time.
+-->
+欢迎来到新的 Kubernetes 博客。关注此博客，了解 Kubernetes 开源项目。我们计划不时发布发布说明，操作方法文章，活动，甚至一些非常有趣的话题。
+
+<!--
+If you are using Kubernetes or contributing to the project and would like to do a guest post, [please let me know](mailto:kitm@google.com).
+-->
+如果您正在使用 Kubernetes 或为该项目做出贡献并想要发帖子，[请告诉我](mailto:kitm@google.com)。
+
+<!--
+To start things off, here's a roundup of recent Kubernetes posts from other sites:
+-->
+首先，以下是 Kubernetes 最近在其他网站上发布的文章摘要：
+
+<!--
+- [Scaling MySQL in the cloud with Vitess and Kubernetes](http://googlecloudplatform.blogspot.com/2015/03/scaling-MySQL-in-the-cloud-with-Vitess-and-Kubernetes.html)
+- [Container Clusters on VMs](http://googlecloudplatform.blogspot.com/2015/02/container-clusters-on-vms.html)
+- [Everything you wanted to know about Kubernetes but were afraid to ask](http://googlecloudplatform.blogspot.com/2015/01/everything-you-wanted-to-know-about-Kubernetes-but-were-afraid-to-ask.html)
+- [What makes a container cluster?](http://googlecloudplatform.blogspot.com/2015/01/what-makes-a-container-cluster.html)
+- [Integrating OpenStack and Kubernetes with Murano](https://www.mirantis.com/blog/integrating-openstack-and-kubernetes-with-murano/)
+- [An introduction to containers, Kubernetes, and the trajectory of modern cloud computing](http://googlecloudplatform.blogspot.com/2015/01/in-coming-weeks-we-will-be-publishing.html)
+- [What is Kubernetes and how to use it?](http://www.centurylinklabs.com/what-is-kubernetes-and-how-to-use-it/)
+- [OpenShift V3, Docker and Kubernetes Strategy](https://blog.openshift.com/v3-docker-kubernetes-interview/)
+- [An Introduction to Kubernetes](https://www.digitalocean.com/community/tutorials/an-introduction-to-kubernetes)
+-->
+
+- [使用 Vitess 和 Kubernetes 在云中扩展 MySQL](http://googlecloudplatform.blogspot.com/2015/03/scaling-MySQL-in-the-cloud-with-Vitess-and-Kubernetes.html)
+- [虚拟机上的容器群集](http://googlecloudplatform.blogspot.com/2015/02/container-clusters-on-vms.html)
+- [想知道的关于 kubernetes 的一切，却又不敢问](http://googlecloudplatform.blogspot.com/2015/01/everything-you-wanted-to-know-about-Kubernetes-but-were-afraid-to-ask.html)
+- [什么构成容器集群？](http://googlecloudplatform.blogspot.com/2015/01/what-makes-a-container-cluster.html)
+- [将 OpenStack 和 Kubernetes 与 Murano 集成](https://www.mirantis.com/blog/integrating-openstack-and-kubernetes-with-murano/)
+- [容器介绍，Kubernetes 以及现代云计算的发展轨迹](http://googlecloudplatform.blogspot.com/2015/01/in-coming-weeks-we-will-be-publishing.html)
+- [什么是 Kubernetes 以及如何使用它？](http://www.centurylinklabs.com/what-is-kubernetes-and-how-to-use-it/)
+- [OpenShift V3，Docker 和 Kubernetes 策略](https://blog.openshift.com/v3-docker-kubernetes-interview/)
+- [Kubernetes 简介](https://www.digitalocean.com/community/tutorials/an-introduction-to-kubernetes)
+
+<!--
+Happy cloud computing!
+-->
+快乐的云计算！
+
+<!--
+ - Kit Merker - Product Manager, Google Cloud Platform
+-->
+ - Kit Merker - Google 云平台产品经理
@@ -0,0 +1,176 @@
+---
+title: " Kubernetes Release: 0.15.0 "
+date: 2015-04-16
+slug: kubernetes-release-0150
+url: /blog/2015/04/Kubernetes-Release-0150
+---
+
+<!--
+Release Notes:
+-->
+
+Release 说明：
+
+<!--
+
+* Enables v1beta3 API and sets it to the default API version ([#6098][1])
+* Added multi-port Services ([#6182][2])
+    * New Getting Started Guides
+    * Multi-node local startup guide ([#6505][3])
+    * Mesos on Google Cloud Platform ([#5442][4])
+    * Ansible Setup instructions ([#6237][5])
+* Added a controller framework ([#5270][6], [#5473][7])
+* The Kubelet now listens on a secure HTTPS port ([#6380][8])
+* Made kubectl errors more user-friendly ([#6338][9])
+* The apiserver now supports client cert authentication ([#6190][10])
+* The apiserver now limits the number of concurrent requests it processes ([#6207][11])
+* Added rate limiting to pod deleting ([#6355][12])
+* Implement Balanced Resource Allocation algorithm as a PriorityFunction in scheduler package ([#6150][13])
+* Enabled log collection from master ([#6396][14])
+* Added an api endpoint to pull logs from Pods ([#6497][15])
+* Added latency metrics to scheduler ([#6368][16])
+* Added latency metrics to REST client ([#6409][17])
+
+-->
+
+* 启用 1beta3 API 并将其设置为默认 API 版本 ([#6098][1])
+* 增加了多端口服务([#6182][2])
+    * 新入门指南
+    * 多节点本地启动指南 ([#6505][3])
+    * Google 云平台上的 Mesos ([#5442][4])
+    * Ansible 安装说明 ([#6237][5])
+* 添加了一个控制器框架 ([#5270][6], [#5473][7])
+* Kubelet 现在监听一个安全的 HTTPS 端口 ([#6380][8])
+* 使 kubectl 错误更加友好 ([#6338][9])
+* apiserver 现在支持客户端 cert 身份验证 ([#6190][10])
+* apiserver 现在限制了它处理的并发请求的数量 ([#6207][11])
+* 添加速度限制删除 pod ([#6355][12])
+* 将平衡资源分配算法作为优先级函数实现在调度程序包中 ([#6150][13])
+* 从主服务器启用日志收集功能 ([#6396][14])
+* 添加了一个 api 端口来从 Pod 中提取日志 ([#6497][15])
+* 为调度程序添加了延迟指标 ([#6368][16])
+* 为 REST 客户端添加了延迟指标 ([#6409][17])
+
+<!--
+
+* etcd now runs in a pod on the master ([#6221][18])
+* nginx now runs in a container on the master ([#6334][19])
+* Began creating Docker images for master components ([#6326][20])
+* Updated GCE provider to work with gcloud 0.9.54 ([#6270][21])
+* Updated AWS provider to fix Region vs Zone semantics ([#6011][22])
+* Record event when image GC fails ([#6091][23])
+* Add a QPS limiter to the kubernetes client ([#6203][24])
+* Decrease the time it takes to run make release ([#6196][25])
+* New volume support
+    * Added iscsi volume plugin ([#5506][26])
+    * Added glusterfs volume plugin ([#6174][27])
+    * AWS EBS volume support ([#5138][28])
+* Updated to heapster version to v0.10.0 ([#6331][29])
+* Updated to etcd 2.0.9 ([#6544][30])
+* Updated to Kibana to v1.2 ([#6426][31])
+* Bug Fixes
+    * Kube-proxy now updates iptables rules if a service's public IPs change ([#6123][32])
+    * Retry kube-addons creation if the initial creation fails ([#6200][33])
+    * Make kube-proxy more resiliant to running out of file descriptors ([#6727][34])
+
+-->
+
+* etcd 现在在 master 上的一个 pod 中运行 ([#6221][18])
+* nginx 现在在 master上的容器中运行 ([#6334][19])
+* 开始为主组件构建 Docker 镜像 ([#6326][20])
+* 更新了 GCE 程序以使用 gcloud 0.9.54 ([#6270][21])
+* 更新了 AWS 程序来修复区域与区域语义 ([#6011][22])
+* 记录镜像 GC 失败时的事件 ([#6091][23])
+* 为 kubernetes 客户端添加 QPS 限制器 ([#6203][24])
+* 减少运行 make release 所需的时间 ([#6196][25])
+* 新卷的支持
+    * 添加 iscsi 卷插件 ([#5506][26])
+    * 添加 glusterfs 卷插件 ([#6174][27])
+    * AWS EBS 卷支持 ([#5138][28])
+* 更新到 heapster 版本到 v0.10.0 ([#6331][29])
+* 更新到 etcd 2.0.9 ([#6544][30])
+* 更新到 Kibana 到 v1.2 ([#6426][31])
+* 漏洞修复
+    * 如果服务的公共 IP 发生变化，Kube-proxy现在会更新iptables规则 ([#6123][32])
+    * 如果初始创建失败，则重试 kube-addons 创建 ([#6200][33])
+    * 使 kube-proxy 对耗尽文件描述符更具弹性 ([#6727][34])
+
+<!--
+To download, please visit https://github.com/GoogleCloudPlatform/kubernetes/releases/tag/v0.15.0
+-->
+要下载，请访问 https://github.com/GoogleCloudPlatform/kubernetes/releases/tag/v0.15.0
+
+<!--
+[1]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6098 "Enabling v1beta3 api version by default in master"
+[2]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6182 "Implement multi-port Services"
+[3]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6505 "Docker multi-node"
+[4]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5442 "Getting started guide for Mesos on Google Cloud Platform"
+[5]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6237 "example ansible setup repo"
+[6]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5270 "Controller framework"
+[7]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5473 "Add DeltaFIFO (a controller framework piece)"
+[8]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6380 "Configure the kubelet to use HTTPS (take 2)"
+[9]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6338 "Return a typed error for config validation, and make errors simple"
+[10]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6190 "Add client cert authentication"
+[11]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6207 "Add a limit to the number of in-flight requests that a server processes."
+[12]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6355 "Added rate limiting to pod deleting"
+[13]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6150 "Implement Balanced Resource Allocation (BRA) algorithm as a PriorityFunction in scheduler package."
+[14]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6396 "Enable log collection from master."
+[15]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6497 "Pod log subresource"
+[16]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6368 "Add basic latency metrics to scheduler."
+[17]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6409 "Add latency metrics to REST client"
+[18]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6221 "Run etcd 2.0.5 in a pod"
+[19]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6334 "Add an nginx docker image for use on the master."
+[20]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6326 "Create Docker images for master components "
+[21]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6270 "Updates for gcloud 0.9.54"
+-->
+[1]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6098 "在 master 中默认启用 v1beta3 api 版本"
+[2]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6182 "实现多端口服务"
+[3]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6505 "Docker 多节点"
+[4]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5442 "谷歌云平台上 Mesos 入门指南"
+[5]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6237 "示例 ansible 设置仓库"
+[6]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5270 "控制器框架"
+[7]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5473 "添加 DeltaFIFO（控制器框架块）"
+[8]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6380 "将 kubelet 配置为使用 HTTPS (获得 2)"
+[9]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6338 "返回用于配置验证的类型化错误，并简化错误"
+[10]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6190 "添加客户端证书认证"
+[11]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6207 "为服务器处理的正在运行的请求数量添加一个限制。"
+[12]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6355 "添加速度限制删除 pod"
+[13]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6150 "将均衡资源分配算法作为优先级函数实现在调度程序包中。"
+[14]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6396 "启用主服务器收集日志。"
+[15]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6497 "pod 子日志资源"
+[16]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6368 "将基本延迟指标添加到调度程序。"
+[17]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6409 "向 REST 客户端添加延迟指标"
+[18]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6221 "在 pod 中运行 etcd 2.0.5"
+[19]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6334 "添加一个 nginx docker 镜像用于主程序。"
+[20]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6326 "为主组件创建 Docker 镜像"
+[21]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6270 "gcloud 0.9.54 的更新"
+
+<!--
+[22]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6011 "Fix AWS region vs zone"
+[23]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6091 "Record event when image GC fails."
+[24]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6203 "Add a QPS limiter to the kubernetes client."
+[25]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6196 "Parallelize architectures in both the building and packaging phases of `make release`"
+[26]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5506 "add iscsi volume plugin"
+[27]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6174 "implement glusterfs volume plugin"
+[28]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5138 "AWS EBS volume support"
+[29]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6331 "Update heapster version to v0.10.0"
+[30]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6544 "Build etcd image (version 2.0.9), and upgrade kubernetes cluster to the new version"
+[31]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6426 "Update Kibana to v1.2 which paramaterizes location of Elasticsearch"
+[32]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6123 "Fix bug in kube-proxy of not updating iptables rules if a service's public IPs change"
+[33]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6200 "Retry kube-addons creation if kube-addons creation fails."
+[34]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6727 "pkg/proxy: panic if run out of fd"
+-->
+[22]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6011 "修复 AWS 区域 与 zone"
+[23]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6091 "记录镜像 GC 失败时的事件。"
+[24]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6203 "向 kubernetes 客户端添加 QPS 限制器。"
+[25]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6196 "在 `make release` 的构建和打包阶段并行化架构"
+[26]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5506 "添加 iscsi 卷插件"
+[27]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6174 "实现 glusterfs 卷插件"
+[28]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5138 "AWS EBS 卷支持"
+[29]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6331 "将 heapster 版本更新到 v0.10.0"
+[30]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6544 "构建 etcd 镜像(版本 2.0.9)，并将 kubernetes 集群升级到新版本"
+[31]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6426 "更新 Kibana 到 v1.2，它对 Elasticsearch 的位置进行了参数化"
+[32]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6123 "修复了 kube-proxy 中的一个错误，如果一个服务的公共 ip 发生变化，它不会更新 iptables 规则"
+[33]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6200 "如果 kube-addons 创建失败，请重试 kube-addons 创建。"
+[34]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6727 "pkg/proxy: fd 用完后引起恐慌"
+
@@ -0,0 +1,287 @@
+---
+title: " Kubernetes 社区每周聚会笔记- 2015年4月17日 "
+date: 2015-04-17
+slug: weekly-kubernetes-community-hangout_17
+url: /blog/2015/04/Weekly-Kubernetes-Community-Hangout_17
+---
+
+<!--
+---
+title: " Weekly Kubernetes Community Hangout Notes - April 17 2015 "
+date: 2015-04-17
+slug: weekly-kubernetes-community-hangout_17
+url: /blog/2015/04/Weekly-Kubernetes-Community-Hangout_17
+---
+-->
+
+<!--
+Every week the Kubernetes contributing community meet virtually over Google Hangouts. We want anyone who's interested to know what's discussed in this forum.  
+-->
+每个星期，Kubernetes 贡献者社区几乎都会在谷歌 Hangouts 上聚会。我们希望任何对此感兴趣的人都能了解这个论坛的讨论内容。
+
+<!--
+Agenda  
+
+* Mesos Integration
+* High Availability (HA)
+* Adding performance and profiling details to e2e to track regressions
+* Versioned clients
+
+-->
+议程  
+
+* Mesos 集成
+* 高可用性（HA）
+* 向 e2e 添加性能和分析详细信息以跟踪回归
+* 客户端版本化
+
+<!--
+Notes  
+-->
+笔记
+
+<!--
+
+* Mesos integration
+
+    * Mesos integration proposal:
+
+    * No blockers to integration.
+
+    * Documentation needs to be updated.
+
+-->
+
+* Mesos 集成
+
+    * Mesos 集成提案：
+
+    * 没有阻塞集成的因素。
+
+    * 文档需要更新。
+
+<!--
+
+* HA
+
+    * Proposal should land today.
+
+    * Etcd cluster.
+
+    * Load-balance apiserver.
+
+    * Cold standby for controller manager and other master components.
+    
+-->
+
+* HA
+
+    * 提案今天应该会提交。
+
+    * Etcd 集群。
+
+    * apiserver 负载均衡。
+
+    * 控制器管理器和其他主组件的冷备用。
+
+<!--
+
+* Adding performance and profiling details to e2e to track regression
+
+    * Want red light for performance regression
+
+    * Need a public DB to post the data
+
+        * See
+
+    * Justin working on multi-platform e2e dashboard
+    
+-->
+
+* 向 e2e 添加性能和分析详细信息以跟踪回归
+
+    * 希望红色为性能回归
+
+    * 需要公共数据库才能发布数据
+
+        * 查看
+
+    * Justin 致力于多平台 e2e 仪表盘
+
+<!--
+
+* Versioned clients
+
+    *
+
+    *
+
+    * Client library currently uses internal API objects.
+
+    * Nobody reported that frequent changes to types.go have been painful, but we are worried about it.
+
+    * Structured types are useful in the client. Versioned structs would be ok.
+
+    * If start with json/yaml (kubectl), shouldn’t convert to structured types. Use swagger.
+    
+-->
+
+* 客户端版本化
+
+    *
+
+    *
+
+    * 客户端库当前使用内部 API 对象。
+
+    * 尽管没有人反映频繁修改 `types.go` 有多痛苦，但我们很为此担心。
+
+    * 结构化类型在客户端中很有用。版本化的结构就可以了。
+
+    * 如果从 json/yaml (kubectl) 开始，则不应转换为结构化类型。使用 swagger。
+
+<!--
+
+* Security context
+
+    *
+
+    * Administrators can restrict who can run privileged containers or require specific unix uids
+
+    * Kubelet will be able to get pull credentials from apiserver
+
+    * Policy proposal coming in the next week or so
+-->
+
+* Security context
+
+    *
+
+    * 管理员可以限制谁可以运行特权容器或需要特定的 unix uid
+
+    * kubelet 将能够从 apiserver 获取证书
+
+    * 政策提案将于下周左右出台
+
+<!--
+
+* Discussing upstreaming of users, etc. into Kubernetes, at least as optional
+* 1.0 Roadmap
+
+    * Focus is performance, stability, cluster upgrades
+
+    * TJ has been making some edits to [roadmap.md][4] but hasn’t sent out a PR yet
+* Kubernetes UI
+
+    * Dependencies broken out into third-party
+
+    * @lavalamp is reviewer
+
+-->
+
+* 讨论用户的上游，等等进入Kubernetes，至少是可选的
+* 1.0 路线图
+
+    * 重点是性能，稳定性，集群升级
+
+    * TJ 一直在对[roadmap.md][4]进行一些编辑，但尚未发布PR
+* Kubernetes UI
+
+    * 依赖关系分解为第三方
+
+    * @lavalamp 是评论家
+
+
+[1]: http://kubernetes.io/images/nav_logo.svg
+[2]: http://kubernetes.io/docs/
+[3]: https://kubernetes.io/blog/
+[4]: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/roadmap.md
+[5]: https://kubernetes.io/blog/2015/04/weekly-kubernetes-community-hangout_17 "permanent link"
+[6]: https://resources.blogblog.com/img/icon18_edit_allbkg.gif
+[7]: https://www.blogger.com/post-edit.g?blogID=112706738355446097&postID=630924463010638300&from=pencil "Edit Post"
+[8]: https://www.blogger.com/share-post.g?blogID=112706738355446097&postID=630924463010638300&target=email "Email This"
+[9]: https://www.blogger.com/share-post.g?blogID=112706738355446097&postID=630924463010638300&target=blog "BlogThis!"
+[10]: https://www.blogger.com/share-post.g?blogID=112706738355446097&postID=630924463010638300&target=twitter "Share to Twitter"
+[11]: https://www.blogger.com/share-post.g?blogID=112706738355446097&postID=630924463010638300&target=facebook "Share to Facebook"
+[12]: https://www.blogger.com/share-post.g?blogID=112706738355446097&postID=630924463010638300&target=pinterest "Share to Pinterest"
+[13]: https://kubernetes.io/blog/search/label/community%20meetings
+[14]: https://kubernetes.io/blog/search/label/containers
+[15]: https://kubernetes.io/blog/search/label/docker
+[16]: https://kubernetes.io/blog/search/label/k8s
+[17]: https://kubernetes.io/blog/search/label/kubernetes
+[18]: https://kubernetes.io/blog/search/label/open%20source
+[19]: https://kubernetes.io/blog/2015/04/kubernetes-and-mesosphere-dcos "Newer Post"
+[20]: https://kubernetes.io/blog/2015/04/introducing-kubernetes-v1beta3 "Older Post"
+[21]: https://kubernetes.io/blog/feeds/630924463010638300/comments/default
+[22]: https://img2.blogblog.com/img/widgets/arrow_dropdown.gif
+[23]: https://img1.blogblog.com/img/icon_feed12.png
+[24]: https://img1.blogblog.com/img/widgets/subscribe-netvibes.png
+[25]: https://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fblog.kubernetes.io%2Ffeeds%2Fposts%2Fdefault
+[26]: https://img1.blogblog.com/img/widgets/subscribe-yahoo.png
+[27]: https://add.my.yahoo.com/content?url=http%3A%2F%2Fblog.kubernetes.io%2Ffeeds%2Fposts%2Fdefault
+[28]: https://kubernetes.io/blog/feeds/posts/default
+[29]: https://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fblog.kubernetes.io%2Ffeeds%2F630924463010638300%2Fcomments%2Fdefault
+[30]: https://add.my.yahoo.com/content?url=http%3A%2F%2Fblog.kubernetes.io%2Ffeeds%2F630924463010638300%2Fcomments%2Fdefault
+[31]: https://resources.blogblog.com/img/icon18_wrench_allbkg.png
+[32]: //www.blogger.com/rearrange?blogID=112706738355446097&widgetType=Subscribe&widgetId=Subscribe1&action=editWidget§ionId=sidebar-right-1 "Edit"
+[33]: https://twitter.com/kubernetesio
+[34]: https://github.com/kubernetes/kubernetes
+[35]: http://slack.k8s.io/
+[36]: http://stackoverflow.com/questions/tagged/kubernetes
+[37]: http://get.k8s.io/
+[38]: //www.blogger.com/rearrange?blogID=112706738355446097&widgetType=HTML&widgetId=HTML2&action=editWidget§ionId=sidebar-right-1 "Edit"
+[39]: javascript:void(0)
+[40]: https://kubernetes.io/blog/2018/
+[41]: https://kubernetes.io/blog/2018/01/
+[42]: https://kubernetes.io/blog/2017/
+[43]: https://kubernetes.io/blog/2017/12/
+[44]: https://kubernetes.io/blog/2017/11/
+[45]: https://kubernetes.io/blog/2017/10/
+[46]: https://kubernetes.io/blog/2017/09/
+[47]: https://kubernetes.io/blog/2017/08/
+[48]: https://kubernetes.io/blog/2017/07/
+[49]: https://kubernetes.io/blog/2017/06/
+[50]: https://kubernetes.io/blog/2017/05/
+[51]: https://kubernetes.io/blog/2017/04/
+[52]: https://kubernetes.io/blog/2017/03/
+[53]: https://kubernetes.io/blog/2017/02/
+[54]: https://kubernetes.io/blog/2017/01/
+[55]: https://kubernetes.io/blog/2016/
+[56]: https://kubernetes.io/blog/2016/12/
+[57]: https://kubernetes.io/blog/2016/11/
+[58]: https://kubernetes.io/blog/2016/10/
+[59]: https://kubernetes.io/blog/2016/09/
+[60]: https://kubernetes.io/blog/2016/08/
+[61]: https://kubernetes.io/blog/2016/07/
+[62]: https://kubernetes.io/blog/2016/06/
+[63]: https://kubernetes.io/blog/2016/05/
+[64]: https://kubernetes.io/blog/2016/04/
+[65]: https://kubernetes.io/blog/2016/03/
+[66]: https://kubernetes.io/blog/2016/02/
+[67]: https://kubernetes.io/blog/2016/01/
+[68]: https://kubernetes.io/blog/2015/
+[69]: https://kubernetes.io/blog/2015/12/
+[70]: https://kubernetes.io/blog/2015/11/
+[71]: https://kubernetes.io/blog/2015/10/
+[72]: https://kubernetes.io/blog/2015/09/
+[73]: https://kubernetes.io/blog/2015/08/
+[74]: https://kubernetes.io/blog/2015/07/
+[75]: https://kubernetes.io/blog/2015/06/
+[76]: https://kubernetes.io/blog/2015/05/
+[77]: https://kubernetes.io/blog/2015/04/
+[78]: https://kubernetes.io/blog/2015/04/weekly-kubernetes-community-hangout_29
+[79]: https://kubernetes.io/blog/2015/04/borg-predecessor-to-kubernetes
+[80]: https://kubernetes.io/blog/2015/04/kubernetes-and-mesosphere-dcos
+[81]: https://kubernetes.io/blog/2015/04/weekly-kubernetes-community-hangout_17
+[82]: https://kubernetes.io/blog/2015/04/introducing-kubernetes-v1beta3
+[83]: https://kubernetes.io/blog/2015/04/kubernetes-release-0150
+[84]: https://kubernetes.io/blog/2015/04/weekly-kubernetes-community-hangout_11
+[85]: https://kubernetes.io/blog/2015/04/faster-than-speeding-latte
+[86]: https://kubernetes.io/blog/2015/04/weekly-kubernetes-community-hangout
+[87]: https://kubernetes.io/blog/2015/03/
+[88]: //www.blogger.com/rearrange?blogID=112706738355446097&widgetType=BlogArchive&widgetId=BlogArchive1&action=editWidget§ionId=sidebar-right-1 "Edit"
+[89]: //www.blogger.com/rearrange?blogID=112706738355446097&widgetType=HTML&widgetId=HTML1&action=editWidget§ionId=sidebar-right-1 "Edit"
+[90]: https://www.blogger.com
+[91]: //www.blogger.com/rearrange?blogID=112706738355446097&widgetType=Attribution&widgetId=Attribution1&action=editWidget§ionId=footer-3 "Edit"
+
+  [*[3:27 PM]: 2015-04-17T15:27:00-07:00
@@ -0,0 +1,143 @@
+---
+title: " Kubernetes 社区每周聚会笔记- 2015年4月24日 "
+date: 2015-04-30
+slug: weekly-kubernetes-community-hangout_29
+url: /blog/2015/04/Weekly-Kubernetes-Community-Hangout_29
+---
+
+<!--
+---
+title: " Weekly Kubernetes Community Hangout Notes - April 24 2015 "
+date: 2015-04-30
+slug: weekly-kubernetes-community-hangout_29
+url: /blog/2015/04/Weekly-Kubernetes-Community-Hangout_29
+---
+
+-->
+
+<!--
+Every week the Kubernetes contributing community meet virtually over Google Hangouts. We want anyone who's interested to know what's discussed in this forum.  
+-->
+每个星期，Kubernetes 贡献者社区几乎都会在谷歌 Hangouts 上聚会。我们希望任何对此感兴趣的人都能了解这个论坛的讨论内容。
+
+<!--
+Agenda:
+
+* Flocker and Kubernetes integration demo
+
+-->
+日程安排：
+
+* Flocker 和 Kubernetes 集成演示
+
+<!--
+Notes:
+
+* flocker and kubernetes integration demo
+* * Flocker Q/A
+
+    * Does the file still exists on node1 after migration?
+
+    * Brendan: Any plan this to make it a volume? So we don't need powerstrip?
+
+        * Luke:  Need to figure out interest to decide if we want to make it a first-class persistent disk provider in kube.
+
+        * Brendan: Removing need for powerstrip would make it simple to use. Totally go for it.
+
+        * Tim: Should take no more than 45 minutes to add it to kubernetes:)
+
+-->
+笔记：
+
+* flocker 和 kubernetes 集成演示
+* * Flocker Q/A
+
+    * 迁移后文件是否仍存在于node1上？
+
+    * Brendan: 有没有计划把它做成一本书？我们不需要 powerstrip？
+
+        * Luke:  需要找出感兴趣的来决定我们是否想让它成为 kube 中的一个一流的持久性磁盘提供商。
+
+        * Brendan: 删除对 powerstrip 的需求会使其易于使用。完全去做。
+
+        * Tim: 将它添加到 kubernetes 应该不超过45分钟:)
+
+<!--
+
+    * Derek: Contrast this with persistent volumes and claims?
+
+        * Luke: Not much difference, except for the novel ZFS based backend. Makes workloads really portable.
+
+        * Tim: very different than network-based volumes. Its interesting that it is the only offering that allows upgrading media.
+
+        * Brendan: claims, how does it look for replicated claims? eg Cassandra wants to have replicated data underneath. It would be efficient to scale up and down. Create storage on the fly based on load dynamically. Its step beyond taking snapshots - programmatically creating replicas with preallocation.
+
+        * Tim: helps with auto-provisioning.
+
+-->
+
+    * Derek: 持久卷和请求相比呢?
+
+        * Luke: 除了基于 ZFS 的新后端之外，差别不大。使工作负载真正可移植。
+
+        * Tim: 与基于网络的卷非常不同。有趣的是，它是唯一允许升级媒体的产品。
+
+        * Brendan: 请求，它如何查找重复请求？Cassandra 希望在底层复制数据。向上和向下扩缩是有效的。根据负载动态地创建存储。它的步骤不仅仅是快照——通过编程使用预分配创建副本。
+
+        * Tim: 帮助自动配置。
+        
+<!--
+
+    * Brian: Does flocker requires any other component?
+
+        * Kai: Flocker control service co-located with the master.  (dia on blog post). Powerstrip + Powerstrip Flocker. Very interested in mpersisting state in etcd. It keeps metadata about each volume.
+
+        * Brendan: In future, flocker can be a plugin and we'll take care of persistence. Post v1.0.
+
+        * Brian: Interested in adding generic plugin for services like flocker.
+
+        * Luke: Zfs can become really valuable when scaling to lot of containers on a single node.
+
+-->
+
+    * Brian: flocker 是否需要其他组件？
+
+        * Kai: Flocker 控制服务与主服务器位于同一位置。(dia 在博客上)。Powerstrip + Powerstrip Flocker。对在 etcd 中持久化状态非常有趣。它保存关于每个卷的元数据。
+
+        * Brendan: 在未来，flocker 可以是一个插件，我们将负责持久性。发布 v1.0。
+
+        * Brian: 有兴趣为 flocker 等服务添加通用插件。
+
+        * Luke: 当扩展到单个节点上的许多容器时，Zfs 会变得非常有价值。
+
+<!--
+
+    * Alex: Can flocker service can be run as a pod?
+
+        * Kai: Yes, only requirement is the flocker control service should be able to talk to zfs agent. zfs agent needs to be installed on the host and zfs binaries need to be accessible.
+
+        * Brendan: In theory, all zfs bits can be put it into a container with devices.
+
+        * Luke: Yes, still working through cross-container mounting issue.
+
+        * Tim: pmorie is working through it to make kubelet work in a container. Possible re-use.
+
+    * Kai: Cinder support is coming. Few days away.
+* Bob: What's the process of pushing kube to GKE? Need more visibility for confidence.
+
+-->
+
+    * Alex: flocker 服务可以作为 pod 运行吗？
+
+        * Kai: 是的，唯一的要求是 flocker 控制服务应该能够与 zfs 代理对话。需要在主机上安装 zfs 代理，并且需要访问 zfs 二进制文件。
+
+        * Brendan: 从理论上讲，所有 zfs 位都可以与设备一起放入容器中。
+
+        * Luke: 是的，仍然在处理跨容器安装问题。
+
+        * Tim: pmorie 正在通过它使 kubelet 在容器中工作。可能重复使用。
+
+    * Kai: Cinder 支持即将到来。几天之后。
+* Bob: 向 GKE 推送 kube 的过程是怎样的？需要更多的可见度。
+
+
@@ -0,0 +1,112 @@
+---
+title: " OpenStack 上的 Kubernetes "
+date: 2015-05-19
+slug: kubernetes-on-openstack
+url: /blog/2015/05/Kubernetes-On-Openstack
+---
+
+<!--
+---
+title: " Kubernetes on OpenStack "
+date: 2015-05-19
+slug: kubernetes-on-openstack
+url: /blog/2015/05/Kubernetes-On-Openstack
+---
+-->
+
+[![](https://3.bp.blogspot.com/-EOrCHChZJZE/VVZzq43g6CI/AAAAAAAAF-E/JUilRHk369E/s400/Untitled%2Bdrawing.jpg)](https://3.bp.blogspot.com/-EOrCHChZJZE/VVZzq43g6CI/AAAAAAAAF-E/JUilRHk369E/s1600/Untitled%2Bdrawing.jpg)
+
+
+<!--
+Today, the [OpenStack foundation](https://www.openstack.org/foundation/) made it even easier for you deploy and manage clusters of Docker containers on OpenStack clouds by including Kubernetes in its [Community App Catalog](http://apps.openstack.org/). &nbsp;At a keynote today at the OpenStack Summit in Vancouver, Mark Collier, COO of the OpenStack Foundation, and Craig Peters, &nbsp;[Mirantis](https://www.mirantis.com/) product line manager, demonstrated the Community App Catalog workflow by launching a Kubernetes cluster in a matter of seconds by leveraging the compute, storage, networking and identity systems already present in an OpenStack cloud.
+-->
+今天，[OpenStack 基金会](https://www.openstack.org/foundation/)通过在其[社区应用程序目录](http://apps.openstack.org/)中包含 Kubernetes，使您更容易在 OpenStack 云上部署和管理 Docker 容器集群。
+今天在温哥华 OpenStack 峰会上的主题演讲中，OpenStack 基金会的首席运营官：Mark Collier 和 [Mirantis](https://www.mirantis.com/) 产品线经理 Craig Peters 通过利用 OpenStack 云中已经存在的计算、存储、网络和标识系统，在几秒钟内启动了 Kubernetes 集群，展示了社区应用程序目录的工作流。
+
+<!--
+The entries in the catalog include not just the ability to [start a Kubernetes cluster](http://apps.openstack.org/#tab=murano-apps&asset=Kubernetes%20Cluster), but also a range of applications deployed in Docker containers managed by Kubernetes. These applications include:
+-->
+目录中的条目不仅包括[启动 Kubernetes 集群](http://apps.openstack.org/#tab=murano-apps&asset=Kubernetes%20Cluster)的功能，还包括部署在 Kubernetes 管理的 Docker 容器中的一系列应用程序。这些应用包括：
+
+<!--
+
+-
+Apache web server
+-
+Nginx web server
+-
+Crate - The Distributed Database for Docker
+-
+GlassFish - Java EE 7 Application Server
+-
+Tomcat - An open-source web server and servlet container
+-
+InfluxDB - An open-source, distributed, time series database
+-
+Grafana - Metrics dashboard for InfluxDB
+-
+Jenkins - An extensible open source continuous integration server
+-
+MariaDB database
+-
+MySql database
+-
+Redis - Key-value cache and store
+-
+PostgreSQL database
+-
+MongoDB NoSQL database
+-
+Zend Server - The Complete PHP Application Platform
+
+-->
+
+
+-
+Apache web 服务器
+-
+Nginx web 服务器
+-
+Crate - Docker的分布式数据库
+-
+GlassFish - Java EE 7 应用服务器
+-
+Tomcat - 一个开源的 web 服务器和 servlet 容器
+-
+InfluxDB - 一个开源的、分布式的、时间序列数据库
+-
+Grafana -   InfluxDB 的度量仪表板
+-
+Jenkins - 一个可扩展的开放源码持续集成服务器
+-
+MariaDB 数据库
+-
+MySql 数据库
+-
+Redis - 键-值缓存和存储
+-
+PostgreSQL 数据库
+-
+MongoDB NoSQL 数据库
+-
+Zend 服务器 - 完整的 PHP 应用程序平台
+
+<!--
+This list will grow, and is curated [here](https://github.com/openstack/murano-apps/tree/master/Docker/Kubernetes). You can examine (and contribute to) the YAML file that tells Murano how to install and start the Kubernetes cluster [here](https://github.com/openstack/murano-apps/blob/master/Docker/Kubernetes/KubernetesCluster/package/Classes/KubernetesCluster.yaml).
+-->
+此列表将会增长，并在[此处](https://github.com/openstack/murano-apps/tree/master/Docker/Kubernetes)进行策划。您可以检查（并参与）YAML 文件，该文件告诉 Murano 如何根据[此处](https://github.com/openstack/murano-apps/blob/master/Docker/Kubernetes/KubernetesCluster/package/Classes/KubernetesCluster.yaml)定义来安装和启动 ...apps/blob/master/Docker/Kubernetes/KubernetesCluster/package/Classes/KubernetesCluster.yaml)安装和启动 Kubernetes 集群。
+
+<!--
+[The Kubernetes open source project](https://github.com/GoogleCloudPlatform/kubernetes) has continued to see fantastic community adoption and increasing momentum, with over 11,000 commits and 7,648 stars on GitHub. With supporters ranging from Red Hat and Intel to CoreOS and Box.net, it has come to represent a range of customer interests ranging from enterprise IT to cutting edge startups. We encourage you to give it a try, give us your feedback, and get involved in our growing community.
+-->
+[Kubernetes 开源项目](https://github.com/GoogleCloudPlatform/kubernetes)继续受到社区的欢迎，并且势头越来越好，GitHub 上有超过 11000 个提交和 7648 颗星。从 Red Hat 和 Intel 到 CoreOS 和 Box.net，它已经代表了从企业 IT 到前沿创业企业的一系列客户。我们鼓励您尝试一下，给我们您的反馈，并参与到我们不断增长的社区中来。
+
+
+<!--
+
+- Martin Buhr, Product Manager, Kubernetes Open Source Project
+
+-->
+
+- Martin Buhr, Kubernetes 开源项目产品经理
+
@@ -0,0 +1,121 @@
+---
+title: " Kubernetes 社区每周聚会笔记- 2015年5月1日 "
+date: 2015-05-11
+slug: weekly-kubernetes-community-hangout
+url: /blog/2015/05/Weekly-Kubernetes-Community-Hangout
+---
+
+<!--
+---
+title: " Weekly Kubernetes Community Hangout Notes - May 1 2015 "
+date: 2015-05-11
+slug: weekly-kubernetes-community-hangout
+url: /blog/2015/05/Weekly-Kubernetes-Community-Hangout
+---
+-->
+
+<!--
+Every week the Kubernetes contributing community meet virtually over Google Hangouts. We want anyone who's interested to know what's discussed in this forum.
+-->
+每个星期，Kubernetes 贡献者社区几乎都会在谷歌 Hangouts 上聚会。我们希望任何对此感兴趣的人都能了解这个论坛的讨论内容。
+
+<!--
+
+* Simple rolling update - Brendan
+
+    * Rolling update = nice example of why RCs and Pods are good.
+
+    * ...pause… (Brendan needs demo recovery tips from Kelsey)
+
+    * Rolling update has recovery: Cancel update and restart, update continues from where it stopped.
+
+    * New controller  gets name of old controller, so appearance is pure update.
+
+    * Can also name versions in update (won't do rename at the end).
+
+-->  
+
+* 简单的滚动更新 - Brendan
+
+    * 滚动更新 = RCs和Pods很好的例子。
+
+    * ...pause… (Brendan 需要 Kelsey 的演示恢复技巧)
+
+    * 滚动更新具有恢复功能:取消更新并重新启动，更新从停止的地方继续。
+
+    * 新控制器获取旧控制器的名称，因此外观是纯粹的更新。
+
+    * 还可以在 update 中命名版本(最后不会重命名)。
+
+<!--
+
+* Rocket demo - CoreOS folks
+
+    * 2 major differences between rocket & docker: Rocket is daemonless & pod-centric.
+
+    * Rocket has AppContainer format as native, but also supports docker image format.
+
+    * Can run AppContainer and docker containers in same pod.
+
+    * Changes are close to merged.
+    
+-->
+
+* Rocket 演示 - CoreOS 的伙计们
+
+    * Rocket 和 docker 之间的主要区别: Rocket 是无守护进程和以 pod 为中心。。
+
+    * Rocket 具有原生的 AppContainer 格式，但也支持 docker 镜像格式。
+
+    * 可以在同一个 pod 中运行 AppContainer 和 docker 容器。
+
+    * 变更接近于合并。
+
+<!--
+
+* demo service accounts and secrets being added to pods - Jordan
+
+    * Problem: It's hard to get a token to talk to the API.
+
+    * New API object: "ServiceAccount"
+
+    * ServiceAccount is namespaced, controller makes sure that at least 1 default service account exists in a namespace.
+
+    * Typed secret "ServiceAccountToken", controller makes sure there is at least 1 default token.
+
+    * DEMO
+
+    *     * Can create new service account with ServiceAccountToken. Controller will create token for it.
+
+    * Can create a pod with service account, pods will have service account secret mounted at /var/run/secrets/kubernetes.io/…
+    
+-->
+
+* 演示 service accounts 和 secrets 被添加到 pod - Jordan
+
+    * 问题：很难获得与API通信的令牌。
+
+    * 新的API对象："ServiceAccount"
+
+    * ServiceAccount 是命名空间，控制器确保命名空间中至少存在一个个默认 service account。
+
+    * 键入 "ServiceAccountToken"，控制器确保至少有一个默认令牌。
+
+    * 演示
+
+    *     * 可以使用 ServiceAccountToken 创建新的 service account。控制器将为它创建令牌。
+
+    * 可以创建一个带有 service account 的 pod, pod 将在 /var/run/secrets/kubernets.io/…
+    
+<!--    
+    
+* Kubelet running in a container - Paul
+
+    * Kubelet successfully ran pod w/ mounted secret.
+
+-->
+    
+* Kubelet 在容器中运行 - Paul
+
+    * Kubelet 成功地运行了带有 secret 的 pod。
+    
@@ -0,0 +1,25 @@
+---
+title: "幻灯片：Kubernetes 集群管理，爱丁堡大学演讲"
+date: 2015-06-26
+slug: slides-cluster-management-with
+url: /blog/2015/06/Slides-Cluster-Management-With
+---
+
+<!--
+---
+title: " Slides: Cluster Management with Kubernetes, talk given at the University of Edinburgh "
+date: 2015-06-26
+slug: slides-cluster-management-with
+url: /blog/2015/06/Slides-Cluster-Management-With
+---
+-->
+
+<!--
+On Friday 5 June 2015 I gave a talk called [Cluster Management with Kubernetes](https://docs.google.com/presentation/d/1H4ywDb4vAJeg8KEjpYfhNqFSig0Q8e_X5I36kM9S6q0/pub?start=false&loop=false&delayms=3000) to a general audience at the University of Edinburgh. The talk includes an example of a music store system with a Kibana front end UI and an Elasticsearch based back end which helps to make concrete concepts like pods, replication controllers and services.
+
+[Cluster Management with Kubernetes](https://docs.google.com/presentation/d/1H4ywDb4vAJeg8KEjpYfhNqFSig0Q8e_X5I36kM9S6q0/pub?start=false&loop=false&delayms=3000).
+-->
+
+2015年6月5日星期五，我在爱丁堡大学给普通听众做了一个演讲，题目是[使用 Kubernetes 进行集群管理](https://docs.google.com/presentation/d/1H4ywDb4vAJeg8KEjpYfhNqFSig0Q8e_X5I36kM9S6q0/pub?start=false&loop=false&delayms=3000)。这次演讲包括一个带有 Kibana 前端 UI 的音乐存储系统的例子，以及一个基于 Elasticsearch 的后端，该后端有助于生成具体的概念，如 pods、复制控制器和服务。
+
+[Kubernetes 集群管理](https://docs.google.com/presentation/d/1H4ywDb4vAJeg8KEjpYfhNqFSig0Q8e_X5I36kM9S6q0/pub?start=false&loop=false&delayms=3000)。
@@ -0,0 +1,84 @@
+---
+title: " KubeCon EU 2016：伦敦 Kubernetes 社区 "
+date: 2016-02-24
+slug: kubecon-eu-2016-kubernetes-community-in
+url: /blog/2016/02/Kubecon-Eu-2016-Kubernetes-Community-In
+---
+
+<!--
+---
+title: " KubeCon EU 2016: Kubernetes Community in London "
+date: 2016-02-24
+slug: kubecon-eu-2016-kubernetes-community-in
+url: /blog/2016/02/Kubecon-Eu-2016-Kubernetes-Community-In
+---
+-->
+
+<!--
+KubeCon EU 2016 is the inaugural [European Kubernetes](http://kubernetes.io/) community conference that follows on the American launch in November 2015. KubeCon is fully dedicated to education and community engagement for[Kubernetes](http://kubernetes.io/) enthusiasts, production users and the surrounding ecosystem.
+-->
+KubeCon EU 2016 是首届[欧洲 Kubernetes](http://kubernetes.io/) 社区会议，紧随 2015 年 11 月召开的北美会议。KubeCon 致力于为 [Kubernetes](http://kubernetes.io/) 爱好者、产品用户和周围的生态系统提供教育和社区参与。
+
+<!--
+Come join us in London and hang out with hundreds from the Kubernetes community and experience a wide variety of deep technical expert talks and use cases.
+-->
+快来加入我们在伦敦，与 Kubernetes 社区的数百人一起出去，体验各种深入的技术专家讲座和用例。
+
+<!--
+Don’t miss these great speaker sessions at the conference:
+-->
+不要错过这些优质的演讲：
+
+<!--
+* “Kubernetes Hardware Hacks: Exploring the Kubernetes API Through Knobs, Faders, and Sliders” by Ian Lewis and Brian Dorsey, Developer Advocate, Google -* [http://sched.co/6Bl3](http://sched.co/6Bl3)  
+
+* “rktnetes: what's new with container runtimes and Kubernetes” by Jonathan Boulle, Developer and Team Lead at CoreOS -* [http://sched.co/6BY7](http://sched.co/6BY7)
+
+* “Kubernetes Documentation: Contributing, fixing issues, collecting bounties” by John Mulhausen, Lead Technical Writer, Google -* [http://sched.co/6BUP](http://sched.co/6BUP)&nbsp;
+* “[What is OpenStack's role in a Kubernetes world?](https://kubeconeurope2016.sched.org/event/6BYC/what-is-openstacks-role-in-a-kubernetes-world?iframe=yes&w=i:0;&sidebar=yes&bg=no#?iframe=yes&w=i:100;&sidebar=yes&bg=no)” By Thierry Carrez, Director of Engineering, OpenStack Foundation -* http://sched.co/6BYC
+* “A Practical Guide to Container Scheduling” by Mandy Waite, Developer Advocate, Google -* [http://sched.co/6BZa](http://sched.co/6BZa)  
+
+* “[Kubernetes in Production in The New York Times newsroom](https://kubeconeurope2016.sched.org/event/67f2/kubernetes-in-production-in-the-new-york-times-newsroom?iframe=yes&w=i:0;&sidebar=yes&bg=no#?iframe=yes&w=i:100;&sidebar=yes&bg=no)” Eric Lewis, Web Developer, New York Times -* [http://sched.co/67f2](http://sched.co/67f2)
+* “[Creating an Advanced Load Balancing Solution for Kubernetes with NGINX](https://kubeconeurope2016.sched.org/event/6Bc9/creating-an-advanced-load-balancing-solution-for-kubernetes-with-nginx?iframe=yes&w=i:0;&sidebar=yes&bg=no#?iframe=yes&w=i:100;&sidebar=yes&bg=no)” by Andrew Hutchings, Technical Product Manager, NGINX -* http://sched.co/6Bc9
+* And many more http://kubeconeurope2016.sched.org/
+-->
+
+* “Kubernetes 硬件黑客：通过旋钮、推杆和滑块探索 Kubernetes API” 演讲者 Ian Lewis 和 Brian Dorsey，谷歌开发布道师* [http://sched.co/6Bl3](http://sched.co/6Bl3)  
+
+* “rktnetes: 容器运行时和 Kubernetes 的新功能” 演讲者 Jonathan Boulle, CoreOS 的主程 -* [http://sched.co/6BY7](http://sched.co/6BY7)
+
+* “Kubernetes 文档：贡献、修复问题、收集奖金” 作者：John Mulhausen，首席技术作家，谷歌 -* [http://sched.co/6BUP](http://sched.co/6BUP)&nbsp;
+* “[OpenStack 在 Kubernetes 的世界中扮演什么角色？](https://kubeconeurope2016.sched.org/event/6BYC/what-is-openstacks-role-in-a-kubernetes-world?iframe=yes&w=i:0;&sidebar=yes&bg=no#?iframe=yes&w=i:100;&sidebar=yes&bg=no)” 作者：Thierry carez, OpenStack 基金会工程总监 -* http://sched.co/6BYC
+* “容器调度的实用指南” 作者：Mandy Waite，开发者倡导者，谷歌 -* [http://sched.co/6BZa](http://sched.co/6BZa)  
+
+* “[《纽约时报》编辑部正在制作 Kubernetes](https://kubeconeurope2016.sched.org/event/67f2/kubernetes-in-production-in-the-new-york-times-newsroom?iframe=yes&w=i:0;&sidebar=yes&bg=no#?iframe=yes&w=i:100;&sidebar=yes&bg=no)” Eric Lewis，《纽约时报》网站开发人员 -* [http://sched.co/67f2](http://sched.co/67f2)
+* “[使用 NGINX 为 Kubernetes 创建一个高级负载均衡解决方案](https://kubeconeurope2016.sched.org/event/6Bc9/creating-an-advanced-load-balancing-solution-for-kubernetes-with-nginx?iframe=yes&w=i:0;&sidebar=yes&bg=no#?iframe=yes&w=i:100;&sidebar=yes&bg=no)” 作者：Andrew Hutchings, NGINX 技术产品经理 -* http://sched.co/6Bc9
+* 还有更多 http://kubeconeurope2016.sched.org/
+
+<!--
+Get your KubeCon EU [tickets here](https://ti.to/kubecon/kubecon-eu-2016).
+-->
+[在这里](https://ti.to/kubecon/kubecon-eu-2016)获取您的 KubeCon EU 门票。
+
+<!--
+Venue Location: CodeNode * 10 South Pl, London, United Kingdom  
+Accommodations: [hotels](https://skillsmatter.com/contact-us#hotels)   
+Website: [kubecon.io](https://www.kubecon.io/)   
+Twitter: [@KubeConio](https://twitter.com/kubeconio) #KubeCon
+Google is a proud Diamond sponsor of KubeCon EU 2016. Come to London next month, March 10th & 11th, and visit booth #13 to learn all about Kubernetes, Google Container Engine (GKE) and Google Cloud Platform!  
+-->
+会场地址：CodeNode * 英国伦敦南广场 10 号
+酒店住宿：[酒店](https://skillsmatter.com/contact-us)
+网站：[kubecon.io] (https://www.kubecon.io/)
+推特：[@KubeConio] (https://twitter.com/kubeconio)
+谷歌是 KubeCon EU 2016 的钻石赞助商。下个月 3 月 10 - 11 号来伦敦，参观 13 号展位，了解 Kubernetes，Google Container Engine（GKE），Google Cloud Platform 的所有信息!
+
+<!--
+_KubeCon is organized by KubeAcademy, LLC, a community-driven group of developers focused on the education of developers and the promotion of Kubernetes._  
+
+-* Sarah Novotny, Kubernetes Community Manager, Google  
+-->
+
+_KubeCon 是由 KubeAcademy、LLC 组织的，这是一个由社区驱动的开发者团体，专注于开发人员的教育和 kubernet.com 的推广
+-* Sarah Novotny, 谷歌的 Kubernetes 社区经理
+
@@ -1,3 +1,10 @@
+---
+title: " SIG-Networking: Kubernetes Network Policy APIs Coming in 1.3 "
+date: 2016-04-18
+slug: kubernetes-network-policy-apis
+url: /blog/2016/04/Kubernetes-Network-Policy-APIs
+---
+
 <!-- ---
 title: " SIG-Networking: Kubernetes Network Policy APIs Coming in 1.3 "
 date: 2016-04-18
@@ -5,13 +12,6 @@ slug: kubernetes-network-policy-apis
 url: /blog/2016/04/Kubernetes-Network-Policy-APIs
 --- -->

---
-title: "SIG-Networking: Kubernetes Network Policy APIs Coming in 1.3 "
-date: 2016-04-18
-slug: kubernetes-network-policy-apis
-url: /blog/2016/04/Kubernetes-Network-Policy-APIs
---
-
 <!-- _Editor’s note: This week we’re featuring [Kubernetes Special Interest Groups](https://github.com/kubernetes/kubernetes/wiki/Special-Interest-Groups-(SIGs)); Today’s post is by the Network-SIG team describing network policy APIs coming in 1.3 - policies for security, isolation and multi-tenancy._ -->

 编者按：这一周，我们的封面主题是 [Kubernetes 特别兴趣小组](https://github.com/kubernetes/kubernetes/wiki/Special-Interest-Groups-(SIGs))；今天的文章由网络兴趣小组撰写，来谈谈 1.3 版本中即将出现的网络策略 API - 针对安全，隔离和多租户的策略。
@@ -1,10 +1,3 @@
-<!-- ---
-title: " How to deploy secure, auditable, and reproducible Kubernetes clusters on AWS "
-date: 2016-04-15
-slug: kubernetes-on-aws_15
-url: /blog/2016/04/Kubernetes-On-Aws_15
--- -->
-
 ---
 title: " 如何在AWS上部署安全，可审计，可复现的k8s集群 "
 date: 2016-04-15
@@ -12,6 +5,13 @@ slug: kubernetes-on-aws_15
 url: /blog/2016/04/Kubernetes-On-Aws_15
 ---

+<!-- ---
+title: " How to deploy secure, auditable, and reproducible Kubernetes clusters on AWS "
+date: 2016-04-15
+slug: kubernetes-on-aws_15
+url: /blog/2016/04/Kubernetes-On-Aws_15
+--- -->
+
 <!-- _Today’s guest post is written by Colin Hom, infrastructure engineer at [CoreOS](https://coreos.com/), the company delivering Google’s Infrastructure for Everyone Else (#GIFEE) and running the world's containers securely on CoreOS Linux, Tectonic and Quay._

 _Join us at [CoreOS Fest Berlin](https://coreos.com/fest/), the Open Source Distributed Systems Conference, and learn more about CoreOS and Kubernetes._ -->
@@ -0,0 +1,72 @@
+---
+title: " Citrix + Kubernetes = 全垒打 "
+date: 2016-07-14
+slug: citrix-netscaler-and-kubernetes
+url: /blog/2016/07/Citrix-Netscaler-And-Kubernetes
+---
+
+<!--
+---
+title: " Citrix + Kubernetes = A Home Run "
+date: 2016-07-14
+slug: citrix-netscaler-and-kubernetes
+url: /blog/2016/07/Citrix-Netscaler-And-Kubernetes
+---
+-->
+
+<!--
+_Editor’s note: today’s guest post is by Mikko Disini, a Director of Product Management at Citrix Systems, sharing their collaboration experience on a Kubernetes integration.&nbsp;_  
+-->
+编者按：今天的客座文章来自 Citrix Systems 的产品管理总监 Mikko Disini，他分享了他们在 Kubernetes 集成上的合作经验。&nbsp;_ 
+
+<!--
+Technical collaboration is like sports. If you work together as a team, you can go down the homestretch and pull through for a win. That’s our experience with the Google Cloud Platform team.  
+-->
+技术合作就像体育运动。如果你能像一个团队一样合作，你就能在最后关头取得胜利。这就是我们对谷歌云平台团队的经验。
+
+<!--
+Recently, we approached Google Cloud Platform (GCP) to collaborate on behalf of Citrix customers and the broader enterprise market looking to migrate workloads.&nbsp;This migration required including the [NetScaler Docker load balancer](https://www.citrix.com/blogs/2016/06/20/the-best-docker-load-balancer-at-dockercon-in-seattle-this-week/), CPX, into Kubernetes nodes and resolving any issues with getting traffic into the CPX proxies. &nbsp;  
+-->
+最近，我们与 Google 云平台（GCP）联系，代表 Citrix 客户以及更广泛的企业市场，希望就工作负载的迁移进行协作。此迁移需要将 [NetScaler Docker 负载均衡器]https://www.citrix.com/blogs/2016/06/20/the-best-docker-load-balancer-at-dockercon-in-seattle-this-week/) CPX 包含到 Kubernetes 节点中，并解决将流量引入 CPX 代理的任何问题。  
+
+<!--
+**Why NetScaler and Kubernetes?**  
+-->
+
+**为什么是 NetScaler 和 Kubernetes**
+
+<!--
+1. Citrix customers want the same Layer 4 to Layer 7 capabilities from NetScaler that they have on-prem as they move to the cloud as they begin deploying their container and microservices architecture with Kubernetes&nbsp;
+2. Kubernetes provides a proven infrastructure for running containers and VMs with automated workload delivery
+3. NetScaler CPX provides Layer 4 to Layer 7 services and highly efficient telemetry data to a logging and analytics platform, [NetScaler Management and Analytics System](https://www.citrix.com/blogs/2016/05/24/introducing-the-next-generation-netscaler-management-and-analytics-system/)
+-->
+
+1. Citrix 的客户希望他们开始使用 Kubernetes 部署他们的容器和微服务体系结构时，能够像当初迁移到云计算时一样，享有 NetScaler 所提供的第 4 层到第 7 层能力&nbsp;
+2. Kubernetes 提供了一套经过验证的基础设施，可用来运行容器和虚拟机，并自动交付工作负载；  
+3. NetScaler CPX 提供第 4 层到第 7 层的服务，并为日志和分析平台 [NetScaler 管理和分析系统](https://www.citrix.com/blogs/2016/05/24/introducing-the-next-generation-netscaler-management-and-analytics-system/) 提供高效的度量数据。
+
+<!--
+I wish all our experiences working together with a technical partner were as good as working with GCP. We had a list of issues to enable our use cases and were able to collaborate swiftly on a solution. To resolve these, GCP team offered in depth technical assistance, working with Citrix such that NetScaler CPX can spin up and take over as a client-side proxy running on each host.&nbsp;  
+-->
+我希望我们所有与技术合作伙伴一起工作的经验都能像与 GCP 一起工作一样好。我们有一个列表，包含支持我们的用例所需要解决的问题。我们能够快速协作形成解决方案。为了解决这些问题，GCP 团队提供了深入的技术支持，与 Citrix 合作，从而使得 NetScaler CPX 能够在每台主机上作为客户端代理启动运行。
+
+<!--
+Next, NetScaler CPX needed to be inserted in the data path of GCP ingress load balancer so that NetScaler CPX can spread traffic to front end web servers. The NetScaler team made modifications so that NetScaler CPX listens to API server events and configures itself to create a VIP, IP table rules and server rules to take ingress traffic and load balance across front end applications. Google Cloud Platform team provided feedback and assistance to verify modifications made to overcome the technical hurdles. Done!  
+-->
+接下来，需要在 GCP 入口负载均衡器的数据路径中插入 NetScaler CPX，使 NetScaler CPX 能够将流量分散到前端 web 服务器。NetScaler 团队进行了修改，以便 NetScaler CPX 监听 API 服务器事件，并配置自己来创建 VIP、IP 表规则和服务器规则，以便跨前端应用程序接收流量和负载均衡。谷歌云平台团队提供反馈和帮助，验证为克服技术障碍所做的修改。完成了!
+
+<!--
+NetScaler CPX use case is supported in [Kubernetes 1.3](https://kubernetes.io/blog/2016/07/kubernetes-1.3-bridging-cloud-native-and-enterprise-workloads). Citrix customers and the broader enterprise market will have the opportunity to leverage NetScaler with Kubernetes, thereby lowering the friction to move workloads to the cloud.&nbsp;  
+-->
+NetScaler CPX 用例在 [Kubernetes 1.3](https://kubernetes.io/blog/2016/07/kubernets-1.3 - bridge -cloud-native-and-enterprise-workload) 中提供支持。Citrix 的客户和更广泛的企业市场将有机会基于 Kubernetes 享用 NetScaler 服务，从而降低将工作负载转移到云平台的阻力。&nbsp;
+
+<!--
+You can learn more about&nbsp;NetScaler CPX [here](https://www.citrix.com/networking/microservices.html).  
+-->
+您可以在[此处](https://www.citrix.com/networking/microservices.html)了解有关 NetScaler CPX 的更多信息。
+
+<!--
+_&nbsp;-- Mikko Disini, Director of Product Management - NetScaler, Citrix Systems_
+-->
+_&nbsp;-- Mikko Disini，Citrix Systems NetScaler 产品管理总监
+
@@ -0,0 +1,72 @@
+---
+title: " Kubernetes 1.8 的五天 "
+date: 2017-10-24
+slug: five-days-of-kubernetes-18
+url: /blog/2017/10/Five-Days-Of-Kubernetes-18
+---
+
+<!--
+---
+title: " Five Days of Kubernetes 1.8 "
+date: 2017-10-24
+slug: five-days-of-kubernetes-18
+url: /blog/2017/10/Five-Days-Of-Kubernetes-18
+---
+-->
+
+<!--
+Kubernetes 1.8 is live, made possible by hundreds of contributors pushing thousands of commits in this latest releases.  
+-->
+Kubernetes 1.8 是现场直播，数百名贡献者在这个最新版本中推出了成千上万的提交。
+
+<!--
+The community has tallied more than 66,000 commits in the main repo and continues rapid growth outside of the main repo, which signals growing maturity and stability for the project. The community has logged more than 120,000 commits across all repos and 17,839 commits across all repos for v1.7.0 to v1.8.0 alone.  
+-->
+社区已经有超过 66,000 个提交在主仓库，并在主仓库之外继续快速增长，这标志着该项目日益成熟和稳定。仅 v1.7.0 到 v1.8.0，社区就记录了所有仓库的超过 120,000 次提交和 17839 次提交。
+
+<!--
+With the help of our growing community of 1,400 plus contributors, we issued more than 3,000 PRs and pushed more than 5,000 commits to deliver Kubernetes 1.8 with significant security and workload support updates. This all points to increased stability, a result of our project-wide focus on maturing [process](https://github.com/kubernetes/sig-release), formalizing [architecture](https://github.com/kubernetes/community/tree/master/sig-architecture), and strengthening Kubernetes’ [governance model](https://github.com/kubernetes/community/tree/master/community/elections/2017).  
+-->
+在拥有 1400 多名贡献者，并且不断发展壮大的社区的帮助下，我们合并了 3000 多个 PR，并发布了 5000 多个提交，最后的 Kubernetes 1.8 在安全和工作负载方面添加了很多的更新。
+这一切都表明稳定性的提高，这是我们整个项目关注成熟[流程](https://github.com/kubernetes/sig-release)、形式化[架构](https://github.com/kubernetes/community/tree/master/sig-architecture)和加强 Kubernetes 的[治理模型](https://github.com/kubernetes/community/tree/master/community/elections/2017)的结果。
+
+<!--
+While many improvements have been contributed, we highlight key features in this series of in-depth&nbsp;posts listed below. [Follow along](https://twitter.com/kubernetesio) and see what’s new and improved with storage, security and more.  
+-->
+虽然有很多改进，但我们在下面列出的这一系列深度文章中突出了一些关键特性。[跟随](https://twitter.com/kubernetesio)并了解存储，安全等方面的新功能和改进功能。
+
+<!--
+**Day 1:** [5 Days of Kubernetes 1.8](https://kubernetes.io/blog/2017/10/five-days-of-kubernetes-18)  
+**Day 2:** [kubeadm v1.8 Introduces Easy Upgrades for Kubernetes Clusters](https://kubernetes.io/blog/2017/10/kubeadm-v18-released)  
+**Day 3:** [Kubernetes v1.8 Retrospective: It Takes a Village to Raise a Kubernetes](https://kubernetes.io/blog/2017/10/it-takes-village-to-raise-kubernetes)
+**Day 4:** [Using RBAC, Generally Available in Kubernetes v1.8](https://kubernetes.io/blog/2017/10/using-rbac-generally-available-18)  
+**Day 5:** [Enforcing Network Policies in Kubernetes](https://kubernetes.io/blog/2017/10/enforcing-network-policies-in-kubernetes)  
+-->
+
+**第一天：** [Kubernetes 1.8 的五天](https://kubernetes.io/blog/2017/10/five-days-of-kubernetes-18)  
+**第二天：** [kubeadm v1.8 为 Kubernetes 集群引入了简单的升级](https://kubernetes.io/blog/2017/10/kubeadm-v18-released)  
+**第三天：** [Kubernetes v1.8 回顾：提升一个 Kubernetes 需要一个 Village](https://kubernetes.io/blog/2017/10/it-takes-village-to-raise-kubernetes)
+**第四天：** [使用 RBAC，一般在 Kubernetes v1.8 中提供](https://kubernetes.io/blog/2017/10/using-rbac-generally-available-18)  
+**第五天：** [在 Kubernetes 执行网络策略](https://kubernetes.io/blog/2017/10/enforcing-network-policies-in-kubernetes)  
+
+<!--
+**Connect**  
+-->
+
+**链接**  
+
+<!--
+- Post questions (or answer questions) on [Stack Overflow](http://stackoverflow.com/questions/tagged/kubernetes)
+- Join the community portal for advocates on [K8sPort](http://k8sport.org/)
+- Follow us on Twitter [@Kubernetesio](https://twitter.com/kubernetesio) for latest updates&nbsp;
+- Connect with the community on [Slack](http://slack.k8s.io/)
+- Get involved with the Kubernetes project on [GitHub](https://github.com/kubernetes/kubernetes)
+-->
+
+- 在 [Stack Overflow](http://stackoverflow.com/questions/tagged/kubernetes) 上发布问题（或回答问题）
+- 加入 [K8sPort](http://k8sport.org/) 布道师的社区门户网站
+- 在 Twitter [@Kubernetesio](https://twitter.com/kubernetesio) 关注我们以获取最新更新
+- 与 [Slack](http://slack.k8s.io/) 上的社区联系
+- 参与 [GitHub](https://github.com/kubernetes/kubernetes) 上的 Kubernetes 项目 
+
+
@@ -0,0 +1,32 @@
+---
+title: " Kubernetes 中自动缩放 "
+date: 2017-11-17
+slug: autoscaling-in-kubernetes
+url: /blog/2017/11/Autoscaling-In-Kubernetes
+---
+
+<!--
+---
+title: " Autoscaling in Kubernetes "
+date: 2017-11-17
+slug: autoscaling-in-kubernetes
+url: /blog/2017/11/Autoscaling-In-Kubernetes
+---
+-->
+
+<!--
+Kubernetes allows developers to automatically adjust cluster sizes and the number of pod replicas based on current traffic and load. These adjustments reduce the amount of unused nodes, saving money and resources. In this talk, Marcin Wielgus of Google walks you through the current state of pod and node autoscaling in Kubernetes: .how it works, and how to use it, including best practices for deployments in production applications.  
+-->
+Kubernetes 允许开发人员根据当前的流量和负载自动调整集群大小和 pod 副本的数量。这些调整减少了未使用节点的数量，节省了资金和资源。
+在这次演讲中，谷歌的 Marcin Wielgus 将带领您了解 Kubernetes 中 pod 和 node 自动调焦的当前状态：它是如何工作的，以及如何使用它，包括在生产应用程序中部署的最佳实践。
+
+<!--
+Enjoyed this talk? Join us for more exciting sessions on scaling and automating your Kubernetes clusters at KubeCon in Austin on December 6-8. [Register Now](https://www.eventbrite.com/e/kubecon-cloudnativecon-north-america-registration-37824050754?_ga=2.9666039.317115486.1510003873-1623727562.1496428006)  
+-->
+喜欢这个演讲吗？ 12 月 6 日至 8 日，在 Austin 参加 KubeCon 关于扩展和自动化您的 Kubernetes 集群的更令人兴奋的会议。[现在注册](https://www.eventbrite.com/e/kubecon-cloudnativecon-north-america-registration-37824050754?_ga=2.9666039.317115486.1510003873-1623727562.1496428006)。
+
+<!--
+Be sure to check out [Automating and Testing Production Ready Kubernetes Clusters in the Public Cloud](http://sched.co/CU64) by Ron Lipke, Senior Developer, Platform as a Service, Gannet/USA Today Network.
+-->
+一定要查看由 Ron Lipke， Gannet/USA Today Network, 平台即服务高级开发人员，在[公共云中自动化和测试产品就绪的 Kubernetes 集群](http://sched.co/CU64)。
+
@@ -0,0 +1,728 @@
+---
+title: 在 Kubernetes 上开发
+date: 2018-05-01
+slug: developing-on-kubernetes
+---
+
+<!--
+---
+title: Developing on Kubernetes
+date: 2018-05-01
+slug: developing-on-kubernetes
+---
+-->
+
+<!--**Authors**:-->
+**作者**： [Michael Hausenblas](https://twitter.com/mhausenblas) (Red Hat), [Ilya Dmitrichenko](https://twitter.com/errordeveloper) (Weaveworks)
+
+<!-- 
+How do you develop a Kubernetes app? That is, how do you write and test an app that is supposed to run on Kubernetes? This article focuses on the challenges, tools and methods you might want to be aware of to successfully write Kubernetes apps alone or in a team setting. 
+-->
+
+您将如何开发一个 Kubernates 应用？也就是说，您如何编写并测试一个要在 Kubernates 上运行的应用程序？本文将重点介绍在独自开发或者团队协作中，您可能希望了解到的为了成功编写 Kubernetes 应用程序而需面临的挑战，工具和方法。
+
+<!--
+We’re assuming you are a developer, you have a favorite programming language, editor/IDE, and a testing framework available. The overarching goal is to introduce minimal changes to your current workflow when developing the app for Kubernetes. For example, if you’re a Node.js developer and are used to a hot-reload setup—that is, on save in your editor the running app gets automagically updated—then dealing with containers and container images, with container registries, Kubernetes deployments, triggers, and more can not only be overwhelming but really take all the fun out if it.
+-->
+
+我们假定您是一位开发人员，有您钟爱的编程语言，编辑器/IDE（集成开发环境），以及可用的测试框架。在针对 Kubernates 开发应用时，最重要的目标是减少对当前工作流程的影响，改变越少越好，尽量做到最小。举个例子，如果您是 Node.js 开发人员，习惯于那种热重载的环境 - 也就是说您在编辑器里一做保存，正在运行的程序就会自动更新 - 那么跟容器、容器镜像或者镜像仓库打交道，又或是跟 Kubernetes 部署、triggers 以及更多头疼东西打交道，不仅会让人难以招架也真的会让开发过程完全失去乐趣。
+
+<!--
+In the following, we’ll first discuss the overall development setup, then review tools of the trade, and last but not least do a hands-on walkthrough of three exemplary tools that allow for iterative, local app development against Kubernetes.
+-->
+
+在下文中，我们将首先讨论 Kubernetes 总体开发环境，然后回顾常用工具，最后进行三个示例性工具的实践演练。这些工具允许针对 Kubernetes 进行本地应用程序的开发和迭代。
+
+<!--
+## Where to run your cluster?
+-->
+
+## 您的集群运行在哪里？
+
+<!--
+As a developer you want to think about where the Kubernetes cluster you’re developing against runs as well as where the development environment sits. Conceptually there are four development modes:
+-->
+
+作为开发人员，您既需要考虑所针对开发的 Kubernetes 集群运行在哪里，也需要思考开发环境如何配置。概念上，有四种开发模式：
+
+![Dev Modes](/images/blog/2018-05-01-developing-on-kubernetes/dok-devmodes_preview.png)
+
+<!--
+A number of tools support pure offline development including Minikube, Docker for Mac/Windows, Minishift, and the ones we discuss in detail below. Sometimes, for example, in a microservices setup where certain microservices already run in the cluster, a proxied setup (forwarding traffic into and from the cluster) is preferable and Telepresence is an example tool in this category. The live mode essentially means you’re building and/or deploying against a remote cluster and, finally, the pure online mode means both your development environment and the cluster are remote, as this is the case with, for example, [Eclipse Che](https://www.eclipse.org/che/docs/kubernetes-single-user.html) or [Cloud 9](https://github.com/errordeveloper/k9c). Let’s now have a closer look at the basics of offline development: running Kubernetes locally.
+-->
+
+许多工具支持纯 offline 开发，包括 Minikube、Docker（Mac 版/Windows 版）、Minishift 以及下文中我们将详细讨论的几种。有时，比如说在一个微服务系统中，已经有若干微服务在运行，proxied 模式（通过转发把数据流传进传出集群）就非常合适，Telepresence 就是此类工具的一个实例。live 模式，本质上是您基于一个远程集群进行构建和部署。最后，纯 online 模式意味着您的开发环境和运行集群都是远程的，典型的例子是 [Eclipse Che](https://www.eclipse.org/che/docs/kubernetes-single-user.html) 或者 [Cloud 9](https://github.com/errordeveloper/k9c)。现在让我们仔细看看离线开发的基础：在本地运行 Kubernetes。
+
+<!--
+[Minikube](/docs/getting-started-guides/minikube/) is a popular choice for those who prefer to run Kubernetes in a local VM. More recently Docker for [Mac](https://docs.docker.com/docker-for-mac/kubernetes/) and [Windows](https://docs.docker.com/docker-for-windows/kubernetes/) started shipping Kubernetes as an experimental package (in the “edge” channel). Some reasons why you may want to prefer using Minikube over the Docker desktop option are:
+-->
+
+[Minikube](/docs/getting-started-guides/minikube/) 在更加喜欢于本地 VM 上运行 Kubernetes 的开发人员中，非常受欢迎。不久前，Docker 的 [Mac](https://docs.docker.com/docker-for-mac/kubernetes/) 版和 [Windows](https://docs.docker.com/docker-for-windows/kubernetes/) 版，都试验性地开始自带 Kubernetes（需要下载 “edge” 安装包）。在两者之间，以下原因也许会促使您选择 Minikube 而不是 Docker 桌面版：
+
+<!--
+* You already have Minikube installed and running
+* You prefer to wait until Docker ships a stable package
+* You’re a Linux desktop user
+* You are a Windows user who doesn’t have Windows 10 Pro with Hyper-V
+-->
+
+* 您已经安装了 Minikube 并且它运行良好
+* 您想等到 Docker 出稳定版本
+* 您是 Linux 桌面用户
+* 您是 Windows 用户，但是没有配有 Hyper-V 的 Windows 10 Pro
+
+<!--
+Running a local cluster allows folks to work offline and that you don’t have to pay for using cloud resources. Cloud provider costs are often rather affordable and free tiers exists, however some folks prefer to avoid having to approve those costs with their manager as well as potentially incur unexpected costs, for example, when leaving cluster running over the weekend.
+-->
+
+运行一个本地集群，开发人员可以离线工作，不用支付云服务。云服务收费一般不会太高，并且免费的等级也有，但是一些开发人员不喜欢为了使用云服务而必须得到经理的批准，也不愿意支付意想不到的费用，比如说忘了下线而集群在周末也在运转。
+
+<!--
+Some developers prefer to use a remote Kubernetes cluster, and this is usually to allow for larger compute and storage capacity and also enable collaborative workflows more easily. This means it’s easier for you to pull in a colleague to help with debugging or share access to an app in the team. Additionally, for some developers it can be critical to mirror production environment as closely as possible, especially when it comes down to external cloud services, say,  proprietary databases, object stores, message queues, external load balancer, or mail delivery systems.
+-->
+
+有些开发人员却更喜欢远程的 Kubernetes 集群，这样他们通常可以获得更大的计算能力和存储容量，也简化了协同工作流程。您可以更容易的拉上一个同事来帮您调试，或者在团队内共享一个应用的使用。再者，对某些开发人员来说，尽可能的让开发环境类似生产环境至关重要，尤其是您依赖外部厂商的云服务时，如：专有数据库、云对象存储、消息队列、外商的负载均衡器或者邮件投递系统。
+
+<!--
+In summary, there are good reasons for you to develop against a local cluster as well as a remote one. It very much depends on in which phase you are: from early prototyping and/or developing alone to integrating a set of more stable microservices.
+-->
+
+总之，无论您选择本地或者远程集群，理由都足够多。这很大程度上取决于您所处的阶段：从早期的原型设计/单人开发到后期面对一批稳定微服务的集成。
+
+<!--
+Now that you have a basic idea of the options around the runtime environment, let’s move on to how to iteratively develop and deploy your app.
+-->
+
+既然您已经了解到运行环境的基本选项，那么我们就接着讨论如何迭代式的开发并部署您的应用。
+
+<!--
+## The tools of the trade
+-->
+
+## 常用工具
+
+<!--
+We are now going to review tooling allowing you to develop apps on Kubernetes with the focus on having minimal impact on your existing workflow. We strive to provide an unbiased description including implications of using each of the tools in general terms.
+-->
+
+我们现在回顾既可以允许您可以在 Kubernetes 上开发应用程序又尽可能最小地改变您现有的工作流程的一些工具。我们致力于提供一份不偏不倚的描述，也会提及使用某个工具将会意味着什么。
+
+<!--
+Note that this is a tricky area since even for established technologies such as, for example, JSON vs YAML vs XML or REST vs gRPC vs SOAP a lot depends on your background, your preferences and organizational settings. It’s even harder to compare tooling in the Kubernetes ecosystem as things evolve very rapidly and new tools are announced almost on a weekly basis; during the preparation of this post alone, for example, [Gitkube](https://gitkube.sh/) and [Watchpod](https://github.com/MinikubeAddon/watchpod) came out. To cover these new tools as well as related, existing tooling such as [Weave Flux](https://github.com/weaveworks/flux) and OpenShift’s [S2I](https://docs.openshift.com/container-platform/3.9/creating_images/s2i.html) we are planning a follow-up blog post to the one you’re reading.
+-->
+
+请注意这很棘手，因为即使在成熟定型的技术中做选择，比如说在 JSON、YAML、XML、REST、gRPC 或者 SOAP 之间做选择，很大程度也取决于您的背景、喜好以及公司环境。在 Kubernetes 生态系统内比较各种工具就更加困难，因为技术发展太快，几乎每周都有新工具面市；举个例子，仅在准备这篇博客的期间，[Gitkube](https://gitkube.sh/) 和 [Watchpod](https://github.com/MinikubeAddon/watchpod) 相继出品。为了进一步覆盖到这些新的，以及一些相关的已推出的工具，例如 [Weave Flux](https://github.com/weaveworks/flux) 和 OpenShift 的 [S2I](https://docs.openshift.com/container-platform/3.9/creating_images/s2i.html)，我们计划再写一篇跟进的博客。
+
+### Draft
+
+
+<!--
+[Draft](https://github.com/Azure/draft) aims to help you get started deploying any app to Kubernetes. It is capable of applying heuristics as to what programming language your app is written in and generates a Dockerfile along with a Helm chart. It then runs the build for you and deploys resulting image to the target cluster via the Helm chart. It also allows user to setup port forwarding to localhost very easily.
+-->
+
+[Draft](https://github.com/Azure/draft) 旨在帮助您将任何应用程序部署到 Kubernetes。它能够检测到您的应用所使用的编程语言，并且生成一份 Dockerfile 和 Helm 图表。然后它替您启动构建并且依照 Helm 图表把所生产的镜像部署到目标集群。它也可以让您很容易地设置到 localhost 的端口映射。
+
+<!--
+Implications:
+-->
+
+这意味着：
+
+<!--
+* User can customise the chart and Dockerfile templates however they like, or even create a [custom pack](https://github.com/Azure/draft/blob/master/docs/reference/dep-003.md) (with Dockerfile, the chart and more) for future use
+-->
+* 用户可以任意地自定义 Helm 图表和 Dockerfile 模版，或者甚至创建一个 [custom pack](https://github.com/Azure/draft/blob/master/docs/reference/dep-003.md)（使用 Dockerfile、Helm 图表以及其他）以备后用
+
+<!--
+* It’s not very simple to guess how just any app is supposed to be built, in some cases user may need to tweak Dockerfile and the Helm chart that Draft generates
+-->
+* 要想理解一个应用应该怎么构建并不容易，在某些情况下，用户也许需要修改 Draft 生成的 Dockerfile 和 Heml 图表
+
+<!--
+* With [Draft version 0.12.0](https://github.com/Azure/draft/releases/tag/v0.12.0) or older, every time user wants to test a change, they need to wait for Draft to copy the code to the cluster, then run the build, push the image and release updated chart; this can timely, but it results in an image being for every single change made by the user (whether it was committed to git or not)
+-->
+* 如果使用 [Draft version 0.12.0](https://github.com/Azure/draft/releases/tag/v0.12.0)<sup>1</sup> 或者更老版本，每一次用户想要测试一个改动，他们需要等 Draft 把代码拷贝到集群，运行构建，推送镜像并且发布更新后的图表；这些步骤可能进行得很快，但是每一次用户的改动都会产生一个镜像（无论是否提交到 git ）
+
+<!--
+* As of Draft version 0.12.0, builds are executed locally
+* User doesn’t have an option to choose something other than Helm for deployment
+* It can watch local changes and trigger deployments, but this feature is not enabled by default
+-->
+* 在 Draft 0.12.0版本，构建是本地进行的
+* 用户不能选择 Helm 以外的工具进行部署
+* 它可以监控本地的改动并且触发部署，但是这个功能默认是关闭的
+
+<!--
+* It allows developer to use either local or remote Kubernetes cluster
+* Deploying to production is up to the user, Draft authors recommend their other project – Brigade
+* Can be used instead of Skaffold, and along the side of Squash
+-->
+* 它允许开发人员使用本地或者远程的 Kubernates 集群
+* 如何部署到生产环境取决于用户， Draft 的作者推荐了他们的另一个项目 - Brigade
+* 可以代替 Skaffold， 并且可以和 Squash 一起使用
+
+<!--
+More info:
+-->
+
+更多信息：
+
+* [Draft: Kubernetes container development made easy](https://kubernetes.io/blog/2017/05/draft-kubernetes-container-development)
+* [Getting Started Guide](https://github.com/Azure/draft/blob/master/docs/getting-started.md)
+
+【1】：此处疑为 0.11.0，因为 0.12.0 已经支持本地构建，见下一条
+
+### Skaffold
+
+<!--
+[Skaffold](https://github.com/GoogleCloudPlatform/skaffold) is a tool that aims to provide portability for CI integrations with different build system, image registry and deployment tools. It is different from Draft, yet somewhat comparable. It has a basic capability for generating manifests, but it’s not a prominent feature. Skaffold is extendible and lets user pick tools for use in each of the steps in building and deploying their app.
+-->
+
+[Skaffold](https://github.com/GoogleCloudPlatform/skaffold) 让 CI 集成具有可移植性的，它允许用户采用不同的构建系统，镜像仓库和部署工具。它不同于 Draft，同时也具有一定的可比性。它具有生成系统清单的基本能力，但那不是一个重要功能。Skaffold 易于扩展，允许用户在构建和部署应用的每一步选取相应的工具。
+
+<!--
+Implications:
+-->
+
+这意味着：
+
+<!--
+* Modular by design
+* Works independently of CI vendor, user doesn’t need Docker or Kubernetes plugin
+* Works without CI as such, i.e. from the developer’s laptop
+* It can watch local changes and trigger deployments
+-->
+* 模块化设计
+* 不依赖于 CI，用户不需要 Docker 或者 Kubernetes 插件
+* 没有 CI 也可以工作，也就是说，可以在开发人员的电脑上工作
+* 它可以监控本地的改动并且触发部署
+
+<!--
+* It allows developer to use either local or remote Kubernetes cluster
+* It can be used to deploy to production, user can configure how exactly they prefer to do it and provide different kind of pipeline for each target environment
+* Can be used instead of Draft, and along the side with most other tools
+-->
+* 它允许开发人员使用本地或者远程的 Kubernetes 集群
+* 它可以用于部署生产环境，用户可以精确配置，也可以为每一套目标环境提供不同的生产线
+* 可以代替 Draft，并且和其他工具一起使用
+
+<!--
+More info:
+-->
+
+更多信息：
+
+* [Introducing Skaffold: Easy and repeatable Kubernetes development](https://cloudplatform.googleblog.com/2018/03/introducing-Skaffold-Easy-and-repeatable-Kubernetes-development.html)
+* [Getting Started Guide](https://github.com/GoogleCloudPlatform/skaffold#getting-started-with-local-tooling)
+
+### Squash
+
+<!--
+[Squash](https://github.com/solo-io/squash) consists of a debug server that is fully integrated with Kubernetes, and a IDE plugin. It allows you to insert breakpoints and do all the fun stuff you are used to doing when debugging an application using an IDE. It bridges IDE debugging experience with your Kubernetes cluster by allowing you to attach the debugger to a pod running in your Kubernetes cluster.
+-->
+[Squash](https://github.com/solo-io/squash) 包含一个与 Kubernetes 全面集成的调试服务器，以及一个 IDE 插件。它允许您插入断点和所有的调试操作，就像您所习惯的使用 IDE 调试一个程序一般。它允许您将调试器应用到 Kubernetes 集群中运行的 pod 上，从而让您可以使用 IDE 调试 Kubernetes 集群。
+
+<!--
+Implications:
+-->
+
+这意味着：
+
+<!--
+* Can be used independently of other tools you chose
+* Requires a privileged DaemonSet
+* Integrates with popular IDEs
+* Supports Go, Python, Node.js, Java and gdb
+-->
+* 不依赖您选择的其它工具
+* 需要一组特权 DaemonSet
+* 可以和流行 IDE 集成
+* 支持 Go、Python、Node.js、Java 和 gdb
+
+<!--
+* User must ensure application binaries inside the container image are compiled with debug symbols
+* Can be used in combination with any other tools described here
+* It can be used with either local or remote Kubernetes cluster
+-->
+* 用户必须确保容器中的应用程序使编译时使用了调试符号
+* 可与此处描述的任何其他工具结合使用
+* 它可以与本地或远程 Kubernetes 集群一起使用
+
+<!--
+More info:
+-->
+
+更多信息：
+
+* [Squash: A Debugger for Kubernetes Apps](https://www.youtube.com/watch?v=5TrV3qzXlgI)
+* [Getting Started Guide](https://github.com/solo-io/squash/blob/master/docs/getting-started.md)
+
+### Telepresence
+
+<!--
+[Telepresence](https://www.telepresence.io/) connects containers running on developer’s workstation with a remote Kubernetes cluster using a two-way proxy and emulates in-cluster environment as well as provides access to config maps and secrets. It aims to improve iteration time for container app development by eliminating the need for deploying app to the cluster and leverages local container to abstract network and filesystem interface in order to make it appear as if the app was running in the cluster.
+-->
+[Telepresence](https://www.telepresence.io/) 使用双向代理将开发人员工作站上运行的容器与远程 Kubernetes 集群连接起来，并模拟集群内环境以及提供对配置映射和机密的访问。它消除了将应用部署到集群的需要，并利用本地容器抽象出网络和文件系统接口，以使其看起来应用好像就在集群中运行，从而改进容器应用程序开发的迭代时间。
+
+<!--
+Implications:
+-->
+
+这意味着：
+
+<!--
+* It can be used independently of other tools you chose
+* Using together with Squash is possible, although Squash would have to be used for pods in the cluster, while conventional/local debugger would need to be used for debugging local container that’s connected to the cluster via Telepresence
+* Telepresence imposes some network latency
+-->
+* 它不依赖于其它您选取的工具
+* 可以同 Squash 一起使用，但是 Squash 必须用于调试集群中的 pods，而传统/本地调试器需要用于调试通过 Telepresence 连接到集群的本地容器
+* Telepresence 会产生一些网络延迟
+
+<!--
+* It provides connectivity via a side-car process - sshuttle, which is based on SSH
+* More intrusive dependency injection mode with LD_PRELOAD/DYLD_INSERT_LIBRARIES is also available
+* It is most commonly used with a remote Kubernetes cluster, but can be used with a local one also
+-->
+* 它通过辅助进程提供连接 -  sshuttle，基于SSH的一个工具
+* 还提供了使用 LD_PRELOAD/DYLD_INSERT_LIBRARIES 的更具侵入性的依赖注入模式
+* 它最常用于远程 Kubernetes 集群，但也可以与本地集群一起使用
+
+<!--
+More info:
+-->
+
+更多信息：
+
+* [Telepresence: fast, realistic local development for Kubernetes microservices](https://www.telepresence.io/)
+* [Getting Started Guide](https://www.telepresence.io/tutorials/docker)
+* [How It Works](https://www.telepresence.io/discussion/how-it-works)
+
+### Ksync
+
+<!--
+[Ksync](https://github.com/vapor-ware/ksync) synchronizes application code (and configuration) between your local machine and the container running in Kubernetes, akin to what [oc rsync](https://docs.openshift.com/container-platform/3.9/dev_guide/copy_files_to_container.html) does in OpenShift. It aims to improve iteration time for app development by eliminating build and deployment steps.
+-->
+
+
+[Ksync](https://github.com/vapor-ware/ksync) 在本地计算机和运行在 Kubernetes 中的容器之间同步应用程序代码（和配置），类似于 [oc rsync](https://docs.openshift.com/container-platform/3.9/dev_guide/copy_files_to_container.html) 在 OpenShift 中的角色。它旨在通过消除构建和部署步骤来缩短应用程序开发的迭代时间。
+
+
+<!--
+Implications:
+-->
+
+这意味着：
+
+<!--
+* It bypasses container image build and revision control
+* Compiled language users have to run builds inside the pod (TBC)
+* Two-way sync – remote files are copied to local directory
+* Container is restarted each time remote filesystem is updated
+* No security features – development only
+-->
+* 它绕过容器图像构建和修订控制
+* 使用编译语言的用户必须在 pod（TBC）内运行构建
+* 双向同步 - 远程文件会复制到本地目录
+* 每次更新远程文件系统时都会重启容器
+* 无安全功能 - 仅限开发
+
+<!--
+* Utilizes [Syncthing](https://github.com/syncthing/syncthing), a Go library for peer-to-peer sync
+* Requires a privileged DaemonSet running in the cluster
+* Node has to use Docker with overlayfs2 – no other CRI implementations are supported at the time of writing
+-->
+* 使用 [Syncthing](https://github.com/syncthing/syncthing)，一个用于点对点同步的 Go 语言库
+* 需要一个在集群中运行的特权 DaemonSet
+* Node 必须使用带有 overlayfs2 的 Docker  - 在写作本文时，尚不支持其他 CRI 实现
+
+<!--
+More info:
+-->
+
+更多信息：
+
+* [Getting Started Guide](https://github.com/vapor-ware/ksync#getting-started)
+* [How It Works](https://github.com/vapor-ware/ksync/blob/master/docs/architecture.md)
+* [Katacoda scenario to try out ksync in your browser](https://www.katacoda.com/vaporio/scenarios/ksync)
+* [Syncthing Specification](https://docs.syncthing.net/specs/)
+
+<!--
+## Hands-on walkthroughs
+-->
+
+## 实践演练
+
+
+<!--
+The app we will be using for the hands-on walkthroughs of the tools in the following is a simple [stock market simulator](https://github.com/kubernauts/dok-example-us), consisting of two microservices:
+-->
+
+我们接下来用于练习使用工具的应用是一个简单的[股市模拟器](https://github.com/kubernauts/dok-example-us)，包含两个微服务：
+
+<!--
+* The `stock-gen` microservice is written in Go and generates stock data randomly and exposes it via HTTP endpoint `/stockdata`.
+‎* A second microservice, `stock-con` is a Node.js app that consumes the stream of stock data from `stock-gen` and provides an aggregation in form of a moving average via the HTTP endpoint `/average/$SYMBOL` as well as a health-check endpoint at `/healthz`.
+-->
+
+* `stock-gen`（股市数据生成器）微服务是用 Go 编写的，随机生成股票数据并通过 HTTP 端点 `/ stockdata` 公开
+* 第二个微服务，`stock-con`（股市数据消费者）是一个 Node.js 应用程序，它使用来自 `stock-gen` 的股票数据流，并通过 HTTP 端点 `/average/$SYMBOL` 提供股价移动平均线，也提供一个健康检查端点 `/healthz`。
+
+<!--
+Overall, the default setup of the app looks as follows:
+-->
+
+总体上，此应用的默认配置如下图所示：
+
+![Default Setup](/images/blog/2018-05-01-developing-on-kubernetes/dok-architecture_preview.png)
+
+<!--
+In the following we’ll do a hands-on walkthrough for a representative selection of tools discussed above: ksync, Minikube with local build, as well as Skaffold. For each of the tools we do the following:
+-->
+
+在下文中，我们将选取以上讨论的代表性工具进行实践演练：ksync，具有本地构建的 Minikube 以及 Skaffold。对于每个工具，我们执行以下操作：
+
+<!--
+* Set up the respective tool incl. preparations for the deployment and local consumption of the `stock-con` microservice.
+* Perform a code update, that is, change the source code of the `/healthz` endpoint in the `stock-con` microservice and observe the updates.
+-->
+
+* 设置相应的工具，包括部署准备和 `stock-con` 微服务数据的本地读取
+* 执行代码更新，即更改 `stock-con` 微服务的 `/healthz` 端点的源代码并观察网页刷新
+
+<!--
+Note that for the target Kubernetes cluster we’ve been using Minikube locally, but you can also a remote cluster for ksync and Skaffold if you want to follow along.
+-->
+
+请注意，我们一直使用 Minikube 的本地 Kubernetes 集群，但是您也可以使用 ksync 和 Skaffold 的远程集群跟随练习。
+
+<!--
+### Walkthrough: ksync
+-->
+
+### 实践演练：ksync
+
+<!--
+As a preparation, install [ksync](https://vapor-ware.github.io/ksync/#installation) and then carry out the following steps to prepare the development setup:
+-->
+
+作为准备，安装 [ksync](https://vapor-ware.github.io/ksync/#installation)，然后执行以下步骤配置开发环境：
+
+```
+$ mkdir -p $(pwd)/ksync
+$ kubectl create namespace dok
+$ ksync init -n dok
+```
+<!--
+With the basic setup completed we're ready to tell ksync’s local client to watch a certain Kubernetes namespace and then we create a spec to define what we want to sync (the directory `$(pwd)/ksync` locally with `/app` in the container). Note that target pod is specified via the selector parameter:
+-->
+
+
+完成基本设置后，我们可以告诉 ksync 的本地客户端监控 Kubernetes 的某个命名空间，然后我们创建一个规范来定义我们想要同步的文件夹（本地的 `$(pwd)/ksync` 和容器中的 `/ app` ）。请注意，目标 pod 是用 selector 参数指定：
+
+```
+$ ksync watch -n dok
+$ ksync create -n dok --selector=app=stock-con $(pwd)/ksync /app
+$ ksync get -n dok
+```
+
+<!--
+Now we deploy the stock generator and the stock consumer microservice:
+-->
+
+现在我们部署股价数据生成器和股价数据消费者微服务：
+
+```
+$ kubectl -n=dok apply \
+      -f https://raw.githubusercontent.com/kubernauts/dok-example-us/master/stock-gen/app.yaml
+$ kubectl -n=dok apply \
+      -f https://raw.githubusercontent.com/kubernauts/dok-example-us/master/stock-con/app.yaml
+```
+<!--
+Once both deployments are created and the pods are running, we forward the `stock-con` service for local consumption (in a separate terminal session):
+-->
+
+
+一旦两个部署建好并且 pod 开始运行，我们转发 `stock-con` 服务以供本地读取（另开一个终端窗口）：
+
+```
+$ kubectl get -n dok po --selector=app=stock-con  \
+                     -o=custom-columns=:metadata.name --no-headers |  \
+                     xargs -IPOD kubectl -n dok port-forward POD 9898:9898
+```
+<!--
+With that we should be able to consume the `stock-con` service from our local machine; we do this by regularly checking the response of the `healthz` endpoint like so (in a separate terminal session):
+-->
+
+
+这样，通过定期查询 `healthz` 端点，我们就应该能够从本地机器上读取 `stock-con` 服务，查询命令如下（在一个单独的终端窗口）：
+
+```
+$ watch curl localhost:9898/healthz
+```
+<!--
+Now change the code in the `ksync/stock-con`directory, for example update the [`/healthz` endpoint code in `service.js`](https://github.com/kubernauts/dok-example-us/blob/2334ee8fb11f8813370122bd46285cf45bdd4c48/stock-con/service.js#L52) by adding a field to the JSON response and observe how the pod gets updated and the response of the `curl localhost:9898/healthz` command changes. Overall you should have something like the following in the end:
+-->
+
+
+现在，改动 `ksync/stock-con` 目录中的代码，例如改动 [`service.js` 中定义的 `/healthz` 端点代码](https://github.com/kubernauts/dok-example-us/blob/2334ee8fb11f8813370122bd46285cf45bdd4c48/stock-con/service.js#L52)，在其 JSON 形式的响应中新添一个字段并观察 pod 如何更新以及 `curl localhost：9898/healthz` 命令的输出发生何种变化。总的来说，您最后应该看到类似的内容：
+
+
+![Preview](/images/blog/2018-05-01-developing-on-kubernetes/dok-ksync_preview.png)
+
+
+<!--
+### Walkthrough: Minikube with local build
+-->
+
+### 实践演练：带本地构建的 Minikube
+
+<!--
+For the following you will need to have Minikube up and running and we will leverage the Minikube-internal Docker daemon for building images, locally. As a preparation, do the following
+-->
+
+
+对于以下内容，您需要启动并运行 Minikube，我们将利用 Minikube 自带的 Docker daemon 在本地构建镜像。作为准备，请执行以下操作
+
+```
+$ git clone https://github.com/kubernauts/dok-example-us.git && cd dok-example-us
+$ eval $(minikube docker-env)
+$ kubectl create namespace dok
+```
+
+<!--
+Now we deploy the stock generator and the stock consumer microservice:
+-->
+
+现在我们部署股价数据生成器和股价数据消费者微服务：
+
+
+```
+$ kubectl -n=dok apply -f stock-gen/app.yaml
+$ kubectl -n=dok apply -f stock-con/app.yaml
+```
+<!--
+Once both deployments are created and the pods are running, we forward the `stock-con` service for local consumption (in a separate terminal session):
+-->
+
+
+一旦两个部署建好并且 pod 开始运行，我们转发 `stock-con` 服务以供本地读取（另开一个终端窗口）：
+
+```
+$ kubectl get -n dok po --selector=app=stock-con  \
+                     -o=custom-columns=:metadata.name --no-headers |  \
+                     xargs -IPOD kubectl -n dok port-forward POD 9898:9898 &
+$ watch curl localhost:9898/healthz
+```
+<!--
+Now change the code in the `stock-con`directory, for example, update the [`/healthz` endpoint code in `service.js`](https://github.com/kubernauts/dok-example-us/blob/2334ee8fb11f8813370122bd46285cf45bdd4c48/stock-con/service.js#L52) by adding a field to the JSON response. Once you’re done with your code update, the last step is to build a new container image and kick off a new deployment like shown below:
+-->
+
+现在，改一下 `ksync/stock-con` 目录中的代码，例如修改 [`service.js` 中定义的 `/healthz` 端点代码](https://github.com/kubernauts/dok-example-us/blob/2334ee8fb11f8813370122bd46285cf45bdd4c48/stock-con/service.js#L52)，在其 JSON 形式的响应中添加一个字段。在您更新完代码后，最后一步是构建新的容器镜像并启动新部署，如下所示：
+
+
+```
+$ docker build -t stock-con:dev -f Dockerfile .
+$ kubectl -n dok set image deployment/stock-con *=stock-con:dev
+```
+<!--
+Overall you should have something like the following in the end:
+-->
+
+总的来说，您最后应该看到类似的内容：
+
+![Local Preview](/images/blog/2018-05-01-developing-on-kubernetes/dok-minikube-localdev_preview.png)
+
+<!--
+### Walkthrough: Skaffold
+-->
+
+### 实践演练：Skaffold
+
+<!--
+To perform this walkthrough you first need to install [Skaffold](https://github.com/GoogleContainerTools/skaffold#installation). Once that is done, you can do the following steps to prepare the development setup:
+-->
+
+要进行此演练，首先需要安装 [Skaffold](https://github.com/GoogleContainerTools/skaffold#installation)。完成后，您可以执行以下步骤来配置开发环境：
+
+```
+$ git clone https://github.com/kubernauts/dok-example-us.git && cd dok-example-us
+$ kubectl create namespace dok
+```
+<!--
+Now we deploy the stock generator (but not the stock consumer microservice, that is done via Skaffold):
+-->
+
+现在我们部署股价数据生成器（但是暂不部署股价数据消费者，此服务将使用 Skaffold 完成）：
+
+```
+$ kubectl -n=dok apply -f stock-gen/app.yaml
+```
+
+<!--
+Note that initially we experienced an authentication error when doing `skaffold dev` and needed to apply a fix as described in [Issue 322](https://github.com/GoogleContainerTools/skaffold/issues/322). Essentially it means changing the content of `~/.docker/config.json` to:
+-->
+
+
+请注意，最初我们在执行 `skaffold dev` 时发生身份验证错误，为避免此错误需要安装[问题322](https://github.com/GoogleContainerTools/skaffold/issues/322) 中所述的修复。本质上，需要将 `〜/.docker/config.json` 的内容改为：
+
+
+```
+{
+   "auths": {}
+}
+```
+
+<!--
+Next, we had to patch `stock-con/app.yaml` slightly to make it work with Skaffold:
+-->
+
+接下来，我们需要略微改动 `stock-con/app.yaml`，这样 Skaffold 才能正常使用此文件：
+
+<!--
+Add a `namespace` field to both the `stock-con` deployment and the service with the value of `dok`.
+Change the `image` field of the container spec to `quay.io/mhausenblas/stock-con` since Skaffold manages the container image tag on the fly.
+-->
+
+在 `stock-con` 部署和服务中添加一个 `namespace` 字段，其值为 `dok`
+
+将容器规范的 `image` 字段更改为 `quay.io/mhausenblas/stock-con`，因为 Skaffold 可以即时管理容器镜像标签。
+
+<!--
+ The resulting `app.yaml` file stock-con looks as follows:
+ -->
+最终的 stock-con 的 `app.yaml` 文件看起来如下：
+
+
+```
+apiVersion: apps/v1beta1
+kind: Deployment
+metadata:
+  labels:
+    app: stock-con
+  name: stock-con
+  namespace: dok
+spec:
+  replicas: 1
+  template:
+    metadata:
+      labels:
+        app: stock-con
+    spec:
+      containers:
+      - name: stock-con
+        image: quay.io/mhausenblas/stock-con
+        env:
+        - name: DOK_STOCKGEN_HOSTNAME
+          value: stock-gen
+        - name: DOK_STOCKGEN_PORT
+          value: "9999"
+        ports:
+        - containerPort: 9898
+          protocol: TCP
+        livenessProbe:
+          initialDelaySeconds: 2
+          periodSeconds: 5
+          httpGet:
+            path: /healthz
+            port: 9898
+        readinessProbe:
+          initialDelaySeconds: 2
+          periodSeconds: 5
+          httpGet:
+            path: /healthz
+            port: 9898
+---
+apiVersion: v1
+kind: Service
+metadata:
+  labels:
+    app: stock-con
+  name: stock-con
+  namespace: dok
+spec:
+  type: ClusterIP
+  ports:
+  - name: http
+    port: 80
+    protocol: TCP
+    targetPort: 9898
+  selector:
+    app: stock-con
+```
+<!--
+The final step before we can start development is to configure Skaffold. So, create a file `skaffold.yaml` in the `stock-con/` directory with the following content:
+ -->
+
+我们能够开始开发之前的最后一步是配置 Skaffold。因此，在 `stock-con/` 目录中创建文件 `skaffold.yaml`，其中包含以下内容：
+
+```
+apiVersion: skaffold/v1alpha2
+kind: Config
+build:
+  artifacts:
+  - imageName: quay.io/mhausenblas/stock-con
+    workspace: .
+    docker: {}
+  local: {}
+deploy:
+  kubectl:
+    manifests:
+      - app.yaml
+```
+<!--
+Now we’re ready to kick off the development. For that execute the following in the `stock-con/` directory:
+ -->
+
+现在我们准备好开始开发了。为此，在 `stock-con/` 目录中执行以下命令：
+
+```
+$ skaffold dev
+```
+<!--
+Above command triggers a build of the `stock-con` image and then a deployment. Once the pod of the `stock-con` deployment is running, we again forward the `stock-con` service for local consumption (in a separate terminal session) and check the response of the `healthz` endpoint:
+ -->
+
+
+上面的命令将触发 `stock-con` 图像的构建和部署。一旦 `stock-con` 部署的 pod 开始运行，我们再次转发 `stock-con` 服务以供本地读取（在单独的终端窗口中）并检查 `healthz` 端点的响应：
+
+```bash
+$ kubectl get -n dok po --selector=app=stock-con  \
+                     -o=custom-columns=:metadata.name --no-headers |  \
+                     xargs -IPOD kubectl -n dok port-forward POD 9898:9898 &
+$ watch curl localhost:9898/healthz
+```
+<!--
+If you now change the code in the `stock-con`directory, for example, by updating the [`/healthz` endpoint code in `service.js`](https://github.com/kubernauts/dok-example-us/blob/2334ee8fb11f8813370122bd46285cf45bdd4c48/stock-con/service.js#L52) by adding a field to the JSON response, you should see Skaffold noticing the change and create a new image as well as deploy it. The resulting screen would look something like this:
+ -->
+ 
+现在，如果您修改一下 `stock-con` 目录中的代码，例如 [`service.js` 中定义的 `/healthz` 端点代码](https://github.com/kubernauts/dok-example-us/blob/2334ee8fb11f8813370122bd46285cf45bdd4c48/stock-con/service.js#L52)，在其 JSON 形式的响应中添加一个字段，您应该看到 Skaffold 可以检测到代码改动并创建新图像以及部署它。您的屏幕看起来应该类似这样：
+ 
+ 
+![Skaffold Preview](/images/blog/2018-05-01-developing-on-kubernetes/dok-skaffold_preview.png)
+<!--
+By now you should have a feeling how different tools enable you to develop apps on Kubernetes and if you’re interested to learn more about tools and or methods, check out the following resources:
+ -->
+
+至此，您应该对不同的工具如何帮您在 Kubernetes 上开发应用程序有了一定的概念，如果您有兴趣了解有关工具和/或方法的更多信息，请查看以下资源：
+
+* Blog post by Shahidh K Muhammed on [Draft vs Gitkube vs Helm vs Ksonnet vs Metaparticle vs Skaffold](https://blog.hasura.io/draft-vs-gitkube-vs-helm-vs-ksonnet-vs-metaparticle-vs-skaffold-f5aa9561f948) (03/2018)
+* Blog post by Gergely Nemeth on [Using Kubernetes for Local Development](https://nemethgergely.com/using-kubernetes-for-local-development/index.html), with a focus on Skaffold (03/2018)
+* Blog post by Richard Li on [Locally developing Kubernetes services (without waiting for a deploy)](https://hackernoon.com/locally-developing-kubernetes-services-without-waiting-for-a-deploy-f63995de7b99), with a focus on Telepresence
+* Blog post by Abhishek Tiwari on [Local Development Environment for Kubernetes using Minikube](https://abhishek-tiwari.com/local-development-environment-for-kubernetes-using-minikube/) (09/2017)
+* Blog post by Aymen El Amri on [Using Kubernetes for Local Development — Minikube](https://medium.com/devopslinks/using-kubernetes-minikube-for-local-development-c37c6e56e3db) (08/2017)
+* Blog post by Alexis Richardson on [GitOps - Operations by Pull Request](https://www.weave.works/blog/gitops-operations-by-pull-request) (08/2017)
+* Slide deck [GitOps: Drive operations through git](https://docs.google.com/presentation/d/1d3PigRVt_m5rO89Ob2XZ16bW8lRSkHHH5k816-oMzZo/), with a focus on Gitkube by Tirumarai Selvan (03/2018)
+* Slide deck [Developing apps on Kubernetes](https://speakerdeck.com/mhausenblas/developing-apps-on-kubernetes), a talk Michael Hausenblas gave at a CNCF Paris meetup  (04/2018)
+* YouTube videos:
+    * [TGI Kubernetes 029: Developing Apps with Ksync](https://www.youtube.com/watch?v=QW85Y0Ug3KY )
+    * [TGI Kubernetes 030: Exploring Skaffold](https://www.youtube.com/watch?v=McwwWhCXMxc)
+    * [TGI Kubernetes 031: Connecting with Telepresence](https://www.youtube.com/watch?v=zezeBAJ_3w8)
+    * [TGI Kubernetes 033: Developing with Draft](https://www.youtube.com/watch?v=8B1D7cTMPgA)
+* Raw responses to the [Kubernetes Application Survey](https://docs.google.com/spreadsheets/d/12ilRCly2eHKPuicv1P_BD6z__PXAqpiaR-tDYe2eudE/edit) 2018 by SIG Apps
+
+<!--
+With that we wrap up this post on how to go about developing apps on Kubernetes, we hope you learned something and if you have feedback and/or want to point out a tool that you found useful, please let us know via Twitter: [Ilya](https://twitter.com/errordeveloper) and [Michael](https://twitter.com/mhausenblas).
+-->
+
+有了这些，我们这篇关于如何在 Kubernetes 上开发应用程序的博客就可以收尾了，希望您有所收获，如果您有反馈和/或想要指出您认为有用的工具，请通过 Twitter 告诉我们：[Ilya](https://twitter.com/errordeveloper) 和 [Michael](https://twitter.com/mhausenblas)
@@ -0,0 +1,67 @@
+---
+title: 'Kubernetes 1 11：向 discuss kubernetes 问好'
+layout: blog
+date: 2018-05-30
+---
+
+<!--
+---
+title: ' Kubernetes 1 11：say-hello-to-discuss-kubernetes '
+cn-approvers:
+- congfairy
+layout: blog
+date: 2018-05-30
+---
+-->
+
+<!--   
+
+Author: Jorge Castro (Heptio)
+
+-->
+
+作者: Jorge Castro (Heptio)
+
+<!-- 
+
+Communication is key when it comes to engaging a community of over 35,000 people in a global and remote environment. Keeping track of everything in the Kubernetes community can be an overwhelming task. On one hand we have our official resources, like Stack Overflow, GitHub, and the mailing lists, and on the other we have more ephemeral resources like Slack, where you can hop in, chat with someone, and then go on your merry way. 
+
+-->
+
+就一个超过 35,000 人的全球性社区而言，参与其中时沟通是非常关键的。 跟踪 Kubernetes 社区中的所有内容可能是一项艰巨的任务。 一方面，我们有官方资源，如 Stack Overflow，GitHub 和邮件列表，另一方面，我们有更多瞬时性的资源，如 Slack，你可以加入进去、与某人聊天然后各走各路。
+
+
+<!--
+
+Slack is great for casual and timely conversations and keeping up with other community members, but communication can't be easily referenced in the future. Plus it can be hard to raise your hand in a room filled with 35,000 participants and find a voice. Mailing lists are useful when trying to reach a specific group of people with a particular ask and want to keep track of responses on the thread, but can be daunting with a large amount of people. Stack Overflow and GitHub are ideal for collaborating on projects or questions that involve code and need to be searchable in the future, but certain topics like "What's your favorite CI/CD tool" or "Kubectl tips and tricks" are offtopic there.
+
+While our current assortment of communication channels are valuable in their own rights, we found that there was still a gap between email and real time chat. Across the rest of the web, many other open source projects like Docker, Mozilla, Swift, Ghost, and Chef have had success building communities on top of Discourse, an open source discussion platform. So what if we could use this tool to bring our discussions together under a modern roof, with an open API, and perhaps not let so much of our information fade into the ether? There's only one way to find out: Welcome to discuss.kubernetes.io
+
+-->
+
+Slack 非常适合随意和及时的对话，并与其他社区成员保持联系，但未来很难轻易引用通信。此外，在35,000名参与者中提问并得到回答很难。邮件列表在有问题尝试联系特定人群并且想要跟踪大家的回应时非常有用，但是对于大量人员来说可能是麻烦的。 Stack Overflow 和 GitHub 非常适合在涉及代码的项目或问题上进行协作，并且如果在将来要进行搜索也很有用，但某些主题如“你最喜欢的 CI/CD 工具是什么”或“[Kubectl提示和技巧](http://discuss.kubernetes.io/t/kubectl-tips-and-tricks/192)“在那里是没有意义的。
+
+虽然我们目前的各种沟通渠道对他们自己来说都很有价值，但我们发现电子邮件和实时聊天之间仍然存在差距。在网络的其他部分，许多其他开源项目，如 Docker、Mozilla、Swift、Ghost 和 Chef，已经成功地在[Discourse](http://www.discourse.org/features)之上构建社区，一个开放的讨论平台。那么，如果我们可以使用这个工具将我们的讨论结合在一个平台下，使用开放的API，或许也不会让我们的大部分信息消失在网络中呢？只有一种方法可以找到：欢迎来到[discuss.kubernetes.io](http://discuss.kubernetes.io)
+
+<!--
+
+Right off the bat we have categories that users can browse. Checking and posting in these categories allow users to participate in things they might be interested in without having to commit to subscribing to a list. Granular notification controls allow the users to subscribe to just the category or tag they want, and allow for responding to topics via email. 
+
+Ecosystem partners and developers now have a place where they can [announce projects](https://discuss.kubernetes.io/c/announcements) that they're working on to users without wondering if it would be offtopic on an official list. We can make this place be not just about core Kubernetes, but about the hundreds of wonderful tools our community is building. 
+
+
+This new community forum gives people a place to go where they can discuss Kubernetes, and a sounding board for developers to make announcements of things happening around Kubernetes, all while being searchable and easily accessible to a wider audience. 
+
+Hop in and take a look. We're just getting started, so you might want to begin by [introducing yourself](https://discuss.kubernetes.io/t/introduce-yourself-here/56) and then browsing around. Apps are also available for [Android](https://play.google.com/store/apps/details?id=com.discourse&hl=en_US&rdid=com.discourse&pli=1)and [iOS](https://itunes.apple.com/us/app/discourse-app/id1173672076?mt=8).  
+ 
+
+-->
+
+马上，我们有用户可以浏览的类别。检查和发布这些类别允许用户参与他们可能感兴趣的事情，而无需订阅列表。精细的通知控件允许用户只订阅他们想要的类别或标签，并允许通过电子邮件回复主题。
+
+生态系统合作伙伴和开发人员现在有一个地方可以[宣布项目](http://discuss.kubernetes.io/c/announcements)，他们正在为用户工作，而不会想知道它是否会在官方列表中脱离主题。我们可以让这个地方不仅仅是关于核心 Kubernetes，而是关于我们社区正在建设的数百个精彩工具。
+
+这个新的社区论坛为人们提供了一个可以讨论 Kubernetes 的地方，也是开发人员在 Kubernetes 周围发布事件的声音板，同时可以搜索并且更容易被更广泛的用户访问。
+
+进来看看。我们刚刚开始，所以，您可能希望从[自我介绍](http://discuss.kubernetes.io/t/introduce-yourself-here/56)开始，到处浏览。也有 [Android](http://play.google.com/store/apps/details?id=com.discourse&hl=en_US&rdid=com.discourse&pli=1) 和 [iOS](http://itunes.apple.com/us/app/discourse-app/id1173672076?mt=8) 应用下载。
+
@@ -0,0 +1,42 @@
+---
+title: Kubernetes 这四年
+approvers:
+cn-approvers:
+- congfairy
+layout: blog
+date: 2018-06-06
+---
+ <!--
+**Author**: Joe Beda (CTO and Founder, Heptio)
+ On June 6, 2014 I checked in the [first commit](https://github.com/kubernetes/kubernetes/commit/2c4b3a562ce34cddc3f8218a2c4d11c7310e6d56) of what would become the public repository for Kubernetes. Many would assume that is where the story starts. It is the beginning of history, right? But that really doesn’t tell the whole story.
+-->
+
+ **作者**：Joe Beda( Heptio 首席技术官兼创始人)
+ 2014 年 6 月 6 日，我检查了 Kubernetes 公共代码库的[第一次 commit](https://github.com/kubernetes/kubernetes/commit/2c4b3a562ce34cddc3f8218a2c4d11c7310e6d56) 。许多人会认为这是故事开始的地方。这难道不是一切开始的地方吗？但这的确不能把整个过程说清楚。
+ 
+ ![k8s_first_commit](/images/blog/2018-06-06-4-years-of-k8s/k8s-first-commit.png)
+ 
+ <!--
+The cast leading up to that commit was large and the success for Kubernetes since then is owed to an ever larger cast.
+ Kubernetes was built on ideas that had been proven out at Google over the previous ten years with Borg. And Borg, itself, owed its existence to even earlier efforts at Google and beyond.
+ Concretely, Kubernetes started as some prototypes from Brendan Burns combined with ongoing work from me and Craig McLuckie to better align the internal Google experience with the Google Cloud experience. Brendan, Craig, and I really wanted people to use this, so we made the case to build out this prototype as an open source project that would bring the best ideas from Borg out into the open.
+ After we got the nod, it was time to actually build the system.  We took Brendan’s prototype (in Java), rewrote it in Go, and built just enough to get the core ideas across.  By this time the team had grown to include Ville Aikas, Tim Hockin, Brian Grant, Dawn Chen and Daniel Smith.  Once we had something working, someone had to sign up to clean things up to get it ready for public launch.  That ended up being me. Not knowing the significance at the time, I created a new repo, moved things over, and checked it in.  So while I have the first public commit to the repo, there was work underway well before that.
+ The version of Kubernetes at that point was really just a shadow of what it was to become.  The core concepts were there but it was very raw.  For example, Pods were called Tasks.  That was changed a day before we went public.  All of this led up to the public announcement of Kubernetes on June 10th, 2014 in a keynote from Eric Brewer at the first DockerCon.  You can watch that video here:
+-->
+
+ 第一次 commit 涉及的人员众多，自那以后 Kubernetes 的成功归功于更大的开发者阵容。
+ Kubernetes 建立在过去十年曾经在 Google 的 Borg 集群管理系统中验证过的思路之上。而 Borg 本身也是 Google 和其他公司早期努力的结果。
+ 具体而言，Kubernetes 最初是从 Brendan Burns 的一些原型开始，结合我和 Craig McLuckie 正在进行的工作，以更好地将 Google 内部实践与 Google Cloud 的经验相结合。 Brendan，Craig 和我真的希望人们使用它，所以我们建议将这个原型构建为一个开源项目，将 Borg 的最佳创意带给大家。
+在我们所有人同意后，就开始着手构建这个系统了。我们采用了 Brendan 的原型（Java 语言），用 Go 语言重写了它，并且以上述核心思想去构建该系统。到这个时候，团队已经成长为包括 Ville Aikas，Tim Hockin，Brian Grant，Dawn Chen 和 Daniel Smith。一旦我们有了一些工作需求，有人必须承担一些脱敏的工作，以便为公开发布做好准备。这个角色最终由我承担。当时，我不知道这件事情的重要性，我创建了一个新的仓库，把代码搬过来，然后进行了检查。所以在我第一次提交 public commit 之前，就有工作已经启动了。
+那时 Kubernetes 的版本只是现在版本的简单雏形。核心概念已经有了，但非常原始。例如，Pods 被称为 Tasks，这在我们推广前一天就被替换。2014年6月10日 Eric Brewe 在第一届 DockerCon 上的演讲中正式发布了 Kubernetes 。您可以在此处观看该视频：
+ 
+
+<center><iframe width="560" height="315" src="https://www.youtube.com/embed/YrxnVKZeqK8" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe></center>  
+
+ <!--
+ But, however raw, that modest start was enough to pique the interest of a community that started strong and has only gotten stronger.  Over the past four years Kubernetes has exceeded the expectations of all of us that were there early on. We owe the Kubernetes community a huge debt.  The success the project has seen  is based not just on code and technology but also the way that an amazing group of people have come together to create something special.  The best expression of this is the [set of Kubernetes values](https://github.com/kubernetes/steering/blob/master/values.md) that Sarah Novotny helped curate.
+ Here is to another 4 years and beyond! 🎉🎉🎉
+-->
+
+ 但是，无论多么原始，这小小的一步足以激起一个开始强大而且变得更强大的社区的兴趣。在过去的四年里，Kubernetes 已经超出了我们所有人的期望。我们对 Kubernetes 社区的所有人员表示感谢。该项目所取得的成功不仅基于代码和技术，还基于一群出色的人聚集在一起所做的有意义的事情。Sarah Novotny 策划的一套 [Kubernetes 价值观](https://github.com/kubernetes/steering/blob/master/values.md)是以上最好的表现形式。
+ 让我们一起期待下一个4年！🎉🎉🎉
@@ -0,0 +1,129 @@
+---
+title: 'Kubernetes 内的动态 Ingress'
+layout: blog
+---
+
+<!--
+title: Dynamic Ingress in Kubernetes
+date:  2018-06-07
+Author: Richard Li (Datawire)
+-->
+
+作者: Richard Li (Datawire)
+
+<!--
+Kubernetes makes it easy to deploy applications that consist of many microservices, but one of the key challenges with this type of architecture is dynamically routing ingress traffic to each of these services.  One approach is Ambassador, a Kubernetes-native open source API Gateway built on the Envoy Proxy. Ambassador is designed for dynamic environment where services may come and go frequently.
+Ambassador is configured using Kubernetes annotations. Annotations are used to configure specific mappings from a given Kubernetes service to a particular URL. A mapping can include a number of annotations for configuring a route. Examples include rate limiting, protocol, cross-origin request sharing, traffic shadowing, and routing rules.
+-->
+
+Kubernetes 可以轻松部署由许多微服务组成的应用程序，但这种架构的关键挑战之一是动态地将流量路由到这些服务中的每一个。
+一种方法是使用 [Ambassador](https://www.getambassador.io)，
+一个基于 [Envoy Proxy](https://www.envoyproxy.io) 构建的 Kubernetes 原生开源 API 网关。
+Ambassador 专为动态环境而设计，这类环境中的服务可能被频繁添加或删除。
+
+Ambassador 使用 Kubernetes 注解进行配置。
+注解用于配置从给定 Kubernetes 服务到特定 URL 的具体映射关系。
+每个映射中可以包括多个注解，用于配置路由。
+注解的例子有速率限制、协议、跨源请求共享（CORS）、流量影射和路由规则等。
+
+<!--
+## A Basic Ambassador Example
+Ambassador is typically installed as a Kubernetes deployment, and is also available as a Helm chart. To configure Ambassador, create a Kubernetes service with the Ambassador annotations. Here is an example that configures Ambassador to route requests to /httpbin/ to the public httpbin.org service:
+-->
+
+## 一个简单的 Ambassador 示例
+
+Ambassador 通常作为 Kubernetes Deployment 来安装，也可以作为 Helm Chart 使用。
+配置 Ambassador 时，请使用 Ambassador 注解创建 Kubernetes 服务。
+下面是一个例子，用来配置 Ambassador，将针对 /httpbin/ 的请求路由到公共的 httpbin.org 服务：
+
+```
+apiVersion: v1
+kind: Service
+metadata:
+  name: httpbin
+  annotations:
+    getambassador.io/config: |
+      ---
+      apiVersion: ambassador/v0
+      kind:  Mapping
+      name:  httpbin_mapping
+      prefix: /httpbin/
+      service: httpbin.org:80
+      host_rewrite: httpbin.org
+spec:
+  type: ClusterIP
+  ports:
+    - port: 80
+```
+
+<!--
+A mapping object is created with a prefix of /httpbin/ and a service name of httpbin.org. The host_rewrite annotation specifies that the HTTP host header should be set to httpbin.org.
+-->
+
+例子中创建了一个 Mapping 对象，其 prefix 设置为 /httpbin/，service 名称为 httpbin.org。
+其中的 host_rewrite 注解指定 HTTP 的 host 头部字段应设置为 httpbin.org。
+
+<!--
+## Kubeflow
+Kubeflow provides a simple way to easily deploy machine learning infrastructure on Kubernetes. The Kubeflow team needed a proxy that provided a central point of authentication and routing to the wide range of services used in Kubeflow, many of which are ephemeral in nature.
+<center><i>Kubeflow architecture, pre-Ambassador</center></i>
+-->
+
+## Kubeflow
+
+[Kubeflow](https://github.com/kubeflow/kubeflow) 提供了一种简单的方法，用于在 Kubernetes 上轻松部署机器学习基础设施。
+Kubeflow 团队需要一个代理，为 Kubeflow 中所使用的各种服务提供集中化的认证和路由能力；Kubeflow 中许多服务本质上都是生命期很短的。
+
+<center><i>Kubeflow architecture, pre-Ambassador</center></i>
+
+<!--
+## Service configuration
+With Ambassador, Kubeflow can use a distributed model for configuration. Instead of a central configuration file, Ambassador allows each service to configure its route in Ambassador via Kubernetes annotations. Here is a simplified example configuration:
+-->
+
+## 服务配置
+
+有了 Ambassador，Kubeflow 可以使用分布式模型进行配置。
+Ambassador 不使用集中的配置文件，而是允许每个服务通过 Kubernetes 注解在 Ambassador 中配置其路由。
+下面是一个简化的配置示例：
+
+```
+---
+apiVersion: ambassador/v0
+kind:  Mapping
+name: tfserving-mapping-test-post
+prefix: /models/test/
+rewrite: /model/test/:predict
+method: POST
+service: test.kubeflow:8000
+```
+
+<!--
+In this example, the “test” service uses Ambassador annotations to dynamically configure a route to the service, triggered only when the HTTP method is a POST, and the annotation also specifies a rewrite rule.
+-->
+
+示例中，“test” 服务使用 Ambassador 注解来为服务动态配置路由。
+所配置的路由仅在 HTTP 方法是 POST 时触发；注解中同时还给出了一条重写规则。
+
+<!--
+With Ambassador, Kubeflow manages routing easily with Kubernetes annotations. Kubeflow configures a single ingress object that directs traffic to Ambassador, then creates services with Ambassador annotations as needed to direct traffic  to specific backends. For example, when deploying TensorFlow services,  Kubeflow creates and and annotates a K8s service so that the model will be served at https://<ingress host>/models/<model name>/. Kubeflow can also use the Envoy Proxy to do the actual L7 routing. Using Ambassador, Kubeflow takes advantage of additional routing configuration like URL rewriting and method-based routing.
+If you’re interested in using Ambassador with Kubeflow, the standard Kubeflow install automatically installs and configures Ambassador.
+If you’re interested in using Ambassador as an API Gateway or Kubernetes ingress solution for your non-Kubeflow services, check out the Getting Started with Ambassador guide.
+## Kubeflow and Ambassador
+-->
+
+## Kubeflow 和 Ambassador
+
+通过 Ambassador，Kubeflow 可以使用 Kubernetes 注解轻松管理路由。
+Kubeflow 配置同一个 Ingress 对象，将流量定向到 Ambassador，然后根据需要创建具有 Ambassador 注解的服务，以将流量定向到特定后端。
+例如，在部署 TensorFlow 服务时，Kubeflow 会创建 Kubernetes 服务并为其添加注解，
+以便用户能够在 `https://<ingress主机>/models/<模型名称>/` 处访问到模型本身。
+Kubeflow 还可以使用 Envoy Proxy 来进行实际的 L7 路由。
+通过 Ambassador，Kubeflow 能够更充分地利用 URL 重写和基于方法的路由等额外的路由配置能力。
+
+如果您对在 Kubeflow 中使用 Ambassador 感兴趣，标准的 Kubeflow 安装会自动安装和配置 Ambassador。
+
+如果您有兴趣将 Ambassador 用作 API 网关或 Kubernetes 的 Ingress 解决方案，
+请参阅 [Ambassador 入门指南](https://www.getambassador.io/user-guide/getting-started)。
+
@@ -0,0 +1,306 @@
+---
+layout: blog
+title: 'KubeDirector：在 Kubernetes 上运行复杂状态应用程序的简单方法'
+date: 2018-10-03
+---
+
+<!--
+layout: blog
+title: 'KubeDirector: The easy way to run complex stateful applications on Kubernetes'
+date: 2018-10-03
+-->
+
+<!--
+**Author**: Thomas Phelan (BlueData)
+-->
+
+**作者**：Thomas Phelan（BlueData）
+
+<!--
+KubeDirector is an open source project designed to make it easy to run complex stateful scale-out application clusters on Kubernetes. KubeDirector is built using the custom resource definition (CRD) framework and leverages the native Kubernetes API extensions and design philosophy. This enables transparent integration with Kubernetes user/resource management as well as existing clients and tools.
+-->
+KubeDirector 是一个开源项目，旨在简化在 Kubernetes 上运行复杂的有状态扩展应用程序集群。KubeDirector 使用自定义资源定义（CRD）
+框架构建，并利用了本地 Kubernetes API 扩展和设计哲学。这支持与 Kubernetes 用户/资源 管理以及现有客户端和工具的透明集成。
+
+<!--
+We recently [introduced the KubeDirector project](https://medium.com/@thomas_phelan/operation-stateful-introducing-bluek8s-and-kubernetes-director-aa204952f619/), as part of a broader open source Kubernetes initiative we call BlueK8s. I’m happy to announce that the pre-alpha
+code for [KubeDirector](https://github.com/bluek8s/kubedirector/) is now available. And in this blog post, I’ll show how it works.
+-->
+我们最近[介绍了 KubeDirector 项目](https://medium.com/@thomas_phelan/operation-stateful-introducing-bluek8s-and-kubernetes-director-aa204952f619/)，作为我们称为 BlueK8s 的更广泛的 Kubernetes 开源项目的一部分。我很高兴地宣布 [KubeDirector](https://github.com/bluek8s/kubedirector/) 的
+pre-alpha 代码现在已经可用。在这篇博客文章中，我将展示它是如何工作的。
+
+<!--
+KubeDirector provides the following capabilities:
+-->
+KubeDirector 提供以下功能：
+
+<!--
+*	The ability to run non-cloud native stateful applications on Kubernetes without modifying the code. In other words, it’s not necessary to decompose these existing applications to fit a microservices design pattern.
+*	Native support for preserving application-specific configuration and state.
+*	An application-agnostic deployment pattern, minimizing the time to onboard new stateful applications to Kubernetes.
+-->
+
+*	无需修改代码即可在 Kubernetes 上运行非云原生有状态应用程序。换句话说，不需要分解这些现有的应用程序来适应微服务设计模式。
+*	本机支持保存特定于应用程序的配置和状态。
+*	与应用程序无关的部署模式，最大限度地减少将新的有状态应用程序装载到 Kubernetes 的时间。
+
+<!--
+KubeDirector enables data scientists familiar with data-intensive distributed applications such as Hadoop, Spark, Cassandra, TensorFlow, Caffe2, etc. to run these applications on Kubernetes -- with a minimal learning curve and no need to write GO code. The applications controlled by KubeDirector are defined by some basic metadata and an associated package of configuration artifacts.  The application metadata is referred to as a KubeDirectorApp resource.
+-->
+KubeDirector 使熟悉数据密集型分布式应用程序（如 Hadoop、Spark、Cassandra、TensorFlow、Caffe2 等）的数据科学家能够在 Kubernetes 上运行这些应用程序 -- 只需极少的学习曲线，无需编写 GO 代码。由 KubeDirector 控制的应用程序由一些基本元数据和相关的配置工件包定义。应用程序元数据称为 KubeDirectorApp 资源。
+
+<!--
+To understand the components of KubeDirector, clone the repository on [GitHub](https://github.com/bluek8s/kubedirector/) using a command similar to:
+-->
+要了解 KubeDirector 的组件，请使用类似于以下的命令在 [GitHub](https://github.com/bluek8s/kubedirector/) 上克隆存储库：
+
+```
+git clone http://<userid>@github.com/bluek8s/kubedirector.
+```
+
+<!--
+The KubeDirectorApp definition for the Spark 2.2.1 application is located
+in the file `kubedirector/deploy/example_catalog/cr-app-spark221e2.json`.
+-->
+Spark 2.2.1 应用程序的 KubeDirectorApp 定义位于文件 `kubedirector/deploy/example_catalog/cr-app-spark221e2.json` 中。
+
+ ```
+ ~> cat kubedirector/deploy/example_catalog/cr-app-spark221e2.json
+ {
+    "apiVersion": "kubedirector.bluedata.io/v1alpha1",
+    "kind": "KubeDirectorApp",
+    "metadata": {
+        "name" : "spark221e2"
+    },
+    "spec" : {
+        "systemctlMounts": true,
+        "config": {
+            "node_services": [
+                {
+                    "service_ids": [
+                        "ssh",
+                        "spark",
+                        "spark_master",
+                        "spark_worker"
+                    ],
+…
+```
+
+<!--
+The configuration of an application cluster is referred to as a KubeDirectorCluster resource. The
+KubeDirectorCluster definition for a sample Spark 2.2.1 cluster is located in the file
+`kubedirector/deploy/example_clusters/cr-cluster-spark221.e1.yaml`.
+-->
+应用程序集群的配置称为 KubeDirectorCluster 资源。示例 Spark 2.2.1 集群的 KubeDirectorCluster 定义位于文件
+`kubedirector/deploy/example_clusters/cr-cluster-spark221.e1.yaml` 中。
+
+```
+~> cat kubedirector/deploy/example_clusters/cr-cluster-spark221.e1.yaml
+apiVersion: "kubedirector.bluedata.io/v1alpha1"
+kind: "KubeDirectorCluster"
+metadata:
+  name: "spark221e2"
+spec:
+  app: spark221e2
+  roles:
+  - name: controller
+    replicas: 1
+    resources:
+      requests:
+        memory: "4Gi"
+        cpu: "2"
+      limits:
+        memory: "4Gi"
+        cpu: "2"
+  - name: worker
+    replicas: 2
+    resources:
+      requests:
+        memory: "4Gi"
+        cpu: "2"
+      limits:
+        memory: "4Gi"
+        cpu: "2"
+  - name: jupyter
+…
+```
+
+<!--
+## Running Spark on Kubernetes with KubeDirector
+-->
+
+## 使用 KubeDirector 在 Kubernetes 上运行 Spark
+
+<!--
+With KubeDirector, it’s easy to run Spark clusters on Kubernetes.
+-->
+使用 KubeDirector，可以轻松在 Kubernetes 上运行 Spark 集群。
+
+<!--
+First, verify that Kubernetes (version 1.9 or later) is running, using the command `kubectl version`
+-->
+首先，使用命令 `kubectl version` 验证 Kubernetes（版本 1.9 或更高）是否正在运行
+
+```
+~> kubectl version
+Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T18:02:47Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
+Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T17:53:03Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}                                    
+```
+
+<!--
+Deploy the KubeDirector service and the example KubeDirectorApp resource definitions with the commands:
+-->
+使用以下命令部署 KubeDirector 服务和示例 KubeDirectorApp 资源定义：
+
+```
+cd kubedirector
+make deploy
+```
+
+<!--
+These will start the KubeDirector pod:
+-->
+这些将启动 KubeDirector pod：
+
+```
+~> kubectl get pods
+NAME                           READY     STATUS     RESTARTS     AGE
+kubedirector-58cf59869-qd9hb   1/1       Running    0            1m     
+```
+
+<!--
+List the installed KubeDirector applications with `kubectl get KubeDirectorApp`
+-->
+`kubectl get KubeDirectorApp` 列出中已安装的 KubeDirector 应用程序
+
+```
+~> kubectl get KubeDirectorApp
+NAME           AGE
+cassandra311   30m
+spark211up     30m
+spark221e2     30m
+```
+
+<!--
+Now you can launch a Spark 2.2.1 cluster using the example KubeDirectorCluster file and the
+`kubectl create -f deploy/example_clusters/cr-cluster-spark211up.yaml` command.
+Verify that the Spark cluster has been started:
+-->
+现在，您可以使用示例 KubeDirectorCluster 文件和 `kubectl create -f deploy/example_clusters/cr-cluster-spark211up.yaml` 命令
+启动 Spark 2.2.1 集群。验证 Spark 集群已经启动:
+
+```
+~> kubectl get pods
+NAME                             READY     STATUS    RESTARTS   AGE
+kubedirector-58cf59869-djdwl     1/1       Running   0          19m
+spark221e2-controller-zbg4d-0    1/1       Running   0          23m
+spark221e2-jupyter-2km7q-0       1/1       Running   0          23m
+spark221e2-worker-4gzbz-0        1/1       Running   0          23m
+spark221e2-worker-4gzbz-1        1/1       Running   0          23m
+```
+
+<!--
+The running services now include the Spark services:
+-->
+现在运行的服务包括 Spark 服务：
+
+```
+~> kubectl get service
+NAME                                TYPE         CLUSTER-IP        EXTERNAL-IP    PORT(S)                                                    AGE
+kubedirector                        ClusterIP    10.98.234.194     <none>         60000/TCP                                                  1d
+kubernetes                          ClusterIP    10.96.0.1         <none>         443/TCP                                                    1d
+svc-spark221e2-5tg48                ClusterIP    None              <none>         8888/TCP                                                   21s
+svc-spark221e2-controller-tq8d6-0   NodePort     10.104.181.123    <none>         22:30534/TCP,8080:31533/TCP,7077:32506/TCP,8081:32099/TCP  20s
+svc-spark221e2-jupyter-6989v-0      NodePort     10.105.227.249    <none>         22:30632/TCP,8888:30355/TCP                                20s
+svc-spark221e2-worker-d9892-0       NodePort     10.107.131.165    <none>         22:30358/TCP,8081:32144/TCP                                20s
+svc-spark221e2-worker-d9892-1       NodePort     10.110.88.221     <none>         22:30294/TCP,8081:31436/TCP                                20s
+```
+
+<!--
+Pointing the browser at port 31533 connects to the Spark Master UI:
+-->
+将浏览器指向端口 31533 连接到 Spark 主节点 UI：
+
+![kubedirector](/images/blog/2018-10-03-kubedirector/kubedirector.png)
+
+<!--
+That’s all there is to it!
+In fact, in the example above we also deployed a Jupyter notebook along with the Spark cluster.
+-->
+就是这样!
+事实上，在上面的例子中，我们还部署了一个 Jupyter notebook 和 Spark 集群。
+
+<!--
+To start another application (e.g. Cassandra), just specify another KubeDirectorApp file:
+-->
+要启动另一个应用程序（例如 Cassandra），只需指定另一个 KubeDirectorApp 文件：
+
+```
+kubectl create -f deploy/example_clusters/cr-cluster-cassandra311.yaml
+```
+
+<!--
+See the running Cassandra cluster:
+-->
+查看正在运行的 Cassandra 集群：
+
+```
+~> kubectl get pods
+NAME                              READY     STATUS    RESTARTS   AGE
+cassandra311-seed-v24r6-0         1/1       Running   0          1m
+cassandra311-seed-v24r6-1         1/1       Running   0          1m
+cassandra311-worker-rqrhl-0       1/1       Running   0          1m
+cassandra311-worker-rqrhl-1       1/1       Running   0          1m
+kubedirector-58cf59869-djdwl      1/1       Running   0          1d
+spark221e2-controller-tq8d6-0     1/1       Running   0          22m
+spark221e2-jupyter-6989v-0        1/1       Running   0          22m
+spark221e2-worker-d9892-0         1/1       Running   0          22m
+spark221e2-worker-d9892-1         1/1       Running   0          22m
+```
+
+<!--
+Now you have a Spark cluster (with a Jupyter notebook) and a Cassandra cluster running on Kubernetes.
+Use `kubectl get service` to see the set of services.
+-->
+现在，您有一个 Spark 集群（带有 Jupyter notebook ）和一个运行在 Kubernetes 上的 Cassandra 集群。
+使用 `kubectl get service` 查看服务集。
+
+```
+~> kubectl get service
+NAME                                TYPE         CLUSTER-IP       EXTERNAL-IP   PORT(S)                                                   AGE
+kubedirector                        ClusterIP    10.98.234.194    <none>        60000/TCP                                                 1d
+kubernetes                          ClusterIP    10.96.0.1        <none>        443/TCP                                                   1d
+svc-cassandra311-seed-v24r6-0       NodePort     10.96.94.204     <none>        22:31131/TCP,9042:30739/TCP                               3m
+svc-cassandra311-seed-v24r6-1       NodePort     10.106.144.52    <none>        22:30373/TCP,9042:32662/TCP                               3m
+svc-cassandra311-vhh29              ClusterIP    None             <none>        8888/TCP                                                  3m
+svc-cassandra311-worker-rqrhl-0     NodePort     10.109.61.194    <none>        22:31832/TCP,9042:31962/TCP                               3m
+svc-cassandra311-worker-rqrhl-1     NodePort     10.97.147.131    <none>        22:31454/TCP,9042:31170/TCP                               3m
+svc-spark221e2-5tg48                ClusterIP    None             <none>        8888/TCP                                                  24m
+svc-spark221e2-controller-tq8d6-0   NodePort     10.104.181.123   <none>        22:30534/TCP,8080:31533/TCP,7077:32506/TCP,8081:32099/TCP 24m
+svc-spark221e2-jupyter-6989v-0      NodePort     10.105.227.249   <none>        22:30632/TCP,8888:30355/TCP                               24m
+svc-spark221e2-worker-d9892-0       NodePort     10.107.131.165   <none>        22:30358/TCP,8081:32144/TCP                               24m
+svc-spark221e2-worker-d9892-1       NodePort     10.110.88.221    <none>        22:30294/TCP,8081:31436/TCP                               24m
+```
+
+<!--
+## Get Involved
+-->
+
+## 参与其中
+
+<!--
+KubeDirector is a fully open source, Apache v2 licensed, project – the first of multiple open source projects within a broader initiative we call BlueK8s.
+The pre-alpha code for KubeDirector has just been released and we would love for you to join the growing community of developers, contributors, and adopters.
+Follow [@BlueK8s](https://twitter.com/BlueK8s/) on Twitter and get involved through these channels:
+-->
+KubeDirector 是一个完全开放源码的 Apache v2 授权项目 – 在我们称为 BlueK8s 的更广泛的计划中，它是多个开放源码项目中的第一个。
+KubeDirector 的 pre-alpha 代码刚刚发布，我们希望您加入到不断增长的开发人员、贡献者和使用者社区。
+在 Twitter 上关注 [@BlueK8s](https://twitter.com/BlueK8s/)，并通过以下渠道参与:
+
+<!--
+* KubeDirector [chat room on Slack](https://join.slack.com/t/bluek8s/shared_invite/enQtNDUwMzkwODY5OTM4LTRhYmRmZmE4YzY3OGUzMjA1NDg0MDVhNDQ2MGNkYjRhM2RlMDNjMTI1NDQyMjAzZGVlMDFkNThkNGFjZGZjMGY/)
+*	KubeDirector [GitHub repo](https://github.com/bluek8s/kubedirector/)
+-->
+
+* KubeDirector [Slack 聊天室](https://join.slack.com/t/bluek8s/shared_invite/enQtNDUwMzkwODY5OTM4LTRhYmRmZmE4YzY3OGUzMjA1NDg0MDVhNDQ2MGNkYjRhM2RlMDNjMTI1NDQyMjAzZGVlMDFkNThkNGFjZGZjMGY/)
+*	KubeDirector [GitHub 仓库](https://github.com/bluek8s/kubedirector/)
@@ -0,0 +1,268 @@
+---
+layout: blog
+title: 'Kubernetes 中的拓扑感知数据卷供应'
+date: 2018-10-11
+---
+<!--
+---
+layout: blog
+title: 'Topology-Aware Volume Provisioning in Kubernetes'
+date: 2018-10-11
+---
+-->
+
+<!--
+**Author**: Michelle Au (Google)
+-->
+**作者**: Michelle Au（谷歌）
+
+<!--
+The multi-zone cluster experience with persistent volumes is improving in Kubernetes 1.12 with the topology-aware dynamic provisioning beta feature. This feature allows Kubernetes to make intelligent decisions when dynamically provisioning volumes by getting scheduler input on the best place to provision a volume for a pod.  In multi-zone clusters, this means that volumes will get provisioned in an appropriate zone that can run your pod, allowing you to easily deploy and scale your stateful workloads across failure domains to provide high availability and fault tolerance.
+-->
+通过提供拓扑感知动态卷供应功能，具有持久卷的多区域集群体验在 Kubernetes 1.12 中得到了改进。此功能使得 Kubernetes 在动态供应卷时能做出明智的决策，方法是从调度器获得为 Pod 提供数据卷的最佳位置。在多区域集群环境，这意味着数据卷能够在满足你的 Pod 运行需要的合适的区域被供应，从而允许您跨故障域轻松部署和扩展有状态工作负载，从而提供高可用性和容错能力。
+
+<!--
+## Previous challenges
+-->
+## 以前的挑战
+
+<!--
+Before this feature, running stateful workloads with zonal persistent disks (such as AWS ElasticBlockStore, Azure Disk, GCE PersistentDisk) in multi-zone clusters had many challenges. Dynamic provisioning was handled independently from pod scheduling, which meant that as soon as you created a PersistentVolumeClaim (PVC), a volume would get provisioned. This meant that the provisioner had no knowledge of what pods were using the volume, and any pod constraints it had that could impact scheduling.
+-->
+在此功能被提供之前，在多区域集群中使用区域化的持久磁盘（例如 AWS ElasticBlockStore，Azure Disk，GCE PersistentDisk）运行有状态工作负载存在许多挑战。动态供应独立于 Pod 调度处理，这意味着只要您创建了一个 PersistentVolumeClaim（PVC），一个卷就会被供应。这也意味着供应者不知道哪些 Pod 正在使用该卷，也不清楚任何可能影响调度的 Pod 约束。
+
+<!--
+This resulted in unschedulable pods because volumes were provisioned in zones that:
+-->
+这导致了不可调度的 Pod，因为在以下区域中配置了卷：
+
+<!--
+* did not have enough CPU or memory resources to run the pod
+* conflicted with node selectors, pod affinity or anti-affinity policies
+* could not run the pod due to taints
+-->
+* 没有足够的 CPU 或内存资源来运行 Pod
+* 与节点选择器、Pod 亲和或反亲和策略冲突
+* 由于污点（taint）不能运行 Pod
+
+<!--
+Another common issue was that a non-StatefulSet pod using multiple persistent volumes could have each volume provisioned in a different zone, again resulting in an unschedulable pod.
+-->
+另一个常见问题是，使用多个持久卷的非有状态 Pod 可能会在不同的区域中配置每个卷，从而导致一个不可调度的 Pod。
+
+<!--
+Suboptimal workarounds included overprovisioning of nodes, or manual creation of volumes in the correct zones, making it difficult to dynamically deploy and scale stateful workloads.
+-->
+次优的解决方法包括节点超配，或在正确的区域中手动创建卷，但这会造成难以动态部署和扩展有状态工作负载的问题。
+
+<!--
+The topology-aware dynamic provisioning feature addresses all of the above issues.
+-->
+拓扑感知动态供应功能解决了上述所有问题。
+
+<!--
+## Supported Volume Types
+-->
+## 支持的卷类型
+
+<!--
+In 1.12, the following drivers support topology-aware dynamic provisioning:
+-->
+在 1.12 中，以下驱动程序支持拓扑感知动态供应：
+
+<!--
+* AWS EBS
+* Azure Disk
+* GCE PD (including Regional PD)
+* CSI (alpha) - currently only the GCE PD CSI driver has implemented topology support
+-->
+* AWS EBS
+* Azure Disk
+* GCE PD （包括 Regional PD）
+* CSI（alpha） - 目前只有 GCE PD CSI 驱动实现了拓扑支持
+
+<!--
+## Design Principles
+-->
+## 设计原则
+
+<!--
+While the initial set of supported plugins are all zonal-based, we designed this feature to adhere to the Kubernetes principle of portability across environments. Topology specification is generalized and uses a similar label-based specification like in Pod nodeSelectors and nodeAffinity. This mechanism allows you to define your own topology boundaries, such as racks in on-premise clusters, without requiring modifications to the scheduler to understand these custom topologies.
+-->
+虽然最初支持的插件集都是基于区域的，但我们设计此功能时遵循 Kubernetes 跨环境可移植性的原则。
+拓扑规范是通用的，并使用类似于基于标签的规范，如 Pod nodeSelectors 和 nodeAffinity。
+该机制允许您定义自己的拓扑边界，例如内部部署集群中的机架，而无需修改调度程序以了解这些自定义拓扑。
+
+<!--
+In addition, the topology information is abstracted away from the pod specification, so a pod does not need knowledge of the underlying storage system’s topology characteristics. This means that you can use the same pod specification across multiple clusters, environments, and storage systems.
+-->
+此外，拓扑信息是从 Pod 规范中抽象出来的，因此 Pod 不需要了解底层存储系统的拓扑特征。
+这意味着您可以在多个集群、环境和存储系统中使用相同的 Pod 规范。
+
+<!--
+## Getting Started
+-->
+## 入门
+
+<!--
+To enable this feature, all you need to do is to create a StorageClass with `volumeBindingMode` set to `WaitForFirstConsumer`:
+-->
+要启用此功能，您需要做的就是创建一个将 `volumeBindingMode` 设置为 `WaitForFirstConsumer` 的 StorageClass：
+
+```
+kind: StorageClass
+apiVersion: storage.k8s.io/v1
+metadata:
+  name: topology-aware-standard
+provisioner: kubernetes.io/gce-pd
+volumeBindingMode: WaitForFirstConsumer
+parameters:
+  type: pd-standard
+```
+
+<!--
+This new setting instructs the volume provisioner to not create a volume immediately, and instead, wait for a pod using an associated PVC to run through scheduling. Note that previous StorageClass `zone` and `zones` parameters do not need to be specified anymore, as pod policies now drive the decision of which zone to provision a volume in.
+-->
+这个新设置表明卷配置器不立即创建卷，而是等待使用关联的 PVC 的 Pod 通过调度运行。
+请注意，不再需要指定以前的 StorageClass `zone` 和 `zones` 参数，因为现在在哪个区域中配置卷由 Pod 策略决定。
+
+<!--
+Next, create a pod and PVC with this StorageClass. This sequence is the same as before, but with a different StorageClass specified in the PVC. The following is a hypothetical example, demonstrating the capabilities of the new feature by specifying many pod constraints and scheduling policies:
+-->
+接下来，使用此 StorageClass 创建一个 Pod 和 PVC。
+此过程与之前相同，但在 PVC 中指定了不同的 StorageClass。
+以下是一个假设示例，通过指定许多 Pod 约束和调度策略来演示新功能特性：
+
+<!--
+* multiple PVCs in a pod
+* nodeAffinity across a subset of zones
+* pod anti-affinity on zones
+-->
+* 一个 Pod 多个 PVC
+* 跨子区域的节点亲和
+* 同一区域 Pod 反亲和
+
+```
+apiVersion: apps/v1
+kind: StatefulSet
+metadata:
+  name: web
+spec:   
+  serviceName: "nginx"
+  replicas: 2
+  selector:
+    matchLabels:
+      app: nginx
+  template:
+    metadata:
+      labels:
+        app: nginx
+    spec:
+      affinity:
+        nodeAffinity:
+          requiredDuringSchedulingIgnoredDuringExecution:
+            nodeSelectorTerms:
+            - matchExpressions:
+              - key: failure-domain.beta.kubernetes.io/zone
+                operator: In
+                values:
+                - us-central1-a
+                - us-central1-f
+        podAntiAffinity:
+          requiredDuringSchedulingIgnoredDuringExecution:
+          - labelSelector:
+              matchExpressions:
+              - key: app
+                operator: In
+                values:
+                - nginx
+            topologyKey: failure-domain.beta.kubernetes.io/zone
+      containers:
+      - name: nginx
+        image: gcr.io/google_containers/nginx-slim:0.8
+        ports:
+        - containerPort: 80
+          name: web
+        volumeMounts:
+        - name: www
+          mountPath: /usr/share/nginx/html
+        - name: logs
+          mountPath: /logs
+ volumeClaimTemplates:
+  - metadata:
+      name: www
+    spec:
+      accessModes: [ "ReadWriteOnce" ]
+      storageClassName: topology-aware-standard
+      resources:
+        requests:
+          storage: 10Gi
+  - metadata:
+      name: logs
+    spec:
+      accessModes: [ "ReadWriteOnce" ]
+      storageClassName: topology-aware-standard
+      resources:
+        requests:
+          storage: 1Gi
+```
+
+<!--
+Afterwards, you can see that the volumes were provisioned in zones according to the policies set by the pod:
+-->
+之后，您可以看到根据 Pod 设置的策略在区域中配置卷：
+
+```
+$ kubectl get pv -o=jsonpath='{range .items[*]}{.spec.claimRef.name}{"\t"}{.metadata.labels.failure\-domain\.beta\.kubernetes\.io/zone}{"\n"}{end}'
+www-web-0       us-central1-f
+logs-web-0      us-central1-f
+www-web-1       us-central1-a
+logs-web-1      us-central1-a
+```
+
+<!--
+## How can I learn more?
+-->
+## 我怎样才能了解更多？
+
+<!--
+Official documentation on the topology-aware dynamic provisioning feature is available here:https://kubernetes.io/docs/concepts/storage/storage-classes/#volume-binding-mode
+-->
+有关拓扑感知动态供应功能的官方文档可在此处获取：https://kubernetes.io/docs/concepts/storage/storage-classes/#volume-binding-mode
+
+<!--
+Documentation for CSI drivers is available at https://kubernetes-csi.github.io/docs/
+-->
+有关 CSI 驱动程序的文档，请访问：https://kubernetes-csi.github.io/docs/
+
+<!--
+## What’s next?
+-->
+## 下一步是什么？
+
+<!--
+We are actively working on improving this feature to support:
+-->
+我们正积极致力于改进此功能以支持：
+
+<!--
+* more volume types, including dynamic provisioning for local volumes
+* dynamic volume attachable count and capacity limits per node
+-->
+* 更多卷类型，包括本地卷的动态供应
+* 动态容量可附加计数和每个节点的容量限制
+
+<!--
+## How do I get involved?
+-->
+## 我如何参与？
+
+<!--
+If you have feedback for this feature or are interested in getting involved with the design and development, join the [Kubernetes Storage Special-Interest-Group](https://github.com/kubernetes/community/tree/master/sig-storage) (SIG). We’re rapidly growing and always welcome new contributors.
+-->
+如果您对此功能有反馈意见或有兴趣参与设计和开发，请加入 [Kubernetes 存储特别兴趣小组](https://github.com/kubernetes/community/tree/master/sig-storage)（SIG）。我们正在快速成长，并始终欢迎新的贡献者。
+
+<!--
+Special thanks to all the contributors that helped bring this feature to beta, including Cheng Xing ([verult](https://github.com/verult)), Chuqiang Li ([lichuqiang](https://github.com/lichuqiang)), David Zhu ([davidz627](https://github.com/davidz627)), Deep Debroy ([ddebroy](https://github.com/ddebroy)), Jan Šafránek ([jsafrane](https://github.com/jsafrane)), Jordan Liggitt ([liggitt](https://github.com/liggitt)), Michelle Au ([msau42](https://github.com/msau42)), Pengfei Ni ([feiskyer](https://github.com/feiskyer)), Saad Ali ([saad-ali](https://github.com/saad-ali)), Tim Hockin ([thockin](https://github.com/thockin)), and Yecheng Fu ([cofyc](https://github.com/cofyc)).
+-->
+特别感谢帮助推出此功能的所有贡献者，包括 Cheng Xing ([verult](https://github.com/verult))、Chuqiang Li ([lichuqiang](https://github.com/lichuqiang))、David Zhu ([davidz627](https://github.com/davidz627))、Deep Debroy ([ddebroy](https://github.com/ddebroy))、Jan Šafránek ([jsafrane](https://github.com/jsafrane))、Jordan Liggitt ([liggitt](https://github.com/liggitt))、Michelle Au ([msau42](https://github.com/msau42))、Pengfei Ni ([feiskyer](https://github.com/feiskyer))、Saad Ali ([saad-ali](https://github.com/saad-ali))、Tim Hockin ([thockin](https://github.com/thockin))，以及 Yecheng Fu ([cofyc](https://github.com/cofyc))。
@@ -0,0 +1,73 @@
+---
+layout: blog
+title: '2018 年督导委员会选举结果'
+date: 2018-10-15
+---
+<!--
+---
+layout: blog
+title: '2018 Steering Committee Election Results'
+date: 2018-10-15
+---
+-->
+
+<!-- **Authors**: Jorge Castro (Heptio), Ihor Dvoretskyi (CNCF), Paris Pittman (Google) -->
+**作者**: Jorge Castro (Heptio), Ihor Dvoretskyi (CNCF), Paris Pittman (Google)
+
+<!--
+## Results
+-->
+## 结果
+<!--
+The [Kubernetes Steering Committee Election](https://kubernetes.io/blog/2018/09/06/2018-steering-committee-election-cycle-kicks-off/) is now complete and the following candidates came ahead to secure two year terms that start immediately:
+-->
+[Kubernetes 督导委员会选举](https://kubernetes.io/blog/2018/09/06/2018-steering-committee-election-cycle-kicks-off/)现已完成，以下候选人获得了立即开始的两年任期：
+
+* Aaron Crickenberger, Google, [@spiffxp](https://github.com/spiffxp)
+* Davanum Srinivas, Huawei, [@dims](https://github.com/dims)
+* Tim St. Clair, Heptio, [@timothysc](https://github.com/timothysc)
+
+<!--
+## Big Thanks!
+-->
+## 十分感谢！
+
+<!-- 
+* Steering Committee Member Emeritus [Quinton Hoole](https://github.com/quinton-hoole) for his service to the community over the past year. We look forward to
+* The candidates that came forward to run for election. May we always have a strong set of people who want to push community forward like yours in every election.
+* All 307 voters who cast a ballot.
+* And last but not least...Cornell University for hosting [CIVS](https://civs.cs.cornell.edu/)! 
+-->
+* 督导委员会荣誉退休成员 [Quinton Hoole](https://github.com/quinton-hoole)，表扬他在过去一年为社区所作的贡献。我们期待着
+* 参加竞选的候选人。愿我们永远拥有一群强大的人，他们希望在每一次选举中都能像你们一样推动社区向前发展。
+* 共计 307 名选民参与投票。
+* 本次选举由康奈尔大学主办 [CIVS](https://civs.cs.cornell.edu/)！
+
+<!--
+## Get Involved with the Steering Committee
+-->
+## 加入督导委员会
+<!--
+You can follow along to Steering Committee [backlog items](https://git.k8s.io/steering/backlog.md) and weigh in by filing an issue or creating a PR against their [repo](https://github.com/kubernetes/steering). They meet bi-weekly on [Wednesdays at 8pm UTC](https://github.com/kubernetes/steering) and regularly attend Meet Our Contributors.
+-->
+你可以关注督导委员会的[任务清单](https://git.k8s.io/steering/backlog.md)，并通过向他们的[代码仓库](https://github.com/kubernetes/steering)提交 issue 或 PR 的方式来参与。他们也会在[UTC 时间每周三晚 8 点](https://github.com/kubernetes/steering)举行会议，并定期与我们的贡献者见面。
+
+<!--
+Steering Committee Meetings:
+-->
+督导委员会会议：
+
+* [YouTube 播放列表](https://www.youtube.com/playlist?list=PL69nYSiGNLP1yP1B_nd9-drjoxp0Q14qM)
+
+<!--
+Meet Our Contributors Steering AMA’s: 
+-->
+与我们的贡献者会面：
+
+<!--
+* [Oct  3 2018](https://youtu.be/x6Jm8p0K-IQ)
+* [Sept 5 2018](https://youtu.be/UbxWV12Or58)
+-->
+
+* [2018 年 10 月 3 日](https://youtu.be/x6Jm8p0K-IQ)
+* [2018 年 7 月 5 日](https://youtu.be/UbxWV12Or58)
@@ -0,0 +1,118 @@
+---
+layout: "Blog"
+title: "Kubernetes 2018 年北美贡献者峰会"
+date: 2018-10-16    
+---
+<!--
+---
+layout: "Blog"
+title: "Kubernetes 2018 North American Contributor Summit"
+date: 2018-10-16    
+---
+-->
+<!--
+**Authors:**
+-->
+**作者：**
+<!--
+[Bob Killen][bob] (University of Michigan)
+[Sahdev Zala][sahdev] (IBM),
+[Ihor Dvoretskyi][ihor] (CNCF) 
+-->
+[Bob Killen][bob]（密歇根大学）
+[Sahdev Zala][sahdev]（IBM），
+[Ihor Dvoretskyi][ihor]（CNCF）
+
+<!--
+The 2018 North American Kubernetes Contributor Summit to be hosted right before
+[KubeCon + CloudNativeCon][kubecon] Seattle is shaping up to be the largest yet.
+-->
+2018 年北美 Kubernetes 贡献者峰会将在西雅图 [KubeCon + CloudNativeCon][kubecon] 会议之前举办，这将是迄今为止规模最大的一次盛会。
+<!--
+It is an event that brings together new and current contributors alike to
+connect and share face-to-face; and serves as an opportunity for existing
+contributors to help shape the future of community development. For new
+community members, it offers a welcoming space to learn, explore and put the
+contributor workflow to practice.
+-->
+这是一个将新老贡献者聚集在一起，面对面交流和分享的活动；并为现有的贡献者提供一个机会，帮助塑造社区发展的未来。它为新的社区成员提供了一个学习、探索和实践贡献工作流程的良好空间。
+
+<!--
+Unlike previous Contributor Summits, the event now spans two-days with a more
+relaxed ‘hallway’ track and general Contributor get-together to be hosted from
+5-8pm on Sunday December 9th at the [Garage Lounge and Gaming Hall][garage], just
+a short walk away from the Convention Center. There, contributors can enjoy
+billiards, bowling, trivia and more; accompanied by a variety of food and drink. 
+-->
+与之前的贡献者峰会不同，本次活动为期两天，有一个更为轻松的行程安排，一般贡献者将于 12 月 9 日（周日）下午 5 点至 8 点在距离会议中心仅几步远的 [Garage Lounge and Gaming Hall][garage] 举办峰会。在那里，贡献者也可以进行台球、保龄球等娱乐活动，而且还有各种食品和饮料。
+
+<!--
+Things pick up the following day, Monday the 10th with three separate tracks: 
+-->
+接下来的一天，也就是 10 号星期一，有三个独立的会议你可以选择参与：
+
+<!--
+### New Contributor Workshop:
+A half day workshop aimed at getting new and first time contributors onboarded
+and comfortable with working within the Kubernetes Community. Staying for the
+duration is required; this is not a workshop you can drop into. 
+-->
+### 新贡献者研讨会：
+
+为期半天的研讨会旨在让新贡献者加入社区，并营造一个良好的 Kubernetes 社区工作环境。
+请在开会期间保持在场，该讨论会不允许随意进出。
+
+<!--
+### Current Contributor Track:
+Reserved for those that are actively engaged with the development of the
+project; the Current Contributor Track includes Talks, Workshops, Birds of a
+Feather, Unconferences, Steering Committee Sessions, and more! Keep an eye on
+the [schedule in GitHub][schedule] as content is frequently being updated.
+-->
+### 当前贡献者追踪：
+
+保留给那些积极参与项目开发的贡献者；目前的贡献者追踪包括讲座、研讨会、聚会、Unconferences 会议、指导委员会会议等等!
+请留意 [GitHub 中的时间表][时间表]，因为内容经常更新。
+
+<!--
+### Docs Sprint:
+SIG-Docs will have a curated list of issues and challenges to be tackled closer
+to the event date.
+-->
+### Docs 冲刺：
+
+SIG-Docs 将在活动日期临近的时候列出一个需要处理的问题和挑战列表。
+
+<!--
+## To Register:
+To register for the Contributor Summit, see the [Registration section of the
+Event Details in GitHub][register]. Please note that registrations are being
+reviewed. If you select the “Current Contributor Track” and are not an active
+contributor, you will be asked to attend the New Contributor Workshop, or asked
+to be put on a waitlist. With thousands of contributors and only 300 spots, we
+need to make sure the right folks are in the room. 
+-->
+## 注册：
+
+要注册贡献者峰会，请参阅 Git Hub 上的[活动详情注册部分][注册]。请注意报名正在审核中。
+如果您选择了 “当前贡献者追踪”，而您却不是一个活跃的贡献者，您将被要求参加新贡献者研讨会，或者被要求进入候补名单。
+成千上万的贡献者只有 300 个位置，我们需要确保正确的人被安排席位。
+
+<!--
+If you have any questions or concerns, please don’t hesitate to reach out to
+the Contributor Summit Events Team at community@kubernetes.io.
+-->
+如果您有任何问题或疑虑，请随时通过 community@kubernetes.io 联系贡献者峰会组织团队。
+
+<!--
+Look forward to seeing everyone there!
+-->
+期待在那里看到每个人！
+
+[bob]: https://twitter.com/mrbobbytables
+[sahdev]: https://twitter.com/sp_zala
+[ihor]: https://twitter.com/idvoretskyi
+[kubecon]: https://events.linuxfoundation.org/events/kubecon-cloudnativecon-north-america-2018/
+[garage]: https://www.garagebilliards.com/
+[时间表]: https://git.k8s.io/community/events/2018/12-contributor-summit#agenda
+[注册]:  https://git.k8s.io/community/events/2018/12-contributor-summit#registration
@@ -0,0 +1,89 @@
+---
+layout: blog
+title: 'Kubernetes 文档更新，国际版'
+date: 2018-11-08
+---
+<!--
+---
+layout: blog
+title: 'Kubernetes Docs Updates, International Edition'
+date: 2018-11-08
+---
+-->
+
+<!-- **Author**: Zach Corleissen (Linux Foundation) -->
+**作者**：Zach Corleissen （Linux 基金会）
+
+<!-- As a co-chair of SIG Docs, I'm excited to share that Kubernetes docs have a fully mature workflow for localization (l10n).  -->
+作为文档特别兴趣小组（SIG Docs）的联合主席，我很高兴能与大家分享 Kubernetes 文档在本地化（l10n）方面所拥有的一个完全成熟的工作流。
+
+<!-- ## Abbreviations galore -->
+## 丰富的缩写
+
+<!-- L10n is an abbreviation for _localization_. -->
+L10n 是 _localization_ 的缩写。
+
+<!-- I18n is an abbreviation for _internationalization_.  -->
+I18n 是 _internationalization_ 的缩写。
+
+<!-- I18n is [what you do](https://www.w3.org/International/questions/qa-i18n) to make l10n easier. L10n is a fuller, more comprehensive process than translation (_t9n_). -->
+I18n 定义了[做什么](https://www.w3.org/International/questions/qa-i18n) 能让 l10n 更容易。而 L10n 更全面，相比翻译（ _t9n_ ）具备更完善的流程。
+
+<!-- ## Why localization matters -->
+## 为什么本地化很重要
+
+<!-- The goal of SIG Docs is to make Kubernetes easier to use for as many people as possible. -->
+SIG Docs 的目标是让 Kubernetes 更容易为尽可能多的人使用。
+
+<!-- One year ago, we looked at whether it was possible to host the output of a Chinese team working independently to translate the Kubernetes docs. After many conversations (including experts on OpenStack l10n), [much transformation](https://kubernetes.io/blog/2018/05/05/hugo-migration/), and [renewed commitment to easier localization](https://github.com/kubernetes/website/pull/10485), we realized that open source documentation is, like open source software, an ongoing exercise at the edges of what's possible. -->
+一年前，我们研究了是否有可能由一个独立翻译 Kubernetes 文档的中国团队来主持文档输出。经过多次交谈（包括 OpenStack l10n 的专家），[多次转变](https://kubernetes.io/blog/2018/05/05/hugo-migration/)，以及[重新致力于更轻松的本地化](https://github.com/kubernetes/website/pull/10485)，我们意识到，开源文档就像开源软件一样，是在可能的边缘不断进行实践。
+
+<!-- Consolidating workflows, language labels, and team-level ownership may seem like simple improvements, but these features make l10n scalable for increasing numbers of l10n teams. While SIG Docs continues to iterate improvements, we've paid off a significant amount of technical debt and streamlined l10n in a single workflow. That's great for the future as well as the present. -->
+整合工作流程、语言标签和团队级所有权可能看起来像是十分简单的改进，但是这些功能使 l10n 可以扩展到规模越来越大的 l10n 团队。随着 SIG Docs 不断改进，我们已经在单一工作流程中偿还了大量技术债务并简化了 l10n。这对未来和现在都很有益。
+
+<!-- ## Consolidated workflow -->
+## 整合的工作流程
+
+<!-- Localization is now consolidated in the [kubernetes/website](https://github.com/kubernetes/website) repository. We've configured the Kubernetes CI/CD system, [Prow](https://github.com/kubernetes/test-infra/tree/master/prow), to handle automatic language label assignment as well as team-level PR review and approval. -->
+现在，本地化已整合到 [kubernetes/website](https://github.com/kubernetes/website) 存储库。我们已经配置了 Kubernetes CI/CD 系统，[Prow](https://github.com/kubernetes/test-infra/tree/master/prow) 来处理自动语言标签分配以及团队级 PR 审查和批准。
+
+<!-- ### Language labels  -->
+### 语言标签
+
+<!-- Prow automatically applies language labels based on file path. Thanks to SIG Docs contributor [June Yi](https://github.com/kubernetes/test-infra/pull/9835), folks can also manually assign language labels in pull request (PR) comments. For example, when left as a comment on an issue or PR, this command assigns the label `language/ko` (Korean). -->
+Prow 根据文件路径自动添加语言标签。感谢 SIG Docs 贡献者 [June Yi](https://github.com/kubernetes/test-infra/pull/9835)，他让人们还可以在 pull request（PR）注释中手动分配语言标签。例如，当为 issue 或 PR 留下下述注释时，将为之分配标签 `language/ko`（Korean）。
+
+```
+/language ko
+```
+
+
+<!-- These repo labels let reviewers filter for PRs and issues by language. For example, you can now filter the k/website dashboard for [PRs with Chinese content](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+label%3Alanguage%2Fzh).   -->
+这些存储库标签允许审阅者按语言过滤 PR 和 issue。例如，您现在可以过滤 kubernetes/website 面板中[具有中文内容的 PR](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+label%3Alanguage%2Fzh)。
+
+<!-- ### Team review  -->
+### 团队审核
+
+<!-- L10n teams can now review and approve their own PRs. For example, review and approval permissions for English are [assigned in an OWNERS file](https://github.com/kubernetes/website/blob/master/content/en/OWNERS) in the top subfolder for English content.  -->
+L10n 团队现在可以审查和批准他们自己的 PR。例如，英语的审核和批准权限在位于用于显示英语内容的顶级子文件夹中的 [OWNERS 文件中指定](https://github.com/kubernetes/website/blob/master/content/en/OWNERS)。
+
+<!-- Adding `OWNERS` files to subdirectories lets localization teams review and approve changes without requiring a rubber stamp approval from reviewers who may lack fluency. -->
+将 `OWNERS` 文件添加到子目录可以让本地化团队审查和批准更改，而无需由可能并不擅长该门语言的审阅者进行批准。
+
+<!-- ## What's next -->
+## 下一步是什么
+
+<!-- We're looking forward to the [doc sprint in Shanghai](https://kccncchina2018english.sched.com/event/HVb2/contributor-summit-doc-sprint-additional-registration-required) to serve as a resource for the Chinese l10n team. -->
+我们期待着[上海的 doc sprint](https://kccncchina2018english.sched.com/event/HVb2/contributor-summit-doc-sprint-additional-registration-required) 能作为中国 l10n 团队的资源。
+
+<!-- We're excited to continue supporting the Japanese and Korean l10n teams, who are making excellent progress. -->
+我们很高兴继续支持正在取得良好进展的日本和韩国 l10n 队伍。
+
+<!-- If you're interested in localizing Kubernetes for your own language or region, check out our [guide to localizing Kubernetes docs](https://kubernetes.io/docs/contribute/localization/) and reach out to a [SIG Docs chair](https://github.com/kubernetes/community/tree/master/sig-docs#leadership) for support. -->
+如果您有兴趣将 Kubernetes 本地化为您自己的语言或地区，请查看我们的[本地化 Kubernetes 文档指南](https://kubernetes.io/docs/contribute/localization/)，并联系 [SIG Docs 主席团](https://github.com/kubernetes/community/tree/master/sig-docs#leadership)获取支持。
+
+<!-- ### Get involved with SIG Docs  -->
+### 加入SIG Docs
+
+<!-- If you're interested in Kubernetes documentation, come to a SIG Docs [weekly meeting](https://github.com/kubernetes/community/tree/master/sig-docs#meetings), or join [#sig-docs in Kubernetes Slack](https://kubernetes.slack.com/messages/C1J0BPD2M/details/). -->
+如果您对 Kubernetes 文档感兴趣，请参加 SIG Docs [每周会议](https://github.com/kubernetes/community/tree/master/sig-docs#meetings)，或在 [Kubernetes Slack 加入 #sig-docs](https://kubernetes.slack.com/messages/C1J0BPD2M/details/)。
@@ -3,8 +3,7 @@ layout: blog
 title: '新贡献者工作坊上海站'
 date: 2018-12-05
 ---
-
-<!-- 
+<!--
 ---
 layout: blog
 title: 'New Contributor Workshop Shanghai'
@@ -12,103 +11,103 @@ date: 2018-12-05
 ---
 -->

-<!-- 
+<!--
 **Authors**: Josh Berkus (Red Hat), Yang Li (The Plant), Puja Abbassi (Giant Swarm), XiangPeng Zhao (ZTE)
 -->

 **作者**: Josh Berkus (红帽), Yang Li (The Plant), Puja Abbassi (Giant Swarm), XiangPeng Zhao (中兴通讯)

-<!-- 
+<!--
 {{< figure src="/images/blog/2018-12-05-new-contributor-shanghai/attendees.png" caption="KubeCon Shanghai New Contributor Summit attendees. Photo by Jerry Zhang" >}}
 -->

 {{< figure src="/images/blog/2018-12-05-new-contributor-shanghai/attendees.png" caption="KubeCon 上海站新贡献者峰会与会者，摄影：Jerry Zhang" >}}

-<!-- 
+<!--
 We recently completed our first New Contributor Summit in China, at the first KubeCon in China. It was very exciting to see all of the Chinese and Asian developers (plus a few folks from around the world) interested in becoming contributors. Over the course of a long day, they learned how, why, and where to contribute to Kubernetes, created pull requests, attended a panel of current contributors, and got their CLAs signed.
 -->

 最近，在中国的首次 KubeCon 上，我们完成了在中国的首次新贡献者峰会。看到所有中国和亚洲的开发者（以及来自世界各地的一些人）有兴趣成为贡献者，这令人非常兴奋。在长达一天的课程中，他们了解了如何、为什么以及在何处为 Kubernetes 作出贡献，创建了 PR，参加了贡献者圆桌讨论，并签署了他们的 CLA。

-<!-- 
+<!--
 This was our second New Contributor Workshop (NCW), building on the one created and led by SIG Contributor Experience members in Copenhagen. Because of the audience, it was held in both Chinese and English, taking advantage of the superb simultaneous interpretation services the CNCF sponsored. Likewise, the NCW team included both English and Chinese-speaking members of the community: Yang Li, XiangPeng Zhao, Puja Abbassi, Noah Abrahams, Tim Pepper, Zach Corleissen, Sen Lu, and Josh Berkus. In addition to presenting and helping students, the bilingual members of the team translated all of the slides into Chinese. Fifty-one students attended.
 -->

 这是我们的第二届新贡献者工作坊（NCW），它由前一次贡献者体验 SIG 成员创建和领导的哥本哈根研讨会延伸而来。根据受众情况，本次活动采用了中英文两种语言，充分利用了 CNCF 赞助的一流的同声传译服务。同样，NCW 团队由社区成员组成，既有说英语的，也有说汉语的：Yang Li、XiangPeng Zhao、Puja Abbassi、Noah Abrahams、Tim Pepper、Zach Corleissen、Sen Lu 和 Josh Berkus。除了演讲和帮助学员外，团队的双语成员还将所有幻灯片翻译成了中文。共有五十一名学员参加。

-<!-- 
+<!--
 {{< figure src="/images/blog/2018-12-05-new-contributor-shanghai/noahabrahams.png" caption="Noah Abrahams explains Kubernetes communications channels. Photo by Jerry Zhang" >}}
 -->

 {{< figure src="/images/blog/2018-12-05-new-contributor-shanghai/noahabrahams.png" caption="Noah Abrahams 讲解 Kubernetes 沟通渠道。摄影：Jerry Zhang" >}}

-<!-- 
+<!--
 The NCW takes participants through the stages of contributing to Kubernetes, starting from deciding where to contribute, followed by an introduction to the SIG system and our repository structure. We also have "guest speakers" from Docs and Test Infrastructure who cover contributing in those areas. We finally wind up with some hands-on exercises in filing issues and creating and approving PRs.
 -->

 NCW 让参与者完成了为 Kubernetes 作出贡献的各个阶段，从决定在哪里作出贡献开始，接着介绍了 SIG 系统和我们的代码仓库结构。我们还有来自文档和测试基础设施领域的「客座讲者」，他们负责讲解有关的贡献。最后，我们在创建 issue、提交并批准 PR 的实践练习后，结束了工作坊。

-<!-- 
+<!--
 Those hands-on exercises use a repository known as [the contributor playground](https://github.com/kubernetes-sigs/contributor-playground), created by SIG Contributor Experience as a place for new contributors to try out performing various actions on a Kubernetes repo. It has modified Prow and Tide automation, uses Owners files like in the real repositories. This lets students learn how the mechanics of contributing to our repositories work without disrupting normal development.
 -->

 这些实践练习使用一个名为[贡献者游乐场](https://github.com/kubernetes-sigs/contributor-playground)的代码仓库，由贡献者体验 SIG 创建，让新贡献者尝试在一个 Kubernetes 仓库中执行各种操作。它修改了 Prow 和 Tide 自动化，使用与真实代码仓库类似的 Owners 文件。这可以让学员了解为我们的仓库做出贡献的有关机制，同时又不妨碍正常的开发流程。

-<!-- 
+<!--
 {{< figure src="/images/blog/2018-12-05-new-contributor-shanghai/yangli.png" caption="Yang Li talks about getting your PRs reviewed. Photo by Josh Berkus" >}}
 -->

 {{< figure src="/images/blog/2018-12-05-new-contributor-shanghai/yangli.png" caption="Yang Li 讲到如何让你的 PR 通过评审。摄影：Josh Berkus" >}}

-<!-- 
+<!--
 Both the "Great Firewall" and the language barrier prevent contributing Kubernetes from China from being straightforward. What's more, because open source business models are not mature in China, the time for employees work on open source projects is limited.
 -->

 「防火长城」和语言障碍都使得在中国为 Kubernetes 作出贡献变得困难。而且，中国的开源商业模式并不成熟，员工在开源项目上工作的时间有限。

-<!-- 
+<!--
 Chinese engineers are eager to participate in the development of Kubernetes, but many of them don't know where to start since Kubernetes is such a large project. With this workshop, we hope to help those who want to contribute, whether they wish to fix some bugs they encountered, improve or localize documentation, or they need to work with Kubernetes at their work. We are glad to see more and more Chinese contributors joining the community in the past few years, and we hope to see more of them in the future.
 -->

 中国工程师渴望参与 Kubernetes 的研发，但他们中的许多人不知道从何处开始，因为 Kubernetes 是一个如此庞大的项目。通过本次工作坊，我们希望帮助那些想要参与贡献的人，不论他们希望修复他们遇到的一些错误、改进或本地化文档，或者他们需要在工作中用到 Kubernetes。我们很高兴看到越来越多的中国贡献者在过去几年里加入社区，我们也希望将来可以看到更多。

-<!-- 
+<!--
 "I have been participating in the Kubernetes community for about three years," said XiangPeng Zhao. "In the community, I notice that more and more Chinese developers are showing their interest in contributing to Kubernetes. However, it's not easy to start contributing to such a project. I tried my best to help those who I met in the community, but I think there might still be some new contributors leaving the community due to not knowing where to get help when in trouble. Fortunately, the community initiated NCW at KubeCon Copenhagen and held a second one at KubeCon Shanghai. I was so excited to be invited by Josh Berkus to help organize this workshop. During the workshop, I met community friends in person, mentored attendees in the exercises, and so on. All of this was a memorable experience for me. I also learned a lot as a contributor who already has years of contributing experience. I wish I had attended such a workshop when I started contributing to Kubernetes years ago."
 -->

 「我已经参与了 Kubernetes 社区大约三年」，XiangPeng Zhao 说，「在社区，我注意到越来越多的中国开发者表现出对 Kubernetes 贡献的兴趣。但是，开始为这样一个项目做贡献并不容易。我尽力帮助那些我在社区遇到的人，但是，我认为可能仍有一些新的贡献者离开社区，因为他们在遇到麻烦时不知道从哪里获得帮助。幸运的是，社区在 KubeCon 哥本哈根站发起了 NCW，并在 KubeCon 上海站举办了第二届。我很高兴受到 Josh Berkus 的邀请，帮助组织这个工作坊。在工作坊期间，我当面见到了社区里的朋友，在练习中指导了与会者，等等。所有这些对我来说都是难忘的经历。作为有着多年贡献者经验的我，也学习到了很多。我希望几年前我开始为 Kubernetes 做贡献时参加过这样的工作坊」。

-<!-- 
+<!--
 {{< figure src="/images/blog/2018-12-05-new-contributor-shanghai/panel.png" caption="Panel of contributors. Photo by Jerry Zhang" >}}
 -->

 {{< figure src="/images/blog/2018-12-05-new-contributor-shanghai/panel.png" caption="贡献者圆桌讨论。摄影：Jerry Zhang" >}}

-<!-- 
+<!--
 The workshop ended with a panel of current contributors, featuring Lucas Käldström, Janet Kuo, Da Ma, Pengfei Ni, Zefeng Wang, and Chao Xu. The panel aimed to give both new and current contributors a look behind the scenes on the day-to-day of some of the most active contributors and maintainers, both from China and around the world. Panelists talked about where to begin your contributor's journey, but also how to interact with reviewers and maintainers. They further touched upon the main issues of contributing from China and gave attendees an outlook into exciting features they can look forward to in upcoming releases of Kubernetes.
 -->

 工作坊以现有贡献者圆桌讨论结束，嘉宾包括 Lucas Käldström、Janet Kuo、Da Ma、Pengfei Ni、Zefeng Wang 和 Chao Xu。这场圆桌讨论旨在让新的和现有的贡献者了解一些最活跃的贡献者和维护者的幕后日常工作，不论他们来自中国还是世界各地。嘉宾们讨论了从哪里开始贡献者的旅程，以及如何与评审者和维护者进行互动。他们进一步探讨了在中国参与贡献的主要问题，并向与会者预告了在 Kubernetes 的未来版本中可以期待的令人兴奋的功能。

-<!-- 
+<!--
 After the workshop, XiangPeng Zhao chatted with some attendees on WeChat and Twitter about their experiences. They were very glad to have attended the NCW and had some suggestions on improving the workshop. One attendee, Mohammad, said, "I had a great time at the workshop and learned a lot about the entire process of k8s for a contributor." Another attendee, Jie Jia, said, "The workshop was wonderful. It systematically explained how to contribute to Kubernetes. The attendee could understand the process even if s/he knew nothing about that before. For those who were already contributors, they could also learn something new. Furthermore, I could make new friends from inside or outside of China in the workshop. It was awesome!"
 -->

 工作坊结束后，XiangPeng Zhao 和一些与会者就他们的经历在微信和 Twitter 上进行了交谈。他们很高兴参加了 NCW，并就改进工作坊提出了一些建议。一位名叫 Mohammad 的与会者说：「我在工作坊上玩得很开心，学习了参与 k8s 贡献的整个过程。」另一位与会者 Jie Jia 说：「工作坊非常精彩。它系统地解释了如何为 Kubernetes 做出贡献。即使参与者之前对此一无所知，他（她）也可以理解这个过程。对于那些已经是贡献者的人，他们也可以学习到新东西。此外，我还可以在工作坊上结识来自国内外的新朋友。真是棒极了！」

-<!-- 
+<!--
 SIG Contributor Experience will continue to run New Contributor Workshops at each upcoming KubeCon, including Seattle, Barcelona, and the return to Shanghai in June 2019. If you failed to get into one this year, register for one at a future KubeCon. And, when you meet an NCW attendee, make sure to welcome them to the community.
 -->

 贡献者体验 SIG 将继续在未来的 KubeCon 上举办新贡献者工作坊，包括西雅图站、巴塞罗那站，然后在 2019 年六月回到上海。如果你今年未能参加，请在未来的 KubeCon 上注册。并且，如果你遇到工作坊的与会者，请务必欢迎他们加入社区。

-<!-- 
+<!--
 Links:
 -->

 链接：

-<!-- 
+<!--
 * English versions of the slides: [PDF](https://gist.github.com/jberkus/889be25c234b01761ce44eccff816380#file-kubernetes-shanghai-english-pdf) or [Google Docs with speaker notes](https://docs.google.com/presentation/d/1l5f_iAFsKg50LFq3N80KbZKUIEL_tyCaUoWPzSxColo/edit?usp=sharing)
 * Chinese version of the slides: [PDF](https://gist.github.com/jberkus/889be25c234b01761ce44eccff816380#file-kubernetes-shanghai-cihinese-pdf)
 * [Contributor playground](https://github.com/kubernetes-sigs/contributor-playground)
@@ -1,23 +1,21 @@
---
-title: 案例研究
-linkTitle: 案例研究
-bigheader: Kubernetes 用户案例研究
-abstract: 在生产环境中运行 Kubernetes 的用户集合。
-layout: basic
-class: gridPage
-cid: caseStudies
---
-
-<!--
-
---
-title: Case Studies
-linkTitle: Case Studies
-bigheader: Kubernetes User Case Studies
-abstract: A collection of users running Kubernetes in production.
-layout: basic
-class: gridPage
-cid: caseStudies
---
-
-->
+---
+title: 案例分析
+linkTitle: 案例分析
+bigheader: Kubernetes 用户案例分析
+abstract: 在生产环境下使用 Kubernetes 的案例集
+layout: basic
+class: gridPage
+cid: caseStudies
+---
+
+<!--
+---
+title: Case Studies
+linkTitle: Case Studies
+bigheader: Kubernetes User Case Studies
+abstract: A collection of users running Kubernetes in production.
+layout: basic
+class: gridPage
+cid: caseStudies
+---
+-->
@@ -0,0 +1,4 @@
+---
+title: CCP Games
+content_url: https://cloud.google.com/customers/ccp-games/
+---
@@ -0,0 +1,4 @@
+---
+title: Goldman Sachs
+content_url: http://blogs.wsj.com/cio/2016/02/24/big-changes-in-goldmans-software-emerge-from-small-containers/
+---
@@ -0,0 +1,433 @@
+---
+title: 华为案例分析
+
+case_study_styles: true
+cid: caseStudies
+css: /css/style_huawei.css
+---
+
+<!--
+---
+title: Huawei Case Study
+
+case_study_styles: true
+cid: caseStudies
+css: /css/style_huawei.css
+---
+-->
+
+<div class="banner1">
+  <h1> 案例分析：<img src="/images/huawei_logo.png" class="header_logo"><br> <div class="subhead">以用户和供应商身份拥抱云原生</div></h1>
+  <!--
+  <h1> CASE STUDY:<img src="/images/huawei_logo.png" class="header_logo"><br> <div class="subhead">Embracing Cloud Native as a User – and a Vendor</div></h1>
+  -->
+</div>
+
+<div class="details">
+    公司 &nbsp;<b>华为</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;地点 &nbsp;<b>中国深圳</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;产业 &nbsp;<b>通信设备</b>
+    <!--
+    Company &nbsp;<b>Huawei</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Location &nbsp;<b>Shenzhen, China</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Industry &nbsp;<b>Telecommunications Equipment</b>
+    -->
+</div>
+
+<hr>
+
+<section class="section1">
+
+<div class="cols">
+  <div class="col1">
+    <h2>挑战</h2>
+    <!--
+    <h2>Challenge</h2>
+    -->
+      华为是世界上最大的电信设备制造商，拥有超过 18 万名员工。
+      <!--
+      A multinational company that’s the largest telecommunications equipment manufacturer in the world, 
+      Huawei has more than 180,000 employees. 
+      -->
+
+      为了支持华为在全球的快速业务发展，<a href="http://www.huawei.com/">华为</a>内部 IT 部门有 8 个数据中心，
+      这些数据中心在 100K+ VMs 上运行了 800 多个应用程序，服务于这 18 万用户。
+      <!--
+      In order to support its fast business development around the globe, 
+      <a href="http://www.huawei.com/">Huawei</a> has eight data centers for its internal I.T. department,
+      which have been running 800+ applications in 100K+ VMs to serve these 180,000 users. 
+      -->
+
+      随着新应用程序的快速增长，基于 VM 的应用程序的管理和部署的成本和效率都成为业务敏捷性的关键挑战。
+      <!--
+      With the rapid increase of new applications, the cost and efficiency of management and 
+      deployment of VM-based apps all became critical challenges for business agility.
+      -->
+
+      该公司首席软件架构师、开源社区总监侯培新表示：
+      “这是一个超大的分布式系统，因此我们发现，以更一致的方式管理所有任务始终是一个挑战。
+      我们希望进入一种更敏捷、更得体的实践”。
+      <!--
+      "It’s very much a distributed system so we found that managing all of the tasks 
+      in a more consistent way is always a challenge," says Peixin Hou, 
+      the company’s Chief Software Architect and Community Director for Open Source. 
+      "We wanted to move into a more agile and decent practice."  
+      -->
+
+  </div>
+
+<div class="col2">
+  <h2>解决方案</h2>
+  <!--
+  <h2>Solution</h2>
+  -->
+      在决定使用容器技术后，华为开始将内部 IT 部门的应用程序迁移到<a href="http://kubernetes.io/"> Kubernetes </a>上运行。
+      到目前为止，大约 30% 的应用程序已经转移为云原生程序。
+      <!--
+      After deciding to use container technology, Huawei began moving the internal I.T. department’s applications 
+      to run on <a href="http://kubernetes.io/">Kubernetes</a>.
+      So far, about 30 percent of these applications have been transferred to cloud native.  
+      -->
+<br>
+<br>
+<h2>影响</h2>
+<!--
+<h2>Impact</h2>  
+-->
+      “到 2016 年底，华为的内部 IT 部门使用基于 Kubernetes 的平台即服务（PaaS）解决方案管理了 4000 多个节点和数万个容器。
+      全局部署周期从一周缩短到几分钟，应用程序交付效率提高了 10 倍”。
+      <!--
+       "By the end of 2016, Huawei’s internal I.T. department managed more than 4,000 nodes with tens of thousands containers 
+       using a Kubernetes-based Platform as a Service (PaaS) solution," says Hou.
+       "The global deployment cycles decreased from a week to minutes, and the efficiency of application delivery has been improved 10 fold."
+      -->
+
+      对于底线，侯培新表示，“我们还看到运营开支大幅削减，在某些情况下可削减 20% 到 30%，我们认为这对我们的业务非常有帮助”。
+      <!--
+      For the bottom line, he says, "We also see significant operating expense spending cut, in some circumstances 20-30 percent, 
+      which we think is very helpful for our business."
+      -->
+      
+      这里给出一些华为内部结果资料、外部需求，也是公司的技术包装产品<a href="http://developer.huawei.com/ict/en/site-paas"> FusionStage™ </a>，
+      它被作为一套 PaaS 解决方案提供给其客户。
+      <!--
+      Given the results Huawei has had internally – and the demand it is seeing externally – the company has also built the technologies 
+      into <a href="http://developer.huawei.com/ict/en/site-paas">FusionStage™</a>, the PaaS solution it offers its customers. 
+      -->
+</div>
+
+</div>
+
+</section>
+
+<div class="banner2">
+  <div class="banner2text">
+    “如果你是一个供应商，为了说服你的客户，你应该自己使用它。
+    幸运的是，因为华为有很多员工，我们可以利用这种技术来展示我们所能构建的云的规模。”
+    <!--
+    "If you’re a vendor, in order to convince your customer, you should use it yourself. 
+    Luckily because Huawei has a lot of employees, 
+    we can demonstrate the scale of cloud we can build using this technology."
+    -->
+
+    <br style="height:25px">
+    <span style="font-size:14px;letter-spacing:2px;text-transform:uppercase;margin-top:5% !important;">
+        <br>- 侯培新，首席软件架构师、开源社区总监
+        <!--
+        <br>- Peixin Hou, chief software architect and community director for open source
+        -->
+    </span>  
+  </div>
+</div>
+
+<section class="section2">
+
+<div class="fullcol">
+    华为的 Kubernetes 之旅始于一位开发者。
+    <!--
+    Huawei’s Kubernetes journey began with one developer. 
+    -->
+
+    两年前，这家网络和电信巨头雇佣的一名工程师对<a href="http://kubernetes.io/"> Kubernetes </a>
+    这一跨主机集群的管理应用程序容器的技术产生了兴趣，并开始为其开源社区作出贡献。
+    <!--
+    Over two years ago, one of the engineers employed by the networking and telecommunications giant became interested 
+    in <a href="http://kubernetes.io/">Kubernetes</a>, 
+    the technology for managing application containers across clusters of hosts, 
+    and started contributing to its open source community.
+    -->
+
+    随着技术和社区的发展，他不断地将这门技术告诉他的经理们。<br><br>
+    <!--
+    As the technology developed and the community grew, he kept telling his managers about it.<br><br>  
+    -->
+
+    与此同时，华为也在为其内部的企业 IT 部门寻找更好的编排系统，该系统应该支持每一个业务的流程处理。
+    <!--
+    And as fate would have it, at the same time, 
+    Huawei was looking for a better orchestration system for its internal enterprise I.T. department, 
+    which supports every business flow processing. 
+    -->
+
+    华为首席软件架构师、开源社区总监侯培新表示，
+    “我们在全球拥有逾 18 万名员工，内部流程复杂，所以这个部门可能每周都需要开发一些新的应用程序。
+    <!--
+    "We have more than 180,000 employees worldwide, and a complicated internal procedure, 
+    so probably every week this department needs to develop some new applications," says Peixin Hou, 
+    Huawei’s Chief Software Architect and Community Director for Open Source. 
+    -->
+
+    我们的 IT 部门经常需要启动数万个容器，任务要跨越全球数千个节点。
+    这是一个超大的分布式的系统，所以我们发现以更一致的方式管理所有的任务总是一个挑战”。<br><br>  
+    <!--
+    "Very often our I.T. departments need to launch tens of thousands of containers, 
+    with tasks running across thousands of nodes across the world. 
+    It’s very much a distributed system, so we found that managing all of the tasks 
+    in a more consistent way is always a challenge."<br><br>
+    -->
+
+    过去，华为曾使用虚拟机来封装应用程序，但是，“每次我们启动虚拟机时”，侯培新说，
+    “无论是因为它是一项新服务，还是因为它是一项由于节点功能异常而被关闭的服务，都需要花费大量时间”。
+    <!--
+    In the past, Huawei had used virtual machines to encapsulate applications, 
+    but "every time when we start a VM," Hou says, 
+    "whether because it’s a new service or because it was a service that was shut down 
+    because of some abnormal node functioning, it takes a lot of time." 
+    -->
+
+    华为转向了容器化，所以是时候尝试 Kubernetes 了。
+    采纳了这位工程师的建议花费了一年的时间，这个过程“不是一蹴而就的”，侯说，
+    <!--
+    Huawei turned to containerization, so the timing was right to try Kubernetes. 
+    It took a year to adopt that engineer’s suggestion – the process "is not overnight," says Hou – 
+    -->
+
+    但一旦投入使用，“Kubernetes 基本上解决了我们的大部分问题。
+    以前，部署时间大约需要一周，现在只需几分钟。
+    <!--
+    but once in use, he says, "Kubernetes basically solved most of our problems. 
+    Before, the time of deployment took about a week, now it only takes minutes. 
+    -->
+
+    开发人员非常高兴。使用 Kubernetes 的那个部门也十分高兴”。<br><br>  
+    <!--
+    The developers are happy. That department is also quite happy."<br><br>
+    -->
+
+    侯培新看到了使用这项技术给公司带来的巨大好处，
+    “Kubernetes 为基于云的应用程序带来了敏捷性、扩展能力和 DevOps 实践”，他说，
+    <!--
+    Hou sees great benefits to the company that come with using this technology: 
+    "Kubernetes brings agility, scale-out capability, 
+    and DevOps practice to the cloud-based applications," he says.
+    -->
+    
+    “它为我们提供了自定义调度体系结构的能力，这使得容器任务之间的关联性成为可能，从而提高了效率。
+    它支持多种容器格式，同时广泛支持各种容器网络解决方案和容器存储方案”。
+    <!--
+    "It provides us with the ability to customize the scheduling architecture, 
+    which makes possible the affinity between container tasks that gives greater efficiency. 
+    It supports multiple container formats. It has extensive support for various container 
+    networking solutions and container storage."
+    -->
+</div>
+</section>
+
+<div class="banner3">
+  <div class="banner3text">
+    “Kubernetes 基本上解决了我们的大部分问题。
+    以前，部署时间大约需要一周，现在只需几分钟。
+    开发人员很高兴。使用 Kubernetes 的部门也很高兴。”
+    <!--
+    "Kubernetes basically solved most of our problems. 
+    Before, the time of deployment took about a week, now it only takes minutes. 
+    The developers are happy. That department is also quite happy."  
+    -->
+  </div>
+</div>
+
+<section class="section3">
+<div class="fullcol">
+      最重要的是，这对底线有影响。侯培新说，
+      “我们还看到，在某些情况下，运营开支会大幅削减 20% 到 30%，这对我们的业务非常有帮助”。<br><br>
+      <!--
+      And not least of all, there’s an impact on the bottom line. 
+      Says Hou: "We also see significant operating expense spending cut in some circumstances 20-30 percent, 
+      which is very helpful for our business."<br><br>
+      -->
+
+    华为对这些初步结果感到满意，并看到客户对云原生技术的需求，因此加大了 Kubernetes 的投入。
+    2016 年春，公司不仅成为用户，而且成为了供应商。<br><br>
+    <!--
+    Pleased with those initial results, and seeing a demand for cloud native technologies from its customers, 
+    Huawei doubled down on Kubernetes. 
+    In the spring of 2016, the company became not only a user but also a vendor.<br><br>  
+    -->
+
+    “我们构建了 Kubernetes 技术解决方案”，侯培新说，
+    指的是华为的<a href="http://developer.huawei.com/ict/en/site-paas"> FusionStage™ </a> PaaS 输出。
+    <!--
+    "We built the Kubernetes technologies into our solutions," says Hou, referring to Huawei’s 
+    <a href="http://developer.huawei.com/ict/en/site-paas">FusionStage™</a> PaaS offering. 
+    -->
+
+    “我们的客户，从非常大的电信运营商到银行，都喜欢云原生的想法。他们喜欢 Kubernetes 的技术。
+    但是他们需要花费大量的时间来分解他们的应用程序，将它们转换为微服务体系结构。
+    作为解决方案提供者，我们帮助他们。
+    <!--
+    "Our customers, from very big telecommunications operators to banks, love the idea of cloud native. 
+    They like Kubernetes technology. But they need to spend a lot of time to decompose their applications 
+    to turn them into microservice architecture, and as a solution provider, we help them. 
+    -->
+
+    我们已经开始与一些中国银行合作，我们看到中国移动（China Mobile）和德国电信（Deutsche Telekom）等客户对我们很感兴趣”。<br><br>
+    <!--
+    We’ve started to work with some Chinese banks, and we see a lot of interest from our customers 
+    like <a href="http://www.chinamobileltd.com/">China Mobile</a> and 
+    <a href="https://www.telekom.com/en">Deutsche Telekom</a>."<br><br>
+    -->
+
+    “如果你是一个用户，你就仅仅是个用户”，侯培新补充道，“但如果你是一个供应商，为了说服你的客户，你应该自己使用它。
+    <!--
+    "If you’re just a user, you’re just a user," adds Hou. 
+    "But if you’re a vendor, in order to even convince your customers, you should use it yourself. 
+    -->
+
+    幸运的是，因为华为有很多员工，我们可以利用这种技术来展示我们所能构建的云的规模，向客户提供智慧服务”。
+    <!--
+    Luckily because Huawei has a lot of employees, we can demonstrate the scale of cloud we can build using this technology. 
+    We provide customer wisdom."
+    -->
+
+    尽管华为拥有自己的私有云，但其许多客户使用华为的解决方案运行跨云应用程序。
+    这是一个很大的卖点，大多数公共云提供商现在都支持 Kubernetes。
+    侯培新说，“这使得跨云转换比其他解决方案更容易”。<br><br>
+    <!--
+    While Huawei has its own private cloud, many of its customers run cross-cloud applications using Huawei’s solutions. 
+    It’s a big selling point that most of the public cloud providers now support Kubernetes. 
+    "This makes the cross-cloud transition much easier than with other solutions," says Hou.<br><br>
+    -->
+</div>
+</section>
+
+<div class="banner4">
+  <div class="banner4text">
+    “我们的客户，从非常大的电信运营商到银行，都喜欢云原生的想法。他们喜欢 Kubernetes 的技术。
+    但是他们需要花很多时间来分解他们的应用程序，把它们变成微服务体系结构，作为一个解决方案提供商，我们帮助他们。”
+    <!--
+    "Our customers, from very big telecommunications operators to banks, love the idea of cloud native. 
+    They like Kubernetes technology. But they need to spend a lot of time to decompose their applications 
+    to turn them into microservice architecture, and as a solution provider, we help them."
+    -->
+  </div>
+</div>
+
+<section class="section4">
+<div class="fullcol">
+
+    在华为内部，一旦他的团队完成内部业务流程部门向 Kubernetes 的转型，侯培新希望说服更多部门转向云原生开发和实践。
+    <!--
+    Within Huawei itself, once his team completes the transition of the internal business procedure department to Kubernetes, 
+    Hou is looking to convince more departments to move over to the cloud native development cycle and practice. 
+    -->
+
+    “我们有很多软件开发人员，所以我们将为他们提供我们的平台作为服务解决方案，我们自己的产品”，
+    他说，“我们希望在他们的迭代周期中看到显著的成本削减”。<br><br>
+    <!--
+    "We have a lot of software developers, 
+    so we will provide them with our platform as a service solution, our own product," he says. 
+    "We would like to see significant cuts in their iteration cycle."<br><br>
+    -->
+
+    在见证了华为最开始的向 Kubernetes 的转型之后，侯培新为其他考虑该技术的公司提供了建议，
+    “当你开始设计应用程序的架构时，首先考虑云原生，然后再考虑微服务架构”，他说，“我想你会从中受益”。<br><br>
+    <!--
+    Having overseen the initial move to Kubernetes at Huawei, Hou has advice for other companies considering the technology: 
+    "When you start to design the architecture of your application, think about cloud native, 
+    think about microservice architecture from the beginning," he says. 
+    "I think you will benefit from that."<br><br>
+    -->
+
+    但是如果您已经有了遗留应用程序，“首先从这些应用程序中一些对微服务友好的部分开始，
+    这些部分相对容易分解成更简单的部分，并且相对轻量级”，侯培新说，
+    <!--
+    But if you already have legacy applications, "start from some microservice-friendly part of those applications first, 
+    parts that are relatively easy to be decomposed into simpler pieces and are relatively lightweight," Hou says. 
+    -->
+
+    “不要从一开始就认为我想在几天内将整个架构或所有东西都迁移到微服务中。
+    不要把它当作目标。你应该循序渐进地做这件事。
+    我想说的是，对于遗留应用程序，并不是每个部分都适合微服务架构”。<br><br>
+    <!--
+    "Don’t think from day one that within how many days I want to move the whole architecture, 
+    or move everything into microservices. Don’t put that as a kind of target. 
+    You should do it in a gradual manner. And I would say for legacy applications, 
+    not every piece would be suitable for microservice architecture. No need to force it."<br><br>  
+    -->
+
+  毕竟，尽管侯培新对华为的 Kubernetes 充满热情，但他估计，
+  “未来 10 年，或许 80% 的工作负载可以分布式地在云原生环境中运行，但仍然有 20% 不是，但是没关系。
+  如果我们能够让 80% 的工作负载真正是云原生的、敏捷的，那么最终会有一个更好的世界”。
+  <!--
+  After all, as enthusiastic as Hou is about Kubernetes at Huawei, he estimates that "in the next 10 years, 
+  maybe 80 percent of the workload can be distributed, can be run on the cloud native environments. 
+  There’s still 20 percent that’s not, but it’s fine. 
+  If we can make 80 percent of our workload really be cloud native, to have agility, 
+  it’s a much better world at the end of the day."
+  -->
+</div>
+</section>
+
+<div class="banner5">
+  <div class="banner5text">
+    “未来 10 年，可能 80% 的工作负载可以分布式地在云原生环境中运行，但仍然有 20% 不是，不过没关系。
+    如果我们能够让 80% 的工作负载真正是云原生的、敏捷的，那么最终会有一个更好的世界。”
+    <!--
+    "In the next 10 years, maybe 80 percent of the workload can be distributed, 
+    can be run on the cloud native environments. 
+    There’s still 20 percent that’s not, but it’s fine. 
+    If we can make 80 percent of our workload really be cloud native, to have agility, 
+    it’s a much better world at the end of the day."
+    -->
+  </div>
+</div>
+<section class="section5">
+<div class="fullcol">
+  在不久的将来，侯培新期待着围绕着 Kubernetes 开发的新功能，尤其是华为正在开发的那些功能。
+  <!--
+  In the nearer future, Hou is looking forward to new features that are being developed around Kubernetes, 
+  not least of all the ones that Huawei is contributing to. 
+  -->
+
+  华为的工程师已经在为联邦功能(将多个 Kubernetes 集群放在一个框架中进行无缝管理)、调度、容器网络和存储，以及刚刚发布的一项名为
+  <a href="http://containerops.org/"的> Container Ops </a>的技术工作，这是一个 DevOps 管道引擎。
+  <!--
+  Huawei engineers have worked on the federation feature 
+  (which puts multiple Kubernetes clusters in a single framework to be managed seamlessly), scheduling, 
+  container networking and storage, and a just-announced technology called 
+  <a href="http://containerops.org/">Container Ops</a>, which is a DevOps pipeline engine.
+  -->
+
+  “这将把每个 DevOps 作业放到一个容器中”，他解释说，“这种容器机制使用 Kubernetes 运行，也用于测试 Kubernetes。
+  有了这种机制，我们可以比以前更容易地创建、共享和管理容器化 DevOps 作业”。<br><br>
+  <!--
+  "This will put every DevOps job into a container," he explains. 
+  "And then this container mechanism is running using Kubernetes, but is also used to test Kubernetes. 
+  With that mechanism, we can make the containerized DevOps jobs be created, 
+  shared and managed much more easily than before."<br><br>
+  -->
+
+  尽管如此，侯培新认为这项技术只是实现其全部潜力的一半。
+  首先，也是最重要的，他想要扩大它可以协调的规模，
+  这对于华为这样的超大规模公司以及它的一些客户来说非常重要。<br><br>
+  <!--
+  Still, Hou sees this technology as only halfway to its full potential. 
+  First and foremost, he’d like to expand the scale it can orchestrate, 
+  which is important for supersized companies like Huawei –  as well as some of its customers.<br><br>
+  -->
+
+  侯培新自豪地指出，在华为第一位工程师成为 Kubernetes 的贡献者和传道者两年后，华为现在是这个社区的最大贡献者。
+  他说，“我们发现，你对社区的贡献越大，你得到的回报也就越多”。
+  <!--
+  Hou proudly notes that two years after that first Huawei engineer became a contributor to and evangelist for Kubernetes, 
+  Huawei is now a top contributor to the community. "We’ve learned that the more you contribute to the community," 
+  he says, "the more you get back."
+  -->
+</div>
+</section>
@@ -0,0 +1,4 @@
+---
+title: LivePerson
+content_url: https://www.openstack.org/videos/video/running-kubernetes-on-openstack-at-liveperson
+---
@@ -0,0 +1,4 @@
+---
+title: Monzo
+content_url: https://youtu.be/YkOY7DgXKyw
+---
@@ -0,0 +1,4 @@
+---
+title: Philips
+content_url: https://cloud.google.com/customers/philips/
+---
@@ -0,0 +1,4 @@
+---
+title: Pokemon GO
+content_url: https://cloudplatform.googleblog.com/2016/09/bringing-Pokemon-GO-to-life-on-Google-Cloud.html
+---
@@ -0,0 +1,4 @@
+---
+title: Samsung SDS
+content_url: http://www.nextplatform.com/2016/05/24/samsung-experts-put-kubernetes-paces/
+---
@@ -0,0 +1,4 @@
+---
+title: SoundCloud
+content_url: https://www.youtube.com/watch?v=5378N5iLb2Q
+---
@@ -0,0 +1,224 @@
+---
+title: Squarespace 案例分析
+case_study_styles: true
+cid: caseStudies
+css: /css/style_case_studies.css
+---
+
+<!--
+---
+title: Squarespace Case Study
+case_study_styles: true
+cid: caseStudies
+css: /css/style_case_studies.css
+---
+-->
+
+<!-- <div class="banner1 desktop" style="background-image: url('/images/CaseStudy_squarespace_banner1.jpg')">
+  <h1> CASE STUDY:<img src="/images/squarespace_logo.png" class="header_logo"><br>
+    <div class="subhead">Squarespace: Gaining Productivity and Resilience with Kubernetes</div>
+  </h1>
+</div> -->
+
+<div class="banner1 desktop" style="background-image: url('/images/CaseStudy_squarespace_banner1.jpg')">
+  <h1> 案例分析：<img src="/images/squarespace_logo.png" class="header_logo"><br>
+    <div class="subhead">Squarespace: 借力 Kubernetes 提升效率和可靠性</div>
+  </h1>
+</div>
+
+<!-- <div class="details">
+    Company &nbsp;<b>Squarespace</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Location &nbsp;<b>New York, N.Y.</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Industry &nbsp;<b>Software as a Service, Website-Building Platform</b>
+</div> -->
+
+<div class="details">
+    公司名 &nbsp;<b>Squarespace</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;地址 &nbsp;<b>纽约市，纽约州</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;行业 &nbsp;<b>软件服务，网站构建平台</b>
+</div>
+
+<hr>
+<section class="section1">
+<div class="cols">
+  <div class="col1">
+    <!-- <h2>Challenge</h2>
+    Moving from a monolith to microservices in 2014 "solved a problem on the development side, but it pushed that problem to the infrastructure team," says Kevin Lynch, Staff Engineer on the Site Reliability team at Squarespace. "The infrastructure deployment process on our 5,000 VM hosts was slowing everyone down." -->
+    <h2>挑战</h2>
+    自从 2014 年，我们从 monolith 架构移植到微服务架构，
+    “虽然解决了开发端的问题，但却带来了架构组的问题”，Squarespace 网站可靠性组的主任工程师 Kevin Lynch 说道。
+    “5000 个 VM 主机上的部署过程，让每个人都举步维艰。”
+
+    <br>
+    <!-- <h2>Solution</h2>
+    The team experimented with container orchestration platforms, and found that Kubernetes "answered all the questions that we had," says Lynch. The company began running Kubernetes in its data centers in&nbsp;2016. -->
+    <h2>解决方案</h2>
+      网站可靠性组开始尝试使用不同的容器编排平台，然后发现 Kubernetes “解决了我们所有的既有问题”，Lynch 说道。于是整个公司在 2016 年开始在自己的数据中心中运行 Kubernetes 集群。
+  </div>
+
+  <div class="col2">
+
+<!-- <h2>Impact</h2>
+Since Squarespace moved to Kubernetes, in conjunction with modernizing its networking stack, deployment time has been reduced by almost 85%.
+Before, their VM deployment would take half an hour; now, says Lynch, "someone can generate a templated application, deploy it within five minutes,
+and have actual instances containerized, running in our staging environment at that point." Because of that, "productivity time is the big cost saver,"
+he adds. "When we started the Kubernetes project, we had probably a dozen microservices. Today there are twice that in the pipeline being actively worked on."
+Resilience has also been improved with Kubernetes: "If a node goes down, it’s rescheduled immediately and there’s no performance&nbsp;impact." -->
+
+<h2>影响</h2>
+自从 Squarespace 开始全面使用 Kubernetes，伴随着网络技术栈的革新，部署时间大幅减少85%。
+以前，他们的 VM 部署需要耗费半个小时；现在，Lynch 提到，“一个人可以生成一个模板应用，在五分钟内部署，并将实例容器化，并在模拟环境下运行。”正因为如此，“开发效率节省了大量的成本。”
+他又补充道，“当我们开始用 Kubernetes 时，我们可能只有十几个微服务。而现在的任务栏里面已经有两倍多的微服务正在进行中。”
+Kubernetes 也同样提升了可靠性：“如果一个节点宕掉，马上会重新调度一个新的节点，没有任何性能上的影响。”
+
+</div>
+
+</div>
+</section>
+<div class="banner2">
+  <div class="banner2text">
+    <iframe width="560" height="315" src="https://www.youtube.com/embed/feQkzJkW-SA" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
+    <br><br>“一旦你验证了 Kubernetes 可以解决一个问题，每个人都会立即着手解决其它的问题，无需你的布道。”
+<br style="height:25px"><span style="font-size:14px;letter-spacing:2px;text-transform:uppercase;margin-top:5% !important;"><br>— Kevin Lynch，Squarespace 网站可靠性组的主任工程师</span>
+  </div>
+</div>
+<section class="section2">
+<div class="fullcol">
+  <!-- <h2>Since it was started in a dorm room in 2003, Squarespace has made it simple for millions of people to create their own websites.</h2> -->
+  <h2>从 2003 年宿舍起步， Squarespace 已经为数百万人提供了网站构建服务。</h2>
+
+  <!-- Behind the scenes, though, the company’s monolithic Java application was making things not so simple for its developers to keep improving the platform.
+  So in 2014, the company decided to "go down the microservices path," says Kevin Lynch, staff engineer on Squarespace’s Site Reliability team.
+  "But we were always deploying our applications in vCenter VMware VMs [in our own data centers]. Microservices solved a problem on the development side,
+  but it pushed that problem to the Infrastructure team. The infrastructure deployment process on our 5,000 VM hosts was slowing everyone down."<br><br> -->
+
+  但在幕后，公司的单体应用却让开发人员在平台创新上举步维艰。所以在 2014 年，公司决定”走微服务之路”，Kevin Lynch 提到，Squarespace 网站稳定性组的主任工程师。
+  “但是我们还是一直在自己的 vCenter VMware 虚拟机[我们自己的数据中心]上部署应用。微服务解决了开发端的问题，但是让问题转变到了基础架构组这一边。我们在5000个虚拟机主机上的部署流程让每个人的开发效率都提高不起来。”
+
+  <!-- After experimenting with another container orchestration platform and "breaking it in very painful ways," Lynch says,
+  the team began experimenting with Kubernetes in mid-2016 and found that it "answered all the questions that we had."
+  Deploying it in the data center rather than the public cloud was their biggest challenge, and at the time, not a lot of other companies were doing that.
+  "We had to figure out how to deploy this in our infrastructure for ourselves, and we had to integrate it with our other applications," says Lynch.<br><br> -->
+
+  在尝试过另外一个容器编排平台，“非常痛苦地拆解它”，Lynch 说道，我们组开始在 2016 年年中尝试 Kubernetes，发现它“能解决我们所有的问题”。
+  将 Kubernetes 部署在数据中心，而非公有云上是我们最大的挑战，但在当时，并没有很多其它的公司会这么做。
+  “我们必须要自己摸索出如何在自己的基础架构中部署它，我们也必须要将其和我们其它的应用做集成，”Lynch补充道。<br><br>
+
+  <!-- At the same time, Squarespace’s Network Engineering team was modernizing its networking stack, switching from a traditional layer-two network to a layer-three spine-and-leaf network.
+  "It mapped beautifully with what we wanted to do with Kubernetes," says Lynch. "It gives us the ability to have our servers communicate directly with the top-of-rack switches. We use Calico for
+  <a href="https://github.com/containernetworking/cnihttps://github.com/containernetworking/cni">CNI networking for Kubernetes</a>,
+  so we can announce all these individual Kubernetes pod IP addresses and have them integrate seamlessly with our other services that are still provisioned in the VMs." -->
+
+  与此同时，Squarespace 的网络工程组也正在革新它们的网络技术栈，从传统的 L2 网络转变为 L3 脊叶网络架构。
+  “” Lynch 说道，“它给了我们服务器直接通过架顶交换机通信的能力。我们使用 Calico 作为
+  <a href="https://github.com/containernetworking/cnihttps://github.com/containernetworking/cni">Kubernetes 的 CNI 网络插件</a>”，
+  因而，我们可以为每个 Kubernetes pod 分配 IP 地址，并将它们和其它仍在虚拟机中创建的服务无缝衔接。
+
+</div>
+</section>
+
+<div class="banner3" style="background-image: url('/images/CaseStudy_squarespace_banner3.jpg')">
+  <!-- <div class="banner3text">
+    After experimenting with another container orchestration platform and "breaking it in very painful ways,"
+    Lynch says, the team began experimenting with Kubernetes in mid-2016 and found that it "answered all the questions that we had."
+  </div> -->
+  <div class="banner3text">
+    在尝试过另外一个容器编排平台，“非常痛苦地拆解它”，Lynch 说道，我们组开始在 2016 年年中尝试 Kubernetes，发现它“能解决我们所有的问题”。
+  </div>
+</div>
+
+<section class="section3">
+<div class="fullcol">
+  <!-- Within a couple months, they had a stable cluster for their internal use, and began rolling out Kubernetes for production.
+  They also added Zipkin and CNCF projects <a href="https://prometheus.io/">Prometheus</a> and <a href="https://www.fluentd.org/">fluentd</a> to their cloud native stack.
+  "We switched to Kubernetes, a new world, and we revamped all our other tooling as well," says Lynch. "It allowed us to streamline our process,
+  so we can now easily create an entire microservice project from templates, generate the code and deployment pipeline for that, generate the Docker file,
+  and then immediately just ship a workable, deployable project to Kubernetes." Deployments across Dev/QA/Stage/Prod were also "simplified drastically," Lynch adds.
+  "Now there is little configuration variation." -->
+
+  几个月的时间，它们就有了一个稳定的集群供内部使用，并开始在生产环境下使用 Kubernetes。
+  他们同时还在自己的云原生技术栈中用到了 Zipkin 和 CNCF 项目 <a href="https://prometheus.io/">Prometheus</a> and <a href="https://www.fluentd.org/">fluentd</a> 。
+  “我们换到 Kubernetes，就像进入了一个新世界，我们也同时改进了其它的工具，” Lynch 说道。“它让我们简化了流程，因而，我们才能更加方便地从模板中创建整个微服务项目，生成代码和部署管道，生成 Docker 文件，
+  并迅速地将可用的、可部署的项目发布到 Kubernetes 集群上。”在 Dev/QA/Stage/Prod 不同环境间的部署也变得 “异常的简单，” Lynch 补充道。
+  “现在，环境间的配置差异变得很小。”
+
+<br><br>
+  <!-- And the whole process takes only five minutes, an almost 85% reduction in time compared to their VM deployment.
+  "From end to end that probably took half an hour, and that’s not accounting for the fact that an infrastructure engineer would be responsible for doing that,
+  so there’s some business delay in there as well." -->
+
+  而且整个部署过程只需要五分钟，和虚拟机部署相比，几乎节约了 85% 的时间。
+  “从端到端可能要半个小时，这还没有考虑可能需要基础架构工程师来做这方面的工作，因而，也还有一些业务上的延时。”
+<br><br>
+  <!-- With faster deployments, "productivity time is the big cost saver," says Lynch. "We had a team that was implementing a new file storage service,
+  and they just started integrating that with our storage back end without our involvement"—which wouldn’t have been possible before Kubernetes.
+  He adds: "When we started the Kubernetes project, we had probably a dozen microservices. Today there are twice that in the pipeline being actively worked on." -->
+
+  部署变快之后，“开发效率节省了大量的成本，” Lynch 提到，“我们有个组想要实现新的文件存储服务，他们就径直和我们的存储后来做了集成，而不需要我们的参与”，这在采用 Kubernetes 之前是不可想象的。
+  他又补充道：“在我们开始 Kubernetes 项目时，我们可能只有十几个微服务。而现在的任务栏里面已经有两倍多的微服务正在进行中。”
+
+
+
+</div>
+</section>
+<div class="banner4" style="background-image: url('/images/CaseStudy_squarespace_banner4.jpg')">
+  <div class="banner4text">
+  <!-- "We switched to Kubernetes, a new world....It allowed us to streamline our process, so we can now easily create an entire microservice project from templates,"
+  Lynch says. And the whole process takes only five minutes, an almost 85% reduction in time compared to their VM deployment. -->
+
+  “我们换到 Kubernetes，就像进入了一个新世界....它让我们简化了流程，因而，我们才能更加方便地从模板中创建整个微服务项目，”
+  Lynch 说道。整个部署过程只需要五分钟，和虚拟机部署相比，几乎节约了 85% 的时间。
+  </div>
+</div>
+
+<section class="section5" style="padding:0px !important">
+<div class="fullcol">
+  <!-- There’s also been a positive impact on the application’s resilience. "When we’re deploying VMs, we have to build tooling to ensure that a service is
+  spread across racks appropriately and can withstand failure," he says. "Kubernetes just does it. If a node goes down,
+  it’s rescheduled immediately and there’s no performance impact." -->
+
+  同样在应用程序的可靠性方面也有积极的影响。“当我们在部署虚拟机时，我们需要工具来保障服务散布在机架间，可以承受失败，”他说道，“Kubernetes 正好可以做到这一点。如果节点宕掉，可以马上重新调度，没有性能影响。”
+<br><br>
+  <!-- Another big benefit is autoscaling. "It wasn’t really possible with the way we’ve been using VMware," says Lynch, "but now we can just
+  add the appropriate autoscaling features via Kubernetes directly, and boom, it’s scaling up as demand increases. And it worked out of the box." -->
+
+  另一个很大的好处就是扩缩容。“按照我们使用 VMware 的方式，扩缩容好像不可能实现，”Lynch 说道，“但现在，我们可以直接通过 Kubernetes 加入合适的扩缩容功能，然后，随着需求的增加而扩容。开箱即用！”
+<br><br>
+  <!-- For others starting out with Kubernetes, Lynch says his best advice is to "fail fast": "Once you’ve planned things out, just execute.
+  Kubernetes has been really great for trying something out quickly and seeing if it works or not." -->
+
+  针对刚开始使用 Kubernetes 的人，Lynch 说他最后的建议就是“快速失败”：“一旦计划后，马上执行。Kubernetes 真的是非常适合快速实验，看看是否可行。”
+
+</div>
+
+<div class="banner5">
+  <div class="banner5text">
+    <!-- "When we’re deploying VMs, we have to build tooling to ensure that a service is spread across racks appropriately and can withstand failure,"
+    he says. "Kubernetes just does it. If a node goes down, it’s rescheduled immediately and there’s no performance impact." -->
+
+    “当我们在部署虚拟机时，我们需要工具来保障服务散布在机架间，可以承受失败，”他说道，“Kubernetes 正好可以做到这一点。如果节点宕掉，可以马上重新调度，没有性能影响。”
+
+  </div>
+</div>
+
+<div class="fullcol">
+  <!-- Lynch and his team are planning to open source some of the tools they’ve developed to extend Kubernetes and use it as an API itself.
+  The first tool injects dependent applications as containers in a pod.
+  "When you ship an application, usually it comes along with a whole bunch of dependent applications that need to be shipped with that,
+  for example, fluentd for logging," he explains. With this tool, the developer doesn’t need to worry about the configurations. -->
+
+  Lynch 和他的小组正准备开源一些他们的工具，这些工具用来延展 Kubernetes，将其作为 API 使用。
+  第一个工具在 pod 将依赖应用作为容器注入。
+  “当你在发布应用时，常常需要一系列的依赖应用，例如，日志用的 fluentd，” 他解释道。
+  有了这个工具，开发人员就不需要担心配置了。
+
+<br><br>
+  <!-- Going forward, all new services at Squarespace are going into Kubernetes, and the end goal is to convert everything it can. About a quarter of
+  existing services have been migrated. "Our monolithic application is going to be the last one, just because it’s so big and complex," says Lynch.
+  "But now I’m seeing other services get moved over, like the file storage service. Someone just did it and it worked—painlessly. So I believe if we tackle it,
+  it’s probably going to be a lot easier than we fear. Maybe I should just take my own advice and fail fast!" -->
+
+  自此之后，Squarespace 所有新的微服务都将直接部署到 Kubernetes 上，而最终的目标是要扩大到所有的服务上。
+  现在已经有四分之一的服务已经移植完。“我的单体应用将是最后一个被移植的，仅仅是以为它太大、太复杂，”Lynch 说道。
+  “但现在我已经看到其它的服务已经被移植到 Kubernetes 上，例如文件存储服务。有人解决了，而且并不复杂。
+  所以我坚信如果我们着手解决它，很可能回避我们所担心的要轻松许多。也许我应该接受自己的建议，“快速失败”！”
+
+</div>
+
+</section>
@@ -0,0 +1,4 @@
+---
+title: WePay
+content_url: http://thenewstack.io/wepay-kubernetes-changed-business/
+---
@@ -0,0 +1,4 @@
+---
+title: Yahoo! Japan
+content_url: https://kubernetes.io/blog/2016/10/kubernetes-and-openstack-at-yahoo-japan
+---
@@ -1,4 +1,4 @@
---
-title: Zulily
-content_url: https://www.youtube.com/embed/of45hYbkIZs
---
+---
+title: Zulily
+content_url: https://www.youtube.com/embed/of45hYbkIZs
+---
@@ -0,0 +1,133 @@
+---
+title: 社区
+layout: basic
+cid: community
+---
+
+<!--
+---
+title: Community
+layout: basic
+cid: community
+---
+-->
+
+<section id="mainContent">
+    <main>
+        <!-- <div class="content">
+            <h3>Ensuring Kubernetes works well everywhere and for everyone.</h3>
+            <p>Connect with the Kubernetes community on our <a href="http://slack.k8s.io/">Slack channel</a>, <a href="https://discuss.kubernetes.io/">discussion board</a>, or join the
+                <a href="https://groups.google.com/forum/#!forum/kubernetes-dev">Kubernetes-dev Google group</a>. A weekly
+                community meeting takes place via video conference to discuss the state of affairs, see
+		<a href="https://github.com/kubernetes/community/blob/master/events/community-meeting.md">these instructions</a> for information
+	        on how to participate.</p>
+            <p>You can also join Kubernetes all around the world through our
+                <a href="https://www.meetup.com/topics/kubernetes/">Kubernetes Meetup Community</a> and the
+                <a href="https://www.meetup.com/Kubernetes-Cloud-Native-Online-Meetup/">Kubernetes Cloud Native Meetup Community</a>.</p>
+          </div> -->
+
+          <div class="content">
+              <h3>保证 Kubernetes 到处都适用，每个人都喜欢。</h3>
+              <p>在我们的<a href="http://slack.k8s.io/">Slack channel</a>,
+                <a href="https://discuss.kubernetes.io/">讨论版</a>, 或者
+                <a href="https://groups.google.com/forum/#!forum/kubernetes-dev">Kubernetes-dev Google 群主</a>上和 Kubernetes 互动。
+              同时，每周我们也有社区视频会议，讨论最新进展。参见
+  		<a href="https://github.com/kubernetes/community/blob/master/events/community-meeting.md">这些指导</a>了解如何参与其中。</p>
+              <p>你也可以在世界各地通过我们的
+                  <a href="https://www.meetup.com/topics/kubernetes/">Kubernetes Meetup 社区</a> 以及
+                  <a href="https://www.meetup.com/Kubernetes-Cloud-Native-Online-Meetup/">Kubernetes Cloud Native Meetup 社区</a>来参与。</p>
+            </div>
+
+        <!-- <div class="content">
+            <h3>Special Interest Groups (SIGs)</h3>
+            <p>Have a special interest in how Kubernetes works with another technology?  See our ever growing
+                <a href="https://git.k8s.io/community/sig-list.md">lists of SIGs</a>,
+                from AWS and Openstack to Big Data and Scalability, there's a place for you to contribute and instructions
+                for forming a new SIG if your special interest isn't covered (yet).</p>
+
+            <p>As a member of the Kubernetes community, you are welcome to join any of the SIG meetings
+                you are interested in. No registration required.</p>
+        </div> -->
+
+        <div class="content">
+            <h3>特殊兴趣小组 （Special Interest Groups，SIGs）</h3>
+            <p>对于 Kubernetes 是如何和另外的技术协作感兴趣？了解下我们不停发展的
+                <a href="https://git.k8s.io/community/sig-list.md">SIGs 群组</a>,
+                从 AWS 和 Openstack 到 大数据和可扩展性，总会有一个适合你，如果你所关注的不在其列，也有指导帮助你成立新的 SIG。</p>
+
+            <p>作为 Kubernetes 社区的一员，你可以随意加入任何你感兴趣的 SIG 会议。不需要额外注册。</p>
+        </div>
+
+        <!-- <div class="content">
+          <h3>Code of Conduct</h3>
+          <p>The Kubernetes community values respect and inclusiveness, and
+             enforces a <a href="code-of-conduct/">Code of Conduct</a> in all
+             interactions. If you notice a violation of the Code of Conduct at
+             an event or meeting, in Slack, or in another communication
+             mechanism, reach out to the <a href="https://github.com/kubernetes/community/tree/master/committee-code-of-conduct">Kubernetes Code of Conduct Committee</a>
+             <a href="mailto:conduct@kubernetes.io">conduct@kubernetes.io</a>.
+             Your anonymity will be protected.</p>
+           </p>
+         </div> -->
+
+         <div class="content">
+           <h3>行为规范</h3>
+           <p>Kubernetes 社区重视尊重和包容，并要求在所有场合都遵循
+             <a href="code-of-conduct/">行为规范</a>。
+             如果你在活动、会议、Slack 或是其它场合发现有任何违反行为规范的行为，请联系
+             <a href="https://github.com/kubernetes/community/tree/master/committee-code-of-conduct">Kubernetes 行为规范委员会</a>
+              <a href="mailto:conduct@kubernetes.io">conduct@kubernetes.io</a>.
+              我们会确保您的匿名性。</p>
+          </div>
+    </main>
+</section>
+
+<!-- <section id="talkToUs">
+    <main>
+        <h3>Talk to Us!</h3>
+        <h4>We would love to hear from you, how you are using Kubernetes,<br> and what we can do to make it better.</h4>
+        <div id="bigSocial">
+            <div>
+                <a href="https://twitter.com/kubernetesio">@kubernetesio</a>
+                <p>Get the latest news and updates.</p>
+            </div>
+            <div>
+                <a href="https://github.com/kubernetes/kubernetes">Github Project</a>
+                <p>Check out the project and consider contributing.</p>
+            </div>
+            <div>
+                <a href="http://slack.k8s.io/">#kubernetes-users</a>
+                <p>Our Slack channel is the best way to contact our engineers and share your ideas with them.</p>
+            </div>
+            <div>
+                <a href="http://stackoverflow.com/questions/tagged/kubernetes">Stack Overflow</a>
+                <p>Our user forum is a great place to go for community support.</p>
+            </div>
+        </div>
+    </main>
+</section> -->
+
+<section id="talkToUs">
+    <main>
+        <h3>与我们联系！</h3>
+        <h4>我们很希望听到你的声音，你是如何使用 Kubernetes 的，<br>以及我们可以将 Kubernetes 变得更美好。</h4>
+        <div id="bigSocial">
+            <div>
+                <a href="https://twitter.com/kubernetesio">@kubernetesio</a>
+                <p>获取更多的资讯和更新。</p>
+            </div>
+            <div>
+                <a href="https://github.com/kubernetes/kubernetes">Github 项目</a>
+                <p>了解项目，作出贡献。</p>
+            </div>
+            <div>
+                <a href="http://slack.k8s.io/">#kubernetes-users</a>
+                <p>Slack channel 是联系工程师，分享想法的最佳方法。</p>
+            </div>
+            <div>
+                <a href="http://stackoverflow.com/questions/tagged/kubernetes">Stack Overflow</a>
+                <p>我们的论坛是获得社区支持的最佳地点。</p>
+            </div>
+        </div>
+    </main>
+</section>
@@ -0,0 +1,44 @@
+---
+title: 社区
+layout: basic
+cid: community
+css: /css/community.css
+---
+
+<!-- ---
+title: Community
+layout: basic
+cid: community
+css: /css/community.css
+--- -->
+
+<div class="community_main">
+<!-- <h1>Kubernetes Community Code of Conduct</h1> -->
+<h1>Kubernetes 社区行为规范</h1>
+
+<!-- Kubernetes follows the
+<a href="https://github.com/cncf/foundation/blob/master/code-of-conduct.md">CNCF Code of Conduct</a>.
+The text of the CNCF CoC is replicated below, as of
+<a href="https://github.com/cncf/foundation/blob/0ce4694e5103c0c24ca90c189da81e5408a46632/code-of-conduct.md">commit 0ce4694</a>.
+If you notice that this is out of date, please
+<a href="https://github.com/kubernetes/website/issues/new">file an issue</a>. -->
+
+Kubernetes 遵循
+<a href="https://github.com/cncf/foundation/blob/master/code-of-conduct.md">CNCF 行为规范</a>。
+CNCF 社区规范文本如下链接
+<a href="https://github.com/cncf/foundation/blob/0ce4694e5103c0c24ca90c189da81e5408a46632/code-of-conduct.md">commit 0ce4694</a>。
+如果您发现这个 CNCF 社区规范文本已经过时，请
+<a href="https://github.com/kubernetes/website/issues/new">提交 issue</a>。
+
+<!-- If you notice a violation of the Code of Conduct at an event or meeting, in
+Slack, or in another communication mechanism, reach out to
+the [Kubernetes Code of Conduct Committee](https://github.com/kubernetes/community/tree/master/committee-code-of-conduct) <conduct@kubernetes.io>.
+Your anonymity will be protected. -->
+
+如果你在活动、会议、Slack 或是其它场合发现有任何违反行为规范的行为，请联系[Kubernetes 行为规范委员会](https://github.com/kubernetes/community/tree/master/committee-code-of-conduct)<conduct@kubernetes.io>。
+我们会确保您的匿名性。
+
+<div class="cncf_coc_container">
+{{< include "/static/cncf-code-of-conduct.md" >}}
+</div>
+</div>
@@ -0,0 +1,5 @@
+<!-- The files in this directory have been imported from other sources. Do not
+edit them directly, except by replacing them with new versions. -->
+
+本路径下的文件从其它地方导入。
+除了版本更新，不要直接修改。
@@ -0,0 +1,46 @@
+<!-- Do not edit this file directly. Get the latest from
+     https://github.com/cncf/foundation/blob/master/code-of-conduct.md -->
+## CNCF Community Code of Conduct v1.0
+
+### Contributor Code of Conduct
+
+As contributors and maintainers of this project, and in the interest of fostering
+an open and welcoming community, we pledge to respect all people who contribute
+through reporting issues, posting feature requests, updating documentation,
+submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free experience for
+everyone, regardless of level of experience, gender, gender identity and expression,
+sexual orientation, disability, personal appearance, body size, race, ethnicity, age,
+religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery
+* Personal attacks
+* Trolling or insulting/derogatory comments
+* Public or private harassment
+* Publishing other's private information, such as physical or electronic addresses,
+ without explicit permission
+* Other unethical or unprofessional conduct.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are not
+aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers
+commit themselves to fairly and consistently applying these principles to every aspect
+of managing this project. Project maintainers who do not follow or enforce the Code of
+Conduct may be permanently removed from the project team.
+
+This code of conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting
+the [Kubernetes Code of Conduct Committee](https://github.com/kubernetes/community/tree/master/committee-code-of-conduct) <conduct@kubernetes.io>.
+
+This Code of Conduct is adapted from the Contributor Covenant
+(http://contributor-covenant.org), version 1.2.0, available at
+http://contributor-covenant.org/version/1/2/0/
+
+### CNCF Events Code of Conduct
+
+CNCF events are governed by the Linux Foundation [Code of Conduct](http://events.linuxfoundation.org/events/cloudnativecon/attend/code-of-conduct) available on the event page. This is designed to be compatible with the above policy and also includes more details on responding to incidents.
@@ -1,3 +1,8 @@
 ---
 title: 文档
 ---
+
+<!-- ---
+title: Home
+weight: 5
+--- -->
@@ -3,40 +3,40 @@ approvers:
 - bgrant0607
 - erictune
 - lavalamp
-title: Kubernetes API访问控制
+title: Kubernetes API 访问控制
 ---

-用户通过 `kubectl`、客户端库或者通过发送REST请求[访问API](/docs/user-guide/accessing-the-cluster)。 用户（自然人）和[Kubernetes服务账户](/docs/tasks/configure-pod-container/configure-service-account/) 都可以被授权进行API访问。
-请求到达API服务器后会经过几个阶段，具体说明如图：
+用户通过 `kubectl`、客户端库或者通过发送 REST 请求[访问 API](/docs/user-guide/accessing-the-cluster)。 用户（自然人）和 [Kubernetes 服务账户](/docs/tasks/configure-pod-container/configure-service-account/) 都可以被授权进行 API 访问。
+请求到达 API 服务器后会经过几个阶段，具体说明如图：

 ![Diagram of request handling steps for Kubernetes API request](/images/docs/admin/access-control-overview.svg)

 ## 传输层安全

-在典型的Kubernetes集群中，API通过443端口提供服务。
-API服务器会提供一份证书。 该证书一般是自签名的， 所以用户机器上的 `$USER/.kube/config` 目录通常
-包含该API服务器证书的根证书，用来代替系统默认根证书。 当用户使用 `kube-up.sh` 创建集群时，该证书通常会被自动写入用户的`$USER/.kube/config`。  如果集群中存在多个用户，则创建者需要与其他用户共享证书。
+在典型的 Kubernetes 集群中，API 通过 443 端口提供服务。
+API 服务器会提供一份证书。 该证书一般是自签名的， 所以用户机器上的 `$USER/.kube/config` 目录通常
+包含该 API 服务器证书的根证书，用来代替系统默认根证书。 当用户使用 `kube-up.sh` 创建集群时，该证书通常会被自动写入用户的 `$USER/.kube/config`。  如果集群中存在多个用户，则创建者需要与其他用户共享证书。

 ## 认证

-一旦 TLS 连接建立，HTTP请求就进入到了认证的步骤。即图中的步骤 **1** 。
-集群创建脚本或集群管理员会为API服务器配置一个或多个认证模块。
-更具体的认证相关的描述详见 [这里](/docs/admin/authentication/)。
+一旦 TLS 连接建立，HTTP 请求就进入到了认证的步骤。即图中的步骤 **1** 。
+集群创建脚本或集群管理员会为 API 服务器配置一个或多个认证模块。
+更具体的认证相关的描述详见[这里](/docs/admin/authentication/)。

-认证步骤的输入是整个HTTP请求，但这里通常只是检查请求头和/或客户端证书。
+认证步骤的输入是整个 HTTP 请求，但这里通常只是检查请求头和 / 或客户端证书。

-认证模块支持客户端证书，密码和Plain Tokens，
-Bootstrap Tokens，以及JWT Tokens (用于服务账户)。
+认证模块支持客户端证书，密码和 Plain Tokens，
+Bootstrap Tokens，以及 JWT Tokens（用于服务账户）。

 （管理员）可以同时设置多种认证模块，在设置了多个认证模块的情况下，每个模块会依次尝试认证，
 直到其中一个认证成功。

-在 GCE 平台中，客户端证书，密码和Plain Tokens，Bootstrap Tokens，以及JWT Tokens同时被启用。
+在 GCE 平台中，客户端证书，密码和 Plain Tokens，Bootstrap Tokens，以及 JWT Tokens 同时被启用。

-如果请求认证失败，则请求被拒绝，返回401状态码。
+如果请求认证失败，则请求被拒绝，返回 401 状态码。
 如果认证成功，则被认证为具体的 `username`，该用户名可供随后的步骤中使用。一些认证模块还提供了用户的组成员关系，另一些则没有。

-尽管Kubernetes使用 "用户名" 来进行访问控制和请求记录，但它实际上并没有 `user` 对象，也不存储用户名称或其他相关信息。
+尽管 Kubernetes 使用“用户名”来进行访问控制和请求记录，但它实际上并没有 `user` 对象，也不存储用户名称或其他相关信息。

 ## 授权

@@ -44,7 +44,7 @@ Bootstrap Tokens，以及JWT Tokens (用于服务账户)。

 请求须包含请求者的用户名，请求动作，以及该动作影响的对象。 如果存在相应策略，声明该用户具有进行相应操作的权限，则该请求会被授权。

-例如，如果Bob有如下策略，那么他只能够读取`projectCaribou`命名空间下的pod资源：
+例如，如果 Bob 有如下策略，那么他只能够读取 `projectCaribou` 命名空间下的 pod 资源：

 ```json
 {
@@ -58,7 +58,7 @@ Bootstrap Tokens，以及JWT Tokens (用于服务账户)。
    }
 }
 ```
-如果Bob发起以下请求，那么请求能够通过授权，因为Bob被允许访问 `projectCaribou` 命名空间下的对象：
+如果 Bob 发起以下请求，那么请求能够通过授权，因为 Bob 被允许访问 `projectCaribou` 命名空间下的对象：

 ```json
 {
@@ -74,20 +74,20 @@ Bootstrap Tokens，以及JWT Tokens (用于服务账户)。
  }
 }
 ```
-如果Bob对 `projectCaribou` 命名空间下的对象发起一个写（`create` 或者 `update`）请求，那么它的授权会被拒绝。 如果Bob请求读取(`get`) 其他命名空间，例如 `projectFish`下的对象，其授权也会被拒绝。 
+如果 Bob 对 `projectCaribou` 命名空间下的对象发起一个写（`create` 或者 `update`）请求，那么它的授权会被拒绝。 如果 Bob 请求读取 （`get`）其他命名空间，例如 `projectFish` 下的对象，其授权也会被拒绝。 

-Kubernetes的授权要求使用通用的REST属性与现有的组织或云服务提供商的访问控制系统进行交互。 采用REST格式是必要的，因为除Kubernetes外，这些访问控制系统还可能与其他的API进行交互。
+Kubernetes 的授权要求使用通用的 REST 属性与现有的组织或云服务提供商的访问控制系统进行交互。 采用 REST 格式是必要的，因为除 Kubernetes 外，这些访问控制系统还可能与其他的 API 进行交互。

-Kubernetes 支持多种授权模块，例如ABAC模式，RBAC模式和 Webhook模式。 管理员创建集群时，会配置API服务器应用的授权模块。 如果多种授权模式同时被启用，Kubernetes将检查所有模块，如果其中一种通过授权，则请求授权通过。 如果所有的模块全部拒绝，则请求被拒绝(HTTP状态码403)。
+Kubernetes 支持多种授权模块，例如 ABAC 模式，RBAC 模式和 Webhook 模式。 管理员创建集群时，会配置 API 服务器应用的授权模块。 如果多种授权模式同时被启用，Kubernetes 将检查所有模块，如果其中一种通过授权，则请求授权通过。 如果所有的模块全部拒绝，则请求被拒绝（HTTP 状态码 403）。

-要了解更多的Kubernetes授权相关信息，包括使用授权模块创建策略的具体说明等，可参考[授权概述](/docs/admin/authorization)。
+要了解更多的 Kubernetes 授权相关信息，包括使用授权模块创建策略的具体说明等，可参考[授权概述](/docs/admin/authorization)。


 ## 准入控制

 准入控制模块是能够修改或拒绝请求的软件模块。
 作为授权模块的补充，准入控制模块会访问被创建或更新的对象的内容。
-它们作用于对象的创建，删除，更新和连接 (proxy)阶段，但不包括对象的读取。
+它们作用于对象的创建，删除，更新和连接（proxy）阶段，但不包括对象的读取。

 可以同时配置多个准入控制器，它们会按顺序依次被调用。

@@ -99,23 +99,23 @@ Kubernetes 支持多种授权模块，例如ABAC模式，RBAC模式和 Webhook

 可用的准入控制模块描述 [如下](/docs/admin/admission-controllers/)。

-一旦请求通过所有准入控制器，将使用对应API对象的验证流程对其进行验证，然后写入对象存储 (如步骤 **4**)。
+一旦请求通过所有准入控制器，将使用对应 API 对象的验证流程对其进行验证，然后写入对象存储 （如步骤 **4**）。


-## API的端口和IP
+## API 的端口和 IP

-上述讨论适用于发送请求到API服务器的安全端口(典型情况)。  
-实际上API服务器可以通过两个端口提供服务：
+上述讨论适用于发送请求到 API 服务器的安全端口（典型情况）。  
+实际上 API 服务器可以通过两个端口提供服务：

-默认情况下，API服务器在2个端口上提供HTTP服务：
+默认情况下，API 服务器在 2 个端口上提供 HTTP 服务：

  1. `Localhost Port`:

          - 用于测试和启动，以及管理节点的其他组件
-            (scheduler, controller-manager)与API的交互
-          - 没有TLS
-          - 默认值为8080，可以通过 `--insecure-port` 标记来修改。
-          - 默认的IP地址为localhost， 可以通过 `--insecure-bind-address`标记来修改。
+            （scheduler, controller-manager）与 API 的交互
+          - 没有 TLS
+          - 默认值为 8080，可以通过 `--insecure-port` 标记来修改。
+          - 默认的 IP 地址为 localhost， 可以通过 `--insecure-bind-address` 标记来修改。
          - 请求会 **绕过** 认证和鉴权模块。
          - 请求会被准入控制模块处理。
          - 其访问需要主机访问的权限。
@@ -124,12 +124,12 @@ Kubernetes 支持多种授权模块，例如ABAC模式，RBAC模式和 Webhook

          - 尽可能使用该端口访问
          - 应用 TLS。 可以通过 `--tls-cert-file` 设置证书， 通过 `--tls-private-key-file` 设置私钥。
-          - 默认值为6443，可以通过 `--secure-port` 标记来修改。
-          - 默认IP是首个非本地的网络接口地址，可以通过 `--bind-address` 标记来修改。
+          - 默认值为 6443，可以通过 `--secure-port` 标记来修改。
+          - 默认 IP 是首个非本地的网络接口地址，可以通过 `--bind-address` 标记来修改。
          - 请求会经过认证和鉴权模块处理。
          - 请求会被准入控制模块处理。
          - 要求认证和授权模块正常运行。

-通过 `kube-up.sh`创建集群时， 对 Google Compute Engine (GCE)
-和一些其他的云供应商来说， API通过443端口提供服务。 对
-GCE而言，项目上配置了防火墙规则，允许外部的HTTPS请求访问API，其他（厂商的）集群设置方法各不相同。
+通过 `kube-up.sh` 创建集群时， 对 Google Compute Engine（GCE）
+和一些其他的云供应商来说， API 通过 443 端口提供服务。 对
+GCE 而言，项目上配置了防火墙规则，允许外部的 HTTPS 请求访问 API，其他（厂商的）集群设置方法各不相同。
@@ -16,63 +16,62 @@ content_template: templates/concept

 {{% capture body %}}

-在 Kubernetes 里，您必须经过身份验证(登录)，才能授权您的请求(授予访问权限).。有关认证的信息，请参阅[访问控制概述](/docs/admin/access-the-api/)。
+在 Kubernetes 里，您必须经过身份验证 ( 登录 )，才能授权您的请求 ( 授予访问权限 ).。有关认证的信息，请参阅[访问控制概述](/docs/admin/access-the-api/)。

 Kubernetes 提供通用的 REST API 请求。这意味着 Kubernetes 授权可以与现有的组织或云提供商的访问控制系统一起使用，该系统可以处理除 Kubernetes API 之外的其他 API。

 ## 确定请求是允许还是被拒绝
-Kubernetes 使用 API 服务器授权 API 请求。它根据所有策略评估所有请求属性，并允许或拒绝请求。某些策略必须允许 API 请求的所有部分继续进行，这意味着默认情况下是拒绝权限。
+Kubernetes 使用 API  服务器授权 API 请求。它根据所有策略评估所有请求属性，并允许或拒绝请求。某些策略必须允许 API 请求的所有部分继续进行，这意味着默认情况下是拒绝权限。

-(虽然 Kubernetes 使用 API 服务器，访问控制和依赖特定类型对象的特定领域策略由 Admission 控制器处理。)
+( 虽然 Kubernetes 使用 API 服务器，访问控制和依赖特定类型对象的特定领域策略由 Admission 控制器处理。)

-当配置多个授权模块时，按顺序检查每个模块，如果有任何模块授权请求，则可以继续执行该请求。如果所有模块拒绝请求，则拒绝该请求(HTTP状态代码403)。
+当配置多个授权模块时，按顺序检查每个模块，如果有任何模块授权请求，则可以继续执行该请求。如果所有模块拒绝请求，则拒绝该请求 (HTTP 状态代码 403)。

 ## 查看您的请求属性

-Kubernetes 仅查看以下API请求属性:
+Kubernetes 仅查看以下 API 请求属性 :

 * **user**  - 验证期间提供的 `user` 字符串
 * **group**  - 认证用户所属的组名列表
-* **“extra"**  - 由认证层提供的任意字符串键到字符串值的映射
-* **API**  - 指示请求是否用于API资源
-* **Request path**  - 诸如`/api`或`/healthz`的其他非资源端点的路径(请参阅[kubectl](#kubectl)).
-* **API request verb**  -  API 动词 `get`，`list`，`create`，`update`，`patch`，`watch`，`proxy`，`redirect`，`delete`和`deletecollection`用于资源请求。要确定资源 API 端点的请求动词，请参阅**确定下面的请求动词**.
-* **HTTP request verb**  -  HTTP动词`get`，`post`，`put`和`delete`用于非资源请求
-* **Resource**  - 正在访问的资源的ID或名称(仅适用于资源请求)
- --* 对于使用`get`, `update`, `patch`, 和 `delete`动词的资源请求，您必须提供资源名称。
-* **Subresource**  - 正在访问的子资源(仅用于资源请求)
-* **Namespace**  - 正在被访问的对象的命名空间(仅针对命名空间的资源请求)
-* **API group**  - 正在访问的API组(仅用于资源请求). 一个空字符串指定[核心 API 组](/docs/api/).
+* **extra**  - 由认证层提供的任意字符串键到字符串值的映射
+* **API**  - 指示请求是否用于 API 资源
+* **Request path**  - 诸如 `/api` 或 `/healthz` 的其他非资源端点的路径 ( 请参阅[kubectl](#kubectl)).
+* **API request verb**  -  API 动词 `get`，`list`，`create`，`update`，`patch`，`watch`，`proxy`，`redirect`，`delete` 和 `deletecollection` 用于资源请求。要确定资源 API 端点的请求动词，请参阅**确定下面的请求动词**.
+* **HTTP request verb**  -  HTTP 动词 `get`，`post`，`put` 和 `delete` 用于非资源请求
+* **Resource**  - 正在访问的资源的 ID 或名称 ( 仅适用于资源请求 )，对于使用 `get`, `update`, `patch`, 和 `delete` 动词的资源请求，您必须提供资源名称。
+* **Subresource**  - 正在访问的子资源 ( 仅用于资源请求 )
+* **Namespace**  - 正在被访问的对象的命名空间 ( 仅针对命名空间的资源请求 )
+* **API group**  - 正在访问的 API 组 ( 仅用于资源请求 ). 一个空字符串指定[核心 API 组](/docs/api/).

 ## 确定请求动词

-要确定资源 API 端点的请求动词，请查看所使用的HTTP动词以及请求是否对单个资源或资源集合进行操作:
+要确定资源 API 端点的请求动词，请查看所使用的 HTTP 动词以及请求是否对单个资源或资源集合进行操作 :

-HTTP动词| 请求动词
+HTTP 动词 | 请求动词
 ---------- | ---------------
 POST | 创建
-GET，HEAD | 获取(个人资源)，列表(集合)
+GET，HEAD | 获取 ( 个人资源 )，列表 ( 集合 )
 PUT | 更新
 PATCH | 补丁
-DELETE| 删除(个人资源)，删除(收藏)
+DELETE| 删除 ( 个人资源 )，删除 ( 收藏 )

-Kubernetes 有时会使用专门的动词检查授权以获得额外的权限。例如:
+Kubernetes 有时会使用专门的动词检查授权以获得额外的权限。例如 :

-* [PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/)在`extensions` API组中的`podsecuritypolicies`资源上检查`use`动词的授权。
-* [RBAC](/docs/admin/authorization/rbac/#privilege-escalation-prevention-and-bootstrapping) 在`rbac.authorization.k8s.io` API组中的`roles`和`clusterroles`资源上检查`bind`动词的授权。
-* [认证](/docs/admin/authentication/) 在核心API组中的`users`，`groups`和`serviceaccounts`上的`impersonate`动词的授权以及`authentication.k8s.io` API组中的`userextras`进行层次检查。
+* [PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/) 在 `extensions` API 组中的 `podsecuritypolicies` 资源上检查 `use` 动词的授权。
+* [RBAC](/docs/admin/authorization/rbac/#privilege-escalation-prevention-and-bootstrapping) 在 `rbac.authorization.k8s.io` API 组中的 `roles` 和 `clusterroles` 资源上检查 `bind` 动词的授权。
+* [认证](/docs/admin/authentication/) 在核心 API 组中的 `users`，`groups` 和 `serviceaccounts` 上的 `impersonate` 动词的授权以及 `authentication.k8s.io` API 组中的 `userextras` 进行层次检查。

 ## 授权模块
-* **ABAC模式**  - 基于属性的访问控制(ABAC)定义了访问控制范例，通过使用将属性组合在一起的策略来授予用户访问权限。策略可以使用任何类型的属性(用户属性，资源属性，对象，环境属性等)。要了解有关使用ABAC模式的更多信息，请参阅[ABAC模式](/docs/admin/authorization/abac/)
-* **RBAC模式**  - 基于角色的访问控制(RBAC)是一种根据企业内个人用户的角色来调整对计算机或网络资源的访问的方法。在这种情况下，访问是单个用户执行特定任务(例如查看，创建或修改文件)的能力。要了解有关使用RBAC模式的更多信息，请参阅[RBAC模式](/docs/admin/authorization/rbac/)
-*当指定 "RBAC"(基于角色的访问控制)使用 "rbac.authorization.k8s.io" API组来驱动授权决定时，允许管理员通过Kubernetes API动态配置权限策略.
-.. *截至1.6 RBAC模式是测试版.
-.. *要启用RBAC，请使用 `--authorization-mode=RBAC` 启动 apiserver.
-* **Webhook模式**  -  WebHook 是HTTP回调:发生事件时发生的HTTP POST; 通过HTTP POST简单的事件通知. 实施 WebHooks 的 Web 应用程序将在某些事情发生时向URL发送消息. 要了解有关使用Webhook模式的更多信息，请参阅[Webhook模式](/docs/admin/authorization/webhook/)
-* **自定义模块**  - 您可以创建使用Kubernetes的自定义模块. 要了解更多信息，请参阅下面的**自定义模块**。
+* **ABAC 模式**  - 基于属性的访问控制 (ABAC) 定义了访问控制范例，通过使用将属性组合在一起的策略来授予用户访问权限。策略可以使用任何类型的属性 ( 用户属性，资源属性，对象，环境属性等 )。要了解有关使用 ABAC 模式的更多信息，请参阅 [ABAC 模式](/docs/admin/authorization/abac/)
+* **RBAC 模式**  - 基于角色的访问控制 (RBAC) 是一种根据企业内个人用户的角色来调整对计算机或网络资源的访问的方法。在这种情况下，访问是单个用户执行特定任务 ( 例如查看，创建或修改文件 ) 的能力。要了解有关使用 RBAC 模式的更多信息，请参阅 [RBAC 模式](/docs/admin/authorization/rbac/)
+*当指定 "RBAC"( 基于角色的访问控制 ) 使用 "rbac.authorization.k8s.io" API 组来驱动授权决定时，允许管理员通过 Kubernetes API 动态配置权限策略 .
+.. *截至 1.6 RBAC 模式是测试版 .
+.. *要启用 RBAC，请使用 `--authorization-mode=RBAC` 启动 apiserver.
+* **Webhook 模式**  -  WebHook 是 HTTP 回调 : 发生事件时发生的 HTTP POST; 通过 HTTP POST 简单的事件通知 . 实施 WebHooks 的 Web 应用程序将在某些事情发生时向 URL 发送消息 . 要了解有关使用 Webhook 模式的更多信息，请参阅[Webhook 模式](/docs/admin/authorization/webhook/)
+* **自定义模块**  - 您可以创建使用 Kubernetes 的自定义模块 . 要了解更多信息，请参阅下面的**自定义模块**。

 ### 自定义模块
-可以相当容易地开发其他实现,APIserver 调用 Authorizer 接口：
+可以相当容易地开发其他实现 ,APIserver 调用 Authorizer 接口：

 ```go
 type Authorizer interface {
@@ -80,15 +79,15 @@ type Authorizer interface {
 }
 ```

-以确定是否允许每个API操作.
+以确定是否允许每个 API 操作 .

-授权插件是实现此接口的模块.授权插件代码位于 `pkg/auth/authorizer/$MODULENAME` 中。
+授权插件是实现此接口的模块 . 授权插件代码位于 `pkg/auth/authorizer/$MODULENAME` 中。

 授权模块可以完全实现，也可以拨出远程授权服务。 授权模块可以实现自己的缓存，以减少具有相同或相似参数的重复授权调用的成本。 开发人员应该考虑缓存和撤销权限之间的交互。

-#### 检查API访问
+#### 检查 API 访问

-Kubernetes 将 `subjectaccessreviews.v1.authorization.k8s.io`  资源公开为允许外部访问API授权者决策的普通资源。 无论您选择使用哪个授权器，您都可以使用`SubjectAccessReview`发出一个`POST`，就像webhook授权器的`apis/authorization.k8s.io/v1/subjectaccessreviews` 端点一样，并回复一个响应。 例如：
+Kubernetes 将 `subjectaccessreviews.v1.authorization.k8s.io`  资源公开为允许外部访问 API 授权者决策的普通资源。 无论您选择使用哪个授权器，您都可以使用 `SubjectAccessReview` 发出一个 `POST`，就像 webhook 授权器的 `apis/authorization.k8s.io/v1/subjectaccessreviews` 端点一样，并回复一个响应。 例如：


 ```bash
@@ -128,16 +127,16 @@ subjectaccessreview "" created

 ## 为您的授权模块使用标志

-您的策略中必须包含一个标志，以指出您的策略包含哪个授权模块:
+您的策略中必须包含一个标志，以指出您的策略包含哪个授权模块 :

-可以使用以下标志:
- - `--authorization-mode=ABAC` 基于属性的访问控制(ABAC)模式允许您使用本地文件配置策略。
- - `--authorization-mode=RBAC` 基于角色的访问控制(RBAC)模式允许您使用Kubernetes API创建和存储策略.
- - `--authorization-mode=Webhook` WebHook是一种HTTP回调模式，允许您使用远程REST管理授权。
- - `--authorization-mode=AlwaysDeny` 此标志阻止所有请求. 仅使用此标志进行测试。
- - `--authorization-mode=AlwaysAllow` 此标志允许所有请求. 只有在您不需要API请求授权的情况下才能使用此标志。
+可以使用以下标志 :
+ - `--authorization-mode=ABAC` 基于属性的访问控制 (ABAC) 模式允许您使用本地文件配置策略。
+ - `--authorization-mode=RBAC` 基于角色的访问控制 (RBAC) 模式允许您使用 Kubernetes API 创建和存储策略 .
+ - `--authorization-mode=Webhook` WebHook 是一种 HTTP 回调模式，允许您使用远程 REST 管理授权。
+ - `--authorization-mode=AlwaysDeny` 此标志阻止所有请求 . 仅使用此标志进行测试。
+ - `--authorization-mode=AlwaysAllow` 此标志允许所有请求 . 只有在您不需要 API 请求授权的情况下才能使用此标志。

-您可以选择多个授权模块. 如果其中一种模式为 `AlwaysAllow`，则覆盖其他模式，并允许所有API请求。
+您可以选择多个授权模块，如果其中一种模式为 `AlwaysAllow`，则覆盖其他模式，并允许所有 API 请求。

 ## 版本控制

@@ -20,36 +20,36 @@ content_template: templates/concept

 基于 `ABAC` 模式，可以这样指定策略文件 `--authorization-policy-file=SOME_FILENAME`。

-此文件是 JSON 格式[每行都是一个JSON对象](http://jsonlines.org/)，不应存在封闭的列表或映射，每行只有一个映射。
+此文件是 JSON 格式[每行都是一个 JSON 对象](http://jsonlines.org/)，不应存在封闭的列表或映射，每行只有一个映射。

-每一行都是一个 "策略对象"，策略对象是具有以下映射的属性:
+每一行都是一个 " 策略对象 "，策略对象是具有以下映射的属性 :

-  - 版本控制属性:
-    - `apiVersion`，字符串类型: 有效值为"abac.authorization.kubernetes.io/v1beta1"，允许版本控制和转换策略格式。
-    - `kind`，字符串类型: 有效值为 "Policy"，允许版本控制和转换策略格式。
-  - `spec` 配置为具有以下映射的属性:
-    - 匹配属性:
-      - `user`，字符串类型; 来自 `--token-auth-file` 的用户字符串，如果你指定`user`，它必须与验证用户的用户名匹配。
-      - `group`，字符串类型; 如果指定`group`，它必须与经过身份验证的用户的一个组匹配，`system:authenticated`匹配所有经过身份验证的请求。`system:unauthenticated`匹配所有未经过身份验证的请求。
-  - 资源匹配属性:
-    - `apiGroup`，字符串类型; 一个 API 组。
-      - 例: `extensions`
-      - 通配符: `*`匹配所有 API 组。
-    - `namespace`，字符串类型; 一个命名空间。
-      - 例如: `kube-system`
-      - 通配符: `*` 匹配所有资源请求。
-    - `resource`，字符串类型; 资源类型。
-      - 例:`pods`
-      - 通配符: `*`匹配所有资源请求。
-  - 非资源匹配属性:
-    - `nonResourcePath`，字符串类型; 非资源请求路径。
-      - 例如:`/version`或`/apis`
-      - 通配符:
+  - 版本控制属性 :
+    - `apiVersion`，字符串类型 : 有效值为 "abac.authorization.kubernetes.io/v1beta1"，允许版本控制和转换策略格式。
+    - `kind`，字符串类型 : 有效值为 "Policy"，允许版本控制和转换策略格式。
+  - `spec` 配置为具有以下映射的属性 :
+    - 匹配属性 :
+      - `user`，字符串类型 ; 来自 `--token-auth-file` 的用户字符串，如果你指定 `user`，它必须与验证用户的用户名匹配。
+      - `group`，字符串类型 ; 如果指定 `group`，它必须与经过身份验证的用户的一个组匹配，`system:authenticated` 匹配所有经过身份验证的请求。`system:unauthenticated` 匹配所有未经过身份验证的请求。
+  - 资源匹配属性 :
+    - `apiGroup`，字符串类型 ; 一个 API 组。
+      - 例 : `extensions`
+      - 通配符 : `*` 匹配所有 API 组。
+    - `namespace`，字符串类型 ; 一个命名空间。
+      - 例如 : `kube-system`
+      - 通配符 : `*` 匹配所有资源请求。
+    - `resource`，字符串类型 ; 资源类型。
+      - 例 :`pods`
+      - 通配符 : `*` 匹配所有资源请求。
+  - 非资源匹配属性 :
+    - `nonResourcePath`，字符串类型 ; 非资源请求路径。
+      - 例如 :`/version` 或 `/apis`
+      - 通配符 :
        - `*` 匹配所有非资源请求。
-        - `/foo/*` 匹配`/foo/`的所有子路径。
+        - `/foo/*` 匹配 `/foo/` 的所有子路径。
  - `readonly`，键入 boolean，如果为 true，则表示该策略仅适用于 get，list 和 watch 操作。

-**注意:** 未设置的属性与类型设置为零值的属性相同(例如空字符串，0、false)，然而未知的应该可读性优先。
+**注意 :** 未设置的属性与类型设置为零值的属性相同 ( 例如空字符串，0、false)，然而未知的应该可读性优先。

 在将来，策略可能以 JSON 格式表示，并通过 REST 界面进行管理。

@@ -57,58 +57,58 @@ content_template: templates/concept

 请求具有与策略对象的属性对应的属性。

-当接收到请求时，确定属性。 未知属性设置为其类型的零值（例如: 空字符串，0，false）。
+当接收到请求时，确定属性。 未知属性设置为其类型的零值（例如 : 空字符串，0，false）。

-设置为`“*"`的属性将匹配相应属性的任何值。
+设置为 `"*"` 的属性将匹配相应属性的任何值。

 检查属性的元组，以匹配策略文件中的每个策略。 如果至少有一行匹配请求属性，则请求被授权（但可能会在稍后验证失败）。

-要允许任何经过身份验证的用户执行某些操作，请将策略组属性设置为 `"system:authenticated“`。
+要允许任何经过身份验证的用户执行某些操作，请将策略组属性设置为 `"system:authenticated"`。

-要允许任何未经身份验证的用户执行某些操作，请将策略组属性设置为`"system:authentication“`。
+要允许任何未经身份验证的用户执行某些操作，请将策略组属性设置为 `"system:authentication"`。

 要允许用户执行任何操作，请使用 apiGroup，命名空间，
-资源和 nonResourcePath 属性设置为 `“*"`的策略.
+资源和 nonResourcePath 属性设置为 `"*"` 的策略。

-要允许用户执行任何操作，请使用设置为`“*”` 的 apiGroup，namespace，resource 和 nonResourcePath 属性编写策略。
+要允许用户执行任何操作，请使用设置为 `"*"` 的 apiGroup，namespace，resource 和 nonResourcePath 属性编写策略。

 ## Kubectl

-Kubectl 使用 api-server 的 `/api` 和 `/apis` 端点进行协商客户端/服务器版本。 通过创建/更新来验证发送到API的对象操作，kubectl 查询某些 swagger 资源。 对于API版本"v1", 那就是`/swaggerapi/api/v1` ＆ `/swaggerapi/ experimental/v1`。
+Kubectl 使用 api-server 的 `/api` 和 `/apis` 端点进行协商客户端 / 服务器版本。 通过创建 / 更新来验证发送到 API 的对象操作，kubectl 查询某些 swagger 资源。 对于 API 版本 "v1", 那就是 `/swaggerapi/api/v1` ＆ `/swaggerapi/ experimental/v1`。

-当使用 ABAC 授权时，这些特殊资源必须明确通过策略中的 `nonResourcePath` 属性暴露出来(参见下面的[例子](#examples)):
+当使用 ABAC 授权时，这些特殊资源必须明确通过策略中的 `nonResourcePath` 属性暴露出来 ( 参见下面的[例子](#examples)):

-* `/api`，`/api/*`，`/apis`和`/apis/*` 用于 API 版本协商.
-* `/version` 通过 `kubectl version` 检索服务器版本.
-* `/swaggerapi/*` 用于创建/更新操作.
+* `/api`，`/api/*`，`/apis` 和 `/apis/*` 用于 API 版本协商。
+* `/version` 通过 `kubectl version` 检索服务器版本。
+* `/swaggerapi/*` 用于创建 / 更新操作。

-要检查涉及到特定kubectl操作的HTTP调用，您可以调整详细程度：
+要检查涉及到特定 kubectl 操作的 HTTP 调用，您可以调整详细程度：

    kubectl --v=8 version

 ## 例子

-1. Alice 可以对所有资源做任何事情:
+1. Alice 可以对所有资源做任何事情 :

    ```json
    {"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"user": "alice", "namespace": "*", "resource": "*", "apiGroup": "*"}}
    ```
-2. Kubelet 可以读取任何pod:
+2. Kubelet 可以读取任何 pod:

    ```json
    {"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"user": "kubelet", "namespace": "*", "resource": "pods", "readonly": true}}
    ```
-3. Kubelet 可以读写事件:
+3. Kubelet 可以读写事件 :

    ```json
    {"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"user": "kubelet", "namespace": "*", "resource": "events"}}
    ```
-4. Bob 可以在命名空间“projectCaribou"中读取 pod:
+4. Bob 可以在命名空间 “projectCaribou” 中读取 pod：

    ```json
    {"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"user": "bob", "namespace": "projectCaribou", "resource": "pods", "readonly": true}}
    ```
-5. 任何人都可以对所有非资源路径进行只读请求:
+5. 任何人都可以对所有非资源路径进行只读请求：

    ```json
    {"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"group": "system:authenticated", "readonly": true, "nonResourcePath": "*"}}
@@ -119,7 +119,7 @@ Kubectl 使用 api-server 的 `/api` 和 `/apis` 端点进行协商客户端/服

 ## 服务帐户的快速说明

-服务帐户自动生成用户。 用户名是根据命名约定生成的:
+服务帐户自动生成用户。 用户名是根据命名约定生成的：

 ```shell
 system:serviceaccount:<namespace>:<serviceaccountname>
@@ -130,13 +130,13 @@ system:serviceaccount:<namespace>:<serviceaccountname>
 system:serviceaccount:<namespace>:default
 ```

-例如，如果要将 API 的 kube-system 完整权限中的默认服务帐户授予，则可以将此行添加到策略文件中:
+例如，如果要将 API 的 kube-system 完整权限中的默认服务帐户授予，则可以将此行添加到策略文件中 :

 ```json
 {"apiVersion":"abac.authorization.kubernetes.io/v1beta1","kind":"Policy","spec":{"user":"system:serviceaccount:kube-system:default","namespace":"*","resource":"*","apiGroup":"*"}}
 ```

-需要重新启动 apiserver 以获取新的策略行.
+需要重新启动 apiserver 以获取新的策略行。

 {{% /capture %}}

@@ -29,10 +29,10 @@ WebHook 是一种 HTTP 回调：某些条件下触发的 HTTP POST 请求；通
 clusters:
  - name: name-of-remote-authz-service
    cluster:
-      certificate-authority: /path/to/ca.pem      # 对远程服务进行身份认证的CA。
+      certificate-authority: /path/to/ca.pem      # 对远程服务进行身份认证的 CA。
      server: https://authz.example.com/authorize # 远程服务的查询 URL. 必须使用 'https'。

-# users 代表 API 服务器的 webhook 配置.
+# users 代表 API 服务器的 webhook 配置 .
 users:
  - name: name-of-api-server
    user:
@@ -55,7 +55,7 @@ contexts:

 需要注意的是 webhook API 对象与其他 Kubernetes API 对象一样都同样都服从 [版本兼容规则](/docs/api/) 。
 实施人员应该了解 beta 对象的更宽松的兼容性承诺，同时确认请求的 "apiVersion" 字段以确保能被正确地反序列化。
-此外，API 服务器还必须启用 `authorization.k8s.io/v1beta1` API 扩展组(`--runtime-config=authorization.k8s.io/v1beta1=true`)。
+此外，API 服务器还必须启用 `authorization.k8s.io/v1beta1` API 扩展组 (`--runtime-config=authorization.k8s.io/v1beta1=true`)。


 一个请求内容的例子：
@@ -15,8 +15,8 @@ Bootstrapping](/docs/admin/kubelet-tls-bootstrapping/) 系统进行工作。

 启动引导令牌被定义成一个特定类型的 secrets(`bootstrap.kubernetes.io/token`)，并存在于
 `kube-system` 命名空间中。然后这些 secrets 会被 API 服务器上的启动引导的认证器读取。
-控制器管理器中的控制器TokenCleaner能够删除过期的令牌。在节点发现的过程中Kubernetes会使用特殊的ConfigMap对象。
-控制器管理器中的BootstrapSigner控制器也会使用启动引导令牌为这类对象生成签名信息。
+控制器管理器中的控制器 TokenCleaner 能够删除过期的令牌。在节点发现的过程中 Kubernetes 会使用特殊的 ConfigMap 对象。
+控制器管理器中的 BootstrapSigner 控制器也会使用启动引导令牌为这类对象生成签名信息。

 目前，启动引导令牌处于 **alpha** 阶段，但是预期也不会有大的突破性变化。

@@ -26,7 +26,7 @@ Bootstrapping](/docs/admin/kubelet-tls-bootstrapping/) 系统进行工作。
 更加规范地说，它们必须符合正则表达式 `[a-z0-9]{6}\.[a-z0-9]{16}`。

 令牌的第一部分是 "Token ID" ，它是公共信息。用于引用某个令牌，并确保不会泄露认证所使用的秘密信息。
-第二部分是 "令牌秘密（Token Secret）"，它应该被共享给收信的第三方。
+第二部分是“令牌秘密（Token Secret）”，它应该被共享给收信的第三方。

 ## 启用启动引导令牌

@@ -82,19 +82,19 @@ TokenCleaner 控制器会删除过期的令牌。

 ## 使用 `kubeadm` 管理令牌

-你可以使用 `kubeadm` 工具管理正在运行集群的令牌。它会从 `kubeadm` 创建的集群(`/etc/kubernetes/admin.conf`)
+你可以使用 `kubeadm` 工具管理正在运行集群的令牌。它会从 `kubeadm` 创建的集群（`/etc/kubernetes/admin.conf`）
 自动抓取默认管理员密码。你可以通过参数 `--kubeconfig` 对下面命令指定一个另外的 kubeconfig 文件抓取密码。

 * `kubeadm token list` 列举了令牌，同时显示了它们的过期时间和用途。
 * `kubeadm token create` 创建一个新令牌。
    * `--description` 设置新令牌的描述。
-    * `--ttl duration` 设置令牌从 "现在" 起到过期时间的差值。
+    * `--ttl duration` 设置令牌从“现在”起到过期时间的差值。
      默认是 0 ，也就是不过期。
    * `--usages` 设置令牌被使用的方式。默认是 `signing,authentication`。用途在上面已经描述。
 * `kubeadm token delete <token id>|<token id>.<token secret>` 删除令牌。
  令牌可以只用 ID 来确认，也可以用整个令牌的值。如果只用 ID 的情况下，密文不匹配的令牌也会被删除。

-### ConfigMap签名
+### ConfigMap 签名

 除了认证之外，令牌可以用于签名 ConfigMap。这在集群启动过程的早期，在客户端信任 API 服务器之前被使用。
 被签名的 ConfigMap 可以通过共享令牌被认证。
@@ -131,6 +131,6 @@ ConfigMap 的 `kubeconfig` 成员是一个填好了集群信息的配置文件
 这里主要交换的信息是 `certificate-authority-data`。在将来可能会有扩展。

 签名是一个 JWS 签名，使用了 "detached" 模式。为了检验签名，用户应该按照 JWS 规则
-(base64 编码而忽略结尾的 `=`)对 `kubeconfig` 的载荷进行编码。完成编码的载荷会被通过插入 JWS 并存在于两个点的中间
+（base64 编码而忽略结尾的 `=`）对 `kubeconfig` 的载荷进行编码。完成编码的载荷会被通过插入 JWS 并存在于两个点的中间
 ，用于形成一个完整的 JWS。可以使用令牌的完整信息（比如 `07401b.f395accd246ae52d`）作为共享密钥，
 通过 `HS256` 方式 (HMAC-SHA256) 对 JWS 进行校验。 用户 _必须_ 确保使用了 HS256。
@@ -7,12 +7,12 @@ title: 创建大规模集群

 ## 支持规格

-在 {{< param "version" >}}，Kubernetes支持最多5000节点规模的集群。 更具体地说，我们支持满足以下 *所有* 标准的配置：
+在 {{< param "version" >}}，Kubernetes 支持最多 5000 节点规模的集群。 更具体地说，我们支持满足以下 *所有* 标准的配置：

-* 不超过5000节点
-* 总共不超过15000个pod
-* 总共不超过300000个容器
-* 每个节点不超过100个pod
+* 不超过 5000 节点
+* 总共不超过 15000 个 pod
+* 总共不超过 300000 个容器
+* 每个节点不超过 100 个 pod

 <br>

@@ -21,64 +21,64 @@ title: 创建大规模集群

 ## 创建

-集群是一组运行Kubernetes代理组件的节点(物理或虚拟机)，它们被 "master" (集群管理平面)所管理。
+集群是一组运行 Kubernetes 代理组件的节点（物理或虚拟机），它们被 `master`（集群管理平面）所管理。

-一般来说，集群的节点数量通过平台相关的 `config-default.sh` 文件中的 `NUM_NODES` 值来控制，(例如，详见 [GCE's `config-default.sh`](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/gce/config-default.sh))。
+一般来说，集群的节点数量通过平台相关的 `config-default.sh` 文件中的 `NUM_NODES` 值来控制，（例如，详见 [GCE's `config-default.sh`](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/gce/config-default.sh)）。

-对很多云提供商来说，单纯地修改`NUM_NODES` 为一个非常大的值，可能会导致集群的创建脚本失败。 例如，在GCE中部署时，会因配额不足，导致集群启动失败。
+对很多云提供商来说，单纯地修改 `NUM_NODES` 为一个非常大的值，可能会导致集群的创建脚本失败。 例如，在 GCE 中部署时，会因配额不足，导致集群启动失败。

-当建立一个大型的Kubernetes集群，以下几个问题必须考虑。
+当建立一个大型的 Kubernetes 集群，以下几个问题必须考虑。

 ### 配额问题

 为了避免出现配额问题，当创建包含大量节点的集群时，考虑：

-* 提高相关配额，如CPU，IP等。
-  * 如，在 [GCE](https://cloud.google.com/compute/docs/resource-quotas)中，你可能需要提高以下资源的配额：
+* 提高相关配额，如 CPU，IP 等。
+  * 如，在 [GCE](https://cloud.google.com/compute/docs/resource-quotas) 中，你可能需要提高以下资源的配额：
    * CPU
    * 虚机实例
    * 磁盘
-    * 使用的IP地址
+    * 使用的 IP 地址
    * 防火墙规则
    * 转发规则
    * 路由
    * 对象池
 * 设置创建脚本，使其以较小的规模分批次拉起新的节点，并在其间设置一定的等待时间，因为一些云供应商可能对虚机的创建速率进行了限制。

-### Etcd存储
+### Etcd 存储

-为了提升大规模集群的性能，我们将事件对象存储到独立的etcd实例中。
+为了提升大规模集群的性能，我们将事件对象存储到独立的 etcd 实例中。

-创建集群时，当前的salt脚本：
+创建集群时，当前的 salt 脚本：

-* 启动并配置额外的etcd实例
-* 配置api-server，将该etcd实例用于事件对象的存储
+* 启动并配置额外的 etcd 实例
+* 配置 api-server，将该 etcd 实例用于事件对象的存储

 ### 管理节点和组件的规格

-在 GCE/Google Kubernetes Engine 或 AWS平台中， `kube-up` 会根据集群的节点规模合理地设置管理节点的规格。 在其他云平台上，用户需要手动配置。 作为参考，GCE使用的规格为：
+在 GCE/Google Kubernetes Engine 或 AWS 平台中， `kube-up` 会根据集群的节点规模合理地设置管理节点的规格。 在其他云平台上，用户需要手动配置。 作为参考，GCE 使用的规格为：

 * 1-5 节点： n1-standard-1
 * 6-10 节点： n1-standard-2
 * 11-100 节点： n1-standard-4
 * 101-250 节点： n1-standard-8
 * 251-500 节点： n1-standard-16
-* 500节点以上： n1-standard-32
+* 500 节点以上： n1-standard-32

-AWS使用的规格为：
+AWS 使用的规格为：

 * 1-5 节点： m3.medium
 * 6-10 节点： m3.large
 * 11-100 节点： m3.xlarge
 * 101-250 节点： m3.2xlarge
 * 251-500 节点： c4.4xlarge
-* 500节点以上： c4.8xlarge
+* 500 节点以上： c4.8xlarge

-注意，管理节点的规格只会在集群创建时进行设置，后续集群规模发生变化 (如 手动增删节点或集群自动扩缩容)后不会再调整。
+注意，管理节点的规格只会在集群创建时进行设置，后续集群规模发生变化（如手动增删节点或集群自动扩缩容）后不会再调整。

 ### 插件的资源占用

-为防止 [集群插件](https://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons) 耗尽节点资源引起内存泄漏或其他资源问题， Kubernetes 设置了插件容器资源的上限，来限制其对CPU和内存资源的占用 (参考 PR [#10653](http://pr.k8s.io/10653/files) 和 [#10778](http://pr.k8s.io/10778/files))。
+为防止[集群插件](https://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons)耗尽节点资源引起内存泄漏或其他资源问题， Kubernetes 设置了插件容器资源的上限，来限制其对 CPU 和内存资源的占用（参考 PR [#10653](http://pr.k8s.io/10653/files) 和 [#10778](http://pr.k8s.io/10778/files)）。

 例如：

@@ -92,31 +92,31 @@ AWS使用的规格为：
        memory: 200Mi
 ```

-除 Heapster 外，这些限制是静态的，基于4个节点规模的集群上运行的插件所采集的数据 (详见 [#10335](http://issue.k8s.io/10335#issuecomment-117861225))。 而实际大规模集群中插件所消耗的资源要多得多 (详见 [#5880](http://issue.k8s.io/5880#issuecomment-113984085))。 所以如果部署大规模集群时不对这些值进行调整，插件可能会因为资源占用达到上限而不断被杀死。
+除 Heapster 外，这些限制是静态的，基于 4 个节点规模的集群上运行的插件所采集的数据（详见 [#10335](http://issue.k8s.io/10335#issuecomment-117861225)）。 而实际大规模集群中插件所消耗的资源要多得多（详见 [#5880](http://issue.k8s.io/5880#issuecomment-113984085)）。 所以如果部署大规模集群时不对这些值进行调整，插件可能会因为资源占用达到上限而不断被杀死。

 为了避免集群插件的资源问题，创建多节点的集群时，考虑以下几点：

-* 当扩大集群规模时，如果涉及，相应扩大以下插件的内存和CPU限制 (通过一个实例处理整个集群，因此其内存和CPU使用量往往与集群的大小/负载成比例增长)：
+* 当扩大集群规模时，如果涉及，相应扩大以下插件的内存和 CPU 限制（通过一个实例处理整个集群，因此其内存和 CPU 使用量往往与集群的大小/负载成比例增长）：
  * [InfluxDB 和 Grafana](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/cluster-monitoring/influxdb/influxdb-grafana-controller.yaml)
  * [kubedns, dnsmasq, 和 sidecar](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/dns/kubedns-controller.yaml.in)
  * [Kibana](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/fluentd-elasticsearch/kibana-controller.yaml)
-* 当扩大集群规模时，如果涉及，相应扩大以下插件副本数 (每个组件有多个副本，因此增加副本将有助于处理增加的负载，但是，由于每个副本的负载也略有增加，也应考虑提高CPU /内存上限)：
+* 当扩大集群规模时，如果涉及，相应扩大以下插件副本数（每个组件有多个副本，因此增加副本将有助于处理增加的负载，但是，由于每个副本的负载也略有增加，也应考虑提高 CPU / 内存上限）：
  * [elasticsearch](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/fluentd-elasticsearch/es-controller.yaml)
-* 当扩大集群规模时，如果涉及，略微扩大以下插件的内存和CPU限制 (每个节点一个副本， 但是CPU/内存使用随集群的大小/负载增长变化不明显)：
+* 当扩大集群规模时，如果涉及，略微扩大以下插件的内存和 CPU 限制（每个节点一个副本， 但是 CPU / 内存使用随集群的大小/负载增长变化不明显）：
  * [FluentD with ElasticSearch Plugin](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/fluentd-elasticsearch/fluentd-es-ds.yaml)
  * [FluentD with GCP Plugin](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/fluentd-gcp/fluentd-gcp-ds.yaml)

-Heapster的资源限制是基于集群的初始规模动态设置的 (参考 [#16185](http://issue.k8s.io/16185)
-和 [#22940](http://issue.k8s.io/22940))。 当发现Heapster资源耗尽，应考虑调整计算Heapster内存请求的公式 (参考上述PR)。
+Heapster 的资源限制是基于集群的初始规模动态设置的 ( 参考 [#16185](http://issue.k8s.io/16185)
+和 [#22940](http://issue.k8s.io/22940))。 当发现 Heapster 资源耗尽，应考虑调整计算 Heapster 内存请求的公式（参考上述 PR）。

 关于如何检测插件是否达到资源上限 参考 [计算资源的故障排除章节](/docs/concepts/configuration/manage-compute-resources-container/#troubleshooting)。

 [将来](http://issue.k8s.io/13048)，我们期望基于集群规模来设置集群插件的资源限制，并且在集群规模增长或缩小时能够动态调整。
-欢迎提出PR来实现这些特性。
+欢迎提出 PR 来实现这些特性。

 ### 启动时允许部分失败

-因为种种原因 (详见 [#18969](https://github.com/kubernetes/kubernetes/issues/18969))，在 `NUM_NODES` 值很大的情况下执行
+因为种种原因（详见 [#18969](https://github.com/kubernetes/kubernetes/issues/18969)），在 `NUM_NODES` 值很大的情况下执行
 `kube-up.sh`， 可能因为其中一小部分节点没有正常启动而失败。
-这时我们有两种选择：重启集群 (`kube-down.sh` 然后再 `kube-up.sh`），或者在执行 `kube-up.sh`之前，
+这时我们有两种选择：重启集群（`kube-down.sh` 然后再 `kube-up.sh`），或者在执行 `kube-up.sh` 之前，
 将环境变量 `ALLOWED_NOTREADY_NODES` 设置为合适的值。 这将允许 `kube-up.sh` 以少于 `NUM_NODES` 的节点数量启动集群。 依据失败的具体原因，另外的节点可能在后面加入集群，或者集群节点数量将保持在 `NUM_NODES - ALLOWED_NOTREADY_NODES`。
@@ -6,12 +6,12 @@ title: 构建高可用集群
 ## 简介


-本文描述了如何构建一个高可用（high-availability, HA）的Kubernetes集群。这是一个非常高级的主题。
+本文描述了如何构建一个高可用（high-availability, HA）的 Kubernetes 集群。这是一个非常高级的主题。

-对于仅希望使用Kubernetes进行试验的用户，推荐使用更简单的配置工具进行搭建，例如：
-[Minikube](/docs/getting-started-guides/minikube/)，或者尝试使用[Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/) 来运行Kubernetes。
+对于仅希望使用 Kubernetes 进行试验的用户，推荐使用更简单的配置工具进行搭建，例如：
+[Minikube](/docs/getting-started-guides/minikube/)，或者尝试使用[Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/) 来运行 Kubernetes。

-此外，当前在我们的端到端（e2e）测试环境中，没有对Kubernetes高可用的支持进行连续测试。我们将会增加这个连续测试项，但当前对单节点master的安装测试得更加严格。
+此外，当前在我们的端到端（e2e）测试环境中，没有对 Kubernetes 高可用的支持进行连续测试。我们将会增加这个连续测试项，但当前对单节点 master 的安装测试得更加严格。

 {{< toc >}}

@@ -23,10 +23,10 @@ title: 构建高可用集群

 相关步骤如下：

-   * [创建可靠的组成节点，共同形成我们的高可用主节点实现。](#可靠的节点)
-   * [使用etcd集群，搭建一个冗余的，可靠的存储层。](#建立一个冗余的，可靠的存储层)
-   * [启动具有备份和负载均衡能力的Kubernetes API 服务](#复制的API服务)
-   * [搭建运行master选举的Kubernetes scheduler和controller-manager守护程序](#进行master选举的组件)
+   * [创建可靠的组成节点，共同形成我们的高可用主节点实现。](# 可靠的节点 )
+   * [使用 etcd 集群，搭建一个冗余的，可靠的存储层。](# 建立一个冗余的，可靠的存储层 )
+   * [启动具有备份和负载均衡能力的 Kubernetes API 服务](# 复制的 API 服务 )
+   * [搭建运行 master 选举的 Kubernetes scheduler 和 controller-manager 守护程序](# 进行 master 选举的组件 )
  
 系统完成时看起来应该像这样：

@@ -36,28 +36,28 @@ title: 构建高可用集群
 ## 初始配置


-本文假设你正在搭建一个3节点的主节点集群，每个节点上都运行者某种Linux系统。
+本文假设你正在搭建一个 3 节点的主节点集群，每个节点上都运行者某种 Linux 系统。

-指南中的示例使用Debian发行版，但它们应该可以被轻松移植到其他发行版上。
+指南中的示例使用 Debian 发行版，但它们应该可以被轻松移植到其他发行版上。

 同样的，不管在公有云还是私有云亦或是裸机上，这个配置都应该可以运行。


-从一个现成的单主节点集群开始是实现一个高可用Kubernetes集群的最简单的方法。这篇指导 [https://get.k8s.io](https://get.k8s.io) 描述了在多种平台上方便的安装一个单主节点集群的方法。
+从一个现成的单主节点集群开始是实现一个高可用 Kubernetes 集群的最简单的方法。这篇指导 [https://get.k8s.io](https://get.k8s.io) 描述了在多种平台上方便的安装一个单主节点集群的方法。

 ## 可靠的节点


-我们在每个主节点上都将运行数个实现Kubernetes API的进程。使他们可靠的第一步是保证在发生故障时，每一个进程都可以自动重启。为了实现这个目标，我们需要安装一个进程监视器。我们选择了在每个工作者节点上都会运行的`kubelet`进程。这会带来便利性，因为我们使用了容器来分发我们的二进制文件，所以我们能够为每一个守护程序建立资源限制并省查它们的资源消耗。当然，我们也需要一些手段来监控kubelete本身（在此监测监控者本身是一个有趣的话题）。对于Debian系统我们选择了monit，但也有许多可替代的工具。例如在基于systemd的系统上（如RHEL, CentOS），你可以运行 'systemctl enable kubelet'。
+我们在每个主节点上都将运行数个实现 Kubernetes API 的进程。使他们可靠的第一步是保证在发生故障时，每一个进程都可以自动重启。为了实现这个目标，我们需要安装一个进程监视器。我们选择了在每个工作者节点上都会运行的 `kubelet` 进程。这会带来便利性，因为我们使用了容器来分发我们的二进制文件，所以我们能够为每一个守护程序建立资源限制并省查它们的资源消耗。当然，我们也需要一些手段来监控 kubelete 本身（在此监测监控者本身是一个有趣的话题）。对于 Debian 系统我们选择了 monit，但也有许多可替代的工具。例如在基于 systemd 的系统上（如 RHEL, CentOS），你可以运行 'systemctl enable kubelet'。


-如果你是从标准的Kubernetes安装扩展而来，那么`kubelet`二进制文件应该已经存在于你的系统中。你可以运行`which kubelet`来判断是否确实安装了这个二进制文件。如果没有安装的话，你应该手动安装 [kubelet binary](https://storage.googleapis.com/kubernetes-release/release/v0.19.3/bin/linux/amd64/kubelet), 
-[kubelet init file](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/saltbase/salt/kubelet/initd) 和 [default-kubelet](/docs/admin/high-availability/default-kubelet)脚本。
+如果你是从标准的 Kubernetes 安装扩展而来，那么 `kubelet` 二进制文件应该已经存在于你的系统中。你可以运行 `which kubelet` 来判断是否确实安装了这个二进制文件。如果没有安装的话，你应该手动安装 [kubelet binary](https://storage.googleapis.com/kubernetes-release/release/v0.19.3/bin/linux/amd64/kubelet), 
+[kubelet init file](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/saltbase/salt/kubelet/initd) 和 [default-kubelet](/docs/admin/high-availability/default-kubelet) 脚本。

-如果使用monit，你还需要安装monit守护程序（`apt-get install monit`）以及[monit-kubelet](/docs/admin/high-availability/monit-kubelet) 和
+如果使用 monit，你还需要安装 monit 守护程序（`apt-get install monit`）以及[monit-kubelet](/docs/admin/high-availability/monit-kubelet) 和
 [monit-docker](/docs/admin/high-availability/monit-docker) 配置。

-在使用systemd的系统上，你可以执行 `systemctl enable kubelet` 和 `systemctl enable docker`。
+在使用 systemd 的系统上，你可以执行 `systemctl enable kubelet` 和 `systemctl enable docker`。


 ## 建立一个冗余的，可靠的存储层
@@ -66,35 +66,35 @@ title: 构建高可用集群
 高可用方案的中心基础是一个冗余的，可靠的存储层。高可用的头条规则是保护数据。不管发生了什么，不管什么着了火，只要还有数据，你就可以重建。如果丢掉了数据，你就完了。


-集群化的etcd已经把你存储的数据复制到了你集群中的所有主节点实例上。这意味着如果要想丢失数据，三个节点的物理（或虚拟）硬盘需要全部同时故障。这种情况发生的概率是比较低的，所以对于许多人来说，运行一个复制的etcd集群可能已经足够的可靠了。你可以将集群数量从3个增大到5个来增加集群的可靠性。如果那样还不够，你可以添加[更多的可靠性到你的存储层](#更加可靠的存储)。
+集群化的 etcd 已经把你存储的数据复制到了你集群中的所有主节点实例上。这意味着如果要想丢失数据，三个节点的物理（或虚拟）硬盘需要全部同时故障。这种情况发生的概率是比较低的，所以对于许多人来说，运行一个复制的 etcd 集群可能已经足够的可靠了。你可以将集群数量从 3 个增大到 5 个来增加集群的可靠性。如果那样还不够，你可以添加[更多的可靠性到你的存储层](# 更加可靠的存储 )。


-### 集群化etcd
+### 集群化 etcd


-集群化etcd的完整细节超出了本文范围，你可以在[etcd clustering page](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/clustering.md)找到许多详细内容。这个例子仅走查一个简单的集群建立过程，使用etcd内置的发现功能来构建我们的集群。
+集群化 etcd 的完整细节超出了本文范围，你可以在[etcd clustering page](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/clustering.md) 找到许多详细内容。这个例子仅走查一个简单的集群建立过程，使用 etcd 内置的发现功能来构建我们的集群。


-首先，调用etcd发现服务来创建一个新令牌:
+首先，调用 etcd 发现服务来创建一个新令牌 :

 ```shell
 curl https://discovery.etcd.io/new?size=3
 ```


-在每个节点上，拷贝 [etcd.yaml](/docs/admin/high-availability/etcd.yaml) 文件到`/etc/kubernetes/manifests/etcd.yaml`。
+在每个节点上，拷贝 [etcd.yaml](/docs/admin/high-availability/etcd.yaml) 文件到 `/etc/kubernetes/manifests/etcd.yaml`。


-每个节点上的kubelet会动态的监控这个文件夹的内容，并且会按照`etcd.yaml`里对pod的定义创建一个`etcd`服务的实例。
+每个节点上的 kubelet 会动态的监控这个文件夹的内容，并且会按照 `etcd.yaml` 里对 pod 的定义创建一个 `etcd` 服务的实例。


-请注意，你应该使用上文中获取的令牌URL替换全部三个节点上`etcd.yaml`中的`${DISCOVERY_TOKEN}`项。同时还应该将每个节点上的 `${NODE_NAME}`替换为一个不同的名字（例如：`node-1`），并将 `${NODE_IP}`替换为正确的IP地址。
+请注意，你应该使用上文中获取的令牌 URL 替换全部三个节点上 `etcd.yaml` 中的 `${DISCOVERY_TOKEN}` 项。同时还应该将每个节点上的 `${NODE_NAME}` 替换为一个不同的名字（例如：`node-1`），并将 `${NODE_IP}` 替换为正确的 IP 地址。


 #### 验证你的集群


-如果已经将这个文件拷贝到所有三个节点，你应该已经搭建起了一个集群化的etcd。你可以在主节点上进行验证：
+如果已经将这个文件拷贝到所有三个节点，你应该已经搭建起了一个集群化的 etcd。你可以在主节点上进行验证：
 ```shell
 kubectl exec < pod_name > etcdctl member list
 ```
@@ -106,43 +106,43 @@ kubectl exec < pod_name > etcdctl cluster-health
 ```


-你也可以在一个节点上运行 `etcdctl set foo bar`，在另一个节点上运行`etcdctl get foo`来验证集群是否工作正常。
+你也可以在一个节点上运行 `etcdctl set foo bar`，在另一个节点上运行 `etcdctl get foo` 来验证集群是否工作正常。


 ### 更加可靠的存储


-当然，如果你对增加数据的可靠性感兴趣，这里还有一些更深入的选项可以使etcd把它的数据存放在比常规硬盘更可靠的地方（裤带和背带，ftw!）。
+当然，如果你对增加数据的可靠性感兴趣，这里还有一些更深入的选项可以使 etcd 把它的数据存放在比常规硬盘更可靠的地方（裤带和背带，ftw!）。


-如果你使用云服务，那么你的提供商通常会为你提供这个特性，例如Google Cloud Platform上的 [Persistent Disk](https://cloud.google.com/compute/docs/disks/persistent-disks) 。它们是可以挂载到你的虚拟机中的块设备持久化存储。其他的云服务提供商提供了类似的解决方案。
+如果你使用云服务，那么你的提供商通常会为你提供这个特性，例如 Google Cloud Platform 上的 [Persistent Disk](https://cloud.google.com/compute/docs/disks/persistent-disks) 。它们是可以挂载到你的虚拟机中的块设备持久化存储。其他的云服务提供商提供了类似的解决方案。


-如果运行于物理机之上，你仍然可以使用iSCSI或者NFS接口通过网络来连接冗余存储。
-此外，你还可以运行一个集群文件系统，比如Gluster或者Ceph。最后，你还可以在你的每个物理机器上运行RAID矩阵。
+如果运行于物理机之上，你仍然可以使用 iSCSI 或者 NFS 接口通过网络来连接冗余存储。
+此外，你还可以运行一个集群文件系统，比如 Gluster 或者 Ceph。最后，你还可以在你的每个物理机器上运行 RAID 矩阵。


-不管你选择如何实现，如果已经选择了使用其中的一个选项，那么你应该保证你的存储被挂载到了每一台机器上。如果你的存储在集群中的三个主节点之间共享，那么你应该在存储上为每一个节点创建一个不同的文件夹。对于所有的这些指导，我们都假设这个存储被挂载到你机器上的`/var/etcd/data`路径。
+不管你选择如何实现，如果已经选择了使用其中的一个选项，那么你应该保证你的存储被挂载到了每一台机器上。如果你的存储在集群中的三个主节点之间共享，那么你应该在存储上为每一个节点创建一个不同的文件夹。对于所有的这些指导，我们都假设这个存储被挂载到你机器上的 `/var/etcd/data` 路径。


-## 复制的API服务
+## 复制的 API 服务


-在正确搭建复制的etcd之后，我们还需要使用kubelet安装apiserver。
+在正确搭建复制的 etcd 之后，我们还需要使用 kubelet 安装 apiserver。




-首先，你需要创建初始的日志文件，这样Docker才会挂载一个文件而不是一个文件夹：
+首先，你需要创建初始的日志文件，这样 Docker 才会挂载一个文件而不是一个文件夹：
 ```shell
 touch /var/log/kube-apiserver.log
 ```

-接下来，你需要在每个节点上创建一个`/srv/kubernetes/`文件夹。这个文件夹包含：
+接下来，你需要在每个节点上创建一个 `/srv/kubernetes/` 文件夹。这个文件夹包含：

   * basic_auth.csv  - 基本认证的用户名和密码
-   * ca.crt - CA证书
-   * known_tokens.csv - 实体（例如kubelet）用来和apiserver通信的令牌
+   * ca.crt - CA 证书
+   * known_tokens.csv - 实体（例如 kubelet）用来和 apiserver 通信的令牌
   * kubecfg.crt - 客户端证书，公钥
   * kubecfg.key - 客户端证书，私钥
   * server.cert - 服务端证书，公钥
@@ -152,46 +152,46 @@ touch /var/log/kube-apiserver.log
 创建这个文件夹最简单的方法可以是从一个工作正常的集群的主节点拷贝，或者你也可以手动生成它们。


-### 启动API服务
+### 启动 API 服务


-一旦这些文件已经存在了，拷贝 [kube-apiserver.yaml](/docs/admin/high-availability/kube-apiserver.yaml) 到每个主节点的 `/etc/kubernetes/manifests/`文件夹。
+一旦这些文件已经存在了，拷贝 [kube-apiserver.yaml](/docs/admin/high-availability/kube-apiserver.yaml) 到每个主节点的 `/etc/kubernetes/manifests/` 文件夹。


-kubelet会监控这个文件夹，并且会按照文件里对pod的定义创建一个`kube-apiserver`容器。
+kubelet 会监控这个文件夹，并且会按照文件里对 pod 的定义创建一个 `kube-apiserver` 容器。


 ### 负载均衡


-现在，你应该有3个全部正常工作的apiserver了。如果搭建了网络负载均衡器，你应该能够通过那个负载均衡器访问你的集群，并且看到负载在apiserver实例间分发。设置负载均衡器依赖于你的平台的实际情况，例如对于Google Cloud Platform的指导可以在[这里](https://cloud.google.com/compute/docs/load-balancing/)找到。
+现在，你应该有 3 个全部正常工作的 apiserver 了。如果搭建了网络负载均衡器，你应该能够通过那个负载均衡器访问你的集群，并且看到负载在 apiserver 实例间分发。设置负载均衡器依赖于你的平台的实际情况，例如对于 Google Cloud Platform 的指导可以在[这里](https://cloud.google.com/compute/docs/load-balancing/) 找到。


-请注意，如果使用了身份认证，你可能需要重新生成你的证书，除每个节点的IP地址外额外包含负载均衡器的IP地址。
+请注意，如果使用了身份认证，你可能需要重新生成你的证书，除每个节点的 IP 地址外额外包含负载均衡器的 IP 地址。


-对于部署在集群中的pods， `kubernetes`服务/dns名称应该自动的为主节点提供了负载均衡的endpoint。
+对于部署在集群中的 pods， `kubernetes` 服务 /dns 名称应该自动的为主节点提供了负载均衡的 endpoint。


-对于使用API的外部用户（如命令行运行的`kubectl`，持续集成管道或其他客户端）你会希望将他们配置成为访问外部负载均衡器的地址。
+对于使用 API 的外部用户（如命令行运行的 `kubectl`，持续集成管道或其他客户端）你会希望将他们配置成为访问外部负载均衡器的地址。


-## 进行Master选举的组件
+## 进行 Master 选举的组件


-到目前为止，我们已经搭建了状态存储，也搭建好了API服务，但我们还没有运行任何真正改变集群状态的服务，比如controller manager和scheduler。为了可靠的实现这个目标，我们希望在同一时间只有一个参与者在修改集群状态。但是我们希望复制这些参与者的实例以防某个机器宕机。要做到这一点，我们打算在API中使用一个lease-lock来执行master选举。我们会对每一个scheduler和controller-manager使用`--leader-elect`标志，从而在API中使用一个租约来保证同一时间只有一个scheduler和controller-manager的实例正在运行。
+到目前为止，我们已经搭建了状态存储，也搭建好了 API 服务，但我们还没有运行任何真正改变集群状态的服务，比如 controller manager 和 scheduler。为了可靠的实现这个目标，我们希望在同一时间只有一个参与者在修改集群状态。但是我们希望复制这些参与者的实例以防某个机器宕机。要做到这一点，我们打算在 API 中使用一个 lease-lock 来执行 master 选举。我们会对每一个 scheduler 和 controller-manager 使用 `--leader-elect` 标志，从而在 API 中使用一个租约来保证同一时间只有一个 scheduler 和 controller-manager 的实例正在运行。


-scheduler和controller-manager可以配置为只和位于它们相同节点（即127.0.0.1）上的API服务通信，也可以配置为使用API服务的负载均衡器的IP地址。不管它们如何配置，当使用`--leader-elect` 时scheduler和controller-manager都将完成上文提到的leader选举过程。
+scheduler 和 controller-manager 可以配置为只和位于它们相同节点（即 127.0.0.1）上的 API 服务通信，也可以配置为使用 API 服务的负载均衡器的 IP 地址。不管它们如何配置，当使用 `--leader-elect` 时 scheduler 和 controller-manager 都将完成上文提到的 leader 选举过程。


-为了防止访问API服务失败，选举出的leader不能通过更新租约来选举一个新的leader。当scheduler和controller-manager通过127.0.0.1访问API服务，而相同节点上的API服务不可用时，这一点相当重要。
+为了防止访问 API 服务失败，选举出的 leader 不能通过更新租约来选举一个新的 leader。当 scheduler 和 controller-manager 通过 127.0.0.1 访问 API 服务，而相同节点上的 API 服务不可用时，这一点相当重要。


 ### 安装配置文件


-首先，在每个节点上创建空白日志文件，这样Docker就会挂载这些文件而不是创建一个新文件夹：
+首先，在每个节点上创建空白日志文件，这样 Docker 就会挂载这些文件而不是创建一个新文件夹：

 ```shell
 touch /var/log/kube-scheduler.log
@@ -199,16 +199,16 @@ touch /var/log/kube-controller-manager.log
 ```


-接下来，在每个节点上配置scheduler和controller manager pods的描述文件。拷贝 [kube-scheduler.yaml](/docs/admin/high-availability/kube-scheduler.yaml) 和 [kube-controller-manager.yaml](/docs/admin/high-availability/kube-controller-manager.yaml) 到`/etc/kubernetes/manifests/` 文件夹。
+接下来，在每个节点上配置 scheduler 和 controller manager pods 的描述文件。拷贝 [kube-scheduler.yaml](/docs/admin/high-availability/kube-scheduler.yaml) 和 [kube-controller-manager.yaml](/docs/admin/high-availability/kube-controller-manager.yaml) 到 `/etc/kubernetes/manifests/` 文件夹。


 ## 结尾


-此时，你已经完成了master组件的配置（耶！），但你还需要添加工作者节点（噗！）。
+此时，你已经完成了 master 组件的配置（耶！），但你还需要添加工作者节点（噗！）。


-如果你有一个现成的集群，你只需要在每个节点上简单的重新配置你的kubeletes连接到负载均衡的endpoint并重启它们。
+如果你有一个现成的集群，你只需要在每个节点上简单的重新配置你的 kubeletes 连接到负载均衡的 endpoint 并重启它们。


-如果你搭建的是一个全新的集群，你将需要在每个工作节点上安装kubelet和kube-proxy，并设置 `--apiserver`指向复制的endpoint。
+如果你搭建的是一个全新的集群，你将需要在每个工作节点上安装 kubelet 和 kube-proxy，并设置 `--apiserver` 指向复制的 endpoint。
--- a/Show More
+++ b/Show More