Official 1.14 Release Docs (#13174)

* Official documentation on Poseidon/Firmament, a new multi-scheduler support for K8S. (#11752)

* Added documentation about Poseidon-Firmament scheduler

* Fixed some style issues.

* Udpated the document as per the review comments.

* Fixed some typos and updated the document

* Updated the document as per the review comments.

* Document timeout attribute for kms-plugin. (#12158)

See 72540.

* Official documentation on Poseidon/Firmament, a new multi-scheduler  (#12343)

* Removed the old version of the Poseidon documentation. Incorrect location.

* Official documentation on Poseidon/Firmament, a new multi-scheduler support for K8S (#12069)

* Official documentation on Poseidon/Firmament, a new multi-scheduler support for K8S. (#11752)

* Added documentation about Poseidon-Firmament scheduler

* Fixed some style issues.

* Udpated the document as per the review comments.

* Fixed some typos and updated the document

* Updated the document as per the review comments.

* Updated the document as per review comments. Added config details.

* Updated the document as per the latest review comments. Fixed nits

* Made changes as per latest suggestions.

* Some more changes added.

* Updated as per suggestions.

* Changed the release process section.

* SIG Docs edits

Small edits to match style guidelines.

* add plus to feature state

* capitalization

* revert feature state shortcode

since this is a Kubernetes extension, not a direct feature, it shouldn't use the regular feature state tagging.

(cherry picked from commit 7730c1540b)

* Remove initializers from doc. It will be removed in 1.14 (#12331)

* kubeadm: Document CRI auto detection functionality (#12462)

Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>

* Minor doc change for GAing Pod DNS Config (#12514)

* Graduate ExpandInUsePersistentVolumes feature to beta (#10574)

* Rename 2018-11-07-grpc-load-balancing-with-linkerd.md.md file (#12594)

* Add dynamic percentage of node scoring to user docs (#12235)

* Add dynamic percentage of node scoring to user docs

* addressed review comments

* delete special symbol (#12445)

* Update documentation for VolumeSubpathEnvExpansion (#11843)

* Update documentation for VolumeSubpathEnvExpansion

* Address comments - improve descriptions

* Graduate Pod Priority and Preemption to GA (#12428)

* Added Instana links to the documentation (#12977)

* Added link to the Instana Kubernetes integration

* Added Instana link for services section

Added Instana and a link to the Kubernetes integration to the analytics services section and broadened the scope to APM, monitoring and analytics.

* Oxford comma /flex

* More Oxford commas, because they matter

* Update kubectl plugins to stable (#12847)

* documentation for CSI topology beta (#12889)

* Document changes to default RBAC discovery ClusterRole(Binding)s (#12888)

* Document changes to default RBAC discovery ClusterRole(Binding)s

Documentation for https://github.com/kubernetes/enhancements/issues/789 and https://github.com/kubernetes/kubernetes/pull/73807

* documentation review feedback

* CSI raw block to beta (#12931)

* Change incorrect string raw to block (#12926)

Fixes #12925

* Update documentation on node OS/arch labels (#12976)

These labels have been promoted to GA:
https://github.com/kubernetes/enhancements/issues/793

* local pv GA doc updates (#12915)

* Publish CRD OpenAPI Documentation (#12910)

* add documentation for CustomResourcePublishOpenAPI

* address comments

fix links, ordered lists, style and typo

* kubeadm: add document for upgrading from 1.13 to 1.14 (single CP and HA) (#13189)

* kubeadm: add document for upgrading from 1.13 to 1.14

- remove doc for upgrading 1.10 -> 1.11

* kubeadm: apply amends to upgrade-1.14 doc

* kubeadm: apply amends to upgrade-1.14 doc (part2)

* kubeadm: apply amends to upgrade-1.14 doc (part3)

* kubeadm: add note about "upgrade node experimental-control-plane"

+ add comment about `upgrade plan`

* kubeadm: add missing "You should see output similar to this"

* fix bullet indentation (#13214)

* mark PodReadinessGate GA (#12800)

* Update RuntimeClass documentation for beta (#13043)

* Update RuntimeClass documentation for beta

* Update feature gate & add upgrade section

* formatting fixes

* Highlight upgrade action required

* Address feedback

* CSI ephemeral volume alpha documentation (#10934)

* update kubectl documentation (#12867)

* update kubectl documentation

* add document for Secret/ConfigMap generators

* replace `kubectl create -f` by `kubectl apply -f`

* Add page for kustomization support in kubectl

* fix spelling errors and address comments

* Documentation for Windows GMSA feature (#12936)

* Documentation for Windows GMSA feature

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Enhancements to GMSA docs

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Fix links

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Fix GMSA link

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Add GMSA feature flag in feature flag list

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Relocate GMSA to container configuration

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Add example for container spec

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Remove changes in Windows index

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Update configure-gmsa.md

* Update configure-gmsa.md

* Update configure-gmsa.md

* Update configure-gmsa.md

* Rearrange the steps into two sections and other edits

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Fix links

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Add reference to script to generate GMSA YAMLs

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Some more clarifications for GMSA

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* HugePages graduated to GA (#13004)

* HugePages graduated to GA

* fixing nit for build

* Docs for node PID limiting (https://github.com/kubernetes/kubernetes/pull/73651) (#12932)

* kubeadm: update the reference documentation for 1.14 (#12911)

* kubeadm: update list of generated files for 1.14

NOTE: PLACEHOLDERS! these files are generated by SIG Docs each
release, but we need them to pass the k/website PR CI.

- add join_phase* (new sub phases of join)
- add init_phase_upload-certs.md (new upload certs phase for init)
- remove alpha-preflight (now both init and join have this)

* kubeadm: update reference docs includes for 1.14

- remove includes from alpha.md
- add upload-certs to init-phase.md
- add join-phase.md and it's phases

* kubeadm: update the editorial content of join and init

- cleanup master->control-plane node
- add some notes about phases and join
- remove table about pre-pulling images
- remove outdated info about self-hosting

* kubeadm: update target release for v1alpha3 removal

1.14 -> 1.15

* kubeadm: copy edits for 1.14 reference docs (part1)

* kubeadm: use "shell" for code blocks

* kubeadm: update the 1.14 HA guide (#13191)

* kubeadm: update the 1.14 HA guide

* kubeadm: try to fix note/caution indent in HA page

* kubeadm: fix missing sudo and minor amends in HA doc

* kubeadm: apply latest amends to the HA doc for 1.14

* fixed a few missed merge conflicts

* Admission Webhook new features doc (#12938)

- kubernetes/kubernetes#74998
- kubernetes/kubernetes#74477
- kubernetes/kubernetes#74562

* Clarifications and fixes in GMSA doc (#13226)

* Clarifications and fixes in GMSA doc

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Update configure-gmsa.md

* Reformat to align headings and pre-reqs better

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Reformat to align headings and pre-reqs better

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Reformat to fix bullets

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Reword application of sample gmsa

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Update configure-gmsa.md

* Address feedback to use active voice

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Address feedback to use active voice

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* RunAsGroup documentation for Progressing this to Beta (#12297)

* start serverside-apply documentation (#13077)

* start serverside-apply documentation

* add more concept info on server side apply

* Update api concepts

* Update api-concepts.md

* fix style issues

* Document CSI update (#12928)

* Document CSI update

* Finish CSI documentation

Also fix mistake with  ExpandInUsePersistentVolumes documented as beta

* Overall docs for CSI Migration feature (#12935)

* Placeholder docs for CSI Migration feature

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Address CR comments and update feature gates

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Add mappings for CSI plugins

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Add sections for AWS and GCE PD migration

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Add docs for Cinder and CSI Migration info

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Clarify scope to volumes with file system

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Change the format of EBS and Cinder CSI Migration sections to follow the GCE template

Signed-off-by: Deep Debroy <ddebroy@docker.com>

* Windows documentation updates for 1.14 (#12929)

* Updated the note to indicate doc work for 1.14

* first attempt at md export from gdoc

* simplifyig

* big attempt

* moving DRAFT windows content to PR for review

* moving content to PR in markdown for review

* updated note tags

* Delete windows-contributing.md

deleting this file as it is already ported to the github contributor guide

* fixed formatting in intro and cluster setup guide

* updating formatting for running containers guide

* rejiggered end of troubleshooting

* fixed minor typos

* Clarified the windows binary download step

* Update _index.md

making updates based on feedback

* Update _index.md

updating ovn-kubernetes docs

* Update _index.md

* Update _index.md

* updating relative docs links

updating all the links to be relative links to /docs

* Update _index.md

* Update _index.md

updates for windows services and ovn-kubernetes

* formatted for correct step numbering

* fix typos

* Update _index.md

updates for flannel PR in troubleshooting

* Update _index.md

* Update _index.md

updating a few sections like roadmap, services, troubleshooting/filing tickets

* Update _index.md

* Update _index.md

* Update _index.md

* Fixed a few whitespace issues

* Update _index.md

* Update _index.md

* Update _index.md

* add section on upgrading CoreDNS (#12909)

* documentation for kubelet resource metrics endpoint (#12934)

* windows docs updates for 1.14 (#13279)

* Delete sample-l2bridge-wincni-config.json

this file is not used anywhere

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Update _index.md

* Rename content/en/docs/getting-started-guides/windows/_index.md to content/en/docs/setup/windows/_index.md

moving to new location

* Delete flannel-master-kubectl-get-ds.png

* Delete flannel-master-kubeclt-get-pods.png

* Delete windows-docker-error.png

* Add files via upload

* Rename _index.md to add-windows-nodes.md

* Create _index.md

* Update _index.md

* Update add-windows-nodes.md

* Update add-windows-nodes.md

* Create user-guide-windows-nodes.md

* Create user-guide-windows-containers.md

* Update and rename add-windows-nodes.md to intro-windows-nodes.md

* Update user-guide-windows-containers.md

* Rename intro-windows-nodes.md to intro-windows-in-kubernetes.md

* Update user-guide-windows-nodes.md

* Update user-guide-windows-containers.md

* Update user-guide-windows-containers.md

* Update user-guide-windows-nodes.md

* Update user-guide-windows-containers.md

* Update _index.md

* Update intro-windows-in-kubernetes.md

* Update intro-windows-in-kubernetes.md

fixing the pause image

* Update intro-windows-in-kubernetes.md

changing tables from html to MD

* Update user-guide-windows-nodes.md

converting tables from HTML to MD

* Update intro-windows-in-kubernetes.md

* Update user-guide-windows-nodes.md

* Update user-guide-windows-nodes.md

* Update user-guide-windows-nodes.md

updating the numbering , even though it messes up the notes a little bit. Jim will file a ticket to follow up

* Update user-guide-windows-nodes.md

* update to windows docs for 1.14 (#13322)

* Update intro-windows-in-kubernetes.md

* Update intro-windows-in-kubernetes.md

* Update intro-windows-in-kubernetes.md

* Update intro-windows-in-kubernetes.md

* Update intro-windows-in-kubernetes.md

* Update user-guide-windows-containers.md

* Update user-guide-windows-nodes.md

* Update intro-windows-in-kubernetes.md (#13344)

* server side apply followup (#13321)

* change some parts of serverside apply docs in response to comments

* fix typos and wording

* Update config.toml (#13365)

.dockerignore

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

.editorconfig

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

.github/ISSUE_TEMPLATE.md

@@ -1,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,10 +1,16 @@
-> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-> For 1.8 Features: set Milestone to `1.8` and Base Branch to `release-1.8`
-> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
->
-> 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.
-
-![Allow edits from maintainers checkbox](https://help.github.com/assets/images/help/pull_requests/allow-maintainers-to-make-edits-sidebar-checkbox.png)
+>
+> For 1.14 Features: set Milestone to 1.14 and Base Branch to dev-1.14
+> 
+> For Chinese localization, base branch to release-1.12
+>
+> For Korean Localization: set Base Branch to dev-1.13-ko.<latest team milestone>
+>
+> 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.
+>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+>

.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,14 @@ Session.vim
 tags
 
 kubernetes.github.io.iml
+
+nohup.out
+
+# Hugo output
+public/
+resources/
+
+# Netlify Functions build output
+package-lock.json
+functions/
+node_modules/

.travis.yml

@@ -1,21 +1,22 @@
+env:
+  global:
+    - KUBE_VERSION: 1.13
 language: go
 go:
-  - 1.8.3
+  - 1.11.5
 
-# 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
-
-# (1) Fetch dependencies for us to run the tests in test/examples_test.go
-- pushd $GOPATH/src/k8s.io && git clone https://github.com/kubernetes/kubernetes && popd
-- pushd $GOPATH/src/k8s.io/kubernetes && git checkout release-1.7 && popd
-- cp -L -R $GOPATH/src/k8s.io/kubernetes/vendor/ $GOPATH/src/
-- rm -r $GOPATH/src/k8s.io/kubernetes/vendor/
-- go get -t -v k8s.io/website/test
-
-script:
-- go test -v k8s.io/website/test
-- ./verify-docs-format.sh
+jobs:
+  include:
+    - name: "Testing examples"
+      cache:
+        directories:
+          - $HOME/.cache/go-build
+      install:
+      - bash scripts/test_examples.sh install
+      script:
+      - bash scripts/test_examples.sh run
+    - name: "Hugo build"
+      install:
+      - make travis-hugo-build
+      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. :(

CONTRIBUTING.md

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

Dockerfile

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

Gemfile

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

Gemfile.lock

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

Makefile

@@ -1,18 +1,58 @@
-.PHONY: all build build-preview help serve
+DOCKER       = docker
+HUGO_VERSION = 0.53
+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.
-	bundle exec jekyll build
+build: ## Build site with production settings and put deliverables in ./public
+	hugo --minify
 
-build-preview: ## Build site with drafts and future posts enabled.
-	bundle exec jekyll build --drafts --future
+build-preview: ## Build site with drafts and future posts enabled
+	hugo --buildDrafts --buildFuture
+
+functions-build:
+	$(NETLIFY_FUNC) build functions-src
+
+check-headers-file:
+	scripts/check-headers-file.sh
+
+production-build: check-hugo-versions build check-headers-file ## Build the production site and ensure that noindex headers aren't added
+
+non-production-build: check-hugo-versions ## Build the non-production site, which adds noindex headers to prevent indexing
+	hugo --enableGitInfo
+
+sass-build:
+	scripts/sass.sh build
+
+sass-develop:
+	scripts/sass.sh develop
 
 serve: ## Boot the development server.
-	bundle exec jekyll serve
+	hugo server --buildFuture
 
-stage: ## Run the Jekyll staging container.
-	docker run -ti --rm -v "${PWD}":/k8sdocs -p 4000:4000 gcr.io/google-samples/k8sdocs:1.1
+docker-image:
+	$(DOCKER) build . --tag $(DOCKER_IMAGE) --build-arg HUGO_VERSION=$(HUGO_VERSION)
+
+docker-build:
+	$(DOCKER_RUN) $(DOCKER_IMAGE) hugo
+
+docker-serve:
+	$(DOCKER_RUN) -p 1313:1313 $(DOCKER_IMAGE) hugo server --buildFuture --bind 0.0.0.0
+
+# This command is used only by Travis CI; do not run this locally
+travis-hugo-build:
+	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
+
+check-hugo-versions:
+	scripts/hugo-version-check.sh $(HUGO_VERSION)

OWNERS

@@ -1,21 +1,10 @@
-# Reviewers can /lgtm /approve but not sufficient for auto-merge without an
-# approver
-reviewers:
-- rajakavitha1
-- stewart-yu
-- xiangpengzhao
-- zhangxiaoyu-zidif
+# See the OWNERS docs at https://go.k8s.io/owners
+
+reviewers:
+- sig-docs-en-reviews # Defined in OWNERS_ALIASES
 
-# 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:
-- bradamant3
-- bradtopol
-- chenopis
-- kbarnard10
-- mistyhacks
-- steveperry-53
-- tengqm
-- zacharysarah
-- zparnold
+- sig-docs-en-owners # Defined in OWNERS_ALIASES
+
+labels:
+- sig/docs

OWNERS_ALIASES

@@ -0,0 +1,137 @@
+aliases:
+  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-docs-en-owners: # Admins for English content
+    - bradamant3
+    - bradtopol
+    - chenopis
+    - cody-clark
+    - jaredbhatti
+    - jimangel
+    - kbarnard10
+    - mistyhacks
+    - rajakavitha1
+    - ryanmcginnis
+    - steveperry-53
+    - stewart-yu
+    - tengqm
+    - tfogo
+    - zacharysarah
+    - zhangxiaoyu-zidif
+    - zparnold
+  sig-docs-en-reviews: # PR reviews for English content
+    - jimangel
+    - rajakavitha1
+    - stewart-yu
+    - xiangpengzhao
+    - zhangxiaoyu-zidif
+  sig-docs-fr-owners: # Admins for French content
+    - sieben
+    - perriea
+    - rekcah78
+    - lledru
+    - yastij
+    - smana
+    - rbenzair
+    - abuisine
+    - erickhun
+    - jygastaud
+    - awkif
+    - oussemos
+  sig-docs-fr-reviews: # PR reviews for French content
+    - sieben
+    - perriea
+    - rekcah78
+    - lledru
+    - yastij
+    - smana
+    - rbenzair
+    - abuisine
+    - erickhun
+    - jygastaud
+    - awkif
+    - oussemos
+  sig-docs-it-owners: # Admins for Italian content
+    - rlenferink
+    - lledru
+    - micheleberardi
+  sig-docs-it-reviews: # PR reviews for Italian content
+    - rlenferink
+    - lledru
+    - micheleberardi
+  sig-docs-ja-owners: # Admins for Japanese content 
+    - cstoku
+    - nasa9084
+    - tnir
+    - zacharysarah
+  sig-docs-ja-reviews: # PR reviews for Italian content 
+    - cstoku
+    - makocchi-git
+    - MasayaAoyama
+    - nasa9084
+    - tnir
+  sig-docs-ko-owners: # Admins for Korean content
+    - ClaudiaJKang
+    - gochist
+    - ianychoi
+    - zacharysarah
+  sig-docs-ko-reviews: # PR reviews for Korean content
+    - ClaudiaJKang
+    - gochist
+    - ianychoi
+  sig-docs-maintainers: # Website maintainers
+    - bradamant3
+    - chenopis
+    - jaredbhatti
+    - jimangel
+    - kbarnard10
+    - mistyhacks
+    - pwittrock
+    - steveperry-53
+    - tengqm
+    - zacharysarah
+    - zparnold
+  sig-docs-zh-owners: # Admins for Chinese content
+    - bradtopol
+    - chenopis
+    - chenrui333
+    - dchen1107
+    - haibinxie
+    - hanjiayao
+    - lichuqiang
+    - lucperkins
+    - markthink
+    - SataQiu
+    - tengqm
+    - xiangpengzhao
+    - xichengliudui
+    - zacharysarah
+    - zhangxiaoyu-zidif
+  sig-docs-zh-reviews: # PR reviews for Chinese content
+    - chenrui333
+    - idealhack
+    - markthink
+    - SataQiu
+    - tengqm
+    - xiangpengzhao
+    - xichengliudui
+    - zhangxiaoyu-zidif
+    - pigletfly
+  

README-fr.md

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

README-ko.md

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

README.md

@@ -1,20 +1,82 @@
-## Instructions for Contributing to the Kubernetes Documentation
+# The Kubernetes documentation
 
-Welcome! We are very pleased you want to contribute to the Kubernetes documentation.
+[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website)
+[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
 
-You can click the **Fork** button in the upper-right area of the screen to create a copy of this repository in your GitHub account called a *fork*. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.
+Welcome! This repository houses all of the assets required to build the [Kubernetes website and documentation](https://kubernetes.io/). We're very pleased that you want to contribute!
+
+## Contributing to the docs
+
+You can click the **Fork** button in the upper-right area of the screen to create a copy of this repository in your GitHub account. This copy is called a *fork*. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.
+
+Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback.  As the owner of the pull request, **it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer.**  Also note that you may end up having more than one Kubernetes reviewer provide you feedback or you may end up getting feedback from a Kubernetes reviewer that is different than the one 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/)
-* [Review Issues](http://kubernetes.io/docs/home/contribute/review-issues/)
-* [Staging Your Documentation Changes](http://kubernetes.io/docs/home/contribute/stage-documentation-changes/)
-* [Using Page Templates](http://kubernetes.io/docs/home/contribute/page-templates/)
-* [Documentation Style Guide](http://kubernetes.io/docs/home/contribute/style-guide/)
+* [Start contributing](https://kubernetes.io/docs/contribute/start/)
+* [Staging Your Documentation Changes](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Using Page Templates](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [Documentation Style Guide](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [Localizing Kubernetes Documentation](https://kubernetes.io/docs/contribute/localization/)
+
+## `README.md`'s Localizing Kubernetes Documentation
+
+### Korean
+
+See translation of `README.md` and more detail guidance for Korean contributors on the [Korean README](README-ko.md) page.
+
+You can reach the maintainers of Korean localization at:
+
+* June Yi ([GitHub - @gochist](https://github.com/gochist))
+* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-ko)
+
+## 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.
+
+## Community, discussion, contribution, and support
+
+Learn how to engage with the Kubernetes community on the [community page](http://kubernetes.io/community/).
+
+You can reach the maintainers of this project at:
+
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+### Code of conduct
+
+Participation in the Kubernetes community is governed by the [Kubernetes Code of Conduct](code-of-conduct.md).
 
 ## Thank you!
 
-Kubernetes thrives on community participation, and we really appreciate your
-contributions to our site and our documentation!
+Kubernetes thrives on community participation, and we 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 Committee to reach out
+# to for triaging and handling of incoming issues.
+#
+# The below names agree to abide by the
+# [Embargo Policy](https://git.k8s.io/security/private-distributors-list.md#embargo-policy)
+# and will be removed and replaced if they violate that agreement.
+#
+# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE
+# INSTRUCTIONS AT https://kubernetes.io/security/
+
+chenopis
+bradamant3
+zacharysarah

_config.yml

@@ -1,90 +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.3"
-      version: "v1.7"
-      githubbranch: "v1.7.3"
-      docsbranch: "release-1.7"
-      versions:
-      - fullversion: "v1.11.0"
-          version: "v1.11"
-          githubbranch: "v1.11.0"
-          docsbranch: "release-1.11"
-          url:  https://kubernetes.io/docs/
-      - fullversion: "v1.10.0"
-          version: "v1.10"
-          githubbranch: "v1.10.0"
-          docsbranch: "release-1.10"
-          url:  https://v1-10.docs.kubernetes.io/
-        - fullversion: "v1.9.0"
-          version: "v1.9"
-          githubbranch: "v1.9.0"
-          docsbranch: "release-1.9"
-          url: https://v1-9.docs.kubernetes.io/docs/home/
-        - fullversion: "v1.8.4"
-          version: "v1.8"
-          githubbranch: "v1.8.4"
-          docsbranch: "release-1.8"
-          url: https://v1-8.docs.kubernetes.io/docs/home/
-        - fullversion: "v1.7.3"
-          version: "v1.7"
-          githubbranch: "v1.7.3"
-          docsbranch: "release-1.7"
-          url: https://v1-7.docs.kubernetes.io/docs/home/
-      deprecated: true
-      currentUrl: https://kubernetes.io/docs/home/
-      nextUrl: http://kubernetes-io-vnext-staging.netlify.com/
-  -
-    scope:
-      path: "docs"
-    values:
-      layout: docwithnav
-      showedit: true
-
-permalink: pretty
-
-gems:
-  - jekyll-feed
-  - jekyll-sitemap
-  - jekyll-seo-tag
-  - jekyll-include-cache
-# disabled gems
-#  - jekyll-redirect-from
-
-include: [_redirects,_headers]
-
-# 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/canonical-tags.yml

@@ -1,12 +0,0 @@
-- Fundamental
-- API Object
-- Metadata
-- Configuration
-- Security
-- Networking
-- Storage
-- Operation
-- Workload
-- Component
-- API
-- Extension

_data/concepts.yml

@@ -1,101 +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/taint-and-toleration.md
-  - docs/concepts/configuration/secret.md
-  - docs/concepts/configuration/organize-cluster-access-kubeconfig.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/cloud-providers.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/glossary/_example.yml

@@ -1,17 +0,0 @@
-id: _example
-name: Example K8s Term
-formerly:
-- Slang K8s Term
-- Misnomer
-- Formerly Known as Prince
-related:
-- Less Fancy K8s Term
-- Tangential Term
-- Commonly Used With
-tags:
-- Some Tag
-short-description: |
-  Required. One or two lines that provide a minimum definition. Do not repeat the term. Write about the plural of the term. Prefer fragments. Model after tooltips. End with a period.
-long-description: |
-  Optional. Longer additional text to appear after (in conjunction with) short description. Provide where the short description is not sufficient as the intro paragraph to a topic. Write complete but concise sentences.
-  **See /_includes/templates/glossary/README.md for the official style guide.**

_data/glossary/statefulset.yml

@@ -1,18 +0,0 @@
-id: statefulset
-name: StatefulSet
-formerly:
-- PetSet
-related:
-- Deployment
-- Pod
-tags:
-- Storage
-- Workload
-- API Object
-short-description: |
-  Manage the deployment and scaling of a set of Pods, *and provide guarantees about ordering*. They do so by maintaining a *unique*, sticky identity for each of their Pods.
-
-long-description: |
-  Like Deployments, StatefulSets manage Pods that are based on an identical container spec. However, although their specs are the same, the Pods in a StatefulSet are not interchangeable. Each Pod has a persistent identifier that it maintains across any rescheduling.
-
-  StatefulSets also operate according to the Controller pattern. You define your desired state in a StatefulSet *object*, and the StatefulSet *controller* makes any necessary updates to the get there from the current state.

_data/reference.yml

@@ -1,106 +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
-  - docs/reference/client-libraries.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/
-  - 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
-
-- title: Setup Tools
-  section:
-  - title: Kubeadm
-    path: /docs/admin/kubeadm/
-  - title: Kubefed
-    path: /docs/admin/kubefed/
-    section:
-    - docs/admin/kubefed.md
-    - docs/admin/kubefed_options.md
-    - docs/admin/kubefed_init.md
-    - docs/admin/kubefed_join.md
-    - docs/admin/kubefed_unjoin.md
-    - docs/admin/kubefed_version.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/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/auth/access.md
-  - docs/admin/ovs-networking.md
-  - title: Security Contexts
-    path: https://git.k8s.io/community/contributors/design-proposals/auth/security_context.md
-  - title: Security in Kubernetes
-    path: https://git.k8s.io/community/contributors/design-proposals/auth/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/alibaba-cloud.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/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

_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/deprecation-warning.html

@@ -1,12 +0,0 @@
-{% if page.deprecated %}
-<section id="deprecationWarning">
-  <main>
-    <div class="content deprecation-warning">
-      <h3>
-        Documentation for Kubernetes {{ page.version}} is no longer actively maintained. The version you are currently viewing is a static snapshot.
-        For up-to-date documentation, see the <a href="{{ page.currentUrl }}">latest</a> version.
-      </h3>
-    </div>
-  </main>
-</section>
-{% endif %}

_includes/feature-dialog.md

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

_includes/feature-state-alpha.md

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

_includes/feature-state-beta.md

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

_includes/feature-state-deprecated.md

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

_includes/feature-state-stable.md

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

_includes/federated-task-tutorial-prereqs.md

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

_includes/federation-content-moved.md

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

_includes/footer-scripts.html

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

_includes/footer.html

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

_includes/head.html

@@ -1,27 +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">
-    {% if page.case_study_styles %}<link rel="stylesheet" type="text/css" href="/css/case_study_styles.css"><!-- custom case_study_styles on -->{% else %}<link rel="stylesheet" type="text/css" href="/css/styles.css"><!-- default styles.css on -->{% endif %}
-    <link rel="stylesheet" type="text/css" href="/css/jquery-ui.min.css">
-    <link rel="stylesheet" type="text/css" href="/css/sweetalert.css">
-    <link rel="stylesheet" type="text/css" href="/css/callouts.css">
-    {% if page.deprecated %}<link rel="stylesheet" type="text/css" href="/css/deprecation-warning.css">{% endif %}
-    {% if page.class == "gridPage" %}<link rel="stylesheet" type="text/css" href="/css/gridpage.css">{% endif %}
-    {% if page.css %}<link rel="stylesheet" type="text/css" href="{{ page.css }}"><!-- custom css added -->{% else %}<!-- no custom css detected -->{% 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,69 +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>
-            <li>
-                <a href="#">
-                    {{page.version}} <span class="ui-icon ui-icon-carat-1-s"></span>
-                </a>
-                <ul>
-                {% for version in page.versions %}
-                  <li><a href="{{ version.url }}">{{ version.version }}</a></li>
-                {% endfor %}
-                </ul>
-              </li>
-            </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,651 +0,0 @@
-;(function () {
-	var partners = [
-		{
-			type: 2,
-			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: 2,
-			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: 'https://www.citrix.com/networking/microservices.html',
-			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: '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://www.wercker.com/integrations/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 Labs',
-			logo: 'rancher-labs',
-			link: 'http://rancher.com/kubernetes/',
-			blurb: 'Rancher is an open-source, production-ready container management platform that makes it easy to deploy and manage Kubernetes.'
-		},
-		{
-			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: 2,
-			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: 2,
- 			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: 2,
- 			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: 2,
-			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: 2,
-			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: 2,
-			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: 2,
-			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/latest/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: 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: 2,
- 			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: 2,
- 			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: 2,
- 			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: '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/product-page/',
- 			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: 'http://lovable.tech/',
- 			blurb: 'World class engineers, designers, and strategic consultants helping you ship Lovable web & mobile technology.'
-  		},
-		{
- 			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: 2,
- 			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: 2,
- 			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'
-			},
-		{
- 			type: 0,
-	 		name: 'SUSE Llc.',
-	 		logo: 'suse',
-	 		link: 'https://www.suse.com/products/caas-platform/',
-	 		blurb: 'SUSE delivers Kubernetes as part of SUSE CaaS Platform and SUSE OpenStack Cloud, for enterprises that want truly open, open source solutions for cloud-native applications.'
-			},
-		{
-	 		type: 0,
-		 	name: 'Instana',
-		 	logo: 'instana',
-		 	link: 'https://www.instana.com/supported-technologies/',
-		 	blurb: 'Instana monitors the infrastructure, containers and services deployed on a Kubernetes cluster.'
-			},
-		{
-		 	type: 0,
-			name: 'Netsil',
-			logo: 'netsil',
-			link: 'https://netsil.com/kubernetes/',
-			blurb: 'Generate a real-time, auto-discovered application topology map! Monitor Kubernetes pods and namespaces without any code instrumentation.'
-			},
-		{
-			type: 2,
-			name: 'Treasure Data',
-			logo: 'treasure-data',
-			link: 'https://fluentd.treasuredata.com/kubernetes-logging/',
-			blurb: 'Fluentd Enterprise brings smart, secure logging to Kubernetes, and brings integrations with backends such as Splunk, Kafka, or AWS S3.'
-			},
-		{
-			type: 2,
-			name: 'IBM',
-			logo: 'IBM',
-			link: 'https://www.ibm.com/cloud-computing/bluemix/containers',
-			blurb: 'IBM Container Service is a managed k8s environment with built-in cluster security and isolation while leveraging services including Watson, IoT, Weather, etc.'
-			},
-		{
-			type: 1,
-			name: 'Kenzan',
-			logo: 'Kenzan',
-			link: 'http://kenzan.com/?ref=kubernetes',
-			blurb: 'Kenzan is a software engineering and full-service consulting firm that provides customized, end-to-end solutions that drive change through digital transformation.'
-			},
-		{
-			type: 0,
-			name: 'Kublr',
-			logo: 'kublr',
-			link: 'http://kublr.com',
-			blurb: 'Simplify your Kubernetes experience with a fully production-ready, enterprise-grade cluster management platform.'
-			},
-		{
-			type: 0,
-			name: 'Endocode AG',
-			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: 2,
-			name: 'Accenture',
-			logo: 'accenture',
-			link: 'https://www.accenture.com/us-en/service-application-containers',
-	 		blurb: 'Architecture, implementation and operation of world-class Kubernetes solutions for cloud-native clients.'
-			},
-		{
-			type: 1,
-			name: 'Biarca',
-			logo: 'biarca',
-			link: 'http://biarca.io/',
-		 	blurb: 'Biarca is a cloud services provider and key focus areas Key areas of focus for Biarca include Cloud Adoption Services, Infrastructure Services, DevOps Services and Application Services. Biarca leverages Kubernetes to deliver containerized solutions.'
-			},
-		{
-			type: 2,
-			name: 'Claranet',
-			logo: 'claranet',
-			link: 'http://www.claranet.co.uk/hosting/google-cloud-platform-consulting-managed-services',
-			blurb: 'Claranet helps people migrate to the cloud and take full advantage of the new world it offers. We consult, design, build and proactively manage the right infrastructure and automation tooling for clients to achieve this.'
-			},
-		{
-			type: 1,
-			name: 'CloudKite',
-			logo: 'cloudkite',
-			link: 'https://cloudkite.io/',
-			blurb: 'CloudKite.io helps companies build and maintain highly automated, resilient, and impressively performing software on Kubernetes.'
-			},
-		{
-			type: 1,
-			name: 'CloudOps',
-			logo: 'CloudOps',
-			link: 'https://www.cloudops.com/services/docker-and-kubernetes-workshops/',
-			blurb: 'CloudOps gets you hands-on with the K8s ecosystem via workshop/lab. Get prod ready K8s in cloud(s) of your choice with our managed services.'
-			},
-		{
-			type: 2,
-			name: 'Ghostcloud',
-			logo: 'ghostcloud',
-			link: 'https://www.ghostcloud.cn/ecos-kubernetes',
-			blurb: 'EcOS is an enterprise-grade PaaS / CaaS based on Docker and Kubernetes, which makes it easier to configure, deploy and manage containerized applications.'
-			},
-		{
-			type: 2,
-			name: 'Contino',
-			logo: 'contino',
-			link: 'https://www.contino.io/',
-			blurb: 'We help enterprise organizations adopt DevOps, containers and cloud computing. Contino is a global consultancy that enables regulated organizations to accelerate innovation through the adoption of modern approaches to software delivery.'
-			},
-		{
-			type: 2,
-			name: 'Heptio',
-			logo: 'heptio',
-			link: 'http://heptio.com',
-			blurb: 'Heptio helps businesses of all sizes get closer to the vibrant Kubernetes community.'
-			},
-		{
-			type: 2,
-			name: 'Booz Allen Hamilton',
-			logo: 'boozallenhamilton',
-			link: 'https://www.boozallen.com/',
-			blurb: 'Booz Allen partners with public and private sector clients to solve their most difficult challenges through a combination of consulting, analytics, mission operations, technology, systems delivery, cybersecurity, engineering, and innovation expertise.'
-			},
-		{
-			type: 0,
-			name: 'Applatix',
-			logo: 'applatix',
-			link: 'https://applatix.com/applatix-product/',
- 			blurb: 'Applatix helps build and run containerized apps on public cloud using Docker and Kubernetes.'
-	  	}
-	]
-
-	var kcspContainer = document.getElementById('kcspContainer')
-	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;
-    if (obj.type === 0) {
-      container = isvContainer;
-    } else if (obj.type === 1) {
-      container = servContainer;
-    } else if (obj.type === 2) {
-      container = kcspContainer;
-    }
-
-		container.appendChild(box)
-	})
-})();

_includes/partner-style.css

@@ -1,158 +0,0 @@
-/*  SECTIONS  */
-.section {
-	clear: both;
-	padding: 0px;
-	margin-bottom: 2em;
-}
-
-/*  COLUMN SETUP  */
-.col {
-	display: block;
-	float:left;
-	margin: 1% 0 1% 1.6%;
-	background-color: #f9f9f9;
-}
-.col:first-child { margin-left: 0; }
-
-
-/*  GROUPING  */
-.group:before,
-.group:after {
-	content:"";
-	display:table;
-}
-.group:after {
-	clear:both;
-}
-.group {
-    zoom:1; /* For IE 6/7 */
-}
-
-/*  GRID OF THREE  */
-.span_3_of_3 {
-	width: 32.2%;
-	background-color: #f9f9f9;
-	padding: 20px;
-}
-.span_2_of_3 {
-	width: 32.2%;
-	background-color: #f9f9f9;
-	padding: 20px;
-}
-.span_1_of_3 {
-	width: 32.2%;
-	background-color: #f9f9f9;
-	padding: 20px;
-}
-
-/*  GO FULL WIDTH AT LESS THAN 480 PIXELS */
-
-@media only screen and (max-width: 480px) {
-	.col { margin: 1% 0 1% 0%;}
-	.span_3_of_3, .span_2_of_3, .span_1_of_3 { width: 100%; }
-}
-
-.button{
-  max-width: 100%;
-	line-height: 14px;
-	padding: 15px;
- }
-
-h5 {
-	font-size: 16px;
-	line-height: 1.5em;
-	margin-bottom: 2em;
-}
-
-#usersGrid a {
-	display: inline-block;
-	background-color: #f9f9f9;
-}
-
-#kcspContainer, #isvContainer, #servContainer {
-	position: relative;
-	width: 100%;
-	display: flex;
-	justify-content: space-between;
-	flex-wrap: wrap;
-}
-
-#isvContainer {
-	margin-bottom: 80px;
-}
-
-#kcspContainer {
-	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) {
-	#kcspContainer, #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) {
-	#kcspContainer, #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/tag-map.md

@@ -1,15 +0,0 @@
-<!-- Use include_cached when incorporating this file, in order to reduce computation/build time -->
-
-{% assign glossary_terms = site.data.glossary | where_exp: "term", "term.id != '_example'" %}
-
-{% assign tag_map = "" | split: " " %}
-
-{% for tag in site.data.canonical-tags %}
-
-{% assign term_list = glossary_terms | where_exp:"term", "term.tags contains tag" | map: "id" %}
-
-{% assign tag_obj = "" | split: " " | push: tag | push: term_list %}
-
-{% assign tag_map = tag_map | push: tag_obj %}
-
-{% endfor %}

_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/glossary/README.md

@@ -1,62 +0,0 @@
-# Kubernetes Glossary
-
-To write a glossary snippet, start with a copy of the template, [`/_data/glossary/_example.yml`](/_data/glossary/_example.yml). Make sure to provide (or omit) values for the following fields:
-
-* (Required) `id`.
-  * This field must match the name of the glossary file itself (without the `*.yml` extension). It is *not* intended to be displayed to users, and is only used programmatically.
-* (Required) `name`.
-  * The name of the term.
-* (Required) `tags`.
-  * Must be one of the tags listed in kubernetes.github.io/_data/canonical-terms-tags.yml.
-* (Required) `short description`.
-  * Make sure to replace the instructional text in the template with your content.
-* (Optional) `formerly` and `related`.
-  * If you do not provide these values, remove the fields.
-* (Optional) `long description`.
-  * If you do not provide a long description, remove the field -- that is, the complete key-value pair.
-
-The `_example.yml` template also contains basic information about how to write your snippet. For additional guidance, continue reading this readme.
-
-## Glossary snippet style guide
-
-This style guide supplements the guidance provided in the glossary template. It's intended to help you think about what and how to write glossary definitions. For more general guidance on style, consult [the core docs style guide](https://kubernetes.io/docs/home/contribute/style-guide/).
-
-### Minimum viable snippet:
-
-Every snippet must include at least the short description. The long description is optional, but should be provided for terms that need additional clarification. For consistency with existing *Concept* definitions, *write your definitions as if the term is plural*.
-
-**short-description** (Required): One line (or two short lines) that provides a minimum definition. Do not repeat the term. Prefer fragments. Model after tooltips. End with a period.
-
-**long-description** (Optional): Longer additional text to appear after (in conjunction with) short description. Provide in cases where the short description is not sufficient for the intro paragraph to a topic. Write complete but concise sentences.
-
-### Examples
-
-```yaml
-- name: Pod
-- tags:
-  - Fundamental
-  - Workload
-  - API Object
-- short-description: The smallest and simplest Kubernetes objects. Represent a set of running processes on your cluster.
-- long-description: Pods most often run only a single container, and are managed by a Deployment.
-```
-
-```yaml
-- name: Deployment
-- tags:
-  - Fundamental
-  - Workload
-  - API Object
-- short-description: Controllers that provide declarative updates for Pods and ReplicaSets.
-- long-description: Deployments are responsible for creating and updating instances of an application.
-```
-
-### Thinking about definitions
-
-* **Think of the short description as it would appear in a tooltip.** Is it sufficient to get the reader started? Is it short enough to be read inside a small UI element?
-
-  *Tip*: look at the API reference doc content (for example, https://kubernetes.io/docs/api-reference/v1.7/). Note, however, that this content should be used with care. The concept docs for Pod, for example, are clearer than the reference docs.
-
-* **The long description should follow the short description to make a complete introduction to a topic.** (This is the content that appears at the top of the content, before any generated TOC.) Does it provide information that's not already clear from the short description? Does it provide information that readers should have a general sense of before they dive into the details of the topic it helps introduce?
-
-  *Tip:* the long description does not need to be long; it's intended to extend but not replace the short description. Look through current related docs for ideas. (The Deployment long description is taken from a tutorial, for example.)

_includes/templates/glossary/_error.md

@@ -1,10 +0,0 @@
-### ERROR: You must define a <span style="font-family: monospace">`{{ include.missing_block }}`</span> field
-{: style="color:red" }
-
-The glossary template requires that you provide text that {{ include.purpose }}.
-
-To get rid of this message and take advantage of this template, define the `{{ include.missing_block }}`
-field for the `{{ include.term }}` glossary term and populate it with content.
-
-See `_data/glossary/_example.yml` for reference.
-<!-- TEMPLATE_ERROR -->

_includes/templates/glossary/snippet.md

@@ -1,25 +0,0 @@
-{% assign term_data = site.data.glossary.[include.term] %}
-
-{% if term_data.short-description %}
-
-{{ term_data.short-description | markdownify }}
-
-{% else %}
-
-{% include templates/glossary/_error.md term=term_data.name missing_block='short-description' purpose='concisely describes the key term in 1-2 lines' %}
-
-{% endif %}
-
-{% if include.length == "long" %}
-
-{% if term_data.long-description %}
-
-{{ term_data.long-description | markdownify }}
-
-{% else %}
-
-{% include templates/glossary/_error.md term=term_data.name missing_block='long-description' purpose='describes the key term in greater depth, supplementing the short-description' %}
-
-{% endif %}
-
-{% 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,79 +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>
-
-{% include deprecation-warning.html %}
-
-<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 }}

_redirects

@@ -1,450 +0,0 @@
-###############################################
-# set server-side redirects in this file      #
-# see https://www.netlify.com/docs/redirects/ #
-# test at https://play.netlify.com/redirects  #
-###############################################
-
-############################
-# pattern matching redirects
-#
-
-/docs/user-guide/kubectl/kubectl_*/     /docs/user-guide/kubectl/v1.7/#:splat 200
-/v1.1/docs/*     /docs/ 301
-/docs/user-guide/kubectl/1_5/*     https://v1-5.docs.kubernetes.io/docs/user-guide/kubectl/v1.5/ 301
-/docs/user-guide/kubectl/v1.5/node_modules/*     https://v1-5.docs.kubernetes.io/docs/user-guide/kubectl/v1.5/ 301
-/docs/resources-reference/1_5/*     https://v1-5.docs.kubernetes.io/docs/resources-reference/v1.5/ 301
-/docs/resources-reference/v1.5/node_modules/*     https://v1-5.docs.kubernetes.io/docs/resources-reference/v1.5/ 301
-/docs/user-guide/kubectl/v1.6/node_modules/*     https://v1-6.docs.kubernetes.io/docs/user-guide/kubectl/v1.6/ 301
-/docs/api-reference/v1.7/node_modules/*     /docs/api-reference/v1.7/ 301
-/docs/getting-started-guides/docker-multinode/*     /docs/setup/independent/create-cluster-kubeadm/ 301
-/docs/admin/resourcequota/*     /docs/concepts/policy/resource-quotas/ 301
-/docs/getting-started-guide/*     /docs/setup/ 301
-/docs/api-reference/v1.4/*     https://v1-4.docs.kubernetes.io/docs/reference/ 301
-/docs/api-reference/1_5/*     https://v1-5.docs.kubernetes.io/docs/reference/ 301
-/docs/api-reference/v1.5/*     https://v1-5.docs.kubernetes.io/docs/reference/ 301
-/docs/api-reference/v1.6/*     https://v1-6.docs.kubernetes.io/docs/reference/ 301
-/docs/resources-reference/1_5/*     /docs/resources-reference/v1.5/ 301
-/docs/resources-reference/1_6/*     /docs/resources-reference/v1.6/ 301
-/docs/resources-reference/1_7/*     /docs/resources-reference/v1.7/ 301
-/docs/templatedemos/*     /docs/home/contribute/page-templates/ 301
-/docs/tutorials/getting-started/*     /docs/tutorials/kubernetes-basics/ 301
-/docs/user-guide/federation/*     /docs/concepts/cluster-administration/federation/ 301
-/docs/user-guide/garbage-collector/*     /docs/concepts/workloads/controllers/garbage-collection/ 301
-/docs/user-guide/horizontal-pod-autoscaler/*     /docs/tasks/run-application/horizontal-pod-autoscale/ 301
-/kubernetes-bootcamp/*     /docs/tutorials/kubernetes-basics/ 301
-/swagger-spec/*     https://github.com/kubernetes/kubernetes/tree/master/api/swagger-spec/ 301
-/third_party/swagger-ui/*     /docs/reference/ 301
-
-############################
-# individual redirects
-#
-
-/gettingstarted/     /docs/home/ 301
-
-/docs/admin/addons/     /docs/concepts/cluster-administration/addons/ 301
-/docs/admin/apparmor/     /docs/tutorials/clusters/apparmor/ 301
-/docs/admin/audit/     /docs/tasks/debug-application-cluster/audit/ 301
-//docs/admin/authorization/rbac.md     /docs/admin/authorization/rbac/ 301
-/docs/admin/cluster-components/     /docs/concepts/overview/components/ 301
-/docs/admin/cluster-management/     /docs/tasks/administer-cluster/cluster-management/ 301
-/docs/admin/cluster-troubleshooting/     /docs/tasks/debug-application-cluster/debug-cluster/ 301
-/docs/admin/daemons/     /docs/concepts/workloads/controllers/daemonset/ 301
-/docs/admin/disruptions/     /docs/concepts/workloads/pods/disruptions/ 301
-/docs/admin/dns/     /docs/concepts/services-networking/dns-pod-service/ 301
-/docs/admin/etcd/     /docs/tasks/administer-cluster/configure-upgrade-etcd/ 301
-/docs/admin/etcd_upgrade/     /docs/tasks/administer-cluster/configure-upgrade-etcd/ 301
-/docs/admin/federation/kubefed/     /docs/tasks/federation/set-up-cluster-federation-kubefed/ 301
-/docs/admin/federation/kubefed.md     /docs/tasks/federation/set-up-cluster-federation-kubefed/ 301
-/docs/tasks/federation/set-up-cluster-federation-kubefed.md     /docs/tasks/federation/set-up-cluster-federation-kubefed/ 301
-/docs/admin/garbage-collection/     /docs/concepts/cluster-administration/kubelet-garbage-collection/ 301
-/docs/admin/ha-master-gce/     /docs/tasks/administer-cluster/highly-available-master/ 301
-/docs/admin/ha-master-gce.md     /docs/tasks/administer-cluster/highly-available-master/ 301
-/docs/admin/     /docs/concepts/cluster-administration/cluster-administration-overview/ 301
-/docs/admin/kubeadm-upgrade-1-7/     /docs/tasks/administer-cluster/kubeadm-upgrade-1-7/ 301
-/docs/admin/limitrange/docs/tasks/administer-cluster/cpu-memory-limit/ 301
-/docs/admin/master-node-communication/     /docs/concepts/architecture/master-node-communication/ 301
-/docs/admin/multi-cluster/     /docs/concepts/cluster-administration/federation/ 301
-/docs/admin/multiple-schedulers/     /docs/tasks/administer-cluster/configure-multiple-schedulers/ 301
-/docs/admin/namespaces/     /docs/tasks/administer-cluster/namespaces/ 301
-/docs/admin/namespaces/walkthrough/     /docs/tasks/administer-cluster/namespaces-walkthrough/ 301
-/docs/admin/network-plugins/     /docs/concepts/cluster-administration/network-plugins/ 301
-/docs/admin/networking/     /docs/concepts/cluster-administration/networking/ 301
-/docs/admin/node/     /docs/concepts/architecture/nodes/ 301
-/docs/admin/node-allocatable/     /docs/tasks/administer-cluster/reserve-compute-resources/ 301
-//docs/admin/node-allocatable.md     /docs/tasks/administer-cluster/reserve-compute-resources/ 301
-/docs/admin/node-conformance.md     /docs/admin/node-conformance/ 301
-/docs/admin/node-problem/     /docs/tasks/debug-application-cluster/monitor-node-health/ 301
-/docs/admin/out-of-resource/     /docs/tasks/administer-cluster/out-of-resource/ 301
-/docs/admin/rescheduler/     /docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/ 301
-/docs/admin/resourcequota/limitstorageconsumption/     /docs/tasks/administer-cluster/limit-storage-consumption/ 301
-/docs/admin/resourcequota/walkthrough/     /docs/tasks/administer-cluster/quota-api-object/ 301
-/docs/admin/static-pods/     /docs/tasks/administer-cluster/static-pod/ 301
-/docs/admin/sysctls/     /docs/concepts/cluster-administration/sysctl-cluster/ 301
-/docs/admin/upgrade-1-6/     /docs/tasks/administer-cluster/upgrade-1-6/ 301
-
-/docs/api/     /docs/concepts/overview/kubernetes-api/ 301
-
-/docs/concepts/abstractions/controllers/garbage-collection/     /docs/concepts/workloads/controllers/garbage-collection/ 301
-/docs/concepts/abstractions/controllers/petsets/     /docs/concepts/workloads/controllers/petset/ 301
-/docs/concepts/abstractions/controllers/statefulsets/     /docs/concepts/workloads/controllers/statefulset/ 301
-/docs/concepts/abstractions/init-containers/     /docs/concepts/workloads/pods/init-containers/ 301
-/docs/concepts/abstractions/overview/     /docs/concepts/overview/working-with-objects/kubernetes-objects/ 301
-/docs/concepts/abstractions/pod/     /docs/concepts/workloads/pods/pod-overview/ 301
-
-/docs/concepts/cluster-administration/access-cluster/     /docs/tasks/access-application-cluster/access-cluster/ 301
-/docs/concepts/cluster-administration/audit/     /docs/tasks/debug-application-cluster/audit/ 301
-/docs/concepts/cluster-administration/authenticate-across-clusters-kubeconfig/     /docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig/ 301
-/docs/concepts/cluster-administration/cluster-management/     /docs/tasks/administer-cluster/cluster-management/ 301
-/docs/concepts/cluster-administration/configure-etcd/     /docs/tasks/administer-cluster/configure-upgrade-etcd/ 301
-/docs/concepts/cluster-administration/etcd-upgrade/     /docs/tasks/administer-cluster/configure-upgrade-etcd/ 301
-/docs/concepts/cluster-administration/federation-service-discovery/     /docs/tasks/federation/federation-service-discovery/ 301
-/docs/concepts/cluster-administration/guaranteed-scheduling-critical-addon-pods/     /docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/ 301
-/docs/concepts/cluster-administration/master-node-communication/     /docs/concepts/architecture/master-node-communication/ 301
-/docs/concepts/cluster-administration/multiple-clusters/     /docs/concepts/cluster-administration/federation/ 301
-/docs/concepts/cluster-administration/out-of-resource/     /docs/tasks/administer-cluster/out-of-resource/ 301
-/docs/concepts/cluster-administration/resource-usage-monitoring/     /docs/tasks/debug-application-cluster/resource-usage-monitoring/ 301
-/docs/concepts/cluster-administration/static-pod/     /docs/tasks/administer-cluster/static-pod/ 301
-/docs/concepts/clusters/logging/     /docs/concepts/cluster-administration/logging/ 301
-/docs/concepts/configuration/container-command-arg/     /docs/tasks/inject-data-application/define-command-argument-container/ 301
-/docs/concepts/ecosystem/thirdpartyresource/     /docs/tasks/access-kubernetes-api/extend-api-third-party-resource/ 301
-/docs/concepts/jobs/cron-jobs/     /docs/concepts/workloads/controllers/cron-jobs/ 301
-/docs/concepts/jobs/run-to-completion-finite-workloads/     /docs/concepts/workloads/controllers/jobs-run-to-completion/ 301
-/docs/concepts/nodes/node/     /docs/concepts/architecture/nodes/ 301
-/docs/concepts/storage/etcd-store-api-object/     /docs/tasks/administer-cluster/configure-upgrade-etcd/ 301
-/docs/concepts/tools/kubectl/object-management-overview/     /docs/tutorials/object-management-kubectl/object-management/ 301
-/docs/concepts/tools/kubectl/object-management-using-declarative-config/     /docs/tutorials/object-management-kubectl/declarative-object-management-configuration/ 301
-/docs/concepts/tools/kubectl/object-management-using-imperative-commands/     /docs/tutorials/object-management-kubectl/imperative-object-management-command/ 301
-/docs/concepts/tools/kubectl/object-management-using-imperative-config/     /docs/tutorials/object-management-kubectl/imperative-object-management-configuration/ 301
-
-/docs/getting-started-guides/     /docs/setup/pick-right-solution/ 301
-/docs/getting-started-guides/kubeadm/     /docs/setup/independent/create-cluster-kubeadm/ 301
-/docs/getting-started-guides/network-policy/calico/     /docs/tasks/administer-cluster/calico-network-policy/ 301
-/docs/getting-started-guides/network-policy/romana/     /docs/tasks/administer-cluster/romana-network-policy/ 301
-/docs/getting-started-guides/network-policy/walkthrough/     /docs/tasks/administer-cluster/declare-network-policy/ 301
-/docs/getting-started-guides/network-policy/weave/     /docs/tasks/administer-cluster/weave-network-policy/ 301
-/docs/getting-started-guides/running-cloud-controller/     /docs/tasks/administer-cluster/running-cloud-controller/ 301
-/docs/getting-started-guides/ubuntu/calico/     /docs/getting-started-guides/ubuntu/ 301
-
-/docs/hellonode/     /docs/tutorials/stateless-application/hello-minikube/ 301
-/docs/     /docs/home/ 301
-/docs/home/coreos/     /docs/getting-started-guides/coreos/ 301
-/docs/samples/     /docs/tutorials/ 301
-
-/docs/tasks/administer-cluster/apply-resource-quota-limit/     /docs/tasks/administer-cluster/quota-api-object/ 301
-/docs/tasks/administer-cluster/assign-pods-nodes/     /docs/tasks/configure-pod-container/assign-pods-nodes/ 301
-/docs/tasks/administer-cluster/overview/     /docs/concepts/cluster-administration/cluster-administration-overview/ 301
-/docs/tasks/administer-cluster/cpu-memory-limit/     /docs/tasks/administer-cluster/memory-default-namespace/ 301
-/docs/tasks/administer-cluster/share-configuration/     /docs/tasks/access-application-cluster/configure-access-multiple-clusters/ 301
-
-/docs/tasks/configure-pod-container/apply-resource-quota-limit/     /docs/tasks/administer-cluster/apply-resource-quota-limit/ 301
-/docs/tasks/configure-pod-container/calico-network-policy/     /docs/tasks/administer-cluster/calico-network-policy/ 301
-/docs/tasks/configure-pod-container/communicate-containers-same-pod/     /docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume/ 301
-/docs/tasks/configure-pod-container/declare-network-policy/     /docs/tasks/administer-cluster/declare-network-policy/ 301
-/docs/tasks/configure-pod-container/define-environment-variable-container/     /docs/tasks/inject-data-application/define-environment-variable-container/ 301
-/docs/tasks/configure-pod-container/distribute-credentials-secure/     /docs/tasks/inject-data-application/distribute-credentials-secure/ 301
-/docs/tasks/configure-pod-container/downward-api-volume-expose-pod-information/     /docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/ 301
-/docs/tasks/configure-pod-container/environment-variable-expose-pod-information/     /docs/tasks/inject-data-application/environment-variable-expose-pod-information/ 301
-/docs/tasks/configure-pod-container/limit-range/     /docs/tasks/administer-cluster/cpu-memory-limit/ 301
-/docs/tasks/configure-pod-container/romana-network-policy/     /docs/tasks/administer-cluster/romana-network-policy/ 301
-/docs/tasks/configure-pod-container/weave-network-policy/     /docs/tasks/administer-cluster/weave-network-policy/ 301
-/docs/tasks/configure-pod-container/assign-cpu-ram-container/     /docs/tasks/configure-pod-container/assign-memory-resource/ 301
-
-/docs/tasks/kubectl/get-shell-running-container/     /docs/tasks/debug-application-cluster/get-shell-running-container/ 301
-/docs/tasks/kubectl/install/     /docs/tasks/tools/install-kubectl/ 301
-/docs/tasks/kubectl/list-all-running-container-images/     /docs/tasks/access-application-cluster/list-all-running-container-images/ 301
-
-/docs/tasks/manage-stateful-set/debugging-a-statefulset/     /docs/tasks/debug-application-cluster/debug-stateful-set/ 301
-/docs/tasks/manage-stateful-set/delete-pods/     /docs/tasks/run-application/force-delete-stateful-set-pod/ 301
-/docs/tasks/manage-stateful-set/deleting-a-statefulset/     /docs/tasks/run-application/delete-stateful-set/ 301
-/docs/tasks/manage-stateful-set/scale-stateful-set/     /docs/tasks/run-application/scale-stateful-set/ 301
-/docs/tasks/manage-stateful-set/upgrade-pet-set-to-stateful-set/     /docs/tasks/run-application/upgrade-pet-set-to-stateful-set/ 301
-
-/docs/tasks/run-application/podpreset/     /docs/tasks/inject-data-application/podpreset/ 301
-/docs/tasks/troubleshoot/debug-init-containers/     /docs/tasks/debug-application-cluster/debug-init-containers/ 301
-/docs/tasks/web-ui-dashboard/     /docs/tasks/access-application-cluster/web-ui-dashboard/ 301
-/docs/templatedemos/     /docs/home/contribute/page-templates/ 301
-/docs/tools/kompose/     /docs/tools/kompose/user-guide/ 301
-
-/docs/tutorials/clusters/multiple-schedulers/     /docs/tasks/administer-cluster/configure-multiple-schedulers/ 301
-/docs/tutorials/connecting-apps/connecting-frontend-backend/     /docs/tasks/access-application-cluster/connecting-frontend-backend/ 301
-/docs/tutorials/federation/set-up-cluster-federation-kubefed/     /docs/tasks/federation/set-up-cluster-federation-kubefed/ 301
-//docs/tutorials/federation/set-up-cluster-federation-kubefed.md     /docs/tasks/federation/set-up-cluster-federation-kubefed/ 301
-/docs/tutorials/federation/set-up-coredns-provider-federation/     /docs/tasks/federation/set-up-coredns-provider-federation/ 301
-/docs/tutorials/federation/set-up-placement-policies-federation/     /docs/tasks/federation/set-up-placement-policies-federation/ 301
-/docs/tutorials/getting-started/create-cluster/     /docs/tutorials/kubernetes-basics/cluster-intro/ 301
-/docs/tutorials/stateful-application/run-replicated-stateful-application/     /docs/tasks/run-application/run-replicated-stateful-application/ 301
-/docs/tutorials/stateful-application/run-stateful-application/     /docs/tasks/run-application/run-single-instance-stateful-application/ 301
-/docs/tutorials/stateless-application/expose-external-ip-address-service/     /docs/tasks/access-application-cluster/service-access-application-cluster/ 301
-/docs/tutorials/stateless-application/run-stateless-ap-replication-controller/     /docs/tasks/run-application/run-stateless-application-deployment/ 301
-/docs/tutorials/stateless-application/run-stateless-application-deployment/     /docs/tasks/run-application/run-stateless-application-deployment/ 301
-
-/docs/user-guide/accessing-the-cluster/     /docs/tasks/access-application-cluster/access-cluster/ 301
-/docs/user-guide/add-entries-to-pod-etc-hosts-with-host-aliases/     /docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/ 301
-/docs/user-guide/annotations/     /docs/concepts/overview/working-with-objects/annotations/ 301
-/docs/user-guide/application-troubleshooting/     /docs/tasks/debug-application-cluster/debug-application/ 301
-/docs/user-guide/compute-resources/     /docs/concepts/configuration/manage-compute-resources-container/ 301
-/docs/user-guide/config-best-practices/     /docs/concepts/configuration/overview/ 301
-/docs/user-guide/configmap/     /docs/tasks/configure-pod-container/configmap/ 301
-/docs/user-guide/configuring-containers/     /docs/tasks/ 301
-/docs/user-guide/connecting-applications/     /docs/concepts/services-networking/connect-applications-service/ 301
-/docs/user-guide/connecting-to-applications-port-forward/     /docs/tasks/access-application-cluster/port-forward-access-application-cluster/ 301
-/docs/user-guide/connecting-to-applications-proxy/     /docs/tasks/access-kubernetes-api/http-proxy-access-api/ 301
-/docs/user-guide/container-environment/     /docs/concepts/containers/container-lifecycle-hooks/ 301
-/docs/user-guide/cron-jobs/     /docs/concepts/workloads/controllers/cron-jobs/ 301
-/docs/user-guide/debugging-pods-and-replication-controllers/     /docs/tasks/debug-application-cluster/debug-pod-replication-controller/ 301
-/docs/user-guide/debugging-services/     /docs/tasks/debug-application-cluster/debug-service/ 301
-/docs/user-guide/deploying-applications/     /docs/tasks/run-application/run-stateless-application-deployment/ 301
-/docs/user-guide/deployments/     /docs/concepts/workloads/controllers/deployment/ 301
-/docs/user-guide/downward-api/     /docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/ 301
-/docs/user-guide/downward-api/volume/     /docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/ 301
-/docs/user-guide/environment-guide/     /docs/tasks/inject-data-application/environment-variable-expose-pod-information/ 301
-/docs/user-guide/federation/cluster/     /docs/tasks/administer-federation/cluster/ 301
-/docs/user-guide/federation/configmap/     /docs/tasks/administer-federation/configmap/ 301
-/docs/user-guide/federation/daemonsets/     /docs/tasks/administer-federation/daemonset/ 301
-/docs/user-guide/federation/deployment/     /docs/tasks/administer-federation/deployment/ 301
-/docs/user-guide/federation/events/     /docs/tasks/administer-federation/events/ 301
-/docs/user-guide/federation/federated-ingress/     /docs/tasks/administer-federation/ingress/ 301
-/docs/user-guide/federation/federated-services/     /docs/tasks/federation/federation-service-discovery/ 301
-/docs/user-guide/federation/     /docs/concepts/cluster-administration/federation/ 301
-/docs/user-guide/federation/namespaces/     /docs/tasks/administer-federation/namespaces/ 301
-/docs/user-guide/federation/replicasets/     /docs/tasks/administer-federation/replicaset/ 301
-/docs/user-guide/federation/secrets/     /docs/tasks/administer-federation/secret/ 301
-/docs/user-guide/garbage-collection/     /docs/concepts/workloads/controllers/garbage-collection/ 301
-/docs/user-guide/getting-into-containers/     /docs/tasks/debug-application-cluster/get-shell-running-container/ 301
-/docs/user-guide/gpus/     /docs/tasks/manage-gpus/scheduling-gpus/ 301
-/docs/user-guide/horizontal-pod-autoscaling/     /docs/tasks/run-application/horizontal-pod-autoscale/ 301
-/docs/user-guide/horizontal-pod-autoscaling/walkthrough/     /docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/ 301
-/docs/user-guide/identifiers/     /docs/concepts/overview/working-with-objects/names/ 301
-/docs/user-guide/images/     /docs/concepts/containers/images/ 301
-/docs/user-guide/     /docs/home/ 301
-/docs/user-guide/ingress/     /docs/concepts/services-networking/ingress/ 301
-/docs/user-guide/introspection-and-debugging/     /docs/tasks/debug-application-cluster/debug-application-introspection/ 301
-/docs/user-guide/jobs/     /docs/concepts/workloads/controllers/jobs-run-to-completion/ 301
-/docs/user-guide/jobs/expansions/     /docs/tasks/job/parallel-processing-expansion/ 301
-/docs/user-guide/jobs/work-queue-1/     /docs/tasks/job/coarse-parallel-processing-work-queue/ 301
-/docs/user-guide/jobs/work-queue-2/     /docs/tasks/job/fine-parallel-processing-work-queue/ 301
-/docs/user-guide/kubeconfig-file/     /docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig/ 301
-/docs/user-guide/labels/     /docs/concepts/overview/working-with-objects/labels/ 301
-/docs/user-guide/liveness/     /docs/tasks/configure-pod-container/configure-liveness-readiness-probes/ 301
-/docs/user-guide/load-balancer/     /docs/tasks/access-application-cluster/create-external-load-balancer/ 301
-/docs/user-guide/logging/elasticsearch/     /docs/tasks/debug-application-cluster/logging-elasticsearch-kibana/ 301
-/docs/user-guide/logging/overview/     /docs/concepts/cluster-administration/logging/ 301
-/docs/user-guide/logging/stackdriver/     /docs/tasks/debug-application-cluster/logging-stackdriver/ 301
-/docs/user-guide/managing-deployments/     /docs/concepts/cluster-administration/manage-deployment/ 301
-/docs/user-guide/monitoring/     /docs/tasks/debug-application-cluster/resource-usage-monitoring/ 301
-/docs/user-guide/namespaces/     /docs/concepts/overview/working-with-objects/namespaces/ 301
-/docs/user-guide/networkpolicies/     /docs/concepts/services-networking/network-policies/ 301
-/docs/user-guide/node-selection/     /docs/concepts/configuration/assign-pod-node/ 301
-/docs/user-guide/persistent-volumes/     /docs/concepts/storage/persistent-volumes/ 301
-/docs/user-guide/persistent-volumes/index     /docs/concepts/storage/persistent-volumes/ 301
-/docs/user-guide/persistent-volumes/index.md     /docs/concepts/storage/persistent-volumes/ 301
-/docs/user-guide/persistent-volumes/walkthrough/     /docs/tasks/configure-pod-container/configure-persistent-volume-storage/ 301
-/docs/user-guide/petset/     /docs/concepts/workloads/controllers/petset/ 301
-/docs/user-guide/petset/bootstrapping/     /docs/concepts/workloads/controllers/petset/ 301
-/docs/user-guide/pod-preset/     /docs/tasks/inject-data-application/podpreset/ 301
-/docs/user-guide/pod-security-policy/     /docs/concepts/policy/pod-security-policy/ 301
-/docs/user-guide/pod-states/     /docs/concepts/workloads/pods/pod-lifecycle/ 301
-/docs/user-guide/pod-templates/     /docs/concepts/workloads/pods/pod-overview/ 301
-/docs/user-guide/pods/     /docs/concepts/workloads/pods/pod/ 301
-/docs/user-guide/pods/init-container/     /docs/concepts/workloads/pods/init-containers/ 301
-/docs/user-guide/pods/multi-container/     /docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume/ 301
-/docs/user-guide/pods/single-container/     /docs/tasks/run-application/run-stateless-application-deployment/ 301
-/docs/user-guide/prereqs/     /docs/tasks/tools/install-kubectl/ 301
-/docs/user-guide/production-pods/     /docs/tasks/ 301
-/docs/user-guide/projected-volume/     /docs/tasks/configure-pod-container/configure-projected-volume-storage/ 301
-/docs/user-guide/quick-start/     /docs/tasks/access-application-cluster/service-access-application-cluster/ 301
-/docs/user-guide/replicasets/     /docs/concepts/workloads/controllers/replicaset/ 301
-/docs/user-guide/replication-controller/     /docs/concepts/workloads/controllers/replicationcontroller/ 301
-/docs/user-guide/rolling-updates/     /docs/tasks/run-application/rolling-update-replication-controller/ 301
-/docs/user-guide/secrets/     /docs/concepts/configuration/secret/ 301
-/docs/user-guide/secrets/walkthrough/     /docs/tasks/inject-data-application/distribute-credentials-secure/ 301
-/docs/user-guide/service-accounts/     /docs/tasks/configure-pod-container/configure-service-account/ 301
-/docs/user-guide/services-firewalls/     /docs/tasks/access-application-cluster/configure-cloud-provider-firewall/ 301
-/docs/user-guide/services/     /docs/concepts/services-networking/service/ 301
-/docs/user-guide/services/operations/     /docs/tasks/access-application-cluster/connecting-frontend-backend/ 301
-/docs/user-guide/sharing-clusters/     /docs/tasks/administer-cluster/share-configuration/ 301
-/docs/user-guide/simple-nginx/     /docs/tasks/run-application/run-stateless-application-deployment/ 301
-/docs/user-guide/thirdpartyresources/     /docs/tasks/access-kubernetes-api/extend-api-third-party-resource/ 301
-/docs/user-guide/ui/     /docs/tasks/access-application-cluster/web-ui-dashboard/ 301
-/docs/user-guide/update-dem/     /docs/tasks/run-application/rolling-update-replication-controller/ 301
-/docs/user-guide/volumes/     /docs/concepts/storage/volumes/ 301
-/docs/user-guide/working-with-resources/     /docs/tutorials/object-management-kubectl/object-management/ 301
-
-/docs/whatisk8s/     /docs/concepts/overview/what-is-kubernetes/ 301
-
-
-##############
-# address 404s
-#
-/concepts/containers/container-lifecycle-hooks/     /docs/concepts/containers/container-lifecycle-hooks/ 301
-
-/docs/api-reference/apps/v1alpha1/definitions     https://v1-4.docs.kubernetes.io/docs/api-reference/apps/v1alpha1/definitions/ 301
-/docs/api-reference/apps/v1beta1/operations     https://v1-4.docs.kubernetes.io/docs/api-reference/apps/v1beta1/operations/ 301
-/docs/api-reference/authorization.k8s.io/v1beta1/definitions     https://v1-4.docs.kubernetes.io/docs/api-reference/authorization.k8s.io/v1beta1/definitions/ 301
-/docs/api-reference/authorization.k8s.io/v1beta1/operations     https://v1-4.docs.kubernetes.io/docs/api-reference/authorization.k8s.io/v1beta1/operations/ 301
-/docs/api-reference/autoscaling/v1/operations     https://v1-4.docs.kubernetes.io/docs/api-reference/autoscaling/v1/operations/ 301
-/docs/api-reference/batch/v1/operations     https://v1-4.docs.kubernetes.io/docs/api-reference/batch/v1/operations/ 301
-/docs/api-reference/batch/v2alpha1/definitions     https://v1-4.docs.kubernetes.io/docs/api-reference/batch/v2alpha1/definitions/ 301
-/docs/api-reference/certificates.k8s.io/v1alpha1/definitions     https://v1-4.docs.kubernetes.io/docs/api-reference/certificates.k8s.io/v1alpha1/definitions/ 301
-/docs/api-reference/certificates/v1alpha1/operations     https://v1-4.docs.kubernetes.io/docs/api-reference/certificates/v1alpha1/operations/ 301
-/docs/api-reference/extensions/v1beta1/operations     https://v1-4.docs.kubernetes.io/docs/api-reference/extensions/v1beta1/operations/ 301
-/docs/api-reference/policy/v1alpha1/definitions     https://v1-4.docs.kubernetes.io/docs/api-reference/policy/v1alpha1/definitions/ 301
-/docs/api-reference/policy/v1beta1/definitions     https://v1-4.docs.kubernetes.io/docs/api-reference/policy/v1beta1/definitions/ 301
-/docs/api-reference/README     https://v1-4.docs.kubernetes.io/docs/api-reference/README/ 301
-/docs/api-reference/storage.k8s.io/v1beta1/operations     https://v1-4.docs.kubernetes.io/docs/api-reference/storage.k8s.io/v1beta1/operations/ 301
-
-/docs/api-reference/v1/definitions/     /docs/api-reference/v1.7/ 301
-/docs/api-reference/v1/operations/     /docs/api-reference/v1.7/ 301
-
-/docs/concepts/cluster/     /docs/concepts/cluster-administration/cluster-administration-overview/ 301
-/docs/concepts/object-metadata/annotations/     /docs/concepts/overview/working-with-objects/annotations/ 301
-
-/docs/contribute/write-new-topic/     /docs/home/contribute/write-new-topic/ 301
-
-/docs/getting-started-guides/coreos/azure/     /docs/getting-started-guides/coreos/ 301
-/docs/getting-started-guides/coreos/bare_metal_calico/     /docs/getting-started-guides/coreos/ 301
-/docs/getting-started-guides/juju/     /docs/getting-started-guides/ubuntu/installation/ 301
-/docs/getting-started-guides/kargo/     /docs/getting-started-guides/kubespray/ 301
-/docs/getting-started-guides/logging-elasticsearch/     /docs/tasks/debug-application-cluster/logging-elasticsearch-kibana/ 301
-/docs/getting-started-guides/logging/     /docs/concepts/cluster-administration/logging/ 301
-/docs/getting-started-guides/rackspace/     /docs/setup/pick-right-solution/ 301
-/docs/getting-started-guides/ubuntu-calico/     /docs/getting-started-guides/ubuntu/ 301
-/docs/getting-started-guides/ubuntu/automated/     /docs/getting-started-guides/ubuntu/ 301
-/docs/getting-started-guides/vagrant/     /docs/getting-started-guides/alternatives/ 301
-/docs/getting-started-guides/windows/While/     /docs/getting-started-guides/windows/ 301
-
-/docs/federation/api-reference/extensions/v1beta1/definitions/     /docs/reference/federation/extensions/v1beta1/definitions/ 301
-/docs/federation/api-reference/federation/v1beta1/definitions/     /docs/reference/federation/extensions/v1beta1/definitions/ 301
-/docs/federation/api-reference/README/     /docs/reference/federation/ 301
-/docs/federation/api-reference/v1/definitions/     /docs/reference/federation/v1/definitions/ 301
-/docs/reference/federation/v1beta1/definitions/     /docs/reference/federation/extensions/v1beta1/definitions/ 301
-/docs/reference/federation/v1beta1/operations/     /docs/reference/federation/extensions/v1beta1/operations/ 301
-
-/docs/reporting-security-issues/     /security/ 301
-
-/docs/stable/user-guide/labels/     /docs/concepts/overview/working-with-objects/labels/ 301
-/docs/tasks/access-application-cluster/access-cluster.md      /docs/tasks/access-application-cluster/access-cluster/ 301
-/docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig/     /docs/tasks/access-application-cluster/configure-access-multiple-clusters/ 301
-/docs/tasks/access-kubernetes-api/access-kubernetes-api/http-proxy-access-api/     /docs/tasks/access-kubernetes-api/http-proxy-access-api/ 301
-/docs/tasks/administer-cluster/reserve-compute-resources/out-of-resource.md     /docs/tasks/administer-cluster/out-of-resource/ 301
-/docs/tasks/configure-pod-container/configure-pod-disruption-budget/     /docs/tasks/run-application/configure-pdb/ 301
-/docs/tasks/configure-pod-container/define-command-argument-container/     /docs/tasks/inject-data-application/define-command-argument-container/ 301
-
-/docs/tasks/debug-application-cluster/sematext-logging-monitoring/     https://sematext.com/kubernetes/ 301
-
-/docs/tasks/job/work-queue-1/     /docs/concepts/workloads/controllers/jobs-run-to-completion/ 301
-/docs/tasks/manage-stateful-set/delete-pods/     /docs/tasks/run-application/delete-stateful-set/ 301
-
-/docs/tutorials/getting-started/cluster-intro/     /docs/tutorials/kubernetes-basics/cluster-intro/ 301
-/docs/tutorials/getting-started/expose-intro/     /docs/tutorials/kubernetes-basics/expose-intro/ 301
-/docs/tutorials/getting-started/scale-app/     /docs/tutorials/kubernetes-basics/scale-interactive/ 301
-/docs/tutorials/getting-started/scale-intro/     /docs/tutorials/kubernetes-basics/scale-intro/ 301
-/docs/tutorials/getting-started/update-interactive/     /docs/tutorials/kubernetes-basics/update-interactive/ 301
-/docs/tutorials/getting-started/update-intro/     /docs/tutorials/kubernetes-basics/ 301
-
-/docs/user-guide/containers/     /docs/tasks/inject-data-application/define-command-argument-container/ 301
-/docs/user-guide/horizontal-pod-autoscaling/walkthrough.md     /docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/ 301
-/docs/user-guide/ingress.md     /docs/concepts/services-networking/ingress/ 301
-/docs/user-guide/replication-controller/operations/     /docs/concepts/workloads/controllers/replicationcontroller/ 301
-/docs/user-guide/resizing-a-replication-controller/     /docs/concepts/workloads/controllers/replicationcontroller/ 301
-/docs/user-guide/scheduled-jobs/     /docs/concepts/workloads/controllers/cron-jobs/ 301
-/docs/user-guide/security-context/     /docs/tasks/configure-pod-container/security-context/ 301
-
-/kubernetes-bootcamp/2-1.html     /docs/tutorials/kubernetes-basics/ 301
-/kubernetes-bootcamp/2-3-2.html     /docs/tutorials/kubernetes-basics/ 301
-/kubernetes     /docs/ 301
-/kubernetes/swagger-spec     https://github.com/kubernetes/kubernetes/tree/master/api/swagger-spec/ 301
-/serviceaccount/token/     /docs/tasks/configure-pod-container/configure-service-account/ 301
-
-/v1.1/docs/admin/networking.html/     /docs/concepts/cluster-administration/networking/ 301
-/v1.1/docs/getting-started-guides/     /docs/tutorials/kubernetes-basics/ 301
-
-#################################
-# redirects from /js/redirects.js
-#
-
-/resource-quota/     /docs/concepts/policy/resource-quotas/ 301
-/horizontal-pod-autoscaler/     /docs/tasks/run-application/horizontal-pod-autoscale/ 301
-/docs/roadmap/     https://github.com/kubernetes/kubernetes/milestones/ 301
-/api-ref/     https://github.com/kubernetes/kubernetes/milestones/ 301
-/kubernetes/third_party/swagger-ui/     /docs/reference/ 301
-/docs/user-guide/overview/     /docs/concepts/overview/what-is-kubernetes/ 301
-/docs/troubleshooting/     /docs/tasks/debug-application-cluster/troubleshooting/ 301
-/docs/concepts/services-networking/networkpolicies/     /docs/concepts/services-networking/network-policies/ 301
-/docs/getting-started-guides/meanstack/     https://medium.com/google-cloud/running-a-mean-stack-on-google-cloud-platform-with-kubernetes-149ca81c2b5d/ 301
-/docs/samples/     /docs/tutorials/ 301
-
-/v1.1 301
-/v1.0 301
-
-########################################################
-# Redirect users with chinese language preference to /cn
-#
-#/     /cn  302  Language=zh
-
-###########################
-# Fixed 404s from analytics
-#
-
-/concepts/containers/container-lifecycle-hooks/     /docs/concepts/containers/container-lifecycle-hooks/ 301
-/docs/abstractions/controllers/petset/     /docs/concepts/workloads/controllers/petset/ 301
-
-/docs/admin/add-ons/     /docs/concepts/cluster-administration/addons/ 301
-/docs/admin/limitrange/Limits/     /docs/tasks/administer-cluster/limit-storage-consumption/#limitrange-to-limit-requests-for-storage/ 301
-
-/docs/concepts/cluster-administration/device-plugins/     /docs/concepts/cluster-administration/network-plugins/ 301
-/docs/concepts/configuration/container-command-args/     /docs/tasks/inject-data-application/define-command-argument-container/ 301
-/docs/concepts/ecosystem/thirdpartyresource/     /docs/tasks/access-kubernetes-api/extend-api-third-party-resource/ 301
-/docs/concepts/overview/     /docs/concepts/overview/what-is-kubernetes/ 301
-/docs/concepts/policy/container-capabilities/     /docs/tasks/configure-pod-container/security-context/#set-capabilities-for-a-container/ 301
-/docs/concepts/policy/security-context/     /docs/tasks/configure-pod-container/security-context/ 301
-/docs/concepts/storage/volumes/emptyDirapiVersion/     /docs/concepts/storage/volumes/#emptydir/ 301
-/docs/concepts/tools/kubectl/object-management-using-commands/     /docs/tutorials/object-management-kubectl/imperative-object-management-command/ 301
-/docs/concepts/workload/pods/pod-overview/     /docs/concepts/workloads/pods/pod-overview 301
-/docs/concepts/workloads/controllers/cron-jobs/deployment/     /docs/concepts/workloads/controllers/cron-jobs/ 301
-/docs/concepts/workloads/controllers/statefulsets/     /docs/concepts/workloads/controllers/statefulset/ 301
-/docs/concepts/workloads/pods/init-containers/Kubernetes     /docs/concepts/workloads/pods/init-containers/ 301
-
-/docs/consumer-guideline/pod-security-coverage/     /docs/concepts/policy/pod-security-policy/ 301
-
-/docs/contribute/create-pull-request/     /docs/home/contribute/create-pull-request 301
-/docs/contribute/page-templates/     /docs/home/contribute/page-templates 301
-/docs/contribute/review-issues/     /docs/home/contribute/review-issues 301
-/docs/contribute/stage-documentation-changes/     /docs/home/contribute/stage-documentation-changes/ 301
-/docs/contribute/style-guide/     /docs/home/contribute/style-guide 301
-
-/docs/deprecate/     /ddocs/reference/deprecation-policy/ 301
-/docs/deprecation-policy/     /docs/reference/deprecation-policy/ 301
-
-/docs/federation/api-reference/     /docs/reference/federation/v1/operations/ 301
-/docs/federation/api-reference/extensions/v1beta1/operations/     /docs/reference/federation/extensions/v1beta1/operations/ 301
-/docs/federation/api-reference/federation/v1beta1/operations/     /docs/reference/federation/extensions/v1beta1/operations/ 301
-/docs/federation/api-reference/v1/operations/     /docs/reference/federation/v1/operations/ 301
-
-/docs/home/deprecation-policy/     /docs/reference/deprecation-policy/ 301
-
-/docs/stable/user-guide/labels/     /docs/concepts/overview/working-with-objects/labels/ 301
-
-/docs/tasks/administer-cluster/apply-resource-quota-limit/     /docs/tasks/administer-cluster/quota-api-object/ 301
-/docs/tasks/administer-cluster/configure-namespace-isolation/     /docs/concepts/services-networking/network-policies/ 301
-/docs/tasks/administer-cluster/configure-pod-disruption-budget/     /docs/tasks/run-application/configure-pdb/ 301
-/docs/tasks/administer-cluster/cpu-management-policies/     /docs/concepts/configuration/manage-compute-resources-container/ 301
-/docs/tasks/administer-cluster/default-cpu-request-limit/     /docs/tasks/configure-pod-container/assign-cpu-resource/#specify-a-cpu-request-and-a-cpu-limit/ 301
-/docs/tasks/administer-cluster/default-memory-request-limit/     /docs/tasks/configure-pod-container/assign-memory-resource/#specify-a-memory-request-and-a-memory-limit/ 301
-
-/docs/tasks/configure-pod-container/cilium-network-policy/     /docs/tasks/administer-cluster/cilium-network-policy/ 301
-/docs/tasks/configure-pod-container/define-command-argument-container/     /docs/tasks/inject-data-application/define-command-argument-container/ 301
-/docs/tasks/configure-pod-container/projected-volume/     /docs/tasks/configure-pod-container/configure-projected-volume-storage/ 301
-
-/docs/tasks/stateful-sets/deleting-pods/     /docs/tasks/run-application/force-delete-stateful-set-pod/ 301
-
-/docs/user-guide/liveness/     /docs/tasks/configure-pod-container/configure-liveness-readiness-probes/ 301
-/docs/user-guide/logging/     /docs/concepts/cluster-administration/logging/ 301
-/docs/user-guide/replication-controller/operations/     /docs/concepts/workloads/controllers/replicationcontroller/ 301
-/docs/user-guide/service-accounts/working-with-resources/     /docs/tutorials/object-management-kubectl/object-management/ 301
-/docs/user-guide/StatefulSet/     /docs/concepts/workloads/controllers/statefulset/ 301
-/docs/user-guide/ui-access/     /docs/tasks/access-application-cluster/web-ui-dashboard/ 301
-
-/latest/docs/     /docs/home/ 301
-
-/kubernetes/swagger-spec     https://github.com/kubernetes/kubernetes/tree/master/api/swagger-spec/ 301

_sass/_code-styles.sass

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

_sass/_desktop.sass

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

_sass/_reset.sass

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

_sass/_size.sass

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

_sass/_skin.sass

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

_sass/_tablet.sass

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

archetypes/default.md

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

case-studies/ancestry.html

@@ -1,117 +0,0 @@
----
-title: Ancestry Case Study
-layout: basic
-case_study_styles: true
-cid: caseStudies
-css: /css/style_ancestry.css
----
-
-<div class="banner1">
-  <h1> CASE STUDY:<img src="http://c.mfcreative.com/i/logo/ancestry-on-dark.svg" width="22%" style="margin-bottom:-12px;margin-left:3px;"><br> <div class="subhead">Digging Into the Past With New Technology</div></h1>
-
-</div>
-
-<div class="details">
-  Company &nbsp;<b>Ancestry</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Location &nbsp;<b>Lehi, Utah</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Industry &nbsp;<b>Internet Company, Online Services</b>
-</div>
-
-<hr>
-
-<section class="section1">
-<div class="cols">
-<div class="col1">
-
-<h2>Challenge</h2>
-Ancestry, the global leader in family history and consumer genomics, uses sophisticated engineering and technology to help everyone, everywhere discover the story of what led to them. The company has spent more than 30 years innovating and building products and technologies that at their core, result in real and emotional human responses. <a href="https://www.ancestry.com">Ancestry</a> currently serves more than 2.6 million paying subscribers, holds 20 billion historical records, 90 million family trees and more than four million people are in its AncestryDNA network, making it the largest consumer genomics DNA network in the world. The company's popular website, <a href="https://www.ancestry.com">ancestry.com</a>, has been working with big data long before the term was popularized. The site was built on hundreds of services, technologies and a traditional deployment methodology. "It's worked well for us in the past," says Paul MacKay, software engineer and architect at Ancestry, "but had become quite cumbersome in its processing and is time-consuming. As a primarily online service, we are constantly looking for ways to accelerate to be more agile in delivering our solutions and our&nbsp;products."
-
-<br>
-
-</div>
-
-<div class="col2">
-  <h2>Solution</h2>
-
-  The company is transitioning to cloud native infrastructure, using <a href="https://www.docker.com">Docker</a> containerization, <a href="https://kubernetes.io">Kubernetes</a> orchestration and <a href="https://prometheus.io">Prometheus</a> for cluster monitoring.<br>
-<br>
-<h2>Impact</h2>
-  "Every single product, every decision we make at Ancestry, focuses on delighting our customers with intimate, sometimes life-changing discoveries about themselves and their families," says MacKay. "As the company continues to grow, the increased productivity gains from using Kubernetes has helped Ancestry make customer discoveries faster. With the move to Dockerization for example, instead of taking between 20 to 50 minutes to deploy a new piece of code, we can now deploy in under a minute for much of our code. We’ve truly experienced significant time savings in addition to the various features and benefits from cloud native and Kubernetes-type technologies."
-</div>
-</div>
-</section>
-
-<div class="banner2">
-  <div class="banner2text">
-    "At a certain point, you have to step back if you're going to push a new technology and get key thought leaders with engineers within the organization to become your champions for new technology adoption. At training sessions, the development teams were always the ones that were saying, 'Kubernetes saved our time tremendously; it's an enabler. It really is incredible.'"<br><br><span style="font-size:16px">- PAUL MACKAY, SOFTWARE ENGINEER AND ARCHITECT AT ANCESTRY</span>
-  </div>
-</div>
-
-<section class="section2">
-<div class="fullcol">
-<h2>It started with a Shaky Leaf.</h2>
-
-    Since its introduction a decade ago, the Shaky Leaf icon has become one of Ancestry's signature features, which signals to users that there's a helpful hint you can use to find out more about your family tree.<br><br>
-    So when the company decided to begin moving its infrastructure to cloud native technology, the first service that was launched on <a href="https://kubernetes.io">Kubernetes</a>, the open source platform for managing application containers across clusters of hosts, was this hint system. Think of it as Amazon's recommended products, but instead of recommending products the company recommends records, stories, or familial connections. "It was a very important part of the site," says Ancestry software engineer and architect Paul MacKay, "but also small enough for a pilot project that we knew we could handle in a very appropriate, secure way."<br><br>
-    And when it went live smoothly in early 2016, "our deployment time for this service literally was cut down from 50 minutes to 2 or 5 minutes," MacKay adds. "The development team was just thrilled because we're focused on supplying a great experience for our customers. And that means features, it means stability, it means all those things that we need for a first-in-class type operation."<br><br>
-    The stability of that Shaky Leaf was a signal for MacKay and his team that their decision to embrace cloud native technologies was the right one for the company. With a private data center, Ancestry built its website (which launched in 1996) on hundreds of services and technologies and a traditional deployment methodology. "It worked well for us in the past, but the sum of the legacy systems became quite cumbersome in its processing and was time-consuming," says MacKay. "We were looking for other ways to accelerate, to be more agile in delivering our solutions and our products."
-</div>
-</section>
-
-<div class="banner3">
-  <div class="banner3text">
-"And when it [Kubernetes] went live smoothly in early 2016, 'our deployment time for this service literally was cut down from 50 minutes to 2 or 5 minutes,' MacKay adds. 'The development team was just thrilled because we're focused on supplying a great experience for our customers. And that means features, it means stability, it means all those things that we need for a first-in-class type operation.'"
-  </div>
-</div>
-
-<section class="section3">
-<div class="fullcol">
-  That need led them in 2015 to explore containerization. Ancestry engineers had already been using technology like <a href="https://www.java.com/en/">Java</a> and <a href="https://www.python.org">Python</a> on Linux, so part of the decision was about making the infrastructure more Linux-friendly. They quickly decided that they wanted to go with Docker for containerization, "but it always comes down to the orchestration part of it to make it really work," says MacKay.<br><br>
-  His team looked at orchestration platforms offered by <a href="https://docs.docker.com/compose/">Docker Compose</a>, <a href="http://mesos.apache.org">Mesos</a> and <a href="https://www.openstack.org/software/">OpenStack</a>, and even started to prototype some homegrown solutions. And then they started hearing rumblings of the imminent release of Kubernetes v1.0. "At the forefront, we were looking at the secret store, so we didn't have to manage that all ourselves, the config maps, the methodology of seamless deployment strategy," he says. "We found that how Kubernetes had done their resources, their types, their labels and just their interface was so much further advanced than the other things we had seen. It was a feature fit."<br><br>
-  <div class="quote">
-  Plus, MacKay says, "I just believed in the confidence that comes with the history that Google has with containerization. So we started out right on the leading edge of it. And we haven't looked back since."</div><br>
-  Which is not to say that adopting a new technology hasn't come with some challenges. "Change is hard," says MacKay. "Not because the technology is hard or that the technology is not good. It's just that people like to do things like they had done [before]. You have the early adopters and you have those who are coming in later. It was a learning experience on both sides."<br><br>
-  Figuring out the best deployment operations for Ancestry was a big part of the work it took to adopt cloud native infrastructure. "We want to make sure the process is easy and also controlled in the manner that allows us the highest degree of security that we demand and our customers demand," says MacKay. "With Kubernetes and other products, there are some good solutions, but a little bit of glue is needed to bring it into corporate processes and governances. It's like having a set of gloves that are generic, but when you really do want to grab something you have to make it so it's customized to you. That's what we had to do."<br><br>
-  Their best practices include allowing their developers to deploy into development stage and production, but then controlling the aspects that need governance and auditing, such as secrets. They found that having one namespace per service is useful for achieving that containment of secrets and config maps. And for their needs, having one container per pod makes it easier to manage and to have a smaller unit of deployment.
-<br><br>
-</div>
-</section>
-
-<div class="banner4">
-<div class="banner4text">
-
-"The success of Ancestry's first deployment of the hint system on Kubernetes helped create momentum for greater adoption of the technology."
-
-</div>
-</div>
-
-<section class="section4">
-<div class="fullcol">
-  With that process established, the time spent on deployment was cut down to under a minute for some services. "As programmers, we have what's called REPL: read, evaluate, print, and loop, but with Kubernetes, we have CDEL: compile, deploy, execute, and loop," says MacKay. "It's a very quick loop back and a great benefit to understand that when our services are deployed in production, they're the same as what we tested in the pre-production environments. The approach of cloud native for Ancestry provides us a better ability to scale and to accommodate the business needs as work loads occur."<br><br>
-  The success of Ancestry's first deployment of the hint system on Kubernetes helped create momentum for greater adoption of the technology. "Engineers like to code, they like to do features, they don't like to sit around waiting for things to be deployed and worrying about scaling up and out and down," says MacKay. "After a while the engineers became our champions. At training sessions, the development teams were always the ones saying, 'Kubernetes saved our time tremendously; it's an enabler; it really is incredible.' Over time, we were able to convince our management that this was a transition that the industry is making and that we needed to be a part of it."<br><br>
-  A year later, Ancestry has transitioned a good number of applications to Kubernetes. "We have many different services that make up the rich environment that [the website] has from both the DNA side and the family history side," says MacKay. "We have front-end stacks, back-end stacks and back-end processing type stacks that are in the cluster."<br><br>
-  The company continues to weigh which services it will move forward to Kubernetes, which ones will be kept as is, and which will be replaced in the future and thus don't have to be moved over. MacKay estimates that the company is "approaching halfway on those features that are going forward. We don't have to do a lot of convincing anymore. It's more of an issue of timing with getting product management and engineering staff the knowledge and information that they need."
-</div>
-</section>
-
-<div class="banner5">
-  <div class="banner5text">
-    "... 'I believe in Kubernetes. I believe in containerization. I think
-    if we can get there and establish ourselves in that world, we will be further along and far better off being agile and all the things we talk about,
-    and it'll&nbsp;go&nbsp;forward.'"
-  </div>
-</div>
-
-<section class="section5">
-<div class="fullcol">
-
-
-Looking ahead, MacKay sees Ancestry maximizing the benefits of Kubernetes in 2017. "We're very close to having everything that should be or could be in a Linux-friendly world in Kubernetes by the end of the year," he says, adding that he's looking forward to features such as federation and horizontal pod autoscaling that are currently in the works. "Kubernetes has been very wonderful for us and we continue to ride the wave."<br><br>
-That wave, he points out, has everything to do with the vibrant Kubernetes community, which has grown by leaps and bounds since Ancestry joined it as an early adopter. "This is just a very rough way of judging it, but on Slack in June 2015, there were maybe 500 on there," MacKay says. "The last time I looked there were maybe 8,500 just on the Slack channel. There are so many major companies and different kinds of companies involved now. It's the variety of contributors, the number of contributors, the incredibly competent and friendly community."<br><br>
-As much as he and his team at Ancestry have benefited from what he calls "the goodness and the technical abilities of many" in the community, they've also contributed information about best practices, logged bug issues and participated in the open source conversation. And they've been active in attending <a href="https://www.meetup.com/Utah-Kubernetes-Meetup/">meetups</a> to help educate and give back to the local tech community in Utah. Says MacKay: "We're trying to give back as far as our experience goes, rather than just code."
-<br><br>When he meets with companies considering adopting cloud native infrastructure, the best advice he has to give from Ancestry's Kubernetes journey is this: "Start small, but with hard problems," he says. And "you need a patron who understands the vision of containerization, to help you tackle the political as well as other technical roadblocks that can occur when change is needed."<br><br>
-With the changes that MacKay's team has led over the past year and a half, cloud native will be part of Ancestry's technological genealogy for years to come. MacKay has been such a champion of the technology that he says people have jokingly accused him of having a Kubernetes tattoo.<br><br>
-"I really don't," he says with a laugh. "But I'm passionate. I'm not exclusive to any technology; I use whatever I need that's out there that makes us great. If it's something else, I'll use it. But right now I believe in Kubernetes. I believe in containerization. I think if we can get there and establish ourselves in that world, we will be further along and far better off being agile and all the things we talk about, and it'll go forward."<br><br>
-He pauses. "So, yeah, I guess you can say I'm an evangelist for Kubernetes," he says. "But I'm not getting a tattoo!"
-
-
-</div>
-</section>

case-studies/box.html

@@ -1,111 +0,0 @@
----
-title: Box Case Study
-layout: basic
-case_study_styles: true
-cid: caseStudies
-css: /css/style_box.css
----
-
-<div class="banner1">
-  <h1>CASE STUDY: <img src="/images/box_logo.png" 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 of 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 of 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="https://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 too 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>

case-studies/buffer.html

@@ -1,112 +0,0 @@
----
-title: Buffer Case Study
-layout: basic
-case_study_styles: true
-cid: caseStudies
-css: /css/style_buffer.css
----
-
-<div class="banner1">
-  <h1>CASE STUDY: <img src="/images/buffer.png" width="18%" style="margin-bottom:-5px;margin-left:10px;"><br>
-  <div class="subhead">Making Deployments Easy for a Small, Distributed Team</div>
-</h1>
-</div>
-
-<div class="details">
-    Company&nbsp;<b>Buffer</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Location &nbsp;<b>Around the World</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Industry &nbsp;<b>Social Media Technology</b>
-</div>
-
-<hr>
-
-<section class="section1">
-  <div class="cols">
-    <div class="col1">
-
-    <h2>Challenge</h2>
-      With a small but fully distributed team of 80 working across almost a dozen time zones, Buffer—which offers social media management to agencies and marketers—was looking to solve its "classic monolithic code base problem," says Architect Dan Farrelly. "We wanted to have the kind of liquid infrastructure where a developer could create an app and deploy it and scale it horizontally as&nbsp;necessary."
-</div>
-
-<div class="col2">
-  <h2>Solution</h2>
-      Embracing containerization, Buffer moved its infrastructure from Amazon Web Services’ Elastic Beanstalk to Docker on AWS, orchestrated with&nbsp;Kubernetes.
-      <br>
-      <br>
-<h2>Impact</h2>
-      The new system "leveled up our ability with deployment and rolling out new changes," says Farrelly. "Building something on your computer and knowing that it’s going to work has shortened things up a lot. Our feedback cycles are a lot faster now&nbsp;too."
-    </div>
-</div>
-</section>
-
-<div class="banner2">
-  <div class="banner2text">
-    "It’s amazing that we can use the Kubernetes solution off the shelf with our team. And it just keeps getting better. Before we even know that we need something, it’s there in the next release or it’s coming in the next few months."<br><br><span style="font-size:16px;letter-spacing:2px;">- DAN FARRELLY, BUFFER ARCHITECT</span>
-  </div>
-</div>
-
-<section class="section2">
-<div class="fullcol">
-<h2>Dan Farrelly uses a carpentry analogy to explain the problem his company, <a href="https://buffer.com">Buffer</a>, began having as its team of developers grew over the past few years.</h2>
-
-    "If you’re building a table by yourself, it’s fine," the company’s architect says. "If you bring in a second person to work on the table, maybe that person can start sanding the legs while you’re sanding the top. But when you bring a third or fourth person in, someone should probably work on a different table." Needing to work on more and more different tables led Buffer on a path toward microservices and containerization made possible by Kubernetes.<br><br>
-    Since around 2012, Buffer had already been using <a href="https://aws.amazon.com/elasticbeanstalk/">Elastic Beanstalk</a>, the orchestration service for deploying infrastructure offered by <a href="https://aws.amazon.com">Amazon Web Services</a>. "We were deploying a single monolithic <a href="http://php.net/manual/en/intro-whatis.php">PHP</a> application, and it was the same application across five or six environments," says Farrelly. "We were very much a product-driven company. It was all about shipping new features quickly and getting things out the door, and if something was not broken, we didn’t spend too much time on it. If things were getting a little bit slow, we’d maybe use a faster server or just scale up one instance, and it would be good enough. We’d move on."<br><br>
-    But things came to a head in 2016. With the growing number of committers on staff, Farrelly and Buffer’s then-CTO, Sunil Sadasivan, decided it was time to re-architect and rethink their infrastructure. "It was a classic monolithic code base problem," says Farrelly.<br><br>Some of the company’s team was already successfully using <a href="https://www.docker.com">Docker</a> in their development environment, but the only application running on Docker in production was a marketing website that didn’t see real user traffic. They wanted to go further with Docker, and the next step was looking at options for&nbsp;orchestration.
-</div>
-</section>
-
-<div class="banner3">
-  <div class="banner3text">
-    And all the things Kubernetes did well suited Buffer’s needs. "We wanted to have the kind of liquid infrastructure where a developer could create an app and deploy it and scale it horizontally as necessary," says Farrelly. "We quickly used some scripts to set up a couple of test clusters, we built some small proof-of-concept applications in containers, and we deployed things within an hour. We had very little experience in running containers in production. It was amazing how quickly we could get a handle on it&nbsp;[Kubernetes]."
-  </div>
-</div>
-
-<section class="section3">
-<div class="fullcol">
-    First they considered <a href="https://mesosphere.com">Mesosphere</a>, <a href="https://dcos.io">DC/OS</a> and <a href="https://aws.amazon.com/ecs/">Amazon Elastic Container Service</a> (which their data systems team was already using for some data pipeline jobs). While they were impressed by these offerings, they ultimately went with Kubernetes. "We run on AWS still, so spinning up, creating services and creating load balancers on demand for us without having to configure them manually was a great way for our team to get into this," says Farrelly. "We didn’t need to figure out how to configure this or that, especially coming from a former Elastic Beanstalk environment that gave us an automatically-configured load balancer. I really liked Kubernetes’ controls of the command line. It just took care of ports. It was a lot more flexible. Kubernetes was designed for doing what it does, so it does it very well."<br><br>
-    And all the things Kubernetes did well suited Buffer’s needs. "We wanted to have the kind of liquid infrastructure where a developer could create an app and deploy it and scale it horizontally as necessary," says Farrelly. "We quickly used some scripts to set up a couple of test clusters, we built some small proof-of-concept applications in containers, and we deployed things within an hour. We had very little experience in running containers in production. It was amazing how quickly we could get a handle on it [Kubernetes]."<br><br>
-    Above all, it provided a powerful solution for one of the company’s most distinguishing characteristics: their remote team that’s spread across a dozen different time zones. "The people with deep knowledge of our infrastructure live in time zones different from our peak traffic time zones, and most of our product engineers live in other places," says Farrelly. "So we really wanted something where anybody could get a grasp of the system early on and utilize it, and not have to worry that the deploy engineer is asleep. Otherwise people would sit around for 12 to 24 hours for something. It’s been really cool to see people moving much faster."
-    <br><br>
-    With a relatively small engineering team—just 25 people, and only a handful working on infrastructure, with the majority front-end developers—Buffer needed "something robust for them to deploy whatever they wanted," says Farrelly. Before, "it was only a couple of people who knew how to set up everything in the old way. With this system, it was easy to review documentation and get something out extremely quickly. It lowers the bar for us to get everything in production. We don't have the big team to build all these tools or manage the infrastructure like other larger companies&nbsp;might."
-</div>
-</section>
-
-<div class="banner4">
-  <div class="banner4text">
-    "In our old way of working, the feedback loop was a lot longer, and it was delicate because if you deployed something, the risk was high to potentially break something else," Farrelly says. "With the kind of deploys that we built around Kubernetes, we were able to detect bugs and fix them, and get them deployed super fast. The second someone is fixing [a bug], it’s out the&nbsp;door."
-  </div>
-</div>
-
-<section class="section4">
-<div class="fullcol">
-    To help with this, Buffer developers wrote a deploy bot that wraps the Kubernetes deploy process and can be used by every team. "Before, our data analysts would update, say, a <a href="https://www.python.org">Python</a> analysis script and have to wait for the lead on that team to click the button and deploy it," Farrelly explains. "Now our data analysts can make a change, enter a <a href="https://slack.com">Slack</a> command, ‘/deploy,’ and it goes out instantly. They don’t need to wait on these slow turnaround times. They don’t even know where it’s running; it doesn’t matter."
-    <br><br>
-    One of the first applications the team built from scratch using Kubernetes was a new image resizing service. As a social media management tool that allows marketing teams to collaborate on posts and send updates across multiple social media profiles and networks, Buffer has to be able to resize photographs as needed to meet the varying limitations of size and format posed by different social networks. "We always had these hacked together solutions," says Farrelly.
-    <br><br>
-    To create this new service, one of the senior product engineers was assigned to learn Docker and Kubernetes, then build the service, test it, deploy it and monitor it—which he was able to do relatively quickly. "In our old way of working, the feedback loop was a lot longer, and it was delicate because if you deployed something, the risk was high to potentially break something else," Farrelly says. "With the kind of deploys that we built around Kubernetes, we were able to detect bugs and fix them, and get them deployed super fast. The second someone is fixing [a bug], it’s out the door."
-    <br><br>
-    Plus, unlike with their old system, they could scale things horizontally with one command. "As we rolled it out," Farrelly says, "we could anticipate and just click a button. This allowed us to deal with the demand that our users were placing on the system and easily scale it to handle it."
-    <br><br>
-    Another thing they weren’t able to do before was a canary deploy. This new capability "made us so much more confident in deploying big changes," says Farrelly. "Before, it took a lot of testing, which is still good, but it was also a lot of ‘fingers crossed.’ And this is something that gets run 800,000 times a day, the core of our business. If it doesn’t work, our business doesn’t work. In a Kubernetes world, I can do a canary deploy to test it for 1 percent and I can shut it down very quickly if it isn’t working. This has leveled up our ability to deploy and roll out new changes quickly while reducing&nbsp;risk."
-
-</div>
-</section>
-
-<div class="banner5">
-  <div class="banner5text">
-    "If you want to run containers in production, with nearly the power that Google uses internally, this [Kubernetes] is a great way to do that," Farrelly says. "We’re a relatively small team that’s actually running Kubernetes, and we’ve never run anything like it before. So it’s more approachable than you might think. That’s the one big thing that I tell people who are experimenting with it. Pick a couple of things, roll it out, kick the tires on this for a couple of months and see how much it can handle. You start learning a lot this&nbsp;way."
-  </div>
-</div>
-
-<section class="section5">
-<div class="fullcol">
-    By October 2016, 54 percent of Buffer’s traffic was going through their Kubernetes cluster. "There’s a lot of our legacy functionality that still runs alright, and those parts might move to Kubernetes or stay in our old setup forever," says Farrelly. But the company made the commitment at that time that going forward, "all new development, all new features, will be running on Kubernetes."
-    <br><br>
-    The plan for 2017 is to move all the legacy applications to a new Kubernetes cluster, and run everything they’ve pulled out of their old infrastructure, plus the new services they’re developing in Kubernetes, on another cluster. "I want to bring all the benefits that we’ve seen on our early services to everyone on the team," says Farrelly.
-    <br><br>
-    <h2>For Buffer’s engineers, it’s an exciting process. "Every time we’re deploying a new service, we need to figure out: OK, what’s the architecture? How do these services communicate? What’s the best way to build this service?" Farrelly says. "And then we use the different features that Kubernetes has to glue all the pieces together. It’s enabling us to experiment as we’re learning how to design a service-oriented architecture. Before, we just wouldn’t have been able to do it. This is actually giving us a blank white board so we can do whatever we want on it."
-    </h2>
-    Part of that blank slate is the flexibility that Kubernetes offers should the time come when Buffer may want or need to change its cloud. "It’s cloud agnostic so maybe one day we could switch to Google or somewhere else," Farrelly says. "We’re very deep in Amazon but it’s nice to know we could move away if we need to."
-    <br><br>
-    At this point, the team at Buffer can’t imagine running their infrastructure any other way—and they’re happy to spread the word. "If you want to run containers in production, with nearly the power that Google uses internally, this [Kubernetes] is a great way to do that," Farrelly says. "We’re a relatively small team that’s actually running Kubernetes, and we’ve never run anything like it before. So it’s more approachable than you might think. That’s the one big thing that I tell people who are experimenting with it. Pick a couple of things, roll it out, kick the tires on this for a couple of months and see how much it can handle. You start learning a lot this&nbsp;way."
-  <br><br>
-</div>
-</section>

case-studies/golfnow.html

@@ -1,125 +0,0 @@
----
-title: GolfNow Case Study
-layout: basic
-case_study_styles: true
-cid: caseStudies
-css: /css/style_golfnow.css
----
-
-<div class="banner1">
-  <h1>CASE STUDY: <img src="/images/golfnow_logo.png" 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>

case-studies/index.html

@@ -1,100 +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/peardeck.png" alt="peardeck">
-                  <p class="quote">"In terms of the cloud, Kubernetes and Prometheus have so much to offer."</p>
-                  <!--<p class="attrib">—  Riley Eynon-Lynch, CEO of Pear Deck</p>-->
-                  <a href="/case-studies/peardeck/">Read about Pear Deck</a>
-              </div>
-              <div class="case-study">
-                  <img src="/images/case_studies/buffer.png" alt="Buffer">
-                  <p class="quote">"It’s amazing that we can use the Kubernetes solution off the shelf with our team. And it just keeps getting better."</p>
-                  <!--<p class="attrib">—  Dan Farrelly, Buffer Architect</p>-->
-                  <a href="/case-studies/buffer/">Read about Buffer</a>
-              </div>
-              <div class="case-study">
-                  <img src="/images/case_studies/wink_logo.png" alt="Wink">
-                  <p class="quote">"What you get by adopting CoreOS/Kubernetes is portability, to not be locked in to anyone. You can really make your own fate."</p>
-                  <!--<p class="attrib">— Kit Klein, Head of Engineering at Wink</p>-->
-                  <a href="/case-studies/wink/">Read about Wink</a>
-              </div>
-              <div class="case-study">
-                  <img src="/images/case_studies/ancestry-logo.png" alt="Ancestry">
-                  <p class="quote">"Kubernetes saved our time tremendously; it’s an enabler. It really is incredible."</p>
-                  <!--<p class="attrib">— Paul MacKay, Software Engineer and Architect at Ancestry</p>-->
-                  <a href="/case-studies/ancestry/">Read about Ancestry.com</a>
-              </div>
-            </div>
-        </div>
-    </main>
-</section>
-
-<section id="video">
-    <main>
-        <!--<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>Box</h3>-->
-            <h4><i>"Kubernetes has the opportunity to be the new cloud platform. The amount of innovation that's going to come from being able to standardize on Kubernetes as a platform is incredibly exciting - more exciting than anything I've seen in the last 10 years of working on the cloud."</i></h4>
-            <img src="/images/case_studies/box-small.png" id="boxlogo" alt="Box">
-        </div>
-        <div style= "padding-left: 40px;"><button onclick="kub.showVideo()"><img src="/images/case_studies/Video-Clip-Box.png" alt="Box video"><h6>Kubernetes at Box</h6></button></div>
-    </main>
-</section>
-
-<section id="users">
-    <main>
-        <h3>Kubernetes Users</h3>
-        <div id="usersGrid">
-          <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="/case-studies/ancestry/"><img src="/images/case_studies/ancestry.png" alt="Ancestry.com"></a>
-          <a target="_blank" href="/case-studies/box/"><img src="/images/case_studies/box_logo.png" alt="box"></a>
-          <a target="_blank" href="/case-studies/buffer/"><img src="/images/case_studies/buffer_logo.png" alt="Buffer"></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://youtu.be/lmeFkH-rHII"><img src="/images/case_studies/comcast_logo.png" alt="Comcast"></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/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="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="/case-studies/golfnow/"><img src="/images/case_studies/golfnow_logo.png" alt="GolfNow"></a>
-          <a target="_blank" href="http://blog.kubernetes.io/2017/02/inside-jd-com-shift-to-kubernetes-from-openstack.html"><img src="/images/case_studies/jd.png" alt="JD.COM"></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://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="/case-studies/peardeck/"><img src="/images/case_studies/peardeck_logo.png" alt="peardeck"></a>
-          <a href="/case-studies/pearson/"><img src="/images/case_studies/pearson_logo.png" alt="Pearson"></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://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://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="https://youtu.be/4gyeixJLabo"><img src="/images/case_studies/sap.png" alt="SAP"></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://thenewstack.io/wepay-kubernetes-changed-business/"><img src="/images/case_studies/wepay.png" alt="WePay"></a>
-          <a target="_blank" href="/case-studies/wink/"><img src="/images/case_studies/wink.png" alt="Wink"></a>
-          <a href="/case-studies/wikimedia/"><img src="/images/case_studies/wikimedia_logo.png" alt="Wikimedia"></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="#" onclick="event.preventDefault(); kub.showVideo()"><img src="/images/case_studies/zulily_logo.png" alt="zulily"></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=of45hYbkIZs" frameborder="0" allowfullscreen></iframe>-->
-    <iframe data-url="https://www.youtube.com/embed/of45hYbkIZs?autoplay=1" frameborder="0" allowfullscreen="true"></iframe>
-    <button id="closeButton"></button>
-</div>

case-studies/peardeck.html

@@ -1,111 +0,0 @@
----
-title: Pear Deck Case Study
-layout: basic
-case_study_styles: true
-cid: caseStudies
-css: /css/style_peardeck.css
----
-
-<div class="banner1">
-  <h1> CASE STUDY:<img src="/images/peardeck_logo.png"  width="22%" style="margin-bottom:-0px"><br> <div class="subhead">Infrastructure for a Growing EdTech Startup</div></h1>
-
-</div>
-
-<div class="details">
-    Company &nbsp;<b>Pear Deck</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Location &nbsp;<b>Iowa City, Iowa</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Industry &nbsp;<b>Educational Software</b>
-</div>
-
-<hr>
-
-<section class="section1">
-<div class="cols">
-  <div class="col1">
-    <h2>Challenge</h2>
-      The three-year-old startup provides a web app for teachers to interact with their students in the classroom. The JavaScript  app was built on Google’s web app development platform <a href="https://firebase.google.com/">Firebase</a>, using <a href="https://www.heroku.com/">Heroku</a>. As the user base steadily grew, so did the development team. "We outgrew Heroku when we started wanting to have multiple services, and the deploying story got pretty horrendous. We were frustrated that we couldn’t have the developers quickly stage a version," says CEO Riley Eynon-Lynch. "Tracing and monitoring became basically impossible." On top of that, many of Pear Deck’s customers are behind government firewalls and connect through Firebase, not Pear Deck’s servers, making troubleshooting even more difficult.
-</div>
-
-<div class="col2">
-  <h2>Solution</h2>
-    In 2016, the company began moving their code from Heroku to <a href="https://www.docker.com/">Docker</a> containers running on <a href="https://cloud.google.com/container-engine/">Google Container Engine</a>, orchestrated by <a href="http://kubernetes.io/">Kubernetes</a> and monitored with <a href="https://prometheus.io/">Prometheus</a>.
-    <br>
-    <br>
-<h2>Impact</h2>
-      The new cloud native stack immediately improved the development workflow, speeding up deployments. Prometheus gave Pear Deck "a lot of confidence, knowing that people are still logging into the app and using it all the time," says Eynon-Lynch. "The biggest impact is being able to work as a team on the configuration in git in a pull request, and the biggest confidence comes from the solidity of the abstractions and the trust that we have in Kubernetes actually making our yaml files a reality."
-</div>
-</div>
-</section>
-
-<div class="banner2">
-  <div class="banner2text">
-    "We didn’t even realize how stressed out we were about our lack of insight into what was happening with the app. I’m really excited and have more and more confidence in the actual state of our application for our actual users, and not just what the CPU graphs are saying, because of Prometheus and Kubernetes."<br><br><span style="font-size:16px;letter-spacing:2px;">– RILEY EYNON-LYNCH, CEO OF PEAR DECK</span>
-  </div>
-</div>
-
-<section class="section2">
-<div class="fullcol">
-<h2>With the speed befitting a startup, Pear Deck delivered its first prototype to customers within three months of incorporating.</h2>
-As a former high school math teacher, CEO Riley Eynon-Lynch felt an urgency to provide a tech solution to classes where instructors struggle to interact with every student in a short amount of time. "Pear Deck is an app that students can use to interact with the teacher all at once," he says. "When the teacher asks a question, instead of just the kid at the front of the room answering again, everybody can answer every single question. It’s a huge fundamental shift in the messaging to the students about how much we care about them and how much they are a part of the classroom."<br><br>
-Eynon-Lynch and his partners quickly built a JavaScript web app on Google’s web app development platform <a href="https://firebase.google.com/">Firebase</a>, and launched the minimum viable product [MVP] on <a href="https://www.heroku.com/">Heroku</a> "because it was fast and easy," he says. "We made everything as easy as we could."
-<br><br>
-But once it launched, the user base began growing steadily at a rate of 30 percent a month. "Our Heroku bill was getting totally insane," Eynon-Lynch says. But even more crucially, as the company hired more developers to keep pace, "we outgrew Heroku. We wanted to have multiple services and the deploying story got pretty horrendous. We were frustrated that we couldn’t have the developers quickly stage a version. Tracing and monitoring became basically impossible."
-<br><br>
-On top of that, many of Pear Deck’s customers are behind government firewalls and connect through Firebase, not Pear Deck’s servers, making troubleshooting even more difficult.
-<br><br>
-The team began looking around for another solution, and finally decided in early 2016 to start moving the app from Heroku to <a href="https://www.docker.com/">Docker</a> containers running on <a href="https://cloud.google.com/container-engine/">Google Container Engine</a>, orchestrated by <a href="http://kubernetes.io/">Kubernetes</a> and monitored with <a href="https://prometheus.io/">Prometheus</a>.
-</div>
-</section>
-
-<div class="banner3">
-  <div class="banner3text">
-    "When it became clear that Google Container Engine was going to have a lot of support from Google and be a fully-managed Kubernetes platform, it seemed very obvious to us that was the way to go," says Eynon-Lynch.
-  </div>
-</div>
-
-<section class="section3">
-<div class="fullcol">
-  They had considered other options like Google’s App Engine (which they were already using for one service) and Amazon’s <a href="https://aws.amazon.com/ec2/">Elastic Compute Cloud</a> (EC2), while experimenting with running one small service that wasn’t accessible to the Internet in Kubernetes. "When it became clear that Google Container Engine was going to have a lot of support from Google and be a fully-managed Kubernetes platform, it seemed very obvious to us that was the way to go," says Eynon-Lynch. "We didn’t really consider Terraform and the other competitors because the abstractions offered by Kubernetes just jumped off the page to us."<br><br>
-  Once the team started porting its Heroku apps into Kubernetes, which was "super easy," he says, the impact was immediate. "Before, to make a new version of the app meant going to Heroku and reconfiguring 10 new services, so basically no one was willing to do it, and we never   staged things," he says. "Now we can deploy our exact same configuration in lots of different clusters in 30 seconds. We have a full set up that’s always running, and then any of our developers or designers can stage new versions with one command, including their recent changes. We stage all the time now, and everyone stopped talking about how cool it is because it’s become invisible how great it is."
-  <br><br>
-  Along with Kubernetes came Prometheus. "Until pretty recently we didn’t have any kind of visibility into aggregate server metrics or performance," says Eynon-Lynch. The team had tried to use GKE’s <a href="https://cloud.google.com/stackdriver/">Stackdriver</a> monitoring, but had problems making it work, and considered <a href="https://newrelic.com/">New Relic</a>. When they started looking at Prometheus in the fall of 2016, "the fit between the abstractions in Prometheus and the way we think about how our system works, was so clear and obvious," he says.<br><br>
-  The integration with Kubernetes made set-up easy. Once Helm installed Prometheus, "We started getting a graph of the health of all our Kubernetes nodes and pods immediately. I think we were pretty hooked at that point," Eynon-Lynch says. "Then we got our own custom instrumentation working in 15 minutes, and had an actively updated count of requests that we could do, rate on and get a sense of how many users are connected at a given point. And then it was another hour before we had alarms automatically showing up in our Slack channel. All that was in one afternoon. And it was an afternoon of gasping with delight, basically!"
-</div>
-</section>
-
-<div class="banner4">
-  <div class="banner4text">
-    "We started getting a graph of the health of all our Kubernetes nodes and pods immediately. I think we were pretty hooked at that point," Eynon-Lynch says. "Then we got our own custom instrumentation working in 15 minutes, and had an actively updated count of requests that we could do, rate on and get a sense of how many users are connected at a given point. And then it was another hour before we had alarms automatically showing up in our Slack channel. All that was in one afternoon. And it was an afternoon of gasping with delight, basically!"
-  </div>
-</div>
-
-<section class="section4">
-<div class="fullcol">
-  With Pear Deck’s specific challenges—traffic through Firebase as well as government firewalls—Prometheus was a game-changer. "We didn’t even realize how stressed out we were about our lack of insight into what was happening with the app," Eynon-Lynch says. Before, when a customer would report that the app wasn’t working, the team had to manually investigate the problem without knowing whether customers were affected all over the world, or whether Firebase was down, and where.<br><br>
-  To help solve that problem, the team wrote a script that pings Firebase from several different geographical locations, and then reports the responses to Prometheus in a histogram. "A huge impact that Prometheus had on us was just an amazing sigh of relief, of feeling like we knew what was happening," he says. "It took 45 minutes to implement [the Firebase alarm] because we knew that we had this trustworthy metrics platform in Prometheus. We weren’t going to have to figure out, ‘Where do we send these metrics? How do we aggregate the metrics? How do we understand them?’"<br><br>
-  Plus, Prometheus has allowed Pear Deck to build alarms for business goals. One measures the rate of successful app loads and goes off if the day’s loads are less than 90 percent of the loads from seven days before. "We run a JavaScript app behind ridiculous firewalls and all kinds of crazy browser extensions messing with it—Chrome will push a feature that breaks some CSS that we’re using," Eynon-Lynch says. "So that gives us a lot of confidence, and we at least know that people are still logging into the app and using it all the time."<br><br>
-  Now, when a customer complains, and none of the alarms have gone off, the team can feel confident that it’s not a widespread problem. "Just to be sure, we can go and double check the graphs and say, ‘Yep, there’s currently 10,000 people connected to that Firebase node. It’s definitely working. Let’s investigate your network settings, customer,’" he says. "And we can pass that back off to our support reps instead of the whole development team freaking out that Firebase is down."<br><br>
-  Pear Deck is also giving back to the community, building and open-sourcing a <a href="https://github.com/peardeck/prometheus-user-metrics">metrics aggregator</a> that enables end-user monitoring in Prometheus. "We can measure, for example, the time to interactive-dom on the web clients," he says. "The users all report that to our aggregator, then the aggregator reports to Prometheus. So we can set an alarm for some client side errors."<br><br>
-  Most of Pear Deck’s services have now been moved onto Kubernetes. And all of the team’s new code is going on Kubernetes. "Kubernetes lets us experiment with service configurations and stage them on a staging cluster all at once, and test different scenarios and talk about them as a development team looking at code, not just talking about the steps we would eventually take as humans," says Eynon-Lynch.
-</div>
-</section>
-
-<div class="banner5">
-  <div class="banner5text">
-    "A huge impact that Prometheus had on us was just an amazing sigh of relief, of feeling like we knew what was happening. It took 45 minutes to implement [the Firebase alarm] because we knew that we had this trustworthy metrics platform in Prometheus...in terms of the cloud, Kubernetes and Prometheus have so much to offer," he says.
-  </div>
-</div>
-
-<section class="section5">
-<div class="fullcol">
-  Looking ahead, the team is planning to explore autoscaling on Kubernetes. With users all over the world but mostly in the United States, there are peaks and valleys in the traffic. One service that’s still on App Engine can get as many as 10,000 requests a second during the day but far less at night. "We pay for the same servers at night, so I understand there’s autoscaling that we can be taking advantage of," he says. "Implementing it is a big worry, exposing the rest of our Kubernetes cluster to us and maybe messing that up. But it’s definitely our intention to move everything over, because now none of the developers want to work on that app anymore because it’s such a pain to deploy it."
-<br><br>
-They’re also eager to explore the work that Kubernetes is doing with stateful sets. "Right now all of the services we run in Kubernetes are stateless, and Google basically runs our databases for us and manages backups," Eynon-Lynch says. "But we’re interested in building our own web-socket solution that doesn’t have to be super stateful but will have maybe an hour’s worth of state on it."
-<br><br>
-That project will also involve Prometheus, for a dark launch of web socket connections. "We don’t know how reliable web socket connections behind all these horrible firewalls will be to our servers," he says. "We don’t know what work Firebase has done to make them more reliable. So I’m really looking forward to trying to get persistent connections with web sockets to our clients and have optional tools to understand if it’s working. That’s our next new adventure, into stateful servers."
-<br><br>
-As for Prometheus, Eynon-Lynch thinks the company has only gotten started. "We haven’t instrumented all our important features, especially those that depend on third parties," he says. "We have to wait for those third parties to tell us they’re down, which sometimes they don’t do for a long time. So I’m really excited and have more and more confidence in the actual state of our application for our actual users, and not just what the CPU graphs are saying, because of Prometheus and Kubernetes."
-<br><br>
-For a spry startup that’s continuing to grow rapidly—and yes, they’re <a href="https://www.peardeck.com/careers/">hiring</a>!—Pear Deck is notably satisfied with how its infrastructure has evolved in the cloud native ecosystem. "Usually I have some angsty thing where I want to get to the new, better technology," says Eynon-Lynch, "but in terms of the cloud, Kubernetes and Prometheus have so much to offer."
-
-  <br><br>
-</div>
-</section>

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>

case-studies/wink.html

@@ -1,109 +0,0 @@
----
-title: Wink Case Study
-layout: basic
-case_study_styles: true
-cid: caseStudies
-css: /css/style_wink.css
----
-
-<div class="banner1">
-  <h1>CASE STUDY: <img src="/images/wink_logo.png" width="13%" style="margin-bottom:-4px"><br>
-    <div class="subhead">Cloud-Native Infrastructure Keeps Your Smart Home Connected</div>
-  </h1>
-</div>
-
-
-<div class="details">
-    Company &nbsp;<b>Wink</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Location &nbsp;<b>New York, N.Y.</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Industry &nbsp;<b>Internet of Things Platform</b>
-</div>
-
-<hr>
-
-<section class="section1">
-<div class="cols">
-  <div class="col1">
-
-      <h2>Challenge</h2>
-        Building a low-latency, highly reliable infrastructure to serve communications between millions of connected smart-home devices and the company’s consumer hubs and mobile app, with an emphasis on horizontal scalability, the ability to encrypt everything quickly and connections that could be easily brought back up if anything went wrong.
-        <br><br>
-      <h2>Solution</h2>
-        Across-the-board use of a Kubernetes-Docker-CoreOS Container Linux stack.<br><br>
-  </div>
-
-  <div class="col2">
-    <h2>Impact</h2>
-      "Two of the biggest American retailers [Home Depot and Walmart] are carrying and promoting the brand and the hardware,” Wink Head of Engineering Kit Klein says proudly – though he adds that "it really comes with a lot of pressure. It’s not a retail situation where you have a lot of tech enthusiasts. These are everyday people who want something that works and have no tolerance for technical excuses.” And that’s further testament to how much faith Klein has in the infrastructure that the Wink team has built. With 80 percent of Wink’s workload running on a unified stack of Kubernetes-Docker-CoreOS, the company has put itself in a position to continually innovate and improve its products and services. Committing to this technology, says Klein, "makes building on top of the infrastructure relatively&nbsp;easy.”
-  </div>
-
-</div>
-</section>
-
-
-<div class="banner2">
-  <div class="banner2text">
-      "It’s not proprietary, it’s totally open, it’s really portable. You can run all the workloads across different cloud providers. You can easily run a hybrid AWS or even bring in your own data center. That’s the benefit of having everything unified on one  open source Kubernetes-Docker-CoreOS Container Linux stack. There are massive security benefits if you only have one Linux distro/machine image to validate. The benefits are enormous because you save money, and you save time.”<br><br><span style="font-size:15px;letter-spacing:0.08em">- KIT KLEIN, HEAD OF ENGINEERING, WINK</span>
-  </div>
-</div>
-
-
-<section class="section2">
-  <div class="fullcol">
-      <h2>How many people does it take to turn on a light bulb?</h2>
-
-      Kit Klein whips out his phone to demonstrate. With a few swipes, the head of engineering at Wink pulls up the smart-home app created by the New York City-based company and taps the light button. "Honestly when you’re holding the phone and you’re hitting the light,” he says, "by the time you feel the pressure of your finger on the screen, it’s on. It takes as long as the signal to travel to your brain.”<br><br>
-      Sure, it takes just one finger and less than 200 milliseconds to turn on the light – or lock a door or change a thermostat. But what allows Wink to help consumers manage their connected smart-home products with such speed and ease is a sophisticated, cloud native infrastructure that Klein and his team built and continue to develop using a unified stack of CoreOS, the open-source operating system designed for clustered deployments, and Kubernetes, an open-source platform for automating deployment, scaling, and operations of application containers across clusters of hosts, providing container-centric infrastructure. "When you have a big, complex network of interdependent microservices that need to be able to discover each other, and need to be horizontally scalable and tolerant to failure, that’s what this is really optimized for,” says Klein. "A lot of people end up relying on proprietary services [offered by some big cloud providers] to do some of this stuff, but what you get by adopting CoreOS/Kubernetes is portability, to not be locked in to anyone. You can really make your own fate.”<br><br>
-      Indeed, Wink did. The company’s mission statement is to make the connected home accessible – that is, user-friendly for non-technical owners, affordable and perhaps most importantly, reliable. "If you can’t trust that when you hit the switch, you know a light is going to go on, or if you’re remote and you’re checking on your house and that information isn’t accurate, then the convenience of the system is lost,” says Klein. "So that’s where the infrastructure comes in.”<br><br>
-      Wink was incubated within Quirky, a company that developed crowd-sourced inventions. The Wink app was first introduced in 2013, and at the time, it controlled only a few consumer products such as the PivotPower Strip that Quirky produced in collaboration with GE. As smart-home products proliferated, Wink was launched in 2014 in Home Depot stores nationwide. Its first project: a hub that could integrate with smart products from about a dozen brands like Honeywell and Chamberlain. The biggest challenge would be to build the infrastructure to serve all those communications between the hub and the products, with a focus on maximizing reliability and minimizing latency.<br><br>
-      "When we originally started out, we were moving very fast trying to get the first product to market, the minimum viable product,” says Klein. "Lots of times you go down a path and end up having to backtrack and try different things. But in this particular case, we did a lot of the work up front, which led to us making a really sound decision to deploy it on CoreOS Container Linux. And that was very early in the life of it.”
-
-  </div>
-</section>
-
-<div class="banner3">
-  <div class="banner3text">
-    "...what you get by adopting CoreOS/Kubernetes is portability, to not be locked in to anyone. You can really make your own fate.”
-  </div>
-</div>
-
-<section class="section3">
-  <div class="fullcol">
-    Concern number one: Wink’s products need to connect to consumer devices in people’s homes, behind a firewall. "You don’t have an end point like a URL, and you don’t even know what ports are open behind that firewall,” Klein explains. "So you essentially need to have this thing wake up and talk to your system and then open real-time, bidirectional communication between the cloud and the device. And it’s really, really important that it’s persistent because you want to decrease as much as possible the overhead of sending a message – you never know when someone is going to turn on the lights.”<br><br>
-    With the earliest version of the Wink Hub, when you decided to turn your lights on or off, the request would be sent to the cloud and then executed. Subsequent updates to Wink’s software enabled local control, cutting latency down to about 10 milliseconds for many devices. But with the need for cloud-enabled integrations of an ever-growing ecosystem of smart home products, low-latency internet connectivity is still a critical consideration.
-    <br><br>
-    <h2>"You essentially need to have this thing wake up and talk to your system and then open real-time, bidirectional communication between the cloud and the device. And it’s really, really important that it’s persistent...you never know when someone is going to turn on the&nbsp;lights.”</h2>
-    In addition, Wink had other requirements: horizontal scalability, the ability to encrypt everything quickly, connections that could be easily brought back up if something went wrong. "Looking at this whole structure we started, we decided to make a secure socket-based service,” says Klein. "We’ve always used, I would say, some sort of clustering technology to deploy our services and so the decision we came to was, this thing is going to be containerized, running on Docker.”<br><br>
-    At the time – just over two years ago – Docker wasn’t yet widely used, but as Klein points out, "it was certainly understood by the people who were on the frontier of technology. We started looking at potential technologies that existed. One of the limiting factors was that we needed to deploy multi-port non-http/https services. It wasn’t really appropriate for some of the early cluster technology. We liked the project a lot and we ended up using it on other stuff for a while, but initially it was too targeted toward http workloads.”<br><br>
-    Once Wink’s backend engineering team decided on a Dockerized workload, they had to make decisions about the OS and the container orchestration platform. "Obviously you can’t just start the containers and hope everything goes well,” Klein says with a laugh. "You need to have a system that is helpful [in order] to manage where the workloads are being distributed out to. And when the container inevitably dies or something like that, to restart it, you have a load balancer. All sorts of housekeeping work is needed to have a robust infrastructure.”
-
-  </div>
-</section>
-
-  <div class="banner4">
-    <div class="banner4text">
-    "Obviously you can’t just start the containers and hope everything goes well,” Klein says with a laugh. "You need to have a system that is helpful [in order] to manage where the workloads are being distributed out to. And when the container inevitably dies or something like that, to restart it, you have a load balancer. All sorts of housekeeping work is needed to have a robust infrastructure.”
-    </div>
-  </div>
-
-<section class="section4">
-  <div class="fullcol">
-    Wink considered building directly on a general purpose Linux distro like Ubuntu (which would have required installing tools to run a containerized workload) and cluster management systems like Mesos (which was targeted toward enterprises with larger teams/workloads), but ultimately set their sights on CoreOS Container Linux. "A container-optimized Linux distribution system was exactly what we needed,” he says. "We didn’t have to futz around with trying to take something like a Linux distro and install everything. It’s got a built-in container orchestration system, which is Fleet, and an easy-to-use API. It’s not as feature-rich as some of the heavier solutions, but we realized that, at that moment, it was exactly what we needed.”<br><br>
-    Wink’s hub (along with a revamped app) was introduced in July 2014 with a short-term deployment, and within the first month, they had moved the service to the Dockerized CoreOS deployment. Since then, they’ve moved almost every other piece of their infrastructure – from third-party cloud-to-cloud integrations to their customer service and payment portals – onto CoreOS Container Linux clusters. <br><br>
-    Using this setup did require some customization. "Fleet is really nice as a basic container orchestration system, but it doesn’t take care of routing, sharing configurations, secrets, et cetera, among instances of a service,” Klein says. "All of those layers of functionality can be implemented, of course, but if you don’t want to spend a lot of time writing unit files manually – which of course nobody does – you need to create a tool to automate some of that, which we did.”<br><br>
-    Wink quickly embraced the Kubernetes container cluster manager when it was launched in 2015 and integrated with CoreOS core technology, and as promised, it ended up providing the features Wink wanted and had planned to build. "If not for Kubernetes, we likely would have taken the logic and library we implemented for the automation tool that we created, and would have used it in a higher level abstraction and tool that could be used by non-DevOps engineers from the command line to create and manage clusters,” Klein says. "But Kubernetes made that totally unnecessary – and is written and maintained by people with a lot more experience in cluster management than us, so all the better.” Now, an estimated 80 percent of Wink’s workload is run on Kubernetes on top of CoreOS Container Linux.
-
-  </div>
-</section>
-
-  <div class="banner5">
-    <div class="banner5text">
-      "Stay close to the development. Understand why decisions are being made. If you understand the intent behind the project, from the technological intent to a certain philosophical intent, then it helps you understand how to build your system in harmony with those systems as opposed to trying to work against it.”
-    </div>
-  </div>
-
-<section class="section5">
-  <div class="fullcol">
-    Wink’s reasons for going all in are clear: "It’s not proprietary, it’s totally open, it’s really portable,” Klein says. "You can run all the workloads across different cloud providers. You can easily run a hybrid AWS or even bring in your own data center. That’s the benefit of having everything unified on one Kubernetes-Docker-CoreOS Container Linux stack. There are massive security benefits if you only have one Linux distro to try to validate. The benefits are enormous because you save money, you save time.”<br><br>
-    Klein concedes that there are tradeoffs in every technology decision. "Cutting-edge technology is going to be scary for some people,” he says. "In order to take advantage of this, you really have to keep up with the technology. You can’t treat it like it’s a black box. Stay close to the development. Understand why decisions are being made. If you understand the intent behind the project, from the technological intent to a certain philosophical intent, then it helps you understand how to build your system in harmony with those systems as opposed to trying to work against it.”<br><br>
-    Wink, which was acquired by Flex in 2015, now controls 2.3 million connected devices in households all over the country. What’s next for the company? A new version of the hub - Wink Hub 2 - hit shelves last November – and is being offered for the first time at Walmart stores in addition to Home Depot. "Two of the biggest American retailers are carrying and promoting the brand and the hardware,” Klein says proudly – though he adds that "it really comes with a lot of pressure. It’s not a retail situation where you have a lot of tech enthusiasts. These are everyday people who want something that works and have no tolerance for technical excuses.” And that’s further testament to how much faith Klein has in the infrastructure that the Wink team has have built.<br><br>
-    Wink’s engineering team has grown exponentially since its early days, and behind the scenes, Klein is most excited about the machine learning Wink is using. "We built [a system of] containerized small sections of the data pipeline that feed each other and can have multiple outputs,” he says. "It’s like data pipelines as microservices.” Again, Klein points to having a unified stack running on CoreOS Container Linux and Kubernetes as the primary driver for the innovations to come. "You’re not reinventing the wheel every time,” he says. "You can just get down to work.”  </div>
-</section>

cn/README.md

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

cn/_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 %}
-
-## 开始下一步
-
-{{ whatsnext }}
-
-{% endif %}
-

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

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

cn/docs/admin/authorization/abac.md

@@ -1,141 +0,0 @@
----
-assignees:
-- erictune
-- lavalamp
-- deads2k
-- liggitt
-title: ABAC 模式
----
-
-{% capture overview %}
-
-基于属性的访问控制（Attribute-based access control - ABAC）定义了访问控制范例，其中通过使用将属性组合在一起的策略来向用户授予访问权限。
-
-{% endcapture %}
-
-{% capture body %}
-
-## 策略文件格式
-
-基于 `ABAC` 模式，可以这样指定策略文件 `--authorization-policy-file=SOME_FILENAME`。
-
-此文件是 JSON 格式[每行都是一个JSON对象](http://jsonlines.org/)，不应存在封闭的列表或映射，每行只有一个映射。
-
-每一行都是一个 "策略对象"，策略对象是具有以下映射的属性:
-
-  - 版本控制属性:
-    - `apiVersion`，字符串类型: 有效值为"abac.authorization.kubernetes.io/v1beta1"，允许版本控制和转换策略格式。
-    - `kind`，字符串类型: 有效值为 "Policy"，允许版本控制和转换策略格式。
-  - `spec` 配置为具有以下映射的属性:
-    - 匹配属性:
-      - `user`，字符串类型; 来自 `--token-auth-file` 的用户字符串，如果你指定`user`，它必须与验证用户的用户名匹配。
-      - `group`，字符串类型; 如果指定`group`，它必须与经过身份验证的用户的一个组匹配，`system:authenticated`匹配所有经过身份验证的请求。`system:unauthenticated`匹配所有未经过身份验证的请求。
-  - 资源匹配属性:
-    - `apiGroup`，字符串类型; 一个 API 组。
-      - 例: `extensions`
-      - 通配符: `*`匹配所有 API 组。
-    - `namespace`，字符串类型; 一个命名空间。
-      - 例如: `kube-system`
-      - 通配符: `*` 匹配所有资源请求。
-    - `resource`，字符串类型; 资源类型。
-      - 例:`pods`
-      - 通配符: `*`匹配所有资源请求。
-  - 非资源匹配属性:
-    - `nonResourcePath`，字符串类型; 非资源请求路径。
-      - 例如:`/version`或`/apis`
-      - 通配符:
-        - `*` 匹配所有非资源请求。
-        - `/foo/*` 匹配`/foo/`的所有子路径。
-  - `readonly`，键入 boolean，如果为 true，则表示该策略仅适用于 get，list 和 watch 操作。
-
-**注意:** 未设置的属性与类型设置为零值的属性相同(例如空字符串，0、false)，然而未知的应该可读性优先。
-
-在将来，策略可能以 JSON 格式表示，并通过 REST 界面进行管理。
-
-## 授权算法
-
-请求具有与策略对象的属性对应的属性。
-
-当接收到请求时，确定属性。 未知属性设置为其类型的零值（例如: 空字符串，0，false）。
-
-设置为`“*"`的属性将匹配相应属性的任何值。
-
-检查属性的元组，以匹配策略文件中的每个策略。 如果至少有一行匹配请求属性，则请求被授权（但可能会在稍后验证失败）。
-
-要允许任何经过身份验证的用户执行某些操作，请将策略组属性设置为 `"system:authenticated“`。
-
-要允许任何未经身份验证的用户执行某些操作，请将策略组属性设置为`"system:authentication“`。
-
-要允许用户执行任何操作，请使用 apiGroup，命名空间，
-资源和 nonResourcePath 属性设置为 `“*"`的策略.
-
-要允许用户执行任何操作，请使用设置为`“*”` 的 apiGroup，namespace，resource 和 nonResourcePath 属性编写策略。
-
-## Kubectl
-
-Kubectl 使用 api-server 的 `/api` 和 `/apis` 端点进行协商客户端/服务器版本。 通过创建/更新来验证发送到API的对象操作，kubectl 查询某些 swagger 资源。 对于API版本"v1", 那就是`/swaggerapi/api/v1` ＆ `/swaggerapi/ experimental/v1`。
-
-当使用 ABAC 授权时，这些特殊资源必须明确通过策略中的 `nonResourcePath` 属性暴露出来(参见下面的[例子](#examples)):
-
-* `/api`，`/api/*`，`/apis`和`/apis/*` 用于 API 版本协商.
-* `/version` 通过 `kubectl version` 检索服务器版本.
-* `/swaggerapi/*` 用于创建/更新操作.
-
-要检查涉及到特定kubectl操作的HTTP调用，您可以调整详细程度：
-
-    kubectl --v=8 version
-
-## 例子
-
-1. Alice 可以对所有资源做任何事情:
-
-    ```json
-    {"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"user": "alice", "namespace": "*", "resource": "*", "apiGroup": "*"}}
-    ```
-2. Kubelet 可以读取任何pod:
-
-    ```json
-    {"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"user": "kubelet", "namespace": "*", "resource": "pods", "readonly": true}}
-    ```
-3. Kubelet 可以读写事件:
-
-    ```json
-    {"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"user": "kubelet", "namespace": "*", "resource": "events"}}
-    ```
-4. Bob 可以在命名空间“projectCaribou"中读取 pod:
-
-    ```json
-    {"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"user": "bob", "namespace": "projectCaribou", "resource": "pods", "readonly": true}}
-    ```
-5. 任何人都可以对所有非资源路径进行只读请求:
-
-    ```json
-    {"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"group": "system:authenticated", "readonly": true, "nonResourcePath": "*"}}
-    {"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"group": "system:unauthenticated", "readonly": true, "nonResourcePath": "*"}}
-    ```
-
-[完整文件示例](http://releases.k8s.io/{{page.githubbranch}}/pkg/auth/authorizer/abac/example_policy_file.jsonl)
-
-## 服务帐户的快速说明
-
-服务帐户自动生成用户。 用户名是根据命名约定生成的:
-
-```shell
-system:serviceaccount:<namespace>:<serviceaccountname>
-```
-创建新的命名空间也会导致创建一个新的服务帐户：
-
-```shell
-system:serviceaccount:<namespace>:default
-```
-
-例如，如果要将 API 的 kube-system 完整权限中的默认服务帐户授予，则可以将此行添加到策略文件中:
-
-```json
-{"apiVersion":"abac.authorization.kubernetes.io/v1beta1","kind":"Policy","spec":{"user":"system:serviceaccount:kube-system:default","namespace":"*","resource":"*","apiGroup":"*"}}
-```
-
-需要重新启动 apitorver 以获取新的策略行.
-
-{% endcapture %}
-{% include templates/concept.md %}

cn/docs/admin/authorization/index.md

@@ -1,155 +0,0 @@
----
-assignees:
-- erictune
-- lavalamp
-- deads2k
-- liggitt
-title: 概述
----
-
-{% capture overview %}
-
-学习有关 Kubernetes 授权的更多信息，包括有关使用支持的授权模块创建策略的详细信息。
-
-{% endcapture %}
-
-{% capture body %}
-
-在 Kubernetes 里，您必须经过身份验证(登录)，才能授权您的请求(授予访问权限).。有关认证的信息，请参阅[访问控制概述](/docs/admin/access-the-api/)。
-
-Kubernetes 提供通用的 REST API 请求。这意味着 Kubernetes 授权可以与现有的组织或云提供商的访问控制系统一起使用，该系统可以处理除 Kubernetes API 之外的其他 API。
-
-## 确定请求是允许还是被拒绝
-Kubernetes 使用 API​​ 服务器授权 API 请求。它根据所有策略评估所有请求属性，并允许或拒绝请求。某些策略必须允许 API 请求的所有部分继续进行，这意味着默认情况下是拒绝权限。
-
-(虽然 Kubernetes 使用 API ​​服务器，访问控制和依赖特定类型对象的特定领域策略由 Admission 控制器处理。)
-
-当配置多个授权模块时，按顺序检查每个模块，如果有任何模块授权请求，则可以继续执行该请求。如果所有模块拒绝请求，则拒绝该请求(HTTP状态代码403)。
-
-## 查看您的请求属性
-
-Kubernetes 仅查看以下API请求属性:
-
-* **user**  - 验证期间提供的 `user` 字符串
-* **group**  - 认证用户所属的组名列表
-* **“extra"**  - 由认证层提供的任意字符串键到字符串值的映射
-* **API**  - 指示请求是否用于API资源
-* **Request path**  - 诸如`/api`或`/healthz`的其他非资源端点的路径(请参阅[kubectl](#kubectl)).
-* **API request verb**  -  API 动词 `get`，`list`，`create`，`update`，`patch`，`watch`，`proxy`，`redirect`，`delete`和`deletecollection`用于资源请求。要确定资源 API 端点的请求动词，请参阅**确定下面的请求动词**.
-* **HTTP request verb**  -  HTTP动词`get`，`post`，`put`和`delete`用于非资源请求
-* **Resource**  - 正在访问的资源的ID或名称(仅适用于资源请求)
- --* 对于使用`get`, `update`, `patch`, 和 `delete`动词的资源请求，您必须提供资源名称。
-* **Subresource**  - 正在访问的子资源(仅用于资源请求)
-* **Namespace**  - 正在被访问的对象的命名空间(仅针对命名空间的资源请求)
-* **API group**  - 正在访问的API组(仅用于资源请求). 一个空字符串指定[核心 API 组](/docs/api/).
-
-## 确定请求动词
-
-要确定资源 API 端点的请求动词，请查看所使用的HTTP动词以及请求是否对单个资源或资源集合进行操作:
-
-HTTP动词| 请求动词
----------- | ---------------
-POST | 创建
-GET，HEAD | 获取(个人资源)，列表(集合)
-PUT | 更新
-PATCH | 补丁
-DELETE| 删除(个人资源)，删除(收藏)
-
-Kubernetes 有时会使用专门的动词检查授权以获得额外的权限。例如:
-
-* [PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/)在`extensions` API组中的`podsecuritypolicies`资源上检查`use`动词的授权。
-* [RBAC](/docs/admin/authorization/rbac/#privilege-escalation-prevention-and-bootstrapping) 在`rbac.authorization.k8s.io` API组中的`roles`和`clusterroles`资源上检查`bind`动词的授权。
-* [认证](/docs/admin/authentication/) 在核心API组中的`users`，`groups`和`serviceaccounts`上的`impersonate`动词的授权以及`authentication.k8s.io` API组中的`userextras`进行层次检查。
-
-## 授权模块
-* **ABAC模式**  - 基于属性的访问控制(ABAC)定义了访问控制范例，通过使用将属性组合在一起的策略来授予用户访问权限。策略可以使用任何类型的属性(用户属性，资源属性，对象，环境属性等)。要了解有关使用ABAC模式的更多信息，请参阅[ABAC模式](/docs/admin/authorization/abac/)
-* **RBAC模式**  - 基于角色的访问控制(RBAC)是一种根据企业内个人用户的角色来调整对计算机或网络资源的访问的方法。在这种情况下，访问是单个用户执行特定任务(例如查看，创建或修改文件)的能力。要了解有关使用RBAC模式的更多信息，请参阅[RBAC模式](/docs/admin/authorization/rbac/)
-*当指定 "RBAC"(基于角色的访问控制)使用 "rbac.authorization.k8s.io" API组来驱动授权决定时，允许管理员通过Kubernetes API动态配置权限策略.
-.. *截至1.6 RBAC模式是测试版.
-.. *要启用RBAC，请使用 `--authorization-mode=RBAC` 启动 apiserver.
-* **Webhook模式**  -  WebHook 是HTTP回调:发生事件时发生的HTTP POST; 通过HTTP POST简单的事件通知. 实施 WebHooks 的 Web 应用程序将在某些事情发生时向URL发送消息. 要了解有关使用Webhook模式的更多信息，请参阅[Webhook模式](/docs/admin/authorization/webhook/)
-* **自定义模块**  - 您可以创建使用Kubernetes的自定义模块. 要了解更多信息，请参阅下面的**自定义模块**。
-
-### 自定义模块
-可以相当容易地开发其他实现,APIserver 调用 Authorizer 接口：
-
-```go
-type Authorizer interface {
-  Authorize(a Attributes) error
-}
-```
-
-以确定是否允许每个API操作.
-
-授权插件是实现此接口的模块.授权插件代码位于 `pkg/auth/authorizer/$MODULENAME` 中。
-
-授权模块可以完全实现，也可以拨出远程授权服务。 授权模块可以实现自己的缓存，以减少具有相同或相似参数的重复授权调用的成本。 开发人员应该考虑缓存和撤销权限之间的交互。
-
-#### 检查API访问
-
-Kubernetes 将 `subjectaccessreviews.v1.authorization.k8s.io`  资源公开为允许外部访问API授权者决策的普通资源。 无论您选择使用哪个授权器，您都可以使用`SubjectAccessReview`发出一个`POST`，就像webhook授权器的`apis/authorization.k8s.io/v1/subjectaccessreviews` 端点一样，并回复一个响应。 例如：
-
-
-```bash
-kubectl create --v=8 -f -  << __EOF__
-{
-  "apiVersion": "authorization.k8s.io/v1",
-  "kind": "SubjectAccessReview",
-  "spec": {
-    "resourceAttributes": {
-      "namespace": "kittensandponies",
-      "verb": "get",
-      "group": "unicorn.example.org",
-      "resource": "pods"
-    },
-    "user": "jane",
-    "group": [
-      "group1",
-      "group2"
-    ],
-    "extra": {
-      "scopes": [
-        "openid",
-        "profile"
-      ]
-    }
-  }
-}
-__EOF__
-
---- snip lots of output ---
-
-I0913 08:12:31.362873   27425 request.go:908] Response Body: {"kind":"SubjectAccessReview","apiVersion":"authorization.k8s.io/v1","metadata":{"creationTimestamp":null},"spec":{"resourceAttributes":{"namespace":"kittensandponies","verb":"GET","group":"unicorn.example.org","resource":"pods"},"user":"jane","group":["group1","group2"],"extra":{"scopes":["openid","profile"]}},"status":{"allowed":true}}
-subjectaccessreview "" created
-```
-
-这对于调试访问问题非常有用，因为您可以使用此资源来确定授权者授予哪些访问权限。
-
-## 为您的授权模块使用标志
-
-您的策略中必须包含一个标志，以指出您的策略包含哪个授权模块:
-
-可以使用以下标志:
- - `--authorization-mode=ABAC` 基于属性的访问控制(ABAC)模式允许您使用本地文件配置策略。
- - `--authorization-mode=RBAC` 基于角色的访问控制(RBAC)模式允许您使用Kubernetes API创建和存储策略.
- - `--authorization-mode=Webhook` WebHook是一种HTTP回调模式，允许您使用远程REST管理授权。
- - `--authorization-mode=AlwaysDeny` 此标志阻止所有请求. 仅使用此标志进行测试。
- - `--authorization-mode=AlwaysAllow` 此标志允许所有请求. 只有在您不需要API请求授权的情况下才能使用此标志。
-
-您可以选择多个授权模块. 如果其中一种模式为 `AlwaysAllow`，则覆盖其他模式，并允许所有API请求。
-
-## 版本控制
-
-对于版本 1.2，配置了 kube-up.sh 创建的集群，以便任何请求都不需要授权。
-
-从版本 1.3 开始，配置由 kube-up.sh 创建的集群，使得 ABAC 授权模块处于启用状态。但是，其输入文件最初设置为允许所有用户执行所有操作，集群管理员需要编辑该文件，或者配置不同的授权器来限制用户可以执行的操作。
-
-{% endcapture %}
-{% capture whatsnext %}
-
-* 要学习有关身份验证的更多信息，请参阅**身份验证**[控制访问 Kubernetes API](docs/admin/access-the-api/)。
-* 要了解有关入学管理的更多信息，请参阅[使用 Admission 控制器](docs/admin/admission-controllers/)。
-*
-{% endcapture %}
-
-{% include templates/concept.md %}

cn/docs/admin/high-availability/index.md

@@ -1,215 +0,0 @@
----
-title: 构建高可用集群
----
-
-
-## 简介
-
-
-本文描述了如何构建一个高可用（high-availability, HA）的Kubernetes集群。这是一个非常高级的主题。
-
-对于仅希望使用Kubernetes进行试验的用户，推荐使用更简单的配置工具进行搭建，例如：
-[Minikube](/docs/getting-started-guides/minikube/)，或者尝试使用[Google Container Engine](https://cloud.google.com/container-engine/) 来运行Kubernetes。
-
-此外，当前在我们的端到端（e2e）测试环境中，没有对Kubernetes高可用的支持进行连续测试。我们将会增加这个连续测试项，但当前对单节点master的安装测试得更加严格。
-
-* TOC
-{:toc}
-
-## 概览
-
-
-搭建一个正真可靠，高度可用的分布式系统需要若干步骤。这类似于穿上内衣，裤子，皮带，背带，另一套内衣和另一套裤子。我们会详细介绍每一个步骤，但先在这里给出一个总结来帮助指导用户。
-
-
-相关步骤如下：
-
-   * [创建可靠的组成节点，共同形成我们的高可用主节点实现。](#可靠的节点)
-   * [使用etcd集群，搭建一个冗余的，可靠的存储层。](#建立一个冗余的，可靠的存储层)
-   * [启动具有备份和负载均衡能力的Kubernetes API 服务](#复制的API服务)
-   * [搭建运行master选举的Kubernetes scheduler和controller-manager守护程序](#进行master选举的组件)
-  
-系统完成时看起来应该像这样：
-
-![High availability Kubernetes diagram](/images/docs/ha.svg)
-
-
-## 初始配置
-
-
-本文假设你正在搭建一个3节点的主节点集群，每个节点上都运行者某种Linux系统。
-
-指南中的示例使用Debian发行版，但它们应该可以被轻松移植到其他发行版上。
-
-同样的，不管在公有云还是私有云亦或是裸机上，这个配置都应该可以运行。
-
-
-从一个现成的单主节点集群开始是实现一个高可用Kubernetes集群的最简单的方法。这篇指导 [https://get.k8s.io](https://get.k8s.io) 描述了在多种平台上方便的安装一个单主节点集群的方法。
-
-## 可靠的节点
-
-
-我们在每个主节点上都将运行数个实现Kubernetes API的进程。使他们可靠的第一步是保证在发生故障时，每一个进程都可以自动重启。为了实现这个目标，我们需要安装一个进程监视器。我们选择了在每个工作者节点上都会运行的`kubelet`进程。这会带来便利性，因为我们使用了容器来分发我们的二进制文件，所以我们能够为每一个守护程序建立资源限制并省查它们的资源消耗。当然，我们也需要一些手段来监控kubelete本身（在此监测监控者本身是一个有趣的话题）。对于Debian系统我们选择了monit，但也有许多可替代的工具。例如在基于systemd的系统上（如RHEL, CentOS），你可以运行 'systemctl enable kubelet'。
-
-
-如果你是从标准的Kubernetes安装扩展而来，那么`kubelet`二进制文件应该已经存在于你的系统中。你可以运行`which kubelet`来判断是否确实安装了这个二进制文件。如果没有安装的话，你应该手动安装 [kubelet binary](https://storage.googleapis.com/kubernetes-release/release/v0.19.3/bin/linux/amd64/kubelet), 
-[kubelet init file](http://releases.k8s.io/{{page.githubbranch}}/cluster/saltbase/salt/kubelet/initd) 和 [default-kubelet](/docs/admin/high-availability/default-kubelet)脚本。
-
-如果使用monit，你还需要安装monit守护程序（`apt-get install monit`）以及[monit-kubelet](/docs/admin/high-availability/monit-kubelet) 和
-[monit-docker](/docs/admin/high-availability/monit-docker) 配置。
-
-在使用systemd的系统上，你可以执行 `systemctl enable kubelet` 和 `systemctl enable docker`。
-
-
-## 建立一个冗余的，可靠的存储层
-
-
-高可用方案的中心基础是一个冗余的，可靠的存储层。高可用的头条规则是保护数据。不管发生了什么，不管什么着了火，只要还有数据，你就可以重建。如果丢掉了数据，你就完了。
-
-
-集群化的etcd已经把你存储的数据复制到了你集群中的所有主节点实例上。这意味着如果要想丢失数据，三个节点的物理（或虚拟）硬盘需要全部同时故障。这种情况发生的概率是比较低的，所以对于许多人来说，运行一个复制的etcd集群可能已经足够的可靠了。你可以将集群数量从3个增大到5个来增加集群的可靠性。如果那样还不够，你可以添加[更多的可靠性到你的存储层](#更加可靠的存储)。
-
-
-### 集群化etcd
-
-
-集群化etcd的完整细节超出了本文范围，你可以在[etcd clustering page](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/clustering.md)找到许多详细内容。这个例子仅走查一个简单的集群建立过程，使用etcd内置的发现功能来构建我们的集群。
-
-
-首先，调用etcd发现服务来创建一个新令牌:
-
-```shell
-curl https://discovery.etcd.io/new?size=3
-```
-
-
-在每个节点上，拷贝 [etcd.yaml](/docs/admin/high-availability/etcd.yaml) 文件到`/etc/kubernetes/manifests/etcd.yaml`。
-
-
-每个节点上的kubelet会动态的监控这个文件夹的内容，并且会按照`etcd.yaml`里对pod的定义创建一个`etcd`服务的实例。
-
-
-请注意，你应该使用上文中获取的令牌URL替换全部三个节点上`etcd.yaml`中的`${DISCOVERY_TOKEN}`项。同时还应该将每个节点上的 `${NODE_NAME}`替换为一个不同的名字（例如：`node-1`），并将 `${NODE_IP}`替换为正确的IP地址。
-
-
-#### 验证你的集群
-
-
-如果已经将这个文件拷贝到所有三个节点，你应该已经搭建起了一个集群化的etcd。你可以在主节点上进行验证：
-```shell
-kubectl exec < pod_name > etcdctl member list
-```
-
-和
-
-```shell
-kubectl exec < pod_name > etcdctl cluster-health
-```
-
-
-你也可以在一个节点上运行 `etcdctl set foo bar`，在另一个节点上运行`etcdctl get foo`来验证集群是否工作正常。
-
-
-### 更加可靠的存储
-
-
-当然，如果你对增加数据的可靠性感兴趣，这里还有一些更深入的选项可以使etcd把它的数据存放在比常规硬盘更可靠的地方（裤带和背带，ftw!）。
-
-
-如果你使用云服务，那么你的提供商通常会为你提供这个特性，例如Google Cloud Platform上的 [Persistent Disk](https://cloud.google.com/compute/docs/disks/persistent-disks) 。它们是可以挂载到你的虚拟机中的块设备持久化存储。其他的云服务提供商提供了类似的解决方案。
-
-
-如果运行于物理机之上，你仍然可以使用iSCSI或者NFS接口通过网络来连接冗余存储。
-此外，你还可以运行一个集群文件系统，比如Gluster或者Ceph。最后，你还可以在你的每个物理机器上运行RAID矩阵。
-
-
-不管你选择如何实现，如果已经选择了使用其中的一个选项，那么你应该保证你的存储被挂载到了每一台机器上。如果你的存储在集群中的三个主节点之间共享，那么你应该在存储上为每一个节点创建一个不同的文件夹。对于所有的这些指导，我们都假设这个存储被挂载到你机器上的`/var/etcd/data`路径。
-
-
-## 复制的API服务
-
-
-在正确搭建复制的etcd之后，我们还需要使用kubelet安装apiserver。
-
-
-
-
-首先，你需要创建初始的日志文件，这样Docker才会挂载一个文件而不是一个文件夹：
-```shell
-touch /var/log/kube-apiserver.log
-```
-
-接下来，你需要在每个节点上创建一个`/srv/kubernetes/`文件夹。这个文件夹包含：
-
-   * basic_auth.csv  - 基本认证的用户名和密码
-   * ca.crt - CA证书
-   * known_tokens.csv - 实体（例如kubelet）用来和apiserver通信的令牌
-   * kubecfg.crt - 客户端证书，公钥
-   * kubecfg.key - 客户端证书，私钥
-   * server.cert - 服务端证书，公钥
-   * server.key - 服务端证书，私钥
-
-
-创建这个文件夹最简单的方法可以是从一个工作正常的集群的主节点拷贝，或者你也可以手动生成它们。
-
-
-### 启动API服务
-
-
-一旦这些文件已经存在了，拷贝 [kube-apiserver.yaml](/docs/admin/high-availability/kube-apiserver.yaml) 到每个主节点的 `/etc/kubernetes/manifests/`文件夹。
-
-
-kubelet会监控这个文件夹，并且会按照文件里对pod的定义创建一个`kube-apiserver`容器。
-
-
-### 负载均衡
-
-
-现在，你应该有3个全部正常工作的apiserver了。如果搭建了网络负载均衡器，你应该能够通过那个负载均衡器访问你的集群，并且看到负载在apiserver实例间分发。设置负载均衡器依赖于你的平台的实际情况，例如对于Google Cloud Platform的指导可以在[这里](https://cloud.google.com/compute/docs/load-balancing/)找到。
-
-
-请注意，如果使用了身份认证，你可能需要重新生成你的证书，除每个节点的IP地址外额外包含负载均衡器的IP地址。
-
-
-对于部署在集群中的pods， `kubernetes`服务/dns名称应该自动的为主节点提供了负载均衡的endpoint。
-
-
-对于使用API的外部用户（如命令行运行的`kubectl`，持续集成管道或其他客户端）你会希望将他们配置成为访问外部负载均衡器的地址。
-
-
-## 进行Master选举的组件
-
-
-到目前为止，我们已经搭建了状态存储，也搭建好了API服务，但我们还没有运行任何真正改变集群状态的服务，比如controller manager和scheduler。为了可靠的实现这个目标，我们希望在同一时间只有一个参与者在修改集群状态。但是我们希望复制这些参与者的实例以防某个机器宕机。要做到这一点，我们打算在API中使用一个lease-lock来执行master选举。我们会对每一个scheduler和controller-manager使用`--leader-elect`标志，从而在API中使用一个租约来保证同一时间只有一个scheduler和controller-manager的实例正在运行。
-
-
-scheduler和controller-manager可以配置为只和位于它们相同节点（即127.0.0.1）上的API服务通信，也可以配置为使用API服务的负载均衡器的IP地址。不管它们如何配置，当使用`--leader-elect` 时scheduler和controller-manager都将完成上文提到的leader选举过程。
-
-
-为了防止访问API服务失败，选举出的leader不能通过更新租约来选举一个新的leader。当scheduler和controller-manager通过127.0.0.1访问API服务，而相同节点上的API服务不可用时，这一点相当重要。
-
-
-### 安装配置文件
-
-
-首先，在每个节点上创建空白日志文件，这样Docker就会挂载这些文件而不是创建一个新文件夹：
-
-```shell
-touch /var/log/kube-scheduler.log
-touch /var/log/kube-controller-manager.log
-```
-
-
-接下来，在每个节点上配置scheduler和controller manager pods的描述文件。拷贝 [kube-scheduler.yaml](/docs/admin/high-availability/kube-scheduler.yaml) 和 [kube-controller-manager.yaml](/docs/admin/high-availability/kube-controller-manager.yaml) 到`/etc/kubernetes/manifests/` 文件夹。
-
-
-## 结尾
-
-
-此时，你已经完成了master组件的配置（耶！），但你还需要添加工作者节点（噗！）。
-
-
-如果你有一个现成的集群，你只需要在每个节点上简单的重新配置你的kubeletes连接到负载均衡的endpoint并重启它们。
-
-
-如果你搭建的是一个全新的集群，你将需要在每个工作节点上安装kubelet和kube-proxy，并设置 `--apiserver`指向复制的endpoint。

cn/docs/admin/kube-apiserver.md

@@ -1,233 +0,0 @@
----
-title: kube-apiserver
-notitle: true
----
-## kube-apiserver
-
-
-
-### 概要
-
-
-Kubernetes API server 为 api 对象验证并配置数据，包括 pods、 services、 replicationcontrollers和其它 api 对象。API Server 提供 REST 操作和到集群共享状态的前端，所有其他组件通过它进行交互。
-
-```
-kube-apiserver
-```
-
-### 选项
-```
-
-      --admission-control stringSlice                           控制资源进入集群的准入控制插件的顺序列表。逗号分隔的NamespaceLifecycle列表。(默认值[AlwaysAdmit])
-
-      --admission-control-config-file string                    包含准入控制配置的文件。
-
-      --advertise-address ip                                    向集群成员通知apiserver消息的IP地址。这个地址必须能够被集群中其他成员访问。如果IP地址为空，将会使用--bind-address，如果未指定--bind-address，将会使用主机的默认接口地址。
-
-      --allow-privileged                                        如果为true, 将允许特权容器.
-
-      --anonymous-auth                                          启用到API server的安全端口的匿名请求。未被其他认证方法拒绝的请求被当做匿名请求。匿名请求的用户名为system:anonymous，用户组名为system:unauthenticated。（默认值true）
-
-      --apiserver-count int                                     集群中运行的apiserver数量，必须为正数。（默认值1）
-
-      --audit-log-maxage int                                    基于文件名中的时间戳，旧审计日志文件的最长保留天数。
-
-      --audit-log-maxbackup int                                 旧审计日志文件的最大保留个数.
-
-      --audit-log-maxsize int                                   审计日志被轮转前的最大兆字节数。
-
-      --audit-log-path string                                   如果设置该值，所有到apiserver的请求都将会被记录到这个文件。'-'表示记录到标准输出。
-
-      --audit-policy-file string                                定义审计策略配置的文件的路径。需要打开'AdvancedAuditing'特性开关。AdvancedAuditing需要一个配置来启用审计功能。
-
-      --audit-webhook-config-file string                        一个具有kubeconfig格式文件的路径，该文件定义了审计的webhook配置。需要打开'AdvancedAuditing'特性开关。
-
-      --audit-webhook-mode string                               发送审计事件的策略。 Blocking模式表示正在发送事件时应该阻塞服务器的响应。 Batch模式使webhook异步缓存和发送事件。 Known模式为batch,blocking。 （默认值"batch")
-
-      --authentication-token-webhook-cache-ttl duration         从webhook令牌认证者获取的响应的缓存时长。(默认值2m0s)
-
-      --authentication-token-webhook-config-file string         包含webhook配置的文件，用于令牌认证，具有kubeconfig格式。API server将查询远程服务来决定对bearer令牌的认证。
-
-      --authorization-mode string                               在安全端口上进行权限验证的插件的顺序列表。以逗号分隔的列表，包括：AlwaysAllow,AlwaysDeny,ABAC,Webhook,RBAC,Node.（默认值"AlwaysAllow"）
- 
-      --authorization-policy-file string                        包含权限验证策略的csv文件，和--authorization-mode=ABAC一起使用，作用在安全端口上。
- 
-      --authorization-webhook-cache-authorized-ttl duration     从webhook授权者获得的'authorized'响应的缓存时长。（默认值5m0s） 
- 
-      --authorization-webhook-cache-unauthorized-ttl duration   从webhook授权者获得的'unauthorized'响应的缓存时长。（默认值30s）
- 
-      --authorization-webhook-config-file string                包含webhook配置的kubeconfig格式文件，和--authorization-mode=Webhook一起使用。API server将查询远程服务来决定对API server安全端口的访问。
- 
-      --azure-container-registry-config string                  包含Azure容器注册表配置信息的文件的路径。
-
-      --basic-auth-file string                                  如果设置该值，这个文件将会被用于准许通过http基本认证到API server安全端口的请求。
-
-      --bind-address ip                                         监听--seure-port的IP地址。被关联的接口必须能够被集群其它节点和CLI/web客户端访问。如果为空，则将使用所有接口（0.0.0.0）。（默认值0.0.0.0）
-
-      --cert-dir string                                         存放TLS证书的目录。如果提供了--tls-cert-file和--tls-private-key-file选项，该标志将被忽略。（默认值 "/var/run/kubernetes"）
-
-      --client-ca-file string                                   如果设置此标志，对于任何请求，如果存包含client-ca-file中的authorities签名的客户端证书，将会使用客户端证书中的CommonName对应的身份进行认证。
- 
-      --cloud-config string                                     云服务提供商配置文件路径。空字符串表示无配置文件.
- 
-      --cloud-provider string                                   云服务提供商，空字符串表示无提供商。
- 
-      --contention-profiling                                    如果已经启用profiling，则启用锁竞争profiling。
-
-      --cors-allowed-origins stringSlice                        CORS的域列表，以逗号分隔。合法的域可以是一个匹配子域名的正则表达式。如果这个列表为空则不会启用CORS.
-
-      --delete-collection-workers int                           用于DeleteCollection调用的工作者数量。这被用于加速namespace的清理。(默认值1)
-
-      --deserialization-cache-size int                          在内存中缓存的反序列化json对象的数量。
-
-      --enable-aggregator-routing                               打开到endpoints IP的aggregator路由请求，替换cluster IP。
-
-      --enable-garbage-collector                                启用通用垃圾回收器. 必须与kube-controller-manager对应的标志保持同步。 （默认值true）
-
-      --enable-logs-handler                                     如果为true，则为apiserver日志功能安装一个/logs处理器。（默认值true）
-
-      --enable-swagger-ui                                       在apiserver的/swagger-ui路径启用swagger ui。
-
-      --etcd-cafile string                                      用于保护etcd通信的SSL CA文件。
-
-      --etcd-certfile string                                    用于保护etcd通信的的SSL证书文件。
-
-      --etcd-keyfile string                                     用于保护etcd通信的SSL密钥文件.
-
-      --etcd-prefix string                                      附加到所有etcd中资源路径的前缀。 （默认值"/registry"）
-
-      --etcd-quorum-read                                        如果为true, 启用quorum读。
-
-      --etcd-servers stringSlice                                连接的etcd服务器列表,形式为（scheme://ip:port)，使用逗号分隔。
-
-      --etcd-servers-overrides stringSlice                      针对单个资源的etcd服务器覆盖配置, 以逗号分隔。 单个配置覆盖格式为: group/resource#servers, 其中servers形式为http://ip:port, 以分号分隔。
-
-      --event-ttl duration                                      事件驻留时间。（默认值1h0m0s)
-
-      --experimental-bootstrap-token-auth                       启用此选项以允许'kube-system'命名空间中的'bootstrap.kubernetes.io/token'类型密钥可以被用于TLS的启动认证。
-
-      --experimental-encryption-provider-config string          包含加密提供程序的配置的文件，该加密提供程序被用于在etcd中保存密钥。
-
-      --experimental-keystone-ca-file string                    如果设置该值，将会使用experimental-keystone-ca-file中的一个authority对Keystone服务的证书进行验证，否则将会使用主机的根CA进行验证。
-
-      --experimental-keystone-url string                        如果设置了该值，将启用keystone认证插件。
-
-      --external-hostname string                                为此master生成外部URL时使用的主机名(例如Swagger API文档)。
-
-      --feature-gates mapStringBool                             一个描述alpha/experimental特性开关的键值对列表。 选项包括:
-Accelerators=true|false (ALPHA - default=false)
-AdvancedAuditing=true|false (ALPHA - default=false)
-AffinityInAnnotations=true|false (ALPHA - default=false)
-AllAlpha=true|false (ALPHA - default=false)
-AllowExtTrafficLocalEndpoints=true|false (default=true)
-AppArmor=true|false (BETA - default=true)
-DynamicKubeletConfig=true|false (ALPHA - default=false)
-DynamicVolumeProvisioning=true|false (ALPHA - default=true)
-ExperimentalCriticalPodAnnotation=true|false (ALPHA - default=false)
-ExperimentalHostUserNamespaceDefaulting=true|false (BETA - default=false)
-LocalStorageCapacityIsolation=true|false (ALPHA - default=false)
-PersistentLocalVolumes=true|false (ALPHA - default=false)
-RotateKubeletClientCertificate=true|false (ALPHA - default=false)
-RotateKubeletServerCertificate=true|false (ALPHA - default=false)
-StreamingProxyRedirects=true|false (BETA - default=true)
-TaintBasedEvictions=true|false (ALPHA - default=false)
-
-      --google-json-key string                                  用于认证的Google Cloud Platform服务账号的JSON密钥。
-
-      --insecure-allow-any-token username/group1,group2         如果设置该值, 你的服务将处于非安全状态。任何令牌都将会被允许，并将从令牌中把用户信息解析成为username/group1,group2。
-
-      --insecure-bind-address ip                                用于监听--insecure-port的IP地址 (设置成0.0.0.0表示监听所有接口)。（默认值127.0.0.1)
-
-      --insecure-port int                                       用于监听不安全和为认证访问的端口。这个配置假设你已经设置了防火墙规则，使得这个端口不能从集群外访问。对集群的公共地址的443端口的访问将被代理到这个端口。默认设置中使用nginx实现。（默认值8080）
-
-      --kubelet-certificate-authority string                    证书authority的文件路径。
-
-      --kubelet-client-certificate string                       用于TLS的客户端证书文件路径。
-
-      --kubelet-client-key string                               用于TLS的客户端证书密钥文件路径.
-
-      --kubelet-https                                           为kubelet启用https。 （默认值true）
-
-      --kubelet-preferred-address-types stringSlice             用于kubelet连接的首选NodeAddressTypes列表。 (默认值[Hostname,InternalDNS,InternalIP,ExternalDNS,ExternalIP])
-
-      --kubelet-read-only-port uint                             已废弃: kubelet端口. （默认值10255）
-
-      --kubelet-timeout duration                                kubelet操作超时时间。（默认值 
-      5s）
-
-      --kubernetes-service-node-port int                        如果不为0，Kubernetes master服务（用于创建/管理apiserver）将会使用NodePort类型，并将这个值作为端口号。如果为0，Kubernetes master服务将会使用ClusterIP类型。
-
-      --master-service-namespace string                         已废弃: 注入到pod中的kubernetes master服务的命名空间。（默认值"default"） 
-
-      --max-connection-bytes-per-sec int                        如果不为0，每个用户连接将会被限速为该值（bytes/sec）。当前只应用于长时间运行的请求。
-
-      --max-mutating-requests-inflight int                      在给定时间内进行中可变请求的最大数量。当超过该值时，服务将拒绝所有请求。0值表示没有限制。（默认值200）
-
-      --max-requests-inflight int                               在给定时间内进行中不可变请求的最大数量。当超过该值时，服务将拒绝所有请求。0值表示没有限制。（默认值400）
-
-      --min-request-timeout int                                 一个可选字段，表示一个handler在一个请求超时前，必须保持它处于打开状态的最小秒数。当前只对监听请求handler有效，它基于这个值选择一个随机数作为连接超时值，以达到分散负载的目的（默认值1800）。
-      
-      --oidc-ca-file string                                    如果设置该值，将会使用oidc-ca-file中的任意一个authority对OpenID服务的证书进行验证，否则将会使用主机的根CA对其进行验证。
-      
-      --oidc-client-id string                                   使用OpenID连接的客户端的ID，如果设置了oidc-issuer-url，则必须设置这个值。
-       
-      --oidc-groups-claim string                                如果提供该值，这个自定义OpenID连接名将指定给特定的用户组。该声明值需要是一个字符串或字符串数组。此标志为实验性的，请查阅验证相关文档进一步了解详细信息。
-
-      --oidc-issuer-url string                                  OpenID颁发者URL，只接受HTTPS方案。如果设置该值，它将被用于验证OIDC JSON Web Token(JWT)。
-      
-      --oidc-username-claim string                              用作用户名的OpenID声明值。注意，不保证除默认 ('sub')外的其他声明值的唯一性和不变性。此标志为实验性的，请查阅验证相关文档进一步了解详细信息。
-       
-      --profiling                                               在web接口host:port/debug/pprof/上启用profiling。（默认值true）
-       
-      --proxy-client-cert-file string                           当必须调用外部程序时，用于证明aggregator或者kube-apiserver的身份的客户端证书。包括代理到用户api-server的请求和调用webhook准入控制插件的请求。它期望这个证书包含一个来自于CA中的--requestheader-client-ca-file标记的签名。该CA在kube-system命名空间的'extension-apiserver-authentication' configmap中发布。从Kube-aggregator收到调用的组件应该使用该CA进行他们部分的双向TLS验证。
- 
-      --proxy-client-key-file string                            当必须调用外部程序时，用于证明aggregator或者kube-apiserver的身份的客户端证书密钥。包括代理到用户api-server的请求和调用webhook准入控制插件的请求。
-      
-      --repair-malformed-updates                                如果为true，服务将会尽力修复更新请求以通过验证，例如：将更新请求UID的当前值设置为空。在我们修复了所有发送错误格式请求的客户端后，可以关闭这个标志。
-
-      --requestheader-allowed-names stringSlice                 使用--requestheader-username-headers指定的，允许在头部提供用户名的客户端证书通用名称列表。如果为空，任何通过--requestheader-client-ca-file中authorities验证的客户端证书都是被允许的。
-      
-      --requestheader-client-ca-file string                     在信任请求头中以--requestheader-username-headers指示的用户名之前，用于验证接入请求中客户端证书的根证书捆绑。
-      
-      --requestheader-extra-headers-prefix stringSlice          用于检查的请求头的前缀列表。建议使用X-Remote-Extra-。
-
-      --requestheader-group-headers stringSlice                 用于检查群组的请求头列表。建议使用X-Remote-Group.
-       
-      --requestheader-username-headers stringSlice              用于检查用户名的请求头列表。建议使用X-Remote-User。
-       
-      --runtime-config mapStringString                          传递给apiserver用于描述运行时配置的键值对集合。 apis/<groupVersion>键可以被用来打开/关闭特定的api版本。apis/<groupVersion>/<resource>键被用来打开/关闭特定的资源. api/all和api/legacy键分别用于控制所有的和遗留的api版本.
-        
-      --secure-port int                                         用于监听具有认证授权功能的HTTPS协议的端口。如果为0，则不会监听HTTPS协议。 （默认值6443)
-       
-      --service-account-key-file stringArray                    包含PEM加密的x509 RSA或ECDSA私钥或公钥的文件，用于验证ServiceAccount令牌。如果设置该值，--tls-private-key-file将会被使用。指定的文件可以包含多个密钥，并且这个标志可以和不同的文件一起多次使用。
-      
-      --service-cluster-ip-range ipNet                          CIDR表示的IP范围，服务的cluster ip将从中分配。 一定不要和分配给nodes和pods的IP范围产生重叠。
-      
-      --ssh-keyfile string                                      如果不为空，在使用安全的SSH代理访问节点时，将这个文件作为用户密钥文件。
-      
-      --storage-backend string                                  持久化存储后端。 选项为: 'etcd3' (默认), 'etcd2'.
-     
-      --storage-media-type string                               在存储中保存对象的媒体类型。某些资源或者存储后端可能仅支持特定的媒体类型，并且忽略该配置项。（默认值 "application/vnd.kubernetes.protobuf")
-      
-      --storage-versions string                                 按组划分资源存储的版本。 以"group1/version1,group2/version2,..."的格式指定。当对象从一组移动到另一组时, 你可以指定"group1=group2/v1beta1,group3/v1beta1,..."的格式。你只需要传入你希望从结果中改变的组的列表。默认为从KUBE_API_VERSIONS环境变量集成而来，所有注册组的首选版本列表。 （默认值"admission.k8s.io/v1alpha1,admissionregistration.k8s.io/v1alpha1,apps/v1beta1,authentication.k8s.io/v1,authorization.k8s.io/v1,autoscaling/v1,batch/v1,certificates.k8s.io/v1beta1,componentconfig/v1alpha1,extensions/v1beta1,federation/v1beta1,imagepolicy.k8s.io/v1alpha1,networking.k8s.io/v1,policy/v1beta1,rbac.authorization.k8s.io/v1beta1,settings.k8s.io/v1alpha1,storage.k8s.io/v1,v1")
-      
-      --target-ram-mb int                                       apiserver内存限制，单位为MB(用于配置缓存大小等)。
-      
-      --tls-ca-file string                                      如果设置该值，这个证书authority将会被用于从Admission Controllers过来的安全访问。它必须是一个PEM加密的合法CA捆绑包。此外, 该证书authority可以被添加到以--tls-cert-file提供的证书文件中.
-      
-      --tls-cert-file string                                    包含用于HTTPS的默认x509证书的文件。（如果有CA证书，则附加于server证书之后）。如果启用了HTTPS服务，并且没有提供--tls-cert-file和--tls-private-key-file，则将为公共地址生成一个自签名的证书和密钥并保存于/var/run/kubernetes目录。
-      
-      --tls-private-key-file string                             包含匹配--tls-cert-file的x509证书私钥的文件。
-      
-      --tls-sni-cert-key namedCertKey                           一对x509证书和私钥的文件路径, 可以使用符合正式域名的域形式作为后缀。 如果没有提供域形式后缀, 则将提取证书名。 非通配符版本优先于通配符版本, 显示的域形式优先于证书中提取的名字。 对于多个密钥/证书对, 请多次使用--tls-sni-cert-key。例如: "example.crt,example.key" or "foo.crt,foo.key:*.foo.com,foo.com". （默认值[])
-      
-      --token-auth-file string                                  如果设置该值，这个文件将被用于通过令牌认证来保护API服务的安全端口。
-      
-      --version version[=true]                                  打印版本信息并退出。
-      
-      --watch-cache                                             启用apiserver的监视缓存。（默认值true）
-      
-      --watch-cache-sizes stringSlice                           每种资源（pods, nodes等）的监视缓存大小列表，以逗号分隔。每个缓存配置的形式为：resource#size，size是一个数字。在watch-cache启用时生效。
-```
-
-###### Auto generated by spf13/cobra on 11-Jul-2017

cn/docs/admin/kubelet-authentication-authorization.md

@@ -1,87 +0,0 @@
----
-approvers:
-- liggitt
-title: Kubelet authentication/authorization
----
-
-* TOC
-{:toc}
-
-## Overview
-
-A kubelet's HTTPS endpoint exposes APIs which give access to data of varying sensitivity,
-and allow you to perform operations with varying levels of power on the node and within containers.
-
-This document describes how to authenticate and authorize access to the kubelet's HTTPS endpoint.
-
-## Kubelet authentication
-
-By default, requests to the kubelet's HTTPS endpoint that are not rejected by other configured
-authentication methods are treated as anonymous requests, and given a username of `system:anonymous`
-and a group of `system:unauthenticated`.
-
-To disable anonymous access and send `401 Unauthorized` responses to unauthenticated requests:
-
-* start the kubelet with the `--anonymous-auth=false` flag
-
-To enable X509 client certificate authentication to the kubelet's HTTPS endpoint:
-
-* start the kubelet with the `--client-ca-file` flag, providing a CA bundle to verify client certificates with
-* start the apiserver with `--kubelet-client-certificate` and `--kubelet-client-key` flags
-* see the [apiserver authentication documentation](/docs/admin/authentication/#x509-client-certs) for more details
-
-To enable API bearer tokens (including service account tokens) to be used to authenticate to the kubelet's HTTPS endpoint:
-
-* ensure the `authentication.k8s.io/v1beta1` API group is enabled in the API server
-* start the kubelet with the `--authentication-token-webhook`, `--kubeconfig`, and `--require-kubeconfig` flags
-* the kubelet calls the `TokenReview` API on the configured API server to determine user information from bearer tokens
-
-## Kubelet authorization
-
-Any request that is successfully authenticated (including an anonymous request) is then authorized. The default authorization mode is `AlwaysAllow`, which allows all requests.
-
-There are many possible reasons to subdivide access to the kubelet API:
-
-* anonymous auth is enabled, but anonymous users' ability to call the kubelet API should be limited
-* bearer token auth is enabled, but arbitrary API users' (like service accounts) ability to call the kubelet API should be limited
-* client certificate auth is enabled, but only some of the client certificates signed by the configured CA should be allowed to use the kubelet API
-
-To subdivide access to the kubelet API, delegate authorization to the API server:
-
-* ensure the `authorization.k8s.io/v1beta1` API group is enabled in the API server
-* start the kubelet with the `--authorization-mode=Webhook`, `--kubeconfig`, and `--require-kubeconfig` flags
-* the kubelet calls the `SubjectAccessReview` API on the configured API server to determine whether each request is authorized
-
-The kubelet authorizes API requests using the same [request attributes](/docs/admin/authorization/#request-attributes) approach as the apiserver.
-
-The verb is determined from the incoming request's HTTP verb:
-
-HTTP verb | request verb
-----------|---------------
-POST      | create
-GET, HEAD | get
-PUT       | update
-PATCH     | patch
-DELETE    | delete
-
-The resource and subresource is determined from the incoming request's path:
-
-Kubelet API  | resource | subresource
--------------|----------|------------
-/stats/\*     | nodes    | stats
-/metrics/\*   | nodes    | metrics
-/logs/\*      | nodes    | log
-/spec/\*      | nodes    | spec
-*all others* | nodes    | proxy
-
-The namespace and API group attributes are always an empty string, and
-the resource name is always the name of the kubelet's `Node` API object.
-
-When running in this mode, ensure the user identified by the `--kubelet-client-certificate` and `--kubelet-client-key`
-flags passed to the apiserver is authorized for the following attributes:
-
-* verb=\*, resource=nodes, subresource=proxy
-* verb=\*, resource=nodes, subresource=stats
-* verb=\*, resource=nodes, subresource=log
-* verb=\*, resource=nodes, subresource=spec
-* verb=\*, resource=nodes, subresource=metrics

cn/docs/admin/kubelet-tls-bootstrapping.md

@@ -1,216 +0,0 @@
----
-approvers:
-- ericchiang
-- mikedanese
-- jcbsmpsn
-title: TLS bootstrapping
----
-
-* TOC
-{:toc}
-
-## Overview
-
-This document describes how to set up TLS client certificate bootstrapping for kubelets.
-Kubernetes 1.4 introduced an API for requesting certificates from a cluster-level Certificate Authority (CA). The original intent of this API is to enable provisioning of TLS client certificates for kubelets. The proposal can be found [here](https://github.com/kubernetes/kubernetes/pull/20439)
-and progress on the feature is being tracked as [feature #43](https://github.com/kubernetes/features/issues/43).
-
-## kube-apiserver configuration
-
-The API server should be configured with an [authenticator](/docs/admin/authentication/) that can authenticate tokens as a user in the `system:bootstrappers` group.
-
-This group will later be used in the controller-manager configuration to scope approvals in the default approval
-controller. As this feature matures, you should ensure tokens are bound to a Role-Based Access Control (RBAC) policy which limits requests
-(using the bootstrap token) strictly to client requests related to certificate provisioning. With RBAC in place, scoping the tokens to a group allows for great flexibility (e.g. you could disable a particular bootstrap group's access when you are done provisioning the nodes).
-
-While any authentication strategy can be used for the kubelet's initial bootstrap credentials, the following two authenticators are recommended for ease of provisioning.
-
-1. [Bootstrap Tokens](/docs/admin/bootstrap-tokens/) - __alpha__
-2. [Token authentication file](###token-authentication-file)
-
-Using bootstrap tokens is currently __alpha__ and will simplify the management of bootstrap token management especially in a HA scenario. 
-
-### Token authentication file
-Tokens are arbitrary but should represent at least 128 bits of entropy derived from a secure random number
-generator (such as /dev/urandom on most modern systems). There are multiple ways you can generate a token. For example:
-
-`head -c 16 /dev/urandom | od -An -t x | tr -d ' '`
-
-will generate tokens that look like `02b50b05283e98dd0fd71db496ef01e8`
-
-The token file should look like the following example, where the first three values can be anything and the quoted group
-name should be as depicted:
-
-```
-02b50b05283e98dd0fd71db496ef01e8,kubelet-bootstrap,10001,"system:bootstrappers"
-```
-
-Add the `--token-auth-file=FILENAME` flag to the kube-apiserver command (in your systemd unit file perhaps) to enable the token file.
-See docs [here](/docs/admin/authentication/#static-token-file) for further details.
-
-### Client certificate CA bundle
-
-Add the `--client-ca-file=FILENAME` flag to the kube-apiserver command to enable client certificate authentication,
-referencing a certificate authority bundle containing the signing certificate (e.g. `--client-ca-file=/var/lib/kubernetes/ca.pem`).
-
-## kube-controller-manager configuration
-The API for requesting certificates adds a certificate-issuing control loop to the Kubernetes Controller Manager. This takes the form of a
-[cfssl](https://blog.cloudflare.com/introducing-cfssl/) local signer using assets on disk. Currently, all certificates issued have one year validity and a default set of key usages.
-
-### Signing assets
-You must provide a Certificate Authority in order to provide the cryptographic materials necessary to issue certificates.
-This CA should be trusted by kube-apiserver for authentication with the `--client-ca-file=FILENAME` flag. The management
-of the CA is beyond the scope of this document but it is recommended that you generate a dedicated CA for Kubernetes.
-Both certificate and key are assumed to be PEM-encoded.
-
-The kube-controller-manager flags are:
-
-```
---cluster-signing-cert-file="/etc/path/to/kubernetes/ca/ca.crt" --cluster-signing-key-file="/etc/path/to/kubernetes/ca/ca.key"
-```
-
-### Approval controller
-
-In 1.7 the experimental "group auto approver" controller is dropped in favor of the new `csrapproving` controller
-that ships as part of [kube-controller-manager](/docs/admin/kube-controller-manager/) and is enabled by default.
-The controller uses the [`SubjectAccessReview` API](/docs/admin/authorization/#checking-api-access) to determine
-if a given user is authorized to request a CSR, then approves based on the authorization outcome. To prevent
-conflicts with other approvers, the builtin approver doesn't explicitly deny CSRs, only ignoring unauthorized requests.
-
-The controller categorizes CSRs into three subresources:
-
-1. `nodeclient` - a request by a user for a client certificate with `O=system:nodes` and `CN=system:node:(node name)`.
-2. `selfnodeclient` - a node renewing a client certificate with the same `O` and `CN`.
-3. `selfnodeserver` - a node renewing a serving certificate. (ALPHA, requires feature gate)
-
-The checks to determine if a CSR is a `selfnodeserver` request is currently tied to the kubelet's credential rotation
-implementation, an __alpha__ feature. As such, the definition of `selfnodeserver` will likely change in a future and
-requires the `RotateKubeletServerCertificate` feature gate on the controller manager. The feature progress can be
-tracked at [kubernetes/features#267](https://github.com/kubernetes/features/issues/267).
-
-```
---feature-gates=RotateKubeletServerCertificate=true
-```
-
-The following RBAC `ClusterRoles` represent the `nodeclient`, `selfnodeclient`, and `selfnodeserver` capabilities. Similar roles
-may be automatically created in future releases.
-
-```yml
-# A ClusterRole which instructs the CSR approver to approve a user requesting
-# node client credentials.
-kind: ClusterRole
-apiVersion: rbac.authorization.k8s.io/v1beta1
-metadata:
-  name: approve-node-client-csr
-rules:
-- apiGroups: ["certificates.k8s.io"]
-  resources: ["certificatesigningrequests/nodeclient"]
-  verbs: ["create"]
----
-# A ClusterRole which instructs the CSR approver to approve a node renewing its
-# own client credentials.
-kind: ClusterRole
-apiVersion: rbac.authorization.k8s.io/v1beta1
-metadata:
-  name: approve-node-client-renewal-csr
-rules:
-- apiGroups: ["certificates.k8s.io"]
-  resources: ["certificatesigningrequests/selfnodeclient"]
-  verbs: ["create"]
----
-# A ClusterRole which instructs the CSR approver to approve a node requesting a
-# serving cert matching its client cert.
-kind: ClusterRole
-apiVersion: rbac.authorization.k8s.io/v1beta1
-metadata:
-  name: approve-node-server-renewal-csr
-rules:
-- apiGroups: ["certificates.k8s.io"]
-  resources: ["certificatesigningrequests/selfnodeserver"]
-  verbs: ["create"]
-```
-
-These powers can be granted to credentials, such as bootstrapping tokens. For example, to replicate the behavior
-provided by the removed auto-approval flag, of approving all CSRs by a single group:
-
-```
-# REMOVED: This flag no longer works as of 1.7.
---insecure-experimental-approve-all-kubelet-csrs-for-group="system:bootstrappers"
-```
-
-An admin would create a `ClusterRoleBinding` targeting that group.
-
-```yml
-# Approve all CSRs for the group "system:bootstrappers"
-kind: ClusterRoleBinding
-apiVersion: rbac.authorization.k8s.io/v1beta1
-metadata:
-  name: auto-approve-csrs-for-group
-subjects:
-- kind: Group
-  name: system:bootstrappers
-  apiGroup: rbac.authorization.k8s.io
-roleRef:
-  kind: ClusterRole
-  name: approve-node-client-csr
-  apiGroup: rbac.authorization.k8s.io
-```
-
-To let a node renew its own credentials, an admin can construct a `ClusterRoleBinding` targeting
-that node's credentials:
-
-```yml
-kind: ClusterRoleBinding
-apiVersion: rbac.authorization.k8s.io/v1beta1
-metadata:
-  name: node1-client-cert-renewal
-subjects:
-- kind: User
-  name: system:node:node-1 # Let "node-1" renew its client certificate.
-  apiGroup: rbac.authorization.k8s.io
-roleRef:
-  kind: ClusterRole
-  name: approve-node-client-renewal-csr
-  apiGroup: rbac.authorization.k8s.io
-```
-
-Deleting the binding will prevent the node from renewing its client credentials, effectively
-removing it from the cluster once its certificate expires.
-
-## kubelet configuration
-To request a client certificate from kube-apiserver, the kubelet first needs a path to a kubeconfig file that contains the
-bootstrap authentication token. You can use `kubectl config set-cluster`, `set-credentials`, and `set-context` to build this kubeconfig. Provide the name `kubelet-bootstrap` to `kubectl config set-credentials` and include `--token=<token-value>` as follows:
-
-```
-kubectl config set-credentials kubelet-bootstrap --token=${BOOTSTRAP_TOKEN} --kubeconfig=bootstrap.kubeconfig
-```
-
-When starting the kubelet, if the file specified by `--kubeconfig` does not exist, the bootstrap kubeconfig is used to request a client certificate from the API server. On approval of the certificate request and receipt back by the kubelet, a kubeconfig file referencing the generated key and obtained certificate is written to the path specified by `--kubeconfig`. The certificate and key file will be placed in the directory specified by `--cert-dir`.
-
-**Note:** The following flags are required to enable this bootstrapping when starting the kubelet:
-
-```
---require-kubeconfig
---bootstrap-kubeconfig="/path/to/bootstrap/kubeconfig"
-```
-
-Additionally, in 1.7 the kubelet implements __alpha__ features for enabling rotation of both its client and/or serving certs.
-These can be enabled through the respective `RotateKubeletClientCertificate` and `RotateKubeletServerCertificate` feature
-flags on the kubelet, but may change in backward incompatible ways in future releases.
-
-```
---feature-gates=RotateKubeletClientCertificate=true,RotateKubeletServerCertificate=true
-```
-
-`RotateKubeletClientCertificate` causes the kubelet to rotate its client certificates by creating new CSRs as its existing
-credentials expire. `RotateKubeletServerCertificate` causes the kubelet to both request a serving certificate after
-bootstrapping its client credentials and rotate the certificate. The serving cert currently does not request DNS or IP
-SANs.
-
-## kubectl approval
-The signing controller does not immediately sign all certificate requests. Instead, it waits until they have been flagged with an
-"Approved" status by an appropriately-privileged user. This is intended to eventually be an automated process handled by an external
-approval controller, but for the alpha version of the API it can be done manually by a cluster administrator using kubectl.
-An administrator can list CSRs with `kubectl get csr` and describe one in detail with `kubectl describe csr <name>`. Before the 1.6 release there were
-[no direct approve/deny commands](https://github.com/kubernetes/kubernetes/issues/30163) so an approver had to update
-the Status field directly ([rough how-to](https://github.com/gtank/csrctl)). Later versions of Kubernetes offer `kubectl certificate approve <name>` and `kubectl certificate deny <name>` commands.

cn/docs/admin/multiple-zones.md

@@ -1,292 +0,0 @@
----
-approvers:
-- jlowdermilk
-- justinsb
-- quinton-hoole
-title: 多区域运行
----
-
-## 介绍
-
-Kubernetes 从v1.2开始支持将集群运行在多个故障域中。
-(GCE 中称其为 "区（Zones）"， AWS 中称其为 "可用区（Availability Zones）"，这里我们也称其为 "区")。
-它是广泛意义上的集群联邦特性的轻量级版本 (之前被称为 ["Ubernetes"](https://github.com/kubernetes/community/blob/{{page.githubbranch}}/contributors/design-proposals/federation/federation.md))。
-完整的集群联邦能够将多个分别运行在不同区或云供应商（或本地数据中心）的集群集中管理。
-然而，很多用户只是希望通过将单一云供应商上的Kubernetes集群运行在多个区域，来提高集群的可用性，
-这就是1.2版本中提供的对多区域的支持。
-(之前被称为 "Ubernetes Lite")。
-
-多区域的支持是有明确限制的： Kubernetes集群能够运行在多个区，但必须在同一个地域内 (云供应商也须一致)。  
-目前只有GCE和AWS自动支持 (尽管在其他云甚至裸机上，也很容易通过为节点和卷添加合适的标签来实现类似的支持)。
-
-
-* TOC
-{:toc}
-
-## 功能
-
-节点启动时，Kubelet自动为其添加区信息的标签。
-
-在单一区域的集群中，Kubernetes 会自动将副本管理器或服务的pod分布到各节点上 (以减轻单实例故障的影响)。
-在多区域的集群中，这种分布的行为扩展到了区域级别
-(以减少区域故障对整体的影响)。  (通过 `SelectorSpreadPriority` 来实现)。
-这种分发是尽力而为（best-effort）的，所以如果集群在各个区之间是异构的
-(比如，各区间的节点数量不同、节点类型不同、pod的资源需求不同等)可能导致pod无法完全均匀地分布。
-如果需要的话，用户可以使用同质的区(节点数量和节点类型相同)来减少区域之间分配不均匀的可能。
-
-当卷被创建时， `PersistentVolumeLabel`准入控制器会自动为其添加区域的标签。
-调度器 (通过 `VolumeZonePredicate` 断言) 会确申领该卷的pod被调度到该卷对应的区域，
-因为卷是不支持跨区挂载的。
-
-## 限制
-
-对多区的支持有一些重要的限制：
-
-* 我们假设不同的区域间在网络上离得很近，所以我们不做任何的区域感知路由。 特别是，通过服务的网络访问可能跨区域 (即使该服务后端pod的其中一些运行在与客户端相同的区域中)，这可能导致额外的延迟和损耗。
-
-* 卷的区域亲和性只对 `PersistentVolume`有效。 例如，如果你在pod的spec中直接指定一个EBS的卷，则不会生效。
-
-* 集群不支持跨云平台或地域 (这些功能需要完整的集群联邦特性支持)。
-
-* 尽管节点位于多区域，目前默认情况下 kube-up 创建的管理节点是单实例的。 所以尽管服务是高可用的，并且能够容忍跨区域的性能损耗，管理平面还是单区域的。 需要高可用的管理平面的用户可以按照 [高可用](/docs/admin/high-availability) 指导来操作。
-
-* 目前StatefulSet的卷动态创建时的跨区域分配，与pod的亲和性/反亲和性不兼容。
-
-* StatefulSet的名称包含破折号 ("-")时，可能影响到卷在区域间的均匀分布。
-
-* 为deployment或pod指定多个PVC时，要求其StorageClass处于同一区域内，否则，相应的PV卷需要在一个区域中静态配置。 另一种方式是使用StatefulSet，这可以确保同一副本所挂载的卷位于同一区内。
-
-
-## 演练
-
-接下来我们将介绍如何同时在 GCE 和 AWS 上创建和使用多区域的集群。 为此，你需要创建一个完整的集群 
-(指定 `MULTIZONE=true`)，然后再次执行 `kube-up`（指定 `KUBE_USE_EXISTING_MASTER=true`）来添加其他区域的节点。
-
-### 创建集群
-
-按正常方式创建集群，但是传入 MULTIZONE 来通知集群对多区域进行管理。 在 us-central1-a 区域创建节点。
-
-GCE:
-
-```shell
-curl -sS https://get.k8s.io | MULTIZONE=true KUBERNETES_PROVIDER=gce KUBE_GCE_ZONE=us-central1-a NUM_NODES=3 bash
-```
-
-AWS:
-
-```shell
-curl -sS https://get.k8s.io | MULTIZONE=true KUBERNETES_PROVIDER=aws KUBE_AWS_ZONE=us-west-2a NUM_NODES=3 bash
-```
-
-该步骤按正常方式创建了集群，仍然运行在单个区域中。
-但 `MULTIZONE=true` 已经开启了多区域的能力。
-
-### 标记节点
-
-查看节点，你可以发现节点上打了区域信息的标签。
-节点位于 `us-central1-a` (GCE) 或者 `us-west-2a` (AWS)。 标签 `failure-domain.beta.kubernetes.io/region` 用于区分地域，
-标签 `failure-domain.beta.kubernetes.io/zone` 用于区分区域。
-
-```shell
-> kubectl get nodes --show-labels
-
-
-NAME                     STATUS                     AGE   VERSION          LABELS
-kubernetes-master        Ready,SchedulingDisabled   6m    v1.6.0+fff5156   beta.kubernetes.io/instance-type=n1-standard-1,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a,kubernetes.io/hostname=kubernetes-master
-kubernetes-minion-87j9   Ready                      6m    v1.6.0+fff5156   beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a,kubernetes.io/hostname=kubernetes-minion-87j9
-kubernetes-minion-9vlv   Ready                      6m    v1.6.0+fff5156   beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a,kubernetes.io/hostname=kubernetes-minion-9vlv
-kubernetes-minion-a12q   Ready                      6m    v1.6.0+fff5156   beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a,kubernetes.io/hostname=kubernetes-minion-a12q
-```
-
-### 添加其它区中的节点
-
-接下来我们复用已有的管理节点，添加运行于其它区域 （us-central1-b或us-west-2b）中的节点。
-再次执行 kube-up， 通过指定 `KUBE_USE_EXISTING_MASTER=true`，
-kube-up 不会创建新的管理节点，而是会复用之前创建的。
-
-GCE:
-
-```shell
-KUBE_USE_EXISTING_MASTER=true MULTIZONE=true KUBERNETES_PROVIDER=gce KUBE_GCE_ZONE=us-central1-b NUM_NODES=3 kubernetes/cluster/kube-up.sh
-```
-
-在 AWS 中我们还需要为新增的子网指定网络CIDR，还有管理节点的内部IP地址。
-
-```shell
-KUBE_USE_EXISTING_MASTER=true MULTIZONE=true KUBERNETES_PROVIDER=aws KUBE_AWS_ZONE=us-west-2b NUM_NODES=3 KUBE_SUBNET_CIDR=172.20.1.0/24 MASTER_INTERNAL_IP=172.20.0.9 kubernetes/cluster/kube-up.sh
-```
-
-
-再次查看节点，3个新增的节点已经启动，并被标记为us-central1-b：
-
-```shell
-> kubectl get nodes --show-labels
-
-NAME                     STATUS                     AGE   VERSION           LABELS
-kubernetes-master        Ready,SchedulingDisabled   16m   v1.6.0+fff5156    beta.kubernetes.io/instance-type=n1-standard-1,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a,kubernetes.io/hostname=kubernetes-master
-kubernetes-minion-281d   Ready                      2m    v1.6.0+fff5156    beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-b,kubernetes.io/hostname=kubernetes-minion-281d
-kubernetes-minion-87j9   Ready                      16m   v1.6.0+fff5156    beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a,kubernetes.io/hostname=kubernetes-minion-87j9
-kubernetes-minion-9vlv   Ready                      16m   v1.6.0+fff5156    beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a,kubernetes.io/hostname=kubernetes-minion-9vlv
-kubernetes-minion-a12q   Ready                      17m   v1.6.0+fff5156    beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a,kubernetes.io/hostname=kubernetes-minion-a12q
-kubernetes-minion-pp2f   Ready                      2m    v1.6.0+fff5156    beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-b,kubernetes.io/hostname=kubernetes-minion-pp2f
-kubernetes-minion-wf8i   Ready                      2m    v1.6.0+fff5156    beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-b,kubernetes.io/hostname=kubernetes-minion-wf8i
-```
-
-### 卷的亲和性
-
-使用动态创建卷的功能创建一个卷 (只有PV持久卷才支持区域亲和性)：
-
-```json
-kubectl create -f - <<EOF
-{
-  "kind": "PersistentVolumeClaim",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "claim1",
-    "annotations": {
-        "volume.alpha.kubernetes.io/storage-class": "foo"
-    }
-  },
-  "spec": {
-    "accessModes": [
-      "ReadWriteOnce"
-    ],
-    "resources": {
-      "requests": {
-        "storage": "5Gi"
-      }
-    }
-  }
-}
-EOF
-```
-
-**注意：** Kubernetes 1.3以上的版本中可以将PVC分发到多个已配置的区域中，在1.2版本中， 动态卷只能创建在管理节点所在的区域内(即这里的 us-central1-a / us-west-2a)；相关issue
-([#23330](https://github.com/kubernetes/kubernetes/issues/23330))
-在1.3后续的版本中已解决。
-
-现在我们验证一下 Kubernetes 自动为创建的PV打上了所在地域和区域的标签。
-
-```shell
-> kubectl get pv --show-labels
-NAME           CAPACITY   ACCESSMODES   STATUS    CLAIM            REASON    AGE       LABELS
-pv-gce-mj4gm   5Gi        RWO           Bound     default/claim1             46s       failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a
-```
-
-现在我们将创建使用这些PVC的pod。
-因为 GCE 的PD存储 / AWS 的EBS 卷 不支持跨区域挂载，
-这意味着相应的pod只能创建在卷所在的区域中。
-
-```yaml
-kubectl create -f - <<EOF
-kind: Pod
-apiVersion: v1
-metadata:
-  name: mypod
-spec:
-  containers:
-    - name: myfrontend
-      image: nginx
-      volumeMounts:
-      - mountPath: "/var/www/html"
-        name: mypd
-  volumes:
-    - name: mypd
-      persistentVolumeClaim:
-        claimName: claim1
-EOF
-```
-
-注意pod被自动创建在了卷所在的区域中，因为云供应商通常不支持卷的跨区域挂载（attach）。
-
-```shell
-> kubectl describe pod mypod | grep Node
-Node:        kubernetes-minion-9vlv/10.240.0.5
-> kubectl get node kubernetes-minion-9vlv --show-labels
-NAME                     STATUS    AGE    VERSION          LABELS
-kubernetes-minion-9vlv   Ready     22m    v1.6.0+fff5156   beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a,kubernetes.io/hostname=kubernetes-minion-9vlv
-```
-
-### Pod的跨区域分布
-
-副本管理器或服务的pod被自动创建在了不同的区域。  首先，在第三个区域内启动节点：
-
-GCE:
-
-```shell
-KUBE_USE_EXISTING_MASTER=true MULTIZONE=true KUBERNETES_PROVIDER=gce KUBE_GCE_ZONE=us-central1-f NUM_NODES=3 kubernetes/cluster/kube-up.sh
-```
-
-AWS:
-
-```shell
-KUBE_USE_EXISTING_MASTER=true MULTIZONE=true KUBERNETES_PROVIDER=aws KUBE_AWS_ZONE=us-west-2c NUM_NODES=3 KUBE_SUBNET_CIDR=172.20.2.0/24 MASTER_INTERNAL_IP=172.20.0.9 kubernetes/cluster/kube-up.sh
-```
-
-验证你现在在3个区域内拥有节点:
-
-```shell
-kubectl get nodes --show-labels
-```
-
-创建 guestbook-go 示例应用， 它包含一个副本数为3的RC，运行一个简单的网络应用：
-
-```shell
-find kubernetes/examples/guestbook-go/ -name '*.json' | xargs -I {} kubectl create -f {}
-```
-
-Pod应该分布在全部3个区域上：
-
-```shell
->  kubectl describe pod -l app=guestbook | grep Node
-Node:        kubernetes-minion-9vlv/10.240.0.5
-Node:        kubernetes-minion-281d/10.240.0.8
-Node:        kubernetes-minion-olsh/10.240.0.11
-
- > kubectl get node kubernetes-minion-9vlv kubernetes-minion-281d kubernetes-minion-olsh --show-labels
-NAME                     STATUS    AGE    VERSION          LABELS
-kubernetes-minion-9vlv   Ready     34m    v1.6.0+fff5156   beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a,kubernetes.io/hostname=kubernetes-minion-9vlv
-kubernetes-minion-281d   Ready     20m    v1.6.0+fff5156   beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-b,kubernetes.io/hostname=kubernetes-minion-281d
-kubernetes-minion-olsh   Ready     3m     v1.6.0+fff5156   beta.kubernetes.io/instance-type=n1-standard-2,failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-f,kubernetes.io/hostname=kubernetes-minion-olsh
-```
-
-
-负载平衡器覆盖集群中的所有区域； guestbook-go 示例包含一个
-负载均衡服务的例子：
-
-```shell
-> kubectl describe service guestbook | grep LoadBalancer.Ingress
-LoadBalancer Ingress:   130.211.126.21
-
-> ip=130.211.126.21
-
-> curl -s http://${ip}:3000/env | grep HOSTNAME
-  "HOSTNAME": "guestbook-44sep",
-
-> (for i in `seq 20`; do curl -s http://${ip}:3000/env | grep HOSTNAME; done)  | sort | uniq
-  "HOSTNAME": "guestbook-44sep",
-  "HOSTNAME": "guestbook-hum5n",
-  "HOSTNAME": "guestbook-ppm40",
-```
-
-负载平衡器正确指向了所有的pod，即使它们位于不同的区域内。
-
-### 停止集群
-
-使用完成后，进行清理：
-
-GCE:
-
-```shell
-KUBERNETES_PROVIDER=gce KUBE_USE_EXISTING_MASTER=true KUBE_GCE_ZONE=us-central1-f kubernetes/cluster/kube-down.sh
-KUBERNETES_PROVIDER=gce KUBE_USE_EXISTING_MASTER=true KUBE_GCE_ZONE=us-central1-b kubernetes/cluster/kube-down.sh
-KUBERNETES_PROVIDER=gce KUBE_GCE_ZONE=us-central1-a kubernetes/cluster/kube-down.sh
-```
-
-AWS:
-
-```shell
-KUBERNETES_PROVIDER=aws KUBE_USE_EXISTING_MASTER=true KUBE_AWS_ZONE=us-west-2c kubernetes/cluster/kube-down.sh
-KUBERNETES_PROVIDER=aws KUBE_USE_EXISTING_MASTER=true KUBE_AWS_ZONE=us-west-2b kubernetes/cluster/kube-down.sh
-KUBERNETES_PROVIDER=aws KUBE_AWS_ZONE=us-west-2a kubernetes/cluster/kube-down.sh
-```

cn/docs/admin/ovs-networking.md

@@ -1,22 +0,0 @@
----
-assignees:
-- thockin
-title: Kubernetes OpenVSwitch GRE/VxLAN 网络
----
-
-本文档介绍了如何使用OpenVSwitch，在跨nodes的pods之间设置网络。
-隧道类型可以是GRE或者是VxLAN。如需在网络内执行大规模隔离时，最好使用VxLAN。
-
-![OVS Networking](/images/docs/ovs-networking.png)
-
-Kubernetes中Vagrant的设置如下：
-
-docker网桥被brctl生成的Linux网桥(kbr0)所代替，kbr0是具有256个地址空间的子网。总的来说，node会得到10.244.x.0/24的子网，docker上配置使用的网桥会代替默认docker0的网桥。
-
-另外，OVS网桥创建(obr0)，并将其作为端口添加到kbr0的网桥中。所有OVS网桥通过GRE隧道连接所有的nodes。因此，每个node都有一个到其他nodes的出站GRE隧道。这个隧道没有必要是一个完整的网状物，但是越像网状结构越好。在网桥上开启STP(生成树)模式以防止环路的发生。
-
-路由规则允许任何10.244.0.0/16通过与隧道相连的OVS网桥到达目标。
-
-
-
-

cn/docs/concepts/architecture/master-node-communication.md

@@ -1,71 +0,0 @@
----
-approvers:
-- dchen1107
-- roberthbailey
-- liggitt
-
-title: Master 节点通信
----
-
-* TOC
-{:toc}
-
-
-## 概览
-
-
-本文对 Master 节点（确切说是 apiserver）和 Kubernetes 集群之间的通信路径进行了分类。目的是为了让用户能够自定义他们的安装，对网络配置进行加固，使得集群能够在不可信的网络上（或者在一个云服务商完全公共的 IP 上）运行。
-
-
-## Cluster -> Master
-
-
-所有从集群到 master 的通信路径都终止于 apiserver（其它 master 组件没有被设计为可暴露远程服务）。在一个典型的部署中，apiserver 被配置为在一个安全的 HTTPS 端口（443）上监听远程连接并启用一种或多种形式的客户端[身份认证](/docs/admin/authentication/)机制。一种或多种客户端[身份认证](/docs/admin/authentication/)机制应该被启用，特别是在允许使用 [匿名请求](/docs/admin/authentication/#anonymous-requests) 或 [service account tokens](/docs/admin/authentication/#service-account-tokens) 的时候。
-
-
-应该使用集群的公共根证书开通节点，如此它们就能够基于有效的客户端凭据安全的连接 apiserver。例如：在一个默认的 GCE 部署中，客户端凭据以客户端证书的形式提供给 kubelet。请查看 [kubelet TLS bootstrapping](/docs/admin/kubelet-tls-bootstrapping/) 获取如何自动提供 kubelet 客户端证书。
-
-
-想要连接到 apiserver 的 Pods 可以使用一个 service account 安全的进行连接。这种情况下，当 Pods 被实例化时 Kubernetes 将自动的把公共根证书和一个有效的不记名令牌注入到 pod 里。`kubernetes` service （所有 namespaces 中）都配置了一个虚拟 IP 地址，用于转发（通过 kube-proxy）请求到 apiserver 的 HTTPS endpoint。
-
-
-Master 组件通过非安全（没有加密或认证）端口和集群的 apiserver 通信。这个端口通常只在 master 节点的 localhost 接口暴露，这样，所有在相同机器上运行的 master 组件就能和集群的 apiserver 通信。一段时间以后，master 组件将变为使用带身份认证和权限验证的安全端口（查看[#13598](https://github.com/kubernetes/kubernetes/issues/13598)）。
-
-
-这样的结果使得从集群（在节点上运行的 nodes 和 pods）到 master 的缺省连接操作模式默认被保护，能够在不可信或公网中运行。
-
-
-## Master -> Cluster
-
-
-从 master（apiserver）到集群有两种主要的通信路径。第一种是从 apiserver 到集群中每个节点上运行的 kubelet 进程。第二种是从 apiserver 通过它的代理功能到任何 node、pod 或者 service。
-
-
-### apiserver -> kubelet
-
-
-从 apiserver 到 kubelet 的连接用于获取 pods 日志、连接（通过 kubectl）运行中的 pods，以及使用 kubele 的端口转发功能。这些连接终止于 kubelet 的 HTTPS endpoint。
-
-
-默认的，apiserver 不会验证 kubelet 的服务证书，这会导致连接遭到中间人攻击，因而在不可信或公共网络上是不安全的。  
-
-
-为了对这个连接进行认证，请使用 `--kubelet-certificate-authority` 标记给 apiserver 提供一个根证书捆绑，用于 kubelet 的服务证书。
-
-
-如果这样不可能，又要求避免在不可信的或公共的网络上进行连接，请在 apiserver 和 kubelet 之间使用 [SSH 隧道](/docs/concepts/architecture/master-node-communication/#ssh-tunnels)。
-
-
-最后，应该启用[Kubelet 用户认证和/或权限认证](/docs/admin/kubelet-authentication-authorization/)来保护 kubelet API。
-
-
-### apiserver -> nodes, pods, and services
-
-
-从 apiserver 到 node、pod或者service 的连接默认为纯 HTTP 方式，因此既没有认证，也没有加密。他们能够通过给API URL 中的 node、pod 或 service 名称添加前缀 `https:` 来运行在安全的 HTTPS 连接上。但他们即不会认证 HTTPS endpoint 提供的证书，也不会提供客户端证书。这样虽然连接是加密的，但它不会提供任何完整性保证。这些连接**目前还不能安全的**在不可信的或公共的网络上运行。
-
-
-### SSH 隧道
-
-
-[Google Container Engine](https://cloud.google.com/container-engine/docs/) 使用 SSH 隧道保护 Master -> Cluster 通信路径。在这种配置下，apiserver 发起一个到集群中每个节点的 SSH 隧道（连接到在 22 端口监听的 ssh 服务）并通过这个隧道传输所有到 kubelet、node、pod 或者 service 的流量。这个隧道保证流量不会在集群运行的私有 GCE 网络之外暴露。