Merge branch 'master' into fix_15161

Makefile

@@ -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

OWNERS_ALIASES

@@ -46,7 +46,6 @@ aliases:
     - kbarnard10
     - kbhawkey
     - makoscafee
-    - mistyhacks
     - rajakavitha1
     - ryanmcginnis
     - simplytunde
@@ -118,13 +117,13 @@ aliases:
   sig-docs-ja-owners: # Admins for Japanese content
     - cstoku
     - nasa9084
-    - zacharysarah
   sig-docs-ja-reviews: # PR reviews for Japanese content
     - cstoku
     - inductor
     - makocchi-git
     - MasayaAoyama
     - nasa9084
+    - oke-py
   sig-docs-ko-owners: # Admins for Korean content
     - ClaudiaJKang
     - gochist
@@ -179,3 +178,9 @@ aliases:
     - femrtnz
     - jcjesus
     - devlware
+  sig-docs-vi-owners: # Admins for Vietnamese content
+    - ngtuna
+    - truongnh1992
+  sig-docs-vi-reviews: # PR reviews for Vietnamese content
+    - ngtuna
+    - truongnh1992

README-vi.md

@@ -0,0 +1,72 @@
+# Tài liệu Kubernetes
+
+[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website)
+[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
+
+Chào mừng! Kho lưu trữ này chứa tất cả các tài nguyên cần thiết để xây dựng [trang web của Kubernetes và các tài liệu](https://kubernetes.io/). Chúng tôi rất vui vì bạn muốn đóng góp.
+
+## Đóng góp cho tài liệu
+
+Bạn có thể click vào nút **Fork** ở góc trên bên phải màn hình để tạo bản sao của kho lưu trữ này trong tài khoản GitHub của bạn. Bản sao này được gọi là một bản *fork*. Thực hiện bất kì thay đổi nào mà bạn muốn trong bản fork của bạn và khi bạn sẵn sang gửi những thay đổi đó cho chúng tôi, hãy đến bản fork của bạn và tạo một Pull Request mới để cho chúng tôi biết về nó.
+
+Một khi Pull Request của bạn được tạo, reviewer sẽ chịu trách nhiệm cung cấp các phản hồi rõ ràng, có thể thực hiện được. Là chủ sở hữu của pull request, **bạn có trách nhiệm sửa đổi Pull Request của mình để giải quyết các phản hồi bởi reviewer.**  Ngoài ra, lưu ý rằng bạn có thể có nhiều hơn một reviewer cung cấp cho bạn các phản hồi hoặc bạn có thể nhận được phản hồi từ reviewer khác với reviewer ban đầu được chỉ định. Hơn nữa, trong một số trường hợp, một trong những reviewer của bạn có thể yêu cầu đánh giá kỹ thuật từ [Kubernetes tech reviewer](https://github.com/kubernetes/website/wiki/Tech-reviewers) khi cần. Các reviewers sẽ cố gắng hết sức để cung cấp phản hồi một cách kịp thời nhưng thời gian phản hồi có thể thay đổi tùy theo hoàn cảnh.
+
+Để biết thêm thông tin về việc đóng góp cho tài liệu Kubernetes, hãy xem:
+
+* [Bắt đầu đóng góp](https://kubernetes.io/docs/contribute/start/)
+* [Các giai đoạn thay đổi tài liệu](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Sử dụng các trang templates](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [Hướng dẫn biểu mẫu tài liệu](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [Địa phương hóa tài liệu Kubernetes](https://kubernetes.io/docs/contribute/localization/)
+
+
+## Chạy website cục bộ dùng Docker
+
+Cách được đề xuất để chạy trang web Kubernetes cục bộ là dùng [Docker](https://docker.com) image chứa trình tạo web tĩnh [Hugo](https://gohugo.io).
+
+> Nếu bạn làm việc trên môi trường Windows, bạn sẽ cần thêm môt vài công cụ mà bạn có thể cài đặt với [Chocolatey](https://chocolatey.org). `choco install make`
+
+> Nếu bạn không muốn dùng Docker để chạy trang web cục bộ, hãy xem [Chạy website cục bộ dùng Hugo](#Chạy website cục bộ dùng Hugo) dưới đây.
+
+Nếu bạn có Docker đang [up và running](https://www.docker.com/get-started), build `kubernetes-hugo` Docker image cục bộ:
+
+```bash
+make docker-image
+```
+
+Khi image đã được built, bạn có thể chạy website cục bộ:
+
+```bash
+make docker-serve
+```
+
+Mở trình duyệt và đến địa chỉ http://localhost:1313 để xem website. Khi bạn thay đổi các file nguồn, Hugo cập nhật website và buộc làm mới trình duyệt.
+
+## Chạy website cục bộ dùng Hugo
+
+Hãy xem [tài liệu chính thức của Hugo](https://gohugo.io/getting-started/installing/) cho việc hướng dẫn cài đặt Hugo. Đảm bảo cài đặt phiên bản mở rộng của Hugo được xác định bởi biến môi trường `HUGO_VERSION` trong file [`netlify.toml`](netlify.toml#L9)
+
+Để chạy website cục bộ khi Hugo được cài đặt:
+
+```bash
+make serve
+```
+
+Câu lệnh trên sẽ khởi động server Hugo cục bộ trên cổng 1313. Mở trình duyệt và đến địa chỉ http://localhost:1313 để xem website. Khi bạn thay đổi các file nguồn, Hugo cập nhật website và buộc làm mới trình duyệt.
+
+## Cộng đồng, thảo luận, đóng góp và hỗ trợ
+
+Tìm hiểu cách tham gia với cộng đồng Kubernetes trên [trang cộng đồng](http://kubernetes.io/community/).
+
+Bạn có thể tiếp cận những maintainers của dự án này tại:
+
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+### Quy tắc ứng xử
+
+Sự tham gia vào cộng đồng Kubernetes được điểu chỉnh bởi [Kubernetes Code of Conduct](code-of-conduct.md).
+
+## Cảm ơn!
+
+Kubernetes phát triển mạnh mẽ về sự tham gia của cộng đồng và chúng tôi đánh giá cao những đóng góp của bạn cho trang web và tài liệu của chúng tôi!

README.md

@@ -26,7 +26,7 @@ For more information about contributing to the Kubernetes documentation, see:
 |[German README](README-de.md)|[Portuguese README](README-pt.md)|
 |[Hindi README](README-hi.md)|[Spanish README](README-es.md)|
 |[Indonesian README](README-id.md)|[Chinese README](README-zh.md)|
-|[Japanese README](README-ja.md)||
+|[Japanese README](README-ja.md)|[Vietnamese README](README-vi.md)|
 |||
 
 ## Running the website locally using Docker

assets/sass/_base.sass

@@ -70,7 +70,7 @@ section
   background-color: white
 
 section, header, footer
-  main
+  .main-section
     position: relative
     margin: auto
 
@@ -249,7 +249,7 @@ header
     color: $blue
     font-weight: normal
 
-  main
+  .main-section
     white-space: nowrap
     overflow: hidden
     clear: both
@@ -439,7 +439,7 @@ footer
   background-image: url(/images/texture.png)
   background-color: $dark-grey
 
-  main
+  .main-section
     padding: 20px 0
 
   nav
@@ -1121,7 +1121,7 @@ $feature-box-div-margin-bottom: 40px
     margin-bottom: 0
     padding-bottom: 1px
 
-    main
+    .main-section
       padding: 0 10px
       margin-bottom: 30px
 
@@ -1147,7 +1147,7 @@ $feature-box-div-margin-bottom: 40px
   a
     color: $blue
 
-  main
+  .main-section
     margin-bottom: $ocean-nodes-padding-Y
     min-height: 160px
 
@@ -1160,7 +1160,7 @@ $feature-box-div-margin-bottom: 40px
       width: 100%
       max-width: 160px
 
-  main:first-child
+  .main-section:first-child
     .image-wrapper
       max-width: 100%
 
@@ -1356,7 +1356,7 @@ $feature-box-div-margin-bottom: 40px
   #mainContent
     padding: 20px 0
 
-    main
+    .main-section
       max-width: none
 
     a
@@ -1775,7 +1775,7 @@ $feature-box-div-margin-bottom: 40px
 
 #home
   #talkToUs
-    main
+    .main-section
       padding: 30px 0
 
     h5

assets/sass/_desktop.sass

@@ -95,7 +95,7 @@ $video-section-height: 550px
       right: -25px
 
   section, header, footer
-    main
+    .main-section
       max-width: $main-max-width
 
   header, #vendorStrip, #encyclopedia, #hero h1, #hero h5, #docs #hero h1, #docs #hero h5,
@@ -108,11 +108,11 @@ $video-section-height: 550px
 
   #home
     section, header, footer
-      main
+      .main-section
         max-width: 1000px
 
   #oceanNodes
-    main
+    .main-section
       position: relative
       max-width: 830px
 
@@ -172,7 +172,7 @@ $video-section-height: 550px
     background-image: url(../images/texture.png)
     background-color: $dark-grey
 
-    main
+    .main-section
       padding: 20px 0
 
     nav

assets/sass/_size.sass

@@ -26,7 +26,7 @@ section, header, #vendorStrip
   padding-left: $full-width-paddingX
   padding-right: $full-width-paddingX
 
-  main
+  .main-section
     width: $main-width
     max-width: $main-max-width
 
@@ -59,7 +59,7 @@ header
   .nav-box + .nav-box
     margin-left: $nav-box-sibling-margin-left
 
-  main + main
+  .main-secton + .main-section
     margin-top: $main-nav-main-sibling-margin-top
 
   .left .button

assets/sass/_tablet.sass

@@ -116,7 +116,7 @@ $feature-box-div-width: 45%
       text-align: left
       margin-bottom: 18px
 
-    main
+    main, .main-section
       position: relative
       clear: both
       display: table

config.toml

@@ -266,3 +266,10 @@ contentDir = "content/hi"
 [languages.hi.params]
 time_format_blog = "01.02.2006"
 language_alternatives = ["en"]
+
+[languages.vi]
+title = "Kubernetes"
+description = "Production-Grade Container Orchestration"
+languageName = "Vietnamese"
+contentDir = "content/vi"
+weight = 12

content/de/docs/tasks/tools/install-kubectl.md

@@ -261,7 +261,7 @@ Sie können kubectl als Teil des Google Cloud SDK installieren.
 
 ## kubectl konfigurieren
 
-Damit kubectl einen Kubernetes-Cluster finden und darauf zugreifen kann, benötigt es eine [kubeconfig Datei](/docs/tasks/access-application-cluster/configure-access-multiple-clusters/). Diese wird automatisch erstellt, wenn Sie einen Cluster mit kube-up.sh erstellen oder einen Minikube-Cluster erfolgreich implementieren. Weitere Informationen zum Erstellen von Clustern finden Sie in den [Anleitungen für die ersten Schritte](/docs/setup/). Wenn Sie Zugriff auf einen Cluster benötigen, den Sie nicht erstellt haben, lesen Sie die [Cluster-Zugriff freigeben Dokumentation](/docs/tasks/access-application-cluster/configure-access-multiple-clusters/).
+Damit kubectl einen Kubernetes-Cluster finden und darauf zugreifen kann, benötigt es eine [kubeconfig Datei](/docs/tasks/access-application-cluster/configure-access-multiple-clusters/). Diese wird automatisch erstellt, wenn Sie einen Cluster mit [kube-up.sh](https://github.com/kubernetes/kubernetes/blob/master/cluster/kube-up.sh)  erstellen oder einen Minikube-Cluster erfolgreich implementieren. Weitere Informationen zum Erstellen von Clustern finden Sie in den [Anleitungen für die ersten Schritte](/docs/setup/). Wenn Sie Zugriff auf einen Cluster benötigen, den Sie nicht erstellt haben, lesen Sie die [Cluster-Zugriff freigeben Dokumentation](/docs/tasks/access-application-cluster/configure-access-multiple-clusters/).
 Die kubectl-Konfiguration befindet sich standardmäßig unter `~/.kube/config`.
 
 ## Überprüfen der kubectl-Konfiguration

content/en/blog/_posts/2015-07-00-The-Growing-Kubernetes-Ecosystem.md

@@ -95,7 +95,7 @@ Mesosphere has incorporated Kubernetes into its Data Center Operating System (DC
 
  |
 
-[Platalytics, Inc][24]. and announced the release of one-touch deploy-anywhere feature for its Spark Application Platform. Based on Kubernetes, Docker, and CoreOS, it allows simple and automated deployment of Apache Hadoop, Spark, and Platalytics platform, with a single click, to all major public clouds, including Google, Amazon, Azure, Digital Ocean, and private on-premise clouds. It also enables hybrid cloud scenarios, where resources on public and private clouds can be mixed.
+[Platalytics, Inc][24]. and announced the release of one-touch deploy-anywhere feature for its Spark Application Platform. Based on Kubernetes, Docker, and CoreOS, it allows simple and automated deployment of Apache Hadoop, Spark, and Platalytics platform, with a single click, to all major public clouds, including Google, Amazon, Azure, DigitalOcean, and private on-premise clouds. It also enables hybrid cloud scenarios, where resources on public and private clouds can be mixed.
 
  |  
 |

content/en/blog/_posts/2016-03-00-Building-Highly-Available-Applications-Using-Kubernetes-New-Multi-Zone-Clusters-aka-Ubernetes-Lite.md

@@ -2,7 +2,7 @@
 title: " Building highly available applications using Kubernetes new multi-zone clusters (a.k.a. 'Ubernetes Lite') "
 date: 2016-03-29
 slug: building-highly-available-applications-using-kubernetes-new-multi-zone-clusters-a.k.a-ubernetes-lite
-url: /blog/2016/03/Building-Highly-Available-Applications-Using-Kubernetes-New-Multi-Zone-Clusters-A.K.A-Ubernetes-Lite
+url: /blog/2016/03/Building-Highly-Available-Applications-Using-Kubernetes-New-Multi-Zone-Clusters-aka-Ubernetes-Lite
 ---
 _Editor's note: this is the third post in a [series of in-depth posts](https://kubernetes.io/blog/2016/03/five-days-of-kubernetes-12) on what's new in Kubernetes 1.2_  
 

content/en/blog/_posts/2016-03-00-Kubernetes-1-2-And-Simplifying-Advanced-Networking-With-Ingress.md

@@ -2,7 +2,7 @@
 title: " Kubernetes 1.2 and simplifying advanced networking with Ingress "
 date: 2016-03-31
 slug: kubernetes-1.2-and-simplifying-advanced-networking-with-ingress
-url: /blog/2016/03/Kubernetes-1.2-And-Simplifying-Advanced-Networking-With-Ingress
+url: /blog/2016/03/Kubernetes-1-2-And-Simplifying-Advanced-Networking-With-Ingress
 ---
 _Editor's note: This is the sixth post in a [series of in-depth posts](https://kubernetes.io/blog/2016/03/five-days-of-kubernetes-12) on what's new in Kubernetes 1.2._  
 _Ingress is currently in beta and under active development._  

content/en/blog/_posts/2016-03-00-Kubernetes-1-2-Even-More-Performance-Upgrades-Plus-Easier-Application-Deployment-And-Management-.md

@@ -2,7 +2,7 @@
 title: " Kubernetes 1.2: Even more performance upgrades, plus easier application deployment and management  "
 date: 2016-03-17
 slug: kubernetes-1.2-even-more-performance-upgrades-plus-easier-application-deployment-and-management
-url: /blog/2016/03/Kubernetes-1.2-Even-More-Performance-Upgrades-Plus-Easier-Application-Deployment-And-Management
+url: /blog/2016/03/Kubernetes-1-2-Even-More-Performance-Upgrades-Plus-Easier-Application-Deployment-And-Management
 ---
 Today we released Kubernetes 1.2. This release represents significant improvements for large organizations building distributed systems. Now with over 680 unique contributors to the project, this release represents our largest yet.  
 

content/en/blog/_posts/2016-07-00-Five-Days-Of-Kubernetes-1-3.md

@@ -2,7 +2,7 @@
 title: " Five Days of Kubernetes 1.3 "
 date: 2016-07-11
 slug: five-days-of-kubernetes-1.3
-url: /blog/2016/07/Five-Days-Of-Kubernetes-1.3
+url: /blog/2016/07/Five-Days-Of-Kubernetes-1-3
 ---
 Last week we [released Kubernetes 1.3](https://kubernetes.io/blog/2016/07/kubernetes-1.3-bridging-cloud-native-and-enterprise-workloads), two years from the day when the first Kubernetes commit was pushed to GitHub. Now 30,000+ commits later from over 800 contributors, this 1.3 releases is jam packed with updates driven by feedback from users.  
 

content/en/blog/_posts/2016-07-00-Kubernetes-1-3-Bridging-Cloud-Native-And-Enterprise-Workloads.md

@@ -2,7 +2,7 @@
 title: " Kubernetes 1.3: Bridging Cloud Native and Enterprise Workloads "
 date: 2016-07-06
 slug: kubernetes-1.3-bridging-cloud-native-and-enterprise-workloads
-url: /blog/2016/07/Kubernetes-1.3-Bridging-Cloud-Native-And-Enterprise-Workloads
+url: /blog/2016/07/Kubernetes-1-3-Bridging-Cloud-Native-And-Enterprise-Workloads
 ---
 Nearly two years ago, when we officially kicked off the Kubernetes project, we wanted to simplify distributed systems management and provide the core technology required to everyone. The community’s response to this effort has blown us away. Today, thousands of customers, partners and developers are running clusters in production using Kubernetes and have joined the cloud native revolution.   
 

content/en/blog/_posts/2016-09-00-Kubernetes-1-4-Making-It-Easy-To-Run-On-Kuberentes-Anywhere.md

@@ -2,7 +2,7 @@
 title: " Kubernetes 1.4: Making it easy to run on Kubernetes anywhere "
 date: 2016-09-26
 slug: kubernetes-1.4-making-it-easy-to-run-on-kuberentes-anywhere
-url: /blog/2016/09/Kubernetes-1.4-Making-It-Easy-To-Run-On-Kuberentes-Anywhere
+url: /blog/2016/09/Kubernetes-1-4-Making-It-Easy-To-Run-On-Kuberentes-Anywhere
 ---
 Today we’re happy to announce the release of Kubernetes 1.4.  
 

content/en/blog/_posts/2016-10-00-Production-Kubernetes-Dashboard-UI-1-4-improvements_3.md

@@ -2,7 +2,7 @@
 title: " How we improved Kubernetes Dashboard UI in 1.4 for your production needs​ "
 date: 2016-10-03
 slug: production-kubernetes-dashboard-ui-1.4-improvements_3
-url: /blog/2016/10/Production-Kubernetes-Dashboard-UI-1.4-improvements_3
+url: /blog/2016/10/Production-Kubernetes-Dashboard-UI-1-4-improvements_3
 ---
 With the release of [Kubernetes 1.4](https://kubernetes.io/blog/2016/09/kubernetes-1.4-making-it-easy-to-run-on-kuberentes-anywhere) last week, Dashboard – the official web UI for Kubernetes – has a number of exciting updates and improvements of its own. The past three months have been busy ones for the Dashboard team, and we’re excited to share the resulting features of that effort here. If you’re not familiar with Dashboard, the [GitHub repo](https://github.com/kubernetes/dashboard#kubernetes-dashboard) is a great place to get started.  
 

content/en/blog/_posts/2016-12-00-Cluster-Federation-In-Kubernetes-1-5.md

@@ -2,7 +2,7 @@
 title: " Cluster Federation in Kubernetes 1.5 "
 date: 2016-12-22
 slug: cluster-federation-in-kubernetes-1.5
-url: /blog/2016/12/Cluster-Federation-In-Kubernetes-1.5
+url: /blog/2016/12/Cluster-Federation-In-Kubernetes-1-5
 ---
 _Editor’s note: this post is part of a [series of in-depth articles](https://kubernetes.io/blog/2016/12/five-days-of-kubernetes-1.5) on what's new in Kubernetes 1.5_  
 

content/en/blog/_posts/2016-12-00-Five-Days-Of-Kubernetes-1-5.md

@@ -2,7 +2,7 @@
 title: " Five Days of Kubernetes 1.5 "
 date: 2016-12-19
 slug: five-days-of-kubernetes-1.5
-url: /blog/2016/12/Five-Days-Of-Kubernetes-1.5
+url: /blog/2016/12/Five-Days-Of-Kubernetes-1-5
 ---
 With the help of our growing community of 1,000 contributors, we pushed some 5,000 commits to extend support for production workloads and deliver [Kubernetes 1.5](https://kubernetes.io/blog/2016/12/kubernetes-1.5-supporting-production-workloads). While many improvements and new features have been added, we selected few to highlight in a series of in-depths posts listed below.   
 

content/en/blog/_posts/2016-12-00-Kubernetes-1-5-Supporting-Production-Workloads.md

@@ -2,7 +2,7 @@
 title: " Kubernetes 1.5: Supporting Production Workloads "
 date: 2016-12-13
 slug: kubernetes-1.5-supporting-production-workloads
-url: /blog/2016/12/Kubernetes-1.5-Supporting-Production-Workloads
+url: /blog/2016/12/Kubernetes-1-5-Supporting-Production-Workloads
 ---
 
 Today we’re announcing the release of Kubernetes 1.5. This release follows close on the heels of KubeCon/CloundNativeCon, where users gathered to share how they’re running their applications on Kubernetes. Many of you expressed interest in running stateful applications in containers with the eventual goal of running all applications on Kubernetes. If you have been waiting to try running a distributed database on Kubernetes, or for ways to guarantee application disruption SLOs for stateful and stateless apps, this release has solutions for you.   

content/en/blog/_posts/2017-03-00-Five-Days-Of-Kubernetes-1-6.md

@@ -2,7 +2,7 @@
 title: " Five Days of Kubernetes 1.6 "
 date: 2017-03-29
 slug: five-days-of-kubernetes-1.6
-url: /blog/2017/03/Five-Days-Of-Kubernetes-1.6
+url: /blog/2017/03/Five-Days-Of-Kubernetes-1-6
 ---
 
 With the help of our growing community of 1,110 plus contributors, we pushed around 5,000 commits to deliver [Kubernetes 1.6](https://kubernetes.io/blog/2017/03/kubernetes-1.6-multi-user-multi-workloads-at-scale), bringing focus on multi-user, multi-workloads at scale. While many improvements have been contributed, we selected few features to highlight in a series of in-depths posts listed below.   

content/en/blog/_posts/2017-03-00-Kubernetes-1-6-Multi-User-Multi-Workloads-At-Scale.md

@@ -2,7 +2,7 @@
 title: " Kubernetes 1.6: Multi-user, Multi-workloads at Scale "
 date: 2017-03-28
 slug: kubernetes-1.6-multi-user-multi-workloads-at-scale
-url: /blog/2017/03/Kubernetes-1.6-Multi-User-Multi-Workloads-At-Scale
+url: /blog/2017/03/Kubernetes-1-6-Multi-User-Multi-Workloads-At-Scale
 ---
 Today we’re announcing the release of Kubernetes 1.6.  
 

content/en/blog/_posts/2017-03-00-Scalability-Updates-In-Kubernetes-1-6.md

@@ -2,7 +2,7 @@
 title: " Scalability updates in Kubernetes 1.6: 5,000 node and 150,000 pod clusters "
 date: 2017-03-30
 slug: scalability-updates-in-kubernetes-1.6
-url: /blog/2017/03/Scalability-Updates-In-Kubernetes-1.6
+url: /blog/2017/03/Scalability-Updates-In-Kubernetes-1-6
 ---
 _Editor’s note: this post is part of a [series of in-depth articles](https://kubernetes.io/blog/2017/03/five-days-of-kubernetes-1.6) on what's new in Kubernetes 1.6_