kubernetes-retired · gochist · Sep 2, 2018 · Jul 17, 2018 · Jul 17, 2018 · Jul 17, 2018
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
@@ -1,4 +1,5 @@
 <!-- Thanks for filing an issue! Before submitting, please fill in the following information. -->
+<!-- See https://kubernetes.io/docs/contribute/start/ for guidance on writing an actionable issue description. -->
 
 <!--Required Information-->
 

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,6 +1,9 @@
 >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+> Please delete this note before submitting the pull request.
 > For 1.12 Features: set Milestone to 1.12 and Base Branch to release-1.12
+> Help editing and submitting pull requests:  https://deploy-preview-9510--kubernetes-io-master-staging.netlify.com/docs/contribute/start/#submit-a-pull-request.
+> Help choosing which branch to use, see
+> https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use.
 >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 >
-> Please delete this note before submitting the pull request.
 
diff --git a/Dockerfile b/Dockerfile
@@ -18,7 +18,9 @@ ARG HUGO_VERSION
 
 RUN mkdir -p /usr/local/src && \
     cd /usr/local/src && \
-    curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_${HUGO_VERSION}_linux-64bit.tar.gz | tar -xz && \
+    curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_linux-64bit.tar.gz | tar -xz && \
+    apk add build-base && \
+    apk add libc6-compat && \
     mv hugo /usr/local/bin/hugo && \
     curl -L https://bin.equinox.io/c/dhgbqpS8Bvy/minify-stable-linux-amd64.tgz | tar -xz && \
     mv minify /usr/local/bin && \

diff --git a/OWNERS_ALIASES b/OWNERS_ALIASES
@@ -41,9 +41,11 @@ aliases:
     - chrislovecnm
     - mfburnett
   sig-azure: #Microsoft Azure
-    - slack
-    - colemickens
-    - jdumars
+    - andyzhangx
+    - feiskyer
+    - justaugustus
+    - karataliu
+    - khenidak
   sig-big-data: #GH: sig-big-data-pr-reviews
     - foxish
   sig-cli: #Team: CLI; GH: sig-cli-pr-reviews; e.g. kubectl

diff --git a/README.md b/README.md
@@ -8,13 +8,10 @@ Once your pull request is created, a Kubernetes reviewer will take responsibilit
 
 For more information about contributing to the Kubernetes documentation, see:
 
