Updating blog approvers (#18041)

* Updating approves

* Update OWNERS_ALIASES

.dockerignore

@@ -0,0 +1 @@
+**

.editorconfig

@@ -0,0 +1,17 @@
+[*]
+end_of_line = lf
+insert_final_newline = false
+charset = utf-8
+max_line_length = 80
+trim_trailing_whitespace = true
+
+[*.{html,js,json,sass,md,mmark,toml,yaml}]
+indent_style = space
+indent_size = 2
+
+[*.{sh}]
+indent_style = space
+indent_size = 4
+
+[Makefile]
+indent_style = tab

.github/ISSUE_TEMPLATE.md

@@ -1,22 +0,0 @@
-<!-- Thanks for filing an issue! Before submitting, please fill in the following information. -->
-
-<!--Required Information-->
-
-**This is a...** 
-<!-- choose one by changing [ ] to [x] -->
-- [ ] Feature Request
-- [ ] Bug Report
-
-**Problem:**
-
-
-**Proposed Solution:**
-
-
-**Page to Update:**
-http://kubernetes.io/...
-
-<!--Optional Information (remove the comment tags around information you would like to include)-->
-<!--Kubernetes Version:-->
-
-<!--Additional Information:-->

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,23 @@
+---
+name: Bug Report
+about: Report a bug encountered with Kubernetes Website
+labels:
+- kind/bug
+---
+**This is a Bug Report**
+
+<!-- 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-->
+**Problem:**
+
+**Proposed Solution:**
+
+**Page to Update:**
+https://kubernetes.io/...
+
+<!--Optional Information (remove the comment tags around information you would like to include)-->
+<!--Kubernetes Version:-->
+
+<!--Additional Information:-->

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,18 @@
+---
+name: Feature Request
+about: Suggest a/an feature/enhancement to the Kubernetes Website project
+labels:
+- kind/feature
+---
+**This is a Feature Request**
+
+<!-- Please only use this template for submitting feature/enhancement requests -->
+<!-- See https://kubernetes.io/docs/contribute/start/ for guidance on writing an actionable issue description. -->
+
+**What would you like to be added**
+<!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. -->
+
+**Why is this needed**
+
+**Comments**
+<!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). -->

.github/ISSUE_TEMPLATE/support.md

