Modify apparmor.md based on PR - Fix site build (#16531) (#16650)

Modify apparmor.md and delete .profile to enable the site to
build with Hugo 0.57.2. Could not cherry pick PR 16531 because
the Korean translation was added in 1.14.
See also PRs #16104 and #16151.

zh/docs/reference/setup-tools/kubeadm/generated/README.md updated to fix
'invalid YAML delimiter' compile error caused by HTML comment.

Signed-off-by: Aimee Ukasick <aimeeu.opensource@gmail.com>

.dockerignore

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

.github/ISSUE_TEMPLATE.md

@@ -1,4 +1,5 @@
 <!-- Thanks for filing an issue! Before submitting, please fill in the following information. -->
+<!-- See https://kubernetes.io/docs/contribute/start/ for guidance on writing an actionable issue description. -->
 
 <!--Required Information-->
 
@@ -14,7 +15,7 @@
 
 
 **Page to Update:**
-http://kubernetes.io/...
+https://kubernetes.io/...
 
 <!--Optional Information (remove the comment tags around information you would like to include)-->
 <!--Kubernetes Version:-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,6 +1,13 @@
-> NOTE: Please check the “Allow edits from maintainers” box (see image below) to  
-> [allow reviewers to fix problems](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) on your patch and speed up the review process.
->
+>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 > Please delete this note before submitting the pull request.
+>
+> For 1.13 Features: set Milestone to 1.13 and Base Branch to dev-1.13
+>
+> Help editing and submitting pull requests:
+> https://kubernetes.io/docs/contribute/start/#improve-existing-content.
+>
+> Help choosing which branch to use:
+> https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use.
+>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+>
 
-![Allow edits from maintainers checkbox](https://help.github.com/assets/images/help/pull_requests/allow-maintainers-to-make-edits-sidebar-checkbox.png)

.gitignore

@@ -1,11 +1,11 @@
 **/.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 +24,17 @@ Session.vim
 tags
 
 kubernetes.github.io.iml
+
+nohup.out
+
+# Hugo output
+public/
+resources/
+
+# User-specific editorconfig files
+.editorconfig
+
+# Netlify Functions build output
+package-lock.json
+functions/
+node_modules/

.travis.yml

@@ -1,29 +1,34 @@
 language: go
 go:
-  - 1.8.1
+  - 1.10.2
 
-# 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
+env:
+  - HUGO_VERSION=0.49
 
-# (1) Fetch dependencies for us to run the tests in test/examples_test.go
-- go get -t -v k8s.io/kubernetes.github.io/test
+jobs:
+  include:
+    - name: "Testing examples"
+      # 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/website && cd $HOME/gopath/src/k8s.io/website
 
-# Simplified deduplication of dependencies.
-- cp -L -R $GOPATH/src/k8s.io/kubernetes/vendor/ $GOPATH/src/
-- rm -r $GOPATH/src/k8s.io/kubernetes/vendor/
+      # Make sure we are testing against the correct branch
+      - pushd $GOPATH/src/k8s.io && git clone https://github.com/kubernetes/kubernetes && popd
+      - pushd $GOPATH/src/k8s.io/kubernetes && git checkout release-1.11 && popd
+      - 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
+      # Fetch additional dependencies to run the tests in examples/examples_test.go
+      - go get -t -v k8s.io/website/content/en/examples
+      script:
+      - go test -v k8s.io/website/content/en/examples
+    - name: "Hugo build"
+      install:
+      - curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_${HUGO_VERSION}_linux-64bit.tar.gz | tar -xz
+      - mkdir -p ${TRAVIS_HOME}/bin
+      - mv hugo ${TRAVIS_HOME}/bin
+      - export PATH=${TRAVIS_HOME}/bin:$PATH
+      script:
+      - hugo

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,33 @@
+# 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 && \
+    curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_${HUGO_VERSION}_linux-64bit.tar.gz | tar -xz && \
+    mv hugo /usr/local/bin/hugo && \
+    #curl -L https://bin.equinox.io/c/dhgbqpS8Bvy/minify-stable-linux-amd64.tgz | tar -xz && \
+    #mv minify /usr/local/bin && \
+    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,48 @@
-.PHONY: all build build-preview help serve
+DOCKER       = docker
+HUGO_VERSION = 0.49
+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 sass 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
 
-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 -D -F
+
+functions-build:
+	$(NETLIFY_FUNC) build functions-src
+
+check-headers-file:
+	scripts/check-headers-file.sh
+
+production-build: build check-headers-file ## Build the production site and ensure that noindex headers aren't added
+
+non-production-build: ## Build the non-production site, which adds noindex headers to prevent indexing
+	hugo --enableGitInfo
+
+sass-build:
+	scripts/sass.sh build
+
+sass-develop:
+	scripts/sass.sh develop
 
 serve: ## Boot the development server.
-	jekyll serve
+	hugo server --ignoreCache --disableFastRender
+
+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 --watch --bind 0.0.0.0

OWNERS

@@ -1,6 +1,10 @@
-assignees:
-- smarterclayton
-- janetkuo
-- pwittrock
-- kelseyhightower
-- jaredbhatti
+# Reviewers can /lgtm /approve but not sufficient for auto-merge without an
+# approver
+reviewers:
+- sig-docs-en-reviews 
+
+# Approvers have all the ability of reviewers but their /approve makes
+# auto-merge happen if a /lgtm exists, or vice versa, or they can do both
+# No need for approvers to also be listed as reviewers
+approvers:
+- sig-docs-en-owners

OWNERS_ALIASES

@@ -0,0 +1,299 @@
+aliases:
+  sig-api-machinery: #Team: API Server; GH: sig-api-machinery-pr-reviews; e.g. Annotations, Labels
+    - lavalamp
+    - sttts
+    - liggitt
+    - smarterclayton
+    - deads2k
+  sig-apps: #Team: Workloads; GH: sig-apps-pr-reviews; e.g. ConfigMaps, CronJobs, CustomResourceDefinitions, DaemonSets, Deployments, Jobs, Secrets, StatefulSets
+    - enisoc
+    - erictune
+    - foxish
+    - janetkuo
+    - kow3ns
+    - lukaszo
+    - mfojtik
+    - smarterclayton
+    - soltysh
+    - tnozicka
+  sig-architecture: #GH: sig-architecture-pr-reviews
+    - smarterclayton
+    - bgrant0607
+  sig-auth: #GH: sig-auth-pr-reviews
+    - php-coder
+    - liggitt
+    - mikedanese
+    - ericchiang
+    - mattmoyer
+    - enj
+    - deads2k
+    - davidopp
+  sig-autoscaling: #GH: sig-autoscaling-pr-reviews
+    - DirectXMan12
+    - bskiba
+    - aleksandra-malinowska
+    - MaciekPytel
+    - davidopp
+    - mwielgus
+  sig-aws: #Amazon AWS
+    - justinsb
+    - kris-nova
+    - chrislovecnm
+    - mfburnett
+  sig-azure: #Microsoft Azure
+    - andyzhangx
+    - feiskyer
+    - justaugustus
+    - karataliu
+    - khenidak
+  sig-big-data: #GH: sig-big-data-pr-reviews
+    - foxish
+  sig-cli: #Team: CLI; GH: sig-cli-pr-reviews; e.g. kubectl
+    - adohe
+    - deads2k
+    - derekwaynecarr
+    - dims
+    - dshulyak
+    - eparis
+    - ericchiang
+    - ghodss
+    - mengqiy
+    - rootfs
+    - shiywang
+    - smarterclayton
+    - soltysh
+    - sttts
+  sig-cluster-lifecycle-kubeadm-approvers: # Approving changes to kubeadm documentation
+    - timothysc
+    - lukemarsden
+    - luxas
+    - roberthbailey
+    - fabriziopandini
+  sig-cluster-lifecycle-kubeadm-reviewers: # Reviewing kubeadm documentation
+    - timothysc
+    - lukemarsden
+    - luxas
+    - roberthbailey
+    - fabriziopandini
+    - kad
+    - xiangpengzhao
+    - stealthybox
+    - liztio
+    - chuckha
+    - detiber
+    - dixudx
+  sig-cluster-ops:
+    - zehicle
+    - jdumars
+  sig-contribex: #aka Contributor Experience; GH: sig-contributor-experience-pr-reviews
+    - rmmh
+    - cblecker
+    - apelisse
+    - grodrigues3
+    - spxtr
+  sig-contributor-experience: #GH: sig-contributor-experience-pr-reviews
+    - rmmh
+    - cblecker
+    - apelisse
+    - grodrigues3
+    - spxtr
+  sig-docs: #Team: documentation; GH: sig-docs-maintainers
+    - bradamant3
+    - bradtopol
+    - chenopis
+    - cody-clark
+    - jaredbhatti
+    - kbarnard10
+    - mistyhacks
+    - ryanmcginnis
+    - steveperry-53
+    - tengqm
+    - tfogo
+    - xiangpengzhao
+    - zacharysarah
+    - zhangxiaoyu-zidif
+    - zparnold
+  sig-docs-en-owners: #Team: Documentation; GH: sig-docs-en-owners
+    - bradamant3
+    - bradtopol
+    - chenopis
+    - cody-clark
+    - jaredbhatti
+    - kbarnard10
+    - mistyhacks
+    - ryanmcginnis
+    - steveperry-53
+    - stewart-yu
+    - tengqm
+    - tfogo
+    - zacharysarah
+    - zparnold
+  sig-docs-en-reviews: #Team: Documentation; GH: sig-docs-pr-reviews
+    - jimangel
+    - rajakavitha1
+    - stewart-yu
+    - xiangpengzhao
+    - zhangxiaoyu
+  sig-docs-ja-owners: #Team: Japanese docs localization; GH: sig-docs-ja-owners
+    - cstoku
+    - nasa9084
+    - tnir
+    - zacharysarah
+  sig-docs-ja-reviews: #Team: Japanese docs PR reviews; GH:sig-docs-ja-reviews
+    - cstoku
+    - makocchi-git
+    - MasayaAoyama
+    - nasa9084
+    - tnir
+  sig-docs-ko-owners: #Team Korean docs localization; GH: sig-docs-ko-owners
+    - ClaudiaJKang
+    - gochist
+    - bradamant3    # Temporary for 1.13 release
+    - jimangel      # Temporary for 1.13 release
+    - tfogo         # Temporary for 1.13 release
+    - zacharysarah
+  sig-docs-ko-reviews: #Team Korean docs reviews; GH: sig-docs-ko-reviews
+    - ClaudiaJKang
+    - gochist
+    - ianychoi
+  sig-docs-zh-owners: #Team Chinese docs localization; GH: sig-docs-zh-owners
+    - bradtopol
+    - chenopis
+    - chenrui333
+    - dchen1107
+    - haibinxie
+    - hanjiayao
+    - lichuqiang
+    - lucperkins
+    - markthink
+    - SataQiu
+    - tengqm
+    - xiangpengzhao
+    - xichengliudui
+    - zacharysarah
+    - zhangxiaoyu-zidif
+    - bradamant3    # Temporary for 1.13 release
+    - jimangel      # Temporary for 1.13 release
+    - tfogo         # Temporary for 1.13 release
+  sig-docs-zh-reviews: #Team Chinese docs reviews; GH: sig-docs-zh-reviews
+    - AdamDang
+    - chenrui333
+    - idealhack
+    - markthink
+    - Mr-Linus
+    - SataQiu
+    - tengqm
+    - xiangpengzhao
+    - xichengliudui
+    - zhangxiaoyu-zidif
+    - pigletfly
+  sig-federation: #Team: Federation; e.g. Federated Clusters
+    - csbell
+  sig-gcp: #Google Cloud Platform; GH: sig-gcp-pr-reviews
+    - abgworrall
+  sig-instrumentation: #GH: sig-instrumentation-pr-reviews; e.g. metrics, logging, events
+    - DirectXMan12
+    - x13n
+    - kawych
+    - brancz
+    - fabxc
+    - loburm
+    - piosz
+    - fgrzadkowski
+  sig-multicluster: #GH: sig-multicluster-pr-reviews; e.g. resiliency against availability zone outages; hybrid clouds; spanning multiple cloud providers; migration to public clouds
+    - madhusudancs
+    - marun
+    - jianhuiz
+    - shashidharatd
+    - nikhiljindal
+    - quinton-hoole
+    - mwielgus
+    - csbell
+  sig-network: #Team: Network; GH: sig-network-pr-reviews; e.g. Ingress, Network Policies, Services
+    - bowei
+    - caseydavenport
+    - danwinship
+    - dcbw
+    - dnardo
+    - freehan
+    - mrhohn
+    - nicksardo
+    - thockin
+  sig-node: #Team: Node; GH: sig-node-pr-reviews; e.g. Containers, Docker, Images, OS images, Pods, Registries
+    - Random-Liu
+    - dashpole
+    - dchen1107
+    - derekwaynecarr
+    - dims
+    - feiskyer
+    - mtaufen
+    - ncdc
+    - pmorie
+    - resouer
+    - sjpotter
+    - tallclair
+    - tmrts
+    - vishh
+    - yifan-gu
+    - yujuhong
+  sig-onprem: #On-premises; GH: sig-onprem-pr-reviews
+    - zen
+    - idvoretskyi
+    - pigmej
+    - feiskyer
+    - nebril
+  sig-openstack: #GH: sig-openstack-pr-reviews
+    - hogepodge
+    - dklyle
+    - rjmorse
+  sig-pm: #aka Product Management
+    - apsinha
+    - idvoretskyi
+    - calebamiles
+  sig-product-management:
+    - apsinha
+    - idvoretskyi
+    - calebamiles
+  sig-release: #GH: sig-release-pr-reviews
+    - calebamiles
+    - enisoc
+    - pwittrock
+  sig-rktnetes:
+    - calebamiles
+  sig-scalability: #GH: sig-scalability-pr-reviews
+    - jbeda
+    - spiffxp
+    - lavalamp
+    - countspongebob
+  sig-scheduling: #Team: Sharing; GH: sig-scheduling-pr-reviews; e.g. Scheduler
+    - bsalamat
+    - davidopp
+    - jayunit100
+    - k82cn
+    - resouer
+    - timothysc
+    - wojtek-t
+  sig-service-catalog: #GH: sig-service-catalog-pr-reviews; e.g. Service Broker
+    - pmorie
+    - jessfraz
+    - pwittrock
+    - droot
+    - seans3
+  sig-storage: #Team: Storage; GH: sig-storage-pr-reviews; e.g. Volumes
+    - childsb
+    - jsafrane
+    - rootfs
+    - saad-ali
+    - matchstick
+    - msau42
+  sig-testing: #GH: sig-testing-pr-reviews
+    - fejta
+    - ixdy
+    - rmmh
+    - spiffxp
+    - spxtr
+  sig-ui: #User Interface
+    - danielromlein
+    - floreks
+  sig-windows:
+    - michmike

README.md

@@ -1,19 +1,55 @@
-## Instructions for Contributing to the Kubernetes Documentation
+# The Kubernetes documentation
 
-Welcome! We are very pleased you want to contribute to the Kubernetes documentation.
+Welcome! This repository houses all of the assets required to build the Kubernetes website and documentation. We're very pleased that you want to contribute!
 
-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.
+## 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 originally 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/)
+
+## Running the site 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 site 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 site 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 site locally:
+
+```bash
+make docker-serve
+```
+
+Open up your browser to http://localhost:1313 to view the site. As you make changes to the source files, Hugo updates the site and forces a browser refresh.
+
+## Running the site locally using 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.
+
+To run the site 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 site. As you make changes to the source files, Hugo updates the site and forces a browser refresh.
 
 ## 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 really appreciate your contributions to our site 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 Team to reach out
+# to for triaging and handling of incoming issues.
+#
+# The below names agree to abide by the
+# [Embargo Policy](https://github.com/kubernetes/sig-release/blob/master/security-release-process-documentation/security-release-process.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/
+
+chenopis
+bradamant3
+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.7.0"
-      version: "v1.7"
-      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,98 +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: Extending the Kubernetes API
-  section:
-  - docs/concepts/api-extension/custom-resources.md
-  - docs/concepts/api-extension/apiserver-aggregation.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
-    - docs/concepts/workloads/pods/disruptions.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
-  - docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.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
-  - docs/concepts/cluster-administration/controller-metrics.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,97 +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/extensible-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/node.md
-    - docs/admin/authorization/webhook.md
-  - docs/reference/deprecation-policy.md
-
-- title: API Reference
-  section:
-  - title: v1.7
-    path: /docs/api-reference/v1.7/
-  - 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.7 Commands
-    path: /docs/user-guide/kubectl/v1.7/
-  - 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,171 +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
-  - docs/tasks/run-application/configure-pdb.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/events-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-custom-resource-definitions.md
-  - docs/tasks/access-kubernetes-api/extend-api-third-party-resource.md
-  - docs/tasks/access-kubernetes-api/migrate-third-party-resource.md
-  - docs/tasks/access-kubernetes-api/configure-aggregation-layer.md
-  - docs/tasks/access-kubernetes-api/setup-extension-api-server.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/securing-a-cluster.md
-  - docs/tasks/administer-cluster/encrypt-data.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/kubeadm-upgrade-1-7.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
-  - docs/tasks/administer-cluster/dns-custom-nameservers.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/federation/set-up-placement-policies-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
-  - docs/tasks/manage-daemon/rollback-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/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>

_layouts/none.html

@@ -1 +0,0 @@
-{{ content }}

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

archetypes/default.md

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

case-studies/box.html

@@ -1,127 +0,0 @@
----
-title: Box Case Study
-layout: none
-class: gridPage
-cid: caseStudies
----
-<!DOCTYPE html>
-<html>
-  <head>
-    <meta charset="utf-8">
-    <meta name="viewport" content="width=device-width, initial-scale=1">
-      <link href="https://fonts.googleapis.com/css?family=Roboto:300,400" rel="stylesheet">
-      <link rel="stylesheet" type="text/css" href="/css/style_box.css">
-    <title>Box Case Study</title>
-  </head>
-<body>
-
-
-<div class="banner1">
-  <h1>CASE STUDY: <img src="/images/box_logo.png" class="logo" width="10%" style="margin-bottom:-6px"><br>
-    <div class="subhead">An Early Adopter Envisions
-      a New Cloud Platform</div>
-  </h1>
-</div>
-
-
-<div class="details">
-    Company &nbsp;<b>Box</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Location &nbsp;<b>Redwood City, California</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Industry &nbsp;<b>Technology</b>
-</div>
-
-<hr>
-
-<section class="section1">
-
-<div class="cols">
-  <div class="col1">
-
-      <h2>Challenge</h2>
-        Founded in 2005, the enterprise content management company allows its more than 50 million users to manage content in the cloud. <a href="https://www.box.com/home">Box</a> was built primarily with bare metal inside the company’s own data centers, with a monolithic PHP code base. As the company was expanding globally, it needed to focus on "how we run our workload across many different cloud infrastructures from bare metal to public cloud," says Sam Ghods, Cofounder and Services Architect of Box. "It’s been a huge challenge because different clouds, especially bare metal, have very different interfaces."
-        <br>
-  </div>
-
-
-  <div class="col2">
-    <h2>Solution</h2>
-      Over the past couple of years, Box has been decomposing its infrastructure into microservices, and became an early adopter of, as well as contributor to, <a href="http://kubernetes.io/">Kubernetes</a> container orchestration. Kubernetes, Ghods says, has allowed Box’s developers to "target a universal set of concepts that are portable across all clouds."<br><br>
-
-    <h2>Impact</h2>
-      "Before Kubernetes," Ghods says, "our infrastructure was so antiquated it was taking us more than six months to deploy a new microservice. Today, a new microservice takes less than five days to deploy. And we’re working on getting it to an hour."
-  </div>
-</div>
-
-</section>
-
-
-<div class="banner2">
-  <div class="banner2text">
-      "We looked at a lot of different options, but Kubernetes really stood out....the fact that on day one it was designed to run on bare metal just as well as Google Cloud meant that we could actually migrate to it inside of our data centers, and then use those same tools and concepts to run across public cloud providers as&nbsp;well."<br><br><span style="font-size:15px;letter-spacing:0.08em">- SAM GHOUDS, CO-FOUNDER AND SERVICES ARCHITECT OF BOX</span>
-  </div>
-</div>
-
-
-<section class="section2">
-
-  <div class="fullcol">
-      <h2>In the summer of 2014, Box was feeling the pain of a decade’s worth of hardware and software infrastructure that wasn’t keeping up with the company’s needs.</h2>
-
-      A platform that allows its more than 50 million users (including governments and big businesses like <a href="https://www.ge.com/">General Electric</a>) to manage and share content in the cloud, Box was originally a <a href="http://php.net/">PHP</a> monolith of millions of lines of code built exclusively with bare metal inside of its own data centers. It had already begun to slowly chip away at the monolith, decomposing it into microservices. And "as we’ve been expanding into regions around the globe, and as the public cloud wars have been heating up, we’ve been focusing a lot more on figuring out how we run our workload across many different environments and many different cloud infrastructure providers," says Box Cofounder and Services Architect Sam Ghods. "It’s been a huge challenge thus far because all these different providers, especially bare metal, have very different interfaces and ways in which you work with them."<br><br>
-      Box’s cloud native journey accelerated that June, when Ghods attended <a href="https://www.docker.com/events/dockercon">DockerCon</a>. The company had come to the realization that it could no longer run its applications only off bare metal, and was researching containerizing with Docker, virtualizing with OpenStack, and supporting public cloud.<br><br>
-      At that conference, Google announced the release of its Kubernetes container management system, and Ghods was won over. "We looked at a lot of different options, but Kubernetes really stood out, especially because of the incredibly strong team of <a href="https://research.google.com/pubs/pub43438.html">Borg</a> veterans and the vision of having a completely infrastructure-agnostic way of being able to run cloud software," he says, referencing Google’s internal container orchestrator Borg. "The fact that on day one it was designed to run on bare metal just as well as <a href="https://cloud.google.com/">Google Cloud</a> meant that we could actually migrate to it inside of our data centers, and then use those same tools and concepts to run across public cloud providers as well."<br><br>
-      Another plus: Ghods liked that <a href="kubernetes.io">Kubernetes</a> has a universal set of API objects like pod, service, replica set and deployment object, which created a consistent surface to build tooling against. "Even PaaS layers like <a href="https://www.openshift.com/">OpenShift</a> or <a href="http://deis.io/">Deis</a> that build on top of Kubernetes still treat those objects as first-class principles," he says. "We were excited about having these abstractions shared across the entire ecosystem, which would result in a lot more momentum than we saw in other potential solutions."<br><br>
-      Box deployed Kubernetes in a cluster in a production data center just six months later. Kubernetes was then still pre-beta, on version 0.11. They started small: The very first thing Ghods’s team ran on Kubernetes was a Box API checker that confirms Box is up. "That was just to write and deploy some software to get the whole pipeline functioning," he says. Next came some daemons that process jobs, which was "nice and safe because if they experienced any interruptions, we wouldn’t fail synchronous incoming requests from customers."
-
-  </div>
-</section>
-
-<div class="banner3">
-  <div class="banner3text">
-    "As we’ve been expanding into regions around the globe, and as the public cloud wars have been heating up, we’ve been focusing a lot more on figuring out how we [can have Kubernetes help] run our workload across many different environments and many different cloud infrastructure providers."
-  </div>
-</div>
-
-<section class="section3">
-  <div class="fullcol">
-    The first live service, which the team could route to and ask for information, was launched a few months later. At that point, Ghods says, "We were comfortable with the stability of the Kubernetes cluster. We started to port some services over, then we would increase the cluster size and port a few more, and that’s ended up to about 100 servers in each data center that are dedicated purely to Kubernetes. And that’s going to be expanding a lot over the next 12 months, probably to many hundreds if not thousands."<br><br>
-    While observing teams who began to use Kubernetes for their microservices, "we immediately saw an uptick in the number of microservices being released," Ghods&nbsp;notes. "There was clearly a pent-up demand for a better way of building software through microservices, and the increase in agility helped our developers be more productive and make better architectural choices."
-    <br><br><div class="quote">"There was clearly a pent-up demand for a better way of building software through microservices, and the increase in agility helped our developers be more productive and make better architectural choices."</div><br>
-    Ghods reflects that as early adopters, Box had a different journey from what companies experience now. "We were definitely lock step with waiting for certain things to stabilize or features to get released," he says. "In the early days we were doing a lot of contributions [to components such as kubectl apply] and waiting for Kubernetes to release each of them, and then we’d upgrade, contribute more, and go back and forth several times. The entire project took about 18 months from our first real deployment on Kubernetes to having general availability. If we did that exact same thing today, it would probably be no more than six."<br><br>
-    In any case, Box didn’t have to make too many modifications to Kubernetes for it to work for the company. "The vast majority of the work our team has done to implement Kubernetes at Box has been making it work inside of our existing (and often legacy) infrastructure," says Ghods, "such as upgrading our base operating system from RHEL6 to RHEL7 or integrating it into <a href="https://www.nagios.org/">Nagios</a>, our monitoring infrastructure. But overall Kubernetes has been remarkably flexible with fitting into many of our constraints, and we’ve been running it very successfully on our bare metal infrastructure."<br><br>
-    Perhaps the bigger challenge for Box was a cultural one. "Kubernetes, and cloud native in general, represents a pretty big paradigm shift, and it’s not very incremental," Ghods says. "We’re essentially making this pitch that Kubernetes is going to solve everything because it does things the right way and everything is just suddenly better. But it’s important to keep in mind that it’s not nearly as proven as many other solutions out there. You can’t say how long this or that company took to do it because there just aren’t that many yet. Our team had to really fight for resources because our project was a bit of a moonshot."
-  </div>
-</section>
-
-  <div class="banner4">
-    <div class="banner4text">
-    "The vast majority of the work our team has done to implement Kubernetes at Box has been making it work inside of our existing [and often legacy] infrastructure....overall Kubernetes has been remarkably flexible with fitting into many of our constraints, and we’ve been running it very successfully on our bare metal infrastructure."
-    </div>
-  </div>
-
-<section class="section4">
-  <div class="fullcol">
-    Having learned from experience, Ghods offers these two pieces of advice for companies going through similar challenges:
-    <h2>1. Deliver early and often.</h2> Service discovery was a huge problem for Box, and the team had to decide whether to build an interim solution or wait for Kubernetes to natively satisfy Box’s unique requirements. After much debate, "we just started focusing on delivering something that works, and then dealing with potentially migrating to a more native solution later," Ghods says. "The above-all-else target for the team should always be to serve real production use cases on the infrastructure, no matter how trivial. This helps keep the momentum going both for the team itself and for the organizational perception of the project." </br></br>
-    <h2>2. Keep an open mind about what your company has to abstract away from developers and what it&nbsp;doesn’t.</h2> Early on, the team built an abstraction on top of Docker files to help ensure that images had the right security updates.
-    This turned out to be superfluous work, since container images are considered immutable and you can easily scan them post-build to ensure they do not contain vulnerabilities. Because managing infrastructure through containerization is such a discontinuous leap, it’s better to start by interacting directly with the native tools and learning their unique advantages and caveats. An abstraction should be built only after a practical need for it arises.</br></br>
-    In the end, the impact has been powerful. "Before Kubernetes," Ghods says, "our infrastructure was so antiquated it was taking us more than six months to deploy a new microservice. Now a new microservice takes less than five days to deploy. And we’re working on getting it to an hour. Granted, much of that six months was due to how broken our systems were, but bare metal is intrinsically a difficult platform to support unless you have a system like Kubernetes to help manage&nbsp;it."</br></br>
-    By Ghods’s estimate, Box is still several years away from his goal of being a 90-plus percent Kubernetes shop. "We’re very far along on having a mission-critical, stable Kubernetes deployment that provides a lot of value," he says. "Right now about five percent of all of our compute runs on Kubernetes, and I think in the next six months we’ll likely be between 20 to 50 percent. We’re working hard on enabling all stateless service use cases, and shift our focus to stateful services after&nbsp;that."
-  </div>
-</section>
-
-  <div class="banner5">
-    <div class="banner5text">
-    "Ghods predicts that Kubernetes has the opportunity to be the new cloud platform. '...because it’s a never-before-seen level of automation and intelligence surrounding infrastructure that is portable and agnostic to every way you can run your infrastructure.'"
-    </div>
-  </div>
-
-<section class="section5">
-  <div class="fullcol">
-    In fact, that’s what he envisions across the industry: Ghods predicts that Kubernetes has the opportunity to be the new cloud platform. Kubernetes provides an API consistent across different cloud platforms including bare metal, and "I don’t think people have seen the full potential of what’s possible when you can program against one single interface," he says. "The same way <a href="https://aws.amazon.com/">AWS</a> changed infrastructure so that you don’t have to think about servers or cabinets or networking equipment anymore, Kubernetes enables you to focus exclusively on the containers that you’re running, which is pretty exciting. That’s the vision."</br></br>
-    Ghods points to projects that are already in development or recently released for Kubernetes as a cloud platform: cluster federation, the Dashboard UI, and <a href="https://coreos.com/">CoreOS</a>’s etcd operator. "I honestly believe it’s the most exciting thing I’ve seen in cloud infrastructure," he says, "because it’s a never-before-seen level of automation and intelligence surrounding infrastructure that is portable and agnostic to every way you can run your infrastructure."</br></br>
-    Box, with its early decision to use bare metal, embarked on its Kubernetes journey out of necessity. But Ghods says that even if companies don’t have to be agnostic about cloud providers today, Kubernetes may soon become the industry standard, as more and more tooling and extensions are built around the API.</br></br>
-    "The same way it doesn’t make sense to deviate from Linux because it’s such a standard," Ghods says, "I think Kubernetes is going down the same path. It is still early days—the documentation still needs work and the user experience for writing and publishing specs to the Kubernetes clusters is still rough. When you’re on the cutting edge you can expect to bleed a little. But the bottom line is, this is where the industry is going. Three to five years from now it’s really going to be shocking if you run your infrastructure any other way."
-  </div>
-</section>
-
-</body>
-</html>

case-studies/golfnow.html

@@ -1,138 +0,0 @@
----
-title: GolfNow Case Study
-layout: none
-class: gridPage
-cid: caseStudies
----
-<!DOCTYPE html>
-<html>
-  <head>
-    <meta charset="utf-8">
-    <meta name="viewport" content="width=device-width, initial-scale=1">
-      <link href="https://fonts.googleapis.com/css?family=Roboto:300,400" rel="stylesheet">
-      <link rel="stylesheet" type="text/css" href="/css/style_golfnow.css">
-    <title>GolfNow Case Study</title>
-  </head>
-<body>
-
-  <div class="banner1">
-    <h1>CASE STUDY: <img src="/images/golfnow_logo.png" class="logo" width="20%" style="margin-bottom:-6px"><br>
-    <div class="subhead">Saving Time and Money with Cloud Native Infrastructure</div>
-  </h1>
-</div>
-
-
-<div class="details">
-    Company&nbsp;<b>GolfNow</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Location&nbsp;<b>Orlando, Florida</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Industry&nbsp;<b>Golf Industry Technology and Services Provider</b>
-</div>
-
-<hr>
-
-<section class="section1">
-  <div class="cols">
-    <div class="col1">
-
-    <h2>Challenge</h2>
-      A member of the <a href="http://www.nbcunicareers.com/our-businesses/nbc-sports-group">NBC Sports Group</a>, <a href="https://www.golfnow.com/">GolfNow</a> is the golf industry’s technology and services leader, managing 10 different products, as well as the largest e-commerce tee time marketplace in the world. As its business began expanding rapidly and globally, GolfNow’s monolithic application became problematic. "We kept growing our infrastructure vertically rather than horizontally, and the cost of doing business became problematic," says Sheriff Mohamed, GolfNow’s Director, Architecture. "We wanted the ability to more easily expand globally."
-      <br>
-  </div>
-
-  <div class="col2">
-    <h2>Solution</h2>
-      Turning to microservices and containerization, GolfNow began moving its applications and databases from third-party services to its own clusters running on <a href="https://www.docker.com/">Docker</a> and <a href="http://kubernetes.io/">Kubernetes.</a><br><br>
-
-    <h2>Impact</h2>
-      The results were immediate. While maintaining the same capacity—and beyond, during peak periods—GolfNow saw its infrastructure costs for the first application virtually cut in half.
-    </div>
-  </div>
-</section>
-
-
-<div class="banner2">
-  <div class="banner2text">
-      "With our growth we obviously needed to expand our infrastructure, and we kept growing vertically rather than horizontally. We were basically wasting money and doubling the cost of our infrastructure."<br><br><span style="font-size:15px;letter-spacing:0.08em">- SHERIFF MOHAMED, DIRECTOR, ARCHITECTURE AT GOLFNOW</span>
-  </div>
-</div>
-
-<section class="section2">
-  <div class="fullcol">
-      <h2>It’s not every day that you can say you’ve slashed an operating expense by half.</h2>
-
-      But Sheriff Mohamed and Josh Chandler did just that when they helped lead their company, <a href="https://www.golfnow.com/">GolfNow</a>, on a journey from a monolithic to a containerized, cloud native infrastructure managed by Kubernetes.
-      <br> <br>
-      A top-performing business within the NBC Sports Group, GolfNow is a technology and services company with the largest tee time marketplace in the world. GolfNow serves 5 million active golfers across 10 different products. In recent years, the business had grown so fast that the infrastructure supporting their giant monolithic application (written in C#.NET and backed by SQL Server database management system) could not keep up. "With our growth we obviously needed to expand our infrastructure, and we kept growing vertically rather than horizontally," says Sheriff, GolfNow’s Director, Architecture. "Our costs were growing exponentially. And on top of that, we had to build a Disaster Recovery (DR) environment, which then meant we’d have to copy exactly what we had in our original data center to another data center that was just the standby. We were basically wasting money and doubling the cost of our infrastructure."
-      <br> <br>
-      In moving just the first of GolfNow’s important applications—a booking engine for golf courses and B2B marketing platform—from third-party services to their own Kubernetes environment, "our bill went down drastically," says Sheriff.
-      <br> <br>
-      The path to those stellar results began in late 2014. In order to support GolfNow’s global growth, the team decided that the company needed to have multiple data centers and the ability to quickly and easily re-route traffic as needed. "From there we knew that we needed to go in a direction of breaking things apart, microservices, and containerization," says Sheriff. "At the time we were trying to get away from <a href="https://www.microsoft.com/net">C#.NET</a> and <a href="https://www.microsoft.com/en-cy/sql-server/sql-server-2016">SQL Server</a> since it didn’t run very well on Linux, where everything container was running smoothly."
-      <br> <br>
-      To that end, the team shifted to working with <a href="https://nodejs.org/">Node.js</a>, the open-source, cross-platform JavaScript runtime environment for developing tools and applications, and <a href="https://www.mongodb.com/">MongoDB</a>, the open-source database program. At the time, <ahref="https://www.docker.com/">Docker</a>, the platform for deploying applications in containers, was still new. But once the team began experimenting with it, Sheriff says, "we realized that was the way we wanted to go, especially since that’s the way the industry is heading."
-  </div>
-</section>
-
-<div class="banner3">
-  <div class="banner3text">
-    "The team migrated the rest of the application into their Kubernetes cluster. And the impact was immediate: On top of cutting monthly costs by a large percentage, says Sheriff, 'Running at the same capacity and during our peak time, we were able to horizontally grow. Since we were using our VMs more efficiently with containers, we didn’t have to pay extra money at all.'"
-  </div>
-</div>
-
-<section class="section3">
-  <div class="fullcol">
-    GolfNow’s dev team ran an "internal, low-key" proof of concept and were won over. "We really liked how easy it was to be able to pass containers around to each other and have them up and running in no time, exactly the way it was running on my machine," says Sheriff. "Because that is always the biggest gripe that Ops has with developers, right? ‘It worked on my machine!’ But then we started getting to the point of, ‘How do we make sure that these things stay up and running?’" <br><br>
-    That led the team on a quest to find the right orchestration system for the company’s needs. Sheriff says the first few options they tried were either too heavy or "didn’t feel quite right." In late summer 2015, they discovered the just-released <a href="http://kubernetes.io/">Kubernetes</a>, which Sheriff immediately liked for its ease of use. "We did another proof of concept," he says, "and Kubernetes won because of the fact that the community backing was there, built on top of what Google had already done."
-    <br><br>
-    But before they could go with Kubernetes, <a href="http://www.nbc.com/">NBC</a>, GolfNow’s parent company, also asked them to comparison shop with another company. Sheriff and his team liked the competing company’s platform user interface, but didn’t like that its platform would not allow containers to run natively on Docker. With no clear decision in sight, Sheriff’s VP at GolfNow, Steve McElwee, set up a three-month trial during which a GolfNow team (consisting of Sheriff and Josh, who’s now Lead Architect, Open Platforms) would build out a Kubernetes environment, and a large NBC team would build out one with the other company’s platform.
-    <br><br>
-    "We spun up the cluster and we tried to get everything to run the way we wanted it to run," Sheriff says. "The biggest thing that we took away from it is that not only did we want our applications to run within Kubernetes and Docker, we also wanted our databases to run there. We literally wanted our entire infrastructure to run within Kubernetes."
-    <br><br>
-    At the time there was nothing in the community to help them get Kafka and MongoDB clusters running within a Kubernetes and Docker environment, so Sheriff and Josh figured it out on their own, taking a full month to get it right. "Everything started rolling from there," Sheriff says. "We were able to get all our applications connected, and we finished our side of the proof of concept a month in advance. My VP was like, ‘Alright, it’s over. Kubernetes wins.’"
-    <br><br>
-    The next step, beginning in January 2016, was getting everything working in production. The team focused first on one application that was already written in Node.js and MongoDB. A booking engine for golf courses and B2B marketing platform, the application was already going in the microservice direction but wasn’t quite finished yet. At the time, it was running in <a href="https://devcenter.heroku.com/articles/mongohq">Heroku Compose</a> and other third-party services—resulting in a large monthly bill.
-
-  </div>
-</section>
-
-  <div class="banner4">
-    <div class="banner4text">
-    "'The time I spent actually moving the applications was under 30 seconds! We can move data centers in just incredible amounts of time. If you haven’t come from the Kubernetes world you wouldn’t believe me.' Sheriff puts it in these terms: 'Before Kubernetes I wasn’t sleeping at night, literally. I was woken up all the time, because things were down. After Kubernetes, I’ve been sleeping at night.'"
-    </div>
-  </div>
-
-<section class="section4">
-  <div class="fullcol">
-    "The goal was to take all of that out and put it within this new platform we’ve created with Kubernetes on <a href="https://cloud.google.com/compute/">Google Compute Engine (GCE)</a>," says Sheriff. "So we ended up building piece by piece, in parallel, what was out in Heroku and Compose, in our Kubernetes cluster. Then, literally, just switched configs in the background. So in Heroku we had the app running hitting a Compose database. We’d take the config, change it and make it hit the database that was running in our cluster."
-    <br><br>
-    Using this procedure, they were able to migrate piecemeal, without any downtime. The first migration was done during off hours, but to test the limits, the team migrated the second database in the middle of the day, when lots of users were running the application. "We did it," Sheriff says, "and again it was successful. Nobody noticed."
-    <br><br>
-    After three weeks of monitoring to make sure everything was running stable, the team migrated the rest of the application into their Kubernetes cluster. And the impact was immediate: On top of cutting monthly costs by a large percentage, says Sheriff, "Running at the same capacity and during our peak time, we were able to horizontally grow. Since we were using our VMs more efficiently with containers, we didn’t have to pay extra money at all."
-    <br><br>
-    Not only were they saving money, but they were also saving time. "I had a meeting this morning about migrating some applications from one cluster to another," says Josh. "I spent about 2 hours explaining the process. The time I spent actually moving the applications was under 30 seconds! We can move data centers in just incredible amounts of time. If you haven’t come from the Kubernetes world you wouldn’t believe me." Sheriff puts it in these terms: "Before Kubernetes I wasn’t sleeping at night, literally. I was woken up all the time, because things were down. After Kubernetes, I’ve been sleeping at night."
-    <br><br>
-    A small percentage of the applications on GolfNow have been migrated over to the Kubernetes environment. "Our Core Team is rewriting a lot of the .NET applications into <a href="https://www.microsoft.com/net/core">.NET Core</a> [which is compatible with Linux and Docker] so that we can run them within containers," says Sheriff.
-    <br><br>
-    Looking ahead, Sheriff and his team want to spend 2017 continuing to build a whole platform around Kubernetes with <a href="https://github.com/drone/drone">Drone</a>, an open-source continuous delivery platform, to make it more developer-centric. "Now they’re able to manage configuration, they’re able to manage their deployments and things like that, making all these subteams that are now creating all these microservices, be self sufficient," he says. "So it can pull us away from applications and allow us to just make sure the cluster is running and healthy, and then actually migrate that over to our Ops team."
-
-  </div>
-</section>
-
-  <div class="banner5">
-    <div class="banner5text">
-    "Having gone from complete newbies to production-ready in three months, the GolfNow team is eager to encourage other companies to follow their lead. 'This is The Six Million Dollar Man of the cloud right now,' adds Josh. 'Just try it out, watch it happen. I feel like the proof is in the pudding when you look at these kinds of application stacks. They’re faster, they’re more resilient.'"
-    </div>
-  </div>
-
-<section class="section5">
-  <div class="fullcol">
-    And long-term, Sheriff has an even bigger goal for getting more people into the Kubernetes fold. "We’re actually trying to make this platform generic enough so that any of our sister companies can use it if they wish," he says. "Most definitely I think it can be used as a model. I think the way we migrated into it, the way we built it out, are all ways that I think other companies can learn from, and should not be afraid of."
-    <br><br>
-    The GolfNow team is also giving back to the Kubernetes community by open-sourcing a bot framework that Josh built. "We noticed that the dashboard user interface is actually moving a lot faster than when we started," says Sheriff. "However we realized what we needed was something that’s more of a bot that really helps us administer Kubernetes as a whole through Slack." Josh explains: "With the Kubernetes-Slack integration, you can essentially hook into a cluster and the issue commands and edit configurations. We’ve tried to simplify the security configuration as much as possible. We hope this will be our major thank you to Kubernetes, for everything you’ve given us."
-    <br><br>
-    Having gone from complete newbies to production-ready in three months, the GolfNow team is eager to encourage other companies to follow their lead. The lessons they’ve learned: "You’ve got to have buy-in from your boss," says Sheriff. "Another big deal is having two to three people dedicated to this type of endeavor. You can’t have people who are half in, half out." And if you don’t have buy-in from the get go, proving it out will get you there.
-    <br><br>
-    "This is The Six Million Dollar Man of the cloud right now," adds Josh. "Just try it out, watch it happen. I feel like the proof is in the pudding when you look at these kinds of application stacks. They’re faster, they’re more resilient."
-
-  </div>
-</section>
-
-</body>
-</html>

case-studies/index.html

@@ -1,105 +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/golfnow.png" alt="GolfNow">
-                  <p class="quote">"We can move data centers in incredible amounts of time. If you haven’t come from the Kubernetes world and I tell you this is what I’ve been doing, you wouldn’t believe me."</p>
-                  <!--<p class="attrib">— Josh Chandler, Lead Architect, Open Platforms at GolfNow</p>-->
-                  <a href="/case-studies/golfnow/">Read about GolfNow</a>
-              </div>
-                <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="/case-studies/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="/case-studies/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 has the opportunity to be the new cloud platform. Because it’s a never-before-seen level of automation and intelligence surrounding infrastructure that is portable and agnostic to every way you can run your infrastructure."</p>
-                    <a href="/case-studies/box/">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="/case-studies/wikimedia/"><img src="/images/case_studies/wikimedia_logo.png" alt="Wikimedia"></a>
-            <a href="/case-studies/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,118 +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 控制面 (Controll Plane)](/docs/admin/cluster-components) 是构建在相同的 [APIs](/docs/api/) 上面，开发人员和用户都可以用。用户可以编写自己的控制器， [调度器](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/docs/devel/scheduler.md)等等，如果这么做，根据新加的[自定义 API](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/design/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 的发音比较接近。

cn/docs/tutorials/kubernetes-basics/cluster-intro.html

@@ -1,110 +0,0 @@
----
-redirect_from:
-- "/docs/tutorials/getting-started/create-cluster/"
-- "/docs/tutorials/getting-started/create-cluster.html"
-title: 使用 Minikube 创建一个集群
----
-
-<!DOCTYPE html>
-
-<html lang="en">
-
-<body>
-
-<link href="/docs/tutorials/kubernetes-basics/public/css/styles.css" rel="stylesheet">
-
-<div class="layout" id="top">
-
-	<main class="content">
-
-		<div class="row">
-
-      <div class="col-md-8">
-      	<h3>目标</h3>
-				<ul>
-					<li>了解什么是 Kubernetes 集群</li>
-					<li>了解什么是 Minikube</li>
-					<li>使用在线终端启动 Kubernetes 集群</li>
-				</ul>
-			</div>
-
-			<div class="col-md-8">
-				<h3>Kubernetes 集群</h3>
-				<p>
-				<b>Kubernetes 用于协调高度可用的计算机集群，这些计算机群集被连接作为单个单元工作。</b> Kubernetes 的抽象性允许您将容器化的应用程序部署到集群，而不必专门将其绑定到单个计算机。为了利用这种新的部署模型，应用程序需要以将它们与各个主机分离的方式打包: 它们需要被容器化。容器化应用程序比过去的部署模型更灵活和可用，其中应用程序直接安装到特定机器上，作为深入集成到主机中的软件包。 <b>Kubernetes 在一个集群上以更有效的方式自动分发和调度容器应用程序。</b> Kubernetes 是一个 <a href="https://github.com/kubernetes/kubernetes">开源</a> 平台，可满足生产环境的需要。
-				</p>
-				<p>Kubernetes 集群由两种类型的资源组成:
-					<ul>
-			            <li>一个 <b>Master</b> 是集群的调度节点</li>
-			            <li><b>Nodes</b> 是应用程序实际运行的工作节点</li>
-			        </ul>
-			    </p>
-			</div>
-
-			<div class="col-md-4">
-				<div class="content__box content__box_lined">
-					<h3>概要:</h3>
-					<ul>
-						<li>Kubernetes 集群</li>
-						<li>Minikube</li>
-					</ul>
-				</div>
-				<div class="content__box content__box_fill">
-					<p><i>
-						Kubernetes 是一个生产级的开源平台，用于协调计算机集群内部和跨计算机集群的应用程序容器的分发(调度)和运行。
-					</i></p>
-				</div>
-			</div>
-		</div>
-		<br>
-
-		<div class="row">
-			<div class="col-md-8">
-				<h2 style="color: #3771e3;">集群图</h2>
-			</div>
-		</div>
-
-		<div class="row">
-			<div class="col-md-8">
-				<p><img src="/docs/tutorials/kubernetes-basics/public/images/module_01_cluster.svg"></p>
-			</div>
-		</div>
-		<br>
-
-		<div class="row">
-			<div class="col-md-8">
-				<p><b>Master 负责管理集群。</b> master 协调集群中的所有活动，例如调度应用程序、维护应用程序的所需状态、扩展应用程序和滚动更新。</p>
-				<p><b>节点 是 Kubernetes 集群中的工作机器，可以是物理机或虚拟机。</b> 每个工作节点都有一个 Kubelet，它是管理 节点 并与 Kubernetes Master 节点进行通信的代理。节点 上还应具有处理容器操作的工作，例如 <a href="https://www.docker.com/">Docker</a> 或 <a href="https://coreos.com/rkt/">rkt</a>。一个 Kubernetes 工作集群至少有三个节点。</p>
-
-			</div>
-			<div class="col-md-4">
-				<div class="content__box content__box_fill">
-					<p><i> Master 管理集群，而 节点 用于托管正在运行的应用程序。  </i></p>
-				</div>
-			</div>
-		</div>
-
-		<div class="row">
-			<div class="col-md-8">
-				<p>当您在 Kubernetes 上部署应用程序时，您可以告诉 master 启动应用程序容器。Master 调度容器在集群的 节点 上运行。<b> 节点 使用 Master 公开的 Kubernetes API 与 Master 通信</b>。最终用户还可以直接使用 Kubernetes 的 API 与集群交互。</p>
-
-				<p>Kubernetes 集群可以部署在物理机或虚拟机上。要开始使用 Kubernetes 开发，您可以使用 <a href="https://github.com/kubernetes/minikube">Minikube</a>。Minikube 是一个轻量级的 Kubernetes 实现，会在本机创建一台虚拟机，并部署一个只包含一个节点的简单集群。 Minikube 适用于 Linux, Mac OS 和 Windows 系统。Minikube CLI 提供了集群的基本引导操作，包括启动、停止、状态和删除。为了完成此基础训练，您将使用预先安装了 Minikube 的在线终端。</p>
-
-				<p>现在您已经知道 Kubernetes 是什么，让我们使用在线教程，开始我们的第一个集群!</p>
-
-			</div>
-		</div>
-		<br>
-
-		<div class="row">
-			<div class="col-md-12">
-				<a class="btn btn-lg btn-success" href="/docs/tutorials/kubernetes-basics/cluster-interactive/" role="button">启动互动教程 <span class="btn__next">›</span></a>
-			</div>
-		</div>
-
-	</main>
-
-</div>
-
-</body>
-</html>

cn/docs/tutorials/kubernetes-basics/expose-intro.html

@@ -1,111 +0,0 @@
----
-title: 使用服务发布您的应用程序
----
-
-<!DOCTYPE html>
-
-<html lang="en">
-
-<body>
-
-<link href="/docs/tutorials/kubernetes-basics/public/css/styles.css" rel="stylesheet">
-
-<div class="layout" id="top">
-
-	<main class="content">
-
-		<div class="row">
-			<div class="col-md-8">
-    		<h3>目标</h3>
-				<ul>
-					<li>了解 Kubernetes 中的服务</li>
-					<li>了解标签和标签选择器对象如何与服务相关联</li>
-					<li>通过 Service 在 Kubernetes 集群外发布应用程序</li>
-				</ul>
-			</div>
-
-			<div class="col-md-8">
-			<h3>Kubernetes 服务概述</h3>
-
-			<p>Kubernetes <a href="/docs/concepts/workloads/pods/pod-overview/">Pods</a> 终有一死. Pods 实际上有一个 <a href="/docs/concepts/workloads/pods/pod-lifecycle/">生命周期</a>. 当工作节点死机时, 节点上运行的Pod也将丢失。 一个 <a href="/docs/user-guide/replication-controller/#what-is-a-replicationcontroller">ReplicationController</a> 可能会通过创建新的Pod以动态地将集群恢复到所需的状态，以保持您的应用程序运行。还有一种方法就是：决定是否使用具有3个副本的图像处理后端。这些副本是可替代的前端系统不应关心后端副本，即使Pod丢失并重建也不会更改。 也就是说，Kubernetes 集群中的每个 Pod 都有一个唯一的IP地址，即使在同一个节点上的 Pods 也是如此，所以此时就需要一种自动调整更改 Pod 的方法, 以便您的应用程序继续运行。输入 <i>服务</i>. Kubernetes 中的服务是一个抽象对象，它定义了一组逻辑的 Pods 和一个访问它们的策略。 服务让互相依赖的 Pod 之间的耦合松动。 服务由 YAML <a href="/docs/concepts/configuration/overview/#general-config-tips">(首选)</a> 或 JSON 定义。像所有 Kubernetes 对象一样。 针对服务的一组 Pod 通常由<i>Label选择器</i>确定（参见下文，为什么您可能希望不将 <code>选择器</code> 包含在规范中。</p>
-
-			<p>虽然每个 Pod 都有一个唯一的 IP 地址，但是这些 IP 不会在没有服务的情况下公开在群集之外。服务允许您的应用程序接收流量。 可以通过在 ServiceSpec 中指定<code>类型</code> 以不同方式显示服务：</p>
-			<ul>
-				<li><i>ClusterIP</i>(默认) - 在集群中的内部IP上公开服务。此类型使服务只能从集群中访问。</li>
-				<li><i>NodePort</i> —— 使用NAT在群集中每个选定的节点的同一端口上显示该服务。使用 <code><NodeIP>:<NodePort></code>可以从群集外部访问服务。建立 ClusterIP 的超集.</li>
-				<li><i>LoadBalancer</i> —— 在当前云中创建外部负载平衡器(如果支持)，并为服务分配固定的外部IP。建立 NodePort 的超集。</li>
-				<li><i>ExternalName</i> —— 使用任意名称显示该服务(由规范中的<code>externalName</code> 指定)，本过程通过使用该名称返回 CNAME 记录达成。无须使用代理。这种类型需要 v1.7 或更高版本的 <code>kube-dns</code>.</li>
-			</ul>
-			<p>有关不同类型服务的详细信息，请参见 <a href="/docs/tutorials/services/source-ip/">使用源IP</a> 教程。另请参阅 <a href="/docs/concepts/services-networking/connect-applications-service">使用服务连接应用程序</a>.</p>
-			<p>另外，请注意，服务中有一些使用案例涉及在规范中不定义<code>选择器</code> 。不使用 <code>选择器</code> 创建的服务也不会创建相应的端点对象。 这允许用户手动将服务映射到特定端点。没有选择器还有可能是因为您严格地使用了 <code>type: ExternalName</code>.</p>
-			</div>
-			<div class="col-md-4">
-				<div class="content__box content__box_lined">
-					<h3>摘要</h3>
-					<ul>
-						<li>对外部流量曝光 Pod </li>
-						<li>跨多个 Pods 进行流量负载均衡</li>
-						<li>使用标签</li>
-					</ul>
-				</div>
-				<div class="content__box content__box_fill">
-						<p><i>Kubernetes 服务是一个抽象层，它定义了一组逻辑的Pods，并为这些Pods启用了外部流量曝光、负载平衡和服务发现。</i></p>
-				</div>
-			</div>
-		</div>
-		<br>
-
-		<div class="row">
-			<div class="col-md-8">
-				<h3>服务和标签</h3>
-			</div>
-		</div>
-
-		<div class="row">
-			<div class="col-md-8">
-				<p><img src="/docs/tutorials/kubernetes-basics/public/images/module_04_services.svg" width="150%" height="150%"></p>
-			</div>
-		</div>
-
-		<div class="row">
-			<div class="col-md-8">
-				<p> A服务可以跨一组 Pod 路由流量。服务是允许 Pod 在 Kubernetes 中死亡和复制而不影响应用程序的抽象层。相关 Pod 之间的发现和路由(如应用程序中的前端和后端组件)是由 Kubernetes Services 处理的。</p>
-				<p> 服务使用 <a href="/docs/concepts/overview/working-with-objects/labels">标签和选择器</a>, 匹配一组 Pod，成为分组原语，此原语允许在 Kubernetes 中的对象进行逻辑运算。标签是一对附加到对象的关键/重要组，可以以多种方式使用，方式如下: </p>
-				<ul>
-					<li>指定用于开发、测试和生产的对象</li>
-					<li>嵌入版本标签</li>
-					<li>使用标签分类对象</li>
-				</ul>
-
-			</div>
-			<div class="col-md-4">
-				<div class="content__box content__box_fill">
-					<p><i>您可以在使用<br><code>--expose</code> 在 kubectl 中创建部署的同时创建服务.</i></p>
-				</div>
-			</div>
-		</div>
-
-		<br>
-
-		<div class="row">
-			<div class="col-md-8">
-				<p><img src="/docs/tutorials/kubernetes-basics/public/images/module_04_labels.svg"></p>
-			</div>
-		</div>
-		<br>
-		<div class="row">
-			<div class="col-md-8">
-				<p>标签可以在创建时或之后附加到对象后，并支持随时修改。让我们现在开始使用服务公开我们的应用程序并应用一些标签吧。</p>
-			</div>
-		</div>
-		<br>
-		<div class="row">
-			<div class="col-md-12">
-				<a class="btn btn-lg btn-success" href="/docs/tutorials/kubernetes-basics/expose-interactive/" role="button">启动互动教程<span class="btn__next">›</span></a>
-			</div>
-		</div>
-	</main>
-</div>
-
-</body>
-</html>

cn/docs/tutorials/kubernetes-basics/index.html

@@ -1,106 +0,0 @@
----
-title: 概述
----
-
-<!DOCTYPE html>
-
-<html lang="en">
-
-<body>
-
-<link href="./public/css/styles.css" rel="stylesheet">
-
-<div class="layout" id="top">
-
-  <main class="content">
-
-    <div class="row">
-      <div class="col-md-9">
-        <h2>Kubernetes 基础</h2>
-        <p>本教程介绍了 Kubernetes 集群编排系统的基础知识。每个模块包含关于 Kubernetes 主要特性和概念的一些背景信息，并包括一个在线互动教程。这些互动教程让您可以自己管理一个简单的集群及其容器化应用程序。</p>
-        <p>使用互动教程，您可以学习:</p>
-        <ul>
-        <li>在集群上部署容器化应用程序</li>
-        <li>弹性部署</li>
-        <li>使用新的软件版本，更新容器化应用程序</li>
-        <li>调试容器化应用程序</li>
-        </ul>
-        <p>教程 Katacoda 在您的浏览器中运行一个虚拟终端，在浏览器中运行 Minikube，这是一个可在任何地方小规模本地部署的 Kubernetes 集群。不需要安装任何软件或进行任何配置; 每个交互性教程都直接从您的网页浏览器上运行。</p>
-      </div>
-    </div>
-
-    <br>
-
-    <div class="row">
-      <div class="col-md-9">
-        <h2>Kubernetes 可以为您做些什么?</h2>
-        <p>通过现代的 Web 服务，用户希望应用程序能够 24/7 全天候使用，开发人员希望每天可以多次发布部署新版本的应用程序。 容器化可以帮助软件包达成这些目标，使应用程序能够以简单快速的方式发布和更新，而无需停机。Kubernetes 帮助您确保这些容器化的应用程序在您想要的时间和地点运行，并帮助应用程序找到它们需要的资源和工具。 <a href="http://kubernetes.io/docs/whatisk8s/">Kubernetes</a>  是一个可用于生产的开源平台，根据 Google 容器集群方面积累的经验，以及来自社区的最佳实践而设计。</p>
-      </div>
-    </div>
-
-    <div class="content__modules">
-      <h2>Kubernetes 基础模块</h2>
-      <div class="row">
-        <div class="col-md-4">
-          <div class="thumbnail">
-            <a href="/docs/tutorials/kubernetes-basics/cluster-intro/"><img src="./public/images/module_01.svg?v=1469803628347" alt=""></a>
-            <div class="caption">
-              <a href="cluster-intro/"><h5>1. 创建一个 Kubernetes 集群</h5></a>
-            </div>
-          </div>
-        </div>
-        <div class="col-md-4">
-          <div class="thumbnail">
-            <a href="/docs/tutorials/kubernetes-basics/deploy-intro/"><img src="./public/images/module_02.svg?v=1469803628347" alt=""></a>
-            <div class="caption">
-              <a href="deploy-intro/"><h5>2. 部署应用程序</h5></a>
-            </div>
-          </div>
-        </div>
-        <div class="col-md-4">
-          <div class="thumbnail">
-            <a href="/docs/tutorials/kubernetes-basics/explore-intro/"><img src="./public/images/module_03.svg?v=1469803628347" alt=""></a>
-            <div class="caption">
-              <a href="explore-intro/"><h5>3. 应用程序探索</h5></a>
-            </div>
-          </div>
-        </div>
-        <div class="col-md-4">
-          <div class="thumbnail">
-            <a href="/docs/tutorials/kubernetes-basics/expose-intro/"><img src="./public/images/module_04.svg?v=1469803628347" alt=""></a>
-            <div class="caption">
-              <a href="expose-intro/"><h5>4. 应用外部可见</h5></a>
-            </div>
-          </div>
-        </div>
-        <div class="col-md-4">
-          <div class="thumbnail">
-            <a href="/docs/tutorials/kubernetes-basics/scale-intro/"><img src="./public/images/module_05.svg?v=1469803628347" alt=""></a>
-            <div class="caption">
-              <a href="scale-intro/"><h5>5. 应用可扩展</h5></a>
-            </div>
-          </div>
-        </div>
-        <div class="col-md-4">
-          <div class="thumbnail">
-            <a href="/docs/tutorials/kubernetes-basics/update-intro/"><img src="./public/images/module_06.svg?v=1469803628347" alt=""></a>
-            <div class="caption">
-              <a href="update-intro/"><h5>6. 应用更新</h5></a>
-            </div>
-          </div>
-        </div>
-      </div>
-    </div>
-
-    <div class="row">
-      <div class="col-md-12">
-        <a class="btn btn-lg btn-success" href="/docs/tutorials/kubernetes-basics/cluster-intro/" role="button">开始教程<span class="btn__next">›</span></a>
-      </div>
-    </div>
-
-  </main>
-
-</div>
-
-</body>
-</html>

cn/docs/tutorials/kubernetes-basics/scale-intro.html

@@ -1,121 +0,0 @@
----
-title: 运行应用程序的多个实例
----
-
-<!DOCTYPE html>
-
-<html lang="en">
-
-<body>
-
-<link href="/docs/tutorials/kubernetes-basics/public/css/styles.css" rel="stylesheet">
-
-<div class="layout" id="top">
-
-	<main class="content">
-
-		<div class="row">
-
-     <div class="col-md-8">
-      	<h3>目标</h3>
-				<ul>
-					<li>使用 kubectl 伸缩应用程序</li>
-				</ul>
-			</div>
-
-			<div class="col-md-8">
-       <h3>应用程序伸缩</h3>
-
-			<p>在之前的模块中，我们创建了一个 <a href="http://kubernetes.io/docs/user-guide/deployments/"> Deployment</a>，然后通过 <a href="http://kubernetes.io/docs/user-guide/services/">Service</a>让应用程序外部可见。Deployment 仅为我们的应用程序创建了一个 Pod。 当流量增加时，我们将需要
-				应用程序以跟上用户需求。</p>
-
-			<p><b>Scaling</b> 是通过更改 Deployment 中的副本数量实现的。</p>
-
-			</div>
-			<div class="col-md-4">
-				<div class="content__box content__box_lined">
-					<h3>摘要:</h3>
-					<ul>
-						<li>Deployment 的伸缩</li>
-					</ul>
-				</div>
-				<div class="content__box content__box_fill">
-					<p><i> 您可以使用 kubectl run 命令的 --replicas 参数，在创建 Deployment 时指定多个实例。 </i></p>
-				</div>
-			</div>
-		</div>
-		<br>
-
-		<div class="row">
-			<div class="col-md-8">
-				<h2 style="color: #3771e3;">Scaling 概述</h2>
-			</div>
-		</div>
-
-		<div class="row">
-			<div class="col-md-1"></div>
-			<div class="col-md-8">
-				<div id="myCarousel" class="carousel" data-ride="carousel" data-interval="3000">
-					<ol class="carousel-indicators">
-					    <li data-target="#myCarousel" data-slide-to="0" class="active"></li>
-					    <li data-target="#myCarousel" data-slide-to="1"></li>
-					</ol>
-					  <div class="carousel-inner" role="listbox">
-					    <div class="item active">
-					      <img src="/docs/tutorials/kubernetes-basics/public/images/module_05_scaling1.svg">
-					    </div>
-
-					    <div class="item">
-					      <img src="/docs/tutorials/kubernetes-basics/public/images/module_05_scaling2.svg">
-					    </div>
-					  </div>
-
-					  <a class="left carousel-control" href="#myCarousel" role="button" data-slide="prev">
-						<span class="sr-only ">Previous</span>
-					  </a>
-					  <a class="right carousel-control" href="#myCarousel" role="button" data-slide="next">
-						<span class="sr-only">Next</span>
-					  </a>
-
-					</div>
-			</div>
-		</div>
-
-		<br>
-
-		<div class="row">
-			<div class="col-md-8">
-
-				<p>扩展 Deployment 将确保新创建的 Pods 会调度到可用资源的 Node 节点上，收缩会保证 Pods 数量减少至新的所需状态。  Kubernetes 还支持 Pods 的 <a href="http://kubernetes.io/docs/user-guide/horizontal-pod-autoscaling/"> 自动缩放版 </a> ，但不在本教程范围之内。收缩到零也是可以的，此时它将终止指定 Deployment 的所有 Pod。 </p>
-
-				<p>运行应用程序的多个实例需要一种将流量分发给所有实例的方法。服务有内置的负载均衡器，可将网络流量分配给 Deployment 暴露的所有 Pods。服务通过使用 endpoints 持续监控运行的 Pods，以确保流量仅发送到可用的 Pods。</p>
-
-			</div>
-			<div class="col-md-4">
-				<div class="content__box content__box_fill">
-					<p><i>通过更改 Deployment 中的副本数可以实现伸缩应用程序。</i></p>
-				</div>
-			</div>
-		</div>
-
-		<br>
-
-		<div class="row">
-			<div class="col-md-8">
-				<p> 一旦您有应用程序的多个实例，您将能够滚动更新，而不会停止服务————我们将在下一个模块中介绍这些。现在，我们去在线终端对我们的应用程序进行伸缩。</p>
-			</div>
-		</div>
-		<br>
-
-		<div class="row">
-			<div class="col-md-12">
-				<a class="btn btn-lg btn-success" href="/docs/tutorials/kubernetes-basics/scale-interactive/" role="button">启动互动教程 <span class="btn__next">›</span></a>
-			</div>
-		</div>
-
-	</main>
-
-</div>
-
-</body>
-</html>

cn/docs/tutorials/object-management-kubectl/imperative-object-management-command.md

@@ -1,145 +0,0 @@
----
-title: 使用命令式的方式管理 Kubernetes 对象
-redirect_from:
-- "/docs/concepts/tools/kubectl/object-management-using-imperative-commands/"
-- "/docs/concepts/tools/kubectl/object-management-using-imperative-commands.html"
----
-
-{% capture overview %}
-直接使用内置的 `kubectl` 命令行工具，以命令式方式可以快速创建，更新和删除 Kubernetes 对象。本文档介绍了这些命令是如何组织的，以及如何使用它们来管理活动对象。
-{% endcapture %}
-
-{% capture body %}
-
-## 权衡
-
-`kubectl` 工具支持三种对象的管理:
-
-* 命令式的方式
-* 命令式的对象配置
-* 声明式的对象配置
-
-参见[Kubernetes对象管理](/docs/concepts/tools/kubectl/object-management-overview/)
-讨论各种对象管理的优缺点.
-
-## 如何创建对象
-
-`kubectl` 工具支持用于创建一些最常用的对象类型的动词驱动命令，这些命令被命名为对于不熟悉的用户也是一目了然。
-
-- `run`: 创建一个新的 Deployment 对象以在一个或多个 Pod 中运行 Containers。
-- `expose`: 创建一个新的 Service 对象用于负载均衡 Pods 上的的网络流量。
-- `autoscale`: 创建一个新的 Autoscaler 对象，即自动水平扩展控制器，提供 Deployment 自动水平伸缩支持。
-
-`kubectl` 工具也支持由对象类型驱动的创建命令。 这些命令支持更多的对象类型，并且对其意图更为明确，但要求用户知道他们打算创建的对象的类型。
-
- - `create <objecttype> [<subtype>] <instancename>`
-
-某些对象类型具有您可以在“create"命令中指定的子类型.
-例如，Service对象有几种子类型，包括ClusterIP，
-LoadBalancer和NodePort. 以下是创建一个服务的示例
-子类型NodePort:
-
-一些对象类型允许你在 `create` 命令中指定子命令。例如，Service 对象拥有几个子命令，包括 ClusterIP、LoadBalancer 和 NodePort。以下是使用子命令 NodePort 创建服务的示例:
-
-
-```shell
-kubectl create service nodeport <myservicename>
-```
-
-在前面的例子中，调用 `create service nodeport`命令是 `create service`命令的子命令.
-
-您可以使用 `-h` 标志来查找子命令支持的参数和标志:
-
-```shell
-kubectl create service nodeport -h
-```
-
-## 如何更新对象
-
-`kubectl` 命令支持一些常见更新操作的动词驱动命令。这样命名可以让不熟悉 Kubernetes 对象的用户，在不知道必须设置的特定字段的情况下也可以执行更新操作:
-
- - `scale`: 通过更新控制器的副本数量，水平扩展控制器以添加或删除 Pod。
- - `annotate`: 从对象添加或删除注释。
- - `label`: 为对象添加或删除标签。
-
-`kubectl`命令还支持由对象的一个​​切面驱动的更新命令.设置此切面可能会为不同的对象类型设置不同的字段:
-
- - `set` <field>: 设置对象的一个​​切面.
-
-**注**: 在 Kubernetes 版本 1.5 中，并不是每个动词驱动的命令都有一个相关的切面驱动的命令.
-
-`kubectl` 工具支持直接更新活动对象的其他方法，然而，它们需要更好的了解 Kubernetes 对象模式。
-
-- `edit`: 通过在编辑器中打开其配置，直接编辑活动对象的原始配置。
-- `patch`: 通过使用补丁字符串直接修改活动对象的特定字段。
-
-有关补丁字符串的更多详细信息，请参阅补丁部分
-[API 公约](https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md#patch-operations).
-
-## 如何删除对象
-
-您可以使用 `delete` 命令从集群中删除一个对象:
-
- - `delete <type>/<name>`
-
- **注意**: 您可以对命令式命令和命令式对象配置都使用 `kubectl delete` 方法。两者的差异在于传递的命令参数不同。要将
- `kubectl delete` 作为命令式命令使用，将要删除的对象作为参数传递。以下是传递名为 nginx 的 Deployment 对象的示例:
-
-```shell
-kubectl delete deployment/nginx
-```
-
-## 如何查看对象
-
-{% comment %}
-TODO(pwittrock): 实现时取消注释.
-
-您可以使用 `kubectl view` 打印指定对象的字段。
-
-- `view`: 打印对象的特定字段的值。
-
-{% endcomment %}
-
-
-
-有几个命令用于打印有关对象的信息:
-
-- `get`: 打印有关匹配对象的基本信息。使用 `get -h` 来查看选项列表。
-- `describe`: 打印有关匹配对象的聚合详细信息。
-- `logs`: 打印 Pod 运行容器的 stdout 和 stderr 信息。
-
-##  使用 `set` 命令在创建之前修改对象
-
-有一些对象字段没有可以使用的标志，在 `create` 命令中。在某些情况下，您可以使用组合 `set` 和 `create` 为对象之前的字段指定一个值创建。这是通过将 `create` 命令的输出管道连接到 `set` 命令，然后回到 `create` 命令。以下是一个例子:
-
-```sh
-kubectl create service clusterip <myservicename> -o yaml --dry-run | kubectl set selector --local -f - 'environment=qa' -o yaml | kubectl create -f -
-```
-
-1.  使用 `create service -o yaml --dry-run` 创建服务配置，并将其作为 YAML 打印到 stdout，而不是将其发送到 Kubernetes API 服务器。
-1.  使用 `set --local -f - -o yaml` 从 stdin 读取配置，并将更新后的配置作为 YAML 写入 stdout。
-1.  使用 `kubectl create -f -` 从 stdin 提供的配置创建对象。
-
-## 使用 `--edit` 在创建之前修改对象
-
-您可以使用 `kubectl create --edit` 命令在对象创建之前，对对象进行任意更改。以下是一个例子:
-
-```sh
-kubectl create service clusterip my-svc -o yaml --dry-run > /tmp/srv.yaml
-kubectl create --edit -f /tmp/srv.yaml
-```
-
-1. 使用`create service` 创建服务的配置并将其保存到 `/tmp/srv.yaml`。
-1. 使用`create --edit` 在创建对象之前打开配置文件进行编辑。
-
-
-{% endcapture %}
-
-{% capture whatsnext %}
- -  [使用对象配置管理 Kubernetes 对象(必要)](/docs/tutorials/object-management-kubectl/imperative-object-management-configuration/)
- -  [使用对象配置(声明式)管理 Kubernetes 对象](/docs/tutorials/object-management-kubectl/declarative-object-management-configuration/)
- -  [Kubectl 命令参考](/docs/user-guide/kubectl/v1.6/)
- -  [Kubernetes 对象模式参考](/docs/resources-reference/v1.6/)
- {% endcapture %}
-
- {% include templates/concept.md %}

cn/docs/tutorials/object-management-kubectl/object-management.md

@@ -1,157 +0,0 @@
----
-title: Kubernetes 对象管理
-redirect_from:
-- "/docs/concepts/tools/kubectl/object-management-overview/"
-- "/docs/concepts/tools/kubectl/object-management-overview.html"
-- "/docs/user-guide/working-with-resources/"
-- "/docs/user-guide/working-with-resources.html"
----
-
-{% capture overview %}
-`kubectl` 命令行工具支持 Kubernetes 对象几种不同的创建和管理方法。本文档简要介绍了这些方法.
-{% endcapture %}
-
-{% capture body %}
-
-## 管理技巧
-
-**警告:** Kubernetes 对象应该只使用一种技术进行管理。混合使用不同的技术，会导致相同对象出现未定义的行为。
-
-| 管理技术             | 操作         |推荐环境 | 支持撰写  | 学习曲线 |
-|----------------------------------|----------------------|------------------------|--------------------|----------------|
-| 命令式的方式              | 活动对象         | 开发项目   | 1+                 | 最低         |
-| 命令式对象配置  | 单文件     | 生产项目    | 1                  | 中等       |
-| 声明式对象配置 | 文件目录 | 生产项目    | 1+                 | 最高        |
-
-## 命令式的方式
-
-当使用命令式的命令时，用户直接对集群中的活动对象进行操作。用户提供 `kubectl` 命令的参数或标记进行操作。
-
-这是在集群中启动或运行一次性任务的最简单的方法。因为这种技术直接在活动对象上运行，所以它没有提供以前配置的历史记录。
-
-### 例子
-
-通过创建 Deployment 对象来运行 nginx 容器的实例:
-
-```sh
-kubectl run nginx --image nginx
-```
-
-使用不同的语法做同样的事情:
-
-```sh
-kubectl create deployment nginx --image nginx
-```
-
-### 权衡
-
-与对象配置相比的优点:
-
- - 命令简单易学，易于记忆。
- - 命令只需要一个步骤即可对群集进行更改。
-
-与对象配置相比的缺点:
-
- - 命令不与变更审核流程整合。
- - 命令不提供与更改相关联的审计跟踪。
- - 除了活动对象之外，命令不提供记录来源。
- - 命令不提供用于创建新对象的模板。
-
-## 命令式对象配置
-
-在命令式对象配置中，`kubectl` 命令指定操作(创建，替换等)，可选标志和至少一个文件名称。指定的文件必须包含对象的完整定义以 YAML 或 JSON 格式。
-
-请参阅[参考资源](https://kubernetes.io/docs/resources-reference/v1.6/)
-查看有关对象定义的更多细节。
-
-**警告:** 命令式 `replace` 命令用新提供的命令替换现有资源规格，将对配置文件中缺少的对象的所有更改都丢弃。这种方法不应更新与配置文件无关的资源类型。例如，`LoadBalancer` 类型的服务使其 `externalIPs` 字段与集群的配置无关。
-
-### 例子
-
-创建对象定义配置文件:
-
-```sh
-kubectl create -f nginx.yaml
-```
-
-删除两个配置文件中定义的对象:
-
-```sh
-kubectl delete -f nginx.yaml -f redis.yaml
-```
-
-通过覆写实时配置更新配置文件中定义的对象:
-
-```sh
-kubectl replace -f nginx.yaml
-```
-
-### 权衡
-
-与命令式的命令相比的优点:
-
- - 对象配置可以存储在源码控制系统中，如Git。
- - 对象配置可以与进程集成，例如在推送和审计跟踪之前查看更改。
- - 对象配置提供了一个用于创建新对象的模板。
-
-与命令式的命令相比的缺点:
-
- - 对象配置需要对对象模式有基本的了解。
- - 对象配置需要编写 YAML 文件的附加步骤。
-
-与声明式对象配置相比的优势:
-
- - 命令对象配置行为更简单易懂。
- - 至于 Kubernetes 1.5 版本，命令式对象配置更为成熟。
-
-与声明式对象配置相比的缺点:
-
- - 命令对象配置最适合于文件，而不是目录。
- - 活动对象的更新必须反映在配置文件中，否则在下次更替时将丢失。
-
-## 声明式对象配置
-
-当使用声明式对象配置时，用户对本地存储的对象配置文件进行操作，但是用户没有定义要对文件执行的操作。通过 `kubectl` 自动检测每个对象进行创建、更新和删除操作。这样可以在目录层级上工作，因为不同的对象可能需要不同的操作。
-
-**注意:** 声明式对象配置保留由其他对象进行的更改，即使更改未合并到对象配置文件中。这可以通过使用 `patch` API 操作来写入观察到的差异，而不是使用`replace` API 操作来替换整个对象的配置。
-
-### 例子
-
-处理`configs` 目录中的所有对象配置文件，创建或修补(patch)活动对象:
-
-```sh
-kubectl apply -f configs/
-```
-
-递归处理目录:
-
-```sh
-kubectl apply -R -f configs/
-```
-
-### 权衡
-
-与命令式对象配置相比的优点:
-
- - 直接对活动对象进行的更改将被保留，即使它们未被并入到配置文件中。
- - 声明式对象配置更好地支持目录操作，并自动检测每个对象的操作类型 (创建、修补，删除)。
-
-与命令式对象配置相比的缺点:
-
-- 声明式对象配置在意外情况下难以调试和了解结果。
-- 使用差异的部分更新会创建复杂的合并和补丁操作。
-
- {% endcapture %}
-
- {% capture whatsnext %}
- -  [使用命令式的命令管理 Kubernetes 对象](/docs/tutorials/object-management-kubectl/imperative-object-management-command/)
- -  [使用对象配置管理 Kubernetes 对象(必要)](/docs/tutorials/object-management-kubectl/imperative-object-management-configuration/)
- -  [使用对象配置(声明式)管理 Kubernetes 对象](/docs/tutorials/object-management-kubectl/declarative-object-management-configuration/)
- -  [Kubectl 命令参考](/docs/user-guide/kubectl/v1.6/)
- -  [Kubernetes 对象模式参考](/docs/resources-reference/v1.6/)
-
- {% comment %}
- {% endcomment %}
- {% endcapture %}
-
- {% include templates/concept.md %}

cn/docs/whatisk8s.md

@@ -1,10 +0,0 @@
----
-assignees:
-- k8s-merge-robot
-
-title: 认识 Kubernetes?
----
-
-{% include user-guide-content-moved.md %}
-
-[认识 Kubernetes?](/docs/concepts/overview/what-is-kubernetes/)

community/index.html

@@ -1,71 +0,0 @@
----
-title: Community
-layout: basic
-cid: community
----
-
-<section id="hero" class="light-text">
-    <h1>Community</h1>
-</section>
-
-<section id="mainContent">
-    <main>
-        <div class="content">
-            <h3>Ensuring Kubernetes works well everywhere and for everyone.</h3>
-            <p>Connect with the Kubernetes community on our <a href="http://slack.k8s.io/">Slack channel</a> or join the
-                <a href="https://groups.google.com/forum/#!forum/kubernetes-dev">Kubernetes-dev Google group</a>. A weekly
-                community meeting takes place via video conference to discuss the state of affairs,
-                <a href="https://groups.google.com/forum/#!forum/kubernetes-community-video-chat">get a calendar invite</a>
-                to participate.</p>
-            <p>You can also join Kubernauts all around the world through our
-                <a href="https://www.meetup.com/topics/kubernetes/">Kubernetes Meetup Community</a> and the
-                <a href="https://www.meetup.com/Kubernetes-Cloud-Native-Online-Meetup/">Kubernetes Cloud Native Meetup Community</a>.</p>
-        </div>
-        <div class="content">
-            <h3>Special Interest Groups (SIGs)</h3>
-            <p>Have a special interest in how Kubernetes works with another technology?  See our ever growing
-                <a href="https://github.com/kubernetes/kubernetes/wiki/Special-Interest-Groups-(SIGs)">lists of SIGs</a>,
-                from AWS and Openstack to Big Data and Scalability, there's a place for you to contribute and instructions
-                for forming a new SIG if your special interest isn't covered (yet).</p>
-
-            <p>As a member of the Kubernetes community, you are welcome to join any of the SIG meetings
-                you are interested in. No registration required.</p>
-            <div id="calendarMeetings">
-                <iframe src="https://calendar.google.com/calendar/embed?src=cgnt364vd8s86hr2phapfjc6uk%40group.calendar.google.com&ctz=America/Los_Angeles"
-                        frameborder="0" scrolling="no"></iframe>
-            </div>
-        </div>
-        <div class="content">
-            <h3>Events</h3>
-            <div id="calendarEvents">
-                <iframe src="https://calendar.google.com/calendar/embed?src=nt2tcnbtbied3l6gi2h29slvc0%40group.calendar.google.com&ctz=America/Los_Angeles"
-                        frameborder="0" scrolling="no"></iframe>
-            </div>
-        </div>
-    </main>
-</section>
-
-<section id="talkToUs">
-    <main>
-        <h3>Talk to Us!</h3>
-        <h4>We would love to hear from you, how you are using Kubernetes,<br> and what we can do to make it better.</h4>
-        <div id="bigSocial">
-            <div>
-                <a href="https://twitter.com/kubernetesio">@kubernetesio</a>
-                <p>Get the latest news and updates.</p>
-            </div>
-            <div>
-                <a href="https://github.com/kubernetes/kubernetes">Github Project</a>
-                <p>Check out the project and consider contributing.</p>
-            </div>
-            <div>
-                <a href="http://slack.k8s.io/">#kubernetes-users</a>
-                <p>Our Slack channel is the best way to contact our engineers and share your ideas with them.</p>
-            </div>
-            <div>
-                <a href="http://stackoverflow.com/questions/tagged/kubernetes">Stack Overflow</a>
-                <p>Our user forum is a great place to go for community support.</p>
-            </div>
-        </div>
-    </main>
-</section>

config.toml

@@ -0,0 +1,167 @@
+baseURL = "https://kubernetes.io"
+title = "Kubernetes"
+
+defaultContentLanguage = "en"
+defaultContentLanguageInSubdir = false
+enableRobotsTXT = true
+
+disableKinds = ["taxonomy", "taxonomyTerm"]
+
+ignoreFiles = [ "^OWNERS$", "README[-]+[a-z]*\\.md", "^node_modules$", "content/en/docs/doc-contributor-tools" ]
+
+contentDir = "content/en"
+
+timeout = 3000
+
+# Highlighting config.
+pygmentsCodeFences = true
+pygmentsUseClasses = false
+# See https://help.farbox.com/pygments.html
+pygmentsStyle = "emacs"
+
+# Enable Git variables like commit, lastmod
+enableGitInfo = true
+
+# Norwegian ("no") is sometimes but not currently used for testing.
+disableLanguages = ["no"]
+
+[blackfriday]
+hrefTargetBlank = true
+fractions = false
+
+[frontmatter]
+date = ["date", ":filename", "publishDate", "lastmod"]
+
+[permalinks]
+blog = "/:section/:year/:month/:day/:slug/"
+
+# Be explicit about the output formats. We (currently) only want an RSS feed for the home page.
+[outputs]
+home = [ "HTML", "RSS", "HEADERS" ]
+page = [ "HTML"]
+section = [ "HTML"]
+
+# Add a "text/netlify" media type for auto-generating the _headers file
+[mediaTypes]
+[mediaTypes."text/netlify"]
+delimiter = ""
+
+[outputFormats]
+[outputFormats.RSS]
+baseName = "feed"
+
+# _headers file output (uses the template at layouts/index.headers)
+[outputFormats.HEADERS]
+mediatype = "text/netlify"
+baseName = "_headers"
+isPlainText = true
+notAlternative = true
+
+[params]
+
+time_format_blog = "Monday, January 02, 2006"
+description = "Production-Grade Container Orchestration"
+showedit = true
+
+latest = "v1.16"
+
+fullversion = "v1.12.10"
+version = "v1.12"
+githubbranch = "v1.12.10"
+docsbranch = "release-1.12"
+deprecated = true
+currentUrl = "https://kubernetes.io/docs/home/"
+nextUrl = "https://kubernetes-io-vnext-staging.netlify.com/"
+githubWebsiteRepo = "github.com/kubernetes/website"
+githubWebsiteRaw = "raw.githubusercontent.com/kubernetes/website"
+
+[[params.versions]]
+fullversion = "v1.16.0"
+version = "v1.16"
+githubbranch = "v1.16.0"
+docsbranch = "release-1.16"
+url = "https://kubernetes.io"
+
+[params.pushAssets]
+css = [
+  "callouts",
+  "styles",
+  "custom-jekyll/tags"
+]
+js = [
+  "custom-jekyll/tags",
+  "script"
+]
+
+[[params.versions]]
+fullversion = "v1.15.3"
+version = "v1.15"
+githubbranch = "v1.15.3"
+docsbranch = "release-1.15"
+url = "https://v1-15.docs.kubernetes.io"
+
+[[params.versions]]
+fullversion = "v1.14.6"
+version = "v1.14"
+githubbranch = "v1.14.6"
+docsbranch = "release-1.14"
+url = "https://v1-14.docs.kubernetes.io"
+
+[[params.versions]]
+fullversion = "v1.13.10"
+version = "v1.13"
+githubbranch = "v1.13.10"
+docsbranch = "release-1.13"
+url = "https://v1-13.docs.kubernetes.io"
+
+[[params.versions]]
+fullversion = "v1.12.10"
+version = "v1.12"
+githubbranch = "v1.12.10"
+docsbranch = "release-1.12"
+url = "https://v1-12.docs.kubernetes.io"
+
+# Language definitions.
+
+[languages]
+[languages.en]
+title = "Kubernetes"
+description = "Production-Grade Container Orchestration"
+languageName ="English"
+# Weight used for sorting.
+weight = 1
+
+[languages.zh]
+title = "Kubernetes"
+description = "Production-Grade Container Orchestration"
+languageName = "中文 Chinese"
+weight = 2
+contentDir = "content/zh"
+
+[languages.zh.params]
+time_format_blog = "2006.01.02"
+language_alternatives = ["en"]
+
+[languages.ko]
+title = "Kubernetes"
+description = "Production-Grade Container Orchestration"
+languageName = "한국어 Korean"
+weight = 3
+contentDir = "content/ko"
+
+[languages.ko.params]
+time_format_blog = "2006.01.02"
+language_alternatives = ["en"]
+
+[languages.no]
+title = "Kubernetes"
+description = "Production-Grade Container Orchestration"
+languageName ="Norsk"
+weight = 4
+contentDir = "content/no"
+
+[languages.no.params]
+time_format_blog = "02.01.2006"
+# A list of language codes to look for untranslated content, ordered from left to right.
+language_alternatives = ["en"]
+

content/en/OWNERS

@@ -0,0 +1,11 @@
+# This is the directory for English source content.
+# Teams and members are visible at https://github.com/orgs/kubernetes/teams.
+
+reviewers:
+- sig-docs-en-reviews
+
+approvers:
+- sig-docs-en-owners
+
+labels:
+- language/en

content/en/_common-resources/index.md

@@ -0,0 +1,3 @@
+---
+headless: true
+---

content/en/_index.html

@@ -0,0 +1,62 @@
+---
+title: "Production-Grade Container Orchestration"
+abstract: "Automated container deployment, scaling, and management"
+cid: home
+---
+
+{{< deprecationwarning >}}
+
+{{< blocks/section id="oceanNodes" >}}
+{{% blocks/feature image="flower" %}}
+### [Kubernetes]({{< relref "/docs/concepts/overview/what-is-kubernetes" >}}) is an open-source system for automating deployment, scaling, and management of containerized applications.
+
+It groups containers that make up an application into logical units for easy management and discovery. Kubernetes builds upon [15 years of experience of running production workloads at Google](http://queue.acm.org/detail.cfm?id=2898444), combined with best-of-breed ideas and practices from the community.
+{{% /blocks/feature %}}
+
+{{% blocks/feature image="scalable" %}}
+#### Planet Scale
+
+Designed on the same principles that allows Google to run billions of containers a week, Kubernetes can scale without increasing your ops team.
+
+{{% /blocks/feature %}}
+
+{{% blocks/feature image="blocks" %}}
+#### Never Outgrow
+
+Whether testing locally or running a global enterprise, Kubernetes flexibility grows with you to deliver your applications consistently and easily no matter how complex your need is.
+
+{{% /blocks/feature %}}
+
+{{% blocks/feature image="suitcase" %}}
+#### Run Anywhere
+
+Kubernetes is open source giving you the freedom to take advantage of on-premises, hybrid, or public cloud infrastructure, letting you effortlessly move workloads to where it matters to you.
+
+{{% /blocks/feature %}}
+
+{{< /blocks/section >}}
+
+{{< blocks/section id="video" background-image="kub_video_banner_homepage" >}}
+<div class="light-text">
+<h2>The Challenges of Migrating 150+ Microservices to Kubernetes</h2>
+        <p>By Sarah Wells, Technical Director for Operations and Reliability, Financial Times</p>
+        <button id="desktopShowVideoButton" onclick="kub.showVideo()">Watch Video</button>
+        <br>
+        <br>
+        <br>
+        <a href="https://www.lfasiallc.com/events/kubecon-cloudnativecon-china-2018/" button id="desktopKCButton">Attend KubeCon in Shanghai on Nov. 13-15, 2018</a>
+        <br>
+        <br>
+        <br>
+        <br>
+        <a href="https://events.linuxfoundation.org/events/kubecon-cloudnativecon-north-america-2018/" button id="desktopKCButton">Attend KubeCon in Seattle on Dec. 11-13, 2018</a>
+</div>
+<div id="videoPlayer">
+    <iframe data-url="https://www.youtube.com/embed/H06qrNmGqyE?autoplay=1" frameborder="0" allowfullscreen></iframe>
+    <button id="closeButton"></button>
+</div>
+{{< /blocks/section >}}
+
+{{< blocks/kubernetes-features >}}
+
+{{< blocks/case-studies >}}

content/en/blog/OWNERS

@@ -0,0 +1,9 @@
+# Owned by Kubernetes Blog reviewers.
+options:
+  no_parent_owners: false
+reviewers:
+  - kbarnard10
+approvers:
+  - bobsky
+  - natekartchner
+  - sarahkconway

content/en/blog/_index.md

@@ -0,0 +1,10 @@
+---
+title: Kubernetes Blog
+linkTitle: Blog
+menu:
+  main:
+    title: "Blog"
+    weight: 40
+    post: >
+       <p>Read the latest news for Kubernetes and the containers space in general, and get technical how-tos hot off the presses.</p>
+---

content/en/blog/_posts/2015-03-00-Kubernetes-Gathering-Videos.md

@@ -0,0 +1,10 @@
+---
+
+title: " Kubernetes Gathering Videos "
+date: 2015-03-23
+slug: kubernetes-gathering-videos
+url: /blog/2015/03/Kubernetes-Gathering-Videos
+---
+If you missed the Kubernetes Gathering in SF last month, fear not! Here are the videos from the evening presentations organized into a playlist on YouTube
+
+[![Kubernetes Gathering](https://img.youtube.com/vi/q8lGZCKktYo/0.jpg)](https://www.youtube.com/playlist?list=PL69nYSiGNLP2FBVvSLHpJE8_6hRHW8Kxe)

content/en/blog/_posts/2015-03-00-Participate-In-Kubernetes-User.md

@@ -0,0 +1,21 @@
+---
+title: " Participate in a Kubernetes User Experience Study "
+date: 2015-03-31
+slug: participate-in-kubernetes-user
+url: /blog/2015/03/Participate-In-Kubernetes-User
+---
+We need your help in shaping the future of Kubernetes and Google Container Engine, and we'd love to have you participate in a remote UX research study to help us learn about your experiences!  If you're interested in participating, we invite you to take [this brief survey](http://goo.gl/AXFFMs) to see if you qualify. If you’re selected to participate, we’ll follow up with you directly.
+
+
+- Length: 60 minute interview
+- Date: April 7th-15th
+- Location: Remote
+- Your gift: $100 Perks gift code\*
+- Study format: Interview with our researcher
+
+
+Interested in participating? Take [this brief survey](http://goo.gl/AXFFMs).
+
+
+
+\* Perks gift codes can be redeemed for gift certificates from VISA and used at a number of online retailers ([http://www.google.com/forms/perks/index1.html](http://www.google.com/forms/perks/index1.html)). Gift codes are only for participants who successfully complete the study session. You’ll be emailed the gift code after you complete the study session.

content/en/blog/_posts/2015-03-00-Weekly-Kubernetes-Community-Hangout.md

@@ -0,0 +1,67 @@
+---
+title: " Weekly Kubernetes Community Hangout Notes - March 27 2015 "
+date: 2015-03-28
+slug: weekly-kubernetes-community-hangout
+url: /blog/2015/03/Weekly-Kubernetes-Community-Hangout
+---
+Every week the Kubernetes contributing community meet virtually over Google Hangouts. We want anyone who's interested to know what's discussed in this forum.
+
+Agenda:
+
+\- Andy - demo remote execution and port forwarding
+
+\- Quinton - Cluster federation - Postponed
+
+\- Clayton - UI code sharing and collaboration around Kubernetes
+
+Notes from meeting:
+
+1\. Andy from RedHat:
+
+* Demo remote execution
+
+    * kubectl exec -p $POD -- $CMD
+
+    * Makes a connection to the master as proxy, figures out which node the pod is on, proxies connection to kubelet, which does the interesting bit.  via nsenter.
+
+    * Multiplexed streaming over HTTP using SPDY
+
+    * Also interactive mode:
+
+    * Assumes first container.  Can use -c $CONTAINER to pick a particular one.
+
+    * If have gdb pre-installed in container, then can interactively attach it to running process
+
+        * backtrace, symbol tbles, print, etc.  Most things you can do with gdb.
+
+    * Can also with careful flag crafting run rsync over this or set up sshd inside container.
+
+    * Some feedback via chat:
+* Andy also demoed port forwarding
+* nsenter vs. docker exec
+
+    * want to inject a binary under control of the host, similar to pre-start hooks
+
+    * socat, nsenter, whatever the pre-start hook needs
+* would be nice to blog post on this
+* version of nginx in wheezy is too old to support needed master-proxy functionality
+
+2\. Clayton: where are we wrt a community organization for e.g. kubernetes UI components?
+
+* google-containers-ui IRC channel, mailing list.
+* Tim: google-containers prefix is historical, should just do "kubernetes-ui"
+* also want to put design resources in, and bower expects its own repo.
+* General agreement
+
+3\. Brian Grant:
+
+* Testing v1beta3, getting that ready to go in.
+* Paul working on changes to commandline stuff.
+* Early to mid next week, try to enable v1beta3 by default?
+* For any other changes, file issue and CC thockin.
+
+4\. General consensus that 30 minutes is better than 60
+
+
+
+* Shouldn't artificially try to extend just to fill time.

content/en/blog/_posts/2015-03-00-Welcome-To-Kubernetes-Blog.md

@@ -0,0 +1,30 @@
+---
+title: Welcome to the Kubernetes Blog! 
+date: 2015-03-20
+slug: welcome-to-kubernetes-blog
+url: /blog/2015/03/Welcome-To-Kubernetes-Blog
+---
+Welcome to the new Kubernetes Blog. Follow this blog to learn about the Kubernetes Open Source project. We plan to post release notes, how-to articles, events, and maybe even some off topic fun here from time to time.
+
+
+If you are using Kubernetes or contributing to the project and would like to do a guest post, [please let me know](mailto:kitm@google.com).
+
+
+
+To start things off, here's a roundup of recent Kubernetes posts from other sites:
+
+- [Scaling MySQL in the cloud with Vitess and Kubernetes](http://googlecloudplatform.blogspot.com/2015/03/scaling-MySQL-in-the-cloud-with-Vitess-and-Kubernetes.html)
+- [Container Clusters on VMs](http://googlecloudplatform.blogspot.com/2015/02/container-clusters-on-vms.html)
+- [Everything you wanted to know about Kubernetes but were afraid to ask](http://googlecloudplatform.blogspot.com/2015/01/everything-you-wanted-to-know-about-Kubernetes-but-were-afraid-to-ask.html)
+- [What makes a container cluster?](http://googlecloudplatform.blogspot.com/2015/01/what-makes-a-container-cluster.html)
+- [Integrating OpenStack and Kubernetes with Murano](https://www.mirantis.com/blog/integrating-openstack-and-kubernetes-with-murano/)
+- [An introduction to containers, Kubernetes, and the trajectory of modern cloud computing](http://googlecloudplatform.blogspot.com/2015/01/in-coming-weeks-we-will-be-publishing.html)
+- [What is Kubernetes and how to use it?](http://www.centurylinklabs.com/what-is-kubernetes-and-how-to-use-it/)
+- [OpenShift V3, Docker and Kubernetes Strategy](https://blog.openshift.com/v3-docker-kubernetes-interview/)
+- [An Introduction to Kubernetes](https://www.digitalocean.com/community/tutorials/an-introduction-to-kubernetes)
+
+
+Happy cloud computing!
+
+
+ - Kit Merker - Product Manager, Google Cloud Platform

content/en/blog/_posts/2015-04-00-Borg-Predecessor-To-Kubernetes.md

@@ -0,0 +1,47 @@
+---
+title: " Borg: The Predecessor to Kubernetes "
+date: 2015-04-23
+slug: borg-predecessor-to-kubernetes
+url: /blog/2015/04/Borg-Predecessor-To-Kubernetes
+---
+Google has been running containerized workloads in production for more than a decade. Whether it's service jobs like web front-ends and stateful servers, infrastructure systems like [Bigtable](http://research.google.com/archive/bigtable.html) and [Spanner](http://research.google.com/archive/spanner.html), or batch frameworks like [MapReduce](http://research.google.com/archive/mapreduce.html) and [Millwheel](http://research.google.com/pubs/pub41378.html), virtually everything at Google runs as a container. Today, we took the wraps off of Borg, Google’s long-rumored internal container-oriented cluster-management system, publishing details at the academic computer systems conference [Eurosys](http://eurosys2015.labri.fr/). You can find the paper [here](https://research.google.com/pubs/pub43438.html).
+
+
+
+Kubernetes traces its lineage directly from Borg. Many of the developers at Google working on Kubernetes were formerly developers on the Borg project. We've incorporated the best ideas from Borg in Kubernetes, and have tried to address some pain points that users identified with Borg over the years.
+
+
+
+To give you a flavor, here are four Kubernetes features that came from our experiences with Borg:
+
+
+
+1) [Pods](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/pods.md). A pod is the unit of scheduling in Kubernetes. It is a resource envelope in which one or more containers run. Containers that are part of the same pod are guaranteed to be scheduled together onto the same machine, and can share state via local volumes.
+
+
+
+Borg has a similar abstraction, called an alloc (short for “resource allocation”). Popular uses of allocs in Borg include running a web server that generates logs alongside a lightweight log collection process that ships the log to a cluster filesystem (not unlike fluentd or logstash); running a web server that serves data from a disk directory that is populated by a process that reads data from a cluster filesystem and prepares/stages it for the web server (not unlike a Content Management System); and running user-defined processing functions alongside a storage shard. Pods not only support these use cases, but they also provide an environment similar to running multiple processes in a single VM -- Kubernetes users can deploy multiple co-located, cooperating processes in a pod without having to give up the simplicity of a one-application-per-container deployment model.
+
+
+
+2) [Services](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/services.md). Although Borg’s primary role is to manage the lifecycles of tasks and machines, the applications that run on Borg benefit from many other cluster services, including naming and load balancing. Kubernetes supports naming and load balancing using the service abstraction: a service has a name and maps to a dynamic set of pods defined by a label selector (see next section). Any container in the cluster can connect to the service using the service name. Under the covers, Kubernetes automatically load-balances connections to the service among the pods that match the label selector, and keeps track of where the pods are running as they get rescheduled over time due to failures.
+
+
+
+3) [Labels](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/labels.md). A container in Borg is usually one replica in a collection of identical or nearly identical containers that correspond to one tier of an Internet service (e.g. the front-ends for Google Maps) or to the workers of a batch job (e.g. a MapReduce). The collection is called a Job, and each replica is called a Task. While the Job is a very useful abstraction, it can be limiting. For example, users often want to manage their entire service (composed of many Jobs) as a single entity, or to uniformly manage several related instances of their service, for example separate canary and stable release tracks. At the other end of the spectrum, users frequently want to reason about and control subsets of tasks within a Job -- the most common example is during rolling updates, when different subsets of the Job need to have different configurations.
+
+
+
+Kubernetes supports more flexible collections than Borg by organizing pods using labels, which are arbitrary key/value pairs that users attach to pods (and in fact to any object in the system). Users can create groupings equivalent to Borg Jobs by using a “job:\<jobname\>” label on their pods, but they can also use additional labels to tag the service name, service instance (production, staging, test), and in general, any subset of their pods. A label query (called a “label selector”) is used to select which set of pods an operation should be applied to. Taken together, labels and [replication controllers](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/replication-controller.md) allow for very flexible update semantics, as well as for operations that span the equivalent of Borg Jobs.
+
+
+
+4) IP-per-Pod. In Borg, all tasks on a machine use the IP address of that host, and thus share the host’s port space. While this means Borg can use a vanilla network, it imposes a number of burdens on infrastructure and application developers: Borg must schedule ports as a resource; tasks must pre-declare how many ports they need, and take as start-up arguments which ports to use; the Borglet (node agent) must enforce port isolation; and the naming and RPC systems must handle ports as well as IP addresses.
+
+
+
+Thanks to the advent of software-defined overlay networks such as [flannel](https://coreos.com/blog/introducing-rudder/) or those built into [public clouds](https://cloud.google.com/compute/docs/networking), Kubernetes is able to give every pod and service its own IP address. This removes the infrastructure complexity of managing ports, and allows developers to choose any ports they want rather than requiring their software to adapt to the ones chosen by the infrastructure. The latter point is crucial for making it easy to run off-the-shelf open-source applications on Kubernetes--pods can be treated much like VMs or physical hosts, with access to the full port space, oblivious to the fact that they may be sharing the same physical machine with other pods.
+
+
+
+With the growing popularity of container-based microservice architectures, the lessons Google has learned from running such systems internally have become of increasing interest to the external DevOps community. By revealing some of the inner workings of our cluster manager Borg, and building our next-generation cluster manager as both an open-source project (Kubernetes) and a publicly available hosted service ([Google Container Engine](http://cloud.google.com/container-engine)), we hope these lessons can benefit the broader community outside of Google and advance the state-of-the-art in container scheduling and cluster management. &nbsp;

content/en/blog/_posts/2015-04-00-Faster-Than-Speeding-Latte.md

@@ -0,0 +1,8 @@
+---
+title: " Faster than a speeding Latte "
+date: 2015-04-06
+slug: faster-than-speeding-latte
+url: /blog/2015/04/Faster-Than-Speeding-Latte
+---
+Check out Brendan Burns racing Kubernetes.
+[![Check out Brendan Burns racing Kubernetes](https://img.youtube.com/vi/7vZ9dRKRMyc/0.jpg)](https://www.youtube.com/watch?v=?7vZ9dRKRMyc)

content/en/blog/_posts/2015-04-00-Introducing-Kubernetes-V1Beta3.md

@@ -0,0 +1,63 @@
+---
+title: " Introducing Kubernetes API Version v1beta3 "
+date: 2015-04-16
+slug: introducing-kubernetes-v1beta3
+url: /blog/2015/04/Introducing-Kubernetes-V1Beta3
+---
+We've been hard at work on cleaning up the API over the past several months (see [https://github.com/GoogleCloudPlatform/kubernetes/issues/1519](https://github.com/GoogleCloudPlatform/kubernetes/issues/1519) for details). The result is v1beta3, which is considered to be the release candidate for the v1 API.  
+
+We would like you to move to this new API version as soon as possible. v1beta1 and v1beta2 are deprecated, and will be removed by the end of June, shortly after we introduce the v1 API.  
+
+As of the latest release, v0.15.0, v1beta3 is the primary, default API. We have changed the default kubectl and client API versions as well as the default storage version (which means objects persisted in etcd will be converted from v1beta1 to v1beta3 as they are rewritten).   
+
+You can take a look at v1beta3 examples such as:  
+
+[https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/guestbook/v1beta3](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/guestbook/v1beta3)
+
+[https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/walkthrough/v1beta3](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/walkthrough/v1beta3)
+
+[https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/update-demo/v1beta3](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/update-demo/v1beta3)
+
+
+
+To aid the transition, we've also created a conversion [tool](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/cluster_management.md#switching-your-config-files-to-a-new-api-version) and put together a list of important [different API changes](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/api.md#v1beta3-conversion-tips).  
+
+
+- The resource `id` is now called `name`.
+- `name`, `labels`, `annotations`, and other metadata are now nested in a map called `metadata`
+- `desiredState` is now called `spec`, and `currentState` is now called `status`
+- `/minions` has been moved to `/nodes`, and the resource has kind `Node`
+- The namespace is required (for all namespaced resources) and has moved from a URL parameter to the path:`/api/v1beta3/namespaces/{namespace}/{resource_collection}/{resource_name}`
+- The names of all resource collections are now lower cased - instead of `replicationControllers`, use`replicationcontrollers`.
+- To watch for changes to a resource, open an HTTP or Websocket connection to the collection URL and provide the`?watch=true` URL parameter along with the desired `resourceVersion` parameter to watch from.
+- The container `entrypoint` has been renamed to `command`, and `command` has been renamed to `args`.
+- Container, volume, and node resources are expressed as nested maps (e.g., `resources{cpu:1}`) rather than as individual fields, and resource values support [scaling suffixes](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/resources.md#resource-quantities) rather than fixed scales (e.g., milli-cores).
+- Restart policy is represented simply as a string (e.g., "Always") rather than as a nested map ("always{}").
+- The volume `source` is inlined into `volume` rather than nested.
+- Host volumes have been changed to hostDir to hostPath  to better reflect that they can be files or directories
+
+
+
+And the most recently generated Swagger specification of the API is here:
+
+[http://kubernetes.io/third\_party/swagger-ui/#!/v1beta3](http://kubernetes.io/third_party/swagger-ui/#!/v1beta3)
+
+
+
+More details about our approach to API versioning and the transition can be found here:
+
+[https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/api.md](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/api.md)
+
+
+
+Another change we discovered is that with the change to the default API version in kubectl, commands that use "-o template" will break unless you specify "--api-version=v1beta1" or update to v1beta3 syntax. An example of such a change can be seen here:
+
+[https://github.com/GoogleCloudPlatform/kubernetes/pull/6377/files](https://github.com/GoogleCloudPlatform/kubernetes/pull/6377/files)
+
+
+
+If you use "-o template", I recommend always explicitly specifying the API version rather than relying upon the default. We may add this setting to kubeconfig in the future.
+
+
+
+Let us know if you have any questions. As always, we're available on IRC (#google-containers) and github issues.

content/en/blog/_posts/2015-04-00-Kubernetes-And-Mesosphere-Dcos.md

@@ -0,0 +1,31 @@
+---
+title: " Kubernetes and the Mesosphere DCOS "
+date: 2015-04-22
+slug: kubernetes-and-mesosphere-dcos
+url: /blog/2015/04/Kubernetes-And-Mesosphere-Dcos
+---
+
+# Kubernetes and the Mesosphere DCOS
+
+
+
+Today Mesosphere announced the addition of Kubernetes as a standard part of their [DCOS][1] offering.  This is a great step forwards in bringing cloud native application management to the world, and should lay to rest many questions we hear about 'Kubernetes or Mesos, which one should I use?'.  Now you can have your cake and eat it too:  use both.  Today's announcement extends the reach of Kubernetes to a new class of users, and add some exciting new capabilities for everyone.
+
+By way of background, Kubernetes is a cluster management framework that was started by Google nine months ago, inspired by the internal system known as Borg.  You can learn a little more about Borg by checking out this [paper][2].  At the heart of it Kubernetes offers what has been dubbed 'cloud native' application management.  To us, there are three things that together make something 'cloud native':
+
+
+
+* **Container oriented deployments**  Package up your application components with all their dependencies and deploy them using technologies like Docker or Rocket.  Containers radically simplify the deployment process, making rollouts repeatable and predictable.
+* **Dynamically managed**  Rely on modern control systems to make moment-to-moment decisions around the health management and scheduling of applications to radically improve reliability and efficiency.  There are some things that just machines do better than people, and actively running applications is one of those things.  
+* **Micro-services oriented**  Tease applications apart into small semi-autonomous services that can be consumed easily so that the resulting systems are easier to understand, extend and adapt.
+
+Kubernetes was designed from the start to make these capabilities available to everyone, and built by the same engineers that built the system internally known as Borg.  For many users the promise of 'Google style app management' is interesting, but they want to run these new classes of applications on the same set of physical resources as their existing workloads like Hadoop, Spark, Kafka, etc.  Now they will have access to commercially supported offering that brings the two worlds together.
+
+Mesosphere, one of the earliest supporters of the Kubernetes project, has been working closely with the core Kubernetes team to create a natural experience for users looking to get the best of both worlds, adding Kubernetes to every Mesos deployment they instantiate, whether it be in the public cloud, private cloud, or in a hybrid deployment model.  This is well aligned with the overall Kubernetes vision of creating ubiquitous management framework that runs anywhere a container can.  It will be interesting to see how you blend together the old world and the new on a commercially supported, versatile platform.
+
+Craig McLuckie
+
+Product Manager, Google and Kubernetes co-founder
+
+[1]: https://mesosphere.com/product/
+[2]: http://research.google.com/pubs/pub43438.html

content/en/blog/_posts/2015-04-00-Kubernetes-Release-0150.md

@@ -0,0 +1,84 @@
+---
+title: " Kubernetes Release: 0.15.0 "
+date: 2015-04-16
+slug: kubernetes-release-0150
+url: /blog/2015/04/Kubernetes-Release-0150
+---
+
+Release Notes:
+
+
+
+* Enables v1beta3 API and sets it to the default API version ([#6098][1])
+* Added multi-port Services ([#6182][2])
+    * New Getting Started Guides
+    * Multi-node local startup guide ([#6505][3])
+    * Mesos on Google Cloud Platform ([#5442][4])
+    * Ansible Setup instructions ([#6237][5])
+* Added a controller framework ([#5270][6], [#5473][7])
+* The Kubelet now listens on a secure HTTPS port ([#6380][8])
+* Made kubectl errors more user-friendly ([#6338][9])
+* The apiserver now supports client cert authentication ([#6190][10])
+* The apiserver now limits the number of concurrent requests it processes ([#6207][11])
+* Added rate limiting to pod deleting ([#6355][12])
+* Implement Balanced Resource Allocation algorithm as a PriorityFunction in scheduler package ([#6150][13])
+* Enabled log collection from master ([#6396][14])
+* Added an api endpoint to pull logs from Pods ([#6497][15])
+* Added latency metrics to scheduler ([#6368][16])
+* Added latency metrics to REST client ([#6409][17])
+* etcd now runs in a pod on the master ([#6221][18])
+* nginx now runs in a container on the master ([#6334][19])
+* Began creating Docker images for master components ([#6326][20])
+* Updated GCE provider to work with gcloud 0.9.54 ([#6270][21])
+* Updated AWS provider to fix Region vs Zone semantics ([#6011][22])
+* Record event when image GC fails ([#6091][23])
+* Add a QPS limiter to the kubernetes client ([#6203][24])
+* Decrease the time it takes to run make release ([#6196][25])
+* New volume support
+    * Added iscsi volume plugin ([#5506][26])
+    * Added glusterfs volume plugin ([#6174][27])
+    * AWS EBS volume support ([#5138][28])
+* Updated to heapster version to v0.10.0 ([#6331][29])
+* Updated to etcd 2.0.9 ([#6544][30])
+* Updated to Kibana to v1.2 ([#6426][31])
+* Bug Fixes
+    * Kube-proxy now updates iptables rules if a service's public IPs change ([#6123][32])
+    * Retry kube-addons creation if the initial creation fails ([#6200][33])
+    * Make kube-proxy more resiliant to running out of file descriptors ([#6727][34])
+
+To download, please visit https://github.com/GoogleCloudPlatform/kubernetes/releases/tag/v0.15.0
+
+[1]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6098 "Enabling v1beta3 api version by default in master"
+[2]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6182 "Implement multi-port Services"
+[3]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6505 "Docker multi-node"
+[4]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5442 "Getting started guide for Mesos on Google Cloud Platform"
+[5]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6237 "example ansible setup repo"
+[6]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5270 "Controller framework"
+[7]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5473 "Add DeltaFIFO (a controller framework piece)"
+[8]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6380 "Configure the kubelet to use HTTPS (take 2)"
+[9]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6338 "Return a typed error for config validation, and make errors simple"
+[10]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6190 "Add client cert authentication"
+[11]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6207 "Add a limit to the number of in-flight requests that a server processes."
+[12]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6355 "Added rate limiting to pod deleting"
+[13]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6150 "Implement Balanced Resource Allocation (BRA) algorithm as a PriorityFunction in scheduler package."
+[14]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6396 "Enable log collection from master."
+[15]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6497 "Pod log subresource"
+[16]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6368 "Add basic latency metrics to scheduler."
+[17]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6409 "Add latency metrics to REST client"
+[18]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6221 "Run etcd 2.0.5 in a pod"
+[19]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6334 "Add an nginx docker image for use on the master."
+[20]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6326 "Create Docker images for master components "
+[21]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6270 "Updates for gcloud 0.9.54"
+[22]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6011 "Fix AWS region vs zone"
+[23]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6091 "Record event when image GC fails."
+[24]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6203 "Add a QPS limiter to the kubernetes client."
+[25]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6196 "Parallelize architectures in both the building and packaging phases of `make release`"
+[26]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5506 "add iscsi volume plugin"
+[27]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6174 "implement glusterfs volume plugin"
+[28]: https://github.com/GoogleCloudPlatform/kubernetes/pull/5138 "AWS EBS volume support"
+[29]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6331 "Update heapster version to v0.10.0"
+[30]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6544 "Build etcd image (version 2.0.9), and upgrade kubernetes cluster to the new version"
+[31]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6426 "Update Kibana to v1.2 which paramaterizes location of Elasticsearch"
+[32]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6123 "Fix bug in kube-proxy of not updating iptables rules if a service's public IPs change"
+[33]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6200 "Retry kube-addons creation if kube-addons creation fails."
+[34]: https://github.com/GoogleCloudPlatform/kubernetes/pull/6727 "pkg/proxy: panic if run out of fd"