-* [Contributing to the Kubernetes Documentation](http://kubernetes.io/editdocs/)
-* [Creating a Documentation Pull Request](http://kubernetes.io/docs/home/contribute/create-pull-request/)
-* [Writing a New Topic](http://kubernetes.io/docs/home/contribute/write-new-topic/)
-* [Review Issues](http://kubernetes.io/docs/home/contribute/review-issues/)
-* [Staging Your Documentation Changes](http://kubernetes.io/docs/home/contribute/stage-documentation-changes/)
-* [Using Page Templates](http://kubernetes.io/docs/home/contribute/page-templates/)
-* [Documentation Style Guide](http://kubernetes.io/docs/home/contribute/style-guide/)
+* [Start contributing](https://kubernetes.io/docs/contribute/start/)
+* [Staging Your Documentation Changes](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Using Page Templates](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [Documentation Style Guide](http://kubernetes.io/docs/contribute/style/style-guide/)
 
 ## Building the site using Docker
 
@@ -33,7 +30,7 @@ You can create an image for a different version of Hugo by changing the value of
 Once the `kubernetes-hugo` image has been built locally, you can build the site:
 
 ```bash
-make stage
+make docker-serve
 
 # The underlying command:
 docker run \

diff --git a/assets/sass/_base.sass b/assets/sass/_base.sass
@@ -1238,8 +1238,15 @@ $feature-box-div-margin-bottom: 40px
 		&:hover
 			border-color: white
 
-
-
+// CNCF
+#cncf
+	padding-top: 60px
+	padding-bottom: 140px
+	background-color: $light-grey
+	background-image: url(/images/cncf-color.png)
+	background-position: center 100px
+	background-repeat: no-repeat
+	background-size: 300px
 
 // Features
 #features
@@ -1768,3 +1775,37 @@ $feature-box-div-margin-bottom: 40px
 
 .gsc-above-wrapper-area
 	border-bottom: 0;
+
+
+
+/* Bing Search */
+#bing-results-container
+    margin-top: 30px
+    margin-left: 20px
+
+.bing-result
+    margin-bottom: 20px
+
+.bing-result-name a
+    font-size: 16px
+    color: #0000CC
+
+
+.bing-result-url
+    color: #008000
+    font-size: 13px
+
+.bing-result-snippet
+    color: #000
+    font-size: 11px
+
+#bing-pagination-container
+	margin: 10px
+	margin-left: 20px
+
+.bing-page-anchor
+    text-decoration: none!important
+    cursor: pointer
+    color: #0000CC
+    margin-right: 8px
+
diff --git a/config.toml b/config.toml
@@ -139,3 +139,5 @@ description = "Production-Grade Container Orchestration"
 languageName = "Korean"
 weight = 3
 contentDir = "content/ko"
+
+
diff --git a/content/cn/docs/tasks/access-application-cluster/connecting-frontend-backend.md b/content/cn/docs/tasks/access-application-cluster/connecting-frontend-backend.md
@@ -34,7 +34,7 @@ content_template: templates/tutorial
 
 * 本任务使用 [外部负载均衡服务](/docs/tasks/access-application-cluster/create-external-load-balancer/)，
   所以需要对应的可支持此功能的环境。如果你的环境不能支持，你可以使用
-  [NodePort](/docs/user-guide/services/#type-nodeport) 类型的服务代替。
+  [NodePort](/docs/user-guide/services/#nodeport) 类型的服务代替。
 
 {{% /capture %}}
 

diff --git a/content/cn/docs/tutorials/services/source-ip.md b/content/cn/docs/tutorials/services/source-ip.md
@@ -116,7 +116,7 @@ command=GET
 ## Type=NodePort 类型 Services 的 Source IP
 
 
-对于 Kubernetes 1.5，发送给类型为 [Type=NodePort](/docs/user-guide/services/#type-nodeport) Services 的数据包默认进行源地址 NAT。你可以创建一个 `NodePort` Service 来进行测试：
+对于 Kubernetes 1.5，发送给类型为 [Type=NodePort](/docs/user-guide/services/#nodeport) Services 的数据包默认进行源地址 NAT。你可以创建一个 `NodePort` Service 来进行测试：
 
 ```console
 $ kubectl expose deployment source-ip-app --name=nodeport --port=80 --target-port=8080 --type=NodePort
@@ -210,7 +210,7 @@ client_address=104.132.1.79
 ## Type=LoadBalancer 类型 Services 的 Source IP
 
 
-对于 Kubernetes 1.5，发送给类型为 [Type=LoadBalancer](/docs/user-guide/services/#type-nodeport) Services 的数据包默认进行源地址 NAT，这是由于所有处于 `Ready` 状态的 Kubernetes 节点对于负载均衡的流量都是符合条件的。所以如果数据包到达一个没有 endpoint 的节点，系统将把这个包代理到*有* endpoint 的节点，并替换数据包的源 IP 为节点的 IP（如前面章节所述）。
+对于 Kubernetes 1.5，发送给类型为 [Type=LoadBalancer](/docs/user-guide/services/#nodeport) Services 的数据包默认进行源地址 NAT，这是由于所有处于 `Ready` 状态的 Kubernetes 节点对于负载均衡的流量都是符合条件的。所以如果数据包到达一个没有 endpoint 的节点，系统将把这个包代理到*有* endpoint 的节点，并替换数据包的源 IP 为节点的 IP（如前面章节所述）。
 
 
 你可以通过在一个 loadbalancer 上暴露这个 source-ip-app 来进行测试。

diff --git a/...ent/cn/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md b/...ent/cn/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md
@@ -15,7 +15,7 @@ approvers:
 
 * [Persistent Volumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) 定义持久化磁盘（磁盘生命周期不和 Pods 绑定）。
 * [Services](https://kubernetes.io/docs/concepts/services-networking/service/) 使得 Pods 能够找到其它 Pods。
-* [External Load Balancers](https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer) 对外暴露 Services。
+* [External Load Balancers](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer) 对外暴露 Services。
 * [Deployments](http://kubernetes.io/docs/user-guide/deployments/) 确保 Pods 持续运行。
 * [Secrets](http://kubernetes.io/docs/user-guide/secrets/) 保存敏感密码信息。
 
@@ -66,7 +66,7 @@ kubectl create -f https://raw.githubusercontent.com/kubernetes/examples/master/m
 Kubernetes本质是模块化的，可以在各种环境中运行。但并不是所有集群都相同。此处是本示例的一些要求：
 * 需要 1.2 版本以上的 Kubernetes，以使用更新的特性，例如 PV Claims 和 Deployments。运行 `kubectl version` 来查看你的集群版本。
 * [Cluster DNS](https://github.com/kubernetes/dns) 将被用于服务发现。
-* 一个 [external load balancer](https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer) 将被用于接入 WordPress。
+* 一个 [external load balancer](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer) 将被用于接入 WordPress。
 * 使用了 [Persistent Volume Claims](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims)。你必须创建集群中需要的 Persistent Volumes。本示例将展示两种类型的 volume 的创建方法，但是任何类型的 volume 都是足够使用的。
 
 

diff --git a/content/en/_index.html b/content/en/_index.html
@@ -48,7 +48,7 @@ <h2>The Challenges of Migrating 150+ Microservices to Kubernetes</h2>
         <br>
         <br>
         <br>
-        <a href="https://www.lfasiallc.com/events/kubecon-cloudnativecon-china-2018/" button id= "desktopKCButton">Attend KubeCon in Shanghai on Nov. 14-15, 2018</a>
+        <a href="https://www.lfasiallc.com/events/kubecon-cloudnativecon-china-2018/" button id= "desktopKCButton">Attend KubeCon in Shanghai on Nov. 13-15, 2018</a>
         <br>
         <br>
         <br>
@@ -122,23 +122,23 @@ <h4><a href="/docs/concepts/workloads/controllers/jobs-run-to-completion/">Batch
         <h3>Case Studies</h3>
         <div id="caseStudiesWrapper">
           <div>
-              <p>Pinning Its Past, Present, and Future on Cloud Native</p>
-              <a href="/case-studies/pinterest">Read more</a>
+              <p>Sling TV: Marrying Kubernetes and AI to Enable Proper Web Scale</p>
+              <a href="/case-studies/slingtv">Read more</a>
           </div>
           <div>
-              <p>Reinventing the World’s Largest Education Company With Kubernetes</p>
-              <a href="/case-studies/pearson">Read more</a>
+              <p>Using OpenTracing to Help Pinpoint the Bottlenecks</p>
+              <a href="/case-studies/workiva">Read more</a>
           </div>
-         
+
           <div>
-              <p>Supporting Fast Decisioning Applications with Kubernetes</p>
-              <a href="/case-studies/capital-one">Read more</a>
+              <p>Pinning Its Past, Present, and Future on Cloud Native</p>
+              <a href="/case-studies/pinterest">Read more</a>
           </div>
           <div>
-              <p>Driving Banking Innovation with Cloud Native</p>
-              <a href="/case-studies/ing">Read more</a>
+              <p>Reinventing the World’s Largest Education Company With Kubernetes</p>
+              <a href="/case-studies/pearson">Read more</a>
           </div>
-        
+
         </div>
 
         <!--<div id="bigSocial">-->
@@ -169,7 +169,7 @@ <h5 style="text-align: center"><a href="/case-studies/" style="color: #3371E3; f
         <section id="cncf">
             <main>
         <center>
-        <p>We are a <a href="https://cncf.io/">CNCF</a> graduated project</p>
+        <p style="font-size: 20px">We are a <a href="https://cncf.io/">CNCF</a> graduated project</p>
         </center>
       </main>
   </section>

diff --git a/content/en/blog/_posts/2018-06-26-kubernetes-1.11-release-announcement.md b/content/en/blog/_posts/2018-06-26-kubernetes-1.11-release-announcement.md
@@ -60,7 +60,7 @@ If you’re interested in exploring these features more in depth, check back in
 * Day 1: [IPVS-Based In-Cluster Service Load Balancing Graduates to General Availability](/blog/2018/07/09/ipvs-based-in-cluster-load-balancing-deep-dive/)
 * Day 2: [CoreDNS Promoted to General Availability](/blog/2018/07/10/coredns-ga-for-kubernetes-cluster-dns/)
 * Day 3: [Dynamic Kubelet Configuration Moves to Beta](/blog/2018/07/11/dynamic-kubelet-configuration/)
-* Day 4: [Resizing Persistent Volumes using Kubernetes](/blog/2018/07/11/resizing-persistent-volumes-using-kubernetes/)
+* Day 4: [Resizing Persistent Volumes using Kubernetes](/blog/2018/07/12/resizing-persistent-volumes-using-kubernetes/)
 
 ## Release team
 

diff --git a/content/en/blog/_posts/2018-08-02-dynamically-expand-volume-csi.md b/content/en/blog/_posts/2018-08-02-dynamically-expand-volume-csi.md
@@ -0,0 +1,161 @@
+---
+layout: blog
+title:  'Dynamically Expand Volume with CSI and Kubernetes'
+date:   2018-08-02
+---
+
+**Author**: Orain Xiong (Co-Founder, WoquTech)
+
+_There is a very powerful storage subsystem within Kubernetes itself, covering a fairly broad spectrum of use cases. Whereas, when planning to build a product-grade relational database platform with Kubernetes, we face a big challenge: coming up with storage. This article describes how to extend latest Container Storage Interface 0.2.0 and integrate with Kubernetes, and demonstrates the essential facet of dynamically expanding volume capacity._
+
+## Introduction
+
+As we focalize our customers, especially in financial space, there is a huge upswell in the adoption of container orchestration technology.
+
+They are looking forward to open source solutions to redesign already existing monolithic applications, which have been running for several years on virtualization infrastructure or bare metal.
+
+Considering extensibility and the extent of technical maturity, Kubernetes and Docker are at the very top of the list. But migrating monolithic applications to a distributed orchestration like Kubernetes is challenging, the relational database is critical for the migration.
+
+With respect to the relational database, we should pay attention to storage. There is a very powerful storage subsystem within Kubernetes itself. It is very useful and covers a fairly broad spectrum of use cases. When planning to run a relational database with Kubernetes in production, we face a big challenge: coming up with storage. There are still some fundamental functionalities which are left unimplemented. Specifically, dynamically expanding volume. It sounds boring but is highly required, except for actions like create and delete and mount and unmount.
+
+Currently, expanding volume is only available with those storage provisioners:
+
+* gcePersistentDisk
+* awsElasticBlockStore
+* OpenStack Cinder
+* glusterfs
+* rbd
+
+In order to enable this feature, we should set feature gate `ExpandPersistentVolumes` true and turn on the `PersistentVolumeClaimResize` admission plugin. Once `PersistentVolumeClaimResize` has been enabled, resizing will be allowed by a Storage Class whose `allowVolumeExpansion` field is set to true.
+
+Unfortunately, dynamically expanding volume through the Container Storage Interface (CSI) and Kubernetes is unavailable, even though the underlying storage providers have this feature.
+
+This article will give a simplified view of CSI, followed by a walkthrough of how to introduce a new expanding volume feature on the existing CSI and Kubernetes. Finally, the article will demonstrate how to dynamically expand volume capacity.
+
+## Container Storage Interface (CSI)
+
+To have a better understanding of what we're going to do, the first thing we need to know is what the Container Storage Interface is. Currently, there are still some problems for already existing storage subsystem within Kubernetes. Storage driver code is maintained in the Kubernetes core repository which is difficult to test. But beyond that, Kubernetes needs to give permissions to storage vendors to check code into the Kubernetes core repository. Ideally, that should be implemented externally.
+
+CSI is designed to define an industry standard that will enable storage providers who enable CSI to be available across container orchestration systems that support CSI.
+
+This diagram depicts a kind of high-level Kubernetes archetypes integrated with CSI:
+
+![csi diagram](/images/blog/2018-08-02-dynamically-expand-volume-csi/csi-diagram.png)
+
+* Three new external components are introduced to decouple Kubernetes and Storage Provider logic
+* Blue arrows present the conventional way to call against API Server
+* Red arrows present gRPC to call against Volume Driver
+
+For more details, please visit: https://github.com/container-storage-interface/spec/blob/master/spec.md
+
+## Extend CSI and Kubernetes
+
+In order to enable the feature of expanding volume atop Kubernetes, we should extend several components including CSI specification, “in-tree” volume plugin, external-provisioner and external-attacher.
+
+## Extend CSI spec
+
+The feature of expanding volume is still undefined in latest CSI 0.2.0. The new 3 RPCs, including `RequiresFSResize` and `ControllerResizeVolume` and `NodeResizeVolume`, should be introduced.
+
+```
+service Controller {
+ rpc CreateVolume (CreateVolumeRequest)
+   returns (CreateVolumeResponse) {}
+……
+ rpc RequiresFSResize (RequiresFSResizeRequest)
+   returns (RequiresFSResizeResponse) {}
+ rpc ControllerResizeVolume (ControllerResizeVolumeRequest)
+   returns (ControllerResizeVolumeResponse) {}
+}
+
+service Node {
+ rpc NodeStageVolume (NodeStageVolumeRequest)
+   returns (NodeStageVolumeResponse) {}
+……
+ rpc NodeResizeVolume (NodeResizeVolumeRequest)
+   returns (NodeResizeVolumeResponse) {}
+}
+```
+
+## Extend “In-Tree” Volume Plugin
+
+In addition to the extend CSI specification, the `csiPlugin` interface within Kubernetes should also implement `expandablePlugin`. The `csiPlugin` interface will expand `PersistentVolumeClaim` representing for `ExpanderController`.
+
+
+```go
+type ExpandableVolumePlugin interface {
+VolumePlugin
+ExpandVolumeDevice(spec Spec, newSize resource.Quantity, oldSize resource.Quantity) (resource.Quantity, error)
+RequiresFSResize() bool
+}
+```
+
+### Implement Volume Driver
+
+Finally, to abstract complexity of the implementation, we should hard code the separate storage provider management logic into the following functions which is well-defined in the CSI specification:
+
+* CreateVolume
+* DeleteVolume
+* ControllerPublishVolume
+* ControllerUnpublishVolume
+* ValidateVolumeCapabilities
+* ListVolumes
+* GetCapacity
+* ControllerGetCapabilities
+* RequiresFSResize
+* ControllerResizeVolume
+
+## Demonstration
+
+Let’s demonstrate this feature with a concrete user case.
+
+* Create storage class for CSI storage provisioner
+
+```yaml
+allowVolumeExpansion: true
+apiVersion: storage.k8s.io/v1
+kind: StorageClass
+metadata:
+  name: csi-qcfs
+parameters:
+  csiProvisionerSecretName: orain-test
+  csiProvisionerSecretNamespace: default
+provisioner: csi-qcfsplugin
+reclaimPolicy: Delete
+volumeBindingMode: Immediate
+```
+
+* Deploy CSI Volume Driver including storage provisioner `csi-qcfsplugin` across Kubernetes cluster
+
+* Create PVC `qcfs-pvc` which will be dynamically provisioned by storage class `csi-qcfs`
+
+```yaml
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: qcfs-pvc
+  namespace: default
+....
+spec:
+  accessModes:
+  - ReadWriteOnce
+  resources:
+    requests:
+      storage: 300Gi
+  storageClassName: csi-qcfs
+```
+
+* Create MySQL 5.7 instance to use PVC `qcfs-pvc`
+* In order to mirror the exact same production-level scenario, there are actually two different types of workloads including:
+    * Batch insert to make MySQL consuming more file system capacity
+    * Surge query request
+* Dynamically expand volume capacity through edit pvc `qcfs-pvc` configuration
+
+The Prometheus and Grafana integration allows us to visualize corresponding critical metrics.
+
+![prometheus grafana](/images/blog/2018-08-02-dynamically-expand-volume-csi/prometheus-grafana.png)
+
+We notice that the middle reading shows MySQL datafile size increasing slowly during bulk inserting. At the same time, the bottom reading shows file system expanding twice in about 20 minutes, from 300 GiB to 400 GiB and then 500 GiB. Meanwhile, the upper reading shows the whole process of expanding volume immediately completes and hardly impacts MySQL QPS.
+
+## Conclusion
+
+Regardless of whatever infrastructure applications have been running on, the database is always a critical resource. It is essential to have a more advanced storage subsystem out there to fully support database requirements. This will help drive the more broad adoption of cloud native technology.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -139,3 +139,5 @@ description = "Production-Grade Container Orchestration"
		languageName = "Korean"
		weight = 3
		contentDir = "content/ko"