@@ -0,0 +1,19 @@
+---
+name: Support Request
+about: Support request or question relating to Kubernetes Website project
+labels:
+- triage/support
+---
+**This is Support**
+
+<!--
+STOP -- PLEASE READ!
+
+GitHub is not the right place for support requests.
+
+If you're looking for help, check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes)
+
+You can also post your question on the [Kubernetes Slack](http://slack.k8s.io/) or the [Discuss Kubernetes](https://discuss.kubernetes.io/) forum.
+
+If the matter is security related, please disclose it privately via https://kubernetes.io/security/.
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,7 +1,17 @@
-> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-> For 1.7 Features: set Milestone to `1.7` and Base Branch to `release-1.7`
-> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+> Remember to delete this note before submitting your pull request.
+>
+> For pull requests on 1.17 Features: set Milestone to 1.17 and Base Branch to dev-1.17
+>
+> For pull requests on Chinese localization, set Base Branch to release-1.16
+> Feel free to ask questions in #kubernetes-docs-zh
+>
+> For pull requests on Korean Localization: set Base Branch to dev-1.16-ko.\<latest team milestone>
+>
+> If you need Help on editing and submitting pull requests, visit:
+> https://kubernetes.io/docs/contribute/start/#improve-existing-content.
+>
+> If you need Help on choosing which branch to use, visit:
+> https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use.
+>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 >
-> NOTE: Please check the “Allow edits from maintainers” box below to allow 
-> reviewers fix problems on your patch and speed up the review process.
-> Please delete this note before submitting the pull request.

.gitignore

@@ -1,11 +1,10 @@
 **/.DS_Store
 **/desktop.ini
-.jekyll-metadata
 _site/**
-.sass-cache/**
 CNAME
 .travis.yml
 .idea/
+.vscode/
 
 # Vim ignore
 # source: https://github.com/github/gitignore/blob/master/Global/Vim.gitignore
@@ -24,3 +23,14 @@ Session.vim
 tags
 
 kubernetes.github.io.iml
+
+nohup.out
+
+# Hugo output
+public/
+resources/
+
+# Netlify Functions build output
+package-lock.json
+functions/
+node_modules/

.travis.yml

@@ -1,29 +0,0 @@
-language: go
-go:
-  - 1.8.1
-
-# Don't want default ./... here:
-install:
-- export PATH=$GOPATH/bin:$PATH
-- mkdir -p $HOME/gopath/src/k8s.io
-- mv $TRAVIS_BUILD_DIR $HOME/gopath/src/k8s.io/kubernetes.github.io
-
-# (1) Fetch dependencies for us to run the tests in test/examples_test.go
-- go get -t -v k8s.io/kubernetes.github.io/test
-
-# Simplified deduplication of dependencies.
-- cp -L -R $GOPATH/src/k8s.io/kubernetes/vendor/ $GOPATH/src/
-- rm -r $GOPATH/src/k8s.io/kubernetes/vendor/
-
-# (2) Fetch md-check along with all its dependencies.
-- git clone --depth=50 --branch=master https://github.com/kubernetes/md-check $HOME/gopath/src/k8s.io/md-check
-- go get -t -v k8s.io/md-check
-
-# (3) Fetch mungedocs
-- go get -v k8s.io/kubernetes/cmd/mungedocs
-
-script:
-- go test -v k8s.io/kubernetes.github.io/test
-- $GOPATH/bin/md-check --root-dir=$HOME/gopath/src/k8s.io/kubernetes.github.io
-- ./verify-docs-format.sh
-- $GOPATH/bin/mungedocs --verbose --verify --upstream=origin --root-dir=$HOME/gopath/src/k8s.io/kubernetes.github.io/docs/ --repo-root=$HOME/gopath/src/k8s.io/kubernetes.github.io --skip-munges=remove-whitespace,blank-lines-surround-preformatted,header-lines,sync-examples,analytics,analytics,kubectl-dash-f,table-of-contents,md-links,kubectl-dash-f

404.md

@@ -1,11 +0,0 @@
----
-layout: docwithnav
-title: 404 Error!
-permalink: /404.html
-no_canonical: true
-sitemap: false
----
-
-<script src="/js/redirects.js"></script>
-
-Sorry, this page was not found. :(

CNAME

@@ -1 +0,0 @@
-kubernetes.io

CONTRIBUTING.md

@@ -9,7 +9,8 @@ These are just guidelines, not rules. Use your best judgment, and feel free to p
 
 ### Code of Conduct
 
-Kubernetes follows the [Cloud Native Computing Foundation (CNCF) Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to Sarah Novotny [sarahnovotny@google.com](mailto:sarahnovotny@google.com) and/or Dan Kohn [dan@linuxfoundation.org](mailto:dan@linuxfoundation.org). 
+Kubernetes follows the [Cloud Native Computing Foundation (CNCF) Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to the
+[Kubernetes Code of Conduct Committee](https://github.com/kubernetes/community/tree/master/committee-code-of-conduct) <conduct@kubernetes.io>.
 
 ### Documentation and Site Decisions
 
@@ -17,7 +18,7 @@ The [Kubernetes SIG Docs Discussion Group](https://groups.google.com/forum/#!for
 
 ### Style Guides and Templates
 
-Before submitting a pull request to create new content, please review the [Kubernetes.io style guide](http://kubernetes.io/docs/home/contribute/style-guide/) and follow the [instructions for using page templates](http://kubernetes.io/docs/home/contribute/page-templates/). 
+Before submitting a pull request to create new content, please review the [Kubernetes.io style guide](http://kubernetes.io/docs/home/contribute/style-guide/) and follow the [instructions for using page templates](http://kubernetes.io/docs/home/contribute/page-templates/).
 
 
 ## Contributing to Documentation
@@ -26,10 +27,10 @@ Before submitting a pull request to create new content, please review the [Kuber
 
 Kubernetes.io uses github issues to track documentation issues and requests. If you see a documentation issue, submit an issue using the following steps:
 
-1. Check the [kubernetes.io issues list](https://github.com/kubernetes/kubernetes.github.io/issues) as you might find out the issue is a duplicate. 
-2. Use the [included template for every new issue](https://github.com/kubernetes/kubernetes.github.io/issues/new).  When you create a bug report, include as many details as possible and include suggested fixes to the issue. 
+1. Check the [kubernetes.io issues list](https://github.com/kubernetes/website/issues) as you might find out the issue is a duplicate.
+2. Use the [included template for every new issue](https://github.com/kubernetes/website/issues/new).  When you create a bug report, include as many details as possible and include suggested fixes to the issue.
 
-Note that code issues should be filed against the main kubernetes repository, while documentation issues should go in the kubernetes.io repository. 
+Note that code issues should be filed against the main kubernetes repository, while documentation issues should go in the kubernetes.io repository.
 
 ### Submitting Documentation Pull Requests
 

Dockerfile

@@ -0,0 +1,30 @@
+# Credit to Julien Guyomard (https://github.com/jguyomard). This Dockerfile
+# is essentially based on his Dockerfile at
+# https://github.com/jguyomard/docker-hugo/blob/master/Dockerfile. The only significant
+# change is that the Hugo version is now an overridable argument rather than a fixed
+# environment variable.
+
+FROM alpine:latest
+
+MAINTAINER Luc Perkins <lperkins@linuxfoundation.org>
+
+RUN apk add --no-cache \
+    curl \
+    git \
+    openssh-client \
+    rsync \
+    build-base \
+    libc6-compat
+
+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_extended_${HUGO_VERSION}_Linux-64bit.tar.gz | tar -xz && \
+    mv hugo /usr/local/bin/hugo && \
+    addgroup -Sg 1000 hugo && \
+    adduser -Sg hugo -u 1000 -h /src hugo
+
+WORKDIR /src
+
+EXPOSE 1313

Gemfile

@@ -1,4 +0,0 @@
-source "https://rubygems.org"
-
-gem "github-pages", group: :jekyll_plugins
-gem "jekyll-include-cache", "~> 0.1"

Gemfile.lock

@@ -1,203 +0,0 @@
-GEM
-  remote: https://rubygems.org/
-  specs:
-    activesupport (4.2.7)
-      i18n (~> 0.7)
-      json (~> 1.7, >= 1.7.7)
-      minitest (~> 5.1)
-      thread_safe (~> 0.3, >= 0.3.4)
-      tzinfo (~> 1.1)
-    addressable (2.5.0)
-      public_suffix (~> 2.0, >= 2.0.2)
-    coffee-script (2.4.1)
-      coffee-script-source
-      execjs
-    coffee-script-source (1.12.2)
-    colorator (1.1.0)
-    ethon (0.10.1)
-      ffi (>= 1.3.0)
-    execjs (2.7.0)
-    faraday (0.10.0)
-      multipart-post (>= 1.2, < 3)
-    ffi (1.9.14)
-    forwardable-extended (2.6.0)
-    gemoji (2.1.0)
-    github-pages (112)
-      activesupport (= 4.2.7)
-      github-pages-health-check (= 1.3.0)
-      jekyll (= 3.3.1)
-      jekyll-avatar (= 0.4.2)
-      jekyll-coffeescript (= 1.0.1)
-      jekyll-default-layout (= 0.1.4)
-      jekyll-feed (= 0.8.0)
-      jekyll-gist (= 1.4.0)
-      jekyll-github-metadata (= 2.2.0)
-      jekyll-mentions (= 1.2.0)
-      jekyll-optional-front-matter (= 0.1.2)
-      jekyll-paginate (= 1.1.0)
-      jekyll-readme-index (= 0.0.3)
-      jekyll-redirect-from (= 0.11.0)
-      jekyll-relative-links (= 0.2.1)
-      jekyll-sass-converter (= 1.3.0)
-      jekyll-seo-tag (= 2.1.0)
-      jekyll-sitemap (= 0.12.0)
-      jekyll-swiss (= 0.4.0)
-      jekyll-theme-architect (= 0.0.3)
-      jekyll-theme-cayman (= 0.0.3)
-      jekyll-theme-dinky (= 0.0.3)
-      jekyll-theme-hacker (= 0.0.3)
-      jekyll-theme-leap-day (= 0.0.3)
-      jekyll-theme-merlot (= 0.0.3)
-      jekyll-theme-midnight (= 0.0.3)
-      jekyll-theme-minimal (= 0.0.3)
-      jekyll-theme-modernist (= 0.0.3)
-      jekyll-theme-primer (= 0.1.5)
-      jekyll-theme-slate (= 0.0.3)
-      jekyll-theme-tactile (= 0.0.3)
-      jekyll-theme-time-machine (= 0.0.3)
-      jekyll-titles-from-headings (= 0.1.3)
-      jemoji (= 0.7.0)
-      kramdown (= 1.11.1)
-      liquid (= 3.0.6)
-      listen (= 3.0.6)
-      mercenary (~> 0.3)
-      minima (= 2.0.0)
-      rouge (= 1.11.1)
-      terminal-table (~> 1.4)
-    github-pages-health-check (1.3.0)
-      addressable (~> 2.3)
-      net-dns (~> 0.8)
-      octokit (~> 4.0)
-      public_suffix (~> 2.0)
-      typhoeus (~> 0.7)
-    html-pipeline (2.4.2)
-      activesupport (>= 2)
-      nokogiri (>= 1.4)
-    i18n (0.7.0)
-    jekyll (3.3.1)
-      addressable (~> 2.4)
-      colorator (~> 1.0)
-      jekyll-sass-converter (~> 1.0)
-      jekyll-watch (~> 1.1)
-      kramdown (~> 1.3)
-      liquid (~> 3.0)
-      mercenary (~> 0.3.3)
-      pathutil (~> 0.9)
-      rouge (~> 1.7)
-      safe_yaml (~> 1.0)
-    jekyll-avatar (0.4.2)
-      jekyll (~> 3.0)
-    jekyll-coffeescript (1.0.1)
-      coffee-script (~> 2.2)
-    jekyll-default-layout (0.1.4)
-      jekyll (~> 3.0)
-    jekyll-feed (0.8.0)
-      jekyll (~> 3.3)
-    jekyll-gist (1.4.0)
-      octokit (~> 4.2)
-    jekyll-github-metadata (2.2.0)
-      jekyll (~> 3.1)
-      octokit (~> 4.0, != 4.4.0)
-    jekyll-include-cache (0.1.0)
-      jekyll (~> 3.3)
-    jekyll-mentions (1.2.0)
-      activesupport (~> 4.0)
-      html-pipeline (~> 2.3)
-      jekyll (~> 3.0)
-    jekyll-optional-front-matter (0.1.2)
-      jekyll (~> 3.0)
-    jekyll-paginate (1.1.0)
-    jekyll-readme-index (0.0.3)
-      jekyll (~> 3.0)
-    jekyll-redirect-from (0.11.0)
-      jekyll (>= 2.0)
-    jekyll-relative-links (0.2.1)
-      jekyll (~> 3.3)
-    jekyll-sass-converter (1.3.0)
-      sass (~> 3.2)
-    jekyll-seo-tag (2.1.0)
-      jekyll (~> 3.3)
-    jekyll-sitemap (0.12.0)
-      jekyll (~> 3.3)
-    jekyll-swiss (0.4.0)
-    jekyll-theme-architect (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-cayman (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-dinky (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-hacker (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-leap-day (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-merlot (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-midnight (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-minimal (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-modernist (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-primer (0.1.5)
-      jekyll (~> 3.3)
-    jekyll-theme-slate (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-tactile (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-time-machine (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-titles-from-headings (0.1.3)
-      jekyll (~> 3.3)
-    jekyll-watch (1.5.0)
-      listen (~> 3.0, < 3.1)
-    jemoji (0.7.0)
-      activesupport (~> 4.0)
-      gemoji (~> 2.0)
-      html-pipeline (~> 2.2)
-      jekyll (>= 3.0)
-    json (1.8.3)
-    kramdown (1.11.1)
-    liquid (3.0.6)
-    listen (3.0.6)
-      rb-fsevent (>= 0.9.3)
-      rb-inotify (>= 0.9.7)
-    mercenary (0.3.6)
-    mini_portile2 (2.1.0)
-    minima (2.0.0)
-    minitest (5.10.1)
-    multipart-post (2.0.0)
-    net-dns (0.8.0)
-    nokogiri (1.6.8.1)
-      mini_portile2 (~> 2.1.0)
-    octokit (4.6.2)
-      sawyer (~> 0.8.0, >= 0.5.3)
-    pathutil (0.14.0)
-      forwardable-extended (~> 2.6)
-    public_suffix (2.0.4)
-    rb-fsevent (0.9.8)
-    rb-inotify (0.9.7)
-      ffi (>= 0.5.0)
-    rouge (1.11.1)
-    safe_yaml (1.0.4)
-    sass (3.4.23)
-    sawyer (0.8.1)
-      addressable (>= 2.3.5, < 2.6)
-      faraday (~> 0.8, < 1.0)
-    terminal-table (1.7.3)
-      unicode-display_width (~> 1.1.1)
-    thread_safe (0.3.5)
-    typhoeus (0.8.0)
-      ethon (>= 0.8.0)
-    tzinfo (1.2.2)
-      thread_safe (~> 0.1)
-    unicode-display_width (1.1.2)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  github-pages
-  jekyll-include-cache (~> 0.1)
-
-BUNDLED WITH
-   1.13.6

Makefile

@@ -1,15 +1,49 @@
+DOCKER       = docker
+HUGO_VERSION = 0.59.1
+DOCKER_IMAGE = kubernetes-hugo
+DOCKER_RUN   = $(DOCKER) run --rm --interactive --tty --volume $(CURDIR):/src
+NODE_BIN     = node_modules/.bin
+NETLIFY_FUNC = $(NODE_BIN)/netlify-lambda
+
 .PHONY: all build build-preview help serve
 
 help: ## Show this help.
 	@awk 'BEGIN {FS = ":.*?## "} /^[a-zA-Z_-]+:.*?## / {sub("\\\\n",sprintf("\n%22c"," "), $$2);printf "\033[36m%-20s\033[0m %s\n", $$1, $$2}' $(MAKEFILE_LIST)
 
-all: build ## Build site with production settings and put deliverables in _site.
+all: build ## Build site with production settings and put deliverables in ./public
 
-build: ## Build site with production settings and put deliverables in _site.
-	jekyll build
+build: ## Build site with production settings and put deliverables in ./public
+	hugo --minify
 
-build-preview: ## Build site with drafts and future posts enabled.
-	jekyll build --drafts --future
+build-preview: ## Build site with drafts and future posts enabled
+	hugo --buildDrafts --buildFuture
+
+functions-build:
+	$(NETLIFY_FUNC) build functions-src
+
+check-headers-file:
+	scripts/check-headers-file.sh
+
+production-build: check-hugo-versions build check-headers-file ## Build the production site and ensure that noindex headers aren't added
+
+non-production-build: check-hugo-versions ## Build the non-production site, which adds noindex headers to prevent indexing
+	hugo --enableGitInfo
 
 serve: ## Boot the development server.
-	jekyll serve
+	hugo server --buildFuture
+
+docker-image:
+	$(DOCKER) build . --tag $(DOCKER_IMAGE) --build-arg HUGO_VERSION=$(HUGO_VERSION)
+
+docker-build:
+	$(DOCKER_RUN) $(DOCKER_IMAGE) hugo
+
+docker-serve:
+	$(DOCKER_RUN) -p 1313:1313 $(DOCKER_IMAGE) hugo server --buildFuture --bind 0.0.0.0
+
+test-examples:
+	scripts/test_examples.sh install
+	scripts/test_examples.sh run
+
+check-hugo-versions:
+	scripts/hugo-version-check.sh $(HUGO_VERSION)

OWNERS

@@ -1,6 +1,16 @@
-assignees:
-- smarterclayton
-- janetkuo
-- pwittrock
-- kelseyhightower
+# See the OWNERS docs at https://go.k8s.io/owners
+
+reviewers:
+- sig-docs-en-reviews # Defined in OWNERS_ALIASES
+
+approvers:
+- sig-docs-en-owners # Defined in OWNERS_ALIASES
+
+emeritus_approvers:
+- chenopis
 - jaredbhatti
+# stewart-yu, you're welcome to return when you're ready to resume PR wrangling
+- stewart-yu 
+
+labels:
+- sig/docs

OWNERS_ALIASES

@@ -0,0 +1,197 @@
+aliases:
+  sig-cluster-lifecycle-kubeadm-approvers: # Approving changes to kubeadm documentation
+    - timothysc
+    - lukemarsden
+    - luxas
+    - fabriziopandini
+  sig-cluster-lifecycle-kubeadm-reviewers: # Reviewing kubeadm documentation
+    - timothysc
+    - lukemarsden
+    - luxas
+    - fabriziopandini
+    - kad
+    - xiangpengzhao
+    - stealthybox
+    - liztio
+    - chuckha
+    - detiber
+    - dixudx
+  sig-docs-blog-owners: # Approvers for blog content
+    - castrojo
+    - kbarnard10
+    - onlydole
+    - zacharysarah
+    - mrbobbytables
+  sig-docs-blog-reviewers: # Reviewers for blog content
+    - castrojo
+    - cody-clark
+    - kbarnard10
+    - mrbobbytables
+    - onlydole
+    - parispittman
+    - vonguard
+    - onlydole
+  sig-docs-de-owners: # Admins for German content
+    - bene2k1
+    - mkorbi
+    - rlenferink
+  sig-docs-de-reviews: # PR reviews for German content
+    - bene2k1
+    - mkorbi
+    - rlenferink
+  sig-docs-en-owners: # Admins for English content
+    - bradamant3
+    - bradtopol
+    - daminisatya
+    - gochist
+    - jaredbhatti
+    - jimangel
+    - kbarnard10
+    - kbhawkey
+    - makoscafee
+    - rajakavitha1
+    - ryanmcginnis
+    - simplytunde
+    - steveperry-53
+    - xiangpengzhao
+    - zacharysarah
+    - zparnold
+  sig-docs-en-reviews: # PR reviews for English content
+    - rajakavitha1
+    - sftim
+    - tengqm
+  sig-docs-es-owners: # Admins for Spanish content
+    - raelga
+    - alexbrand
+  sig-docs-es-reviews: # PR reviews for Spanish content
+    - raelga
+    - alexbrand
+    # glo-pena
+    - electrocucaracha
+  sig-docs-fr-owners: # Admins for French content
+    - remyleone
+    - perriea
+    - rekcah78
+    - yastij
+    - smana
+    - rbenzair
+    - abuisine
+    - erickhun
+    - jygastaud
+    - awkif
+    - oussemos
+  sig-docs-fr-reviews: # PR reviews for French content
+    - remyleone
+    - perriea
+    - rekcah78
+    - yastij
+    - smana
+    - rbenzair
+    - abuisine
+    - erickhun
+    - jygastaud
+    - awkif
+    - oussemos
+  sig-docs-hi-owners: # Admins for Hindi content
+    - avidLearnerInProgress
+    - daminisatya
+    - mittalyashu
+    - Rajakavitha1
+  sig-docs-hi-reviews: # PR reviews for Hindi content
+    - avidLearnerInProgress
+    - daminisatya
+    - mittalyashu
+    - Rajakavitha1
+  sig-docs-id-owners: # Admins for Indonesian content
+    - girikuncoro
+    - irvifa
+  sig-docs-id-reviews: # PR reviews for Indonesian content
+    - girikuncoro
+    - irvifa
+  sig-docs-it-owners: # Admins for Italian content
+    - mattiaperi
+    - micheleberardi
+    - rlenferink
+  sig-docs-it-reviews: # PR reviews for Italian content
+    - mattiaperi
+    - micheleberardi
+    - rlenferink
+  sig-docs-ja-owners: # Admins for Japanese content
+    - cstoku
+    - inductor
+    - nasa9084
+  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
+    - ianychoi
+    - seokho-son
+    - zacharysarah
+  sig-docs-ko-reviews: # PR reviews for Korean content
+    - ClaudiaJKang
+    - gochist
+    - ianychoi
+    - seokho-son
+  sig-docs-maintainers: # Website maintainers
+    - bradamant3
+    - jimangel
+    - kbarnard10
+    - pwittrock
+    - steveperry-53
+    - zacharysarah
+    - zparnold
+  sig-docs-zh-owners: # Admins for Chinese content
+    - chenopis
+    - chenrui333
+    - dchen1107
+    - haibinxie
+    - hanjiayao
+    - lichuqiang
+    - markthink
+    - SataQiu
+    - xiangpengzhao
+    - xichengliudui
+    - zacharysarah
+    - zhangxiaoyu-zidif
+  sig-docs-zh-reviews: # PR reviews for Chinese content
+    - chenrui333
+    - idealhack
+    - markthink
+    - SataQiu
+    - tengqm
+    - xiangpengzhao
+    - xichengliudui
+    - zhangxiaoyu-zidif
+    - pigletfly
+  sig-docs-pt-owners: # Admins for Portuguese content
+    - femrtnz
+    - jcjesus
+    - devlware
+  sig-docs-pt-reviews: # PR reviews for Portugese content
+    - femrtnz
+    - jcjesus
+    - devlware
+  sig-docs-vi-owners: # Admins for Vietnamese content
+    - huynguyennovem
+    - ngtuna
+    - truongnh1992
+  sig-docs-vi-reviews: # PR reviews for Vietnamese content
+    - huynguyennovem
+    - ngtuna
+    - truongnh1992
+  sig-docs-ru-owners: # Admins for Russian content
+    - msheldyakov
+    - aisonaku
+    - potapy4
+    - dianaabv
+  sig-docs-ru-reviews: # PR reviews for Russian content
+    - msheldyakov
+    - aisonaku
+    - potapy4
+    - dianaabv

README-de.md

@@ -0,0 +1,81 @@
+# Kubernetes Dokumentation
+
+[![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)
+
+Herzlich willkommen! Dieses Repository enthält alle Assets, die zur Erstellung der [Kubernetes-Website und Dokumentation](https://kubernetes.io/) erforderlich sind. Wir freuen uns sehr, dass Sie dazu beitragen wollen!
+
+## Beiträge zur Dokumentation
+
+Sie können auf die Schaltfläche **Fork** im oberen rechten Bereich des Bildschirms klicken, um eine Kopie dieses Repositorys in Ihrem GitHub-Konto zu erstellen. Diese Kopie wird als *Fork* bezeichnet. Nehmen Sie die gewünschten Änderungen an Ihrem Fork vor. Wenn Sie bereit sind, diese Änderungen an uns zu senden, gehen Sie zu Ihrem Fork und erstellen Sie eine neue Pull-Anforderung, um uns darüber zu informieren.
+
+Sobald Ihre Pull-Anfrage erstellt wurde, übernimmt ein Rezensent von Kubernetes die Verantwortung für klares, umsetzbares Feedback. Als Eigentümer des Pull-Request **liegt es in Ihrer Verantwortung Ihren Pull-Reqest enstsprechend des Feedbacks, dass Sie vom Kubernetes-Reviewer erhalten haben abzuändern.** Beachten Sie auch, dass Sie am Ende mehr als einen Rezensenten von Kubernetes erhalten, der Ihnen Feedback gibt, oder dass Sie Rückmeldungen von einem Rezensenten von Kubernetes erhalten, der sich von demjenigen unterscheidet, der ursprünglich für das Feedback zugewiesen wurde. In einigen Fällen kann es vorkommen, dass einer Ihrer Prüfer bei Bedarf eine technische Überprüfung von einem [Kubernetes Tech-Reviewer](https://github.com/kubernetes/website/wiki/tech-reviewers) anfordert. Reviewer geben ihr Bestes, um zeitnah Feedback zu geben, die Antwortzeiten können jedoch je nach den Umständen variieren.
+
+Weitere Informationen zum Beitrag zur Kubernetes-Dokumentation finden Sie unter:
+
+* [Mitwirkung beginnen](https://kubernetes.io/docs/contribute/start/)
+* [Ihre Dokumentationsänderungen bereitstellen](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Seitenvorlagen verwenden](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [Dokumentationsstil-Handbuch](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [Übersetzung der Kubernetes-Dokumentation](https://kubernetes.io/docs/contribute/localization/)
+
+## `README.md`'s Localizing Kubernetes Documentation
+
+### Deutsch
+Die Betreuer der deutschen Lokalisierung erreichen Sie unter:
+
+* Benedikt Rollik ([@bene2k1](https://github.com/bene2k1))
+* Max Körbächer ([@mkorbi](https://github.com/mkorbi))
+* [Slack Kanal](https://kubernetes.slack.com/messages/kubernetes-docs-de)
+
+## Site lokal mit Docker ausführen
+
+Um die Kubernetes-Website lokal laufen zu lassen, empfiehlt es sich, ein spezielles [Docker](https://docker.com) Image auszuführen, das den statischen Site-Generator [Hugo](https://gohugo.io) enthält.
+
+> Unter Windows benötigen Sie einige weitere Tools, die Sie mit [Chocolatey](https://chocolatey.org) installieren können.
+`choco install make`
+
+> Wenn Sie die Website lieber lokal ohne Docker ausführen möchten, finden Sie weitere Informationen unter [Website lokal mit Hugo ausführen](#Die-Site-lokal-mit-Hugo-ausführen).
+
+Wenn Sie Docker [installiert](https://www.docker.com/get-started) haben, erstellen Sie das Docker-Image `kubernetes-hugo` lokal:
+
+```bash
+make docker-image
+```
+
+Nachdem das Image erstellt wurde, können Sie die Site lokal ausführen:
+
+```bash
+make docker-serve
+```
+
+Öffnen Sie Ihren Browser unter http://localhost:1313, um die Site anzuzeigen. Wenn Sie Änderungen an den Quelldateien vornehmen, aktualisiert Hugo die Site und erzwingt eine Browseraktualisierung.
+
+## Die Site lokal mit Hugo ausführen
+
+Hugo-Installationsanweisungen finden Sie in der [offiziellen Hugo-Dokumentation](https://gohugo.io/getting-started/installing/). Stellen Sie sicher, dass Sie die Hugo-Version installieren, die in der Umgebungsvariablen `HUGO_VERSION` in der Datei [`netlify.toml`](netlify.toml#L9) angegeben ist.
+
+So führen Sie die Site lokal aus, wenn Sie Hugo installiert haben:
+
+```bash
+make serve
+```
+
+Dadurch wird der lokale Hugo-Server an Port 1313 gestartet. Öffnen Sie Ihren Browser unter http://localhost:1313, um die Site anzuzeigen. Wenn Sie Änderungen an den Quelldateien vornehmen, aktualisiert Hugo die Site und erzwingt eine Browseraktualisierung.
+
+## Community, Diskussion, Beteiligung und Unterstützung
+
+Erfahren Sie auf der [Community-Seite](http://kubernetes.io/community/) wie Sie mit der Kubernetes-Community interagieren können.
+
+Sie können die Betreuer dieses Projekts unter folgender Adresse erreichen:
+
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+### Verhaltensregeln
+
+Die Teilnahme an der Kubernetes-Community unterliegt dem [Kubernetes-Verhaltenskodex](code-of-conduct.md).
+
+## Vielen Dank!
+
+Kubernetes lebt vom Community Engagement und wir freuen uns sehr über Ihre Beiträge zu unserer Website und unserer Dokumentation!

README-es.md

@@ -0,0 +1,76 @@
+# La documentación de 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)
+
+Bienvenido!
+Este repositorio contiene todos los recursos necesarios para construir el [sitio web de Kubernetes y su documentación](https://kubernetes.io/). ¡Estamos encantados de que quiera contribuir!
+
+## Contribuyendo con la documentación
+
+Puede hacer clic en el botón **Fork** situado en la esquina superior derecha de la pantalla para crear una copia de este repositorio en su cuenta de GitHub. A ese tipo de copia se le llama **Fork** (bifurcación) y le permite editar el contenido del repositorio en su copia personal. Realice los cambios que quiera en su **fork** y, cuando esté listo para enviarnos esos cambios, vaya a **fork** en repositorio en su GitHub y cree una nueva **pull request** para que tengamos constancia de la propuesta de cambios.
+
+Una vez la **pull request** ha sido creada, un revisor de Kubernetes asumirá la responsabilidad de proporcionar comentarios claros y prácticos sobre como continuar. Como propietario de la PR, **es su responsabilidad modificar la pull request para abordar los comentarios proporcionados por el revisor de Kubernetes.** Tenga en cuenta que algunas veces puede terminar teniendo más de un revisor de Kubernetes participando en la revisión, por lo que es posible que reciba comentarios de más revisores a parte del asignado originalmente en la creación de la **pull request**. Además, en algunas ocasiones, es posible que uno de sus revisores solicite una revisión técnica por parte de un [revisor técnico de Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) si lo considera necesario.
+
+Los revisores harán todo lo posible para proporcionar toda la información necesaria para que la **pull request** siga adelante en un tiempo razonable, pero este tiempo de respuesta puede variar según las circunstancias.
+
+Para obtener más información sobre cómo contribuir a la documentación de Kubernetes, puede consultar:
+
+* [Empezando a contribuir](https://kubernetes.io/docs/contribute/start/)
+* [Visualizando sus cambios en su entorno local](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Utilizando las plantillas de las páginas](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [Guía de estilo de la documentación](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [Traduciendo la documentación de Kubernetes](https://kubernetes.io/docs/contribute/localization/)
+
+## Levantando el sitio web kubernetes.io en su entorno local con Docker
+
+El método recomendado para levantar una copia local del sitio web kubernetes.io es utilizando la imagen de [Docker](https://docker.com) que incluye el generador de sitios estáticos [Hugo](https://gohugo.io).
+
+> Para Windows, algunas otras herramientas como Make son necesarias. Puede instalarlas utilizando el gestor [Chocolatey](https://chocolatey.org). `choco install make` o siguiendo las instrucciones de [Make for Windows](http://gnuwin32.sourceforge.net/packages/make.htm).
+
+> Si prefiere levantar el sitio web sin utilizar **Docker**, puede seguir las instrucciones disponibles en la sección [Levantando kubernetes.io en local con Hugo](#levantando-kubernetes.io-en-local-con-hugo).
+
+Una vez tenga Docker [configurado en su máquina](https://www.docker.com/get-started), puede construir la imagen de Docker `kubernetes-hugo` localmente ejecutando el siguiente comando en la raíz del repositorio:
+
+```bash
+make docker-image
+```
+
+Una vez tenga la imagen construida, puede levantar el sitio web ejecutando:
+
+```bash
+make docker-serve
+```
+
+Abra su navegador y visite http://localhost:1313 para acceder a su copia local del sitio. A medida que vaya haciendo cambios en el código fuente, Hugo irá actualizando la página y forzará la actualización en el navegador.
+
+## Levantando kubernetes.io en local con Hugo
+
+Revise la [documentación oficial de Hugo](https://gohugo.io/getting-started/installing/) para obtener las instrucciones de instalación en su sistema operativo. Asegúrese de instalar la versión de Hugo especificada en la variable de entorno  `HUGO_VERSION` del fichero [`netlify.toml`](netlify.toml#L9).
+
+Para levantar el sitio localmente una vez Hugo está instalado en su sistema, puede ejecutar el siguiente comando:
+
+```bash
+make serve
+```
+
+Este comando levantará un servidor de Hugo en el puerto **1313** al que podrá acceder visitando http://localhost:1313 y dónde podrá visualizar su copia local del sitio web. A medida que vaya haciendo cambios en el código fuente, Hugo irá actualizando la página y forzará la actualización en el navegador.
+
+## Comunidad, discusión, contribuir y soporte
+
+Aprenda como participar en la comunidad de Kubernetes visitando la [página de comunidad](http://kubernetes.io/community/).
+
+Puede ponerse en contacto con los mantenedores de este proyecto en:
+
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+### Código de conducta
+
+La participación en la comunidad de Kubernetes está regulada por el [Código de Conducta de Kubernetes](code-of-conduct.md).
+
+## ¡Muchas gracias!
+
+Kubernetes es posible gracias a la participación de la comunidad y la documentación es vital para facilitar el acceso al proyecto.
+
+Agradecemos muchísimo sus contribuciones a nuestro sitio web y nuestra documentación.

README-fr.md

@@ -0,0 +1,83 @@
+# Documentation de 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)
+
+Bienvenue !
+Ce référentiel contient toutes les informations nécessaires à la construction du site web et de la documentation de Kubernetes.
+Nous sommes très heureux que vous vouliez contribuer !
+
+## Contribuer à la rédaction des docs
+
+Vous pouvez cliquer sur le bouton **Fork** en haut à droite de l'écran pour créer une copie de ce dépôt dans votre compte GitHub.
+Cette copie s'appelle un *fork*.
+Faites tous les changements que vous voulez dans votre fork, et quand vous êtes prêt à nous envoyer ces changements, allez dans votre fork et créez une nouvelle pull request pour nous le faire savoir.
+
+Une fois votre pull request créée, un examinateur de Kubernetes se chargera de vous fournir une revue claire et exploitable.
+En tant que propriétaire de la pull request, **il est de votre responsabilité de modifier votre pull request pour tenir compte des commentaires qui vous ont été fournis par l'examinateur de Kubernetes.**
+Notez également que vous pourriez vous retrouver avec plus d'un examinateur de Kubernetes pour vous fournir des commentaires ou vous pourriez finir par recevoir des commentaires d'un autre examinateur que celui qui vous a été initialement affecté pour vous fournir ces commentaires.
+De plus, dans certains cas, l'un de vos examinateur peut demander un examen technique à un [examinateur technique de Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) au besoin.
+Les examinateurs feront de leur mieux pour fournir une revue rapidement, mais le temps de réponse peut varier selon les circonstances.
+
+Pour plus d'informations sur la contribution à la documentation Kubernetes, voir :
+
+* [Commencez à contribuer](https://kubernetes.io/docs/contribute/start/)
+* [Apperçu des modifications apportées à votre documentation](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Utilisation des modèles de page](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [Documentation Style Guide](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [Traduction de la documentation Kubernetes](https://kubernetes.io/docs/contribute/localization/)
+
+## Exécuter le site localement en utilisant Docker
+
+La façon recommandée d'exécuter le site web Kubernetes localement est d'utiliser une image spécialisée [Docker](https://docker.com) qui inclut le générateur de site statique [Hugo](https://gohugo.io).
+
+> Si vous êtes sous Windows, vous aurez besoin de quelques outils supplémentaires que vous pouvez installer avec [Chocolatey](https://chocolatey.org). `choco install install make`
+
+> Si vous préférez exécuter le site Web localement sans Docker, voir [Exécuter le site localement avec Hugo](#running-the-site-locally-using-hugo) ci-dessous.
+
+Si vous avez Docker [up and running](https://www.docker.com/get-started), construisez l'image Docker `kubernetes-hugo' localement:
+
+```bash
+make docker-image
+```
+
+Une fois l'image construite, vous pouvez exécuter le site localement :
+
+```bash
+make docker-serve
+```
+
+Ouvrez votre navigateur à l'adresse: http://localhost:1313 pour voir le site.
+Lorsque vous apportez des modifications aux fichiers sources, Hugo met à jour le site et force le navigateur à rafraîchir la page.
+
+## Exécuter le site localement en utilisant Hugo
+
+Voir la [documentation officielle Hugo](https://gohugo.io/getting-started/installing/) pour les instructions d'installation Hugo.
+Assurez-vous d'installer la version Hugo spécifiée par la variable d'environnement `HUGO_VERSION` dans le fichier [`netlify.toml`](netlify.toml#L9).
+
+Pour exécuter le site localement lorsque vous avez Hugo installé :
+
+```bash
+make serve
+```
+
+Le serveur Hugo local démarrera sur le port 1313.
+Ouvrez votre navigateur à l'adresse: http://localhost:1313 pour voir le site.
+Lorsque vous apportez des modifications aux fichiers sources, Hugo met à jour le site et force le navigateur à rafraîchir la page.
+
+## Communauté, discussion, contribution et assistance
+
+Apprenez comment vous engager avec la communauté Kubernetes sur la [page communauté](http://kubernetes.io/community/).
+
+Vous pouvez joindre les responsables de ce projet à l'adresse :
+
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+### Code de conduite
+
+La participation à la communauté Kubernetes est régie par le [Code de conduite de Kubernetes](code-of-conduct.md).
+
+## Merci !
+
+Kubernetes prospère grâce à la participation de la communauté, et nous apprécions vraiment vos contributions à notre site et à notre documentation !

README-hi.md

@@ -0,0 +1,84 @@
+# कुबरनेट्स प्रलेखन
+
+[![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)
+
+स्वागत हे! इस रिपॉजिटरी में [कुबरनेट्स वेबसाइट और दस्तावेज](https://kubernetes.io/) बनाने के लिए आवश्यक सभी संपत्तियां हैं। हम बहुत खुश हैं कि आप योगदान करना चाहते हैं!
+
+## डॉक्स में योगदान देना
+
+आप अपने GitHub खाते में इस रिपॉजिटरी की एक copy बनाने के लिए स्क्रीन के ऊपरी-दाएँ क्षेत्र में **Fork** बटन पर क्लिक करें। इस copy को *Fork* कहा जाता है। अपने fork में कोई भी परिवर्तन करना चाहते हैं, और जब आप उन परिवर्तनों को हमारे पास भेजने के लिए तैयार हों, तो अपने fork पर जाएं और हमें इसके बारे में बताने के लिए एक नया pull request बनाएं।
+
+एक बार जब आपका pull request बन जाता है, तो एक कुबरनेट्स समीक्षक स्पष्ट, कार्रवाई योग्य प्रतिक्रिया प्रदान करने की जिम्मेदारी लेगा। pull request के मालिक के रूप में, **यह आपकी जिम्मेदारी है कि आप कुबरनेट्स समीक्षक द्वारा प्रदान की गई प्रतिक्रिया को संबोधित करने के लिए अपने pull request को संशोधित करें।**
+
+यह भी ध्यान दें कि आप एक से अधिक कुबरनेट्स समीक्षक आपको प्रतिक्रिया प्रदान कर सकते हैं या आप एक कुबरनेट्स समीक्षक से प्रतिक्रिया प्राप्त कर सकते हैं जो मूल रूप से आपको प्रतिक्रिया प्रदान करने के लिए दिए गए एक से भिन्न है। इसके अलावा, कुछ मामलों में, आपका एक समीक्षक जरूरत पड़ने पर [कुबेरनेट्स टेक समीक्षक](https://github.com/kubernetes/website/wiki/Tech-reviewers) से तकनीकी समीक्षा प्राप्त कर सकता है। समीक्षक समय पर प्रतिक्रिया देने के लिए पूरी कोशिश करेंगे, लेकिन परिस्थितियों के आधार पर प्रतिक्रिया समय अलग-अलग हो सकता है।
+
+कुबरनेट्स प्रलेखन में योगदान देने के बारे में अधिक जानकारी के लिए, देखें:
+
+* [योगदान देना शुरू करें](https://kubernetes.io/docs/contribute/start/)
+* [परिवर्तनों को अंतिम चरण में लेजाएं](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [पेज टेम्पलेट](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [प्रलेखन शैली गाइड](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [स्थानीयकरण कुबरनेट्स प्रलेखन](https://kubernetes.io/docs/contribute/localization/)
+
+## `README.md`'s स्थानीयकरण कुबरनेट्स प्रलेखन
+
+आप पर हिंदी स्थानीयकरण के maintainers तक पहुँच सकते हैं:
+
+* Yashu Mittal ([Twitter](https://twitter.com/mittalyashu77), [GitHub](https://github.com/mittalyashu))
+* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-hi)
+
+## स्थानीय रूप से डॉकर का उपयोग करके साइट चलाना
+
+कुबरनेट्स वेबसाइट को स्थानीय रूप से चलाने के लिए अनुशंसित तरीका एक विशेष [डॉकर](https://docker.com) image को चलाना है, जिसमें [Hugo](https://gohugo.io) स्टेटिक साइट जनरेटर शामिल है।
+
+> यदि आप विंडोज पर हैं, तो आपको कुछ और टूल्स की आवश्यकता होगी जिन्हें आप [Chocolatey](https://chocolatey.org) के साथ इंस्टॉल कर सकते हैं।
+
+> यदि आप डॉकर के बिना स्थानीय रूप से वेबसाइट चलाना पसंद करते हैं, तो नीचे Hugo का उपयोग करके स्थानीय रूप से साइट चलाना देखें।
+
+यदि आप डॉकर के बिना स्थानीय रूप से वेबसाइट चलाना पसंद करते हैं, तो नीचे दिए गए Hugo का उपयोग करके स्थानीय रूप से [साइट को चलाने](#running-the-site-locally-using-hugo) का तरीका देखें।
+
+यदि आप [डॉकर](https://www.docker.com/get-started) चला रहे हैं, तो स्थानीय रूप से `कुबेरनेट्स-ह्यूगो` Docker image बनाएँ:
+
+```bash
+make docker-image
+```
+
+एक बार image बन जाने के बाद, आप साइट को स्थानीय रूप से चला सकते हैं:
+
+```bash
+make docker-serve
+```
+
+साइट देखने के लिए अपने browser को `http://localhost:1313` पर खोलें। जैसा कि आप source फ़ाइलों में परिवर्तन करते हैं, Hugo साइट को अपडेट करता है और browser को refresh करने पर मजबूर करता है।
+
+## Hugo का उपयोग करते हुए स्थानीय रूप से साइट चलाना
+
+Hugo निर्देशों के लिए [आधिकारिक Hugo प्रलेखन](https://gohugo.io/getting-started/installing/) देखें। [`Netlify.toml`](netlify.toml#L9) फ़ाइल में `HUGO_VERSION` environment variable द्वारा निर्दिष्ट Hugo version को install करना सुनिश्चित करें।
+
+जब आप Hugo को install करते हैं तो स्थानीय रूप से साइट को चलाने के लिए:
+
+```bash
+make serve
+```
+
+यह पोर्ट `1313` पर Hugo सर्वर को शुरू करेगा। साइट देखने के लिए अपने browser को `http://localhost:1313` पर खोलें। जैसा कि आप source फ़ाइलों में परिवर्तन करते हैं, Hugo साइट को अपडेट करता है और एक browser को refresh करने पर मजबूर करता है।
+
+## समुदाय, चर्चा, योगदान और समर्थन
+
+[Community page](http://kubernetes.io/community/) पर कुबरनेट्स समुदाय के साथ जुड़ना सीखें।
+
+आप इस परियोजना के स्थानीयकरण तक पहुँच सकते हैं:
+
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+## कोड ओफ़ कंडक्ट
+
+कुबरनेट्स समुदाय में भागीदारी [कुबरनेट्स कोड ओफ़ कंडक्ट](https://github.com/cncf/foundation/blob/master/code-of-conduct-languages/hi.md) द्वारा शासित है.
+
+## धन्यवाद!
+
+कुबरनेट्स सामुदायिक भागीदारी पर पनपती है, और हम वास्तव में हमारी साइट और हमारे प्रलेखन में आपके योगदान की सराहना करते हैं!
+
+कुबरनेट्स आपकी भागीदारी पर निर्भर है, और हम हमारी साइट और प्रलेखन में आपके योगदान का मान करते हैं!

README-id.md

@@ -0,0 +1,72 @@
+# Dokumentasi 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)
+
+Selamat datang! Repositori ini merupakan wadah bagi semua komponen yang dibutuhkan untuk membuat [dokumentasi Kubernetes](https://kubernetes.io/). Kami merasa sangat senang apabila kamu berminat untuk menjadi kontributor!
+
+## Kontribusi pada dokumentasi
+
+Pertama, kamu dapat menekan tombol **Fork** yang berada pada bagian atas layar, untuk menyalin repositori pada akun Github-mu. Salinan ini disebut sebagai **fork**. Kamu dapat menambahkan konten pada **fork** yang kamu miliki, setelah kamu merasa cukup untuk menambahkan konten yang kamu miliki dan ingin memberikan konten tersebut pada kami, kamu dapat melihat **fork** yang telah kamu buat dan membuat **pull request** untuk memberi tahu kami bahwa kamu ingin menambahkan konten yang telah kamu buat.
+
+Setelah kamu membuat sebuah **pull request**, seorang **reviewer** akan memberikan masukan terhadap konten yang kamu sediakan serta beberapa hal yang dapat kamu lakukan apabila perbaikan diperlukan terhadap konten yang telah kamu sediakan. Sebagai seorang yang membuat **pull request**, **sudah menjadi kewajiban kamu untuk melakukan modifikasi terhadap konten yang kamu berikan sesuai dengan masukan yang diberikan oleh seorang reviewer Kubernetes**. Perlu kamu ketahui bahwa kamu dapat saja memiliki lebih dari satu orang **reviewer Kubernetes** atau dalam kasus kamu bisa saja mendapatkan **reviewer Kubernetes** yang berbeda dengan **reviewer Kubernetes** awal yang ditugaskan untuk memberikan masukan terhadap konten yang kamu sediakan. Selain itu, seorang **reviewer Kubernetes** bisa saja meminta masukan teknis dari [reviewer teknis Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) jika diperlukan. 
+
+Untuk informasi lebih lanjut mengenai tata cara melakukan kontribusi, kamu dapat melihat tautan di bawah ini:
+
+* [Petunjuk Melakukan Kontribusi](https://kubernetes.io/docs/contribute/start/)
+* [Melakukan Tahap Staging pada Konten Dokumentasi yang telah Kamu Sediakan](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Petunjuk Menggunakan Page Templates](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [Petunjuk untuk Documentation Style](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [Petunjuk untuk Melakukan Lokalisasi Dokumentasi Kubernetes](https://kubernetes.io/docs/contribute/localization/)
+
+## Menjalankan Dokumentasi Kubernetes pada Mesin Lokal Kamu
+
+Petunjuk yang disarankan untuk menjalankan Dokumentasi Kubernetes pada mesin lokal kamus adalah dengan menggunakan [Docker](https://docker.com) **image** yang memiliki **package** [Hugo](https://gohugo.io), **Hugo** sendiri merupakan generator website statis. 
+
+> Jika kamu menggunakan Windows, kamu mungkin membutuhkan beberapa langkah tambahan untuk melakukan instalasi perangkat lunak yang dibutuhkan. Instalasi ini dapat dilakukan dengan menggunakan [Chocolatey](https://chocolatey.org). `choco install make`
+
+> Jika kamu ingin menjalankan **website** tanpa menggunakan **Docker**, kamu dapat melihat tautan berikut [Petunjuk untuk menjalankan website pada mesin lokal dengan menggunakan Hugo](#petunjuk-untuk-menjalankan-website-pada-mesin-lokal-denga-menggunakan-hugo) di bagian bawah.
+
+Jika kamu sudah memiliki **Docker** [yang sudah dapat digunakan](https://www.docker.com/get-started), kamu dapat melakukan **build** `kubernetes-hugo` **Docker image** secara lokal:
+
+```bash
+make docker-image
+```
+
+Setelah **image** berhasil di-**build**, kamu dapat menjalankan website tersebut pada mesin lokal-mu:
+
+```bash
+make docker-serve
+```
+
+Buka **browser** kamu ke http://localhost:1313 untuk melihat laman dokumentasi. Selama kamu melakukan penambahan konten, **Hugo** akan secara otomatis melakukan perubahan terhadap laman dokumentasi apabila **browser** melakukan proses **refresh**.
+
+
+## Petunjuk untuk menjalankan website pada mesin lokal dengan menggunakan Hugo
+
+Kamu dapat melihat [dokumentasi resmi Hugo](https://gohugo.io/getting-started/installing/) untuk mengetahui langkah yang diperlukan untuk melakukan instalasi **Hugo**. Pastikan kamu melakukan instalasi versi **Hugo** sesuai dengan versi yang tersedia pada **environment variable** `HUGO_VERSION` pada **file**[`netlify.toml`](netlify.toml#L9). 
+
+Untuk menjalankan laman pada mesin lokal setelah instalasi **Hugo**, kamu dapat menjalankan perintah berikut:
+
+```bash
+make serve
+```
+
+Buka **browser** kamu ke http://localhost:1313 untuk melihat laman dokumentasi. Selama kamu melakukan penambahan konten, **Hugo** akan secara otomatis melakukan perubahan terhadap laman dokumentasi apabila **browser** melakukan proses **refresh**.
+
+## Komunitas, Diskusi, Kontribusi, dan Bantuan
+
+Kamu dapat belajar bagaimana tata cara untuk ikut terlibat dalam komunitas Kubernetes melalui [laman komunitas](http://kubernetes.io/community/).
+
+Kamu dapat berinteraksi dengan **maintainers** project ini melalui:
+
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+### Etika dalam Berkontribusi
+
+Partisipasi dalam komunitas Kubernetes diatur dalam [Etika dalam Berkontribusi pada Kubernetes](code-of-conduct.md).
+
+## Terima Kasih!
+
+Kubernetes sangat menjunjung tinggi partisipasi dari komunitas, dan kami sangat mengapresiasi kontribusi kamu pada laman dan dokumentasi kami!

README-ja.md

@@ -0,0 +1,75 @@
+# 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)
+
+ようこそ！このリポジトリには、[KubernetesのWebサイトとドキュメント](https://kubernetes.io/)をビルドするために必要な全アセットが格納されています。貢献に興味を持っていただきありがとうございます！
+
+## ドキュメントに貢献する
+
+GitHubの画面右上にある**Fork**ボタンをクリックすると、お使いのGitHubアカウントに紐付いた本リポジトリのコピーが作成され、このコピーのことを*フォーク*と呼びます。フォークリポジトリの中ではお好きなように変更を加えていただいて構いません。加えた変更をこのリポジトリに追加したい任意のタイミングにて、フォークリポジトリからPull Reqeustを作成してください。
+
+Pull Requestが作成されると、レビュー担当者が責任を持って明確かつ実用的なフィードバックを返します。
+Pull Requestの所有者は作成者であるため、**ご自身で作成したPull Requestを編集し、フィードバックに対応するのはご自身の役目です。**
+また、状況によっては2人以上のレビュアーからフィードバックが返されたり、アサインされていないレビュー担当者からのフィードバックが来ることがある点もご注意ください。
+さらに、特定のケースにおいては、レビュー担当者が[Kubernetes tech reviewer](https://github.com/kubernetes/website/wiki/Tech-reviewers)に対してレビューを依頼することもあります。
+レビュー担当者はタイムリーにフィードバックを提供するために最善を尽くしますが、応答時間は状況に応じて異なる場合があります。
+
+Kubernetesのドキュメントへの貢献に関する詳細については以下のページをご覧ください:
+
+* [貢献のはじめ方](https://kubernetes.io/docs/contribute/start/)
+* [ドキュメントの変更をステージする](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [ページテンプレートの使い方](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [ドキュメントのスタイルガイド](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [Kubernetesドキュメントの翻訳方法](https://kubernetes.io/docs/contribute/localization/)
+
+## Dockerを使ってローカル環境でWebサイトを動かす
+
+ローカル環境で本ページを動かすのに推奨される方法は、静的サイトジェネレータの[Hugo](https://gohugo.io)を動かすのに特化した[Docker](https://docker.com)イメージを使うことです。
+
+> Windows上で環境を作る場合は[Chocolatey](https://chocolatey.org)を使ってインストール可能な追加のツールが必要になります。 `choco install make`
+
+> Dockerを使わずに環境を構築したい場合は、[Hugoをローカル環境で動かす](#hugoをローカル環境で動かす)をご覧ください。
+
+既に[Dockerが動いている環境](https://www.docker.com/get-started)であれば、以下のコマンドを使って`kubernetes-hugo`イメージをローカルでビルドします:
+
+```bash
+make docker-image
+```
+
+イメージが作成されたら、以下のコマンドを使ってWebサイトをローカル上で動かすことができます:
+
+```bash
+make docker-serve
+```
+
+お使いのブラウザにて http://localhost:1313 にアクセスすることでWebサイトが開きます。リポジトリ内のソースファイルに変更を加えると、HugoがWebサイトの内容を更新してブラウザに反映します。
+
+## Hugoをローカル環境で動かす
+
+Hugoのインストール方法については[Hugoの公式ドキュメント](https://gohugo.io/getting-started/installing/)をご覧ください。このとき、[`netlify.toml`](netlify.toml#L9)ファイルに記述されている`HUGO_VERSION`と同じバージョンをインストールするようにしてください。
+
+Hugoがインストールできたら、以下のコマンドを使ってWebサイトをローカル上で動かすことができます:
+
+```bash
+make serve
+```
+
+これで、Hugoのサーバーが1313番ポートを使って開始します。 お使いのブラウザにて http://localhost:1313 にアクセスしてください。リポジトリ内のソースファイルに変更を加えると、HugoがWebサイトの内容を更新してブラウザに反映します。
+
+## コミュニティ内での議論、貢献、サポートなどについて
+
+[コミュニティのページ](http://kubernetes.io/community/)をご覧になることで、Kubernetesコミュニティとの関わり方を学ぶことができます。
+
+本プロジェクトのメンテナーには以下の方法で連絡することができます:
+
+- [Slack](https://kubernetes.slack.com/messages/kubernetes-docs-ja)
+- [メーリングリスト](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+### 行動規範
+
+Kubernetesコミュニティへの参加については、[Kubernetesの行動規範](code-of-conduct.md)によって管理されています。
+
+## ありがとうございます！
+
+Kubernetesはコミュニティの参加によって成長しています。Webサイトおよびドキュメンテーションへの皆さんの貢献に感謝します！

README-ko.md

@@ -0,0 +1,69 @@
+# 쿠버네티스 문서화
+
+[![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)
+
+환영합니다! 이 저장소는 쿠버네티스 웹사이트 및 문서화를 만드는 데 필요로 하는 모든 asset에 대한 공간을 제공합니다. 여러분이 기여를 원한다는 사실에 매우 기쁩니다!
+
+## 문서에 기여하기
+
+이 저장소에 대한 복제본을 여러분의 GitHub 계정에 생성하기 위해 화면 오른쪽 위 영역에 있는 **Fork** 버튼을 클릭 가능합니다. 이 복제본은 *fork* 라고 부릅니다. 여러분의 fork에서 원하는 임의의 변경 사항을 만들고, 해당 변경 사항을 보낼 준비가 되었다면, 여러분의 fork로 이동하여 새로운 풀 리퀘스트를 만들어 우리에게 알려주시기 바랍니다.
+
+여러분의 풀 리퀘스트가 생성된 이후에는, 쿠버네티스 리뷰어가 명료하고 실행 가능한 피드백을 제공하는 책임을 담당할 것입니다. 풀 리퀘스트의 오너로서, **쿠버네티스 리뷰어로부터 제공받은 피드백을 수용하기 위해 풀 리퀘스트를 수정하는 것은 여러분의 책임입니다.** 또한, 참고로 한 명 이상의 쿠버네티스 리뷰어가 여러분에게 피드백을 제공하는 상황에 처하거나, 또는 여러분에게 피드백을 제공하기로 원래 할당된 사람이 아닌 다른 쿠버네티스 리뷰어로부터 피드백을 받는 상황에 처할 수도 있습니다.  그뿐만 아니라, 몇몇 상황에서는, 필요에 따라 리뷰어 중 한 명이 [쿠버네티스 기술 리뷰어](https://github.com/kubernetes/website/wiki/Tech-reviewers)로부터의 기술 리뷰를 요청할지도 모릅니다. 리뷰어는 제시간에 피드백을 제공하기 위해 최선을 다할 것이지만, 응답 시간은 상황에 따라 달라질 수도 있습니다.
+
+쿠버네티스 문서화에 기여하기와 관련된 보다 자세한 정보는, 다음을 살펴봅니다:
+
+* [기여 시작하기](https://kubernetes.io/docs/contribute/start/)
+* [문서화 변경 사항 스테이징하기](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [페이지 템플릿 사용하기](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [문서화 스타일 가이드](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [쿠버네티스 문서화 로컬라이징](https://kubernetes.io/docs/contribute/localization/)
+
+## `README.md`에 대한 쿠버네티스 문서화 번역
+
+### 한국어
+
+`README.md` 번역 및 한국어 기여자를 위한 보다 자세한 가이드를 [한국어 README](README-ko.md) 페이지 혹은 [쿠버네티스 문서 한글화 가이드](https://kubernetes.io/ko/docs/contribute/localization_ko/)에서 살펴봅니다.
+
+한국어 번역 메인테이너에게 다음을 통해 연락 가능합니다.
+
+* 이덕준 ([GitHub - @gochist](https://github.com/gochist))
+* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-ko)
+
+## 도커를 사용하여 사이트를 로컬에서 실행하기
+
+쿠버네티스 웹사이트를 로컬에서 실행하기 위한 추천하는 방식은 [Hugo](https://gohugo.io) 정적 사이트 생성기를 포함하는 특별한 [도커](https://docker.com) 이미지를 실행하는 것입니다.
+
+> Windows에서 실행하는 경우, [Chocolatey](https://chocolatey.org)로 설치할 수 있는 명명 추가 도구를 필요로 할 것입니다. `choco install make`
+
+> 도커를 사용하지 않고 웹사이트를 로컬에서 실행하기를 선호하는 경우에는, 아래 [Hugo를 사용한 로컬 사이트 실행하기](#hugo를-사용한-로컬-사이트-실행하기)를 살펴봅니다.
+
+도커 [동작 및 실행](https://www.docker.com/get-started) 환경이 있는 경우, 로컬에서 `kubernetes-hugo` 도커 이미지를 빌드 합니다:
+
+```bash
+make docker-image
+```
+
+해당 이미지가 빌드 된 이후, 사이트를 로컬에서 실행할 수 있습니다:
+
+```bash
+make docker-serve
+```
+
+브라우저에서 http://localhost:1313 를 열어 사이트를 살펴봅니다. 소스 파일에 변경 사항이 있을 때, Hugo는 사이트를 업데이트하고 브라우저를 강제로 새로고침합니다.
+
+## Hugo를 사용한 로컬 사이트 실행하기
+
+Hugo 설치 안내를 위해서는 [공식 Hugo 문서화](https://gohugo.io/getting-started/installing/)를 살펴봅니다. [`netlify.toml`](netlify.toml#L9) 파일에 있는 `HUGO_VERSION` 환경 변수에서 지정된 Hugo 버전이 설치되었는지를 확인합니다.
+
+Hugo가 설치되었을 때 로컬에서 사이트를 실행하기 위해 (다음을 실행합니다):
+
+```bash
+make serve
+```
+
+이를 통해 로컬 Hugo 서버를 1313번 포트에 시작합니다. 브라우저에서 http://localhost:1313 를 열어 사이트를 살펴봅니다. 소스 파일에 변경 사항이 있을 때, Hugo는 사이트를 업데이트하고 브라우저를 강제로 새로고침합니다.
+
+## 감사합니다!
+
+쿠버네티스는 커뮤니티 참여와 함께 생존하며, 우리는 사이트 및 문서화에 대한 여러분의 컨트리뷰션에 대해 정말 감사하게 생각합니다!

README-pt.md

@@ -0,0 +1,76 @@
+# A documentação do 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)
+
+Bem vindos! Este repositório abriga todos os recursos necessários para criar o [site e documentação do Kubernetes](https://kubernetes.io/). Estamos muito satisfeitos por você querer contribuir!
+
+## Contribuindo com os documentos
+
+Você pode clicar no botão **Fork** na área superior direita da tela para criar uma cópia desse repositório na sua conta do GitHub. Esta cópia é chamada de *fork*. Faça as alterações desejadas no seu fork e, quando estiver pronto para enviar as alterações para nós, vá até o fork e crie uma nova solicitação de pull para nos informar sobre isso.
+
+Depois que seu **pull request** for criado, um revisor do Kubernetes assumirá a responsabilidade de fornecer um feedback claro e objetivo. Como proprietário do pull request, **é sua responsabilidade modificar seu pull request para abordar o feedback que foi fornecido a você pelo revisor do Kubernetes.** Observe também que você pode acabar tendo mais de um revisor do Kubernetes para fornecer seu feedback ou você pode acabar obtendo feedback de um revisor do Kubernetes que é diferente daquele originalmente designado para lhe fornecer feedback. Além disso, em alguns casos, um de seus revisores pode solicitar uma revisão técnica de um [revisor de tecnologia Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) quando necessário. Os revisores farão o melhor para fornecer feedback em tempo hábil, mas o tempo de resposta pode variar de acordo com as circunstâncias.
+
+Para mais informações sobre como contribuir com a documentação do Kubernetes, consulte:
+
+* [Comece a contribuir](https://kubernetes.io/docs/contribute/start/)
+* [Preparando suas alterações na documentação](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Usando Modelos de Página](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [Guia de Estilo da Documentação](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [Localizando documentação do Kubernetes](https://kubernetes.io/docs/contribute/localization/)
+
+Você pode contactar os mantenedores da localização em Português em:
+
+* Felipe ([GitHub - @femrtnz](https://github.com/femrtnz))
+* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-pt)
+
+## Executando o site localmente usando o Docker
+
+A maneira recomendada de executar o site do Kubernetes localmente é executar uma imagem especializada do [Docker](https://docker.com) que inclui o gerador de site estático [Hugo](https://gohugo.io).
+
+> Se você está rodando no Windows, você precisará de mais algumas ferramentas que você pode instalar com o [Chocolatey](https://chocolatey.org). `choco install make`
+
+> Se você preferir executar o site localmente sem o Docker, consulte [Executando o site localmente usando o Hugo](#executando-o-site-localmente-usando-o-hugo) abaixo.
+
+Se você tiver o Docker [em funcionamento](https://www.docker.com/get-started), crie a imagem do Docker do `kubernetes-hugo` localmente:
+
+```bash
+make docker-image
+```
+
+Depois que a imagem foi criada, você pode executar o site localmente:
+
+```bash
+make docker-serve
+```
+
+Abra seu navegador para http://localhost:1313 para visualizar o site. Conforme você faz alterações nos arquivos de origem, Hugo atualiza o site e força a atualização do navegador.
+
+## Executando o site localmente usando o Hugo
+
+Veja a [documentação oficial do Hugo](https://gohugo.io/getting-started/installing/) para instruções de instalação do Hugo. Certifique-se de instalar a versão do Hugo especificada pela variável de ambiente `HUGO_VERSION` no arquivo [`netlify.toml`](netlify.toml#L9).
+
+Para executar o site localmente quando você tiver o Hugo instalado:
+
+```bash
+make serve
+```
+
+Isso iniciará o servidor Hugo local na porta 1313. Abra o navegador para http://localhost:1313 para visualizar o site. Conforme você faz alterações nos arquivos de origem, Hugo atualiza o site e força a atualização do navegador.
+
+## Comunidade, discussão, contribuição e apoio
+
+Aprenda a se envolver com a comunidade do Kubernetes na [página da comunidade](http://kubernetes.io/community/).
+
+Você pode falar com os mantenedores deste projeto:
+
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+### Código de conduta
+
+A participação na comunidade Kubernetes é regida pelo [Código de Conduta da Kubernetes](code-of-conduct.md).
+
+## Obrigado!
+
+O Kubernetes conta com a participação da comunidade e nós realmente agradecemos suas contribuições para o nosso site e nossa documentação!

README-ru.md

@@ -0,0 +1,80 @@
+# Документация по 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)
+
+Добро пожаловать! Данный репозиторий содержит все необходимые файлы для сборки [сайта Kubernetes и документации](https://kubernetes.io/). Мы благодарим вас за старания!
+
+## Вклад в документацию
+
+Нажмите на кнопку **Fork** в правом верхнем углу, чтобы создать копию этого репозитория в ваш GitHub-аккаунт. Это копия называется *форк-репозиторием*. Делайте любые изменения в вашем форк-репозитории, и когда вы будете готовы опубликовать изменения, откройте форк-репозиторий и создайте новый пулреквест, чтобы уведомить нас.
+
+После того, как вы отправите пулреквест, ревьювер Kubernetes даст по нему обратную связь. Вы, как автор пулреквеста, **должны обновить свой пулреквест после его рассмотрения ревьювером Kubernetes.** Вполне возможно, что более одного ревьювера Kubernetes оставят свои комментарии или даже может быть так, что новый комментарий ревьювера Kubernetes будет отличаться от первоначального назначенного ревьювера. Кроме того, в некоторых случаях один из ревьюверов может запросить технический обзор у [технического ревьювера Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers), если это будет необходимо. Ревьюверы сделают все возможное, чтобы как можно оперативно оставить свои предложения и пожелания, но время ответа может варьироваться в зависимости от обстоятельств.
+
+Узнать подробнее о том, как поучаствовать в документации Kubernetes, вы можете по ссылкам ниже:
+
+* [Начните вносить свой вклад](https://kubernetes.io/docs/contribute/start/)
+* [Просмотр локальных изменений](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Использование шаблонов страниц](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [Руководство по оформлению документации](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [Руководство по локализации Kubernetes](https://kubernetes.io/docs/contribute/localization/)
+
+## `README.md` файлы на других языках
+|  |  |
+|---|---|
+|[Французский](README-fr.md)|[Корейский](README-ko.md)|
+|[Немецкий](README-de.md)|[Португальский](README-pt.md)|
+|[Хинди README](README-hi.md)|[Испанский](README-es.md)|
+|[Индонезийский](README-id.md)|[Китайский](README-zh.md)|
+|||
+
+## Запуск сайта локально с помощью Docker
+
+Рекомендованный способ запуска сайта Kubernetes на локальной машине - использовать специальный образ [Docker](https://docker.com), который включает статический генератор сайтов [Hugo](https://gohugo.io).
+
+> Если вы используете Windows, вам необходимо установить дополнительные инструменты через [Chocolatey](https://chocolatey.org). `choco install make`
+
+> Если вы хотите запустить сайт локально без Docker, обратитесь к разделу [Запуск сайта с помощью Hugo](#running-the-site-locally-using-hugo) ниже на этой странице.
+
+Когда Docker [установлен и запущен](https://www.docker.com/get-started), соберите локально Docker-образ `kubernetes-hugo`, выполнив команду в консоли:
+
+```bash
+make docker-image
+```
+
+После того, как вы собрали образ, можно запустить сайт локально:
+
+```bash
+make docker-serve
+```
+
+Откройте браузер и перейдите по ссылке http://localhost:1313, чтобы открыть сайт. Если вы редактируете исходные файлы сайта, Hugo автоматически применит изменения и обновит страницу в браузере.
+
+## Запуск веб-сайта с помощью Hugo {#running-the-site-locally-using-hugo}
+
+Обратитесь к [официальной документации Hugo](https://gohugo.io/getting-started/installing/), чтобы установить Hugo. Убедитесь, что вы установили правильную версию Hugo, которая устанавливается в переменной окружения `HUGO_VERSION` в файле [`netlify.toml`](netlify.toml#L9).
+
+После установки Hugo, чтобы запустить сайт, выполните в консоли:
+
+```bash
+make serve
+```
+
+Эта команда запустит сервер Hugo на порту 1313. Откройте браузер и перейдите по ссылке http://localhost:1313, чтобы открыть сайта. Если вы отредактируете исходные файлы сайта, Hugo автоматически применит изменения и обновит страницу в браузере.
+
+## Сообщество, обсуждение, вклад и поддержка
+
+Узнайте, как поучаствовать в жизни сообщества Kubernetes на [странице сообщества](http://kubernetes.io/community/).
+
+Вы можете связаться с сопровождающими этого проекта по:
+
+- [Канал в Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Рассылка](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+### Нормы поведения
+
+Участие в сообществе Kubernetes регулируется [нормами поведения Kubernetes](code-of-conduct.md).
+
+## Спасибо!
+
+Kubernetes процветает благодаря сообществу и мы ценим ваш вклад в сайт и документацию!

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-zh.md

@@ -0,0 +1,182 @@
+# Kubernetes 文档
+<!--
+# The Kubernetes documentation
+ -->
+
+[![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)
+
+<!--
+Welcome! This repository houses all of the assets required to build the [Kubernetes website and documentation](https://kubernetes.io/).
+We're glad that you want to contribute!
+ -->
+欢迎！本仓库包含了所有用于构建 [Kubernetes 网站和文档](https://kubernetes.io/)的内容。
+我们非常高兴您想要参与贡献！
+
+<!--
+## Contributing to the docs
+ -->
+## 贡献文档
+
+<!--
+You can click the **Fork** button in the upper-right area of the screen to create a copy of this repository in your GitHub account.
+This copy is called a *fork*. Make any changes you want in your fork,
+and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.
+ -->
+您可以点击屏幕右上方的 **Fork** 按钮，在您的 GitHub 账户下创建一份本仓库的副本。这个副本叫做 *fork*。您可以对 fork 副本进行任意修改，
+当准备好把修改提交给我们时，您可以通过创建一个 pull request 来告知我们。
+
+<!--
+Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback.
+As the owner of the pull request, **it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer.**
+Also, note that you may end up having more than one Kubernetes reviewer provide you feedback or you may end up getting feedback from a Kubernetes reviewer that is different than the one initially assigned to provide you feedback.
+Furthermore, in some cases, one of your reviewers might ask for a technical review from a [Kubernetes tech reviewer](https://github.com/kubernetes/website/wiki/Tech-reviewers) when needed.
+Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances.
+ -->
+创建 pull request 后，Kubernetes 审核人员将负责提供清晰且可操作的反馈。作为 pull request 的所有者，**您有责任修改 pull request 以解决 Kubernetes 审核者提供给您的反馈。**
+另请注意，您最终可能会收到多个 Kubernetes 审核人员为您提供的反馈，也可能出现后面 Kubernetes 审核人员的反馈与前面审核人员的反馈不尽相同的情况。
+此外，在某些情况下，您的某位评审员可能会在需要时要求 [Kubernetes 技术评审员](https://github.com/kubernetes/website/wiki/Tech-reviewers) 进行技术评审。
+审稿人将尽最大努力及时提供反馈，但响应时间可能因情况而异。
+
+<!--
+For more information about contributing to the Kubernetes documentation, see:
+
+* [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/)
+* [Localizing Kubernetes Documentation](https://kubernetes.io/docs/contribute/localization/)
+ -->
+有关为 Kubernetes 文档做出贡献的更多信息，请参阅：
+
+* [开始贡献](https://kubernetes.io/docs/contribute/start/)
+* [缓存您的文档变更](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [使用页面模版](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [文档风格指南](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [本地化 Kubernetes 文档](https://kubernetes.io/docs/contribute/localization/)
+
+<!--
+## `README.md`'s Localizing Kubernetes Documentation
+ -->
+## `README.md` 的本地化 Kubernetes 文档
+
+<!--
+### Korean
+
+You can reach the maintainers of Korean localization at:
+
+* June Yi ([GitHub - @gochist](https://github.com/gochist))
+* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-ko)
+ -->
+### 中文
+
+可以通过以下方式联系中文本地化的维护人员：
+
+* Rui Chen ([GitHub - @chenrui333](https://github.com/chenrui333))
+* He Xiaolong ([GitHub - @markthink](https://github.com/markthink))
+* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-zh)
+
+<!--
+## Running the website locally using Docker
+ -->
+## 在本地使用 docker 运行网站
+
+<!--
+The recommended way to run the Kubernetes website locally is to run a specialized [Docker](https://docker.com) image that includes the [Hugo](https://gohugo.io) static website generator.
+ -->
+在本地运行 Kubernetes 网站的推荐方法是运行包含 [Hugo](https://gohugo.io) 静态网站生成器的专用 [Docker](https://docker.com) 镜像。
+
+<!--
+> If you are running on Windows, you'll need a few more tools which you can install with [Chocolatey](https://chocolatey.org). `choco install make`
+ -->
+> 如果您使用的是 Windows，则需要一些工具，可以使用 [Chocolatey](https://chocolatey.org) 进行安装。`choco install make`
+
+<!--
+> If you'd prefer to run the website locally without Docker, see [Running the website locally using Hugo](#running-the-site-locally-using-hugo) below.
+ -->
+> 如果您更喜欢在没有 Docker 的情况下在本地运行网站，请参阅下面的[使用 Hugo 在本地运行网站](#running-the-site-locally-using-hugo) 章节。
+
+<!--
+If you have Docker [up and running](https://www.docker.com/get-started), build the `kubernetes-hugo` Docker image locally:
+ -->
+如果您已经[安装运行](https://www.docker.com/get-started)了 Docker，使用以下命令在本地构建 `kubernetes-hugo` Docker 镜像：
+
+```bash
+make docker-image
+```
+
+<!--
+Once the image has been built, you can run the website locally:
+ -->
+一旦创建了镜像，您就可以在本地运行网站了：
+
+```bash
+make docker-serve
+```
+
+<!--
+Open up your browser to http://localhost:1313 to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
+ -->
+打开浏览器访问 http://localhost:1313 以查看网站。当您对源文件进行更改时，Hugo 会更新网站并强制刷新浏览器。
+
+<!--
+## Running the website locally using Hugo
+ -->
+## 使用 Hugo 在本地运行网站
+
+<!--
+See the [official Hugo documentation](https://gohugo.io/getting-started/installing/) for Hugo installation instructions.
+Make sure to install the Hugo version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L9) file.
+ -->
+有关 Hugo 的安装说明，请参阅 [Hugo 官方文档](https://gohugo.io/getting-started/installing/)。
+确保安装对应版本的 Hugo，版本号由 [`netlify.toml`](netlify.toml#L9) 文件中的 `HUGO_VERSION` 环境变量指定。
+
+<!--
+To run the website locally when you have Hugo installed:
+ -->
+安装 Hugo 后，在本地运行网站：
+
+```bash
+make serve
+```
+
+<!--
+This will start the local Hugo server on port 1313. Open up your browser to http://localhost:1313 to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
+ -->
+这将在 1313 端口上启动本地 Hugo 服务器。打开浏览器访问 http://localhost:1313 查看网站。当您对源文件进行更改时，Hugo 会更新网站并强制刷新浏览器。
+
+<!--
+## Community, discussion, contribution, and support
+ -->
+## 社区、讨论、贡献和支持
+
+<!--
+Learn how to engage with the Kubernetes community on the [community page](http://kubernetes.io/community/).
+ -->
+在[社区页面](http://kubernetes.io/community/)了解如何与 Kubernetes 社区互动。
+
+<!--
+You can reach the maintainers of this project at:
+ -->
+您可以通过以下方式联系该项目的维护人员：
+
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+<!--
+### Code of conduct
+
+Participation in the Kubernetes community is governed by the [Kubernetes Code of Conduct](code-of-conduct.md).
+ -->
+### 行为准则
+
+参与 Kubernetes 社区受 [Kubernetes 行为准则](code-of-conduct.md)的约束。
+
+<!--
+## Thank you!
+
+Kubernetes thrives on community participation, and we appreciate your contributions to our website and our documentation!
+ -->
+## 感谢！
+
+Kubernetes 因为社区的参与而蓬勃发展，感谢您对我们网站和文档的贡献！

README.md

@@ -1,19 +1,82 @@
-## Instructions for Contributing to the Kubernetes Documentation
+# The Kubernetes documentation
 
-Welcome! We are very pleased you want to contribute to the Kubernetes documentation.
+[![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)
 
-You can click the **Fork** button in the upper-right area of the screen to create a copy of this repository in your GitHub account called a *fork*. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.
+Welcome! This repository houses all of the assets required to build the [Kubernetes website and documentation](https://kubernetes.io/). We're glad that you want to contribute!
+
+## Contributing to the docs
+
+You can click the **Fork** button in the upper-right area of the screen to create a copy of this repository in your GitHub account. This copy is called a *fork*. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.
+
+Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback.  As the owner of the pull request, **it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer.**  Also, note that you may end up having more than one Kubernetes reviewer provide you feedback or you may end up getting feedback from a Kubernetes reviewer that is different than the one initially assigned to provide you feedback. Furthermore, in some cases, one of your reviewers might ask for a technical review from a [Kubernetes tech reviewer](https://github.com/kubernetes/website/wiki/Tech-reviewers) when needed.  Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances.
 
 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/)
-* [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/)
+* [Localizing Kubernetes Documentation](https://kubernetes.io/docs/contribute/localization/)
+
+## Localization `README.md`'s
+|  |  |
+|---|---|
+|[French README](README-fr.md)|[Korean README](README-ko.md)|
+|[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)|[Vietnamese README](README-vi.md)|
+|[Russian README](README-ru.md)|
+|||
+
+## Running the website locally using Docker
+
+The recommended way to run the Kubernetes website locally is to run a specialized [Docker](https://docker.com) image that includes the [Hugo](https://gohugo.io) static website generator.
+
+> If you are running on Windows, you'll need a few more tools which you can install with [Chocolatey](https://chocolatey.org). `choco install make`
+
+> If you'd prefer to run the website locally without Docker, see [Running the website locally using Hugo](#running-the-site-locally-using-hugo) below.
+
+If you have Docker [up and running](https://www.docker.com/get-started), build the `kubernetes-hugo` Docker image locally:
+
+```bash
+make docker-image
+```
+
+Once the image has been built, you can run the website locally:
+
+```bash
+make docker-serve
+```
+
+Open up your browser to http://localhost:1313 to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
+
+## Running the website locally using Hugo
+
+See the [official Hugo documentation](https://gohugo.io/getting-started/installing/) for Hugo installation instructions. Make sure to install the Hugo extended version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L9) file.
+
+To run the website locally when you have Hugo installed:
+
+```bash
+make serve
+```
+
+This will start the local Hugo server on port 1313. Open up your browser to http://localhost:1313 to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
+
+## Community, discussion, contribution, and support
+
+Learn how to engage with the Kubernetes community on the [community page](http://kubernetes.io/community/).
+
+You can reach the maintainers of this project at:
+
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+### Code of conduct
+
+Participation in the Kubernetes community is governed by the [Kubernetes Code of Conduct](code-of-conduct.md).
 
 ## Thank you!
 
-Kubernetes thrives on community participation, and we really appreciate your
-contributions to our site and our documentation!
+Kubernetes thrives on community participation, and we appreciate your contributions to our website and our documentation!

SECURITY_CONTACTS

@@ -0,0 +1,15 @@
+# Defined below are the security contacts for this repo.
+#
+# They are the contact point for the Product Security Committee to reach out
+# to for triaging and handling of incoming issues.
+#
+# The below names agree to abide by the
+# [Embargo Policy](https://git.k8s.io/security/private-distributors-list.md#embargo-policy)
+# and will be removed and replaced if they violate that agreement.
+#
+# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE
+# INSTRUCTIONS AT https://kubernetes.io/security/
+
+bradamant3
+jimangel
+zacharysarah

_config.yml

@@ -1,58 +0,0 @@
-name: Kubernetes
-title: Kubernetes
-url: https://kubernetes.io
-description: Production-Grade Container Orchestration
-markdown: kramdown
-kramdown:
-  input: GFM
-  html_to_native: true
-  hard_wrap: false
-  syntax_highlighter: rouge
-incremental: true
-
-safe: false
-lsi: false
-
-defaults:
-  -
-    scope:
-      path: ""
-    values:
-      fullversion: "v1.6.3"
-      version: "v1.6"
-      githubbranch: "master"
-      docsbranch: "master"
-  -
-    scope:
-      path: "docs"
-    values:
-      layout: docwithnav
-      showedit: true
-
-permalink: pretty
-
-gems:
-  - jekyll-redirect-from
-  - jekyll-feed
-  - jekyll-sitemap
-  - jekyll-seo-tag
-  - jekyll-include-cache
-
-# SEO
-logo: /images/favicon.png
-twitter:
-  username: kubernetesio
-
-# empty array for tabs
-emptyArray: []
-
-# Tables of contents, stored in the _data folder, that control the sidebar nav
-tocs:
-  - docs-home
-  - setup
-  - tasks
-  - tutorials
-  - concepts
-  - reference
-  - samples
-  - search

_data/concepts.yml

@@ -1,90 +0,0 @@
-bigheader: "Concepts"
-abstract: "Detailed explanations of Kubernetes system concepts and abstractions."
-toc:
-- docs/concepts/index.md
-
-- title: Overview
-  section:
-  - docs/concepts/overview/what-is-kubernetes.md
-  - docs/concepts/overview/components.md
-  - title: Working with Kubernetes Objects
-    section:
-    - docs/concepts/overview/working-with-objects/kubernetes-objects.md
-    - docs/concepts/overview/working-with-objects/names.md
-    - docs/concepts/overview/working-with-objects/namespaces.md
-    - docs/concepts/overview/working-with-objects/labels.md
-    - docs/concepts/overview/working-with-objects/annotations.md
-  - docs/concepts/overview/kubernetes-api.md
-
-- title: Kubernetes Architecture
-  section:
-  - docs/concepts/architecture/nodes.md
-  - docs/concepts/architecture/master-node-communication.md
-
-- title: Containers
-  section:
-  - docs/concepts/containers/images.md
-  - docs/concepts/containers/container-environment-variables.md
-  - docs/concepts/containers/container-lifecycle-hooks.md
-
-- title: Workloads
-  section:
-  - title: Pods
-    section:
-    - docs/concepts/workloads/pods/pod-overview.md
-    - docs/concepts/workloads/pods/pod.md
-    - docs/concepts/workloads/pods/pod-lifecycle.md
-    - docs/concepts/workloads/pods/init-containers.md
-  - title: Controllers
-    section:
-    - docs/concepts/workloads/controllers/replicaset.md
-    - docs/concepts/workloads/controllers/replicationcontroller.md
-    - docs/concepts/workloads/controllers/deployment.md
-    - docs/concepts/workloads/controllers/statefulset.md
-    - docs/concepts/workloads/controllers/petset.md
-    - docs/concepts/workloads/controllers/daemonset.md
-    - docs/concepts/workloads/controllers/garbage-collection.md
-    - docs/concepts/workloads/controllers/jobs-run-to-completion.md
-    - docs/concepts/workloads/controllers/cron-jobs.md
-
-- title: Configuration
-  section:
-  - docs/concepts/configuration/overview.md
-  - docs/concepts/configuration/manage-compute-resources-container.md
-  - docs/concepts/configuration/assign-pod-node.md
-  - docs/concepts/configuration/secret.md
-
-- title: Services, Load Balancing, and Networking
-  section:
-  - docs/concepts/services-networking/service.md
-  - docs/concepts/services-networking/dns-pod-service.md
-  - docs/concepts/services-networking/connect-applications-service.md
-  - docs/concepts/services-networking/ingress.md
-  - docs/concepts/services-networking/network-policies.md
-
-- title: Storage
-  section:
-  - docs/concepts/storage/volumes.md
-  - docs/concepts/storage/persistent-volumes.md
-  - title: Dynamic Provisioning
-    path: http://blog.kubernetes.io/2016/10/dynamic-provisioning-and-storage-in-kubernetes.html
-
-- title: Cluster Administration
-  section:
-  - docs/concepts/cluster-administration/cluster-administration-overview.md
-  - docs/concepts/cluster-administration/manage-deployment.md
-  - docs/concepts/cluster-administration/networking.md
-  - docs/concepts/cluster-administration/network-plugins.md
-  - docs/concepts/cluster-administration/logging.md
-  - docs/concepts/cluster-administration/kubelet-garbage-collection.md
-  - docs/concepts/cluster-administration/federation.md
-  - docs/concepts/cluster-administration/sysctl-cluster.md
-  - docs/concepts/cluster-administration/authenticate-across-clusters-kubeconfig.md
-  - docs/concepts/cluster-administration/master-node-communication.md
-  - docs/concepts/cluster-administration/proxies.md
-  - title: Policies
-    section:
-    - docs/concepts/policy/resource-quotas.md
-    - docs/concepts/policy/pod-security-policy.md
-
-

_data/docs-home.yml

@@ -1,23 +0,0 @@
-bigheader: "Documentation Home"
-abstract: "Documentation for using and learning about Kubernetes."
-toc:
-- docs/home/index.md
-
-- docs/home/index.md
-
-- title: Release Notes
-  path: https://git.k8s.io/kubernetes/CHANGELOG.md
-- title: Release Roadmap
-  path: https://github.com/kubernetes/kubernetes/milestones/
-
-- docs/tasks/debug-application-cluster/troubleshooting.md
-
-- title: Contributing to the Kubernetes Docs
-  section:
-  - editdocs.md
-  - docs/home/contribute/create-pull-request.md
-  - docs/home/contribute/write-new-topic.md
-  - docs/home/contribute/stage-documentation-changes.md
-  - docs/home/contribute/page-templates.md
-  - docs/home/contribute/review-issues.md
-  - docs/home/contribute/style-guide.md

_data/reference.yml

@@ -1,91 +0,0 @@
-bigheader: "Reference Documentation"
-abstract: "Design docs, concept definitions, and references for APIs and CLIs."
-toc:
-- docs/reference/index.md
-
-- title: Using the API
-  section:
-  - docs/reference/api-overview.md
-  - title: Accessing the API
-    section:
-    - docs/admin/accessing-the-api.md
-    - docs/admin/authentication.md
-    - docs/admin/bootstrap-tokens.md
-    - docs/admin/admission-controllers.md
-    - docs/admin/service-accounts-admin.md
-  - title: Authorization
-    section:
-    - docs/admin/authorization/index.md
-    - docs/admin/authorization/abac.md
-    - docs/admin/authorization/rbac.md
-    - docs/admin/authorization/webhook.md
-  - docs/reference/deprecation-policy.md
-
-- title: API Reference
-  section:
-  - title: v1.6
-    path: /docs/api-reference/v1.6/
-  - title: v1.5
-    path: /docs/api-reference/v1.5/
-  - docs/reference/labels-annotations-taints.md
-  - title: OpenAPI and Swagger
-    section:
-    - title: OpenAPI Spec
-      path: https://git.k8s.io/kubernetes/api/openapi-spec/
-    - title: Swagger Spec
-      path: https://git.k8s.io/kubernetes/api/swagger-spec/
-
-- title: Federation API
-  section:
-    - docs/reference/federation/v1/operations.html
-    - docs/reference/federation/v1/definitions.html
-    - docs/reference/federation/v1beta1/operations.html
-    - docs/reference/federation/v1beta1/definitions.html
-    - docs/reference/federation/extensions/v1beta1/operations.html
-    - docs/reference/federation/extensions/v1beta1/definitions.html
-
-- title: kubectl CLI
-  section:
-  - docs/user-guide/kubectl-overview.md
-  - title: v1.6 Commands
-    path: /docs/user-guide/kubectl/v1.6/
-  - title: v1.5 Commands
-    path: /docs/user-guide/kubectl/v1.5/
-  - docs/user-guide/docker-cli-to-kubectl.md
-  - docs/user-guide/kubectl-conventions.md
-  - docs/user-guide/jsonpath.md
-  - docs/user-guide/kubectl-cheatsheet.md
-
-- docs/admin/kubeadm.md
-
-- title: Config Reference
-  section:
-  - docs/admin/kubelet.md
-  - docs/admin/kube-apiserver.md
-  - docs/admin/kube-controller-manager.md
-  - docs/admin/kube-proxy.md
-  - docs/admin/kube-scheduler.md
-  - docs/admin/federation-apiserver.md
-  - docs/admin/federation-controller-manager.md
-
-- title: Kubernetes Design Docs
-  section:
-  - title: Kubernetes Architecture
-    path: https://git.k8s.io/community/contributors/design-proposals/architecture.md
-  - title: Kubernetes Design Overview
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.6/docs/design
-  - title: Kubernetes Identity and Access Management
-    path: https://git.k8s.io/community/contributors/design-proposals/access.md
-  - docs/admin/ovs-networking.md
-  - title: Security Contexts
-    path: https://git.k8s.io/community/contributors/design-proposals/security_context.md
-  - title: Security in Kubernetes
-    path: https://git.k8s.io/community/contributors/design-proposals/security.md
-
-- title: Kubernetes Issues and Security
-  section:
-  - title: Kubernetes Issue Tracker on GitHub
-    path: https://github.com/kubernetes/kubernetes/issues/
-  - docs/reference/security.md
-
-

_data/setup.yml

@@ -1,107 +0,0 @@
-bigheader: "Setup"
-abstract: "Instructions for setting up a Kubernetes cluster."
-toc:
-- docs/setup/index.md
-- docs/setup/pick-right-solution.md
-
-- title: Independent Solutions
-  section:
-  - docs/getting-started-guides/minikube.md
-
-  - title: Bootstrapping Clusters with kubeadm
-    section:
-    - docs/setup/independent/install-kubeadm.md
-    - docs/setup/independent/create-cluster-kubeadm.md
-
-  - docs/getting-started-guides/scratch.md
-  - docs/getting-started-guides/alternatives.md
-
-- title: Hosted Solutions
-  section:
-  - title: Running Kubernetes on Google Container Engine
-    path: https://cloud.google.com/container-engine/docs/before-you-begin/
-  - title: Running Kubernetes on Azure Container Service
-    path: https://docs.microsoft.com/en-us/azure/container-service/container-service-kubernetes-walkthrough
-  - title: Running Kubernetes on IBM Bluemix Container Service
-    path: https://console.ng.bluemix.net/docs/containers/container_index.html
-
-- title: Turn-key Cloud Solutions
-  section:
-  - docs/getting-started-guides/gce.md
-  - docs/getting-started-guides/aws.md
-  - docs/getting-started-guides/azure.md
-  - docs/getting-started-guides/clc.md
-  - title: Running Kubernetes on IBM Bluemix
-    path: https://github.com/patrocinio/kubernetes-softlayer
-  - docs/getting-started-guides/stackpoint.md
-
-- title: Custom Solutions
-
-  section:
-  - title: Custom Cloud Solutions
-    section:
-    - docs/getting-started-guides/coreos/index.md
-    - docs/getting-started-guides/ubuntu/index.md
-    - docs/getting-started-guides/kops.md
-    - docs/getting-started-guides/kubespray.md
-    - docs/getting-started-guides/running-cloud-controller.md
-
-  - title: On-Premise VMs
-    section:
-    - docs/getting-started-guides/coreos/index.md
-    - docs/getting-started-guides/cloudstack.md
-    - docs/getting-started-guides/vsphere.md
-    - docs/getting-started-guides/photon-controller.md
-    - docs/getting-started-guides/dcos.md
-    - docs/getting-started-guides/libvirt-coreos.md
-    - docs/getting-started-guides/ovirt.md
-    - docs/getting-started-guides/openstack-heat.md
-
-    - title: rkt
-      section:
-      - docs/getting-started-guides/rkt/index.md
-      - docs/getting-started-guides/rkt/notes.md
-
-    - docs/getting-started-guides/mesos/index.md
-    - docs/getting-started-guides/mesos-docker.md
-
-    - title: Bare Metal
-      section:
-      - docs/getting-started-guides/coreos/bare_metal_offline.md
-      - docs/getting-started-guides/fedora/fedora_ansible_config.md
-      - docs/getting-started-guides/fedora/fedora_manual_config.md
-      - docs/getting-started-guides/fedora/flannel_multi_node_cluster.md
-      - docs/getting-started-guides/centos/centos_manual_config.md
-      - docs/getting-started-guides/coreos/index.md
-      - docs/getting-started-guides/ubuntu/index.md
-
-      - title: Ubuntu
-        section:
-        - docs/getting-started-guides/ubuntu/index.md
-        - docs/getting-started-guides/ubuntu/validation.md
-        - docs/getting-started-guides/ubuntu/backups.md
-        - docs/getting-started-guides/ubuntu/upgrades.md
-        - docs/getting-started-guides/ubuntu/scaling.md
-        - docs/getting-started-guides/ubuntu/installation.md
-        - docs/getting-started-guides/ubuntu/monitoring.md
-        - docs/getting-started-guides/ubuntu/networking.md
-        - docs/getting-started-guides/ubuntu/security.md
-        - docs/getting-started-guides/ubuntu/storage.md
-        - docs/getting-started-guides/ubuntu/troubleshooting.md
-        - docs/getting-started-guides/ubuntu/decommissioning.md
-        - docs/getting-started-guides/ubuntu/operational-considerations.md
-        - docs/getting-started-guides/ubuntu/glossary.md
-        - docs/getting-started-guides/ubuntu/local.md
-        - docs/getting-started-guides/ubuntu/logging.md
-        - docs/getting-started-guides/ubuntu/manual.md
-
-    - docs/getting-started-guides/windows/index.md
-
-  - docs/admin/node-conformance.md
-
-- docs/concepts/cluster-administration/addons.md
-- docs/admin/salt.md
-- docs/admin/cluster-large.md
-- docs/admin/multiple-zones.md
-- docs/admin/high-availability/index.md
-- docs/getting-started-guides/binary_release.md

_data/tasks.yml

@@ -1,159 +0,0 @@
-bigheader: "Tasks"
-abstract: "Step-by-step instructions for performing operations with Kubernetes."
-toc:
-- docs/tasks/index.md
-
-- title: Install Tools
-  section:
-  - docs/tasks/tools/install-kubectl.md
-  - docs/tasks/tools/install-minikube.md
-  - docs/setup/independent/install-kubeadm.md
-
-- title: Configure Pods and Containers
-  section:
-  - docs/tasks/configure-pod-container/assign-cpu-ram-container.md
-  - docs/tasks/configure-pod-container/configure-volume-storage.md
-  - docs/tasks/configure-pod-container/configure-persistent-volume-storage.md
-  - docs/tasks/configure-pod-container/configure-projected-volume-storage.md
-  - docs/tasks/configure-pod-container/projected-volume.md
-  - docs/tasks/configure-pod-container/security-context.md
-  - docs/tasks/configure-pod-container/environment-variable-expose-pod-information.md
-  - docs/tasks/configure-pod-container/configure-service-account.md
-  - docs/tasks/configure-pod-container/pull-image-private-registry.md
-  - docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
-  - docs/tasks/configure-pod-container/assign-pods-nodes.md
-  - docs/tasks/configure-pod-container/configure-pod-initialization.md
-  - docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md
-  - docs/tasks/configure-pod-container/configmap.md
-  - docs/tasks/configure-pod-container/configure-pod-configmap.md
-  - docs/tools/kompose/user-guide.md
-
-- title: Inject Data Into Applications
-  section:
-  - docs/tasks/inject-data-application/define-command-argument-container.md
-  - docs/tasks/inject-data-application/define-environment-variable-container.md
-  - docs/tasks/inject-data-application/environment-variable-expose-pod-information.md
-  - docs/tasks/inject-data-application/downward-api-volume-expose-pod-information.md
-  - docs/tasks/inject-data-application/distribute-credentials-secure.md
-  - docs/tasks/inject-data-application/podpreset.md
-
-- title: Run Applications
-  section:
-  - docs/tasks/run-application/run-stateless-application-deployment.md
-  - docs/tasks/run-application/run-single-instance-stateful-application.md
-  - docs/tasks/run-application/run-replicated-stateful-application.md
-  - docs/tasks/run-application/upgrade-pet-set-to-stateful-set.md
-  - docs/tasks/run-application/scale-stateful-set.md
-  - docs/tasks/run-application/delete-stateful-set.md
-  - docs/tasks/run-application/force-delete-stateful-set-pod.md
-  - docs/tasks/run-application/rolling-update-replication-controller.md
-  - docs/tasks/run-application/horizontal-pod-autoscale.md
-  - docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md
-
-- title: Run Jobs
-  section:
-  - docs/tasks/job/parallel-processing-expansion.md
-  - docs/tasks/job/coarse-parallel-processing-work-queue/index.md
-  - docs/tasks/job/fine-parallel-processing-work-queue/index.md
-
-- title: Access Applications in a Cluster
-  section:
-  - docs/tasks/access-application-cluster/web-ui-dashboard.md
-  - docs/tasks/access-application-cluster/access-cluster.md
-  - docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig.md
-  - docs/tasks/access-application-cluster/port-forward-access-application-cluster.md
-  - docs/tasks/access-application-cluster/load-balance-access-application-cluster.md
-  - docs/tasks/access-application-cluster/service-access-application-cluster.md
-  - docs/tasks/access-application-cluster/connecting-frontend-backend.md
-  - docs/tasks/access-application-cluster/create-external-load-balancer.md
-  - docs/tasks/access-application-cluster/configure-cloud-provider-firewall.md
-  - docs/tasks/access-application-cluster/list-all-running-container-images.md
-  - docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md
-  - title: Configuring DNS for a Cluster
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.5/examples/cluster-dns
-
-- title: Monitor, Log, and Debug
-  section:
-  - docs/tasks/debug-application-cluster/resource-usage-monitoring.md
-  - docs/tasks/debug-application-cluster/get-shell-running-container.md
-  - docs/tasks/debug-application-cluster/monitor-node-health.md
-  - docs/tasks/debug-application-cluster/logging-stackdriver.md
-  - docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md
-  - docs/tasks/debug-application-cluster/determine-reason-pod-failure.md
-  - docs/tasks/debug-application-cluster/debug-init-containers.md
-  - docs/tasks/debug-application-cluster/debug-pod-replication-controller.md
-  - docs/tasks/debug-application-cluster/debug-service.md
-  - docs/tasks/debug-application-cluster/debug-cluster.md
-  - docs/tasks/debug-application-cluster/debug-application.md
-  - docs/tasks/debug-application-cluster/debug-stateful-set.md
-  - docs/tasks/debug-application-cluster/debug-application-introspection.md
-  - docs/tasks/debug-application-cluster/audit.md
-  - title: Use Explorer to Examine the Runtime Environment
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.5/examples/explorer
-
-- title: Access and Extend the Kubernetes API
-  section:
-  - docs/tasks/access-kubernetes-api/http-proxy-access-api.md
-  - docs/tasks/access-kubernetes-api/extend-api-third-party-resource.md
-
-- title: TLS
-  section:
-  - docs/tasks/tls/managing-tls-in-a-cluster.md
-
-- title: Administer a Cluster
-  section:
-  - docs/tasks/administer-cluster/access-cluster-api.md
-  - docs/tasks/administer-cluster/access-cluster-services.md
-  - docs/tasks/administer-cluster/configure-upgrade-etcd.md
-  - docs/tasks/administer-cluster/apply-resource-quota-limit.md
-  - docs/tasks/administer-cluster/out-of-resource.md
-  - docs/tasks/administer-cluster/cpu-memory-limit.md
-  - docs/tasks/administer-cluster/reserve-compute-resources.md
-  - docs/tasks/administer-cluster/static-pod.md
-  - docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods.md
-  - docs/tasks/administer-cluster/cluster-management.md
-  - docs/tasks/administer-cluster/upgrade-1-6.md
-  - docs/tasks/administer-cluster/namespaces.md
-  - docs/tasks/administer-cluster/namespaces-walkthrough.md
-  - docs/tasks/administer-cluster/dns-horizontal-autoscaling.md
-  - docs/tasks/administer-cluster/safely-drain-node.md
-  - docs/tasks/administer-cluster/declare-network-policy.md
-  - docs/tasks/administer-cluster/calico-network-policy.md
-  - docs/tasks/administer-cluster/romana-network-policy.md
-  - docs/tasks/administer-cluster/weave-network-policy.md
-  - docs/tasks/administer-cluster/change-pv-reclaim-policy.md
-  - docs/tasks/administer-cluster/configure-pod-disruption-budget.md
-  - docs/tasks/administer-cluster/limit-storage-consumption.md
-  - docs/tasks/administer-cluster/change-default-storage-class.md
-  - docs/tasks/administer-cluster/share-configuration.md
-  - docs/tasks/administer-cluster/running-cloud-controller.md
-  - docs/tasks/administer-cluster/highly-available-master.md
-  - docs/tasks/administer-cluster/configure-multiple-schedulers.md
-  - docs/tasks/administer-cluster/ip-masq-agent.md
-  - title: Change Cluster Size
-    path: https://github.com/kubernetes/kubernetes/wiki/User-FAQ#how-do-i-change-the-size-of-my-cluster/
-
-- title: Federation - Run an App on Multiple Clusters
-  section:
-  - docs/tasks/federation/federation-service-discovery.md
-  - docs/tasks/federation/set-up-cluster-federation-kubefed.md
-  - docs/tasks/federation/set-up-coredns-provider-federation.md
-  - docs/tasks/administer-federation/cluster.md
-  - docs/tasks/administer-federation/configmap.md
-  - docs/tasks/administer-federation/daemonset.md
-  - docs/tasks/administer-federation/deployment.md
-  - docs/tasks/administer-federation/events.md
-  - docs/tasks/administer-federation/ingress.md
-  - docs/tasks/administer-federation/namespaces.md
-  - docs/tasks/administer-federation/replicaset.md
-  - docs/tasks/administer-federation/secret.md
-
-- title: Manage Cluster Daemons
-  section:
-  - docs/tasks/manage-daemon/update-daemon-set.md
-
-- title: Manage GPUs
-  section:
-  - docs/tasks/manage-gpus/scheduling-gpus.md
-
-

_data/tutorials.yml

@@ -1,64 +0,0 @@
-bigheader: "Tutorials"
-abstract: "Detailed walkthroughs of common Kubernetes operations and workflows."
-toc:
-- docs/tutorials/index.md
-- title: Kubernetes Basics
-  section:
-  - docs/tutorials/kubernetes-basics/index.html
-  - title: 1. Create a Cluster
-    section:
-    - docs/tutorials/kubernetes-basics/cluster-intro.html
-    - docs/tutorials/kubernetes-basics/cluster-interactive.html
-  - title: 2. Deploy an App
-    section:
-    - docs/tutorials/kubernetes-basics/deploy-intro.html
-    - docs/tutorials/kubernetes-basics/deploy-interactive.html
-  - title: 3. Explore Your App
-    section:
-    - docs/tutorials/kubernetes-basics/explore-intro.html
-    - docs/tutorials/kubernetes-basics/explore-interactive.html
-  - title: 4. Expose Your App Publicly
-    section:
-    - docs/tutorials/kubernetes-basics/expose-intro.html
-    - docs/tutorials/kubernetes-basics/expose-interactive.html
-  - title: 5. Scale Your App
-    section:
-    - docs/tutorials/kubernetes-basics/scale-intro.html
-    - docs/tutorials/kubernetes-basics/scale-interactive.html
-  - title: 6. Update Your App
-    section:
-    - docs/tutorials/kubernetes-basics/update-intro.html
-    - docs/tutorials/kubernetes-basics/update-interactive.html
-- title: Online Training Course
-  path: https://www.udacity.com/course/scalable-microservices-with-kubernetes--ud615
-- docs/tutorials/stateless-application/hello-minikube.md
-- title: Configuration
-  section:
-  - docs/tutorials/configuration/configure-redis-using-configmap.md
-- title: Object Management Using kubectl
-  section:
-  - docs/tutorials/object-management-kubectl/object-management.md
-  - docs/tutorials/object-management-kubectl/imperative-object-management-command.md
-  - docs/tutorials/object-management-kubectl/imperative-object-management-configuration.md
-  - docs/tutorials/object-management-kubectl/declarative-object-management-configuration.md
-- title: Stateless Applications
-  section:
-  - docs/tasks/run-application/run-stateless-application-deployment.md
-  - docs/tutorials/stateless-application/guestbook.md
-  - docs/tasks/access-application-cluster/service-access-application-cluster.md
-  - docs/tutorials/stateless-application/expose-external-ip-address.md
-- title: Stateful Applications
-  section:
-  - docs/tutorials/stateful-application/basic-stateful-set.md
-  - docs/tasks/run-application/run-single-instance-stateful-application.md
-  - docs/tasks/run-application/run-replicated-stateful-application.md
-  - docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md
-  - docs/tutorials/stateful-application/cassandra.md
-  - docs/tutorials/stateful-application/zookeeper.md
-- title: Clusters
-  section:
-  - docs/tutorials/clusters/apparmor.md
-- title: Services
-  section:
-  - docs/tutorials/services/source-ip.md
-

_includes/api-reference-content-moved.md

@@ -1,2 +0,0 @@
-The topics in the `/docs/api-reference/` section of the Kubernetes docs
-are being moved to the [Reference](/docs/reference/) section. The content in this topic has moved to:

_includes/code.html

@@ -1,26 +0,0 @@
-{% capture samplecode %}{% include_relative {{include.file}} %}{% endcapture %}
-{% if include.k8slink %}{% capture ghlink %}https://raw.githubusercontent.com/kubernetes/kubernetes/blob/{{page.githubbranch}}{{include.k8slink}}{% endcapture %}{% endif %}
-{% if include.ghlink %}{% capture ghlink %}https://raw.githubusercontent.com/kubernetes/kubernetes.github.io/{{page.docsbranch}}{{include.ghlink}}{% endcapture %}{% endif %}
-{% capture mysample %}
-```{{include.language}}
-{{ samplecode | raw | strip }}
-```
-{: id="{{include.file | handleize}}"}
-{% endcapture %}
-<table class="includecode">
-    <thead>
-        <tr>
-            <th>
-                {% if ghlink %}<a href="{{ghlink}}" download="{{include.file}}">{% endif %}
-                    <code>{{include.file}}</code>
-                {% if ghlink %}</a>{% endif %}
-                <img src="/images/copycode.svg" style="max-height:24px" onclick="copyCode('{{include.file | handleize}}')" title="Copy {{include.file}} to clipboard">
-            </th>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>{{ mysample | markdownify }}</td>
-        </tr>
-    </tbody>
-</table>

_includes/default-storage-class-prereqs.md

@@ -1,6 +0,0 @@
-You need to either have a dynamic PersistentVolume provisioner with a default
-[StorageClass](/docs/user-guide/persistent-volumes/#storageclasses),
-or [statically provision PersistentVolumes](/docs/user-guide/persistent-volumes/#provisioning)
-yourself to satisfy the [PersistentVolumeClaims](/docs/user-guide/persistent-volumes/#persistentvolumeclaims)
-used here.
-

_includes/feature-dialog.md

@@ -1,28 +0,0 @@
-<a href="#" id="feature-state-dialog-link" class="ui-state-default ui-corner-all"><span class="ui-icon ui-icon-newwin"></span>{{ dialog_title }}</a>
-<div id="feature-state-dialog" class="ui-dialog-content" title="{{ dialog_title }}">
-{{ dialog_content | markdownify }}
-</div>
-{% raw %}<script>
-$(function(){
-    
-    $( "#feature-state-dialog" ).dialog({
-        autoOpen: false,
-        width: {% endraw %}{{ dialog_width | default: "600" }}{% raw %},
-        buttons: [
-            {
-                text: "Ok",
-                click: function() {
-                    $( this ).dialog( "close" );
-                }
-            }
-        ]
-    });
-
-    // Link to open the dialog
-    $( "#feature-state-dialog-link" ).click(function( event ) {
-        $( "#feature-state-dialog" ).dialog( "open" );
-        event.preventDefault();
-    });
-
-});
-</script>{% endraw %}

_includes/feature-state-alpha.md

@@ -1,13 +0,0 @@
-{% assign dialog_title = "alpha" %}
-{% capture dialog_content %}
-This feature is currently in a *alpha* state, meaning:
-
-* The version names contain alpha (e.g. v1alpha1).
-* Might be buggy. Enabling the feature may expose bugs. Disabled by default.
-* Support for feature may be dropped at any time without notice.
-* The API may change in incompatible ways in a later software release without notice.
-* Recommended for use only in short-lived testing clusters, due to increased risk of bugs and lack of long-term support.
-
-{% endcapture %}
-
-**FEATURE STATE:** `Kubernetes {{ for_k8s_version | default: page.version }}` {% include feature-dialog.md %}

_includes/feature-state-beta.md

@@ -1,14 +0,0 @@
-{% assign dialog_title = "beta" %}
-{% capture dialog_content %}
-This feature is currently in a *beta* state, meaning:
-
-* The version names contain beta (e.g. v2beta3).
-* Code is well tested. Enabling the feature is considered safe. Enabled by default.
-* Support for the overall feature will not be dropped, though details may change.
-* The schema and/or semantics of objects may change in incompatible ways in a subsequent beta or stable release. When this happens, we will provide instructions for migrating to the next version. This may require deleting, editing, and re-creating API objects. The editing process may require some thought. This may require downtime for applications that rely on the feature.
-* Recommended for only non-business-critical uses because of potential for incompatible changes in subsequent releases. If you have multiple clusters that can be upgraded independently, you may be able to relax this restriction.
-* **Please do try our beta features and give feedback on them! After they exit beta, it may not be practical for us to make more changes.**
-
-{% endcapture %}
-
-**FEATURE STATE:** `Kubernetes {{ for_k8s_version | default: page.version }}` {% include feature-dialog.md %}

_includes/feature-state-deprecated.md

@@ -1,6 +0,0 @@
-{% assign dialog_title = "deprecated" %}
-{% capture dialog_content %}
-This feature is *deprecated*. For more information on this state, see the [Kubernetes Deprecation Policy](/docs/reference/deprecation-policy/).
-{% endcapture %}
-
-**DEPRECATION NOTICE:** As of `Kubernetes {{ for_k8s_version | default: page.version }}`, this has been {% include feature-dialog.md %}

_includes/feature-state-stable.md

@@ -1,10 +0,0 @@
-{% assign dialog_title = "stable" %}
-{% capture dialog_content %}
-This feature is *stable*, meaning:
-
-* The version name is vX where X is an integer.
-* Stable versions of features will appear in released software for many subsequent versions.
-
-{% endcapture %}
-
-**FEATURE STATE:** `Kubernetes {{ for_k8s_version | default: page.version }}` {% include feature-dialog.md %}

_includes/federated-task-tutorial-prereqs.md

@@ -1,8 +0,0 @@
-This guide assumes that you have a running Kubernetes Cluster
-Federation installation. If not, then head over to the
-[federation admin guide](/docs/tutorials/federation/set-up-cluster-federation-kubefed/) to learn how to
-bring up a cluster federation (or have your cluster administrator do
-this for you).
-Other tutorials, such as Kelsey Hightower's 
-[Federated Kubernetes Tutorial](https://github.com/kelseyhightower/kubernetes-cluster-federation),
-might also help you create a Federated Kubernetes cluster.

_includes/federation-content-moved.md

@@ -1,2 +0,0 @@
-The topics in the [Federation API](/docs/federation/api-reference/) section of the Kubernetes docs
-are being moved to the [Reference](/docs/reference/) section. The content in this topic has moved to:

_includes/footer-scripts.html

@@ -1,53 +0,0 @@
-<button class="flyout-button" onclick="kub.toggleToc()"></button>
-
-<style>
-.cse .gsc-control-cse, .gsc-control-cse, {
-    padding: 0;
-}
-  .gsc-control-cse table, .gsc-control-cse-en table {
-      margin:0px !important;
-  }
-  .gsc-above-wrapper-area {
-      border-bottom: 0;
-  }
-</style>
-
-<script>
-(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
-    (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
-m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
-})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
-ga('create', 'UA-36037335-10', 'auto');
-ga('send', 'pageview');
-
-// hide docs nav area if no nav is present, or if nav only contains a link to the current page
-(function () {
-    window.addEventListener('DOMContentLoaded', init)
-
-        // play nice with our neighbors
-        function init() {
-            window.removeEventListener('DOMContentLoaded', init)
-                hideNav()
-        }
-
-    function hideNav(toc){
-        if (!toc) toc = document.querySelector('#docsToc')
-            var container = toc.querySelector('.container')
-
-                // container is built dynamically, so it may not be present on the first runloop
-                if (container) {
-                    if (container.childElementCount === 0 || toc.querySelectorAll('a.item').length === 1) {
-                        toc.style.display = 'none'
-                            document.getElementById('docsContent').style.width = '100%'
-                    }
-                } else {
-                    requestAnimationFrame(function () {
-                        hideNav(toc)
-                    })
-                }
-    }
-})();
-</script>
-
-<!-- Commenting out AnswerDash for now; we need to work on our list of questions/answers/design first
-    <!-- Start of AnswerDash script <script>var AnswerDash;!function(e,t,n,s,a){if(!t.getElementById(s)){var i,r=t.createElement(n),c=t.getElementsByTagName(n)[0];e[a]||(i=e[a]=function(){i.__oninit.push(arguments)},i.__oninit=[]),r.type="text/javascript",r.async=!0,r.src="https://p1.answerdash.com/answerdash.min.js?siteid=756",r.setAttribute("id",s),c.parentNode.insertBefore(r,c)}}(window,document,"script","answerdash-script","AnswerDash");</script> <!-- End of AnswerDash script -->

_includes/footer.html

@@ -1,34 +0,0 @@
-<footer>
-    <main class="light-text">
-        <nav>
-            <a href="/docs/tutorials/stateless-application/hello-minikube/">Get Started</a>
-            <a href="/docs/home/">Documentation</a>
-            <a href="http://blog.kubernetes.io/">Blog</a>
-            <a href="/partners/">Partners</a>
-            <a href="/community/">Community</a>
-            <a href="/case-studies/">Case Studies</a>
-        </nav>
-        <div class="social">
-            <div>
-                <a href="https://twitter.com/kubernetesio" class="twitter"><span>twitter</span></a>
-                <a href="https://github.com/kubernetes/kubernetes" class="github"><span>Github</span></a>
-                <a href="http://slack.k8s.io/" class="slack"><span>Slack</span></a>
-            </div>
-            <div>
-                <a href="http://stackoverflow.com/questions/tagged/kubernetes" class="stack-overflow"><span>Stack Overflow</span></a>
-                <a href="https://groups.google.com/forum/#!forum/kubernetes-users" class="mailing-list"><span>Mailing List</span></a>
-                <a href="https://calendar.google.com/calendar/embed?src=nt2tcnbtbied3l6gi2h29slvc0%40group.calendar.google.com" class="calendar"><span>Events Calendar</span></a>
-            </div>
-            <div>
-                <a href="/docs/setup/pick-right-solution/" class="button">Get Kubernetes</a>
-                <a href="https://github.com/kubernetes/kubernetes" class="button">Contribute</a>
-            </div>
-        </div>
-        <div id="miceType" class="center">
-            &copy; {{ 'now' | date: "%Y" }} The Kubernetes Authors | Documentation Distributed under <a href="https://git.k8s.io/kubernetes.github.io/LICENSE" class="light-text">CC BY 4.0</a>
-        </div>
-        <div id="miceType" class="center">
-            Copyright &copy; {{ 'now' | date: "%Y" }} The Linux Foundation&reg;. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page: <a href="https://www.linuxfoundation.org/trademark-usage" class="light-text">https://www.linuxfoundation.org/trademark-usage</a>
-        </div>
-    </main>
-</footer>

_includes/head.html

@@ -1,24 +0,0 @@
-<head>
-    <meta charset="utf-8">
-    <meta name="viewport" content="width=device-width, initial-scale=1">
-    <link rel="shortcut icon" type="image/png" href="/images/favicon.png">
-    <link rel="stylesheet" type="text/css" href="https://fonts.googleapis.com/css?family=Roboto:400,100,100italic,300,300italic,400italic,500,500italic,700,700italic,900,900italic">
-    <link rel="stylesheet" type="text/css" href="https://fonts.googleapis.com/css?family=Roboto+Mono">
-    <link rel="stylesheet" type="text/css" href="/css/styles.css">
-    <link rel="stylesheet" type="text/css" href="/css/jquery-ui.min.css">
-    <link rel="stylesheet" type="text/css" href="/css/sweetalert.css">
-    {% if page.class == "gridPage" %}<link rel="stylesheet" type="text/css" href="/css/gridpage.css">{% endif %}
-
-    {% if page.description %}
-    <meta name="description" content="{{ page.description }}" />
-    {% else %}
-    <meta name="description" content="{{ page.title }}" />
-    {% endif %}
-
-    <script src="/js/jquery-2.2.0.min.js"></script>
-    <script src="/js/jquery-ui.min.js"></script>
-    <script src="/js/script.js"></script>
-    <script src="/js/sweetalert.min.js"></script>
-    <script src="/js/bootstrap.min.js"></script>
-    {% seo %}
-</head>

_includes/header.html

@@ -1,58 +0,0 @@
-<div id="cellophane" onclick="kub.toggleMenu()"></div>
-
-<header>
-    <a href="/" class="logo"></a>
-
-    <div class="nav-buttons" data-auto-burger="primary">
-        <ul class="global-nav">
-            <li><a href="/docs/home/">Documentation</a></li>
-            <li><a href="http://blog.kubernetes.io/">Blog</a></li>
-            <li><a href="/partners/">Partners</a></li>
-            <li><a href="/community/">Community</a></li>
-            <li><a href="/case-studies/">Case Studies</a></li>
-        </ul>
-        <!-- <a href="/docs/home" class="button" id="viewDocs" data-auto-burger-exclude>View Documentation</a> -->
-        <a href="/docs/tutorials/kubernetes-basics/" class="button" id="tryKubernetes" data-auto-burger-exclude>Try Kubernetes</a>
-        <button id="hamburger" onclick="kub.toggleMenu()" data-auto-burger-exclude><div></div></button>
-    </div>
-
-    <nav id="mainNav">
-        <main data-auto-burger="primary">
-        <div class="nav-box">
-            <h3><a href="/docs/tutorials/stateless-application/hello-minikube/">Get Started</a></h3>
-            <p>Ready to get your hands dirty? Build a simple Kubernetes cluster that runs "Hello World" for Node.js.</p>
-        </div>
-        <div class="nav-box">
-            <h3><a href="/docs/home/">Documentation</a></h3>
-            <p>Learn how to use Kubernetes with the use of walkthroughs, samples, and reference documentation. You can even <a href="/editdocs/" data-auto-burger-exclude>help contribute to the docs</a>!</p>
-        </div>
-        <div class="nav-box">
-            <h3><a href="/community/">Community</a></h3>
-            <p>If you need help, you can connect with other Kubernetes users and the Kubernetes authors, attend community events, and watch video presentations from around the web.</p>
-        </div>
-        <div class="nav-box">
-            <h3><a href="http://blog.kubernetes.io">Blog</a></h3>
-            <p>Read the latest news for Kubernetes and the containers space in general, and get technical how-tos hot off the presses.</p>
-        </div>
-        </main>
-        <main data-auto-burger="primary">
-        <div class="left">
-            <h5 class="github-invite">Interested in hacking on the core Kubernetes code base?</h5>
-            <a href="https://github.com/kubernetes/kubernetes" class="button" data-auto-burger-exclude>View On Github</a>
-        </div>
-
-        <div class="right">
-            <h5 class="github-invite">Explore the community</h5>
-            <div class="social">
-                <a href="https://twitter.com/kubernetesio" class="twitter"><span>Twitter</span></a>
-                <a href="https://github.com/kubernetes/kubernetes" class="github"><span>Github</span></a>
-                <a href="http://slack.k8s.io/" class="slack"><span>Slack</span></a>
-                <a href="http://stackoverflow.com/questions/tagged/kubernetes" class="stack-overflow"><span>Stack Overflow</span></a>
-                <a href="https://groups.google.com/forum/#!forum/kubernetes-users" class="mailing-list"><span>Mailing List</span></a>
-                <a href="https://calendar.google.com/calendar/embed?src=nt2tcnbtbied3l6gi2h29slvc0%40group.calendar.google.com" class="calendar"><span>Events Calendar</span></a>
-            </div>
-        </div>
-        <div class="clear" style="clear: both"></div>
-        </main>
-    </nav>
-</header>

_includes/partner-script.js

@@ -1,559 +0,0 @@
-;(function () {
-	var partners = [
-		{
-			type: 0,
-			name: 'CoreOS',
-			logo: 'core_os',
-			link: 'https://tectonic.com/',
-			blurb: 'Tectonic is the enterprise-ready Kubernetes product, by CoreOS. It adds key features to allow you to manage, update, and control clusters in production.'
-		},
-		{
-			type: 0,
-			name: 'Deis',
-			logo: 'deis',
-			link: 'https://deis.com',
-			blurb: 'Deis the creators of Helm, Workflow, and Steward, helps developers and operators build, deploy, manage and scale their applications on top of Kubernetes.'
-		},
-		{
-			type: 0,
-			name: 'StackPointCloud',
-			logo: 'stackpoint',
-			link: 'https://stackpoint.io',
-			blurb: 'StackPointCloud builds Stackpoint.io, the universal control plane for Kubernetes Anywhere -- compose and build your own infrastructure as easily as a DigitalOcean droplet at any public cloud provider.'
-		},
-		{
-			type: 0,
-			name: 'Sysdig Cloud',
-			logo: 'sys_dig',
-			link: 'https://sysdig.com/blog/monitoring-kubernetes-with-sysdig-cloud/',
-			blurb: 'Container native monitoring with deep support for Kubernetes.'
-		},
-		{
-			type: 0,
-			name: 'Puppet',
-			logo: 'puppet',
-			link: 'https://puppet.com/blog/managing-kubernetes-configuration-puppet',
-			blurb: 'The Puppet module for Kubernetes makes it easy to manage Pods, Replication Controllers, Services and more in Kubernetes, and to build domain-specific interfaces to one\'s Kubernetes configuration.'
-		},
-		{
-			type: 0,
-			name: 'Citrix',
-			logo: 'citrix',
-			link: 'http://wercker.com/workflows/partners/kubernetes/',
-			blurb: 'Netscaler CPX gives app developers all the features they need to load balance their microservices and containerized apps with Kubernetes.'
-		},
-		{
-			type: 0,
-			name: 'Cockroach Labs',
-			logo: 'cockroach_labs',
-			link: 'https://www.cockroachlabs.com/blog/running-cockroachdb-on-kubernetes/',
-			blurb: 'CockroachDB is a distributed SQL database whose built-in replication and survivability model pair with Kubernetes to truly make data easy.'
-		},
-		{
-			type: 0,
-			name: 'Skippbox',
-			logo: 'skippbox',
-			link: 'http://www.skippbox.com/tag/products/',
-			blurb: 'Creator of Cabin the first mobile application for Kubernetes, and kompose. Skippbox’s solutions distill all the power of k8s in simple easy to use interfaces.'
-		},
-		{
-			type: 0,
-			name: 'Weave Works',
-			logo: 'weave_works',
-			link: ' https://weave.works/kubernetes',
-			blurb: 'Weaveworks enables Developers and Dev/Ops teams to easily connect, deploy, secure, manage, and troubleshoot microservices in Kubernetes.'
-		},
-		{
-			type: 0,
-			name: 'Wercker',
-			logo: 'wercker',
-			link: 'http://wercker.com/workflows/partners/kubernetes/',
-			blurb: 'Wercker automates your build, test and deploy pipelines for launching containers and triggering rolling updates on your Kubernetes cluster. '
-		},
-		{
-			type: 0,
-			name: 'Rancher',
-			logo: 'rancher',
-			link: 'http://rancher.com/kubernetes/',
-			blurb: 'Rancher is an open-source, production-ready container management platform that makes it easy to deploy and leverage Kubernetes in the enterprise.'
-		},
-		{
-			type: 0,
-			name: 'Red Hat',
-			logo: 'redhat',
-			link: 'https://www.openshift.com/',
-			blurb: 'Leverage an enterprise Kubernetes platform to orchestrate complex, multi-container apps.'
-		},
-		{
-			type: 0,
-			name: 'Intel',
-			logo: 'intel',
-			link: 'https://tectonic.com/press/intel-coreos-collaborate-on-openstack-with-kubernetes.html',
-			blurb: 'Powering the GIFEE (Google’s Infrastructure for Everyone Else), to run OpenStack deployments on Kubernetes.'
-		},
-		{
-			type: 0,
-			name: 'ElasticKube',
-			logo: 'elastickube',
-			link: 'https://www.ctl.io/elastickube-kubernetes/',
-			blurb: 'Self-service container management for Kubernetes.'
-		},
-		{
-			type: 0,
-			name: 'Platform9',
-			logo: 'platform9',
-			link: 'https://platform9.com/products/kubernetes/',
-			blurb: 'Platform9 is the open source-as-a-service company that takes all of the goodness of Kubernetes and delivers it as a managed service.'
-		},
-		{
-			type: 0,
-			name: 'Datadog',
-			logo: 'datadog',
-			link: 'http://docs.datadoghq.com/integrations/kubernetes/',
-			blurb: 'Full-stack observability for dynamic infrastructure & applications. Includes precision alerting, analytics and deep Kubernetes integrations. '
-		},
-		{
-			type: 0,
-			name: 'AppFormix',
-			logo: 'appformix',
-			link: 'http://www.appformix.com/solutions/appformix-for-kubernetes/',
-			blurb: 'AppFormix is a cloud infrastructure performance optimization service helping enterprise operators streamline their cloud operations on any Kubernetes cloud. '
-		},
-		{
-			type: 0,
-			name: 'Crunchy',
-			logo: 'crunchy',
-			link: 'http://info.crunchydata.com/blog/advanced-crunchy-containers-for-postgresql',
-			blurb: 'Crunchy PostgreSQL Container Suite is a set of containers for managing PostgreSQL with DBA microservices leveraging Kubernetes and Helm.'
-		},
-		{
-			type: 0,
-			name: 'Aqua',
-			logo: 'aqua',
-			link: 'http://blog.aquasec.com/security-best-practices-for-kubernetes-deployment',
-			blurb: 'Deep, automated security for your containers running on Kubernetes.'
-		},
-		{
-			type: 0,
-			name: 'Canonical',
-			logo: 'canonical',
-			link: 'https://jujucharms.com/canonical-kubernetes/',
-			blurb: 'The Canonical Distribution of Kubernetes enables you to operate Kubernetes clusters on demand on any major public cloud and private	infrastructure.'
-		},
-		{
-			type: 0,
-			name: 'Distelli',
-			logo: 'distelli',
-			link: 'https://www.distelli.com/',
-			blurb: 'Pipelines from your source repositories to your Kubernetes Clusters on any cloud.'
-		},
-		{
-			type: 0,
-			name: 'Nuage networks',
-			logo: 'nuagenetworks',
-			link: 'https://github.com/nuagenetworks/nuage-kubernetes',
-			blurb: 'The Nuage SDN platform provides policy-based networking between Kubernetes Pods and non-Kubernetes environments with visibility and security monitoring.'
-		},
-		{
-			type: 0,
-			name: 'Sematext',
-			logo: 'sematext',
-			link: 'https://sematext.com/kubernetes/',
-			blurb: 'Logging & Monitoring: Automatic collection and processing of Metrics, Events and Logs for auto-discovered pods and Kubernetes nodes.'
-		},
-		{
-			type: 0,
-			name: 'Diamanti',
-			logo: 'diamanti',
-			link: 'https://www.diamanti.com/products/',
-			blurb: 'Diamanti deploys containers with guaranteed performance using Kubernetes in the first hyperconverged appliance purpose built for containerized applications.'
-		},
-		{
-			type: 0,
-			name: 'Apprenda',
-			logo: 'apprenda',
-			link: 'https://apprenda.com/kubernetes-support/',
-			blurb: 'Apprenda creates and supports modern, enterprise-ready application platforms for both cloud native and traditional application workloads.'
-		},
-		{
-			type: 0,
-			name: 'Aporeto',
-			logo: 'aporeto',
-			link: 'https://aporeto.com/trireme',
-			blurb: 'Aporeto makes cloud-native applications secure by default without impacting developer velocity and works at any scale, on any cloud.'
-		},
-		{
-  		type: 0,
- 			name: 'Giant Swarm',
- 			logo: 'giant_swarm',
- 			link: 'https://giantswarm.io',
- 			blurb: 'Giant Swarm provides fully-managed Kubernetes Clusters in your location of choice, so you can focus on your product.'
- 		},
-		{
- 			type: 0,
- 			name: 'Mirantis',
- 			logo: 'mirantis',
- 			link: 'https://content.mirantis.com/Containerizing-OpenStack-on-Kubernetes-Video-Landing-Page.html',
- 			blurb: 'Mirantis builds and manages private clouds with open source software such as OpenStack, deployed as containers orchestrated by Kubernetes.'
- 		},
-		{
- 			type: 0,
- 			name: 'Kubernetic',
- 			logo: 'kubernetic',
- 			link: 'https://kubernetic.com/',
- 			blurb: 'Kubernetic is a Kubernetes Desktop client that simplifies and democratizes cluster management for DevOps.'
- 		},
-		{
-			type: 1,
-			name: 'Apprenda',
-			logo: 'apprenda',
-			link: 'https://apprenda.com/kubernetes-support/',
-			blurb: 'Apprenda offers flexible and wide range of support plans for pure play Kubernetes on your choice of infrastructure, cloud provider and operating system.'
-		},
-		{
-			type: 1,
-			name: 'Reactive Ops',
-			logo: 'reactive_ops',
-			link: 'https://www.reactiveops.com/kubernetes/',
-			blurb: 'ReactiveOps has written automation on best practices for infrastructure as code on GCP & AWS using Kubernetes, helping you build and maintain a world-class infrastructure at a fraction of the price of an internal hire.'
-		},
-		{
-			type: 1,
-			name: 'Livewyer',
-			logo: 'livewyer',
-			link: 'https://livewyer.io/services/kubernetes-experts/',
-			blurb: 'Kubernetes experts that on-board applications and empower IT teams to get the most out of containerised technology.'
-		},
-		{
-			type: 1,
-			name: 'Deis',
-			logo: 'deis',
-			link: 'https://deis.com/services/',
-			blurb: 'Deis provides professional services and 24x7 operational support for any Kubernetes cluster managed by our global cluster operations team.'
-		},
-		{
-			type: 1,
-			name: 'StackPointCloud',
-			logo: 'stackpoint',
-			link: 'https://stackpoint.io',
-			blurb: 'StackPointCloud offers a wide range of support plans for managed Kubernetes clusters built through its universal control plane for Kubernetes Anywhere.'
-		},
-		{
-			type: 1,
-			name: 'Samsung SDS',
-			logo: 'samsung_sds',
-			link: 'http://www.samsungsdsa.com/cloud-infrastructure_kubernetes',
-			blurb: 'Samsung SDS’s Cloud Native Computing Team offers expert consulting across the range of technical aspects involved in building services targeted at a Kubernetes cluster.'
-		},
-		{
-			type: 1,
-			name: 'Container Solutions',
-			logo: 'container_solutions',
-			link: 'http://container-solutions.com/resources/kubernetes/',
-			blurb: 'Container Solutions is a premium software consultancy that focuses on programmable infrastructure, offering our expertise in software development, strategy and operations to help you innovate at speed and scale.'
-		},
-		{
-			type: 1,
-			name: 'Jetstack',
-			logo: 'jetstack',
-			link: 'https://www.jetstack.io/',
-			blurb: 'Jetstack is an organisation focused entirely on Kubernetes. They will help you to get the most out of Kubernetes through expert professional services and open source tooling. Get in touch, and accelerate your project.'
-		},
-		{
-			type: 0,
-			name: 'Tigera',
-			logo: 'tigera',
-			link: 'http://docs.projectcalico.org/v1.5/getting-started/kubernetes/',
-			blurb: 'Tigera builds high performance, policy driven, cloud native networking solutions for Kubernetes.'
-		},
-		{
-			type: 1,
-			name: 'Skippbox',
-			logo: 'skippbox',
-			link: 'http://www.skippbox.com/services/',
-			blurb: 'Skippbox brings its Kubernetes expertise to help companies embrace Kubernetes on their way to digital transformation. Skippbox offers both professional services and expert training.'
-		},
-		{
- 			type: 1,
- 			name: 'Harbur',
- 			logo: 'harbur',
- 			link: 'https://harbur.io/',
- 			blurb: 'Based in Barcelona, Harbur is a consulting firm that helps companies deploy self-healing solutions empowered by Container technologies'
-  		},
-		{
- 			type: 1,
- 			name: 'Endocode',
- 			logo: 'endocode',
- 			link: 'https://endocode.com/kubernetes/',
- 			blurb: 'Endocode practices and teaches the open source way. Kernel to cluster - Dev to Ops. We offer Kubernetes trainings, services and support.'
-  		},
-		{
- 			type: 0,
- 			name: 'Spotinst',
- 			logo: 'spotinst',
- 			link: 'http://blog.spotinst.com/2016/08/04/elastigroup-kubernetes-minions-steroids/',
- 			blurb: 'Spotinst uses a prediction algorithm in the Amazon EC2 Spot allowing k8s clusters to increase performance and lower the infrastructure costs'
-  		},
-		{
- 			type: 1,
- 			name: 'inwinSTACK',
- 			logo: 'inwinstack',
- 			link: 'http://www.inwinstack.com/index.php/en/solutions-en/',
- 			blurb: 'Our container service leverages OpenStack-based infrastructure and its container orchestration engine Magnum to manage Kubernetes clusters.'
-  		},
-		{
- 			type: 1,
- 			name: 'Semantix',
- 			logo: 'semantix',
- 			link: 'http://www.semantix.com.br/',
- 			blurb: 'Semantix is a company that works with data analytics and distributed systems. Kubernetes is used to orchestrate services for our customers.'
-  		},
-		{
- 			type: 0,
- 			name: 'ASM Technologies Limited',
- 			logo: 'asm',
- 			link: 'http://www.asmtech.com/',
- 			blurb: 'Our technology supply chain portfolio enables your software products to be accessible, viable and available more effectively.'
-  		},
-		{
- 			type: 1,
- 			name: 'InfraCloud Technologies',
- 			logo: 'infracloud',
- 			link: 'http://blog.infracloud.io/state-of-kubernetes/',
- 			blurb: 'InfraCloud Technologies is software consultancy which provides services in Containers, Cloud and DevOps.'
-  		},
-		{
- 			type: 0,
- 			name: 'SignalFx',
- 			logo: 'signalfx',
- 			link: 'https://github.com/signalfx/integrations/tree/master/kubernetes',
- 			blurb: 'Gain real-time visibility across metrics & the most intelligent alerts for todays architectures, including deep integration with Kubernetes'
-  		},
-		{
- 			type: 0,
- 			name: 'NATS',
- 			logo: 'nats',
- 			link: 'https://github.com/pires/kubernetes-nats-cluster',
- 			blurb: 'NATS is a simple, secure, and scalable cloud native messaging system.'
-  		},
-		{
- 			type: 1,
- 			name: 'RX-M',
- 			logo: 'rxm',
- 			link: 'http://rx-m.com/training/kubernetes-training/',
- 			blurb: 'Market neutral Kubernetes Dev, DevOps and Production training and consulting services'
-  		},
-		{
- 			type: 1,
- 			name: 'Emerging Technology Advisors',
- 			logo: 'eta',
- 			link: 'https://www.emergingtechnologyadvisors.com/services/kubernetes.html',
- 			blurb: 'ETA helps companies architect, implement, and manage scalable applications using Kubernetes on on public or private cloud.'
-  		},
-		{
- 			type: 0,
- 			name: 'CloudPlex.io',
- 			logo: 'cloudplex',
- 			link: 'http://www.cloudplex.io',
- 			blurb: 'CloudPlex enables operations teams to visually deploy, orchestrate, manage, and monitor infrastructure, applications, and services in public or private cloud.'
-  		},
-		{
- 			type: 1,
- 			name: 'Kumina',
- 			logo: 'kumina',
- 			link: 'https://www.kumina.nl/managed_kubernetes',
- 			blurb: 'Kumina creates Kubernetes solutions on your choice of infrastructure with around-the-clock management and unlimited support.'
-  		},
-		{
- 			type: 0,
- 			name: 'CA Technologies',
- 			logo: 'ca',
- 			link: 'https://www.ca.com/us/products/application-deployment.html',
- 			blurb: 'The RA CDE Kubernetes plugin enables an automated process for pushing changes to production by applying standard Kubernetes YAML files'
-  		},
-		{
- 			type: 0,
- 			name: 'CoScale',
- 			logo: 'coscale',
- 			link: 'http://www.coscale.com/blog/how-to-monitor-your-kubernetes-cluster',
- 			blurb: 'Full stack monitoring of containers and microservices orchestrated by Kubernetes. Powered by anomaly detection to find problems faster.'
-  		},
-		{
- 			type: 0,
- 			name: 'Supergiant.io',
- 			logo: 'supergiant',
- 			link: 'https://supergiant.io/blog/supergiant-packing-algorithm-unique-save-money',
- 			blurb: 'Supergiant autoscales hardware for Kubernetes. Open-source, it makes HA, distributed, stateful apps easy to deploy, manage, and scale.'
-  		},
-		{
- 			type: 0,
- 			name: 'Avi Networks',
- 			logo: 'avinetworks',
- 			link: 'https://kb.avinetworks.com/avi-vantage-openshift-installation-guide/',
- 			blurb: 'Avis elastic application services fabric provides scalable, feature rich & integrated L4-7 networking for K8S environments.'
-  		},
-		{
- 			type: 1,
- 			name: 'codecrux web technologies pvt ltd',
- 			logo: 'codecrux',
- 			link: 'http://codecrux.com/kubernetes/',
- 			blurb: 'At CodeCrux we help your organization get the most out of Containers and Kubernetes, regardless of where you are in your journey'
-  		},
-		{
- 			type: 0,
- 			name: 'Greenqloud',
- 			logo: 'qstack',
- 			link: 'https://www.qstack.com/application-orchestration/',
- 			blurb: 'Qstack provides self-serviceable on-site Kubernetes clusters with an intuitive User Interface for Infrastructure and Kubernetes management.'
-  		},
-		{
- 			type: 1,
- 			name: 'StackOVerdrive.io',
- 			logo: 'stackoverdrive',
- 			link: 'http://www.stackoverdrive.net/kubernetes-consulting/',
- 			blurb: 'We are a devops consulting firm and we do alot of work with containers and Kunbernetes is one of our go to tools.'
-  		},
-		{
- 			type: 0,
- 			name: 'F5 Networks',
- 			logo: 'f5networks',
- 			link: 'https://f5.com/about-us/news/press-kit',
- 			blurb: 'Integration of our ADC services with Kubernetes'
-  		},
-		{
- 			type: 0,
- 			name: 'StackIQ, Inc.',
- 			logo: 'stackiq',
- 			link: 'https://www.stackiq.com/kubernetes/',
- 			blurb: 'With Stacki and the Stacki Pallet for Kubernetes, you can go from bare metal to containers in one step very quickly and easily.'
-  		},
-		{
- 			type: 0,
- 			name: 'Cobe',
- 			logo: 'cobe',
- 			link: 'https://cobe.io/blog/posts/problems-within-your-kubernetes-cluster/',
- 			blurb: 'Manage Kubernetes clusters with a live, searchable model that captures all relationships and performance data in full visualised context.'
-  		},
-		{
- 			type: 0,
- 			name: 'Datawire',
- 			logo: 'datawire',
- 			link: 'http://www.datawire.io',
- 			blurb: 'Datawires open source tools let your microservices developers be awesomely productive on Kubernetes, while letting ops sleep at night.'
-  		},
-		{
- 			type: 0,
- 			name: 'Mashape, Inc.',
- 			logo: 'mashape',
- 			link: 'https://getkong.org/install/kubernetes/',
- 			blurb: 'Kong is a scalable open source API layer that runs in front of any RESTful API and can be provisioned to a Kubernetes cluster.'
-  		},
-		{
- 			type: 0,
- 			name: 'F5 Networks',
- 			logo: 'f5networks',
- 			link: 'http://github.com/f5networks',
- 			blurb: 'We have a LB integration into Kubernetes.'
-  		},
-		{
- 			type: 1,
- 			name: 'Lovable Tech',
- 			logo: 'lovable',
- 			link: 'https://drive.google.com/file/d/0BxCnAyMK1pgBTUFOdEZsUndLa01xMGJYZWtUVmVOdldadk80/view?usp=sharing',
- 			blurb: ''
-  		},
-		{
- 			type: 0,
- 			name: 'StackState',
- 			logo: 'stackstate',
- 			link: 'http://stackstate.com/platform/container-monitoring',
- 			blurb: 'Operational Analytics across teams and tools. Includes topology visualization, root cause analysis and anomaly detection for Kubernetes.'
-  		},
-		{
- 			type: 1,
- 			name: 'INEXCCO INC',
- 			logo: 'inexcco',
- 			link: 'https://www.inexcco.com/',
- 			blurb: 'Strong DevOps and Cloud talent working with couple clients on kubernetes and helm implementations. '
-  		},
-		{
- 			type: 0,
- 			name: 'Bitnami',
- 			logo: 'bitnami',
- 			link: 'http://bitnami.com/kubernetes',
- 			blurb: 'Bitnami brings a catalog of trusted, up to date, and easy to use applications and application building blocks to Kubernetes.'
-  		},
-		{
- 			type: 1,
- 			name: 'Nebulaworks',
- 			logo: 'nebulaworks',
- 			link: 'http://www.nebulaworks.com/container-platforms',
- 			blurb: 'Nebulaworks provides services to help the enterprise adopt modern container platforms and optimized processes to enable innovation at scale.'
-  		},
-		{
- 			type: 1,
- 			name: 'EASYNUBE LTD',
- 			logo: 'easynube',
- 			link: 'https://www.carrefour.es/supermercado/?ic_source=portal-home&ic_medium=menu-links&ic_content=section-home',
- 			blurb: 'Provide consultancy, architecture and implementation'
-  		},
-		{
- 			type: 1,
- 			name: 'Opcito Technologies',
- 			logo: 'opcito',
- 			link: 'http://www.opcito.com/kubernetes/',
- 			blurb: 'Opcito is a software consultancy that uses Kubernetes to help organisations build, architect & deploy highly scalable applications.'
-  		},
-		{
- 			type: 0,
- 			name: 'Huawei Technologies Co., Ltd.',
- 			logo: 'huawei',
- 			link: 'http://developer.huawei.com/ict/en/site-paas',
- 			blurb: 'FusionStage is an enterprise-grade PaaS, the core of which is based on open source container technology including Kubernetes and Docker.'
-  		},
-		{
- 			type: 0,
- 			name: '{code} by Dell EMC',
- 			logo: 'codedellemc',
- 			link: 'https://blog.codedellemc.com',
- 			blurb: 'Respected as a thought leader in storage persistence for containerized applications. Contributed significant work to K8 and Ecosystem'
-  		}
-		
-	]
-
-	var isvContainer = document.getElementById('isvContainer')
-	var servContainer = document.getElementById('servContainer')
-
-	var sorted = partners.sort(function (a, b) {
-		if (a.name > b.name) return 1
-		if (a.name < b.name) return -1
-		return 0
-	})
-
-	sorted.forEach(function (obj) {
-		var box = document.createElement('div')
-		box.className = 'partner-box'
-
-		var img = document.createElement('img')
-		img.src = '/images/square-logos/' + obj.logo + '.png'
-
-		var div = document.createElement('div')
-
-		var p = document.createElement('p')
-		p.textContent = obj.blurb
-
-		var link = document.createElement('a')
-		link.href = obj.link
-		link.target = '_blank'
-		link.textContent = 'Learn more'
-
-		div.appendChild(p)
-		div.appendChild(link)
-
-		box.appendChild(img)
-		box.appendChild(div)
-
-		var container = obj.type ? servContainer : isvContainer
-		container.appendChild(box)
-	})
-})();

_includes/partner-style.css

@@ -1,94 +0,0 @@
-h5 {
-	font-size: 18px;
-	line-height: 1.5em;
-	margin-bottom: 2em;
-}
-
-#usersGrid a {
-	display: inline-block;
-	background-color: #f9f9f9;
-}
-
-#isvContainer, #servContainer {
-	position: relative;
-	width: 100%;
-	display: flex;
-	justify-content: space-between;
-	flex-wrap: wrap;
-}
-
-#isvContainer {
-	margin-bottom: 80px;
-}
-
-.partner-box {
-	position: relative;
-	width: 47%;
-	max-width: 48%;
-	min-width: 48%;
-	margin-bottom: 20px;
-	padding: 20px;
-	flex: 1;
-	display: flex;
-	justify-content: space-between;
-	align-items: flex-start;
-}
-
-.partner-box img {
-	background-color: #f9f9f9;
-}
-
-.partner-box > div {
-	margin-left: 30px;
-}
-
-.partner-box a {
-	color: #3576E3;
-}
-
-@media screen and (max-width: 1024px) {
-	.partner-box {
-		flex-direction: column;
-		justify-content: flex-start;
-	}
-
-	.partner-box > div {
-		margin: 20px 0 0;
-	}
-}
-
-@media screen and (max-width: 568px) {
-	#isvContainer, #servContainer {
-		justify-content: center;
-	}
-
-	.partner-box {
-		flex-direction: column;
-		justify-content: flex-start;
-		width: 100%;
-		max-width: 100%;
-		min-width: 100%;
-	}
-
-	.partner-box > div {
-		margin: 20px 0 0;
-	}
-}
-
-@media screen and (max-width: 568px) {
-	#isvContainer, #servContainer {
-		justify-content: center;
-	}
-
-	.partner-box {
-		flex-direction: column;
-		justify-content: flex-start;
-		width: 100%;
-		max-width: 100%;
-		min-width: 100%;
-	}
-
-	.partner-box > div {
-		margin: 20px 0 0;
-	}
-}

_includes/tabs.md

@@ -1,15 +0,0 @@
-{% comment %} See /docs/tabs-example.md for usage example. {% endcomment %}
-{% assign tab_set_id = tab_set_name | default: "tabset" | slugify %}
-<div id="{{tab_set_id}}">
-    <ul>
-{% for name in tab_names %}
-        <li><a href="#{{tab_set_id}}-{{forloop.index0}}">{{ name | strip }}</a></li>
-{% endfor %}
-    </ul>
-{% for content in tab_contents %}
-    <div id="{{tab_set_id}}-{{forloop.index0}}">
-    {{ content | markdownify }}
-    </div>
-{% endfor %}
-</div>
-<script>$(function(){$("#{{tab_set_id}}").tabs();});</script>

_includes/task-tutorial-prereqs.md

@@ -1,4 +0,0 @@
-You need to have a Kubernetes cluster, and the kubectl command-line tool must
-be configured to communicate with your cluster. If you do not already have a
-cluster, you can create one by using
-[Minikube](/docs/getting-started-guides/minikube).

_includes/templates/_errorthrower.md

@@ -1,16 +0,0 @@
-### ERROR: You must define a <span style="font-family: monospace">`{{ include.missing_block }}`</span> block
-{: style="color:red" }
-
-This template requires that you provide text that {{ include.purpose }}. The text in this block will
-be displayed under the heading **{{ include.heading }}**.
-
-To get rid of this message and take advantage of this template, define the `{{ include.missing_block }}`
-variable and populate it with content.
-
-```liquid
-{% raw %}{%{% endraw %} capture {{ include.missing_block }} {% raw %}%}{% endraw %}
-Text that {{ include.purpose }}.
-{% raw %}{%{% endraw %} endcapture {% raw %}%}{% endraw %}
-```
-
-<!-- TEMPLATE_ERROR -->

_includes/templates/concept-overview.md

@@ -1,88 +0,0 @@
-{% if concept %}<!-- check for this before going any further; if not present, skip to else at bottom -->
-
-# Overview of {{concept}}s
-
-{% if what_is %}
-
-### What is a {{ concept }}?
-
-{{ what_is }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='what_is' heading='What is a (Concept)?' purpose='explains what this concept is and its purpose.' %}
-
-{% endif %}
-
-
-{% if when_to_use %}
-
-### When to use {{ concept }}s
-
-{{ when_to_use }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='when_to_use' heading='When to use (Concept)' purpose='explains when to use this object.' %}
-
-{% endif %}
-
-
-{% if when_not_to_use %}
-
-### When not to use {{ concept }}s
-
-{{ when_not_to_use }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='when_not_to_use' heading='When not to use (Concept)' purpose='explains when not to use this object.' %}
-
-{% endif %}
-
-
-{% if status %}
-
-### {{ concept }} status
-
-{{ status }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='status' heading='Retrieving status for a (Concept)' purpose='explains how to retrieve a status description for this object.' %}
-
-{% endif %}
-
-
-{% if usage %}
-
-#### Usage
-
-{{ usage }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='usage' heading='Usage' purpose='shows the most basic, common use case for this object, in the form of a code sample, command, etc, using tabs to show multiple approaches' %}
-
-{% endif %}
-
-<!-- continuing the "if concept" if/then: -->
-
-{% else %}
-
-### ERROR: You must define a "concept" variable
-{: style="color:red" }
-
-This template requires a variable called `concept` that is simply the name of the
-concept for which you are giving an overview. This will be displayed in the 
-headings for the document.
-
-To get rid of this message and take advantage of this template, define `concept`:
-
-```liquid
-{% raw %}{% assign concept="Replication Controller" %}{% endraw %}
-```
-
-Complete this task, then we'll walk you through preparing the rest of the document.
-
-{% endif %}

_includes/templates/concept.md

@@ -1,32 +0,0 @@
-{% if overview %}
-
-{{ overview }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='overview' purpose='provides an overview of this concept.' %}
-
-{% endif %}
-
-* TOC
-{:toc}
-
-{% if body %}
-
-{{ body }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='body' purpose='supplies the body of the page content.' %}
-
-{% endif %}
-
-
-{% if whatsnext %}
-
-## What's next
-
-{{ whatsnext }}
-
-{% endif %}
-

_includes/templates/kubectl.md

@@ -1,37 +0,0 @@
-{% if command %}
-
-# {% if site.data.kubectl[command].name != "kubectl" %}kubectl {% endif %}{{ site.data.kubectl[command].name }}
-
-{{ site.data.kubectl[command].synopsis }}
-
-## Description
-
-{{ site.data.kubectl[command].description }}
-
-{% if site.data.kubectl[command].options %}
-## Options
-
-| Option | Shorthand | Default Value | Usage |
-|--------------------|---------------|-------|{% for option in site.data.kubectl[command].options %}
-| `{{option.name | strip}}` | {% if option.shorthand %}`{{ option.shorthand | strip }}`{% endif %} | {% if option.default_value %}`{{option.default_value| strip}}`{% endif %} | {% if option.usage %}{{option.usage| strip | replace:'|',', '}}{% endif %} |{% endfor %}
-{% endif %}
-
-{% if site.data.kubectl[command].inherited_options %}
-## Inherited Options
-
-| Option | Shorthand | Default Value | Usage |
-|--------------------|---------------|-------|{% for option in site.data.kubectl[command].inherited_options %}
-| `{{option.name | strip}}` | {% if option.shorthand %}`{{ option.shorthand | strip }}`{% endif %} | {% if option.default_value %}`{{option.default_value| strip}}`{% endif %} | {% if option.usage %}{{option.usage| strip | replace:'|',', '}}{% endif %} |{% endfor %}
-{% endif %}
-
-## See also
-
-{% for seealso in site.data.kubectl[command].see_also %}
-- [`{{ seealso }}`](/docs/kubectl/{% if seealso != "kubectl" %}kubectl_{{seealso}}{% endif %})
-{% endfor %}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='command' heading='kubectl (command)' purpose='names the kubectl command, so that the appropriate YAML file (from _data/kubectl) can be transformed into a page.' %}
-
-{% endif %}

_includes/templates/task.md

@@ -1,55 +0,0 @@
-{% if overview %}
-
-{{ overview }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='overview' purpose='states, in one or two sentences, the purpose of this document' %}
-
-{% endif %}
-
-
-* TOC
-{: toc}
-
-
-{% if prerequisites %}
-
-## Before you begin
-
-{{ prerequisites }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='prerequisites' heading='Before you begin' purpose='lists action prerequisites and knowledge prerequisites' %}
-
-{% endif %}
-
-
-{% if steps %}
-
-{{ steps }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='steps' purpose='lists a sequence of numbered steps that accomplish the task.' %}
-
-{% endif %}
-
-
-{% if discussion %}
-
-{{ discussion }}
-
-{% else %}
-
-{% endif %}
-
-
-{% if whatsnext %}
-
-## What's next
-
-{{ whatsnext }}
-
-{% endif %}

_includes/templates/tutorial.md

@@ -1,68 +0,0 @@
-{% if overview %}
-
-{{ overview }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='overview' purpose='states, in one or two sentences, the purpose of this document' %}
-
-{% endif %}
-
-
-* TOC
-{: toc}
-
-
-{% if objectives %}
-
-## Objectives
-
-{{ objectives }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='objectives' heading='Objectives' purpose='lists the objectives for this tutorial.' %}
-
-{% endif %}
-
-
-{% if prerequisites %}
-
-## Before you begin
-
-{{ prerequisites }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='prerequisites' heading='Before you begin' purpose='lists action prerequisites and knowledge prerequisites' %}
-
-{% endif %}
-
-
-{% if lessoncontent %}
-
-{{ lessoncontent }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='lessoncontent' purpose='provides the lesson content for this tutorial.' %}
-
-{% endif %}
-
-
-{% if cleanup %}
-
-## Cleaning up
-
-{{ cleanup }}
-
-{% endif %}
-
-
-{% if whatsnext %}
-
-## What's next
-
-{{ whatsnext }}
-
-{% endif %}

_includes/tocsearch.html

@@ -1,15 +0,0 @@
-{% capture whitespace %}
-  {% for item in include.tree %}
-    {% if found_toc %}
-      {% break %}
-    {% endif %}
-    {% if item.section %}
-      {% include tocsearch.html tree=item.section toc=include.toc %}
-    {% else %}
-      {% if item == page.path %}
-        {% assign found_toc = include.toc %}
-        {% break %}
-      {% endif %}
-    {% endif %}
-  {% endfor %}
-{% endcapture %}

_includes/tree.html

@@ -1,25 +0,0 @@
-{% for item in include.tree %}
-  {% if item.section %}
-    <div class="item" data-title="{{ item.title }}">
-      <div class="container">
-        {% include_cached tree.html tree=item.section %}
-      </div>
-    </div>
-  {% else %}
-
-    {% capture whitespace %}
-      {% if item.path %}
-        {% assign path   = item.path %}
-        {% assign title  = item.title %}
-      {% else %}
-        {% assign found_page = site.pages | where: "path", item | first %}
-        {% assign title = found_page.title %}
-        {% assign path  = found_page.url %}
-      {% endif %}
-    {% endcapture %}
-
-    {% if path %}
-      <a class="item" data-title="{{ title }}" href="{{ path }}"></a>
-    {% endif %}
-  {% endif %}
-{% endfor %}

_layouts/basic.html

@@ -1,15 +0,0 @@
-<!DOCTYPE html>
-<html id="{{ page.cid }}" lang="en" class="{{ page.class }}">
-
-    {% include head.html %}
-
-    <body>
-        {% include header.html %}
-
-        {{ content }}
-
-        {% include footer.html %}
-
-        {% include footer-scripts.html %}
-    </body>
-</html>

_layouts/docwithnav.html

@@ -1,77 +0,0 @@
-{% for current_toc in site.tocs %}
-  {% if found_toc %}
-    {% break %}
-  {% else %}
-    {% assign toc=site.data[current_toc] %}
-    {% include tocsearch.html tree=toc.toc toc=toc %}
-  {% endif %}
-{% endfor %}
-
-<!Doctype html>
-<html id="docs" class="{{ toc.bigheader }}">
-
-{% include head.html %}
-
-<body>
-
-{% include header.html %}
-
-<!--  HERO  -->
-<section id="hero" class="light-text">
-  <h1>{{ toc.bigheader }}</h1>
-  <h5>{{ toc.abstract }}</h5>
-  <div id="vendorStrip" class="light-text">
-    <ul>
-      <li><a href="/docs/home/" {% if toc.bigheader == "Kubernetes Documentation" %}class="YAH"{% endif %}>HOME</a></li>
-      <li><a href="/docs/setup/" {% if toc.bigheader == "Setup" %}class="YAH"{% endif %}>SETUP</a></li>
-      <li><a href="/docs/concepts/" {% if toc.bigheader == "Concepts" %}class="YAH"{% endif %}>CONCEPTS</a></li>
-      <li><a href="/docs/tasks/" {% if toc.bigheader == "Tasks" %}class="YAH"{% endif %}>TASKS</a></li>
-      <li><a href="/docs/tutorials/" {% if toc.bigheader == "Tutorials" %}class="YAH"{% endif %}>TUTORIALS</a></li>
-      <li><a href="/docs/reference/" {% if toc.bigheader == "Reference Documentation" %}class="YAH"{% endif %}>REFERENCE</a></li>
-    </ul>
-    <div id="searchBox">
-      <input type="text" id="search" placeholder="Search" onkeydown="if (event.keyCode==13) window.location.replace('/docs/search/?q=' + this.value)" autofocus="autofocus">
-    </div>
-  </div>
-</section>
-
-<section id="encyclopedia">
-  <div id="docsToc">
-        <div class="pi-accordion">
-          {% include_cached tree.html tree=toc.toc %}
-        </div> <!-- /pi-accordion -->
-    <button class="push-menu-close-button" onclick="kub.toggleToc()"></button>
-  </div> <!-- /docsToc -->
-
-  <div id="docsContent">
-        <p><a href="/editdocs#{{ page.path }}" id="editPageButton">Edit This Page</a></p>
-
-        {% unless page.notitle %}
-          <h1>{{ page.title }}</h1>
-        {% endunless %}
-
-        {{ content }}
-
-        <p><a href=""><img src="https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/{{ page.path }}?pixel" alt="Analytics" /></a></p>
-        {% if page.url != "/404.html" and page.url != "/docs/search/" %}
-        <script type="text/javascript">
-            PDRTJS_settings_8345992 = {
-                "id" : "8345992",
-                "unique_id" : "{{ page.url }}",
-                "title" : "{{ page.title }}",
-                "permalink" : "http://kubernetes.github.io{{ page.url }}"
-            };
-            (function(d,c,j){if(!document.getElementById(j)){var pd=d.createElement(c),s;pd.id=j;pd.src=('https:'==document.location.protocol)?'https://polldaddy.com/js/rating/rating.js':'http://i0.poll.fm/js/rating/rating.js';s=document.getElementsByTagName(c)[0];s.parentNode.insertBefore(pd,s);}}(document,'script','pd-rating-js'));
-        </script>
-        <a href="" onclick="window.open('https://github.com/kubernetes/kubernetes.github.io/issues/new?title=Issue%20with%20' +
-        'k8s.io'+window.location.pathname)" class="button issue">Create an Issue</a>
-        <a href="/editdocs#{{ page.path }}" class="button issue">Edit this Page</a>
-    {% endif %}
-    </div>
-</section>
-
-{% include_cached footer.html %}
-{% include footer-scripts.html %}
-
-</body>
-</html>

_sass/_code-styles.sass

@@ -1,199 +0,0 @@
-/* Default gh-pages-blog css from https://github.com/thedereck/gh-pages-blog/blob/master/css/syntax.css */
-.highlight br
-	display: none
-
-.highlight
-	background: #ffffff
-
-.highlight .c
-	color: #999988
-	font-style: italic
-
-.highlight .err
-	color: #a61717
-	background-color: #e3d2d2
-
-.highlight .k
-	font-weight: bold
-
-.highlight .o
-	font-weight: bold
-
-.highlight .cm
-	color: #999988
-	font-style: italic
-
-.highlight .cp
-	color: #999999
-	font-weight: bold
-
-.highlight .c1
-	color: #999988
-	font-style: italic
-
-.highlight .cs
-	color: #999999
-	font-weight: bold
-	font-style: italic
-
-.highlight .gd
-	color: #000000
-	background-color: #ffdddd
-
-.highlight .gd .x
-	color: #000000
-	background-color: #ffaaaa
-
-.highlight .ge
-	font-style: italic
-
-.highlight .gr
-	color: #aa0000
-
-.highlight .gh
-	color: #999999
-
-.highlight .gi
-	color: #000000
-	background-color: #ddffdd
-
-.highlight .gi .x
-	color: #000000
-	background-color: #aaffaa
-
-.highlight .go
-	color: #888888
-
-.highlight .gp
-	color: #555555
-
-.highlight .gs
-	font-weight: bold
-
-.highlight .gu
-	color: #aaaaaa
-
-.highlight .gt
-	color: #aa0000
-
-.highlight .kc
-	font-weight: bold
-
-.highlight .kd
-	font-weight: bold
-
-.highlight .kp
-	font-weight: bold
-
-.highlight .kr
-	font-weight: bold
-
-.highlight .kt
-	color: #445588
-	font-weight: bold
-
-.highlight .m
-	color: #009999
-
-.highlight .s
-	color: #d14
-
-.highlight .na
-	color: #008080
-
-.highlight .nb
-	color: #0086B3
-
-.highlight .nc
-	color: #445588
-	font-weight: bold
-
-.highlight .no
-	color: #008080
-
-.highlight .ni
-	color: #800080
-
-.highlight .ne
-	color: #990000
-	font-weight: bold
-
-.highlight .nf
-	color: #990000
-	font-weight: bold
-
-.highlight .nn
-	color: #555555
-
-.highlight .nt
-	color: #000080
-
-.highlight .nv
-	color: #008080
-
-.highlight .ow
-	font-weight: bold
-
-.highlight .w
-	color: #bbbbbb
-
-.highlight .mf
-	color: #009999
-
-.highlight .mh
-	color: #009999
-
-.highlight .mi
-	color: #009999
-
-.highlight .mo
-	color: #009999
-
-.highlight .sb
-	color: #d14
-
-.highlight .sc
-	color: #d14
-
-.highlight .sd
-	color: #d14
-
-.highlight .s2
-	color: #d14
-
-.highlight .se
-	color: #d14
-
-.highlight .sh
-	color: #d14
-
-.highlight .si
-	color: #d14
-
-.highlight .sx
-	color: #d14
-
-.highlight .sr
-	color: #009926
-
-.highlight .s1
-	color: #d14
-
-.highlight .ss
-	color: #990073
-
-.highlight .bp
-	color: #999999
-
-.highlight .vc
-	color: #008080
-
-.highlight .vg
-	color: #008080
-
-.highlight .vi
-	color: #008080
-
-.highlight .il
-	color: #009999
-

_sass/_desktop.sass

@@ -1,311 +0,0 @@
-$main-max-width: 1200px
-$vendor-strip-height: 44px
-$video-section-height: 550px
-
-@media screen and (min-width: 1025px)
-	#hamburger
-		display: none
-
-	ul.global-nav
-		display: inline-block
-
-	#docs #vendorStrip #searchBox:before
-		top: 15px
-
-	#vendorStrip
-		height: $vendor-strip-height
-		line-height: $vendor-strip-height
-
-		li
-			a.YAH
-				&:after
-					content: ""
-					display: block
-					position: absolute
-					left: 0
-					bottom: 0
-					width: 100%
-					height: 4px
-					background-color: $blue
-
-
-		#searchBox
-			float: right
-
-
-	#home
-		#hero
-			#vendorStrip
-				display: block
-
-	#docs
-		#hero
-			h1, h5
-				text-align: left
-
-			#vendorStrip
-				ul
-					float: left
-
-				#searchBox
-					float: right
-					width: 320px
-
-				#search
-					vertical-align: middle
-
-		.flyout-button
-			display: none
-
-		.logo
-			position: relative
-			float: left
-			display: block
-			width: 180px
-			height: 88px
-			top: 0
-			left: 0
-			transform: none
-			background-image: url(../images/nav_logo.svg)
-
-		&.flip-nav, &.open-nav
-			.logo
-				background-image: url(../images/nav_logo2.svg)
-
-
-	#encyclopedia
-		padding: 50px 50px 100px 100px
-		clear: both
-
-	#docsToc
-		position: relative
-		float: left
-		padding: 0 20px
-		left: 0
-		width: 350px
-		z-index: auto
-
-		.push-menu-close-button
-			display: none
-
-	#docsContent
-		width: calc(100% - 400px)
-
-		#editPageButton
-			right: -25px
-
-	section, header, footer
-		main
-			max-width: $main-max-width
-	
-	header, #vendorStrip, #encyclopedia, #hero h1, #hero h5, #docs #hero h1, #docs #hero h5,
-	#community #hero h1, .gridPage #hero h1, #community #hero h5, .gridPage #hero h5
-		padding-left: 100px
-		padding-right: 100px
-
-	#home
-		section, header, footer
-			main
-				max-width: 1000px
-
-	#oceanNodes
-		main
-			position: relative
-			max-width: 830px
-
-			&:nth-child(1)
-				max-width: 1000px
-				padding-right: 475px
-
-				h3, p
-					text-align: left
-
-				.image-wrapper
-					position: absolute
-					max-width: 48%
-					transform: translateY(-50%)
-
-					img
-						max-width: 425px
-
-				//.content
-				//	width: 50%
-
-
-	#video
-		height: $video-section-height
-		position: relative
-		background-image: url(../images/kub_video_banner.jpg)
-		background-position: center center
-		background-size: cover
-
-
-
-	#talkToUs
-		h4
-			br
-				display: block
-
-		#bigSocial
-			div
-				width: calc(25% - 18px)
-
-			div + div
-				margin-left: 20px
-			//
-			//div:nth-child(3), div:nth-child(4)
-			//	margin-top: 0
-
-
-	//#home #bigSocial
-	//	div
-	//		width: calc(33% - 15px)
-	//
-	//	div:nth-child(3)
-	//		margin-top: inherit
-
-	// FOOTER
-	footer
-		width: 100%
-		background-image: url(../images/texture.png)
-		background-color: $dark-grey
-
-		main
-			padding: 20px 0
-
-		nav
-			overflow: hidden
-			margin-bottom: 20px
-
-			a
-				width: 16.65%
-				float: left
-				font-size: 24px
-				font-weight: 300
-				white-space: nowrap
-
-		.social
-			padding: 0 30px
-			max-width: 1200px
-
-			div
-				float: left
-
-			div:last-child
-				float: right
-
-	#search, #wishField
-		background-color: transparent
-		padding: 10px
-		font-size: 16px
-		font-weight: 100
-		color: white
-		border: 1px solid white
-		transition: 0.3s
-
-		&:focus
-			background-color: $light-grey
-			color: $dark-grey
-
-	.social a
-		display: inline-block
-		background-image: url(../images/social_sprite.png)
-		background-repeat: no-repeat
-		background-size: auto
-		width: 50px
-		height: 50px
-		border-radius: 5px
-		margin-right: 10px
-
-		&:hover
-			background-color: #fff
-
-		span
-			position: absolute
-			display: block
-			height: 0
-			overflow: hidden
-
-	a.twitter
-		background-position: 0 0
-
-		&:hover
-			background-position: 0 100%
-
-	a.stack-overflow
-		background-position: -50px 0
-
-		&:hover
-			background-position: -50px 100%
-
-	a.slack
-		background-position: -100px 0
-
-		&:hover
-			background-position: -100px 100%
-
-	a.github
-		background-position: -150px 0
-
-		&:hover
-			background-position: -150px 100%
-
-	a.mailing-list
-		background-position: -200px 0
-
-		&:hover
-			background-position: -200px 100%
-
-	a.calendar
-		background-position: -250px 0
-
-		&:hover
-			background-position: -250px 100%
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-	#community, .gridPage
-		#hero
-			text-align: left
-
-			h1
-				padding: 20px 100px
-
-		#tryKubernetes
-			width: auto
-			background-color: $blue
-			padding: 0 20px
-			
-
-
-
-	#bigSocial
-		div
-			width: calc(25% - 18px)
-
-
-	#home #caseStudiesWrapper
-		div
-			width: 24%
-			min-height: 260px

_sass/_reset.sass

@@ -1,61 +0,0 @@
-html, body
-	margin: 0
-	padding: 0
-
-
-input, button
-	outline: none
-
-button
-	cursor: pointer
-
-ul, li
-	list-style: none
-
-ul
-	margin: 0
-	padding: 0
-	
-a
-	text-decoration: none
-
-// CONVENIENCE
-.clear
-	display: block
-	clear: both
-
-.light-text
-	color: white
-
-.right
-	float: right
-
-.left
-	float: left
-
-.center
-	text-align: center
-
-
-//mixins
-@mixin fullScreen
-	position: fixed
-	top: 0
-	left: 0
-	width: 100vw
-	height: 100vh
-
-
-@mixin pureCenter($left: 50%, $top: 50%)
-	position: absolute
-	top: $top
-	left: $left
-	transform: translate(-50%, -50%)
-
-
-@mixin maintain-aspect-ratio ($width-factor: 16, $height-factor: 9, $target-width: 80vw, $target-height: 80vh)
-	width: $target-width
-	height: $target-width * ($height-factor / $width-factor)
-	max-width: $target-height * ($width-factor / $height-factor)
-	max-height: $target-height
-

_sass/_size.sass

@@ -1,86 +0,0 @@
-h1
-	font-size: $h1-font-size
-	line-height: $h1-line-height
-
-h2
-	font-size: $h2-font-size
-	line-height: $h2-line-height
-
-h3
-	font-size: $h3-font-size
-	line-height: $h3-line-height
-
-h4
-	font-size: $h4-font-size
-	line-height: $h4-line-height
-
-h5
-	font-size: $h5-font-size
-	line-height: $h5-line-height
-
-p
-	font-size: $p-font-size
-	line-height: $p-line-height
-
-section, header, #vendorStrip
-	padding-left: $full-width-paddingX
-	padding-right: $full-width-paddingX
-
-	main
-		width: $main-width
-		max-width: $main-max-width
-
-header
-	height: $header-height
-
-.nav-buttons
-	height: $header-height
-	line-height: $header-height
-
-	.button + *
-		margin-left: $nav-buttons-margin-left
-
-#hamburger
-	width: $hamburger-size
-	height: $hamburger-size
-
-#mainNav
-	padding: $main-nav-padding
-
-	h5
-		margin-bottom: $main-nav-h5-margin-bottom
-
-	h3
-		margin-bottom: $main-nav-h3-margin-bottom
-
-	.nav-box
-		width: $nav-box-width
-
-	.nav-box + .nav-box
-		margin-left: $nav-box-sibling-margin-left
-
-	main + main
-		margin-top: $main-nav-main-sibling-margin-top
-
-	.left .button
-		height: $main-nav-left-button-size
-		line-height: $main-nav-left-button-size
-		font-size: $main-nav-left-button-font-size
-
-.open-nav, .y-enough
-	#tryKubernetes
-		margin-left: $nav-buttons-margin-left
-
-#hero
-	padding-top: $hero-padding-top
-
-#docs
-	#hero
-		h1, h5
-			padding-left: $full-width-paddingX
-			padding-right: $full-width-paddingX
-
-#vendorStrip
-	height: $vendor-strip-height
-	line-height: $vendor-strip-height
-	font-size: $vendor-strip-font-size

_sass/_skin.sass

@@ -1,25 +0,0 @@
-$blue: #3371e3
-$light-grey: #f7f7f7
-$dark-grey: #303030
-$medium-grey: #4c4c4c
-$white: #ffffff
-
-$base-font: 'Roboto', sans-serif
-$mono-font: 'Roboto Mono', monospace
-
-
-*, .button
-	box-sizing: border-box
-	font-family: $base-font
-	background: none
-	margin: 0
-	border: 0
-
-body
-	font-family: $base-font
-
-h1, h2, h5, p
-	font-weight: 300
-
-h3, h4
-	font-weight: 400

_sass/_tablet.sass

@@ -1,249 +0,0 @@
-// TEXT
-//$h1-font-size: 60px
-//$h1-line-height: 80px
-//
-//$h2-font-size: 42px
-//$h2-line-height: 60px
-//
-//$h3-font-size: 26px
-//$h3-line-height: 32px
-//
-//$h4-font-size: 26px
-//$h4-line-height: 40px
-//
-//$h5-font-size: 18px
-//$h5-line-height: 36px
-//
-//$p-font-size: 20px
-//$p-line-height: 28px
-
-
-// header
-$full-width-paddingX: 20px
-
-$main-width: 100%
-$main-max-width: 100%
-
-$header-height: 80px
-
-$logo-width: 180px
-
-$nav-buttons-margin-left: 30px
-
-$hamburger-size: 50px
-
-
-// main nav
-$main-nav-padding: 140px 0 30px
-$main-nav-h5-margin-bottom: 1em
-$main-nav-h3-margin-bottom: 0.6em
-$nav-box-width: 20%
-$nav-box-sibling-margin-left: calc(20% / 3)
-$main-nav-main-sibling-margin-top: 60px
-$main-nav-left-button-size: 50px
-$main-nav-left-button-font-size: 18px
-
-
-// hero
-$hero-padding-top: 80px
-$headline-wrapper-margin-bottom: 40px
-$quickstart-button-padding: 0 50px
-$vendor-strip-font-size: 16px
-
-//video
-$video-section-height: 400px
-
-//features
-$features-h3-margin-bottom: 40px
-$feature-box-margin-bottom: 60px
-$feature-box-div-margin-bottom: 0
-$feature-box-div-width: 45%
-
-
-
-////////////////////////////////////////////////////////////////////////////////////////////////////
-////////////////////////////////////////////////////////////////////////////////////////////////////
-////////////////////////////////////////////////////////////////////////////////////////////////////
-
-@media screen and (min-width: 750px)
-	@import "size"
-
-	p
-		font-size: 16px
-		line-height: 24px
-		letter-spacing: 0.1px
-
-	h1
-		font-size: 36px
-		line-height: 44px
-
-	h3
-		font-size: 28px
-		line-height: 36px
-
-	h4
-		font-size: 24px
-		line-height: 40px
-
-
-
-	#home
-		#viewDocs, #tryKubernetes
-			display: inline-block
-
-	#vendorStrip
-		display: block
-		text-align: center
-
-		img
-			max-height: 24px
-			vertical-align: middle
-			margin: 0 30px
-
-	#docs
-		#vendorStrip
-			li
-				a
-					font-size: 1em
-					font-weight: normal
-
-				li + li
-					margin-left: 60px
-
-
-	#oceanNodes
-		h3
-			text-align: left
-			margin-bottom: 18px
-
-		main
-			position: relative
-			clear: both
-			display: table
-
-			.content
-				display: table-cell
-				position: relative
-				vertical-align: middle
-
-			.image-wrapper
-				position: absolute
-				top: 50%
-				max-width: 25%
-				max-height: 100%
-				transform: translateY(-50%)
-
-			&:nth-child(odd)
-				padding-right: 210px
-
-				.image-wrapper
-					right: 0
-
-			&:nth-child(even)
-				padding-left: 210px
-
-				.image-wrapper
-					left: 0
-
-			&:nth-child(1)
-				padding-right: 0
-
-				h3, p
-					text-align: center
-
-				.image-wrapper
-					position: relative
-					display: block
-					float: none
-					max-width: 100%
-					transform: none
-
-				.content
-					display: block
-
-			img
-				width: 100%
-
-
-	#video
-		height: $video-section-height
-		display: block
-
-		& > .light-text
-			display: block
-
-	#mobileShowVideoButton
-		display: none
-
-	#features
-		padding-bottom: 60px
-
-		.feature-box
-			margin-bottom: 30px
-
-			&:last-child
-				margin-bottom: 0
-
-		h3
-			margin-bottom: $features-h3-margin-bottom
-
-		.feature-box
-			& > div
-				width: $feature-box-div-width
-				margin-bottom: $feature-box-div-margin-bottom
-
-	#talkToUs
-		#bigSocial
-			div
-				width: calc(50% - 15px)
-
-			div + div
-				margin-top: 0
-
-			div:nth-child(2)
-				margin-left: 20px
-
-			div:nth-child(3)
-				margin-top: 20px
-
-			div:nth-child(4)
-				margin-top: 20px
-				margin-left: 20px
-
-			a
-				display: inline-block
-				color: $blue
-				font-weight: 400
-				text-decoration: none
-
-	// FOOTER
-	footer
-		nav
-			text-align: center
-
-			a
-				width: 30%
-				padding: 0 20px
-
-		.social
-			text-align: center
-
-			div
-				display: inline-block
-
-			div:last-child
-				display: block
-				margin: 0
-
-			span
-				display: inline-block
-				margin-right: 10px
-
-			input
-				text-align: left
-
-
-
-	#home #caseStudiesWrapper
-		div
-			width: 48%

archetypes/default.md

@@ -0,0 +1,6 @@
+---
+title: "{{ replace .Name "-" " " | title }}"
+date: {{ .Date }}
+draft: true
+---
+

assets/sass/_case-studies.sass

@@ -0,0 +1,99 @@
+// SASS for Case Studies pages go here:
+
+hr
+  background-color: #999999
+
+h2
+  margin-bottom: 15px !important
+
+.subhead
+  padding-bottom: 2% !important
+  padding-top: 0% !important
+
+.details
+  margin-left: 1.9%
+  padding-right: 5%
+  font-size: 16px !important
+  padding-bottom: 2% !important
+
+.section1
+  margin-bottom: 3%
+  .cols
+    width: 80% !important
+    margin-left: 6.8%
+    padding-top: 1.5%
+    .col1
+      width: 52% !important
+      font-weight: 300 !important
+    .col2
+      width: 46% !important
+
+.banner2text
+  width: 63%
+  padding-top: 10%
+  padding-left: 0% !important
+  float: initial !important
+  text-align: center
+  margin: 0 auto
+  position: relative
+
+.banner3text, .banner4text, .banner5text
+  width: 63%
+  padding-left: 0% !important
+  float: initial !important
+  text-align: center
+  margin: 0 auto
+  position: relative
+
+.fullcol
+  float: initial !important
+
+body footer
+  background-color: #585858 !important
+
+.section1
+  float: left !important
+
+.banner1
+  padding-left: 11.9% !important
+
+.banner2
+  float: initial !important
+  padding-bottom: 2% !important
+
+footer
+  padding: 0% 7%
+
+.banner4, .banner3, .banner5
+  float: initial !important
+
+@media screen and (max-width: 910px)
+  .banner2text
+    width: 47%
+    padding-top: 45%
+  .details
+    margin-left: 0%
+    margin-bottom: 3%
+  .subhead
+    padding-bottom: 0% !important
+    padding-top: 0% !important
+  .banner3
+    width: 100% !important
+
+@media screen and (max-width: 780px)
+  .section1 .cols
+    width: 100% !important
+    margin-left: 0%
+    padding-top: 5%
+    .col1, .col2
+      width: 100% !important
+      margin-left: 0% !important
+  .fullcol
+    width: 90% !important
+    margin-left: 5% !important
+  .banner1
+    padding-left: 10% !important
+    margin-bottom: 6% !important
+  .banner2text
+    padding-top: 60% !important
+    padding-bottom: 2% !important

assets/sass/_desktop.sass

@@ -0,0 +1,302 @@
+$main-max-width: 1200px
+$vendor-strip-height: 44px
+$video-section-height: 550px
+
+@media screen and (min-width: 1025px)
+  #hamburger
+    display: none
+
+  ul.global-nav
+    display: inline-block
+
+  #docs #vendorStrip #searchBox:before
+    top: 15px
+
+  #vendorStrip
+    height: $vendor-strip-height
+    line-height: $vendor-strip-height
+
+    li
+      a.YAH
+        &:after
+          content: ""
+          display: block
+          position: absolute
+          left: 0
+          bottom: 0
+          width: 100%
+          height: 4px
+          background-color: $blue
+
+
+    #searchBox
+      float: right
+
+
+  #home
+    #hero
+      #vendorStrip
+        display: block
+
+  #docs
+    #hero
+      h1, h5
+        text-align: left
+
+      #vendorStrip
+        ul
+          float: left
+
+        #searchBox
+          float: right
+          width: 250px
+
+        #search
+          vertical-align: middle
+
+    .flyout-button
+      display: none
+
+    .logo
+      position: relative
+      float: left
+      display: block
+      width: 180px
+      height: 88px
+      top: 0
+      left: 0
+      transform: none
+      background-image: url(../images/nav_logo.svg)
+
+    &.flip-nav, &.open-nav
+      .logo
+        background-image: url(../images/nav_logo2.svg)
+
+
+  #encyclopedia
+    padding: 50px 50px 100px 100px
+    clear: both
+
+  #docsToc
+    position: relative
+    float: left
+    padding: 0 20px
+    left: 0
+    width: 350px
+    z-index: auto
+
+    .push-menu-close-button
+      display: none
+
+  #docsContent
+    width: calc(100% - 400px)
+
+    #editPageButton
+      right: -25px
+
+  section, header, footer
+    .main-section
+      max-width: $main-max-width
+
+  header, #vendorStrip, #encyclopedia, #hero h1, #hero h5, #docs #hero h1, #docs #hero h5,
+  #community #hero h1, .gridPage #hero h1, #community #hero h5, .gridPage #hero h5
+    padding-left: 100px
+    padding-right: 100px
+
+  #vendorStrip
+    padding-right: 10px
+
+  #home
+    section, header, footer
+      .main-section
+        max-width: 1000px
+
+  #oceanNodes
+    .main-section
+      position: relative
+      max-width: 830px
+
+      &:nth-child(1)
+        max-width: 1000px
+        padding-right: 475px
+
+        h3, p
+          text-align: left
+
+        .image-wrapper
+          position: absolute
+          max-width: 48%
+          transform: translateY(-50%)
+
+          img
+            width: 425px
+
+        //.content
+        //	width: 50%
+
+
+  #video
+    height: $video-section-height
+    position: relative
+    background-position: center center
+    background-size: cover
+
+
+
+  #talkToUs
+    h4
+      br
+        display: block
+
+    #bigSocial
+      div
+        width: calc(25% - 18px)
+
+      div + div
+        margin-left: 20px
+      //
+      //div:nth-child(3), div:nth-child(4)
+      //	margin-top: 0
+
+
+  //#home #bigSocial
+  //	div
+  //		width: calc(33% - 15px)
+  //
+  //	div:nth-child(3)
+  //		margin-top: inherit
+
+  // FOOTER
+  footer
+    width: 100%
+    background-image: url(../images/texture.png)
+    background-color: $dark-grey
+
+    .main-section
+      padding: 20px 0
+
+    nav
+      overflow: hidden
+      margin-bottom: 20px
+
+      a
+        width: 16.65%
+        float: left
+        font-size: 24px
+        font-weight: 300
+        white-space: nowrap
+
+    .social
+      padding: 0 30px
+      max-width: 1200px
+
+      div
+        float: left
+
+      div:last-child
+        float: right
+
+  #search, #wishField
+    background-color: transparent
+    padding: 10px
+    font-size: 16px
+    font-weight: 100
+    color: white
+    border: 1px solid white
+    transition: 0.3s
+
+    &:focus
+      background-color: $light-grey
+      color: $dark-grey
+
+  .social a
+    display: inline-block
+    background-image: url(../images/social_sprite.svg)
+    background-repeat: no-repeat
+    background-size: 350px
+    width: 50px
+    height: 50px
+    border-radius: 5px
+    margin-right: 10px
+
+    &:hover
+      background-color: #fff
+
+    span
+      position: absolute
+      display: block
+      height: 0
+      overflow: hidden
+
+  a.twitter
+    background-position: 0 0
+
+    &:hover
+      background-position: 0 100%
+
+  a.stack-overflow
+    background-position: -50px 0
+
+    &:hover
+      background-position: -50px 100%
+
+  a.slack
+    background-position: -100px 0
+
+    &:hover
+      background-position: -100px 100%
+
+  a.github
+    background-position: -150px 0
+
+    &:hover
+      background-position: -150px 100%
+
+  a.mailing-list
+    background-position: -200px 0
+
+    &:hover
+      background-position: -200px 100%
+
+  a.calendar
+    background-position: -250px 0
+
+    &:hover
+      background-position: -250px 100%
+
+  a.youtube
+    background-position: -300px 0
+
+    &:hover
+      background-position: -300px 100%
+
+  #community, .gridPage
+    #hero
+      text-align: left
+
+      h1
+        padding: 20px 100px
+
+    #tryKubernetes
+      width: auto
+      background-color: $blue
+      padding: 0 20px
+
+  #bigSocial
+    div
+      width: calc(25% - 18px)
+
+
+  #home #caseStudiesWrapper
+    div
+      width: 24%
+      min-height: 260px
+
+@media screen and (min-width: 1300px)
+  #vendorStrip
+    padding-right: 100px
+
+@media screen and (min-width: 456px)
+  #vendorStrip
+    li + li
+      margin-left: 20px

assets/sass/_reset.sass

@@ -0,0 +1,61 @@
+html, body
+  margin: 0
+  padding: 0
+
+
+input, button
+  outline: none
+
+button
+  cursor: pointer
+
+ul, li
+  list-style: none
+
+ul
+  margin: 0
+  padding: 0
+	
+a
+  text-decoration: none
+
+// CONVENIENCE
+.clear
+  display: block
+  clear: both
+
+.light-text
+  color: white
+
+.right
+  float: right
+
+.left
+  float: left
+
+.center
+  text-align: center
+
+
+//mixins
+@mixin fullScreen
+  position: fixed
+  top: 0
+  left: 0
+  width: 100vw
+  height: 100vh
+
+
+@mixin pureCenter($left: 50%, $top: 50%)
+  position: absolute
+  top: $top
+  left: $left
+  transform: translate(-50%, -50%)
+
+
+@mixin maintain-aspect-ratio ($width-factor: 16, $height-factor: 9, $target-width: 80vw, $target-height: 80vh)
+  width: $target-width
+  height: $target-width * ($height-factor / $width-factor)
+  max-width: $target-height * ($width-factor / $height-factor)
+  max-height: $target-height
+

assets/sass/_size.sass

@@ -0,0 +1,86 @@
+h1
+  font-size: $h1-font-size
+  line-height: $h1-line-height
+
+h2
+  font-size: $h2-font-size
+  line-height: $h2-line-height
+
+h3
+  font-size: $h3-font-size
+  line-height: $h3-line-height
+
+h4
+  font-size: $h4-font-size
+  line-height: $h4-line-height
+
+h5
+  font-size: $h5-font-size
+  line-height: $h5-line-height
+
+p
+  font-size: $p-font-size
+  line-height: $p-line-height
+
+section, header, #vendorStrip
+  padding-left: $full-width-paddingX
+  padding-right: $full-width-paddingX
+
+  .main-section
+    width: $main-width
+    max-width: $main-max-width
+
+header
+  height: $header-height
+
+.nav-buttons
+  height: $header-height
+  line-height: $header-height
+
+  .button + *
+    margin-left: $nav-buttons-margin-left
+
+#hamburger
+  width: $hamburger-size
+  height: $hamburger-size
+
+#mainNav
+  padding: $main-nav-padding
+
+  h5
+    margin-bottom: $main-nav-h5-margin-bottom
+
+  h3
+    margin-bottom: $main-nav-h3-margin-bottom
+
+  .nav-box
+    width: $nav-box-width
+
+  .nav-box + .nav-box
+    margin-left: $nav-box-sibling-margin-left
+
+  .main-secton + .main-section
+    margin-top: $main-nav-main-sibling-margin-top
+
+  .left .button
+    height: $main-nav-left-button-size
+    line-height: $main-nav-left-button-size
+    font-size: $main-nav-left-button-font-size
+
+.open-nav, .y-enough
+  #tryKubernetes
+    margin-left: $nav-buttons-margin-left
+
+#hero
+  padding-top: $hero-padding-top
+
+#docs
+  #hero
+    h1, h5
+      padding-left: $full-width-paddingX
+      padding-right: $full-width-paddingX
+
+#vendorStrip
+  height: $vendor-strip-height
+  line-height: $vendor-strip-height
+  font-size: $vendor-strip-font-size

assets/sass/_skin.sass

@@ -0,0 +1,25 @@
+$blue: #3371e3
+$light-grey: #f7f7f7
+$dark-grey: #303030
+$medium-grey: #4c4c4c
+$white: #ffffff
+
+$base-font: 'Roboto', sans-serif
+$mono-font: 'Roboto Mono', monospace
+
+
+*, .button
+  box-sizing: border-box
+  font-family: $base-font
+  background: none
+  margin: 0
+  border: 0
+
+body
+  font-family: $base-font
+
+h1, h2, h5, p
+  font-weight: 300
+
+h3, h4
+  font-weight: 400

assets/sass/_tablet.sass

@@ -0,0 +1,248 @@
+// TEXT
+//$h1-font-size: 60px
+//$h1-line-height: 80px
+//
+//$h2-font-size: 42px
+//$h2-line-height: 60px
+//
+//$h3-font-size: 26px
+//$h3-line-height: 32px
+//
+//$h4-font-size: 26px
+//$h4-line-height: 40px
+//
+//$h5-font-size: 18px
+//$h5-line-height: 36px
+//
+//$p-font-size: 20px
+//$p-line-height: 28px
+
+
+// header
+$full-width-paddingX: 20px
+
+$main-width: 100%
+$main-max-width: 100%
+
+$header-height: 80px
+
+$logo-width: 180px
+
+$nav-buttons-margin-left: 30px
+
+$hamburger-size: 50px
+
+
+// main nav
+$main-nav-padding: 140px 0 30px
+$main-nav-h5-margin-bottom: 1em
+$main-nav-h3-margin-bottom: 0.6em
+$nav-box-width: 20%
+$nav-box-sibling-margin-left: calc(20% / 3)
+$main-nav-main-sibling-margin-top: 60px
+$main-nav-left-button-size: 50px
+$main-nav-left-button-font-size: 18px
+
+
+// hero
+$hero-padding-top: 80px
+$headline-wrapper-margin-bottom: 40px
+$quickstart-button-padding: 0 50px
+$vendor-strip-font-size: 16px
+
+//video
+$video-section-height: 400px
+
+//features
+$features-h3-margin-bottom: 40px
+$feature-box-margin-bottom: 60px
+$feature-box-div-margin-bottom: 0
+$feature-box-div-width: 45%
+
+
+
+////////////////////////////////////////////////////////////////////////////////////////////////////
+////////////////////////////////////////////////////////////////////////////////////////////////////
+////////////////////////////////////////////////////////////////////////////////////////////////////
+
+@media screen and (min-width: 750px)
+  @import "size"
+
+  p
+    font-size: 16px
+    line-height: 24px
+    letter-spacing: 0.1px
+
+  h1
+    font-size: 36px
+    line-height: 44px
+
+  h3
+    font-size: 28px
+    line-height: 36px
+
+  h4
+    font-size: 24px
+    line-height: 40px
+
+
+
+  #home
+    #viewDocs, #tryKubernetes
+      display: inline-block
+
+  #vendorStrip
+    display: block
+    text-align: center
+
+    img
+      max-height: 24px
+      vertical-align: middle
+      margin: 0 30px
+
+  #docs
+    #vendorStrip
+      li
+        a
+          font-size: 1em
+          font-weight: normal
+
+        li + li
+          margin-left: 60px
+
+
+  #oceanNodes
+    h3
+      text-align: left
+      margin-bottom: 18px
+
+    main, .main-section
+      position: relative
+      clear: both
+      display: table
+      height: 160px
+
+      .content
+        display: table-cell
+        position: relative
+        vertical-align: middle
+
+      .image-wrapper
+        position: absolute
+        top: 50%
+        max-width: 25%
+        max-height: 100%
+        transform: translateY(-50%)
+
+      &:nth-child(odd)
+        padding-right: 210px
+
+        .image-wrapper
+          right: 0
+
+      &:nth-child(even)
+        padding-left: 210px
+
+        .image-wrapper
+          left: 0
+
+      &:nth-child(1)
+        padding-right: 0
+
+        h3, p
+          text-align: center
+
+        .image-wrapper
+          position: relative
+          display: block
+          float: none
+          max-width: 100%
+          transform: none
+
+        .content
+          display: block
+
+      img
+        width: 100%
+
+
+  #video
+    height: $video-section-height
+    display: block
+
+    & > .light-text
+      display: block
+
+  #mobileShowVideoButton
+    display: none
+
+  #features
+    padding-bottom: 60px
+
+    .feature-box
+      margin-bottom: 30px
+
+      &:last-child
+        margin-bottom: 0
+
+    h3
+      margin-bottom: $features-h3-margin-bottom
+
+    .feature-box
+      & > div
+        width: $feature-box-div-width
+        margin-bottom: $feature-box-div-margin-bottom
+
+  #talkToUs
+    #bigSocial
+      div
+        width: calc(50% - 15px)
+
+      div + div
+        margin-top: 0
+
+      div:nth-child(2)
+        margin-left: 20px
+
+      div:nth-child(3)
+
+      div:nth-child(4)
+        margin-left: 20px
+
+      a
+        display: inline-block
+        color: $blue
+        font-weight: 400
+        text-decoration: none
+
+  // FOOTER
+  footer
+    nav
+      text-align: center
+
+      a
+        width: 30%
+        padding: 0 20px
+
+    .social
+      text-align: center
+
+      div
+        display: inline-block
+
+      div:last-child
+        display: block
+        margin: 0
+
+      span
+        display: inline-block
+        margin-right: 10px
+
+      input
+        text-align: left
+
+
+
+  #home #caseStudiesWrapper
+    div
+      width: 48%

assets/sass/style.sass

@@ -0,0 +1,11 @@
+@import "reset"
+@import "skin"
+
+// media queries
+@import "base"
+@import "tablet"
+@import "desktop"
+
+{{ if .Params.case_study_styles }}
+@import "case-studies"
+{{ end }}

case-studies/index.html

@@ -1,99 +0,0 @@
----
-title: Case Studies
-layout: basic
-class: gridPage
-cid: caseStudies
----
-
-<section id="hero" class="light-text">
-    <h1>Kubernetes User Case Studies</h1>
-    <h5>A collection of users running Kubernetes in production.</h5>
-</section>
-
-<section id="mainContent">
-    <main>
-        <div class="content">
-            <div class="case-studies">
-                <div class="case-study">
-                    <img src="/images/case_studies/pearson.png" alt="Pearson">
-                    <p class="quote">"We chose Kubernetes because of its flexibility, ease of management and the way it improves our engineers' productivity."</p>
-                    <!--<p class="attrib">— Chris Jackson, Director for Cloud Product Engineering, Pearson</p>-->
-                    <a href="./pearson/">Read about Pearson</a>
-                </div>
-                <div class="case-study">
-                    <img src="/images/case_studies/wikimedia.png" alt="Wikimedia">
-                    <p class="quote">"With Kubernetes, we're simplifying our environment and making it easier for developers to build the tools that make wikis run better."</p>
-                    <!--<p class="attrib">— Yuvi Panda, Operations Engineer, Wikimedia Foundation</p>-->
-                    <a href="./wikimedia/">Read about Wikimedia</a>
-                </div>
-                <div class="case-study">
-                    <img src="/images/case_studies/ebay.png" alt="eBay">
-                    <p class="quote">Inside eBay's shift to Kubernetes and containers atop OpenStack</p>
-                    <a href="http://www.nextplatform.com/2015/11/12/inside-ebays-shift-to-kubernetes-and-containers-atop-openstack/">Read about eBay</a>
-                </div>
-                <div class="case-study">
-                    <img src="/images/case_studies/box.png" alt="box">
-                    <p class="quote">Kubernetes at Box: Microservices at Maximum Velocity</p>
-                    <a href="https://blog.box.com/blog/kubernetes-box-microservices-maximum-velocity/">Read about Box</a>
-                </div>
-            </div>
-        </div>
-    </main>
-</section>
-
-<section id="video">
-    <main>
-        <!--<div>-->
-            <!--<h3>"I don't want to deploy software the old way ever again"</h3>-->
-            <!--<p class="attrib">— Dylan Carney, Lead Software Engineer, Zulily</p>-->
-            <!--<img src="/images/case_studies/zulily.png" id="zulilyLogo" alt="zulily">-->
-        <!--</div>-->
-        <!--<div><button onclick="kub.showVideo()"><img src="/images/case_studies/video_thumb.jpg" alt="Zulily video"><h6>Kubernetes at zulily</h6></button></div>-->
-        <div>
-            <!--<h3>SAP</h3>-->
-            <h3>SAP's OpenStack, running on Kubernetes in production</h3>
-            <img src="/images/case_studies/sap_small.png" id="zulilyLogo" alt="SAP">
-        </div>
-        <div><button onclick="kub.showVideo()"><img src="/images/case_studies/video_thumb1.png" alt="SAP video"><h6>Kubernetes at SAP</h6></button></div>
-    </main>
-</section>
-
-<section id="users">
-    <main>
-        <h3>Kubernetes Users</h3>
-        <div id="usersGrid">
-            <a target="_blank" href="https://www.youtube.com/watch?v=P5qfyv_zGcU"><img src="/images/case_studies/nyt.png" alt="New York Times"></a>
-            <a target="_blank" href="https://openai.com/blog/infrastructure-for-deep-learning"><img src="/images/case_studies/openai.png" alt="OpenAI"></a>
-            <a target="_blank" href="http://blogs.wsj.com/cio/2016/02/24/big-changes-in-goldmans-software-emerge-from-small-containers/"><img src="/images/case_studies/gs.png" alt="Goldman Sachs"></a>
-            <a target="_blank" href="https://youtu.be/4gyeixJLabo"><img src="/images/case_studies/sap.png" alt="SAP"></a>
-            <a target="_blank" href="http://www.nextplatform.com/2016/05/24/samsung-experts-put-kubernetes-paces/"><img src="/images/case_studies/sds.png" alt="Samsung SDS"></a>
-            <a target="_blank" href="http://thenewstack.io/wepay-kubernetes-changed-business/"><img src="/images/case_studies/wepay.png" alt="WePay"></a>
-            <a target="_blank" href="https://www.youtube.com/watch?v=5378N5iLb2Q"><img src="/images/case_studies/soundcloud.png" alt="SoundCloud"></a>
-            <a target="_blank" href="https://www.youtube.com/watch?v=F3iMkz_NSvU"><img src="/images/case_studies/homeoffice.png" alt="UK Home Office"></a>
-            <a target="_blank" href="http://searchitoperations.techtarget.com/news/450297178/Tech-firms-roll-out-Kubernetes-in-production"><img src="/images/case_studies/concur.png" alt="Concur"></a>
-            <a target="_blank" href="http://www.nextplatform.com/2015/08/04/amadeus-takes-off-with-containers-and-clouds/"><img src="/images/case_studies/amadeus.png" alt="Amadeus"></a>
-            <a target="_blank" href="http://superuser.openstack.org/articles/how-ancestry-com-s-open-source-strategy-combines-kubernetes-and-openstack"><img src="/images/case_studies/ancestry.png" alt="Ancestry.com"></a>
-            <a target="_blank" href="https://cloud.google.com/customers/ccp-games/"><img src="/images/case_studies/ccp.png" alt="CCP Games"></a>
-            <a target="_blank" href="https://www.openstack.org/videos/video/running-kubernetes-on-openstack-at-liveperson"><img src="/images/case_studies/liveperson.png" alt="LivePerson"></a>
-            <a target="_blank" href="https://youtu.be/YkOY7DgXKyw"><img src="/images/case_studies/monzo_logo.png" alt="monzo"></a>
-            <a target="_blank" href="https://blog.box.com/blog/kubernetes-box-microservices-maximum-velocity/"><img src="/images/case_studies/box_logo.png" alt="Box"></a>
-            <a target="_blank" href="https://cloudplatform.googleblog.com/2016/09/bringing-Pokemon-GO-to-life-on-Google-Cloud.html"><img src="/images/case_studies/pokemon_go_logo.png" alt="Pokemon GO"></a>
-            <a target="_blank" href="http://blog.kubernetes.io/2016/10/kubernetes-and-openstack-at-yahoo-japan.html"><img src="/images/case_studies/yahooJapan_logo.png" alt="Yahoo! Japan"></a>
-            <a target="_blank" href="https://cloud.google.com/customers/philips/"><img src="/images/case_studies/philips_logo.png" alt="Philips"></a>
-            <a target="_blank" href="https://youtu.be/EC_ZRLsw58M"><img src="/images/case_studies/buffer_logo.png" alt="buffer"></a>
-            <a target="_blank" href="https://youtu.be/lmeFkH-rHII"><img src="/images/case_studies/comcast_logo.png" alt="Comcast"></a>
-            <a href="./wikimedia/"><img src="/images/case_studies/wikimedia_logo.png" alt="Wikimedia"></a>
-            <a href="./pearson/"><img src="/images/case_studies/pearson_logo.png" alt="Pearson"></a>
-            <a target="_blank" href="#" onclick="event.preventDefault(); kub.showVideo()"><img src="/images/case_studies/zulily_logo.png" alt="zulily"></a>
-            <a target="_blank" href="http://www.nextplatform.com/2015/11/12/inside-ebays-shift-to-kubernetes-and-containers-atop-openstack/"><img src="/images/case_studies/ebay_logo.png" alt="Ebay"></a>
-            <a target="_blank" href="https://docs.google.com/a/google.com/forms/d/e/1FAIpQLScuI7Ye3VQHQTwBASrgkjQDSS5TP0g3AXfFhwSM9YpHgxRKFA/viewform" class="tell-your-story"><img src="/images/case_studies/story.png" alt="Tell your story"></a>
-        </div>
-    </main>
-</section>
-
-
-<div id="videoPlayer">
-    <!--<iframe data-url="https://www.youtube.com/watch?v=B0_5Nms8sD0" frameborder="0" allowfullscreen></iframe>-->
-    <iframe data-url="https://www.youtube.com/embed/4gyeixJLabo?autoplay=1" frameborder="0" allowfullscreen="true"></iframe>
-    <button id="closeButton"></button>
-</div>

case-studies/pearson.html

@@ -1,81 +0,0 @@
----
-title: Pearson Case Study
-layout: basic
-class: gridPage
-cid: caseStudies
----
-
-<section id="hero" class="light-text">
-    <h1> Pearson Case Study</h1>
-</section>
-
-<section id="mainContent">
-    <main>
-        <div class="content">
-            <h3 id="caseStudyTitle">Using Kubernetes to reinvent the world's largest educational company</h3>
-            <p>
-                Pearson, the world's education company, serving 75 million learners worldwide, set a goal to more than double that number to 200 million by 2025. A key part of this growth is in digital learning experiences, and that  requires an infrastructure platform that is able to scale quickly and deliver products to market faster. So Pearson's Cloud Technology team chose Kubernetes to help build a platform to meet the business requirements.            </p>
-            <div class="feature">
-                <img src="/images/case_studies/pearson.png" alt="Pearson">
-                <p class="quote">
-                    "To transform our infrastructure, we had to think beyond simply enabling automated provisioning, we realized we had to build a platform that would allow Pearson developers to build manage and deploy applications in a completely different way. We chose Kubernetes because of its flexibility, ease of management and the way it would improve our engineers' productivity."                </p>
-                <p class="attrib">— Chris Jackson, Director for Cloud Product Engineering, Pearson</p>
-            </div>
-        </div>
-    </main>
-</section>
-
-<section class="bullets">
-    <main>
-        <div class="content">
-            <div class="bullet">
-                <h4>Challenges:</h4>
-                <ul>
-                    <li>Pearson had difficulty in scaling and adapting to the growing online audience. They wanted to build and deliver content primarily over the web.</li>
-                </ul>
-            </div>
-            <div class="bullet">
-                <h4>Why Kubernetes:</h4>
-                <ul>
-                    <li>Kubernetes will allow Pearson's teams to develop their apps in a consistent manner, saving time and minimizing complexity.</li>
-                </ul>
-            </div>
-            <div class="bullet">
-                <h4>Approach:</h4>
-                <ul>
-                    <li>Build a centralized platform for use across the entire enterprise</li>
-                    <li>Use container technology as the core of the platform</li>
-                    <li>Deploy Kubernetes to manage the platform</li>
-                </ul>
-            </div>
-            <div class="bullet">
-                <h4>Results:</h4>
-                <ul>
-                    <li>Pearson is building an enterprise-wide platform for delivering innovative, web-based educational content. They expect engineers' productivity to increase by up to 20 percent.</li>
-                </ul>
-            </div>
-        </div>
-    </main>
-</section>
-
-<section class="details">
-    <main>
-        <div class="content">
-            <h4>Kubernetes powers a comprehensive developer experience</h4>
-            <p>Pearson wanted to use as much open source technology as possible for the platform given that it provides both technical and commercial benefits over the duration of the project. Jackson says, "Building an infrastructure platform based on open source technology in Pearson was a no-brainer, the sharing of technical challenges and advanced use cases in a community of people with talent far beyond what we could hire independently allows us to innovate at a level we could not reach on our own. Our engineers enjoy returning code to the community and participating in talks, blogs and meetings, it's a great way for us to allow our team to express themselves and share the pride they have in their work."</p>
-            <p>It also wanted to use a container-focused platform. Pearson has 400 development groups and diverse brands with varying business and technical needs. With containers, each brand could experiment with building new types of content using their preferred technologies, and then deliver it using containers. Pearson chose Kubernetes because it believes that is the best technology for managing containers, has the widest community support and offers the most flexible and powerful tools."</p>
-            <p>Kubernetes is at the core of the platform we've built for developers. After we get our big spike in back-to-school in traffic, much of Pearson's traffic will interact with Kubernetes. It is proving to be as effective as we had hoped," Jackson says.</p>
-        </div>
-    </main>
-</section>
-
-<section class="details">
-    <main>
-        <div class="content">
-            <h4>Encouraging experimentation, saving engineers time</h4>
-            <p>With the new platform, Pearson will increase stability and performance, and to bring products to market more quickly. The company says its engineers will also get a productivity boost because they won't spend time managing infrastructure. Jackson estimates 15 to 20 percent in productivity savings.</p>
-            <p>Beyond that, Pearson says the platform will encourage innovation because of the ease with which new applications can be developed, and because applications will be deployed far more quickly than in the past. It expects that will help the company meet its goal of reaching 200 million learners within the next 10 years.</p>
-            <p>"We're already seeing tremendous benefits with Kubernetes — improved engineering productivity, faster delivery of applications and a simplified infrastructure. But this is just the beginning. Kubernetes will help transform the way that educational content is delivered online," says Jackson.</p>
-        </div>
-    </main>
-</section>

case-studies/wikimedia.html

@@ -1,96 +0,0 @@
----
-title: Wikimedia Case Study
-layout: basic
-class: gridPage
-cid: caseStudies
----
-
-<section id="hero" class="light-text">
-    <h1> Wikimedia Case Study</h1>
-</section>
-
-<section id="mainContent">
-    <main>
-        <div class="content">
-            <h3 id="caseStudyTitle">Using Kubernetes to Build Tools to Improve the World's Wikis</h3>
-            <p>
-                The non-profit Wikimedia Foundation operates some of the largest collaboratively edited reference projects in the world, including Wikipedia. To help users maintain and use wikis, it runs Wikimedia Tool Labs, a hosting environment for community developers working on tools and bots to help editors and other volunteers do their work, including reducing vandalism. The community around Wikimedia Tool Labs began forming nearly 10 years ago.
-            </p>
-            <div class="feature">
-                <img src="/images/case_studies/wikimedia.png" alt="Wikimedia">
-                <p class="quote">
-                    "Wikimedia Tool Labs is vital for making sure wikis all around the world work as well as they possibly can. Because it's grown organically for almost 10 years, it has become an extremely challenging environment and difficult to maintain. It's like a big ball of mud — you really can't see through it. With Kubernetes, we're simplifying the environment and making it easier for developers to build the tools that make wikis run better."
-                </p>
-                <p class="attrib">— Yuvi Panda, operations engineer at Wikimedia Foundation and Wikimedia Tool Labs</p>
-            </div>
-        </div>
-    </main>
-</section>
-
-<section class="bullets">
-    <main>
-        <div class="content">
-            <div class="bullet">
-                <h4>Challenges:</h4>
-                <ul>
-                    <li>Simplify a complex, difficult-to-manage infrastructure</li>
-                    <li>Allow developers to continue writing tools and bots using existing techniques</li>
-                </ul>
-            </div>
-            <div class="bullet">
-                <h4>Why Kubernetes:</h4>
-                <ul>
-                    <li>Wikimedia Tool Labs chose Kubernetes because it can mimic existing workflows, while reducing complexity</li>
-                </ul>
-            </div>
-            <div class="bullet">
-                <h4>Approach:</h4>
-                <ul>
-                    <li>Migrate old systems and a complex infrastructure to Kubernetes</li>
-                </ul>
-            </div>
-            <div class="bullet">
-                <h4>Results:</h4>
-                <ul>
-                    <li>20 percent of web tools that account for more than 40 percent of web traffic now run on Kubernetes</li>
-                    <li>A 25-node cluster that keeps up with each new Kubernetes release</li>
-                    <li>Thousands of lines of old code have been deleted, thanks to Kubernetes</li>
-                </ul>
-            </div>
-        </div>
-    </main>
-</section>
-
-<section class="details">
-    <main>
-        <div class="content">
-            <h4>Using Kubernetes to provide tools for maintaining wikis</h4>
-            <p>
-                Wikimedia Tool Labs is run by a staff of four-and-a-half paid employees and two volunteers. The infrastructure didn't make it easy or intuitive for developers to build bots and other tools to make wikis work more easily. Yuvi says, "It's incredibly chaotic. We have lots of Perl and Bash duct tape on top of it. Everything is super fragile."
-            </p>
-            <p>
-                To solve the problem, Wikimedia Tool Labs migrated parts of its infrastructure to Kubernetes, in preparation for eventually moving its entire system. Yuvi said Kubernetes greatly simplifies maintenance. The goal is to allow developers creating bots and other tools to use whatever development methods they want, but make it easier for the Wikimedia Tool Labs to maintain the required infrastructure for hosting and sharing them.
-            </p>
-            <p>
-                "With Kubernetes, I've been able to remove a lot of our custom-made code, which makes everything easier to maintain. Our users' code also runs in a more stable way than previously," says Yuvi.
-            </p>
-        </div>
-    </main>
-</section>
-
-<section class="details">
-    <main>
-        <div class="content">
-            <h4>Simplifying infrastructure and keeping wikis running better</h4>
-            <p>
-                Wikimedia Tool Labs has seen great success with the initial Kubernetes deployment. Old code is being simplified and eliminated, contributing developers don't have to change the way they write their tools and bots, and those tools and bots run in a more stable fashion than they have in the past. The paid staff and volunteers are able to better keep up with fixing issues.
-            </p>
-            <p>
-                In the future, with a more complete migration to Kubernetes, Wikimedia Tool Labs expects to make it even easier to host and maintain the bots and tools that help run wikis across the world. The tool labs already host approximately 1,300 tools and bots from 800 volunteers, with many more being submitted every day. Twenty percent of the tool labs' web tools that account for more than 60 percent of web traffic now run on Kubernetes. The tool labs has a 25-node cluster that keeps up with each new Kubernetes release. Many existing web tools are migrating to Kubernetes.
-            </p>
-            <p>
-                "Our goal is to make sure that people all over the world can share knowledge as easily as possible. Kubernetes helps with that, by making it easier for wikis everywhere to have the tools they need to thrive," says Yuvi.
-            </p>
-        </div>
-    </main>
-</section>

cn/README.md

@@ -1,18 +0,0 @@
-## 如何参与 Kubernetes 文档汉化工作
-
-我们非常欢迎，非常希望您参与 Kubernetes 文档汉化做出贡献。
-
-您可以单击屏幕右上角的 **Fork** 按钮，在您的 Github 账户中创建一外名为 *fork* 的存储库副本。在您的分支中进行更改，当您准备好将这些更改发送给我们时，请转到您的仓库创建新的 pull 请求，让我们知道这一点。
-
-关于更多的贡献信息，请参阅:
-
-* [贡献于 Kubernetes 文档](http://kubernetes.io/editdocs/)
-* [创建文档拉取请求](http://kubernetes.io/docs/contribute/create-pull-request/)
-* [写一个新的话题](http://kubernetes.io/docs/contribute/write-new-topic/)
-* [暂停您的文档更改](http://kubernetes.io/docs/contribute/stage-documentation-changes/)
-* [更用页面模板](http://kubernetes.io/docs/contribute/page-templates/)
-* [文档样式指南](http://kubernetes.io/docs/contribute/style-guide/)
-
-## 谢谢您!
-
-Kubernetes 在社区参与中茁壮成长，我们非常感谢您对我们的网站和文档的贡献！

cn/_includes/user-guide-content-moved.md

@@ -1,2 +0,0 @@
-Kubernetes 文档的 [用户指南](/docs/user-guide/) 部分中的主题将被移动到 [任务](/docs/tasks/)、[教程](/docs/tutorials/)和
-[概念](/docs/concepts) 部分。 本主题的内容已转移到:

cn/docs/concepts/overview/what-is-kubernetes.md

@@ -1,119 +0,0 @@
----
-assignees:
-- k8s-merge-robot
-
-title: 认识 Kubernetes?
----
-
-Kubernetes 是一个 [开源的容器调度平台，它可以自动化应用容器的部署、扩展和操作](http://www.slideshare.net/BrianGrant11/wso2con-us-2015-kubernetes-a-platform-for-automating-deployment-scaling-and-operations) 可以跨主机集群, 提供以容器为中心的基础架构。
-
-使用 Kubernetes, 您可以快速高效地响应客户需求:
-
- - 快速、可预测地部署您的应用程序
- - 拥有即时扩展应用程序的能力
- - 不影响现有业务的情况下，无缝地发布新功能。
- - 优化您的硬件资源，降低您的拥有成本
-
-我们的目标是构建一个软件和工具的生态系统，以减轻您在公共云或私有云运行应用程序的负担。
-
-#### Kubernetes 具有如下特点:
-
-* **便携性**: 无论公有云、私有云、混合云还是多云架构都全面支持
-* **可扩展**: 它是模块化、可插拔、可挂载、可组合的，支持各种形式的扩展
-* **自修复**: 它可以自保持应用状态、可自重启、自复制、自缩放的，通过声明式语法提供了强大的自修复能力
-
-Kubernetes 项目由 Google 公司在 2014 年启动。Kubernetes 建立在 [Google 公司超过十余年的运维经验基础之上，Google 所有的应用都运行在容器上](https://research.google.com/pubs/pub43438.html), 再与社区中最好的想法和实践相结合，也许它是最受欢迎的容器平台。
-
-##### 准备好 [开始](/docs/getting-started-guides/)?
-
-## 为什么是容器?
-
-查看此文，可以了解为什么您要使用容器 [容器](http://aucouranton.com/2014/06/13/linux-containers-parallels-lxc-openvz-docker-and-more/)?
-
-![为什么是容器?](/images/docs/why_containers.svg)
-
-*传统* 部署应用程序的方式，一般是使用操作系统自带的包管理器在主机上安装应用依赖，之后再安装应用程序。这无疑将应用程序的可执行文件、应用的配置、应用依赖库和应用的生命周期与宿主机操作系统进行了紧耦合。在此情境下，可以通过构建不可改变的虚拟机镜像版本，通过镜像版本实现可预测的发布和回滚，但是虚拟机实在是太重量级了，且镜像体积太庞大，便捷性差。
-
-*新方式* 是基于操作系统级虚拟化而不是硬件级虚拟化方法来部署容器。容器之间彼此隔离并与主机隔离：它们具有自己的文件系统，不能看到彼此的进程，并且它们所使用的计算资源是可以被限制的。它们比虚拟机更容易构建，并且因为它们与底层基础架构和主机文件系统隔离，所以它们可以跨云和操作系统快速分发。
-
-由于容器体积小且启动快，因此可以在每个容器镜像中打包一个应用程序。这种一对一的应用镜像关系拥有很多好处。使用容器，不需要与外部的基础架构环境绑定, 因为每一个应用程序不需要外部依赖，更不需要与外部的基础架构环境依赖。完美解决了从开发到生产环境的一致性问题。
-
-类似地，容器比虚拟机更加透明，这有助于监测和管理。真实的情况是，容器进程的生命周期由基础设施管理，而容器内的进程对外是隐藏的。最后，每个应用程序用容器封装，管理容器部署就等同于管理应用程序部署。
-
-容器好处摘要:
-
-* **敏捷的应用程序创建和部署**:
-    与虚拟机镜像相比，容器镜像更容易创建，提升了硬件的使用效率。
-* **持续开发、集成和部署**:
-    提供可靠与频繁的容器镜像构建和部署，可以很方便及快速的回滚 (由于镜像不可变性).
-* **关注开发与运维的分离**:
-    在构建/发布时创建应用程序容器镜像，从而将应用程序与基础架构分离。
-* **开发、测试和生产环境的一致性**:
-    在笔记本电脑上运行与云中一样。
-* **云和操作系统的可移植性**:
-    可运行在 Ubuntu, RHEL, CoreOS, 内部部署, Google 容器引擎和其他任何地方。
-* **以应用为中心的管理**:
-    提升了操作系统的抽象级别，以便在使用逻辑资源的操作系统上运行应用程序。
-* **松耦合、分布式、弹性伸缩 [微服务](http://martinfowler.com/articles/microservices.html)**:
-    应用程序被分成更小，更独立的部分，可以动态部署和管理 - 而不是巨型单体应用运行在专用的大型机。
-* **资源隔离**:
-    通过对应用进行资源隔离，可以很容易的预测应用程序性能。
-* **资源利用**:
-    高效率和高密度。
-
-#### 为什么我们需要 Kubernetes，它能做什么?
-
-最基础的，Kubernetes 可以在物理或虚拟机集群上调度和运行应用程序容器。然而，Kubernetes 还允许开发人员从物理和虚拟机'脱离'，从以**主机为中心**的基础架构转移到以**容器为中心**的基础架构，这样可以提供容器固有的全部优点和益处。Kubernetes 提供了基础设施来构建一个真正以**容器为中心**的开发环境。
-
-Kubernetes 满足了生产中运行应用程序的许多常见的需求，例如：
-
-* [Pod](/docs/user-guide/pods/) 提供复合应用并保留一个应用一个容器的容器模型,
-* [挂载外部存储](/docs/user-guide/volumes/),
-* [Secret管理](/docs/user-guide/secrets/),
-* [应用健康检查](/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks),
-* [副本应用实例](/docs/user-guide/replication-controller/),
-* [横向自动扩缩容](/docs/user-guide/horizontal-pod-autoscaling/),
-* [服务发现](/docs/user-guide/connecting-applications/),
-* [负载均衡](/docs/user-guide/services/),
-* [滚动更新](/docs/user-guide/update-demo/),
-* [资源监测](/docs/user-guide/monitoring/),
-* [日志采集和存储](/docs/user-guide/logging/overview/),
-* [支持自检和调试](/docs/user-guide/introspection-and-debugging/),
-* [认证和鉴权](/docs/admin/authorization/).
-
-这提供了平台即服务 (PAAS) 的简单性以及基础架构即服务 (IAAS) 的灵活性，并促进跨基础设施供应商的可移植性。
-
-有关详细信息，请参阅 [用户指南](/docs/user-guide/).
-
-#### 为什么 Kubernetes 是一个平台?
-
-Kubernetes 提供了很多的功能，总会有新的场景会受益于新特性。它可以简化应用程序的工作流，加快开发速度。被大家认可的应用编排通常需要有较强的自动化能力。这就是为什么 Kubernetes 被设计作为构建组件和工具的生态系统平台，以便更轻松地部署、扩展和管理应用程序。
-
-[Label](/docs/user-guide/labels/) 允许用户按照自己的方式组织管理对应的资源。 [注解](/docs/user-guide/annotations/) 使用户能够以自定义的描述信息来修饰资源，以适用于自己的工作流，并为管理工具提供检查点状态的简单方法。
-
-此外，[Kubernetes 控制面](/docs/admin/cluster-components) 是构建在相同的 [APIs](/docs/api/) 上面，开发员人和用户都可以用。用户可以编写自己的控制器， [调度器](https://git.k8s.io/community/contributors/devel/scheduler.md)等等，如果这么做，根据新加的[自定义 API](https://git.k8s.io/community/contributors/design-proposals/extending-api.md) ，可以扩展当前的通用 [CLI 命令行工具](/docs/user-guide/kubectl-overview/)。
-
-这种 [设计](https://git.k8s.io/community/contributors/design-proposals/principles.md) 使得许多其他系统可以构建在 Kubernetes 之上。
-
-#### Kubernetes 不是什么:
-
-Kubernetes 不是一个传统意义上，包罗万象的 PaaS (平台即服务) 系统。我们保留用户选择的自由，这非常重要。
-
-* Kubernetes 不限制支持的应用程序类型。 它不插手应用程序框架 (例如 [Wildfly](http://wildfly.org/)), 不限制支持的语言运行时 (例如 Java, Python, Ruby)，只迎合符合 [12种因素的应用程序](http://12factor.net/)，也不区分"应用程序"与"服务"。Kubernetes 旨在支持极其多样化的工作负载，包括无状态、有状态和数据处理工作负载。如果应用可以在容器中运行，它就可以在 Kubernetes 上运行。
-* Kubernetes 不提供作为内置服务的中间件 (例如 消息中间件)、数据处理框架 (例如 Spark)、数据库 (例如 mysql)或集群存储系统 (例如 Ceph)。这些应用可以运行在 Kubernetes 上。
-* Kubernetes 没有提供点击即部署的服务市场
-* Kubernetes 从源代码到镜像都是非垄断的。 它不部署源代码且不构建您的应用程序。 持续集成 (CI) 工作流是一个不同用户和项目都有自己需求和偏好的领域。 所以我们支持在 Kubernetes 分层的 CI 工作流，但不指定它应该如何工作。
-* Kubernetes 允许用户选择其他的日志记录，监控和告警系统 (虽然我们提供一些集成作为概念验证)
-* Kubernetes 不提供或授权一个全面的应用程序配置语言/系统 (例如 [jsonnet](https://github.com/google/jsonnet)).
-* Kubernetes 不提供也不采用任何全面机器配置、保养、管理或自我修复系统
-
-另一方面，许多 PaaS 系统*运行*在 Kubernetes 上面，例如  [Openshift](https://github.com/openshift/origin), [Deis](http://deis.io/), and [Eldarion](http://eldarion.cloud/)。 您也可以自定义您自己的 PaaS, 与您选择的 CI 系统集成，或与 Kubernetes 一起使用: 将您的容器镜像部署到 Kubernetes。
-
-由于 Kubernetes 在应用级别而不仅仅在硬件级别上运行，因此它提供 PaaS 产品通用的一些功能，例如部署、扩展、负载均衡、日志记录、监控等。但是，Kubernetes 不是单一的，默认解决方案是可选和可插拔的。
-
-此处，Kubernetes 不仅仅是一个 "编排系统"；它消除了编排的需要。 "编排"技术定义的是工作流的执行: 从 A 到 B，然后到 C。相反，Kubernetes 是包括一套独立、可组合的控制过程，通过声明式语法使其连续地朝着期望状态驱动当前状态。 不需要告诉它具体从 A 到 C 的过程，只要告诉到 C 的状态即可。 也不需要集中控制；该方法更类似于"编舞"。这使得系统更容易使用并且更强大、更可靠、更具弹性和可扩展性。
-
-#### *Kubernetes* 是什么意思? K8s?
-
-名称 **Kubernetes** 源于希腊语，意为 "舵手" 或 "飞行员"， 且是英文 "governor" 和 ["cybernetic"](http://www.etymonline.com/index.php?term=cybernetics)的词根。 **K8s** 是通过将 8 个字母 "ubernete" 替换为 8 而导出的缩写。另外，在中文里，k8s 的发音与 Kubernetes 的发音比较接近。
-