Merge pull request #1321 from lukemarsden/official-packages

Update kubeadm guide to use official stable deb and rpm repos
Use the official 1.4.0 image.
2016-09-27 08:07:30 -07:00 · 2016-09-27 15:58:01 +01:00 · 2016-09-27 15:51:32 +01:00
5382 changed files with 272935 additions and 752277 deletions
@@ -1 +0,0 @@
-**
@@ -1,17 +0,0 @@
-[*]
-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
@@ -1,23 +0,0 @@
---
-name: Bug Report
-about: Report a bug encountered with Kubernetes Website
-labels:
- kind/bug
---
-**This is a Bug Report**
-
-<!-- Thanks for filing an issue! Before submitting, please fill in the following information. -->
-<!-- See https://kubernetes.io/docs/contribute/start/ for guidance on writing an actionable issue description. -->
-
-<!--Required Information-->
-**Problem:**
-
-**Proposed Solution:**
-
-**Page to Update:**
-https://kubernetes.io/...
-
-<!--Optional Information (remove the comment tags around information you would like to include)-->
-<!--Kubernetes Version:-->
-
-<!--Additional Information:-->
@@ -1,18 +0,0 @@
---
-name: Feature Request
-about: Suggest a/an feature/enhancement to the Kubernetes Website project
-labels:
- kind/feature
---
-**This is a Feature Request**
-
-<!-- Please only use this template for submitting feature/enhancement requests -->
-<!-- See https://kubernetes.io/docs/contribute/start/ for guidance on writing an actionable issue description. -->
-
-**What would you like to be added**
-<!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. -->
-
-**Why is this needed**
-
-**Comments**
-<!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). -->
@@ -1,19 +0,0 @@
---
-name: Support Request
-about: Support request or question relating to Kubernetes Dashboard project
-labels:
- triage/support
---
-**This is Support**
-
-<!--
-STOP -- PLEASE READ!
-
-GitHub is not the right place for support requests.
-
-If you're looking for help, check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes)
-
-You can also post your question on the [Kubernetes Slack](http://slack.k8s.io/) or the [Discuss Kubernetes](https://discuss.kubernetes.io/) forum.
-
-If the matter is security related, please disclose it privately via https://kubernetes.io/security/.
-->
@@ -1,16 +0,0 @@
->^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-> Remember to delete this note before submitting your pull request.
->
-> For pull requests on 1.15 Features: set Milestone to 1.15 and Base Branch to dev-1.15
-> 
-> For pull requests on Chinese localization, set Base Branch to release-1.14
->
-> For pull requests on Korean Localization: set Base Branch to dev-1.14-ko.\<latest team milestone>
->
-> If you need Help on editing and submitting pull requests, visit:
-> https://kubernetes.io/docs/contribute/start/#improve-existing-content.
->
-> If you need Help on choosing which branch to use, visit:
-> https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use.
->^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
->
@@ -1,36 +1,7 @@
 **/.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
-
-# swap
-[._]*.s[a-v][a-z]
-[._]*.sw[a-p]
-[._]s[a-v][a-z]
-[._]sw[a-p]
-# session
-Session.vim
-# temporary
-.netrwhist
-*~
-# auto-generated tag files
-tags
-
-kubernetes.github.io.iml
-
-nohup.out
-
-# Hugo output
-public/
-resources/
-
-# Netlify Functions build output
-package-lock.json
-functions/
-node_modules/
@@ -0,0 +1,16 @@
+language: go
+go:
+  - 1.6.2
+
+# Don't want default ./... here:
+install:
+- export PATH=$GOPATH/bin:$PATH
+- mkdir -p $HOME/gopath/src/k8s.io
+- mv $TRAVIS_BUILD_DIR $HOME/gopath/src/k8s.io/kubernetes.github.io
+- go get -t -v k8s.io/kubernetes.github.io/test
+- git clone --depth=50 --branch=master https://github.com/kubernetes/md-check $HOME/gopath/src/k8s.io/md-check
+- go get -t -v k8s.io/md-check
+
+script:
+- go test -v k8s.io/kubernetes.github.io/test
+- $GOPATH/bin/md-check --root-dir=$HOME/gopath/src/k8s.io/kubernetes.github.io
@@ -0,0 +1,68 @@
+---
+layout: docwithnav
+title: 404 Error!
+permalink: /404.html
+---
+<script language="JavaScript">
+$( document ).ready(function() {
+  var oldURLs=["/README.md","/README.html",".html",".md","/v1.1/","/v1.0/"];
+  var fwdDirs=["examples/","cluster/","docs/devel","docs/design"];
+  var doRedirect = false;
+  var notHere = false;
+  var forwardingURL=window.location.href;
+  if (forwardingURL.indexOf("third_party/swagger-ui") > -1)
+  {
+    notHere = true;
+    window.location.replace("http://kubernetes.io/kubernetes/third_party/swagger-ui/");
+  }
+  if (forwardingURL.indexOf("resource-quota") > -1)
+  {
+    notHere = true;
+    window.location.replace("http://kubernetes.io/docs/admin/resourcequota/");
+  }
+  if (forwardingURL.indexOf("horizontal-pod-autoscaler") > -1)
+  {
+    notHere = true;
+    window.location.replace("http://kubernetes.io/docs/user-guide/horizontal-pod-autoscaling/");
+  } 
+  if (forwardingURL.indexOf("docs/roadmap") > -1)
+  {
+    notHere = true;
+    window.location.replace("https://github.com/kubernetes/kubernetes/milestones/");
+  }
+  if (forwardingURL.indexOf("api-ref/") > -1) 
+  {
+    notHere = true;
+    window.location.replace("http://kubernetes.io/docs/api/");
+  }
+  if (forwardingURL.indexOf("docs/user-guide/overview") > -1)
+  {
+    notHere = true;
+    window.location.replace("http://kubernetes.io/docs/whatisk8s/");
+  }
+  for (i=0;i<fwdDirs.length;i++) {
+    if (forwardingURL.indexOf(fwdDirs[i]) > -1)
+    {
+      var urlPieces = forwardingURL.split(fwdDirs[i]);
+      var newURL = "https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/" + fwdDirs[i] + urlPieces[1];
+      notHere = true;
+      window.location.replace(newURL);
+    }
+  }
+  if (!notHere) {
+    for (i=0;i<oldURLs.length;i++) {
+      if (forwardingURL.indexOf(oldURLs[i]) > -1)
+      {
+        doRedirect=true;
+        forwardingURL=forwardingURL.replace(oldURLs[i],"/");
+      }
+    }
+    if (doRedirect)
+    {
+      window.location.replace(forwardingURL);
+    };
+  }
+});
+</script>
+
+Sorry, this page was not found. :(
@@ -0,0 +1,2 @@
+kubernetes.io
+kubernet.es
@@ -1,37 +0,0 @@
-# Contributing to Kubernetes Documentation
-
-**First off, thanks for taking the time to contribute!**
-
-The following is a set of guidelines for contributing to Kubernetes documentation, hosted at [Kubernetes.io](http://kubernetes.io/).
-These are just guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
-
-## Before you get started
-
-### 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 the
-[Kubernetes Code of Conduct Committee](https://github.com/kubernetes/community/tree/master/committee-code-of-conduct) <conduct@kubernetes.io>.
-
-### Documentation and Site Decisions
-
-The [Kubernetes SIG Docs Discussion Group](https://groups.google.com/forum/#!forum/kubernetes-sig-docs) is the discussion group for doc releases, suggested site improvements, and improving the doc contribution experience. If you are planning to be a regular contributor, join this group to stay informed and involved.
-
-### 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/).
-
-
-## Contributing to Documentation
-
-### Reporting Documentation Issues
-
-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/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.
-
-### Submitting Documentation Pull Requests
-
-If you're fixing an issue in the existing documentation, you should submit a PR against the master branch.  Follow [these instructions to create a documentation pull request against the kubernetes.io repository](http://kubernetes.io/docs/home/contribute/create-pull-request/).
@@ -1,30 +0,0 @@
-# Credit to Julien Guyomard (https://github.com/jguyomard). This Dockerfile
-# is essentially based on his Dockerfile at
-# https://github.com/jguyomard/docker-hugo/blob/master/Dockerfile. The only significant
-# change is that the Hugo version is now an overridable argument rather than a fixed
-# environment variable.
-
-FROM alpine:latest
-
-MAINTAINER Luc Perkins <lperkins@linuxfoundation.org>
-
-RUN apk add --no-cache \
-    curl \
-    git \
-    openssh-client \
-    rsync \
-    build-base \
-    libc6-compat
-
-ARG HUGO_VERSION
-
-RUN mkdir -p /usr/local/src && \
-    cd /usr/local/src && \
-    curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_Linux-64bit.tar.gz | tar -xz && \
-    mv hugo /usr/local/bin/hugo && \
-    addgroup -Sg 1000 hugo && \
-    adduser -Sg hugo -u 1000 -h /src hugo
-
-WORKDIR /src
-
-EXPOSE 1313
@@ -0,0 +1,20 @@
+source "https://rubygems.org"
+
+gem "jekyll", "3.2.1"
+gem "jekyll-sass-converter", "1.3.0"
+gem "minima", "1.1.0"
+gem "kramdown", "1.11.1"
+gem "liquid", "3.0.6"
+gem "rouge", "1.11.1"
+gem "jemoji", "0.7.0"
+gem "jekyll-mentions", "1.2.0"
+gem "jekyll-redirect-from", "0.11.0"
+gem "jekyll-sitemap", "0.10.0"
+gem "jekyll-feed", "0.5.1"
+gem "jekyll-gist", "1.4.0"
+gem "jekyll-paginate", "1.1.0"
+gem "jekyll-coffeescript", "1.0.1"
+gem "jekyll-seo-tag", "2.0.0"
+gem "jekyll-github-metadata", "2.0.2"
+gem "listen", "3.0.6"
+gem "activesupport", "4.2.7"
@@ -0,0 +1,119 @@
+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.4.0)
+    coffee-script (2.4.1)
+      coffee-script-source
+      execjs
+    coffee-script-source (1.10.0)
+    colorator (1.1.0)
+    execjs (2.7.0)
+    faraday (0.9.2)
+      multipart-post (>= 1.2, < 3)
+    ffi (1.9.14)
+    forwardable-extended (2.6.0)
+    gemoji (2.1.0)
+    html-pipeline (2.4.2)
+      activesupport (>= 2)
+      nokogiri (>= 1.4)
+    i18n (0.7.0)
+    jekyll (3.2.1)
+      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-coffeescript (1.0.1)
+      coffee-script (~> 2.2)
+    jekyll-feed (0.5.1)
+    jekyll-gist (1.4.0)
+      octokit (~> 4.2)
+    jekyll-github-metadata (2.0.2)
+      jekyll (~> 3.1)
+      octokit (~> 4.0)
+    jekyll-mentions (1.2.0)
+      activesupport (~> 4.0)
+      html-pipeline (~> 2.3)
+      jekyll (~> 3.0)
+    jekyll-paginate (1.1.0)
+    jekyll-redirect-from (0.11.0)
+      jekyll (>= 2.0)
+    jekyll-sass-converter (1.3.0)
+      sass (~> 3.2)
+    jekyll-seo-tag (2.0.0)
+      jekyll (~> 3.1)
+    jekyll-sitemap (0.10.0)
+    jekyll-watch (1.5.0)
+      listen (~> 3.0, < 3.1)
+    jemoji (0.7.0)
+      activesupport (~> 4.0)
+      gemoji (~> 2.0)
+      html-pipeline (~> 2.2)
+      jekyll (>= 3.0)
+    json (1.8.3)
+    kramdown (1.11.1)
+    liquid (3.0.6)
+    listen (3.0.6)
+      rb-fsevent (>= 0.9.3)
+      rb-inotify (>= 0.9.7)
+    mercenary (0.3.6)
+    mini_portile2 (2.1.0)
+    minima (1.1.0)
+    minitest (5.9.0)
+    multipart-post (2.0.0)
+    nokogiri (1.6.8)
+      mini_portile2 (~> 2.1.0)
+      pkg-config (~> 1.1.7)
+    octokit (4.3.0)
+      sawyer (~> 0.7.0, >= 0.5.3)
+    pathutil (0.14.0)
+      forwardable-extended (~> 2.6)
+    pkg-config (1.1.7)
+    rb-fsevent (0.9.7)
+    rb-inotify (0.9.7)
+      ffi (>= 0.5.0)
+    rouge (1.11.1)
+    safe_yaml (1.0.4)
+    sass (3.4.22)
+    sawyer (0.7.0)
+      addressable (>= 2.3.5, < 2.5)
+      faraday (~> 0.8, < 0.10)
+    thread_safe (0.3.5)
+    tzinfo (1.2.2)
+      thread_safe (~> 0.1)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  activesupport (= 4.2.7)
+  jekyll (= 3.2.1)
+  jekyll-coffeescript (= 1.0.1)
+  jekyll-feed (= 0.5.1)
+  jekyll-gist (= 1.4.0)
+  jekyll-github-metadata (= 2.0.2)
+  jekyll-mentions (= 1.2.0)
+  jekyll-paginate (= 1.1.0)
+  jekyll-redirect-from (= 0.11.0)
+  jekyll-sass-converter (= 1.3.0)
+  jekyll-seo-tag (= 2.0.0)
+  jekyll-sitemap (= 0.10.0)
+  jemoji (= 0.7.0)
+  kramdown (= 1.11.1)
+  liquid (= 3.0.6)
+  listen (= 3.0.6)
+  minima (= 1.1.0)
+  rouge (= 1.11.1)
+
+BUNDLED WITH
+   1.11.2
@@ -0,0 +1,22 @@
+<!-- Thanks for filing an issue! Before submitting, please fill in the following information. -->
+
+<!--Required Information-->
+
+**This is a...** 
+<!-- choose one by changing [ ] to [x] -->
+- [ ] Feature Request
+- [ ] Bug Report
+
+**Problem:**
+
+
+**Proposed Solution:**
+
+
+**Page to Update:**
+http://kubernetes.io/...
+
+<!--Optional Information (remove the comment tags around information you would like to include)-->
+<!--Kubernetes Version:-->
+
+<!--Additional Information:-->
@@ -1,395 +1,201 @@
-Attribution 4.0 International
-
-=======================================================================
-
-Creative Commons Corporation ("Creative Commons") is not a law firm and
-does not provide legal services or legal advice. Distribution of
-Creative Commons public licenses does not create a lawyer-client or
-other relationship. Creative Commons makes its licenses and related
-information available on an "as-is" basis. Creative Commons gives no
-warranties regarding its licenses, any material licensed under their
-terms and conditions, or any related information. Creative Commons
-disclaims all liability for damages resulting from their use to the
-fullest extent possible.
-
-Using Creative Commons Public Licenses
-
-Creative Commons public licenses provide a standard set of terms and
-conditions that creators and other rights holders may use to share
-original works of authorship and other material subject to copyright
-and certain other rights specified in the public license below. The
-following considerations are for informational purposes only, are not
-exhaustive, and do not form part of our licenses.
-
-     Considerations for licensors: Our public licenses are
-     intended for use by those authorized to give the public
-     permission to use material in ways otherwise restricted by
-     copyright and certain other rights. Our licenses are
-     irrevocable. Licensors should read and understand the terms
-     and conditions of the license they choose before applying it.
-     Licensors should also secure all rights necessary before
-     applying our licenses so that the public can reuse the
-     material as expected. Licensors should clearly mark any
-     material not subject to the license. This includes other CC-
-     licensed material, or material used under an exception or
-     limitation to copyright. More considerations for licensors:
-	wiki.creativecommons.org/Considerations_for_licensors
-
-     Considerations for the public: By using one of our public
-     licenses, a licensor grants the public permission to use the
-     licensed material under specified terms and conditions. If
-     the licensor's permission is not necessary for any reason--for
-     example, because of any applicable exception or limitation to
-     copyright--then that use is not regulated by the license. Our
-     licenses grant only permissions under copyright and certain
-     other rights that a licensor has authority to grant. Use of
-     the licensed material may still be restricted for other
-     reasons, including because others have copyright or other
-     rights in the material. A licensor may make special requests,
-     such as asking that all changes be marked or described.
-     Although not required by our licenses, you are encouraged to
-     respect those requests where reasonable. More_considerations
-     for the public: 
-	wiki.creativecommons.org/Considerations_for_licensees
-
-=======================================================================
-
-Creative Commons Attribution 4.0 International Public License
-
-By exercising the Licensed Rights (defined below), You accept and agree
-to be bound by the terms and conditions of this Creative Commons
-Attribution 4.0 International Public License ("Public License"). To the
-extent this Public License may be interpreted as a contract, You are
-granted the Licensed Rights in consideration of Your acceptance of
-these terms and conditions, and the Licensor grants You such rights in
-consideration of benefits the Licensor receives from making the
-Licensed Material available under these terms and conditions.
-
-
-Section 1 -- Definitions.
-
-  a. Adapted Material means material subject to Copyright and Similar
-     Rights that is derived from or based upon the Licensed Material
-     and in which the Licensed Material is translated, altered,
-     arranged, transformed, or otherwise modified in a manner requiring
-     permission under the Copyright and Similar Rights held by the
-     Licensor. For purposes of this Public License, where the Licensed
-     Material is a musical work, performance, or sound recording,
-     Adapted Material is always produced where the Licensed Material is
-     synched in timed relation with a moving image.
-
-  b. Adapter's License means the license You apply to Your Copyright
-     and Similar Rights in Your contributions to Adapted Material in
-     accordance with the terms and conditions of this Public License.
-
-  c. Copyright and Similar Rights means copyright and/or similar rights
-     closely related to copyright including, without limitation,
-     performance, broadcast, sound recording, and Sui Generis Database
-     Rights, without regard to how the rights are labeled or
-     categorized. For purposes of this Public License, the rights
-     specified in Section 2(b)(1)-(2) are not Copyright and Similar
-     Rights.
-
-  d. Effective Technological Measures means those measures that, in the
-     absence of proper authority, may not be circumvented under laws
-     fulfilling obligations under Article 11 of the WIPO Copyright
-     Treaty adopted on December 20, 1996, and/or similar international
-     agreements.
-
-  e. Exceptions and Limitations means fair use, fair dealing, and/or
-     any other exception or limitation to Copyright and Similar Rights
-     that applies to Your use of the Licensed Material.
-
-  f. Licensed Material means the artistic or literary work, database,
-     or other material to which the Licensor applied this Public
-     License.
-
-  g. Licensed Rights means the rights granted to You subject to the
-     terms and conditions of this Public License, which are limited to
-     all Copyright and Similar Rights that apply to Your use of the
-     Licensed Material and that the Licensor has authority to license.
-
-  h. Licensor means the individual(s) or entity(ies) granting rights
-     under this Public License.
-
-  i. Share means to provide material to the public by any means or
-     process that requires permission under the Licensed Rights, such
-     as reproduction, public display, public performance, distribution,
-     dissemination, communication, or importation, and to make material
-     available to the public including in ways that members of the
-     public may access the material from a place and at a time
-     individually chosen by them.
-
-  j. Sui Generis Database Rights means rights other than copyright
-     resulting from Directive 96/9/EC of the European Parliament and of
-     the Council of 11 March 1996 on the legal protection of databases,
-     as amended and/or succeeded, as well as other essentially
-     equivalent rights anywhere in the world.
-
-  k. You means the individual or entity exercising the Licensed Rights
-     under this Public License. Your has a corresponding meaning.
-
-
-Section 2 -- Scope.
-
-  a. License grant.
-
-       1. Subject to the terms and conditions of this Public License,
-          the Licensor hereby grants You a worldwide, royalty-free,
-          non-sublicensable, non-exclusive, irrevocable license to
-          exercise the Licensed Rights in the Licensed Material to:
-
-            a. reproduce and Share the Licensed Material, in whole or
-               in part; and
-
-            b. produce, reproduce, and Share Adapted Material.
-
-       2. Exceptions and Limitations. For the avoidance of doubt, where
-          Exceptions and Limitations apply to Your use, this Public
-          License does not apply, and You do not need to comply with
-          its terms and conditions.
-
-       3. Term. The term of this Public License is specified in Section
-          6(a).
-
-       4. Media and formats; technical modifications allowed. The
-          Licensor authorizes You to exercise the Licensed Rights in
-          all media and formats whether now known or hereafter created,
-          and to make technical modifications necessary to do so. The
-          Licensor waives and/or agrees not to assert any right or
-          authority to forbid You from making technical modifications
-          necessary to exercise the Licensed Rights, including
-          technical modifications necessary to circumvent Effective
-          Technological Measures. For purposes of this Public License,
-          simply making modifications authorized by this Section 2(a)
-          (4) never produces Adapted Material.
-
-       5. Downstream recipients.
-
-            a. Offer from the Licensor -- Licensed Material. Every
-               recipient of the Licensed Material automatically
-               receives an offer from the Licensor to exercise the
-               Licensed Rights under the terms and conditions of this
-               Public License.
-
-            b. No downstream restrictions. You may not offer or impose
-               any additional or different terms or conditions on, or
-               apply any Effective Technological Measures to, the
-               Licensed Material if doing so restricts exercise of the
-               Licensed Rights by any recipient of the Licensed
-               Material.
-
-       6. No endorsement. Nothing in this Public License constitutes or
-          may be construed as permission to assert or imply that You
-          are, or that Your use of the Licensed Material is, connected
-          with, or sponsored, endorsed, or granted official status by,
-          the Licensor or others designated to receive attribution as
-          provided in Section 3(a)(1)(A)(i).
-
-  b. Other rights.
-
-       1. Moral rights, such as the right of integrity, are not
-          licensed under this Public License, nor are publicity,
-          privacy, and/or other similar personality rights; however, to
-          the extent possible, the Licensor waives and/or agrees not to
-          assert any such rights held by the Licensor to the limited
-          extent necessary to allow You to exercise the Licensed
-          Rights, but not otherwise.
-
-       2. Patent and trademark rights are not licensed under this
-          Public License.
-
-       3. To the extent possible, the Licensor waives any right to
-          collect royalties from You for the exercise of the Licensed
-          Rights, whether directly or through a collecting society
-          under any voluntary or waivable statutory or compulsory
-          licensing scheme. In all other cases the Licensor expressly
-          reserves any right to collect such royalties.
-
-
-Section 3 -- License Conditions.
-
-Your exercise of the Licensed Rights is expressly made subject to the
-following conditions.
-
-  a. Attribution.
-
-       1. If You Share the Licensed Material (including in modified
-          form), You must:
-
-            a. retain the following if it is supplied by the Licensor
-               with the Licensed Material:
-
-                 i. identification of the creator(s) of the Licensed
-                    Material and any others designated to receive
-                    attribution, in any reasonable manner requested by
-                    the Licensor (including by pseudonym if
-                    designated);
-
-                ii. a copyright notice;
-
-               iii. a notice that refers to this Public License;
-
-                iv. a notice that refers to the disclaimer of
-                    warranties;
-
-                 v. a URI or hyperlink to the Licensed Material to the
-                    extent reasonably practicable;
-
-            b. indicate if You modified the Licensed Material and
-               retain an indication of any previous modifications; and
-
-            c. indicate the Licensed Material is licensed under this
-               Public License, and include the text of, or the URI or
-               hyperlink to, this Public License.
-
-       2. You may satisfy the conditions in Section 3(a)(1) in any
-          reasonable manner based on the medium, means, and context in
-          which You Share the Licensed Material. For example, it may be
-          reasonable to satisfy the conditions by providing a URI or
-          hyperlink to a resource that includes the required
-          information.
-
-       3. If requested by the Licensor, You must remove any of the
-          information required by Section 3(a)(1)(A) to the extent
-          reasonably practicable.
-
-       4. If You Share Adapted Material You produce, the Adapter's
-          License You apply must not prevent recipients of the Adapted
-          Material from complying with this Public License.
-
-
-Section 4 -- Sui Generis Database Rights.
-
-Where the Licensed Rights include Sui Generis Database Rights that
-apply to Your use of the Licensed Material:
-
-  a. for the avoidance of doubt, Section 2(a)(1) grants You the right
-     to extract, reuse, reproduce, and Share all or a substantial
-     portion of the contents of the database;
-
-  b. if You include all or a substantial portion of the database
-     contents in a database in which You have Sui Generis Database
-     Rights, then the database in which You have Sui Generis Database
-     Rights (but not its individual contents) is Adapted Material; and
-
-  c. You must comply with the conditions in Section 3(a) if You Share
-     all or a substantial portion of the contents of the database.
-
-For the avoidance of doubt, this Section 4 supplements and does not
-replace Your obligations under this Public License where the Licensed
-Rights include other Copyright and Similar Rights.
-
-
-Section 5 -- Disclaimer of Warranties and Limitation of Liability.
-
-  a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
-     EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
-     AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
-     ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
-     IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
-     WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
-     PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
-     ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
-     KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
-     ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
-
-  b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
-     TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
-     NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
-     INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
-     COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
-     USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
-     ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
-     DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
-     IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
-
-  c. The disclaimer of warranties and limitation of liability provided
-     above shall be interpreted in a manner that, to the extent
-     possible, most closely approximates an absolute disclaimer and
-     waiver of all liability.
-
-
-Section 6 -- Term and Termination.
-
-  a. This Public License applies for the term of the Copyright and
-     Similar Rights licensed here. However, if You fail to comply with
-     this Public License, then Your rights under this Public License
-     terminate automatically.
-
-  b. Where Your right to use the Licensed Material has terminated under
-     Section 6(a), it reinstates:
-
-       1. automatically as of the date the violation is cured, provided
-          it is cured within 30 days of Your discovery of the
-          violation; or
-
-       2. upon express reinstatement by the Licensor.
-
-     For the avoidance of doubt, this Section 6(b) does not affect any
-     right the Licensor may have to seek remedies for Your violations
-     of this Public License.
-
-  c. For the avoidance of doubt, the Licensor may also offer the
-     Licensed Material under separate terms or conditions or stop
-     distributing the Licensed Material at any time; however, doing so
-     will not terminate this Public License.
-
-  d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
-     License.
-
-
-Section 7 -- Other Terms and Conditions.
-
-  a. The Licensor shall not be bound by any additional or different
-     terms or conditions communicated by You unless expressly agreed.
-
-  b. Any arrangements, understandings, or agreements regarding the
-     Licensed Material not stated herein are separate from and
-     independent of the terms and conditions of this Public License.
-
-
-Section 8 -- Interpretation.
-
-  a. For the avoidance of doubt, this Public License does not, and
-     shall not be interpreted to, reduce, limit, restrict, or impose
-     conditions on any use of the Licensed Material that could lawfully
-     be made without permission under this Public License.
-
-  b. To the extent possible, if any provision of this Public License is
-     deemed unenforceable, it shall be automatically reformed to the
-     minimum extent necessary to make it enforceable. If the provision
-     cannot be reformed, it shall be severed from this Public License
-     without affecting the enforceability of the remaining terms and
-     conditions.
-
-  c. No term or condition of this Public License will be waived and no
-     failure to comply consented to unless expressly agreed to by the
-     Licensor.
-
-  d. Nothing in this Public License constitutes or may be interpreted
-     as a limitation upon, or waiver of, any privileges and immunities
-     that apply to the Licensor or You, including from the legal
-     processes of any jurisdiction or authority.
-
-
-=======================================================================
-
-Creative Commons is not a party to its public
-licenses. Notwithstanding, Creative Commons may elect to apply one of
-its public licenses to material it publishes and in those instances
-will be considered the "Licensor." The text of the Creative Commons
-public licenses is dedicated to the public domain under the CC0 Public
-Domain Dedication. Except for the limited purpose of indicating that
-material is shared under a Creative Commons public license or as
-otherwise permitted by the Creative Commons policies published at
-creativecommons.org/policies, Creative Commons does not authorize the
-use of the trademark "Creative Commons" or any other trademark or logo
-of Creative Commons without its prior written consent including,
-without limitation, in connection with any unauthorized modifications
-to any of its public licenses or any other arrangements,
-understandings, or agreements concerning use of licensed material. For
-the avoidance of doubt, this paragraph does not form part of the
-public licenses.
-
-Creative Commons may be contacted at creativecommons.org.
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2016 The Kubernetes Authors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
@@ -1,49 +1,15 @@
-DOCKER       = docker
-HUGO_VERSION = 0.58.3
-DOCKER_IMAGE = kubernetes-hugo
-DOCKER_RUN   = $(DOCKER) run --rm --interactive --tty --volume $(CURDIR):/src
-NODE_BIN     = node_modules/.bin
-NETLIFY_FUNC = $(NODE_BIN)/netlify-lambda
-
-.PHONY: all build build-preview help serve
+.PONY: all build build-preview help serve

 help: ## Show this help.
 	@awk 'BEGIN {FS = ":.*?## "} /^[a-zA-Z_-]+:.*?## / {sub("\\\\n",sprintf("\n%22c"," "), $$2);printf "\033[36m%-20s\033[0m %s\n", $$1, $$2}' $(MAKEFILE_LIST)

-all: build ## Build site with production settings and put deliverables in ./public
+all: build ## Build site with production settings and put deliverables in _site.

-build: ## Build site with production settings and put deliverables in ./public
-	hugo --minify
+build: ## Build site with production settings and put deliverables in _site.
+	jekyll build

-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
+build-preview: ## Build site with drafts and future posts enabled.
+	jekyll build --drafts --future

 serve: ## Boot the development server.
-	hugo server --buildFuture
-
-docker-image:
-	$(DOCKER) build . --tag $(DOCKER_IMAGE) --build-arg HUGO_VERSION=$(HUGO_VERSION)
-
-docker-build:
-	$(DOCKER_RUN) $(DOCKER_IMAGE) hugo
-
-docker-serve:
-	$(DOCKER_RUN) -p 1313:1313 $(DOCKER_IMAGE) hugo server --buildFuture --bind 0.0.0.0
-
-test-examples:
-	scripts/test_examples.sh install
-	scripts/test_examples.sh run
-
-check-hugo-versions:
-	scripts/hugo-version-check.sh $(HUGO_VERSION)
+	jekyll serve
@@ -1,10 +1,7 @@
-# See the OWNERS docs at https://go.k8s.io/owners
-
-reviewers:
- sig-docs-en-reviews # Defined in OWNERS_ALIASES
-
-approvers:
- sig-docs-en-owners # Defined in OWNERS_ALIASES
-
-labels:
- sig/docs
+assignees:
+- lavalamp
+- smarterclayton
+- janetkuo
+- pwittrock
+- kelseyhightower
+- jaredbhatti
@@ -1,172 +0,0 @@
-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-de-owners: # Admins for German content
-    - bene2k1
-    - mkorbi
-    - rlenferink
-  sig-docs-de-reviews: # PR reviews for German content
-    - bene2k1
-    - mkorbi
-    - rlenferink
-  sig-docs-en-owners: # Admins for English content
-    - bradamant3
-    - bradtopol
-    - chenopis
-    - cody-clark
-    - jaredbhatti
-    - jimangel
-    - kbarnard10
-    - makoscafee
-    - 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-es-owners: # Admins for Spanish content
-    - raelga
-    - alexbrand
-  sig-docs-es-reviews: # PR reviews for Spanish content
-    - raelga
-    - alexbrand
-    - glo-pena
-    - electrocucaracha
-  sig-docs-fr-owners: # Admins for French content
-    - remyleone
-    - perriea
-    - rekcah78
-    - yastij
-    - smana
-    - rbenzair
-    - abuisine
-    - erickhun
-    - jygastaud
-    - awkif
-    - oussemos
-  sig-docs-fr-reviews: # PR reviews for French content
-    - remyleone
-    - perriea
-    - rekcah78
-    - yastij
-    - smana
-    - rbenzair
-    - abuisine
-    - erickhun
-    - jygastaud
-    - awkif
-    - oussemos
-  sig-docs-hi-owners: # Admins for Hindi content
-    - avidLearnerInProgress
-    - daminisatya
-    - mittalyashu
-    - Rajakavitha1
-  sig-docs-hi-reviews: # PR reviews for Hindi content
-    - avidLearnerInProgress
-    - daminisatya
-    - mittalyashu
-    - Rajakavitha1
-  sig-docs-id-owners: # Admins for Indonesian content
-    - girikuncoro
-    - irvifa
-  sig-docs-id-reviews: # PR reviews for Indonesian content
-    - girikuncoro
-    - irvifa
-  sig-docs-it-owners: # Admins for Italian content
-    - rlenferink
-    - micheleberardi
-  sig-docs-it-reviews: # PR reviews for Italian content
-    - rlenferink
-    - micheleberardi
-  sig-docs-ja-owners: # Admins for Japanese content 
-    - cstoku
-    - nasa9084
-    - tnir
-    - zacharysarah
-  sig-docs-ja-reviews: # PR reviews for Japanese 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
-    - seokho-son
-  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
-  sig-docs-pt-owners: # Admins for Portuguese content
-    - femrtnz
-    - jcjesus
-  sig-docs-pt-reviews: # PR reviews for Portugese content
-    - femrtnz
-    - jcjesus
@@ -1,81 +0,0 @@
-# Kubernetes Dokumentation
-
-[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website)
-[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-Herzlich willkommen! Dieses Repository enthält alle Assets, die zur Erstellung der [Kubernetes-Website und Dokumentation](https://kubernetes.io/) erforderlich sind. Wir freuen uns sehr, dass Sie dazu beitragen wollen!
-
-## Beiträge zur Dokumentation
-
-Sie können auf die Schaltfläche **Fork** im oberen rechten Bereich des Bildschirms klicken, um eine Kopie dieses Repositorys in Ihrem GitHub-Konto zu erstellen. Diese Kopie wird als *Fork* bezeichnet. Nehmen Sie die gewünschten Änderungen an Ihrem Fork vor. Wenn Sie bereit sind, diese Änderungen an uns zu senden, gehen Sie zu Ihrem Fork und erstellen Sie eine neue Pull-Anforderung, um uns darüber zu informieren.
-
-Sobald Ihre Pull-Anfrage erstellt wurde, übernimmt ein Rezensent von Kubernetes die Verantwortung für klares, umsetzbares Feedback. Als Eigentümer des Pull-Request **liegt es in Ihrer Verantwortung Ihren Pull-Reqest enstsprechend des Feedbacks, dass Sie vom Kubernetes-Reviewer erhalten haben abzuändern.** Beachten Sie auch, dass Sie am Ende mehr als einen Rezensenten von Kubernetes erhalten, der Ihnen Feedback gibt, oder dass Sie Rückmeldungen von einem Rezensenten von Kubernetes erhalten, der sich von demjenigen unterscheidet, der ursprünglich für das Feedback zugewiesen wurde. In einigen Fällen kann es vorkommen, dass einer Ihrer Prüfer bei Bedarf eine technische Überprüfung von einem [Kubernetes Tech-Reviewer](https://github.com/kubernetes/website/wiki/tech-reviewers) anfordert. Reviewer geben ihr Bestes, um zeitnah Feedback zu geben, die Antwortzeiten können jedoch je nach den Umständen variieren.
-
-Weitere Informationen zum Beitrag zur Kubernetes-Dokumentation finden Sie unter:
-
-* [Mitwirkung beginnen](https://kubernetes.io/docs/contribute/start/)
-* [Ihre Dokumentationsänderungen bereitstellen](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
-* [Seitenvorlagen verwenden](http://kubernetes.io/docs/contribute/style/page-templates/)
-* [Dokumentationsstil-Handbuch](http://kubernetes.io/docs/contribute/style/style-guide/)
-* [Übersetzung der Kubernetes-Dokumentation](https://kubernetes.io/docs/contribute/localization/)
-
-## `README.md`'s Localizing Kubernetes Documentation
-
-### Deutsch
-Die Betreuer der deutschen Lokalisierung erreichen Sie unter:
-
-* Benedikt Rollik ([@bene2k1](https://github.com/bene2k1))
-* Max Körbächer ([@mkorbi](https://github.com/mkorbi))
-* [Slack Kanal](https://kubernetes.slack.com/messages/kubernetes-docs-de)
-
-## Site lokal mit Docker ausführen
-
-Um die Kubernetes-Website lokal laufen zu lassen, empfiehlt es sich, ein spezielles [Docker](https://docker.com) Image auszuführen, das den statischen Site-Generator [Hugo](https://gohugo.io) enthält.
-
-> Unter Windows benötigen Sie einige weitere Tools, die Sie mit [Chocolatey](https://chocolatey.org) installieren können.
-`choco install make`
-
-> Wenn Sie die Website lieber lokal ohne Docker ausführen möchten, finden Sie weitere Informationen unter [Website lokal mit Hugo ausführen](#Die-Site-lokal-mit-Hugo-ausführen).
-
-Wenn Sie Docker [installiert](https://www.docker.com/get-started) haben, erstellen Sie das Docker-Image `kubernetes-hugo` lokal:
-
-```bash
-make docker-image
-```
-
-Nachdem das Image erstellt wurde, können Sie die Site lokal ausführen:
-
-```bash
-make docker-serve
-```
-
-Öffnen Sie Ihren Browser unter http://localhost:1313, um die Site anzuzeigen. Wenn Sie Änderungen an den Quelldateien vornehmen, aktualisiert Hugo die Site und erzwingt eine Browseraktualisierung.
-
-## Die Site lokal mit Hugo ausführen
-
-Hugo-Installationsanweisungen finden Sie in der [offiziellen Hugo-Dokumentation](https://gohugo.io/getting-started/installing/). Stellen Sie sicher, dass Sie die Hugo-Version installieren, die in der Umgebungsvariablen `HUGO_VERSION` in der Datei [`netlify.toml`](netlify.toml#L9) angegeben ist.
-
-So führen Sie die Site lokal aus, wenn Sie Hugo installiert haben:
-
-```bash
-make serve
-```
-
-Dadurch wird der lokale Hugo-Server an Port 1313 gestartet. Öffnen Sie Ihren Browser unter http://localhost:1313, um die Site anzuzeigen. Wenn Sie Änderungen an den Quelldateien vornehmen, aktualisiert Hugo die Site und erzwingt eine Browseraktualisierung.
-
-## Community, Diskussion, Beteiligung und Unterstützung
-
-Erfahren Sie auf der [Community-Seite](http://kubernetes.io/community/) wie Sie mit der Kubernetes-Community interagieren können.
-
-Sie können die Betreuer dieses Projekts unter folgender Adresse erreichen:
-
- [Slack](https://kubernetes.slack.com/messages/sig-docs)
- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-### Verhaltensregeln
-
-Die Teilnahme an der Kubernetes-Community unterliegt dem [Kubernetes-Verhaltenskodex](code-of-conduct.md).
-
-## Vielen Dank!
-
-Kubernetes lebt vom Community Engagement und wir freuen uns sehr über Ihre Beiträge zu unserer Website und unserer Dokumentation!
@@ -1,76 +0,0 @@
-# La documentación de Kubernetes
-
-[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website)
-[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-Bienvenido!
-Este repositorio contiene todos los recursos necesarios para construir el [sitio web de Kubernetes y su documentación](https://kubernetes.io/). ¡Estamos encantados de que quiera contribuir!
-
-## Contribuyendo con la documentación
-
-Puede hacer clic en el botón **Fork** situado en la esquina superior derecha de la pantalla para crear una copia de este repositorio en su cuenta de GitHub. A ese tipo de copia se le llama **Fork** (bifurcación) y le permite editar el contenido del repositorio en su copia personal. Realice los cambios que quiera en su **fork** y, cuando esté listo para enviarnos esos cambios, vaya a **fork** en repositorio en su GitHub y cree una nueva **pull request** para que tengamos constancia de la propuesta de cambios.
-
-Una vez la **pull request** ha sido creada, un revisor de Kubernetes asumirá la responsabilidad de proporcionar comentarios claros y prácticos sobre como continuar. Como propietario de la PR, **es su responsabilidad modificar la pull request para abordar los comentarios proporcionados por el revisor de Kubernetes.** Tenga en cuenta que algunas veces puede terminar teniendo más de un revisor de Kubernetes participando en la revisión, por lo que es posible que reciba comentarios de más revisores a parte del asignado originalmente en la creación de la **pull request**. Además, en algunas ocasiones, es posible que uno de sus revisores solicite una revisión técnica por parte de un [revisor técnico de Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) si lo considera necesario.
-
-Los revisores harán todo lo posible para proporcionar toda la información necesaria para que la **pull request** siga adelante en un tiempo razonable, pero este tiempo de respuesta puede variar según las circunstancias.
-
-Para obtener más información sobre cómo contribuir a la documentación de Kubernetes, puede consultar:
-
-* [Empezando a contribuir](https://kubernetes.io/docs/contribute/start/)
-* [Visualizando sus cambios en su entorno local](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
-* [Utilizando las plantillas de las páginas](http://kubernetes.io/docs/contribute/style/page-templates/)
-* [Guía de estilo de la documentación](http://kubernetes.io/docs/contribute/style/style-guide/)
-* [Traduciendo la documentación de Kubernetes](https://kubernetes.io/docs/contribute/localization/)
-
-## Levantando el sitio web kubernetes.io en su entorno local con Docker
-
-El método recomendado para levantar una copia local del sitio web kubernetes.io es utilizando la imagen de [Docker](https://docker.com) que incluye el generador de sitios estáticos [Hugo](https://gohugo.io).
-
-> Para Windows, algunas otras herramientas como Make son necesarias. Puede instalarlas utilizando el gestor [Chocolatey](https://chocolatey.org). `choco install make` o siguiendo las instrucciones de [Make for Windows](http://gnuwin32.sourceforge.net/packages/make.htm).
-
-> Si prefiere levantar el sitio web sin utilizar **Docker**, puede seguir las instrucciones disponibles en la sección [Levantando kubernetes.io en local con Hugo](#levantando-kubernetes.io-en-local-con-hugo).
-
-Una vez tenga Docker [configurado en su máquina](https://www.docker.com/get-started), puede construir la imagen de Docker `kubernetes-hugo` localmente ejecutando el siguiente comando en la raíz del repositorio:
-
-```bash
-make docker-image
-```
-
-Una vez tenga la imagen construida, puede levantar el sitio web ejecutando:
-
-```bash
-make docker-serve
-```
-
-Abra su navegador y visite http://localhost:1313 para acceder a su copia local del sitio. A medida que vaya haciendo cambios en el código fuente, Hugo irá actualizando la página y forzará la actualización en el navegador.
-
-## Levantando kubernetes.io en local con Hugo
-
-Revise la [documentación oficial de Hugo](https://gohugo.io/getting-started/installing/) para obtener las instrucciones de instalación en su sistema operativo. Asegúrese de instalar la versión de Hugo especificada en la variable de entorno  `HUGO_VERSION` del fichero [`netlify.toml`](netlify.toml#L9).
-
-Para levantar el sitio localmente una vez Hugo está instalado en su sistema, puede ejecutar el siguiente comando:
-
-```bash
-make serve
-```
-
-Este comando levantará un servidor de Hugo en el puerto **1313** al que podrá acceder visitando http://localhost:1313 y dónde podrá visualizar su copia local del sitio web. A medida que vaya haciendo cambios en el código fuente, Hugo irá actualizando la página y forzará la actualización en el navegador.
-
-## Comunidad, discusión, contribuir y soporte
-
-Aprenda como participar en la comunidad de Kubernetes visitando la [página de comunidad](http://kubernetes.io/community/).
-
-Puede ponerse en contacto con los mantenedores de este proyecto en:
-
- [Slack](https://kubernetes.slack.com/messages/sig-docs)
- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-### Código de conducta
-
-La participación en la comunidad de Kubernetes está regulada por el [Código de Conducta de Kubernetes](code-of-conduct.md).
-
-## ¡Muchas gracias!
-
-Kubernetes es posible gracias a la participación de la comunidad y la documentación es vital para facilitar el acceso al proyecto.
-
-Agradecemos muchísimo sus contribuciones a nuestro sitio web y nuestra documentación.
@@ -1,83 +0,0 @@
-# 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 !
@@ -1,84 +0,0 @@
-# कुबरनेट्स प्रलेखन
-
-[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website)
-[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-स्वागत हे! इस रिपॉजिटरी में [कुबरनेट्स वेबसाइट और दस्तावेज](https://kubernetes.io/) बनाने के लिए आवश्यक सभी संपत्तियां हैं। हम बहुत खुश हैं कि आप योगदान करना चाहते हैं!
-
-## डॉक्स में योगदान देना
-
-आप अपने GitHub खाते में इस रिपॉजिटरी की एक copy बनाने के लिए स्क्रीन के ऊपरी-दाएँ क्षेत्र में **Fork** बटन पर क्लिक करें। इस copy को *Fork* कहा जाता है। अपने fork में कोई भी परिवर्तन करना चाहते हैं, और जब आप उन परिवर्तनों को हमारे पास भेजने के लिए तैयार हों, तो अपने fork पर जाएं और हमें इसके बारे में बताने के लिए एक नया pull request बनाएं।
-
-एक बार जब आपका pull request बन जाता है, तो एक कुबरनेट्स समीक्षक स्पष्ट, कार्रवाई योग्य प्रतिक्रिया प्रदान करने की जिम्मेदारी लेगा। pull request के मालिक के रूप में, **यह आपकी जिम्मेदारी है कि आप कुबरनेट्स समीक्षक द्वारा प्रदान की गई प्रतिक्रिया को संबोधित करने के लिए अपने pull request को संशोधित करें।**
-
-यह भी ध्यान दें कि आप एक से अधिक कुबरनेट्स समीक्षक आपको प्रतिक्रिया प्रदान कर सकते हैं या आप एक कुबरनेट्स समीक्षक से प्रतिक्रिया प्राप्त कर सकते हैं जो मूल रूप से आपको प्रतिक्रिया प्रदान करने के लिए दिए गए एक से भिन्न है। इसके अलावा, कुछ मामलों में, आपका एक समीक्षक जरूरत पड़ने पर [कुबेरनेट्स टेक समीक्षक](https://github.com/kubernetes/website/wiki/Tech-reviewers) से तकनीकी समीक्षा प्राप्त कर सकता है। समीक्षक समय पर प्रतिक्रिया देने के लिए पूरी कोशिश करेंगे, लेकिन परिस्थितियों के आधार पर प्रतिक्रिया समय अलग-अलग हो सकता है।
-
-कुबरनेट्स प्रलेखन में योगदान देने के बारे में अधिक जानकारी के लिए, देखें:
-
-* [योगदान देना शुरू करें](https://kubernetes.io/docs/contribute/start/)
-* [परिवर्तनों को अंतिम चरण में लेजाएं](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
-* [पेज टेम्पलेट](http://kubernetes.io/docs/contribute/style/page-templates/)
-* [प्रलेखन शैली गाइड](http://kubernetes.io/docs/contribute/style/style-guide/)
-* [स्थानीयकरण कुबरनेट्स प्रलेखन](https://kubernetes.io/docs/contribute/localization/)
-
-## `README.md`'s स्थानीयकरण कुबरनेट्स प्रलेखन
-
-आप पर हिंदी स्थानीयकरण के maintainers तक पहुँच सकते हैं:
-
-* Yashu Mittal ([Twitter](https://twitter.com/mittalyashu77), [GitHub](https://github.com/mittalyashu))
-* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-hi)
-
-## स्थानीय रूप से डॉकर का उपयोग करके साइट चलाना
-
-कुबरनेट्स वेबसाइट को स्थानीय रूप से चलाने के लिए अनुशंसित तरीका एक विशेष [डॉकर](https://docker.com) image को चलाना है, जिसमें [Hugo](https://gohugo.io) स्टेटिक साइट जनरेटर शामिल है।
-
-> यदि आप विंडोज पर हैं, तो आपको कुछ और टूल्स की आवश्यकता होगी जिन्हें आप [Chocolatey](https://chocolatey.org) के साथ इंस्टॉल कर सकते हैं।
-
-> यदि आप डॉकर के बिना स्थानीय रूप से वेबसाइट चलाना पसंद करते हैं, तो नीचे Hugo का उपयोग करके स्थानीय रूप से साइट चलाना देखें।
-
-यदि आप डॉकर के बिना स्थानीय रूप से वेबसाइट चलाना पसंद करते हैं, तो नीचे दिए गए Hugo का उपयोग करके स्थानीय रूप से [साइट को चलाने](#running-the-site-locally-using-hugo) का तरीका देखें।
-
-यदि आप [डॉकर](https://www.docker.com/get-started) चला रहे हैं, तो स्थानीय रूप से `कुबेरनेट्स-ह्यूगो` Docker image बनाएँ:
-
-```bash
-make docker-image
-```
-
-एक बार image बन जाने के बाद, आप साइट को स्थानीय रूप से चला सकते हैं:
-
-```bash
-make docker-serve
-```
-
-साइट देखने के लिए अपने browser को `http://localhost:1313` पर खोलें। जैसा कि आप source फ़ाइलों में परिवर्तन करते हैं, Hugo साइट को अपडेट करता है और browser को refresh करने पर मजबूर करता है।
-
-## Hugo का उपयोग करते हुए स्थानीय रूप से साइट चलाना
-
-Hugo निर्देशों के लिए [आधिकारिक Hugo प्रलेखन](https://gohugo.io/getting-started/installing/) देखें। [`Netlify.toml`](netlify.toml#L9) फ़ाइल में `HUGO_VERSION` environment variable द्वारा निर्दिष्ट Hugo version को install करना सुनिश्चित करें।
-
-जब आप Hugo को install करते हैं तो स्थानीय रूप से साइट को चलाने के लिए:
-
-```bash
-make serve
-```
-
-यह पोर्ट `1313` पर Hugo सर्वर को शुरू करेगा। साइट देखने के लिए अपने browser को `http://localhost:1313` पर खोलें। जैसा कि आप source फ़ाइलों में परिवर्तन करते हैं, Hugo साइट को अपडेट करता है और एक browser को refresh करने पर मजबूर करता है।
-
-## समुदाय, चर्चा, योगदान और समर्थन
-
-[Community page](http://kubernetes.io/community/) पर कुबरनेट्स समुदाय के साथ जुड़ना सीखें।
-
-आप इस परियोजना के स्थानीयकरण तक पहुँच सकते हैं:
-
- [Slack](https://kubernetes.slack.com/messages/sig-docs)
- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-## कोड ओफ़ कंडक्ट
-
-कुबरनेट्स समुदाय में भागीदारी [कुबरनेट्स कोड ओफ़ कंडक्ट](https://github.com/cncf/foundation/blob/master/code-of-conduct-languages/hi.md) द्वारा शासित है.
-
-## धन्यवाद!
-
-कुबरनेट्स सामुदायिक भागीदारी पर पनपती है, और हम वास्तव में हमारी साइट और हमारे प्रलेखन में आपके योगदान की सराहना करते हैं!
-
-कुबरनेट्स आपकी भागीदारी पर निर्भर है, और हम हमारी साइट और प्रलेखन में आपके योगदान का मान करते हैं!
@@ -1,72 +0,0 @@
-# Dokumentasi Kubernetes
-
-[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website)
-[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-Selamat datang! Repositori ini merupakan wadah bagi semua komponen yang dibutuhkan untuk membuat [dokumentasi Kubernetes](https://kubernetes.io/). Kami merasa sangat senang apabila kamu berminat untuk menjadi kontributor!
-
-## Kontribusi pada dokumentasi
-
-Pertama, kamu dapat menekan tombol **Fork** yang berada pada bagian atas layar, untuk menyalin repositori pada akun Github-mu. Salinan ini disebut sebagai **fork**. Kamu dapat menambahkan konten pada **fork** yang kamu miliki, setelah kamu merasa cukup untuk menambahkan konten yang kamu miliki dan ingin memberikan konten tersebut pada kami, kamu dapat melihat **fork** yang telah kamu buat dan membuat **pull request** untuk memberi tahu kami bahwa kamu ingin menambahkan konten yang telah kamu buat.
-
-Setelah kamu membuat sebuah **pull request**, seorang **reviewer** akan memberikan masukan terhadap konten yang kamu sediakan serta beberapa hal yang dapat kamu lakukan apabila perbaikan diperlukan terhadap konten yang telah kamu sediakan. Sebagai seorang yang membuat **pull request**, **sudah menjadi kewajiban kamu untuk melakukan modifikasi terhadap konten yang kamu berikan sesuai dengan masukan yang diberikan oleh seorang reviewer Kubernetes**. Perlu kamu ketahui bahwa kamu dapat saja memiliki lebih dari satu orang **reviewer Kubernetes** atau dalam kasus kamu bisa saja mendapatkan **reviewer Kubernetes** yang berbeda dengan **reviewer Kubernetes** awal yang ditugaskan untuk memberikan masukan terhadap konten yang kamu sediakan. Selain itu, seorang **reviewer Kubernetes** bisa saja meminta masukan teknis dari [reviewer teknis Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) jika diperlukan. 
-
-Untuk informasi lebih lanjut mengenai tata cara melakukan kontribusi, kamu dapat melihat tautan di bawah ini:
-
-* [Petunjuk Melakukan Kontribusi](https://kubernetes.io/docs/contribute/start/)
-* [Melakukan Tahap Staging pada Konten Dokumentasi yang telah Kamu Sediakan](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
-* [Petunjuk Menggunakan Page Templates](http://kubernetes.io/docs/contribute/style/page-templates/)
-* [Petunjuk untuk Documentation Style](http://kubernetes.io/docs/contribute/style/style-guide/)
-* [Petunjuk untuk Melakukan Lokalisasi Dokumentasi Kubernetes](https://kubernetes.io/docs/contribute/localization/)
-
-## Menjalankan Dokumentasi Kubernetes pada Mesin Lokal Kamu
-
-Petunjuk yang disarankan untuk menjalankan Dokumentasi Kubernetes pada mesin lokal kamus adalah dengan menggunakan [Docker](https://docker.com) **image** yang memiliki **package** [Hugo](https://gohugo.io), **Hugo** sendiri merupakan generator website statis. 
-
-> Jika kamu menggunakan Windows, kamu mungkin membutuhkan beberapa langkah tambahan untuk melakukan instalasi perangkat lunak yang dibutuhkan. Instalasi ini dapat dilakukan dengan menggunakan [Chocolatey](https://chocolatey.org). `choco install make`
-
-> Jika kamu ingin menjalankan **website** tanpa menggunakan **Docker**, kamu dapat melihat tautan berikut [Petunjuk untuk menjalankan website pada mesin lokal dengan menggunakan Hugo](#petunjuk-untuk-menjalankan-website-pada-mesin-lokal-denga-menggunakan-hugo) di bagian bawah.
-
-Jika kamu sudah memiliki **Docker** [yang sudah dapat digunakan](https://www.docker.com/get-started), kamu dapat melakukan **build** `kubernetes-hugo` **Docker image** secara lokal:
-
-```bash
-make docker-image
-```
-
-Setelah **image** berhasil di-**build**, kamu dapat menjalankan website tersebut pada mesin lokal-mu:
-
-```bash
-make docker-serve
-```
-
-Buka **browser** kamu ke http://localhost:1313 untuk melihat laman dokumentasi. Selama kamu melakukan penambahan konten, **Hugo** akan secara otomatis melakukan perubahan terhadap laman dokumentasi apabila **browser** melakukan proses **refresh**.
-
-
-## Petunjuk untuk menjalankan website pada mesin lokal dengan menggunakan Hugo
-
-Kamu dapat melihat [dokumentasi resmi Hugo](https://gohugo.io/getting-started/installing/) untuk mengetahui langkah yang diperlukan untuk melakukan instalasi **Hugo**. Pastikan kamu melakukan instalasi versi **Hugo** sesuai dengan versi yang tersedia pada **environment variable** `HUGO_VERSION` pada **file**[`netlify.toml`](netlify.toml#L9). 
-
-Untuk menjalankan laman pada mesin lokal setelah instalasi **Hugo**, kamu dapat menjalankan perintah berikut:
-
-```bash
-make serve
-```
-
-Buka **browser** kamu ke http://localhost:1313 untuk melihat laman dokumentasi. Selama kamu melakukan penambahan konten, **Hugo** akan secara otomatis melakukan perubahan terhadap laman dokumentasi apabila **browser** melakukan proses **refresh**.
-
-## Komunitas, Diskusi, Kontribusi, dan Bantuan
-
-Kamu dapat belajar bagaimana tata cara untuk ikut terlibat dalam komunitas Kubernetes melalui [laman komunitas](http://kubernetes.io/community/).
-
-Kamu dapat berinteraksi dengan **maintainers** project ini melalui:
-
- [Slack](https://kubernetes.slack.com/messages/sig-docs)
- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-### Etika dalam Berkontribusi
-
-Partisipasi dalam komunitas Kubernetes diatur dalam [Etika dalam Berkontribusi pada Kubernetes](code-of-conduct.md).
-
-## Terima Kasih!
-
-Kubernetes sangat menjunjung tinggi partisipasi dari komunitas, dan kami sangat mengapresiasi kontribusi kamu pada laman dan dokumentasi kami!
@@ -1,69 +0,0 @@
-# 쿠버네티스 문서화
-
-[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website)
-[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-환영합니다! 이 저장소는 쿠버네티스 웹사이트 및 문서화를 만드는 데 필요로 하는 모든 asset에 대한 공간을 제공합니다. 여러 분이 기여를 원한다는 사실에 매우 기쁩니다!
-
-## 문서에 기여하기
-
-이 저장소에 대한 복제본을 여러분의 GitHub 계정에 생성하기 위해 화면 오른쪽 위 영역에 있는 **Fork** 버튼을 클릭 가능합니 다. 이 복제본은 *fork* 라고 부릅니다. 여러분의 fork에서 원하는 임의의 변경 사항을 만들고, 해당 변경 사항을 보낼 준비가  되었다면, 여러분의 fork로 이동하여 새로운 풀 리퀘스트를 만들어 우리에게 알려주시기 바랍니다.
-
-여러분의 풀 리퀘스트가 생생된 이후에는, 쿠버네티스 리뷰어가 명료하고 실행 가능한 피드백을 제공하는 책임을 담당할 것입니 다. 풀 리퀘스트의 오너로서, **쿠버네티스 리뷰어로부터 제공받은 피드백을 수용하기 위해 풀 리퀘스트를 수정하는 것은 여러분의 책임입니다.** 또한, 참고로 한 명 이상의 쿠버네티스 리뷰어가 여러분에게 피드백을 제공하는 상황에 처하거나, 또는 여러분에게 피드백을 제공하기로 원래 할당된 사람이 아닌 다른 쿠버네티스 리뷰어로부터 피드백을 받는 상황에 처할 수도 있습니다.  뿐만 아니라, 몇몇 상황에서는, 필요에 따라 리뷰어 중 한 명이 [쿠버네티스 기술 리뷰어](https://github.com/kubernetes/website/wiki/Tech-reviewers)로부터의 기술 리뷰를 요청할지도 모릅니다. 리뷰어는 제시간에 피드백을 제공하기 위해 최선을 다할 것이지만, 응답 시간은 상황에 따라 달라질 수도 있습니다.
-
-쿠버네티스 문서화에 기여하기와 관련된 보다 자세한 정보는, 다음을 살펴봅니다:
-
-* [기여 시작하기](https://kubernetes.io/docs/contribute/start/)
-* [문서화 변경 사항 스테이징하기](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
-* [페이지 템플릿 사용하기](http://kubernetes.io/docs/contribute/style/page-templates/)
-* [문서화 스타일 가이드](http://kubernetes.io/docs/contribute/style/style-guide/)
-* [쿠버네티스 문서화 로컬라이징](https://kubernetes.io/docs/contribute/localization/)
-
-## `README.md`에 대한 쿠버네티스 문서화 번역
-
-### 한국어
-
-`README.md` 번역 및 한국어 기여자를 위한 보다 자세한 가이드를 [한국어 README](README-ko.md) 페이지 혹은 [쿠버네티스 문서 한글화 가이드](https://kubernetes.io/ko/docs/contribute/localization_ko/)에서 살펴봅니다.
-
-한국어 번역 메인테이너에게 다음을 통해 연락 가능합니다.
-
-* 이덕준 ([GitHub - @gochist](https://github.com/gochist))
-* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-ko)
-
-## 도커를 사용하여 사이트를 로컬에서 실행하기
-
-쿠버네티스 웹사이트를 로컬에서 실행하기 위한 추천하는 방식은 [Hugo](https://gohugo.io) 정적 사이트 생성기를 포함하는 특 별한 [도커](https://docker.com) 이미지를 실행하는 것입니다.
-
-> Windows에서 실행하는 경우, [Chocolatey](https://chocolatey.org)로 설치할 수 있는 명명 추가 도구를 필요로 할 것입니다. `choco install make`
-
-> 도커를 사용하지 않고 웹사이트를 로컬에서 실행하기를 선호하는 경우에는, 아래 [Hugo를 사용한 로컬 사이트 실행하기](#hugo를-사용한-로컬-사이트-실행하기)를 살펴봅니다.
-
-도커 [동작 및 실행](https://www.docker.com/get-started) 환경이 있는 경우, 로컬에서 `kubernetes-hugo` 도커 이미지를 빌드 합니다:
-
-```bash
-make docker-image
-```
-
-해당 이미지가 빌드된 이후, 사이트를 로컬에서 실행할 수 있습니다:
-
-```bash
-make docker-serve
-```
-
-브라우저에서 http://localhost:1313 를 열어 사이트를 살펴봅니다. 소스 파일에 변경 사항이 있을 때, Hugo는 사이트를 업데이 트하고 브라우저를 강제로 새로고침합니다.
-
-## Hugo를 사용한 로컬 사이트 실행하기
-
-Hugo 설치 안내를 위해서는 [공식 Hugo 문서화](https://gohugo.io/getting-started/installing/)를 살펴봅니다. [`netlify.toml`](netlify.toml#L9) 파일에 있는 `HUGO_VERSION` 환경 변수에서 지정된 Hugo 버전이 설치되었는지를 확인합니다.
-
-Hugo가 설치되었을 때 로컬에서 사이트를 실행하기 위해 (다음을 실행합니다):
-
-```bash
-make serve
-```
-
-이를 통해 로컬 Hugo 서버를 1313번 포트에 시작합니다. 브라우저에서 http://localhost:1313 를 열어 사이트를 살펴봅니다. 소 스 파일에 변경 사항이 있을 때, Hugo는 사이트를 업데이트하고 브라우저를 강제로 새로고침합니다.
-
-## 감사합니다!
-
-쿠버네티스는 커뮤니티 참여와 함께 생존하며, 우리는 사이트 및 문서화에 대한 여러분의 컨트리뷰션에 대해 정말 감사하게 생각합니다!
@@ -1,82 +0,0 @@
-# A documentação do Kubernetes
-
-[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website)
-[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-Bem vindos! Este repositório abriga todos os recursos necessários para criar o [site e documentação do Kubernetes](https://kubernetes.io/). Estamos muito satisfeitos por você querer contribuir!
-
-## Contribuindo com os documentos
-
-Você pode clicar no botão **Fork** na área superior direita da tela para criar uma cópia desse repositório na sua conta do GitHub. Esta cópia é chamada de *fork*. Faça as alterações desejadas no seu fork e, quando estiver pronto para enviar as alterações para nós, vá até o fork e crie uma nova solicitação de pull para nos informar sobre isso.
-
-Depois que seu **pull request** for criada, um revisor do Kubernetes assumirá a responsabilidade de fornecer um feedback claro e objetivo. Como proprietário do pull request, **é sua responsabilidade modificar seu pull request para abordar o feedback que foi fornecido a você pelo revisor do Kubernetes.** Observe também que você pode acabar tendo mais de um revisor do Kubernetes para fornecer seu feedback ou você pode acabar obtendo feedback de um revisor do Kubernetes que é diferente daquele originalmente designado para lhe fornecer feedback. Além disso, em alguns casos, um de seus revisores pode solicitar uma revisão técnica de um [revisor de tecnologia Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) quando necessário. Os revisores farão o melhor para fornecer feedback em tempo hábil, mas o tempo de resposta pode variar de acordo com as circunstâncias.
-
-Para mais informações sobre como contribuir com a documentação do Kubernetes, consulte:
-
-* [Comece a contribuir](https://kubernetes.io/docs/contribute/start/)
-* [Preparando suas alterações na documentação](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
-* [Usando Modelos de Página](http://kubernetes.io/docs/contribute/style/page-templates/)
-* [Guia de Estilo da Documentação](http://kubernetes.io/docs/contribute/style/style-guide/)
-* [Localizando documentação do Kubernetes](https://kubernetes.io/docs/contribute/localization/)
-
-## Documentação do Kubernetes Localizando o `README.md`
-
-### coreano
-
-Veja a tradução de `README.md` e mais orientações sobre detalhes para contribuidores coreanos na página [README coreano](README-ko.md).
-
-Você pode alcançar os mantenedores da localização coreana em:
-
-* June Yi ([GitHub - @gochist](https://github.com/gochist))
-* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-ko)
-
-## Executando o site localmente usando o Docker
-
-A maneira recomendada de executar o site do Kubernetes localmente é executar uma imagem especializada do [Docker](https://docker.com) que inclui o gerador de site estático [Hugo](https://gohugo.io).
-
-> Se você está rodando no Windows, você precisará de mais algumas ferramentas que você pode instalar com o [Chocolatey](https://chocolatey.org). `choco install make`
-
-> Se você preferir executar o site localmente sem o Docker, consulte [Executando o site localmente usando o Hugo](#executando-o-site-localmente-usando-o-hugo) abaixo.
-
-Se você tiver o Docker [em funcionamento](https://www.docker.com/get-started), crie a imagem do Docker do `kubernetes-hugo` localmente:
-
-```bash
-make docker-image
-```
-
-Depois que a imagem foi criada, você pode executar o site localmente:
-
-```bash
-make docker-serve
-```
-
-Abra seu navegador para http://localhost:1313 para visualizar o site. Conforme você faz alterações nos arquivos de origem, Hugo atualiza o site e força a atualização do navegador.
-
-## Executando o site localmente usando o Hugo
-
-Veja a [documentação oficial do Hugo](https://gohugo.io/getting-started/installing/) para instruções de instalação do Hugo. Certifique-se de instalar a versão do Hugo especificada pela variável de ambiente `HUGO_VERSION` no arquivo [`netlify.toml`](netlify.toml#L9).
-
-Para executar o site localmente quando você tiver o Hugo instalado:
-
-```bash
-make serve
-```
-
-Isso iniciará o servidor Hugo local na porta 1313. Abra o navegador para http://localhost:1313 para visualizar o site. Conforme você faz alterações nos arquivos de origem, Hugo atualiza o site e força a atualização do navegador.
-
-## Comunidade, discussão, contribuição e apoio
-
-Aprenda a se envolver com a comunidade do Kubernetes na [página da comunidade](http://kubernetes.io/community/).
-
-Você pode alcançar os mantenedores deste projeto em:
-
- [Slack](https://kubernetes.slack.com/messages/sig-docs)
- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-### Código de conduta
-
-A participação na comunidade Kubernetes é regida pelo [Código de Conduta da Kubernetes](code-of-conduct.md).
-
-## Obrigado!
-
-A Kubernetes prospera com a participação da comunidade e nós realmente apreciamos suas contribuições para o nosso site e nossa documentação!
@@ -1,80 +1,194 @@
-# The Kubernetes documentation
+## Instructions for Contributing to the Docs/Website

-[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website)
-[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
+Welcome! We are very pleased you want to contribute to the documentation and/or website for Kubernetes.

-Welcome! This repository houses all of the assets required to build the [Kubernetes website and documentation](https://kubernetes.io/). We're glad that you want to contribute!
+You can click the "Fork" button in the upper-right area of the screen to create a copy of our site on 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 the index page for your fork and click "New Pull Request" to let us know about it.

-## Contributing to the docs
+## Staging the site on GitHub Pages

-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.
+If you want to see your changes staged without having to install anything locally, remove the CNAME file in this directory and
+change the name of the fork to be:

-Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback.  As the owner of the pull request, **it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer.**  Also, note that you may end up having more than one Kubernetes reviewer provide you feedback or you may end up getting feedback from a Kubernetes reviewer that is different than the one initially assigned to provide you feedback. Furthermore, in some cases, one of your reviewers might ask for a technical review from a [Kubernetes tech reviewer](https://github.com/kubernetes/website/wiki/Tech-reviewers) when needed.  Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances.
+    YOUR_GITHUB_USERNAME.github.io

-For more information about contributing to the Kubernetes documentation, see:
+Then make your changes.

-* [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/)
+When you visit [http://YOUR_GITHUB_USERNAME.github.io](http://YOUR_GITHUB_USERNAME.github.io) you should see a special-to-you version of the site that contains the changes you just made.

-## Localization `README.md`'s
-|  |  |
-|---|---|
-|[French README](README-fr.md)|[Korean README](README-ko.md)|
-|[German README](README-de.md)|[Portuguese README](README-pt.md)|
-|[Hindi README](README-hi.md)|[Spanish README](README-es.md)|
-|[Indonesian README](README-id.md)|
-|||
+## Staging the site locally (using Docker)

-## Running the website locally using Docker
+Don't like installing stuff? Download and run a local staging server with a single `docker run` command. 

-The recommended way to run the Kubernetes website locally is to run a specialized [Docker](https://docker.com) image that includes the [Hugo](https://gohugo.io) static website generator.
+    git clone https://github.com/kubernetes/kubernetes.github.io.git
+    cd kubernetes.github.io
+    docker run -ti --rm -v "$PWD":/k8sdocs -p 4000:4000 gcr.io/google-samples/k8sdocs:1.0

-> 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`
+Then visit [http://localhost:4000](http://localhost:4000) to see our site. Any changes you make on your local machine will be automatically staged.

-> If you'd prefer to run the website locally without Docker, see [Running the website locally using Hugo](#running-the-site-locally-using-hugo) below.
+If you're interested you can view [the Dockerfile for this image](https://github.com/kubernetes/kubernetes.github.io/blob/master/staging-container/Dockerfile).

-If you have Docker [up and running](https://www.docker.com/get-started), build the `kubernetes-hugo` Docker image locally:
+## Staging the site locally (from scratch setup)

-```bash
-make docker-image
-```
+The below commands to setup your environment for running GitHub pages locally. Then, any edits you make will be viewable
+on a lightweight webserver that runs on your local machine.

-Once the image has been built, you can run the website locally:
+This will typically be the fastest way (by far) to iterate on docs changes and see them staged, once you get this set up, but it does involve several install steps that take awhile to complete, and makes system-wide modifications.

-```bash
-make docker-serve
-```
+Install Ruby 2.2 or higher. If you're on Linux, run these commands:

-Open up your browser to http://localhost:1313 to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
+    apt-get install software-properties-common
+    apt-add-repository ppa:brightbox/ruby-ng
+    apt-get install ruby2.2
+    apt-get install ruby2.2-dev

-## Running the website locally using Hugo
+* If you're on a Mac, follow [these instructions](https://gorails.com/setup/osx/). 
+* If you're on a Windows machine you can use the [Ruby Installer](http://rubyinstaller.org/downloads/). During the installation make sure to check the option for *Add Ruby executables to your PATH*.

-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.
+The remainder of the steps should work the same across operating systems.

-To run the website locally when you have Hugo installed:
+To confirm you've installed Ruby correctly, at the command prompt run `gem --version` and you should get a response with your version number. Likewise you can confirm you have Git installed properly by running `git --version`, which will respond with your version of Git.

-```bash
-make serve
-```
+Install the GitHub Pages package, which includes Jekyll:

-This will start the local Hugo server on port 1313. Open up your browser to http://localhost:1313 to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
+	gem install github-pages

-## Community, discussion, contribution, and support
+Clone our site:

-Learn how to engage with the Kubernetes community on the [community page](http://kubernetes.io/community/).
+	git clone https://github.com/kubernetes/kubernetes.github.io.git

-You can reach the maintainers of this project at:
+Make any changes you want. Then, to see your changes locally:

- [Slack](https://kubernetes.slack.com/messages/sig-docs)
- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+	cd kubernetes.github.io
+	jekyll serve

-### Code of conduct
+Your copy of the site will then be viewable at: [http://localhost:4000](http://localhost:4000)
+(or wherever Jekyll tells you).

-Participation in the Kubernetes community is governed by the [Kubernetes Code of Conduct](code-of-conduct.md).
+
+## GitHub help
+
+If you're a bit rusty with git/GitHub, you might wanna read
+[this](http://readwrite.com/2013/10/02/github-for-beginners-part-2) for a refresher.
+
+## Common Tasks
+
+### Edit Page Titles or Change the Left Navigation
+
+Edit the yaml files in `/_data/` for the Guides, Reference, Samples, or Support areas.
+
+You may have to exit and `jekyll clean` before restarting the `jekyll serve` to
+get changes to files in `/_data/` to show up.
+
+### Add Images
+
+Put the new image in `/images/docs/` if it's for the documentation, and just `/images/` if it's for the website.
+
+**For diagrams, we greatly prefer SVG files!**
+
+### Include code from another file
+
+To include a file that is hosted on this GitHub repo, insert this code:
+
+<pre>&#123;% include code.html language="&lt;LEXERVALUE&gt;" file="&lt;RELATIVEPATH&gt;" ghlink="&lt;PATHFROMROOT&gt;" %&#125;</pre>
+
+* `LEXERVALUE`: The language in which the file was written; must be [a value supported by Rouge](https://github.com/jneen/rouge/wiki/list-of-supported-languages-and-lexers).
+* `RELATIVEPATH`: The path to the file you're including, relative to the current file.
+* `PATHFROMROOT`: The path to the file relative to root, e.g. `/docs/admin/foo.yaml`
+
+To include a file that is hosted in the external, main Kubernetes repo, make sure it's added to [/update-imported-docs.sh](https://github.com/kubernetes/kubernetes.github.io/blob/master/update-imported-docs.sh), and run it so that the file gets downloaded, then enter:
+
+<pre>&#123;% include code.html language="&lt;LEXERVALUE&gt;" file="&lt;RELATIVEPATH&gt;" k8slink="&lt;PATHFROMK8SROOT&gt;" %&#125;</pre>
+
+* `PATHFROMK8SROOT`: The path to the file relative to the root of [the Kubernetes repo](https://github.com/kubernetes/kubernetes/tree/release-1.2), e.g. `/examples/rbd/foo.yaml`
+
+## Using tabs for multi-language examples
+
+By specifying some inline CSV in a varable called `tabspec`, you can include a file
+called `tabs.html` that generates tabs showing code examples in multiple langauges.
+
+<pre>&#123;% capture tabspec %&#125;servicesample
+JSON,json,service-sample.json,/docs/user-guide/services/service-sample.json
+YAML,yaml,service-sample.yaml,/docs/user-guide/services/service-sample.yaml&#123;% endcapture %&#125;
+&#123;% include tabs.html %&#125;</pre>
+
+In English, this would read: "Create a set of tabs with the alias `servicesample`,
+and have tabs visually labeled "JSON" and "YAML" that use `json` and `yaml` Rouge syntax highlighting, which display the contents of
+`service-sample.{extension}` on the page, and link to the file in GitHub at (full path)."
+
+Example file: [Pods: Multi-Container](http://kubernetes.io/docs/user-guide/pods/multi-container/).
+
+## Use a global variable
+
+The `/_config.yml` file defines some useful variables you can use when editing docs.
+
+* `page.githubbranch`: The name of the GitHub branch on the Kubernetes repo that is associated with this branch of the docs. e.g. `release-1.2`
+* `page.version` The version of Kubernetes associated with this branch of the docs. e.g. `v1.2`
+* `page.docsbranch` The name of the GitHub branch on the Docs/Website repo that you are currently using. e.g. `release-1.1` or `master`
+
+This keeps the docs you're editing aligned with the Kubernetes version you're talking about. For example, if you define a link like so, you'll never have to worry about it going stale in future doc branches:
+
+<pre>View the README [here](http://releases.k8s.io/&#123;&#123;page.githubbranch&#125;&#125;/cluster/addons/README.md).</pre>
+
+That, of course, will send users to:
+
+[http://releases.k8s.io/release-1.2/cluster/addons/README.md](http://releases.k8s.io/release-1.2/cluster/addons/README.md)
+
+(Or whatever Kubernetes release that docs branch is associated with.)
+
+## Branch structure
+
+The current version of the website is served out of the `master` branch.
+
+All versions of the site that relate to past and future versions will be named after their Kubernetes release number. For example, [the old branch for the 1.1 docs is called `release-1.1`](https://github.com/kubernetes/kubernetes.github.io/tree/release-1.1).
+
+Changes in the "docsv2" branch (where we are testing a revamp of the docs) are automatically staged here:
+http://k8sdocs.github.io/docs/tutorials/
+
+Changes in the "release-1.1" branch (for k8s v1.1 docs) are automatically staged here:
+http://kubernetes-v1-1.github.io/
+
+Changes in the "release-1.3" branch (for k8s v1.3 docs) are automatically staged here:
+http://kubernetes-v1-3.github.io/
+
+Editing of these branches will kick off a build using Travis CI that auto-updates these URLs; you can monitor the build progress at [https://travis-ci.org/kubernetes/kubernetes.github.io](https://travis-ci.org/kubernetes/kubernetes.github.io).
+
+## Config yaml guidelines
+
+Guidelines for config yamls that are included in the site docs. These
+are the yaml or json files that contain Kubernetes object
+configuration to be used with `kubectl create -f` Config yamls should
+be:
+
+* Separate deployable files, not embedded in the document, unless very
+  small variations of a full config.
+* Included in the doc with the include code
+  [above.](#include-code-from-another-file)
+* In the same directory as the doc that they are being used in
+  * If you are re-using a yaml from another doc, that is OK, just
+    leave it there, don't move it up to a higher level directory.
+* Tested in
+  [test/examples_test.go](https://github.com/kubernetes/kubernetes.github.io/blob/master/test/examples_test.go)
+* Follows
+  [best practices.](http://kubernetes.io/docs/user-guide/config-best-practices/)
+
+Don't assume the reader has this repository checked out, use `kubectl
+create -f https://github...` in example commands. For Docker images
+used in config yamls, try to use an image from an existing Kubernetes
+example. If creating an image for a doc, follow the
+[example guidelines](https://github.com/kubernetes/kubernetes/blob/master/examples/guidelines.md#throughout)
+section on "Docker images" from the Kubernetes repository.
+
+## Partners
+Kubernetes partners refers to the companies who contribute to the Kubernetes core codebase and/or extend their platform to support Kubernetes. Partners can get their logos added to the partner section of the [community page](http://k8s.io/community) by following the below steps and meeting the below logo specifications. Partners will also need to have a URL that is specific to integrating with Kubernetes ready; this URL will be the destination when the logo is clicked.
+
+* The partner product logo should be a transparent png image centered in a 215x125 px frame. (look at the existing logos for reference)
+* The logo must link to a URL that is specific to integrating with Kubernetes, hosted on the partner's site.
+* The logo should be named *product-name*_logo.png and placed in the `/images/community_logos` folder.
+* The image reference (including the link to the partner URL) should be added in `community.html` under `<div class="partner-logos" > ...</div>`.
+* Please do not change the order of the existing partner images. Append your logo to the end of the list.
+* Once completed and tested the look and feel, submit the pull request.

 ## Thank you!

-Kubernetes thrives on community participation, and we appreciate your contributions to our website and our documentation!
+Kubernetes thrives on community participation and we really appreciate your
+contributions to our site and our documentation!
@@ -1,15 +0,0 @@
-# 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
@@ -0,0 +1,29 @@
+name: Kubernetes
+markdown: kramdown
+kramdown:
+  input: GFM
+  html_to_native: true
+  hard_wrap: false
+  syntax_highlighter: rouge
+baseurl: /
+incremental: true
+
+safe: false
+lsi: false
+
+defaults:
+  -
+    scope:
+      path: ""
+    values:
+      version: "v1.3"
+      githubbranch: "master"
+      docsbranch: "release-1.3"
+  -
+    scope:
+      path: "docs"
+    values:
+      layout: docwithnav
+      showedit: true
+
+permalink: pretty
@@ -0,0 +1,5 @@
+tocs:
+- guides
+- reference
+- samples
+- support
@@ -0,0 +1,300 @@
+bigheader: "Guides"
+abstract: "How to get started, and achieve tasks, using Kubernetes"
+toc:
+- title: Guides
+  path: /docs/
+
+- title: Getting Started
+  section:
+  - title: What is Kubernetes?
+    path: /docs/whatisk8s/
+  - title: Installing Kubernetes on Linux with kubeadm
+    path: /docs/getting-started-guides/kubeadm/
+  - title: Hello World on Google Container Engine
+    path: /docs/hellonode/
+  - title: Downloading or Building Kubernetes
+    path: /docs/getting-started-guides/binary_release/
+  - title: Online Training Course
+    path: https://www.udacity.com/course/scalable-microservices-with-kubernetes--ud615
+
+- title: Accessing the Cluster
+  section:
+  - title: Installing and Setting up kubectl
+    path: /docs/user-guide/prereqs/
+  - title: Accessing Clusters
+    path: /docs/user-guide/accessing-the-cluster/
+  - title: Sharing Cluster Access with kubeconfig
+    path: /docs/user-guide/sharing-clusters/
+  - title: Authenticating Across Clusters with kubeconfig
+    path: /docs/user-guide/kubeconfig-file/
+
+- title: User Guide
+  path: /docs/user-guide/
+
+- title: Web UI (Dashboard)
+  path: /docs/user-guide/ui/
+
+- title: Workload Deployment and Management
+  section:
+  - title: Launching, Exposing, and Killing Applications
+    path: /docs/user-guide/quick-start/
+  - title: Deploying Applications
+    path: /docs/user-guide/deploying-applications/
+  - title: Managing Resources
+    path: /docs/user-guide/managing-deployments/
+  - title: Replication Controller Operations
+    path: /docs/user-guide/replication-controller/operations/
+  - title: Resizing a Replication Controller
+    path: /docs/user-guide/resizing-a-replication-controller/
+  - title: Rolling Updates
+    path: /docs/user-guide/rolling-updates/
+  - title: Rolling Update Demo
+    path: /docs/user-guide/update-demo/
+  - title: Secrets Walkthrough
+    path: /docs/user-guide/secrets/walkthrough/
+  - title: Using ConfigMap
+    path: /docs/user-guide/configmap/
+  - title: Horizontal Pod Autoscaling
+    path: /docs/user-guide/horizontal-pod-autoscaling/walkthrough/
+  - title: Best Practices for Configuration
+    path: /docs/user-guide/config-best-practices/
+  - title: Using kubectl to Manage Resources
+    path: /docs/user-guide/working-with-resources/
+  - title: Garbage Collection (Beta)
+    path: /docs/user-guide/garbage-collection/
+  - title: Using NetworkPolicy
+    section:
+    - title: Example Walkthrough
+      path: /docs/getting-started-guides/network-policy/walkthrough/
+    - title: Using Calico for NetworkPolicy 
+      path: /docs/getting-started-guides/network-policy/calico/
+
+- title: Batch Jobs
+  section:
+  - title: Jobs
+    path: /docs/user-guide/jobs/
+  - title: Parallel Processing using Expansions
+    path: /docs/user-guide/jobs/expansions/
+  - title: Coarse Parallel Processing using a Work Queue
+    path: /docs/user-guide/jobs/work-queue-1/
+  - title: Fine Parallel Processing using a Work Queue
+    path: /docs/user-guide/jobs/work-queue-2/
+
+- title: Service Discovery and Load Balancing
+  section:
+  - title: Connecting Applications with Services
+    path: /docs/user-guide/connecting-applications/
+  - title: Service Operations
+    path: /docs/user-guide/services/operations/
+  - title: Creating an External Load Balancer
+    path: /docs/user-guide/load-balancer/
+  - title: Configuring Your Cloud Provider's Firewalls
+    path: /docs/user-guide/services-firewalls/
+  - title: Cross-cluster Service Discovery using Federated Services
+    path: /docs/user-guide/federation/federated-services/
+
+- title: Containers and Pods
+  section:
+  - title: Running Your First Containers
+    path: /docs/user-guide/simple-nginx/
+  - title: Creating Single-Container Pods
+    path: /docs/user-guide/pods/single-container/
+  - title: Creating Multi-Container Pods
+    path: /docs/user-guide/pods/multi-container/
+  - title: Configuring Containers
+    path: /docs/user-guide/configuring-containers/
+  - title: Working with Containers in Production
+    path: /docs/user-guide/production-pods/
+  - title: Commands and Capabilities
+    path: /docs/user-guide/containers/
+  - title: Using Environment Variables
+    path: /docs/user-guide/environment-guide/
+  - title: Managing Compute Resources
+    path: /docs/user-guide/compute-resources/
+  - title: The Lifecycle of a Pod
+    path: /docs/user-guide/pod-states/
+  - title: Checking Pod Health
+    path: /docs/user-guide/liveness/
+  - title: Container Lifecycle Hooks
+    path: /docs/user-guide/container-environment/
+  - title: Assigning Pods to Nodes
+    path: /docs/user-guide/node-selection/
+  - title: Using the Downward API to Convey Pod Properties
+    path: /docs/user-guide/downward-api/
+  - title: Downward API Volumes
+    path: /docs/user-guide/downward-api/volume
+  - title: Persistent Volumes Walkthrough
+    path: /docs/user-guide/persistent-volumes/walkthrough/
+  - title: Bootstrapping Pet Sets
+    path: /docs/user-guide/petset/bootstrapping/
+
+- title: Monitoring, Logging, and Debugging Containers
+  section:
+  - title: Resource Usage Monitoring
+    path: /docs/user-guide/monitoring/
+  - title: Logging
+    path: /docs/getting-started-guides/logging/
+  - title: Logging with Elasticsearch and Kibana
+    path: /docs/getting-started-guides/logging-elasticsearch/
+  - title: Running Commands in a Container with kubectl exec
+    path: /docs/user-guide/getting-into-containers/
+  - title: Connect with Proxies
+    path: /docs/user-guide/connecting-to-applications-proxy/
+  - title: Connect with Port Forwarding
+    path: /docs/user-guide/connecting-to-applications-port-forward/
+  - title: Using Explorer to Examine the Runtime Environment
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/explorer
+
+- title: Creating a Cluster
+  section:
+  - title: Picking the Right Solution
+    path: /docs/getting-started-guides/
+  - title: Running Kubernetes on Your Local Machine
+    section:
+    - title: Running Kubernetes Locally via Minikube
+      path: /docs/getting-started-guides/minikube/
+    - title: Deprecated Alternatives
+      path: /docs/getting-started-guides/alternatives/
+  - title: Running Kubernetes on Turn-key Cloud Solutions
+    section:
+    - title: Running Kubernetes on Google Container Engine
+      path: https://cloud.google.com/container-engine/docs/before-you-begin/
+    - title: Running Kubernetes on Google Compute Engine
+      path: /docs/getting-started-guides/gce/
+    - title: Running Kubernetes on AWS EC2
+      path: /docs/getting-started-guides/aws/
+    - title: Running Kubernetes on Azure (Weave-based)
+      path: /docs/getting-started-guides/coreos/azure/
+    - title: Running Kubernetes on Azure (Flannel-based)
+      path: /docs/getting-started-guides/azure/
+    - title: Running Kubernetes on CenturyLink Cloud
+      path: /docs/getting-started-guides/clc/
+    - title: Running Kubernetes on IBM SoftLayer
+      path: https://github.com/patrocinio/kubernetes-softlayer
+  - title: Running Kubernetes on Custom Solutions
+    section:
+    - title: Creating a Custom Cluster from Scratch
+      path: /docs/getting-started-guides/scratch/
+    - title: Custom Cloud Solutions
+      section:
+      - title: CoreOS on AWS or GCE
+        path: /docs/getting-started-guides/coreos/
+      - title: Ubuntu on AWS or Joyent
+        path: /docs/getting-started-guides/juju/
+      - title: CoreOS on Rackspace
+        path: /docs/getting-started-guides/rackspace/
+    - title: On-Premise VMs
+      section:
+      - title: CoreOS on Vagrant
+        path: /docs/getting-started-guides/coreos/
+      - title: Cloudstack
+        path: /docs/getting-started-guides/cloudstack/
+      - title: VMware vSphere
+        path: /docs/getting-started-guides/vsphere/
+      - title: VMware Photon Controller
+        path: /docs/getting-started-guides/photon-controller/
+      - title: Juju
+        path: /docs/getting-started-guides/juju/
+      - title: DCOS
+        path: /docs/getting-started-guides/dcos/
+      - title: CoreOS on libvirt
+        path: /docs/getting-started-guides/libvirt-coreos/
+      - title: oVirt
+        path: /docs/getting-started-guides/ovirt/
+      - title: OpenStack Heat
+        path: /docs/getting-started-guides/openstack-heat/
+      - title: CoreOS on Multinode Cluster
+        path: /docs/getting-started-guides/coreos/coreos_multinode_cluster/
+      - title: rkt
+        section:
+        - title: Running Kubernetes with rkt
+          path: /docs/getting-started-guides/rkt/
+        - title: Known Issues when Using rkt
+          path: /docs/getting-started-guides/rkt/notes/
+      - title: Kubernetes on Mesos
+        path: /docs/getting-started-guides/mesos/
+      - title: Kubernetes on Mesos on Docker
+        path: /docs/getting-started-guides/mesos-docker/
+    - title: Bare Metal
+      section:
+      - title: Offline
+        path: /docs/getting-started-guides/coreos/bare_metal_offline/
+      - title: Fedora via Ansible
+        path: /docs/getting-started-guides/fedora/fedora_ansible_config/
+      - title: Fedora (Single Node)
+        path: /docs/getting-started-guides/fedora/fedora_manual_config/
+      - title: Fedora (Multi Node)
+        path: /docs/getting-started-guides/fedora/flannel_multi_node_cluster/
+      - title: CentOS
+        path: /docs/getting-started-guides/centos/centos_manual_config/
+      - title: CoreOS
+        path: /docs/getting-started-guides/coreos
+      - title: CoreOS with Calico
+        path: /docs/getting-started-guides/coreos/bare_metal_calico/
+      - title: Ubuntu
+        path: /docs/getting-started-guides/ubuntu/
+      - title: Ubuntu Nodes with Calico
+        path: /docs/getting-started-guides/ubuntu-calico/
+    - title: Validate Node Setup
+      path: /docs/admin/node-conformance
+  - title: Portable Multi-Node Cluster
+    path: /docs/getting-started-guides/docker-multinode/
+  - title: Building Large Clusters
+    path: /docs/admin/cluster-large/
+  - title: Running in Multiple Zones
+    path: /docs/admin/multiple-zones/
+  - title: Building High-Availability Clusters
+    path: /docs/admin/high-availability/
+
+- title: Administering Clusters
+  section:
+  - title: Admin Guide
+    path: /docs/admin/
+  - title: Cluster Management Guide
+    path: /docs/admin/cluster-management/
+  - title: Installing Addons
+    path: /docs/admin/addons/
+  - title: Sharing a Cluster with Namespaces
+    path: /docs/admin/namespaces/
+  - title: Namespaces Walkthrough
+    path: /docs/admin/namespaces/walkthrough/
+  - title: Setting Pod CPU and Memory Limits
+    path: /docs/admin/limitrange/
+  - title: Understanding Resource Quotas
+    path: /docs/admin/resourcequota/
+  - title: Applying Resource Quotas and Limits
+    path: /docs/admin/resourcequota/walkthrough/
+  - title: Kubernetes Components
+    path: /docs/admin/cluster-components/
+  - title: Configuring Kubernetes Use of etcd
+    path: /docs/admin/etcd/
+  - title: Federating Clusters
+    path: /docs/admin/federation/
+  - title: Using Multiple Clusters
+    path: /docs/admin/multi-cluster/
+  - title: Changing Cluster Size
+    path: https://github.com/kubernetes/kubernetes/wiki/User-FAQ#how-do-i-change-the-size-of-my-cluster/
+  - title: Configuring Multiple Schedulers
+    path: /docs/admin/multiple-schedulers/
+  - title: Networking in Kubernetes
+    path: /docs/admin/networking/
+  - title: Using DNS Pods and Services
+    path: /docs/admin/dns/
+  - title: Setting Up and Configuring DNS
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/cluster-dns
+  - title: Master <-> Node Communication
+    path: /docs/admin/master-node-communication/
+  - title: Network Plugins
+    path: /docs/admin/network-plugins/
+  - title: Static Pods
+    path: /docs/admin/static-pods/
+  - title: Configuring kubelet Garbage Collection
+    path: /docs/admin/garbage-collection/
+  - title: Configuring Out Of Resource Handling
+    path: /docs/admin/out-of-resource/    
+  - title: Configuring Kubernetes with Salt
+    path: /docs/admin/salt/
+  - title: Monitoring Node Health
+    path: /docs/admin/node-problem/
+  - title: AppArmor
+    path: /docs/admin/apparmor/
@@ -0,0 +1,19 @@
+overrides:
+- path: docs/api-reference
+- path: docs/user-guide/kubectl
+- path: docs/admin/federation-apiserver.md
+- path: docs/admin/federation-controller-manager.md
+- path: docs/admin/kube-apiserver.md
+- path: docs/admin/kube-controller-manager.md
+- path: docs/admin/kube-proxy.md
+- path: docs/admin/kube-scheduler.md
+- path: docs/admin/kubelet.md
+- changedpath: docs/api-reference/extensions/v1beta1/definitions.html _includes/v1.4/extensions-v1beta1-definitions.html
+- changedpath: docs/api-reference/extensions/v1beta1/operations.html _includes/v1.4/extensions-v1beta1-operations.html
+- changedpath: docs/api-reference/v1/definitions.html _includes/v1.4/v1-definitions.html
+- changedpath: docs/api-reference/v1/operations.html _includes/v1.4/v1-operations.html
+- copypath: k8s/federation/docs/api-reference/ docs/federation/
+- copypath: k8s/cluster/saltbase/salt/fluentd-gcp/fluentd-gcp.yaml docs/getting-started-guides/fluentd-gcp.yaml
+- copypath: k8s/examples/blog-logging/counter-pod.yaml docs/getting-started-guides/counter-pod.yaml
+- copypath: k8s/examples/blog-logging/counter-pod.yaml docs/user-guide/counter-pod.yaml
+
@@ -0,0 +1,262 @@
+bigheader: "Reference Documentation"
+abstract: "Design docs, concept definitions, and references for APIs and CLIs."
+toc:
+- title: Reference Documentation
+  path: /docs/reference/
+
+- title: Kubernetes API
+  section:
+  - title: Kubernetes API Overview
+    path: /docs/api/
+  - title: Accessing the API
+    section:
+    - title: Overview
+      path: /docs/admin/accessing-the-api/
+    - title: Authenticating
+      path: /docs/admin/authentication/
+    - title: Using Authorization Plugins
+      path: /docs/admin/authorization/
+    - title: Using Admission Controllers
+      path: /docs/admin/admission-controllers/
+    - title: Managing Service Accounts
+      path: /docs/admin/service-accounts-admin/
+  - title: Kubernetes API Operations
+    path: /docs/api-reference/v1/operations/
+  - title: Kubernetes API Definitions
+    path: /docs/api-reference/v1/definitions/
+  - title: Kubernetes API Swagger Spec
+    path: /kubernetes/third_party/swagger-ui/
+
+- title: Autoscaling API
+  section:
+  - title: Autoscaling API Operations
+    path: /docs/api-reference/autoscaling/v1/operations/
+  - title: Autoscaling API Definitions
+    path: /docs/api-reference/autoscaling/v1/definitions/
+
+- title: Batch API
+  section:
+  - title: Batch API Operations
+    path: /docs/api-reference/batch/v1/operations/
+  - title: Batch API Definitions
+    path: /docs/api-reference/batch/v1/definitions/
+    
+- title: Extensions API
+  section:
+  - title: Extensions API Operations
+    path: /docs/api-reference/extensions/v1beta1/operations/
+  - title: Extensions API Definitions
+    path: /docs/api-reference/extensions/v1beta1/definitions/    
+
+- title: kubectl CLI
+  section:
+  - title: kubectl Overview
+    path: /docs/user-guide/kubectl-overview/
+  - title: kubectl for Docker Users
+    path: /docs/user-guide/docker-cli-to-kubectl/
+  - title: kubectl Usage Conventions
+    path: /docs/user-guide/kubectl-conventions/
+  - title: JSONpath Support
+    path: /docs/user-guide/jsonpath/
+  - title: kubectl Cheat Sheet
+    path: /docs/user-guide/kubectl-cheatsheet/
+  - title: kubectl Commands
+    section:
+    - title: kubectl
+      path: /docs/user-guide/kubectl/kubectl/
+    - title: kubectl annotate
+      path: /docs/user-guide/kubectl/kubectl_annotate/
+    - title: kubectl api-versions
+      path: /docs/user-guide/kubectl/kubectl_api-versions/
+    - title: kubectl apply
+      path: /docs/user-guide/kubectl/kubectl_apply/
+    - title: kubectl attach
+      path: /docs/user-guide/kubectl/kubectl_attach/
+    - title: kubectl autoscale
+      path: /docs/user-guide/kubectl/kubectl_autoscale/
+    - title: kubectl cluster-info
+      path: /docs/user-guide/kubectl/kubectl_cluster-info/
+    - title: kubectl config
+      path: /docs/user-guide/kubectl/kubectl_config/
+    - title: kubectl config current-context
+      path: /docs/user-guide/kubectl/kubectl_config_current-context/
+    - title: kubectl config set-cluster
+      path: /docs/user-guide/kubectl/kubectl_config_set-cluster/
+    - title: kubectl config set-context
+      path: /docs/user-guide/kubectl/kubectl_config_set-context/
+    - title: kubectl config set-credentials
+      path: /docs/user-guide/kubectl/kubectl_config_set-credentials/
+    - title: kubectl config set
+      path: /docs/user-guide/kubectl/kubectl_config_set/
+    - title: kubectl config unset
+      path: /docs/user-guide/kubectl/kubectl_config_unset/
+    - title: kubectl config use-context
+      path: /docs/user-guide/kubectl/kubectl_config_use-context/
+    - title: kubectl config view
+      path: /docs/user-guide/kubectl/kubectl_config_view/
+    - title: kubectl convert
+      path: /docs/user-guide/kubectl/kubectl_convert/
+    - title: kubectl cordon
+      path: /docs/user-guide/kubectl/kubectl_cordon/
+    - title: kubectl create
+      path: /docs/user-guide/kubectl/kubectl_create/
+    - title: kubectl create configmap
+      path: /docs/user-guide/kubectl/kubectl_create_configmap/
+    - title: kubectl create namespace
+      path: /docs/user-guide/kubectl/kubectl_create_namespace/
+    - title: kubectl create secret docker-registry
+      path: /docs/user-guide/kubectl/kubectl_create_secret_docker-registry/
+    - title: kubectl create secret
+      path: /docs/user-guide/kubectl/kubectl_create_secret/
+    - title: kubectl create secret generic
+      path: /docs/user-guide/kubectl/kubectl_create_secret_generic/
+    - title: kubectl create serviceaccount
+      path: /docs/user-guide/kubectl/kubectl_create_serviceaccount/
+    - title: kubectl delete
+      path: /docs/user-guide/kubectl/kubectl_delete/
+    - title: kubectl describe
+      path: /docs/user-guide/kubectl/kubectl_describe/
+    - title: kubectl drain
+      path: /docs/user-guide/kubectl/kubectl_drain/
+    - title: kubectl edit
+      path: /docs/user-guide/kubectl/kubectl_edit/
+    - title: kubectl exec
+      path: /docs/user-guide/kubectl/kubectl_exec/
+    - title: kubectl explain
+      path: /docs/user-guide/kubectl/kubectl_explain/
+    - title: kubectl expose
+      path: /docs/user-guide/kubectl/kubectl_expose/
+    - title: kubectl get
+      path: /docs/user-guide/kubectl/kubectl_get/
+    - title: kubectl label
+      path: /docs/user-guide/kubectl/kubectl_label/
+    - title: kubectl logs
+      path: /docs/user-guide/kubectl/kubectl_logs/
+    - title: kubectl patch
+      path: /docs/user-guide/kubectl/kubectl_patch/
+    - title: kubectl port-forward
+      path: /docs/user-guide/kubectl/kubectl_port-forward/
+    - title: kubectl proxy
+      path: /docs/user-guide/kubectl/kubectl_proxy/
+    - title: kubectl replace
+      path: /docs/user-guide/kubectl/kubectl_replace/
+    - title: kubectl rolling-update
+      path: /docs/user-guide/kubectl/kubectl_rolling-update/
+    - title: kubectl rollout
+      path: /docs/user-guide/kubectl/kubectl_rollout/
+    - title: kubectl rollout history
+      path: /docs/user-guide/kubectl/kubectl_rollout_history/
+    - title: kubectl rollout pause
+      path: /docs/user-guide/kubectl/kubectl_rollout_pause/
+    - title: kubectl rollout resume
+      path: /docs/user-guide/kubectl/kubectl_rollout_resume/
+    - title: kubectl rollout undo
+      path: /docs/user-guide/kubectl/kubectl_rollout_undo/
+    - title: kubectl run
+      path: /docs/user-guide/kubectl/kubectl_run/
+    - title: kubectl scale
+      path: /docs/user-guide/kubectl/kubectl_scale/
+    - title: kubectl uncordon
+      path: /docs/user-guide/kubectl/kubectl_uncordon/
+    - title: kubectl version
+      path: /docs/user-guide/kubectl/kubectl_version/
+    - title: Superseded and Deprecated Commands
+      section:
+      - title: kubectl namespace
+        path: /docs/user-guide/kubectl/kubectl_namespace/
+      - title: kubectl stop
+        path: /docs/user-guide/kubectl/kubectl_stop/
+
+- title: Kubernetes Components
+  section:
+  - title: kube-apiserver
+    path: /docs/admin/kube-apiserver/
+  - title: kube-controller-manager
+    path: /docs/admin/kube-controller-manager/    
+  - title: kube-proxy
+    path: /docs/admin/kube-proxy/
+  - title: kube-scheduler
+    path: /docs/admin/kube-scheduler/
+  - title: kubelet
+    path: /docs/admin/kubelet/
+
+- title: Glossary
+  section:
+  - title: Annotations
+    path: /docs/user-guide/annotations/  
+  - title: Daemon Sets
+    path: /docs/admin/daemons/
+  - title: Deployments    
+    path: /docs/user-guide/deployments/
+  - title: Horizontal Pod Autoscaling
+    path: /docs/user-guide/horizontal-pod-autoscaling/    
+  - title: Images
+    path: /docs/user-guide/images/
+  - title: Ingress Resources
+    path: /docs/user-guide/ingress/    
+  - title: Jobs
+    path: /docs/user-guide/jobs/    
+  - title: Labels and Selectors
+    path: /docs/user-guide/labels/
+  - title: Names
+    path: /docs/user-guide/identifiers/
+  - title: Namespaces
+    path: /docs/user-guide/namespaces/
+  - title: Network Policies 
+    path: /docs/user-guide/networkpolicies/    
+  - title: Nodes
+    path: /docs/admin/node/    
+  - title: Persistent Volumes
+    path: /docs/user-guide/persistent-volumes/    
+  - title: Pet Sets
+    path: /docs/user-guide/petset/    
+  - title: Pods
+    path: /docs/user-guide/pods/
+  - title: Pod Security Policies
+    path: /docs/user-guide/pod-security-policy/
+  - title: Replica Sets
+    path: /docs/user-guide/replicasets/
+  - title: Replication Controller
+    path: /docs/user-guide/replication-controller/    
+  - title: Resource Quotas
+    path: /docs/admin/resource-quota/    
+  - title: Scheduled Jobs
+    path: /docs/user-guide/scheduled-jobs/
+  - title: Secrets
+    path: /docs/user-guide/secrets/
+  - title: Security Context
+    path: /docs/user-guide/security-context/
+  - title: Services
+    path: /docs/user-guide/services/
+  - title: Service Accounts
+    path: /docs/user-guide/service-accounts/
+  - title: Volumes
+    path: /docs/user-guide/volumes/
+
+- title: Kubernetes Design Docs
+  section:
+  - title: Kubernetes Architecture
+    path: https://github.com/kubernetes/kubernetes/blob/release-1.3/docs/design/architecture.md
+  - title: Kubernetes Design Overview
+    path: https://github.com/kubernetes/kubernetes/blob/release-1.3/docs/design/
+  - title: Kubernetes Identity and Access Management
+    path: https://github.com/kubernetes/kubernetes/blob/release-1.3/docs/design/access.md
+  - title: Kubernetes OpenVSwitch GRE/VxLAN networking
+    path: /docs/admin/ovs-networking/    
+  - title: Security Contexts
+    path: https://github.com/kubernetes/kubernetes/blob/release-1.3/docs/design/security_context.md
+  - title: Security in Kubernetes
+    path: https://github.com/kubernetes/kubernetes/blob/release-1.3/docs/design/security.md    
+
+- title: Federation
+  section:
+  - title: User guide
+    path: /docs/user-guide/federation/
+  - title: Federation API
+    path: /docs/federation/api-reference/README/
+  - title: Federation Components
+    section:
+    - title: federation-apiserver
+      path: /docs/admin/federation-apiserver.md
+    - title : federation-controller-mananger
+      path: /docs/admin/federation-controller-manager.md
@@ -0,0 +1,77 @@
+bigheader: "Samples"
+abstract: "A collection of example applications that show how to use Kubernetes."
+toc:
+- title: Samples
+  path: /docs/samples/
+
+- title: Storage / Database / KV
+  section:
+  - title: Apache Cassandra Database
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/cassandra
+  - title: Ceph
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/rbd/
+  - title: CephFS
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/cephfs/
+  - title: GlusterFS
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/glusterfs/
+  - title: Hazelcast
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/hazelcast
+  - title: iSCSI
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/iscsi/
+  - title: MySQL Galera
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/mysql-galera
+  - title: NFS
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/nfs/
+  - title: Redis
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/redis/
+  - title: RethinkDB
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/rethinkdb/
+  - title: Vitess
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/vitess/
+
+- title: Big Data
+  section:
+  - title: Apache Spark
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/spark
+  - title: Apache Storm
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/storm
+
+- title: Messaging / Queueing
+  section:
+  - title: Celery + RabbitMQ
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/celery-rabbitmq
+  - title: Hazelcast
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/hazelcast
+
+- title: Miscellaneous
+  section:
+  - title: Meteor Applications
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/meteor/
+  - title: OpenShift Origin
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/openshift-origin/
+  - title: Selenium
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/selenium/
+
+- title: Monitoring and Logging
+  section:
+  - title: Elasticsearch
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/elasticsearch/
+  - title: NewRelic
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/newrelic
+
+- title: Multi-tier Applications
+  section:
+  - title: Guestbook - Go Server
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/guestbook-go/
+  - title: GuestBook - PHP Server
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/guestbook/
+  - title: MEAN stack on Google Cloud Platform
+    path: /docs/getting-started-guides/meanstack/
+  - title: MySQL + Wordpress
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/mysql-wordpress-pd/
+  - title: MySQL + Phabricator Server
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/phabricator/
+  - title: Nodejs + Mongo
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/nodesjs-mongodb
+  - title: Petstore
+    path: https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/k8petstore/
@@ -0,0 +1,44 @@
+bigheader: "Support"
+abstract: "Troubleshooting resources, frequently asked questions, and community support channels."
+toc:
+- title: Support
+  path: /docs/troubleshooting/
+
+- title: Troubleshooting
+  section:
+  - title: Debugging Pods and Replication Controllers
+    path: /docs/user-guide/debugging-pods-and-replication-controllers/
+  - title: Application Introspection and Debugging
+    path: /docs/user-guide/introspection-and-debugging/
+  - title: Retrieving Logs
+    path: /docs/user-guide/logging/
+  - title: Troubleshooting Applications
+    path: /docs/user-guide/application-troubleshooting/
+  - title: Troubleshooting Clusters
+    path: /docs/admin/cluster-troubleshooting/
+  - title: Debugging Services
+    path: /docs/user-guide/debugging-services/
+
+- title: Frequently Asked Questions
+  section:
+  - title: User FAQ
+    path: https://github.com/kubernetes/kubernetes/wiki/User-FAQ/
+  - title: Debugging FAQ
+    path: https://github.com/kubernetes/kubernetes/wiki/Debugging-FAQ/
+  - title: Services FAQ
+    path: https://github.com/kubernetes/kubernetes/wiki/Services-FAQ/
+
+- title: Other Resources
+  section:
+  - title: Kubernetes Issue Tracker on GitHub
+    path: https://github.com/kubernetes/kubernetes/issues/
+  - title: Report a Security Vulnerability
+    path: /docs/reporting-security-issues/
+  - title: Release Notes
+    path: https://github.com/kubernetes/kubernetes/releases/
+  - title: Release Roadmap
+    path: https://github.com/kubernetes/kubernetes/milestones/
+  - title: Contributing to Kubernetes Documentation
+    path: /editdocs/
+  - title: New Template Instructions
+    path: /docs/templatedemos/
@@ -0,0 +1,11 @@
+{% 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></a><img src="/images/copycode.svg" style="max-height:24px" onClick="copyCode('{{include.file | handleize}}')" title="Copy {{include.file}} to clipboard"></th></tr></thead>
+<tr><td>{{ mysample | markdownify }}</td></tr></table>
@@ -0,0 +1,25 @@
+<footer>
+	<main class="light-text">
+		<nav>
+			<a href="/docs/hellonode/">Get Started</a>
+			<a href="/docs/">Documentation</a>
+			<a href="http://blog.kubernetes.io/">Blog</a>
+			<a href="/community/">Community</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>
+			</div>
+		</div>
+		<div id="miceType" class="center">&copy; {{ 'now' | date: "%Y" }} Kubernetes</div>
+	</main>
+</footer>
@@ -0,0 +1,67 @@
+{% if page.title %}{% assign title=page.title %}{% endif %}
+<head>
+	<meta charset="utf-8">
+	<meta name="viewport" content="width=device-width, initial-scale=1">
+	<link rel="canonical" href="http://kubernetes.io{{page.url}}" />
+	<link rel="shortcut icon" type="image/png" href="/images/favicon.png">
+	<link href='https://fonts.googleapis.com/css?family=Roboto:400,100,100italic,300,300italic,400italic,500,500italic,700,700italic,900,900italic' rel='stylesheet' type='text/css'>
+	<link rel="stylesheet" href='https://fonts.googleapis.com/css?family=Roboto+Mono' type='text/css'>
+	<link rel="stylesheet" href="/css/styles.css"/>
+        <link rel="stylesheet" href="/css/jquery-ui.min.css">
+        <link rel="stylesheet" href="/css/sweetalert.css">
+	<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>
+	<title>Kubernetes - {{ title }}</title>
+</head>
+<body>
+<div id="cellophane" onclick="kub.toggleMenu()"></div>
+<header>
+	<a href="/" class="logo"></a>
+	<div class="nav-buttons" data-auto-burger="primary">
+		<a href="/docs/" class="button" id="viewDocs" data-auto-burger-exclude>View Documentation</a>
+		<a href="/docs/hellonode/" 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/hellonode/">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/">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>
@@ -0,0 +1,17 @@
+{% assign tabsraw = tabspec | newline_to_br | split: '<br />' %}
+{% assign tabsetname = tabsraw[0] %}
+<script>$(function(){$("#{{tabsetname}}").tabs();});</script>
+<div id="{{tabsetname}}">
+  <ul>{% for tab in tabsraw offset:1 %}{% assign thisTab = tab | split: ',' %}
+    <li><a href="#{{ thisTab[0] | strip | handleize }}">{{ thisTab[0] | strip}}</a></li>{% endfor %}
+  </ul>
+  {% for tab in tabsraw offset:1 %}
+  {% assign thisTab = tab | split: ',' %}
+  {% assign tabLang=thisTab[1] %}
+  {% assign tabFile=thisTab[2] %}
+  {% assign tabGHLink=thisTab[3] %}
+  <div id="{{ thisTab[0] | strip | handleize }}">
+  {% include code.html language=tabLang file=tabFile ghlink=tabGHLink %}
+  </div>
+  {% endfor %}
+</div>
@@ -0,0 +1,16 @@
+### 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 -->
@@ -0,0 +1,88 @@
+{% 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 %}
@@ -0,0 +1,37 @@
+{% 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 %}
@@ -0,0 +1,121 @@
+{% if page.cards %}<!-- check for this before going any further; if not present, skip to else at bottom -->
+<style>
+h2, h3, h4 {
+  border-bottom: 0px !important;
+  font-size: 22px !important;
+  padding-bottom: 20px !important;
+}
+.colContainer {
+  padding-top:2px;
+  padding-left: 2px;
+  overflow: auto;
+}
+#samples a {
+  color: #000;
+}
+.col3rd {
+  display: block;
+  float: left;
+  margin-right: 30px;
+  margin-bottom: 30px;
+  overflow: hidden;
+}
+.col3rd h3, .col2nd h3 {
+  margin-bottom: 0px !important;
+}
+.col3rd .button, .col2nd .button {
+  margin-top: 20px;
+  border-radius: 2px;
+}
+.col3rd p, .col2nd p {
+  margin-left: 2px;
+}
+.col2nd {
+  display: block;
+  width: 400px;
+  float: left;
+  margin-right: 30px;
+  margin-bottom: 30px;
+  overflow: hidden;
+}
+.shadowbox {
+  width: 250px;
+  display: inline;
+  float: left;
+  text-transform: none;
+  font-weight: bold;
+  text-overflow: ellipsis;
+  overflow: hidden;
+  line-height: 24px;
+  position: relative;
+  display: block;
+  cursor: pointer;
+  box-shadow: 0 2px 2px rgba(0,0,0,.24),0 0 2px rgba(0,0,0,.12);
+  border-radius: 5px;
+  background: #fff;
+  transition: all .3s;
+  padding: 16px;
+  margin: 0 16px 16px 0;
+  text-decoration: none;
+  letter-spacing: .01em;
+  height: 220px;
+}
+.shadowbox img {
+    min-width: 100px;
+    max-width: 100px;
+    max-height: 50px;
+    margin-right: 5px;
+    margin-bottom: 5px;
+    float: left;
+}
+</style>
+
+<div class="colContainer">
+{% for card in page.cards %}{% if card.title %}
+  <div class="col3rd shadowbox">
+    <h3>{{card.title}}</h3>
+    <p>{% if card.image %}<img src="{{card.image}}">{% endif %}{{card.description}}</p>
+  </div>
+{% endif %}{% endfor %}
+</div>
+
+{% else %}
+
+### ERROR: You must define "cards" front-matter YAML
+{: style="color:red" }
+
+This template requires that you insert YAML at the top of your document
+that defines the "cards" you'd like to display on the page. The cards will
+render in clickable boxes. 
+
+To get rid of this message and take advantage of this template, define `cards`:
+
+```yaml
+---
+cards:
+- progression: no
+- card:
+  title: Mean Stack
+  image: /docs/meanstack/image_0.png
+  description: Lorem ipsum dolor it verberum.
+- card:
+  title: Guestbook + Redis
+  image: /images/docs/redis.svg
+  description: Lorem ipsum dolor it verberum.
+- card:
+  title: Cloud Native Cassandra
+  image: /images/docs/cassandra.svg
+  description: Lorem ipsum dolor it verberum.
+- card:
+  title: WordPress + MySQL
+  image: /images/docs/wordpress.svg
+  description: Lorem ipsum dolor it verberum. 
+---
+```
+
+**Note:** If `progression` is set to `yes` then a "Start Here!" icon will be
+placed on the first card and arrows suggesting linear reading will be overlayed
+between the other cards, telling the reader that they should explore the content
+in a certain order. 
+
+{% endif %}
@@ -0,0 +1,36 @@
+{% if purpose %}
+
+### Purpose
+
+{{ purpose }}
+
+{% else %}
+
+{% include templates/_errorthrower.md missing_block='purpose' heading='Purpose' purpose='states, in one sentence, what the purpose of this document is, so that the user will know what they are able to achieve if they follow the provided steps.' %}
+
+{% endif %}
+
+{% if recommended_background %}
+
+### Recommended background
+
+{{ recommended_background }}
+
+{% else %}
+
+{% include templates/_errorthrower.md missing_block='recommended_background' heading='Recommended background' purpose='lists assumptions of baseline knowledge that you expect the user to have before reading ahead.' %}
+
+{% endif %}
+
+
+{% if step_by_step %}
+
+### Step by step
+
+{{ step_by_step }}
+
+{% else %}
+
+{% include templates/_errorthrower.md missing_block='step_by_step' heading='Step by step' purpose='lists a series of linear, numbered steps that accomplish the described task.' %}
+
+{% endif %}
@@ -0,0 +1 @@
+{% for item in tree %}{% if item.section %}{% assign tree = item.section %}{% include tocsearch.html %}{% else %}{% if item.path == page.url %}{% assign foundTOC = thistoc %}{% assign title = item.title %}{% break %}{% endif %}{% endif %}{% endfor %}
@@ -0,0 +1,6 @@
+{% for item in tree %}{% if item.section %}
+<div class="item" data-title="{{ item.title }}">
+  <div class="container">{% assign tree = item.section %}{% include tree.html %}
+  </div>
+</div>{% else %}{% assign prefix = item.path | slice: 0, 4 %}{% if prefix == "http" %}{% assign target=" target='_blank'" %}{% else %}{% assign target="" %}{% endif %}
+    <a class="item" data-title="{{ item.title }}" href="{{ item.path }}"{{ target }}></a>{% endif %}{% endfor %}
@@ -0,0 +1,83 @@
+{% for thistoc in site.data.globals.tocs %}{% if foundTOC %}{% break %}{% else %}{% assign tree = site.data[thistoc].toc %}{% include tocsearch.html %}{% endif %}{% endfor %}
+{% for override in site.data.overrides.overrides %}{% if page.path contains override.path %}{% assign notitle = "true" %}{% endif %}{% endfor %}
+<!Doctype html>
+<html id="docs" class="{{site.data[foundTOC].bigheader}}">
+
+{% include head-header.html %}
+
+<!--  HERO  -->
+<section id="hero" class="light-text">
+	<h1>{{ site.data[foundTOC].bigheader }}</h1>
+	<h5>{{ site.data[foundTOC].abstract }}</h5>
+	<div id="vendorStrip" class="light-text">
+		<ul>
+			<li><a href="/docs/" {% if site.data[foundTOC].bigheader == "Guides" %}class="YAH"{% endif %}>GUIDES</a></li>
+			<li><a href="/docs/reference" {% if site.data[foundTOC].bigheader == "Reference Documentation" %}class="YAH"{% endif %}>REFERENCE</a></li>
+			<li><a href="/docs/samples" {% if site.data[foundTOC].bigheader == "Samples" %}class="YAH"{% endif %}>SAMPLES</a></li>
+			<li><a href="/docs/troubleshooting/" {% if site.data[foundTOC].bigheader == "Support" %}class="YAH"{% endif %}>SUPPORT</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)">
+		</div>
+	</div>
+</section>
+
+<section id="encyclopedia">
+	<div id="docsToc">
+        <div class="pi-accordion">
+        {% assign tree = site.data[foundTOC].toc %}{% include tree.html %}
+        </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>
+    	{% if notitle != "true" %}<h1>{{ title }}</h1>{% endif %}
+		{{ content }}
+        <p><a href=""><img src="https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/{{ page.path }}?pixel" alt="Analytics" /></a>
+        {% if page.url != "/404.html" && page.url != "/docs/search/" %}<div id="pd_rating_holder_8345992"></div>
+		<script type="text/javascript">
+	        PDRTJS_settings_8345992 = {
+		        "id" : "8345992",
+		        "unique_id" : "{{page.url}}",
+		        "title" : "{{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' +
+		window.location.pathname + '&body=Issue%20with%20' +
+		window.location.pathname)" class="button issue">Create Issue</a>
+		<a href="/editdocs#{{ page.path }}" class="button issue">Edit This Page</a>
+	{% endif %}
+	</div>
+</section>
+
+{% include footer.html %}
+
+<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');
+</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 -->
+</body>
+</html>
@@ -0,0 +1,199 @@
+/* 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
+
@@ -0,0 +1,283 @@
+$main-max-width: 1200px
+$vendor-strip-height: 44px
+$video-section-height: 550px
+
+@media screen and (min-width: 1025px)
+	#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: 30%
+
+				#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 20px 20px
+		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
+
+	#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_thm.jpg)
+		background-position: center center
+		background-size: cover
+
+
+
+	#talkToUs
+		h4
+			br
+				display: block
+
+		#bigSocial
+			div
+				width: calc(25% - 15px)
+
+			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: 25%
+				float: left
+				font-size: 24px
+				font-weight: 300
+
+		.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
+		#hero
+			text-align: left
+
+			h1
+				padding: 20px
+
+		#tryKubernetes
+			width: auto
+			background-color: $blue
+			padding: 0 20px
@@ -0,0 +1,61 @@
+html, body
+	margin: 0
+	padding: 0
+
+
+input, button
+	outline: none
+
+button
+	cursor: pointer
+
+ul, li
+	list-style: none
+
+ul
+	margin: 0
+	padding: 0
+
+a
+	text-decoration: none
+
+// CONVENIENCE
+.clear
+	display: block
+	clear: both
+
+.light-text
+	color: white
+
+.right
+	float: right
+
+.left
+	float: left
+
+.center
+	text-align: center
+
+
+//mixins
+@mixin fullScreen
+	position: fixed
+	top: 0
+	left: 0
+	width: 100vw
+	height: 100vh
+
+
+@mixin pureCenter($left: 50%, $top: 50%)
+	position: absolute
+	top: $top
+	left: $left
+	transform: translate(-50%, -50%)
+
+
+@mixin maintain-aspect-ratio ($width-factor: 16, $height-factor: 9, $target-width: 80vw, $target-height: 80vh)
+	width: $target-width
+	height: $target-width * ($height-factor / $width-factor)
+	max-width: $target-height * ($width-factor / $height-factor)
+	max-height: $target-height
+
@@ -0,0 +1,86 @@
+h1
+	font-size: $h1-font-size
+	line-height: $h1-line-height
+
+h2
+	font-size: $h2-font-size
+	line-height: $h2-line-height
+
+h3
+	font-size: $h3-font-size
+	line-height: $h3-line-height
+
+h4
+	font-size: $h4-font-size
+	line-height: $h4-line-height
+
+h5
+	font-size: $h5-font-size
+	line-height: $h5-line-height
+
+p
+	font-size: $p-font-size
+	line-height: $p-line-height
+
+section, header, #vendorStrip
+	padding-left: $full-width-paddingX
+	padding-right: $full-width-paddingX
+
+	main
+		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
@@ -0,0 +1,25 @@
+$blue: #3371e3
+$light-grey: #f7f7f7
+$dark-grey: #303030
+$medium-grey: #4c4c4c
+$white: #ffffff
+
+$base-font: 'Roboto', sans-serif
+$mono-font: 'Roboto Mono', monospace
+
+
+*, .button
+	box-sizing: border-box
+	font-family: $base-font
+	background: none
+	margin: 0
+	border: 0
+
+body
+	font-family: $base-font
+
+h1, h2, h5, p
+	font-weight: 300
+
+h3, h4
+	font-weight: 400
@@ -0,0 +1,246 @@
+// 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-size: 24px
+				font-weight: 400
+				text-decoration: none
+				margin-bottom: 15px
+
+	// FOOTER
+	footer
+		nav
+			text-align: center
+
+			a
+				font-size: 22px
+				width: auto
+				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
@@ -1,6 +0,0 @@
---
-title: "{{ replace .Name "-" " " | title }}"
-date: {{ .Date }}
-draft: true
---
-
@@ -1,10 +0,0 @@
-# See the OWNERS docs at https://go.k8s.io/owners
-
-# Allow CSS/SASS updates from blog and case studies owners 
-options:
-  no_parent_owners: false
-reviewers:
-  - alexcontini
-approvers:
-  - alexcontini
-  
@@ -1,99 +0,0 @@
-// SASS for Case Studies pages go here:
-
-hr
-  background-color: #999999
-
-h2
-  margin-bottom: 15px !important
-
-.subhead
-  padding-bottom: 2% !important
-  padding-top: 0% !important
-
-.details
-  margin-left: 1.9%
-  padding-right: 5%
-  font-size: 16px !important
-  padding-bottom: 2% !important
-
-.section1
-  margin-bottom: 3%
-  .cols
-    width: 80% !important
-    margin-left: 6.8%
-    padding-top: 1.5%
-    .col1
-      width: 52% !important
-      font-weight: 300 !important
-    .col2
-      width: 46% !important
-
-.banner2text
-  width: 63%
-  padding-top: 10%
-  padding-left: 0% !important
-  float: initial !important
-  text-align: center
-  margin: 0 auto
-  position: relative
-
-.banner3text, .banner4text, .banner5text
-  width: 63%
-  padding-left: 0% !important
-  float: initial !important
-  text-align: center
-  margin: 0 auto
-  position: relative
-
-.fullcol
-  float: initial !important
-
-body footer
-  background-color: #585858 !important
-
-.section1
-  float: left !important
-
-.banner1
-  padding-left: 11.9% !important
-
-.banner2
-  float: initial !important
-  padding-bottom: 2% !important
-
-footer
-  padding: 0% 7%
-
-.banner4, .banner3, .banner5
-  float: initial !important
-
-@media screen and (max-width: 910px)
-  .banner2text
-    width: 47%
-    padding-top: 45%
-  .details
-    margin-left: 0%
-    margin-bottom: 3%
-  .subhead
-    padding-bottom: 0% !important
-    padding-top: 0% !important
-  .banner3
-    width: 100% !important
-
-@media screen and (max-width: 780px)
-  .section1 .cols
-    width: 100% !important
-    margin-left: 0%
-    padding-top: 5%
-    .col1, .col2
-      width: 100% !important
-      margin-left: 0% !important
-  .fullcol
-    width: 90% !important
-    margin-left: 5% !important
-  .banner1
-    padding-left: 10% !important
-    margin-bottom: 6% !important
-  .banner2text
-    padding-top: 60% !important
-    padding-bottom: 2% !important
@@ -1,296 +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: 250px
-
-        #search
-          vertical-align: middle
-
-    .flyout-button
-      display: none
-
-    .logo
-      position: relative
-      float: left
-      display: block
-      width: 180px
-      height: 88px
-      top: 0
-      left: 0
-      transform: none
-      background-image: url(../images/nav_logo.svg)
-
-    &.flip-nav, &.open-nav
-      .logo
-        background-image: url(../images/nav_logo2.svg)
-
-
-  #encyclopedia
-    padding: 50px 50px 100px 100px
-    clear: both
-
-  #docsToc
-    position: relative
-    float: left
-    padding: 0 20px
-    left: 0
-    width: 350px
-    z-index: auto
-
-    .push-menu-close-button
-      display: none
-
-  #docsContent
-    width: calc(100% - 400px)
-
-    #editPageButton
-      right: -25px
-
-  section, header, footer
-    main
-      max-width: $main-max-width
-
-  header, #vendorStrip, #encyclopedia, #hero h1, #hero h5, #docs #hero h1, #docs #hero h5,
-  #community #hero h1, .gridPage #hero h1, #community #hero h5, .gridPage #hero h5
-    padding-left: 100px
-    padding-right: 100px
-
-  #vendorStrip
-    padding-right: 10px
-
-  #home
-    section, header, footer
-      main
-        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-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
-
-@media screen and (min-width: 1300px)
-  #vendorStrip
-    padding-right: 100px
-
-@media screen and (min-width: 456px)
-  #vendorStrip
-    li + li
-      margin-left: 20px
@@ -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
-
@@ -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
@@ -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
@@ -1,248 +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
-      height: 160px
-
-      .content
-        display: table-cell
-        position: relative
-        vertical-align: middle
-
-      .image-wrapper
-        position: absolute
-        top: 50%
-        max-width: 25%
-        max-height: 100%
-        transform: translateY(-50%)
-
-      &:nth-child(odd)
-        padding-right: 210px
-
-        .image-wrapper
-          right: 0
-
-      &:nth-child(even)
-        padding-left: 210px
-
-        .image-wrapper
-          left: 0
-
-      &:nth-child(1)
-        padding-right: 0
-
-        h3, p
-          text-align: center
-
-        .image-wrapper
-          position: relative
-          display: block
-          float: none
-          max-width: 100%
-          transform: none
-
-        .content
-          display: block
-
-      img
-        width: 100%
-
-
-  #video
-    height: $video-section-height
-    display: block
-
-    & > .light-text
-      display: block
-
-  #mobileShowVideoButton
-    display: none
-
-  #features
-    padding-bottom: 60px
-
-    .feature-box
-      margin-bottom: 30px
-
-      &:last-child
-        margin-bottom: 0
-
-    h3
-      margin-bottom: $features-h3-margin-bottom
-
-    .feature-box
-      & > div
-        width: $feature-box-div-width
-        margin-bottom: $feature-box-div-margin-bottom
-
-  #talkToUs
-    #bigSocial
-      div
-        width: calc(50% - 15px)
-
-      div + div
-        margin-top: 0
-
-      div:nth-child(2)
-        margin-left: 20px
-
-      div:nth-child(3)
-
-      div:nth-child(4)
-        margin-left: 20px
-
-      a
-        display: inline-block
-        color: $blue
-        font-weight: 400
-        text-decoration: none
-
-  // FOOTER
-  footer
-    nav
-      text-align: center
-
-      a
-        width: 30%
-        padding: 0 20px
-
-    .social
-      text-align: center
-
-      div
-        display: inline-block
-
-      div:last-child
-        display: block
-        margin: 0
-
-      span
-        display: inline-block
-        margin-right: 10px
-
-      input
-        text-align: left
-
-
-
-  #home #caseStudiesWrapper
-    div
-      width: 48%
@@ -1,11 +0,0 @@
-@import "reset"
-@import "skin"
-
-// media queries
-@import "base"
-@import "tablet"
-@import "desktop"
-
-{{ if .Params.case_study_styles }}
-@import "case-studies"
-{{ end }}
@@ -1,3 +0,0 @@
-# Kubernetes Community Code of Conduct
-
-Please refer to our [Kubernetes Community Code of Conduct](https://git.k8s.io/community/code-of-conduct.md)
@@ -0,0 +1,112 @@
+---
+title: Community
+---
+
+<!Doctype html>
+<html id="community">
+{% include head-header.html %}
+
+<section id="hero" class="light-text">
+	<h1>Community</h1>
+</section>
+
+
+
+<section id="mainContent">
+	<main>
+		<div class="content">
+			<h3>Ensuring Kubernetes works well everywhere and for everyone.</h3>
+			<p>Connect with the Kubernetes community on our <a href="http://slack.k8s.io/">Slack channel</a> or join the
+				<a href="https://groups.google.com/forum/#!forum/kubernetes-dev">Kubernetes-dev Google group</a>. A weekly
+				community meeting takes place via video conference to discuss the state of affairs,
+				<a href="https://groups.google.com/forum/#!forum/kubernetes-community-video-chat">get a calendar invite</a>
+				to participate.</p>
+		</div>
+		<div class="content">
+			<h3>SIGs</h3>
+			<p>Have a special interest in how Kubernetes works with another technology?  See our ever growing
+				<a href="https://github.com/kubernetes/kubernetes/wiki/Special-Interest-Groups-(SIGs)">lists of SIGs</a>,
+				from AWS and Openstack to Big Data and Scalability, there’s a place for you to contribute and instructions
+				for forming a new SIG if your special interest isn’t covered (yet).</p>
+		</div>
+		<div class="content">
+			<h3>Customers</h3>
+			<div class="company-logos">
+				<img src="/images/community_logos/zulily_logo.png">
+				<img src="/images/community_logos/we_pay_logo.png">
+				<img src="/images/community_logos/goldman_sachs_logo.png">
+				<img src="/images/community_logos/ebay_logo.png">
+				<img src="/images/community_logos/box_logo.png">
+				<img src="/images/community_logos/wikimedia_logo.png">
+				<img src="/images/community_logos/soundcloud_logo.png">
+				<img src="/images/community_logos/new_york_times_logo.png">
+				<img src="/images/community_logos/kabam_logo.png">
+			</div>
+		</div>
+		<div class="content">
+			<h3>Events</h3>
+			<div id="calendarWrapper">
+				<iframe src="https://calendar.google.com/calendar/embed?src=nt2tcnbtbied3l6gi2h29slvc0%40group.calendar.google.com&ctz=America/Los_Angeles"
+				        frameborder="0" scrolling="no"></iframe>
+			</div>
+		</div>
+		<div class="content">
+			<h3>Partners</h3>
+			<p>We are working with a broad group of partners who contribute to the kubernetes core codebase, making it stronger and richer, as well as help in growing the kubernetes ecosystem supporting
+				a sprectrum of compelmenting platforms, from open source solutions to market-leading technologies.</p>
+			<div class="partner-logos">
+        <a href="https://coreos.com/kubernetes"><img src="/images/community_logos/core_os_logo.png"></a>
+				<a href="https://deis.com"><img src="/images/community_logos/deis_logo.png"></a>
+				<a href="https://sysdig.com/blog/monitoring-kubernetes-with-sysdig-cloud/"><img src="/images/community_logos/sysdig_cloud_logo.png"></a>
+				<a href="https://puppet.com/blog/managing-kubernetes-configuration-puppet"><img src="/images/community_logos/puppet_logo.png"></a>
+				<a href="https://www.citrix.com/blogs/2016/07/15/citrix-kubernetes-a-home-run/"><img src="/images/community_logos/citrix_logo.png"></a>
+				<a href="http://wercker.com/workflows/partners/kubernetes/"><img src="/images/community_logos/wercker_logo.png"></a>
+				<a href="http://rancher.com/kubernetes/"><img src="/images/community_logos/rancher_logo.png"></a>
+				<a href="https://www.openshift.com/"><img src="/images/community_logos/red_hat_logo.png"></a>
+				<a href="https://tectonic.com/press/intel-coreos-collaborate-on-openstack-with-kubernetes.html"><img src="/images/community_logos/intel_logo.png"></a>
+				<a href="https://elasticbox.com/kubernetes/"><img src="/images/community_logos/elastickube_logo.png"></a>
+				<a href="https://platform9.com/blog/containers-as-a-service-kubernetes-docker"><img src="/images/community_logos/platform9_logo.png"></a>
+				<a href="http://www.appformix.com/solutions/appformix-for-kubernetes/"><img src="/images/community_logos/appformix_logo.png"></a>
+				<a href="http://kubernetes.io/docs/getting-started-guides/dcos/"><img src="/images/community_logos/mesosphere_logo.png"></a>
+				<a href="http://docs.datadoghq.com/integrations/kubernetes/"><img src="/images/community_logos/datadog_logo.png"></a>
+				<a href="https://apprenda.com/kubernetes-support/"><img src="/images/community_logos/apprenda_logo.png"></a>
+				<a href="http://www.ibm.com/cloud-computing/"><img src="/images/community_logos/ibm_logo.png"></a>
+				<a href="http://info.crunchydata.com/blog/advanced-crunchy-containers-for-postgresql"><img src="/images/community_logos/crunchy_data_logo.png"></a>
+				<a href="https://content.mirantis.com/Containerizing-OpenStack-on-Kubernetes-Video-Landing-Page.html"><img src="/images/community_logos/mirantis_logo.png"></a>
+				<a href="http://blog.aquasec.com/security-best-practices-for-kubernetes-deployment"><img src="/images/community_logos/aqua_logo.png"></a>
+				<a href="https://jujucharms.com/canonical-kubernetes/"><img src="/images/community_logos/ubuntu_cannonical_logo.png"></a>
+				<a href="https://github.com/nuagenetworks/nuage-kubernetes"><img src="/images/community_logos/nuage_network_logo.png"></a>
+			</div>
+		</div>
+	</main>
+</section>
+
+<section id="talkToUs">
+	<main>
+		<h3>Talk to Us!</h3>
+		<h4>We would love to hear from you, how you are using Kubernetes,<br> and what we can do to make it better.</h4>
+		<div id="bigSocial">
+			<div>
+				<a href="https://twitter.com/kubernetesio">@kubernetesio</a>
+				<p>Get the latest news and updates.</p>
+			</div>
+			<div>
+				<a href="https://github.com/kubernetes/kubernetes">Github Project</a>
+				<p>Check out the project and consider contributing.</p>
+			</div>
+			<div>
+				<a href="http://slack.k8s.io/">#kubernetes-users</a>
+				<p>Our Slack channel is the best way to contact our engineers and share your ideas with them.</p>
+			</div>
+			<div>
+				<a href="http://stackoverflow.com/questions/tagged/kubernetes">Stack Overflow</a>
+				<p>Our user forum is a great place to go for community support.</p>
+			</div>
+		</div>
+	</main>
+</section>
+
+{% include footer.html %}
+
+</body>
+</html>
@@ -1,260 +0,0 @@
-baseURL = "https://kubernetes.io"
-title = "Kubernetes"
-
-defaultContentLanguage = "en"
-defaultContentLanguageInSubdir = false
-enableRobotsTXT = true
-disableBrowserError = true
-
-disableKinds = ["taxonomy", "taxonomyTerm"]
-
-ignoreFiles = [ "^OWNERS$", "README[-]+[a-z]*\\.md", "^node_modules$", "content/en/docs/doc-contributor-tools" ]
-
-contentDir = "content/en"
-
-timeout = 3000
-
-# Highlighting config.
-pygmentsCodeFences = true
-pygmentsUseClasses = false
-# See https://help.farbox.com/pygments.html
-pygmentsStyle = "emacs"
-
-# Enable Git variables like commit, lastmod
-enableGitInfo = true
-
-# Norwegian ("no") is sometimes but not currently used for testing.
-# Hindi is disabled because it's currently in development.
-# Italian is disabled until it meets minimum standards for quality.
-disableLanguages = ["hi", "it", "no"]
-
-[blackfriday]
-hrefTargetBlank = true
-fractions = false
-
-[frontmatter]
-date = ["date", ":filename", "publishDate", "lastmod"]
-
-[permalinks]
-blog = "/:section/:year/:month/:day/:slug/"
-
-# Be explicit about the output formats. We (currently) only want an RSS feed for the home page.
-[outputs]
-home = [ "HTML", "RSS", "HEADERS" ]
-page = [ "HTML"]
-section = [ "HTML"]
-
-# Add a "text/netlify" media type for auto-generating the _headers file
-[mediaTypes]
-[mediaTypes."text/netlify"]
-delimiter = ""
-
-[outputFormats]
-[outputFormats.RSS]
-baseName = "feed"
-
-# _headers file output (uses the template at layouts/index.headers)
-[outputFormats.HEADERS]
-mediatype = "text/netlify"
-baseName = "_headers"
-isPlainText = true
-notAlternative = true
-
-[params]
-
-time_format_blog = "Monday, January 02, 2006"
-description = "Production-Grade Container Orchestration"
-showedit = true
-
-latest = "v1.18"
-
-fullversion = "v1.14.10"
-version = "v1.14"
-githubbranch = "v1.14.10"
-docsbranch = "release-1.14"
-deprecated = true
-currentUrl = "https://kubernetes.io/docs/home/"
-nextUrl = "https://kubernetes-io-vnext-staging.netlify.com/"
-githubWebsiteRepo = "github.com/kubernetes/website"
-githubWebsiteRaw = "raw.githubusercontent.com/kubernetes/website"
-
-[params.pushAssets]
-css = [
-  "callouts",
-  "styles",
-  "custom-jekyll/tags"
-]
-js = [
-  "custom-jekyll/tags",
-  "script"
-]
-
-[[params.versions]]
-fullversion = "v1.18.0"
-version = "v1.18"
-githubbranch = "v1.18.0"
-docsbranch = "release-1.18"
-url = "https://kubernetes.io"
-
-[[params.versions]]
-fullversion = "v1.17.4"
-version = "v1.17"
-githubbranch = "v1.17.4"
-docsbranch = "release-1.17"
-url = "https://v1-17.docs.kubernetes.io"
-
-[[params.versions]]
-fullversion = "v1.16.8"
-version = "v1.16"
-githubbranch = "v1.16.8"
-docsbranch = "release-1.16"
-url = "https://v1-16.docs.kubernetes.io"
-
-[[params.versions]]
-fullversion = "v1.15.11"
-version = "v1.15"
-githubbranch = "v1.15.11"
-docsbranch = "release-1.15"
-url = "https://v1-15.docs.kubernetes.io"
-
-[[params.versions]]
-fullversion = "v1.14.10"
-version = "v1.14"
-githubbranch = "v1.14.10"
-docsbranch = "release-1.14"
-url = "https://v1-14.docs.kubernetes.io"
-
-# Language definitions.
-
-[languages]
-[languages.en]
-title = "Kubernetes"
-description = "Production-Grade Container Orchestration"
-languageName ="English"
-# Weight used for sorting.
-weight = 1
-
-[languages.zh]
-title = "Kubernetes"
-description = "Production-Grade Container Orchestration"
-languageName = "中文 Chinese"
-weight = 2
-contentDir = "content/zh"
-
-[languages.zh.params]
-time_format_blog = "2006.01.02"
-language_alternatives = ["en"]
-deprecated = false
-
-[languages.ko]
-title = "Kubernetes"
-description = "Production-Grade Container Orchestration"
-languageName = "한국어 Korean"
-weight = 3
-contentDir = "content/ko"
-
-[languages.ko.params]
-time_format_blog = "2006.01.02"
-language_alternatives = ["en"]
-
-[languages.ja]
-title = "Kubernetes"
-description = "Production-Grade Container Orchestration"
-languageName = "日本語 Japanese"
-weight = 4
-contentDir = "content/ja"
-
-[languages.ja.params]
-time_format_blog = "2006.01.02"
-language_alternatives = ["en"]
-
-[languages.fr]
-title = "Kubernetes"
-description = "Production-Grade Container Orchestration"
-languageName ="Français"
-weight = 5
-contentDir = "content/fr"
-
-[languages.fr.params]
-time_format_blog = "02.01.2006"
-# A list of language codes to look for untranslated content, ordered from left to right.
-language_alternatives = ["en"]
-
-[languages.it]
-title = "Kubernetes"
-description = "Production-Grade Container Orchestration"
-languageName ="Italian"
-weight = 6
-contentDir = "content/it"
-
-[languages.it.params]
-time_format_blog = "02.01.2006"
-# A list of language codes to look for untranslated content, ordered from left to right.
-language_alternatives = ["en"]
-
-[languages.no]
-title = "Kubernetes"
-description = "Production-Grade Container Orchestration"
-languageName ="Norsk"
-weight = 7
-contentDir = "content/no"
-
-[languages.no.params]
-time_format_blog = "02.01.2006"
-# A list of language codes to look for untranslated content, ordered from left to right.
-language_alternatives = ["en"]
-
-[languages.de]
-title = "Kubernetes"
-description = "Production-Grade Container Orchestration"
-languageName ="Deutsch"
-weight = 8
-contentDir = "content/de"
-
-[languages.de.params]
-time_format_blog = "02.01.2006"
-# A list of language codes to look for untranslated content, ordered from left to right.
-language_alternatives = ["en"]
-
-[languages.es]
-title = "Kubernetes"
-description = "Production-Grade Container Orchestration"
-languageName ="Español"
-weight = 9
-contentDir = "content/es"
-
-[languages.es.params]
-time_format_blog = "02.01.2006"
-# A list of language codes to look for untranslated content, ordered from left to right.
-language_alternatives = ["en"]
-
-[languages.pt]
-title = "Kubernetes"
-description = "Orquestração de contêineres em nível de produção"
-languageName ="Português"
-weight = 9
-contentDir = "content/pt"
-
-[languages.pt.params]
-time_format_blog = "02.01.2006"
-# A list of language codes to look for untranslated content, ordered from left to right.
-language_alternatives = ["en"]
-
-[languages.id]
-title = "Kubernetes"
-description = "Production-Grade Container Orchestration"
-languageName ="Bahasa Indonesia"
-weight = 10
-contentDir = "content/id"
-
-[languages.id.params]
-time_format_blog = "02.01.2006"
-# A list of language codes to look for untranslated content, ordered from left to right.
-language_alternatives = ["en"]
-
-[languages.hi]
-title = "Kubernetes"
-description = "Production-Grade Container Orchestration"
-languageName ="Hindi"
-weight = 11
-contentDir = "content/hi"
@@ -1,13 +0,0 @@
-# See the OWNERS docs at https://go.k8s.io/owners
-
-# This is the localization project for German.
-# Teams and members are visible at https://github.com/orgs/kubernetes/teams.
-
-reviewers:
- sig-docs-de-reviews
-
-approvers:
- sig-docs-de-owners
-
-labels:
- language/de
@@ -1,3 +0,0 @@
---
-headless: true
---
@@ -1,62 +0,0 @@
---
-title: "Production-Grade Container Orchestration"
-abstract: "Automatisierte Bereitstellung, Skalierung und Verwaltung von Containern"
-cid: home
---
-
-{{< deprecationwarning >}}
-
-{{< blocks/section id="oceanNodes" >}}
-{{% blocks/feature image="flower" %}}
-### [Kubernetes (K8s)]({{< relref "/docs/concepts/overview/what-is-kubernetes" >}}) ist ein Open-Source-System zur Automatisierung der Bereitstellung, Skalierung und Verwaltung von containerisierten Anwendungen.
-
-Es gruppiert Container, aus denen sich eine Anwendung zusammensetzt, in logische Einheiten, um die Verwaltung und Erkennung zu erleichtern. Kubernetes baut auf [15 Jahre Erfahrung in Bewältigung von Produktions-Workloads bei Google] (http://queue.acm.org/detail.cfm?id=2898444), kombiniert mit Best-of-Breed-Ideen und Praktiken aus der Community.
-{{% /blocks/feature %}}
-
-{{% blocks/feature image="scalable" %}}
-#### Planet Scale
-
-Kubernetes basiert auf denselben Prinzipien, die es Google ermöglichen, Milliarden von Containern pro Woche zu betreiben.
-
-{{% /blocks/feature %}}
-
-{{% blocks/feature image="blocks" %}}
-#### Never Outgrow
-
-Unabhängig davon, ob Sie lokal testen oder ein globales Unternehmen betreiben, die Flexibilität von Kubernetes wächst mit Ihnen, um Ihre Anwendungen konsistent und einfach bereitzustellen, unabhängig von der Komplexität Ihrer Anforderungen.
-
-{{% /blocks/feature %}}
-
-{{% blocks/feature image="suitcase" %}}
-#### Run Anywhere
-
-Kubernetes ist Open Source und bietet Ihnen die Freiheit, die Infrastruktur vor Ort, Hybrid oder Public Cloud zu nutzen. So können Sie Workloads mühelos dorthin verschieben, wo es Ihnen wichtig ist.
-
-{{% /blocks/feature %}}
-
-{{< /blocks/section >}}
-
-{{< blocks/section id="video" background-image="kub_video_banner_homepage" >}}
-<div class="light-text">
-<h2>Die Herausforderungen bei der Migration von über 150 Microservices auf Kubernetes</h2>
-        <p>Von Sarah Wells, technischer Direktor für Betrieb und Zuverlässigkeit, Financial Times</p>
-        <button id="desktopShowVideoButton" onclick="kub.showVideo()">Video ansehen</button>
-        <br>
-        <br>
-        <br>
-        <a href="https://events.linuxfoundation.org/events/kubecon-cloudnativecon-europe-2019" button id="desktopKCButton">KubeCon vom 20-23. Mai 2019 in Barcelona</a>
-        <br>
-        <br>
-        <br>
-        <br>
-        <a href="https://www.lfasiallc.com/events/kubecon-cloudnativecon-china-2019" button id="desktopKCButton">KubeCon vom 24-26. Juni 2019 in Shanghai</a>
-</div>
-<div id="videoPlayer">
-    <iframe data-url="https://www.youtube.com/embed/H06qrNmGqyE?autoplay=1" frameborder="0" allowfullscreen></iframe>
-    <button id="closeButton"></button>
-</div>
-{{< /blocks/section >}}
-
-{{< blocks/kubernetes-features >}}
-
-{{< blocks/case-studies >}}
@@ -1,10 +0,0 @@
---
-title: Kubernetes Blog
-linkTitle: Blog
-menu:
-  main:
-    title: "Blog"
-    weight: 40
-    post: >
-       <p>Lesen Sie die neuesten Nachrichten über Kubernetes und das Containeruniversum im Allgemeinen. Erhalten Sie druckfrisch die neuesten Tutorials und technische Anleitungen.</p>
---
@@ -1,9 +0,0 @@
---
-title: Fallstudien
-linkTitle: Fallstudien
-bigheader: Kubernetes Anwenderberichte 
-abstract: Eine Sammlung von Benutzern, die Kubernetes in Produktion verwenden.
-layout: basic
-class: gridPage
-cid: caseStudies
---
@@ -1,61 +0,0 @@
---
-title: Community
-layout: basic
-cid: community
---
-
-<section id="mainContent">
-    <main>
-        <div class="content">
-            <h3>Die Gewissheit, dass Kubernetes überall und für alle gut funktioniert.</h3>
-            <p>Verbinden Sie sich mit der Kubernetes-Community in unserem <a href="http://slack.k8s.io/">Slack Kanal</a>, <a href="https://discuss.kubernetes.io/">Diskussionsforum</a>, oder beteiligen Sie sich an der <a href="https://groups.google.com/forum/#!forum/kubernetes-dev"> Kubernetes-dev-Google-Gruppe</a>. Eine wöchentliches Community-Meeting findet per Videokonferenz statt, um den Stand der Dinge zu diskutieren, folgen Sie
-		<a href="https://github.com/kubernetes/community/blob/master/events/community-meeting.md">diesen Anweisungen</a> für Informationen wie Sie teilnehmen können.</p>
-            <p>Sie können Kubernetes auch auf der ganzen Welt über unsere
-                <a href="https://www.meetup.com/topics/kubernetes/">Kubernetes Meetup Community</a> und der
-                <a href="https://www.meetup.com/Kubernetes-Cloud-Native-Online-Meetup/">Kubernetes Cloud Native Meetup Community</a> beitreten.</p>
-          </div>
-        <div class="content">
-            <h3>Special Interest Groups (SIGs)</h3>
-            <p>Haben Sie ein besonderes Interesse daran, wie Kubernetes mit einer anderen Technologie arbeitet?  Werfen Sie einen Blick auf unsere kontinuierlich wachsende
-                <a href="https://git.k8s.io/community/sig-list.md">Listen von SIGs</a>, von AWS und Openstack bis hin zu Big Data und Skalierbarkeit, es gibt einen Platz für Sie, an dem Sie mitwirken können, und Anweisungen zur Gründung einer neuen SIG finden, wenn Ihr besonderes Interesse (noch) nicht abgedeckt ist.
-            </p>
-
-            <p>Als Mitglied der Kubernetes-Community sind Sie herzlich eingeladen, an allen SIG-Treffen teilzunehmen, die Sie interessieren. Eine Registrierung ist nicht erforderlich.</p>
-
-        </div>
-
-        <div class="content">
-          <h3>Verhaltensregeln</h3>
-          <p>Die Kubernetes-Community schätzt Respekt und Inklusivität und setzt einen <a href="code-of-conduct/">Verhaltenskodex</a> 
-            in allen Interaktionen durch. Wenn Sie einen Verstoß gegen den Verhaltenskodex bei einer Veranstaltung oder Sitzung, 
-            in Slack oder in einem anderen Kommunikationsmechanismus feststellen, wenden Sie sich 
-            bitte an das <a href="https://github.com/kubernetes/community/tree/master/committee-code-of-conduct">Kubernetes Code of Conduct Committee</a> <a href="mailto:conduct@kubernetes.io">conduct@kubernetes.io</a>. Ihre Anonymität wird geschützt.
-          </p>
-         </div>
-    </main>
-</section>
-
-<section id="talkToUs">
-    <main>
-        <h3>Talk to Us!</h3>
-        <h4>Wir würden uns freuen, von Ihnen zu hören, wie Sie Kubernetes verwenden<br>und was wir tun können, um es besser zu machen.</h4>
-        <div id="bigSocial">
-            <div>
-                <a href="https://twitter.com/kubernetesio">@kubernetesio</a>
-                <p>Erhalten Sie die neuesten Nachrichten und Updates.</p>
-            </div>
-            <div>
-                <a href="https://github.com/kubernetes/kubernetes">Github Project</a>
-                <p>Informieren Sie sich über das Projekt und erwägen Sie, einen Beitrag zu leisten.</p>
-            </div>
-            <div>
-                <a href="http://slack.k8s.io/">#kubernetes-users</a>
-                <p>Unser Slack-Kanal ist der beste Weg, um unsere Ingenieure zu kontaktieren und Ihre Ideen mit ihnen zu teilen.</p>
-            </div>
-            <div>
-                <a href="http://stackoverflow.com/questions/tagged/kubernetes">Stack Overflow</a>
-                <p>Unser Benutzerforum ist ein großartiger Ort, um Community-Support zu erhalten.</p>
-            </div>
-        </div>
-    </main>
-</section>
@@ -1,3 +0,0 @@
---
-title: Dokumentation
---
@@ -1,75 +0,0 @@
---
-title: Konzepte
-main_menu: true
-content_template: templates/concept
-weight: 40
---
-
-{{% capture overview %}}
-
-Im Abschnitt Konzepte erfahren Sie mehr über die Teile des Kubernetes-Systems und die Abstraktionen, die Kubernetes zur Darstellung Ihres Clusters verwendet, und Sie erhalten ein tieferes Verständnis der Funktionsweise von Kubernetes.
-
-{{% /capture %}}
-
-{{% capture body %}}
-
-## Überblick
-
-Um mit Kubernetes zu arbeiten, verwenden Sie *Kubernetes-API-Objekte*, um den *gewünschten Status Ihres Clusters* zu beschreiben: 
-welche Anwendungen oder anderen Workloads Sie ausführen möchten, welche Containerimages sie verwenden, die Anzahl der Replikate, welche Netzwerk- und Festplattenressourcen Sie zur Verfügung stellen möchten, und vieles mehr. Sie legen den gewünschten Status fest, indem Sie Objekte mithilfe der Kubernetes-API erstellen, normalerweise über die Befehlszeilenschnittstelle `kubectl`. Sie können die Kubernetes-API auch direkt verwenden, um mit dem Cluster zu interagieren und den gewünschten Status festzulegen oder zu ändern.
-
-Sobald Sie den gewünschten Status eingestellt haben, wird das *Kubernetes Control Plane* dafür sorgen, dass der aktuelle Status des Clusters mit dem gewünschten Status übereinstimmt. Zu diesem Zweck führt Kubernetes verschiedene Aufgaben automatisch aus, z. B. Starten oder Neustarten von Containern, Skalieren der Anzahl der Repliken einer bestimmten Anwendung und vieles mehr. Das Kubernetes Control Plane besteht aus einer Reihe von Prozessen, die in Ihrem Cluster ausgeführt werden:
-
-* Der **Kubernetes Master** bestehet aus drei Prozessen, die auf einem einzelnen Node in Ihrem Cluster ausgeführt werden, der als Master-Node bezeichnet wird. Diese Prozesse sind:[kube-apiserver](/docs/admin/kube-apiserver/), [kube-controller-manager](/docs/admin/kube-controller-manager/) und [kube-scheduler](/docs/admin/kube-scheduler/).
-* Jeder einzelne Node in Ihrem Cluster, welcher nicht der Master ist, führt zwei Prozesse aus:
-  * **[kubelet](/docs/admin/kubelet/)**, das mit dem Kubernetes Master kommuniziert.
-  * **[kube-proxy](/docs/admin/kube-proxy/)**, ein Netzwerk-Proxy, der die Netzwerkdienste von Kubernetes auf jedem Node darstellt.
-
-## Kubernetes Objects
-
-Kubernetes enthält eine Reihe von Abstraktionen, die den Status Ihres Systems darstellen: implementierte containerisierte Anwendungen und Workloads, die zugehörigen Netzwerk- und Festplattenressourcen sowie weitere Informationen zu den Aufgaben Ihres Clusters. Diese Abstraktionen werden durch Objekte in der Kubernetes-API dargestellt; Lesen Sie [Kubernetes Objects Überblick](/docs/concepts/abstractions/overview/) für weitere Details. 
-
-Die grundlegenden Objekte von Kubernetes umfassen:
-
-* [Pod](/docs/concepts/workloads/pods/pod-overview/)
-* [Service](/docs/concepts/services-networking/service/)
-* [Volume](/docs/concepts/storage/volumes/)
-* [Namespace](/docs/concepts/overview/working-with-objects/namespaces/)
-
-Darüber hinaus enthält Kubernetes eine Reihe von Abstraktionen auf höherer Ebene, die als Controller bezeichnet werden. Controller bauen auf den Basisobjekten auf und bieten zusätzliche Funktionen und Komfortfunktionen. Sie beinhalten:
-
-* [ReplicaSet](/docs/concepts/workloads/controllers/replicaset/)
-* [Deployment](/docs/concepts/workloads/controllers/deployment/)
-* [StatefulSet](/docs/concepts/workloads/controllers/statefulset/)
-* [DaemonSet](/docs/concepts/workloads/controllers/daemonset/)
-* [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/)
-
-## Kubernetes Control Plane
-
-Die verschiedenen Teile der Kubernetes-Steuerungsebene (Control Plane), wie der Kubernetes Master- und der Kubelet-Prozess, bestimmen, wie Kubernetes mit Ihrem Cluster kommuniziert. Das Control Plane führt ein Inventar aller Kubernetes-Objekte im System und führt fortlaufende Steuerkreise aus, um den Status dieser Objekte zu verwalten. Zu jeder Zeit reagieren die Steuerkreise des Control Plane auf Änderungen im Cluster und arbeiten daran, dass der tatsächliche Status aller Objekte im System mit dem gewünschten Status, den Sie definiert haben, übereinstimmt.
-
-Wenn Sie beispielsweise mit der Kubernetes-API ein Deployment-Objekt erstellen, geben Sie einen neuen gewünschten Status für das System an. Das Kubernetes Control Plane zeichnet die Objekterstellung auf und führt Ihre Anweisungen aus, indem es die erforderlichen Anwendungen startet und sie für auf den Cluster-Nodes plant--Dadurch wird der tatsächliche Status des Clusters an den gewünschten Status angepasst.
-
-### Kubernetes Master
-
-Der Kubernetes-Master ist für die Aufrechterhaltung des gewünschten Status für Ihren Cluster verantwortlich. Wenn Sie mit Kubernetes interagieren, beispielsweise mit dem Kommanduzeilen-Tool `kubectl`, kommunizieren Sie mit dem Kubernetes-Master Ihres Clusters.
-
-> Der "Master" bezieht sich auf eine Reihe von Prozessen, die den Clusterstatus verwalten.  Normalerweise werden diese Prozesse alle auf einem einzigen Node im Cluster ausgeführt. Dieser Node wird auch als Master bezeichnet. Der Master kann repliziert werden um Verfügbarkeit und Redundanz zu erhöhen.
-
-### Kubernetes Nodes
-
-Die Nodes in einem Cluster sind die Maschinen (VMs, physische Server usw.), auf denen Ihre Anwendungen und Cloud-Workflows ausgeführt werden. Der Kubernetes-Master steuert jeden Master. Sie werden selten direkt mit Nodes interagieren.
-
-#### Objekt Metadata
-
-
-* [Anmerkungen](/docs/concepts/overview/working-with-objects/annotations/)
-
-{{% /capture %}}
-
-{{% capture whatsnext %}}
-
-Wenn Sie eine Konzeptseite schreiben möchten, lesen Sie [Seitenvorlagen verwenden](/docs/home/contribute/page-templates/)
-für Informationen zum Konzeptseitentyp und zur Dokumentations Vorlage.
-
-{{% /capture %}}
@@ -1,4 +0,0 @@
---
-title: "Kubernetes Architekur"
-weight: 30
---
@@ -1,72 +0,0 @@
---
-title: Master-Node Kommunikation
-content_template: templates/concept
-weight: 20
---
-
-{{% capture overview %}}
-
-Dieses Dokument katalogisiert die Kommunikationspfade zwischen dem Master (eigentlich dem Apiserver) und des Kubernetes-Clusters. 
-Die Absicht besteht darin, Benutzern die Möglichkeit zu geben, ihre Installation so anzupassen, dass die Netzwerkkonfiguration so abgesichert wird, dass der Cluster in einem nicht vertrauenswürdigen Netzwerk (oder mit vollständig öffentlichen IP-Adressen eines Cloud-Providers) ausgeführt werden kann.
-
-{{% /capture %}}
-
-
-{{% capture body %}}
-
-## Cluster zum Master
-
-Alle Kommunikationspfade vom Cluster zum Master enden beim Apiserver (keine der anderen Master-Komponenten ist dafür ausgelegt, Remote-Services verfügbar zu machen).
-In einem typischen Setup ist der Apiserver so konfiguriert, dass er Remote-Verbindungen an einem sicheren HTTPS-Port (443) mit einer oder mehreren Formen der [Clientauthentifizierung](/docs/reference/access-authn-authz/authentication/) überwacht.
-Eine oder mehrere Formene von [Autorisierung](/docs/reference/access-authn-authz/authorization/) sollte aktiviert sein, insbesondere wenn [anonyme Anfragen](/docs/reference/access-authn-authz/authentication/#anonymous-requests) oder [Service Account Tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens) aktiviert sind.
-
-Nodes sollten mit dem öffentlichen Stammzertifikat für den Cluster konfigurirert werden, sodass sie eine sichere Verbindung zum Apiserver mit gültigen Client-Anmeldeinformationen herstellen können.
-Beispielsweise bei einer gewöhnlichen GKE-Konfiguration enstprechen die dem kubelet zur Verfügung gestellten Client-Anmeldeinformationen eines Client-Zertifikats.
-Lesen Sie über [kubelet TLS bootstrapping](/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/) zur automatisierten Bereitstellung von kubelet-Client-Zertifikaten.
-
-Pods, die eine Verbindung zum Apiserver herstellen möchten, können dies auf sichere Weise tun, indem sie ein Dienstkonto verwenden, sodass Kubernetes das öffentliche Stammzertifikat und ein gültiges Trägertoken automatisch in den Pod einfügt, wenn er instanziert wird.
-Der `kubernetes`-Dienst (in allen Namespaces) ist mit einer virtuellen IP-Adresse konfiguriert, die (über den Kube-Proxy) an den HTTPS-Endpunkt auf dem Apiserver umgeleitet wird.
-
-Die Master-Komponenten kommunizieren auch über den sicheren Port mit dem Cluster-Apiserver.
-
-Der Standardbetriebsmodus für Verbindungen vom Cluster (Knoten und Pods, die auf den Knoten ausgeführt werden) zum Master ist daher standardmäßig gesichert und kann über nicht vertrauenswürdige und/oder öffentliche Netzwerke laufen.
-
-## Master zum Cluster
-
-Es gibt zwei primäre Kommunikationspfade vom Master (Apiserver) zum Cluster.
-Der erste ist vom Apiserver bis zum Kubelet-Prozess, der auf jedem Node im Cluster ausgeführt wird. 
-Der zweite ist vom Apiserver zu einem beliebigen Node, Pod oder Dienst über die Proxy-Funktionalität des Apiservers.
-
-### Apiserver zum kubelet
-
-Die Verbindungen vom Apiserver zum Kubelet werden verwendet für:
-
-  * Abrufen von Protokollen für Pods.
-  * Verbinden (durch kubectl) mit laufenden Pods.
-  * Bereitstellung der Portweiterleitungsfunktion des kubelet.
-
-Diese Verbindungen enden am HTTPS-Endpunkt des kubelet.
-Standardmäßig überprüft der Apiserver das Serverzertifikat des Kubelet nicht, was die Verbindung von angreifbar für Man-in-the-Middle-Angriffe macht, und ist es ist daher **unsicher** wenn die Verbindungen über nicht vertrauenswürdige und/oder öffentliche Netzwerke laufen.
-
-Um diese Verbindung zu überprüfen, verwenden Sie das Flag `--kubelet-certificate-authority`, um dem Apiserver ein Stammzertifikatbündel bereitzustellen, das zur Überprüfung des Server-Zertifikats des kubelet verwendet wird.
-
-Wenn dies nicht möglich ist, verwenden Sie [SSH tunneling](/docs/concepts/architecture/master-node-communication/#ssh-tunnels)
-zwischen dem Apiserver und kubelet, falls erforderlich, um eine Verbindung über ein nicht vertrauenswürdiges oder öffentliches Netz zu vermeiden.
-
-Ausserdem sollte, [Kubelet Authentifizierung und/oder Autorisierung](/docs/admin/kubelet-authentication-authorization/) sollte aktiviert sein, um die kubelet-API zu sichern.
-
-### Apiserver zu Nodes, Pods und Services
-
-Die Verbindungen vom Apiserver zu einem Node, Pod oder Dienst verwenden standardmäßig einfache HTTP-Verbindungen und werden daher weder authentifiziert noch verschlüsselt.
-Sie können über eine sichere HTTPS-Verbindung ausgeführt werden, indem dem Node, dem Pod oder dem Servicenamen in der API-URL "https:" vorangestellt wird. Das vom HTTPS-Endpunkt bereitgestellte Zertifikat wird jedoch nicht überprüft, und es werden keine Clientanmeldeinformationen bereitgestellt. Die Verbindung wird zwar verschlüsselt, garantiert jedoch keine Integrität.
-Diese Verbindungen **sind derzeit nicht sicher** innerhalb von nicht vertrauenswürdigen und/oder öffentlichen Netzen.
-
-### SSH Tunnels
-
-Kubernetes unterstützt SSH-Tunnel zum Schutz der Kommunikationspfade von Master -> Cluster.
-In dieser Konfiguration initiiert der Apiserver einen SSH-Tunnel zu jedem Nodem im Cluster (Verbindung mit dem SSH-Server, der Port 22 läuft), und leitet den gesamten Datenverkehr für ein kubelet, einen Node, einen Pod oder einen Dienst durch den Tunnel.
-Dieser Tunnel stellt sicher, dass der Datenverkehr nicht außerhalb des Netzwerks sichtbar ist, in dem die Knoten ausgeführt werden.
-
-SSH-Tunnel sind derzeit nicht mehr unterstützt. Sie sollten sie also nicht verwenden, es sei denn, Sie wissen, was Sie tun. Ein Ersatz für diesen Kommunikationskanal wird entwickelt.
-
-{{% /capture %}}
@@ -1,247 +0,0 @@
---
-title: Nodes
-content_template: templates/concept
-weight: 10
---
-
-{{% capture overview %}}
-
-Ein Knoten (Node in Englisch) ist eine Arbeitsmaschine in Kubernetes, früher als `minion` bekannt. Ein Node
-kann je nach Cluster eine VM oder eine physische Maschine sein. Jeder Node enthält
-die für den Betrieb von [Pods](/docs/concepts/workloads/pods/pod/) notwendigen Dienste 
-und wird von den Master-Komponenten verwaltet. 
-Die Dienste auf einem Node umfassen die [Container Runtime](/docs/concepts/overview/components/#node-components), das Kubelet und den Kube-Proxy. 
-Weitere Informationen finden Sie im Abschnitt Kubernetes Node in der Architekturdesign-Dokumentation.
-
-{{% /capture %}}
-
-
-{{% capture body %}}
-
-## Node Status
-
-Der Status eines Nodes enthält folgende Informationen:
-
-* [Adressen](#adressen)
-* [Zustand](#zustand)
-* [Kapazität](#kapazität)
-* [Info](#info)
-
-Jeder Abschnitt wird folgend detailliert beschrieben.
-
-### Adressen
-
-Die Verwendung dieser Felder hängt von Ihrem Cloud-Anbieter oder der Bare-Metal-Konfiguration ab.
-
-* HostName: Der vom Kernel des Nodes gemeldete Hostname. Kann mit dem kubelet-Parameter `--hostname-override` überschrieben werden.
-* ExternalIP: In der Regel die IP-Adresse des Nodes, die extern geroutet werden kann (von außerhalb des Clusters verfügbar).
-* InternalIP: In der Regel die IP-Adresse des Nodes, die nur innerhalb des Clusters routbar ist.
-
-
-### Zustand
-
-Das `conditions` Feld beschreibt den Zustand, aller `Running` Nodes.
-
-| Node Condition | Beschreibung |
-|----------------|-------------|
-| `OutOfDisk`    | `True` wenn auf dem Node nicht genügend freier Speicherplatz zum Hinzufügen neuer Pods vorhanden ist, andernfalls `False` |
-| `Ready`        | `True` wenn der Node in einem guten Zustand und bereit ist Pods aufzunehmen, `False` wenn der Node nicht in einem guten Zustand ist und nicht bereit ist Pods aufzunehmeb, und `Unknown` wenn der Node-Controller seit der letzten `node-monitor-grace-period` nichts von dem Node gehört hat (Die Standardeinstellung beträgt 40 Sekunden) |
-| `MemoryPressure`    | `True` wenn der verfügbare Speicher des Nodes niedrig ist; Andernfalls`False` |
-| `PIDPressure`    | `True` wenn zu viele Prozesse auf dem Node vorhanden sind; Andernfalls`False` |
-| `DiskPressure`    | `True` wenn die Festplattenkapazität niedrig ist. Andernfalls `False` |
-| `NetworkUnavailable`    | `True` wenn das Netzwerk für den Node nicht korrekt konfiguriert ist, andernfalls `False` |
-
-Der Zustand eines Nodes wird als JSON-Objekt dargestellt. Die folgende Antwort beschreibt beispielsweise einen fehlerfreien Node.
-
-```json
-"conditions": [
-  {
-    "type": "Ready",
-    "status": "True"
-  }
-]
-```
-
-Wenn der Status der `Ready`-Bedingung `Unknown` oder `False` länger als der `pod-eviction-timeout` bleibt, wird ein Parameter an den [kube-controller-manager](/docs/admin/kube-controller-manager/) übergeben und alle Pods auf dem Node werden vom Node Controller gelöscht.
-
-Die voreingestellte Zeit vor der Entfernung beträgt **fünf Minuten**. 
-In einigen Fällen, in denen der Node nicht erreichbar ist, kann der Apiserver nicht mit dem Kubelet auf dem Node kommunizieren. 
-Die Entscheidung, die Pods zu löschen, kann dem Kublet erst mitgeteilt werden, wenn die Kommunikation mit dem Apiserver wiederhergestellt ist.
-In der Zwischenzeit können Pods, deren Löschen geplant ist, weiterhin auf dem unzugänglichen Node laufen.
-
-
-In Versionen von Kubernetes vor 1.5 würde der Node Controller das Löschen dieser unerreichbaren Pods vom Apiserver [erzwingen](/docs/concepts/workloads/pods/pod/#force-deletion-of-pods). In Version 1.5 und höher erzwingt der Node Controller jedoch keine Pod Löschung, bis bestätigt wird, dass sie nicht mehr im Cluster ausgeführt werden. Pods die auf einem unzugänglichen Node laufen sind eventuell in einem einem `Terminating` oder `Unkown` Status. In Fällen, in denen Kubernetes nicht aus der zugrunde liegenden Infrastruktur schließen kann, ob ein Node einen Cluster dauerhaft verlassen hat, muss der Clusteradministrator den Node möglicherweise manuell löschen.  
-Das Löschen des Kubernetes-Nodeobjekts bewirkt, dass alle auf dem Node ausgeführten Pod-Objekte gelöscht und deren Namen freigegeben werden.
-
-In Version 1.12 wurde die Funktion `TaintNodesByCondition` als Beta-Version eingeführt, die es dem Node-Lebenszyklus-Controller ermöglicht, automatisch [Markierungen](/docs/concepts/configuration/taint-and-toleration/) (*taints* in Englisch) zu erstellen, die Bedingungen darstellen.
-
-Ebenso ignoriert der Scheduler die Bedingungen, wenn er einen Node berücksichtigt; stattdessen betrachtet er die Markierungen (taints) des Nodes und die Toleranzen eines Pod.
-
-Anwender können jetzt zwischen dem alten Scheduling-Modell und einem neuen, flexibleren Scheduling-Modell wählen.
-
-Ein Pod, der keine Toleranzen aufweist, wird gemäß dem alten Modell geplant. 
-Aber ein Pod, die die Taints eines bestimmten Node toleriert, kann auf diesem Node geplant werden.
-
-{{< caution >}}
-Wenn Sie diese Funktion aktivieren, entsteht eine kleine Verzögerung zwischen der Zeit, 
-in der eine Bedingung beobachtet wird, und der Zeit, in der ein Taint entsteht. 
-Diese Verzögerung ist in der Regel kürzer als eine Sekunde, aber sie kann die Anzahl 
-der Pods erhöhen, die erfolgreich geplant, aber vom Kubelet abgelehnt werden.
-{{< /caution >}}
-
-### Kapazität
-
-Beschreibt die auf dem Node verfügbaren Ressourcen: CPU, Speicher und die maximale
-Anzahl der Pods, die auf dem Node ausgeführt werden können.
-
-### Info
-
-Allgemeine Informationen zum Node, z. B. Kernelversion, Kubernetes-Version
-(kubelet- und kube-Proxy-Version), Docker-Version (falls verwendet), Betriebssystemname.
-Die Informationen werden von Kubelet vom Node gesammelt.
-
-## Management
-
-Im Gegensatz zu [Pods](/docs/concepts/workloads/pods/pod/) und [Services](/docs/concepts/services-networking/service/),
-ein Node wird nicht von Kubernetes erstellt: Er wird extern von Cloud-Anbietern wie Google Compute Engine erstellt oder ist in Ihrem Pool physischer oder virtueller Maschinen vorhanden.
-Wenn Kubernetes also einen Node erstellt, wird ein Objekt erstellt, das den Node darstellt. 
-Nach der Erstellung überprüft Kubernetes, ob der Node gültig ist oder nicht.
-
-Wenn Sie beispielsweise versuchen, einen Node aus folgendem Inhalt zu erstellen:
-
-```json
-{
-  "kind": "Node",
-  "apiVersion": "v1",
-  "metadata": {
-    "name": "10.240.79.157",
-    "labels": {
-      "name": "my-first-k8s-node"
-    }
-  }
-}
-```
-
-
-Kubernetes erstellt intern ein Node-Oject (die Darstellung) und validiert den Node durch Zustandsprüfung basierend auf dem Feld `metadata.name`. 
-Wenn der Node gültig ist, d.h. wenn alle notwendigen Dienste ausgeführt werden, ist er berechtigt, einen Pod auszuführen.
-Andernfalls wird er für alle Clusteraktivitäten ignoriert, bis er gültig wird.
-
-
-{{< note >}}
-Kubernetes behält das Objekt für den ungültigen Node und prüft ständig seine Gültigkeit.
-Sie müssen das Node-Objekt explizit löschen, um diesen Prozess zu stoppen.
-{{< /note >}}
-
-Aktuell gibt es drei Komponenten, die mit dem Kubernetes Node-Interface interagieren: Node Controller, Kubelet und Kubectl.
-
-
-### Node Controller
-
-Der Node Controller ist eine Kubernetes-Master-Komponente, die verschiedene Aspekte von Nodes verwaltet.
-
-Der Node Controller hat mehrere Rollen im Leben eines Nodes. 
-Der erste ist die Zuordnung eines CIDR-Blocks zu dem Node, wenn er registriert ist (sofern die CIDR-Zuweisung aktiviert ist).
-
-Die zweite ist, die interne Node-Liste des Node Controllers mit der Liste der verfügbaren Computer des Cloud-Anbieters auf dem neuesten Stand zu halten.
-Wenn ein Node in einer Cloud-Umgebung ausgeführt wird und sich in einem schlechten Zustand befindet, fragt der Node Controller den Cloud-Anbieter, ob die virtuelle Maschine für diesen Node noch verfügbar ist. Wenn nicht, löscht der Node Controller den Node aus seiner Node-Liste.
-
-Der dritte ist die Überwachung des Zustands der Nodes. Der Node Controller ist dafür verantwortlich,
-die NodeReady-Bedingung von NodeStatus auf ConditionUnknown zu aktualisieren, wenn ein wenn ein Node unerreichbar wird (der Node Controller empfängt aus irgendeinem Grund keine Herzschläge mehr, z.B. weil der Node heruntergefahren ist) und später alle Pods aus dem Node zu entfernen (und diese ordnungsgemäss zu beenden), wenn der Node weiterhin unzugänglich ist. (Die Standard-Timeouts sind 40s, um ConditionUnknown zu melden und 5 Minuten, um mit der Evakuierung der Pods zu beginnen). 
-Der Node Controller überprüft den Zustand jedes Nodes alle `--node-monitor-period` Sekunden.
-
-
-In Versionen von Kubernetes vor 1.13 ist NodeStatus der Herzschlag des Nodes.
-Ab Kubernetes 1.13 wird das Node-Lease-Feature als Alpha-Feature eingeführt (Feature-Gate `NodeLease`, [KEP-0009](https://github.com/kubernetes/community/blob/master/keps/sig-node/0009-node-heartbeat.md)).
-
-Wenn die Node Lease Funktion aktiviert ist, hat jeder Node ein zugeordnetes `Lease`-Objekt im `kube-node-lease`-Namespace, das vom Node regelmäßig erneuert wird. 
-Sowohl NodeStatus als auch Node Lease werden als Herzschläge vom Node aus behandelt. 
-Node Leases werden häufig erneuert, während NodeStatus nur dann vom Node zu Master gemeldet wird, wenn sich etwas ändert oder genügend Zeit vergangen ist (Standard ist 1 Minute, was länger ist als der Standard-Timeout von 40 Sekunden für unerreichbare Nodes). 
-Da Node Leases viel lastärmer sind als NodeStatus, macht diese Funktion den Node Herzschlag sowohl in Bezug auf Skalierbarkeit als auch auf die Leistung deutlich effizienter.
-
-In Kubernetes 1.4 haben wir die Logik der Node-Steuerung aktualisiert, um Fälle besser zu handhaben, in denen eine große Anzahl von Nodes Probleme hat, den Master zu erreichen (z.B. weil der Master Netzwerkprobleme hat). 
-Ab 1.4 betrachtet der Node-Controller den Zustand aller Nodes im Cluster, wenn er eine Entscheidung über die Enterfung eines Pods trifft.
-
-In den meisten Fällen begrenzt der Node-Controller die Entfernungsrate auf `--node-eviction-rate` (Standard 0,1) pro Sekunde, was bedeutet, dass er die Pods nicht von mehr als einem Node pro 10 Sekunden entfernt.
-
-Das Entfernungsverhalten von Nodes ändert sich, wenn ein Node in einer bestimmten Verfügbarkeitszone ungesund wird. 
-Der Node-Controller überprüft gleichzeitig, wie viel Prozent der Nodes in der Zone ungesund sind (NodeReady-Bedingung ist ConditionUnknown oder ConditionFalse). 
-Wenn der Anteil der ungesunden Nodes mindestens `--unhealthy-zone-threshold` (Standard 0,55) beträgt, wird die Entfernungsrate reduziert:
-
-Wenn der Cluster klein ist (d.h. weniger als oder gleich `--large-cluster-size-threshold` Node - Standard 50), werden die Entfernungen gestoppt. Andernfalls wird die Entfernungsrate auf `--secondary-node-eviction-rate` (Standard 0,01) pro Sekunde reduziert. 
-
-Der Grund, warum diese Richtlinien pro Verfügbarkeitszone implementiert werden, liegt darin, dass eine Verfügbarkeitszone vom Master unerreichbar werden könnte, während die anderen verbunden bleiben. Wenn Ihr Cluster nicht mehrere Verfügbarkeitszonen von Cloud-Anbietern umfasst, gibt es nur eine Verfügbarkeitszone (den gesamten Cluster).
-
-Ein wichtiger Grund für die Verteilung Ihrer Nodes auf Verfügbarkeitszonen ist, dass die Arbeitsbelastung auf gesunde Zonen verlagert werden kann, wenn eine ganze Zone ausfällt.
-Wenn also alle Nodes in einer Zone ungesund sind, entfernt Node Controller mit der normalen `--node-eviction-rate` Geschwindigkeit.  
-Der Ausnahmefall ist, wenn alle Zonen völlig ungesund sind (d.h. es gibt keine gesunden Node im Cluster). 
-In diesem Fall geht der Node-Controller davon aus, dass es ein Problem mit der Master-Konnektivität gibt und stoppt alle Entfernungen, bis die Verbindung wiederhergestellt ist.
-
-Ab Kubernetes 1.6 ist der Node-Controller auch für die Entfernung von Pods zuständig, die auf Nodes mit `NoExecute`-Taints laufen, wenn die Pods die Markierungen nicht tolerieren. 
-Zusätzlich ist der NodeController als Alpha-Funktion, die standardmäßig deaktiviert ist, dafür verantwortlich, Taints hinzuzufügen, die Node Probleme, wie `Node unreachable` oder `not ready` entsprechen. 
-Siehe [diese Dokumentation](/docs/concepts/configuration/taint-and-toleration/) für Details über `NoExecute` Taints und die Alpha-Funktion.
-
-
-Ab Version 1.8 kann der Node-Controller für die Erzeugung von Taints, die Node Bedingungen darstellen, verantwortlich gemacht werden. Dies ist eine Alpha-Funktion der Version 1.8.
-
-### Selbstregistrierung von Nodes
-
-Wenn das Kubelet-Flag `--register-node` aktiv ist (Standard), versucht das Kubelet, sich beim API-Server zu registrieren.  Dies ist das bevorzugte Muster, das von den meisten Distributionen verwendet wird.
-
-Zur Selbstregistrierung wird das kubelet mit den folgenden Optionen gestartet:
-
-  - `--kubeconfig` - Pfad zu Anmeldeinformationen, um sich beim Apiserver zu authentifizieren.
-  - `--cloud-provider` - Wie man sich mit einem Cloud-Anbieter unterhält, um Metadaten über sich selbst zu lesen.
-  - `--register-node` - Automatisch beim API-Server registrieren.
-  - `--register-with-taints` - Registrieren Sie den Node mit der angegebenen Taints-Liste (Kommagetrennt `<key>=<value>:<effect>`). No-op wenn `register-node` false ist.
-  - `--node-ip` - IP-Adresse des Nodes.
-  - `--node-labels` - Labels, die bei der Registrierung des Nodes im Cluster hinzugefügt werden sollen (Beachten Sie die Richlinien des [NodeRestriction admission plugin](/docs/reference/access-authn-authz/admission-controllers/#noderestriction) in 1.13+).
-  - `--node-status-update-frequency` - Gibt an, wie oft kubelet den Nodestatus an den Master übermittelt.
-
-Wenn der [Node authorization mode](/docs/reference/access-authn-authz/node/) und 
-[NodeRestriction admission plugin](/docs/reference/access-authn-authz/admission-controllers/#noderestriction) aktiviert sind,
-dürfen kubelets nur ihre eigene Node-Ressource erstellen / ändern.
-
-#### Manuelle Nodeverwaltung
-
-Ein Cluster-Administrator kann Nodeobjekte erstellen und ändern.
-
-Wenn der Administrator Nodeobjekte manuell erstellen möchte, setzen Sie das kubelet Flag `--register-node=false`.
-
-Der Administrator kann Node-Ressourcen ändern (unabhängig von der Einstellung von `--register-node`).
-Zu den Änderungen gehören das Setzen von Labels und das Markieren des Nodes.
-
-Labels auf Nodes können in Verbindung mit node selectors auf Pods verwendet werden, um die Planung zu steuern, z.B. um einen Pod so zu beschränken, dass er nur auf einer Teilmenge der Nodes ausgeführt werden darf.
-
-Das Markieren eines Nodes als nicht geplant, verhindert, dass neue Pods für diesen Node geplant werden. Dies hat jedoch keine Auswirkungen auf vorhandene Pods auf dem Node.
-Dies ist nützlich als vorbereitender Schritt vor einem Neustart eines Nodes usw. 
-Um beispielsweise einen Node als nicht geplant zu markieren, führen Sie den folgenden Befehl aus:
-
-```shell
-kubectl cordon $NODENAME
-```
-
-{{< note >}}
-Pods, die von einem DaemonSet-Controller erstellt wurden, umgehen den Kubernetes-Scheduler und respektieren nicht das _unschedulable_ Attribut auf einem Node. 
-Dies setzt voraus, dass Daemons auf dem Computer verbleiben, auch wenn während der Vorbereitung eines Neustarts keine Anwendungen mehr vorhanden sind.
-{{< /note >}}
-
-### Node Kapazität
-
-Die Kapazität des Nodes (Anzahl der CPU und Speichermenge) ist Teil des Nodeobjekts.
-Normalerweise registrieren sich Nodes selbst und melden ihre Kapazität beim Erstellen des Nodeobjekts.
-Sofern Sie [Manuelle Nodeverwaltung](#Manuelle-Nodeverwaltung) betreiben, müssen Sie die Node Kapazität setzen, wenn Sie einen Node hinzufügen.
-
-Der Kubernetes-Scheduler stellt sicher, dass für alle Pods auf einem Nodes genügend Ressourcen vorhanden sind.
-Er prüft, dass die Summe der Requests von Containern auf dem Node nicht größer ist als die Kapazität des Nodes.
-Er beinhaltet alle Container die vom kubelet gestarted worden, aber keine Container die direkt von der [container runtime](/docs/concepts/overview/components/#node-components) gestartet wurden, noch jegleiche Prozesse die ausserhalb von Containern laufen. 
-
-Wenn Sie Ressourcen explizit für Nicht-Pod-Prozesse reservieren möchten, folgen Sie diesem Lernprogramm um [Ressourcen für Systemdaemons zu reservieren](/docs/tasks/administer-cluster/reserve-compute-resources/#system-reserved).
-
-
-## API-Objekt
-
-Node ist eine Top-Level-Ressource in der Kubernetes-REST-API. Weitere Details zum API-Objekt finden Sie unter:
-[Node API object](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#node-v1-core).
-
-{{% /capture %}}
@@ -1,5 +0,0 @@
---
-title: "Cluster Administration"
-weight: 100
---
-
@@ -1,5 +0,0 @@
---
-title: "Konfiguration"
-weight: 80
---
-
@@ -1,5 +0,0 @@
---
-title: "Container"
-weight: 40
---
-
@@ -1,38 +0,0 @@
---
-title: Konzept Dokumentations-Vorlage
-content_template: templates/concept
-toc_hide: true
---
-
-{{% capture overview %}}
-
-{{< note >}}
-Stellen Sie auch sicher [einen Eintrag im Inhaltsverzeichnis](/docs/home/contribute/write-new-topic/#creating-an-entry-in-the-table-of-contents) für Ihr neues Dokument zu erstellen.
-{{< /note >}}
-
-Diese Seite erklärt ...
-
-{{% /capture %}}
-
-{{% capture body %}}
-
-## Verstehen ...
-
-Kubernetes bietet ...
-
-## Verwenden ...
-
-Benutzen Sie ...
-
-{{% /capture %}}
-
-{{% capture whatsnext %}}
-
-**[Optionaler Bereich]**
-
-* Lernen Sie mehr über [ein neues Thema schreiben](/docs/home/contribute/write-new-topic/).
-* Besuchen Sie [Seitenvorlagen verwenden - Konzeptvorlage](/docs/home/contribute/page-templates/#concept_template) wie Sie diese Vorlage verwenden.
-
-{{% /capture %}}
-
-
@@ -1,4 +0,0 @@
---
-title: "Kubernets erweitern"
-weight: 110
---
@@ -1,5 +0,0 @@
---
-title: "Überblick"
-weight: 20
---
-
@@ -1,112 +0,0 @@
---
-title: Kubernetes Komponenten
-content_template: templates/concept
-weight: 20
-card: 
-  name: concepts
-  weight: 20
---
-
-{{% capture overview %}}
-In diesem Dokument werden die verschiedenen binären Komponenten beschrieben, die zur Bereitstellung eines funktionsfähigen Kubernetes-Clusters erforderlich sind.
-{{% /capture %}}
-
-{{% capture body %}}
-## Master-Komponenten
-
-Master-Komponenten stellen die Steuerungsebene des Clusters bereit. Master-Komponenten treffen globale Entscheidungen über den Cluster (z. B. Zeitplanung) und das Erkennen und Reagieren auf Clusterereignisse (Starten eines neuen Pods, wenn das `replicas`-Feld eines Replikationscontrollers nicht zufriedenstellend ist).
-
-Master-Komponenten können auf jedem Computer im Cluster ausgeführt werden.
-Der Einfachheit halber starten Setup-Skripts normalerweise alle Master-Komponenten auf demselben Computer, und es werden keine Benutzercontainer auf diesem Computer ausgeführt.
-Lesen Sie [Cluster mit hoher Verfügbarkeit erstellen](/docs/admin/high-availability/) für ein Beispiel für ein Multi-Master-VM-Setup.
-
-### kube-apiserver
-
-{{< glossary_definition term_id="kube-apiserver" length="all" >}}
-
-### etcd
-
-{{< glossary_definition term_id="etcd" length="all" >}}
-
-### kube-scheduler
-
-{{< glossary_definition term_id="kube-scheduler" length="all" >}}
-
-### kube-controller-manager
-
-{{< glossary_definition term_id="kube-controller-manager" length="all" >}}
-
-Diese Controller umfassen:
-
-  * Node Controller: Verantwortlich für das Erkennen und Reagieren, wenn Nodes ausfallen.
-  * Replication Controller: Verantwortlich für die Aufrechterhaltung der korrekten Anzahl von Pods für jedes Replikationscontrollerobjekt im System.
-  * Endpoints Controller: Füllt das Endpoints-Objekt aus (d.h. verbindet Services & Pods).
-  * Service Account & Token Controllers: Erstellt Standardkonten und API-Zugriffstoken für neue Namespaces.
-
-### cloud-controller-manager
-
-[cloud-controller-manager](/docs/tasks/administer-cluster/running-cloud-controller/) führt Controller aus, die mit den entsprechenden Cloud-Anbietern interagieren.
-Der cloud-controller-manager ist eine Alpha-Funktion, die in Kubernetes Version 1.6 eingeführt wurde.
-
-cloud-controller-manager führt nur Cloud-Provider-spezifische Controller-Schleifen aus. Sie müssen diese Controller-Schleifen im Cube-Controller-Manager deaktivieren. Sie können die Controller-Schleifen deaktivieren, indem Sie beim Starten des kube-controller-manager das Flag `--cloud-provider` auf `external` setzen.
-
-cloud-controller-manager erlaubt es dem Cloud-Anbieter Code und dem Kubernetes-Code, sich unabhängig voneinander zu entwickeln. 
-In früheren Versionen war der Kerncode von Kubernetes für die Funktionalität von Cloud-Provider-spezifischem Code abhängig.
-In zukünftigen Versionen sollte der für Cloud-Anbieter spezifische Code vom Cloud-Anbieter selbst verwaltet und mit dem Cloud-Controller-Manager verknüpft werden, während Kubernetes ausgeführt wird.
-
-Die folgenden Controller haben Abhängigkeiten von Cloud-Anbietern:
-
-  * Node Controller: Zum Überprüfen, ob ein Node in der Cloud beim Cloud-Anbieter gelöscht wurde, nachdem er nicht mehr reagiert
-  * Route Controller: Zum Einrichten von Routen in der zugrunde liegenden Cloud-Infrastruktur
-  * Service Controller: Zum Erstellen, Aktualisieren und Löschen von Lastverteilern von Cloud-Anbietern
-  * Volume Controller: Zum Erstellen, Verbinden und Bereitstellen von Volumes und zur Interaktion mit dem Cloud-Provider zum Orchestrieren von Volumes
-
-## Node-Komponenten
-
-Node Komponenten werden auf jedem Knoten ausgeführt, halten laufende Pods aufrecht und stellen die Kubernetes-Laufzeitumgebung bereit.
-
-### kubelet
-
-{{< glossary_definition term_id="kubelet" length="all" >}}
-
-### kube-proxy
-
-[kube-proxy](/docs/admin/kube-proxy/) ermöglicht die Kubernetes Service-Abstraktion, indem die Netzwerkregeln auf dem Host beibehalten und die Verbindungsweiterleitung durchgeführt wird.
-
-### Container Runtime
-
-Die Containerlaufzeit ist die Software, die für das Ausführen von Containern verantwortlich ist.
-Kubernetes unterstützt mehrere Laufzeiten: [Docker](http://www.docker.com), [containerd](https://containerd.io), [cri-o](https://cri-o.io/), [rktlet](https://github.com/kubernetes-incubator/rktlet) und jede Implementierung des [Kubernetes CRI (Container Runtime Interface)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md).
-
-## Addons
-
-Addons sind Pods und Dienste, die Clusterfunktionen implementieren. Die Pods können verwaltet werden
-durch Deployments, ReplicationControllers, und so wieter. 
-Namespace-Addon-Objekte werden im Namespace `kube-system` erstellt.
-
-Ausgewählte Addons werden unten beschrieben. Eine erweiterte Liste verfügbarer Addons finden Sie unter [Addons](/docs/concepts/cluster-administration/addons/).
-
-### DNS
-
-Während die anderen Addons nicht unbedingt erforderlich sind, sollte [cluster DNS](/docs/concepts/services-networking/dns-pod-service/) in allen Kubernetes-Cluster vorhanden sein, da viele Beispiele davon abhängen.
-
-Cluster-DNS ist neben anderen DNS-Servern in Ihrer Umgebung ein DNS-Server, der DNS-Einträge für Kubernetes-Dienste bereitstellt.
-
-Von Kubernetes gestartete Container schließen diesen DNS-Server automatisch in ihre DNS-Suchen ein.
-
-### Web UI (Dashboard)
-
-[Dashboard](/docs/tasks/access-application-cluster/web-ui-dashboard/) ist eine allgemeine, webbasierte Benutzeroberfläche für Kubernetes-Cluster. Benutzer können damit Anwendungen, die im Cluster ausgeführt werden, sowie den Cluster selbst verwalten und Fehler beheben.
-
-### Container Resource Monitoring
-
-[Container Resource Monitoring](/docs/tasks/debug-application-cluster/resource-usage-monitoring/) zeichnet generische Zeitreihenmessdaten zu Containern in einer zentralen Datenbank auf und stellt eine Benutzeroberfläche zum Durchsuchen dieser Daten bereit.
-
-
-### Cluster-level Logging
-
-Ein [Cluster-level logging](/docs/concepts/cluster-administration/logging/) Mechanismus ist für das Speichern von Containerprotokollen in einem zentralen Protokollspeicher mit Such- / Browsing-Schnittstelle verantwortlich.
-
-{{% /capture %}}
-
-
@@ -1,170 +0,0 @@
---
-title: Was ist Kubernetes?
-content_template: templates/concept
-weight: 10
-card: 
-  name: concepts
-  weight: 10
---
-
-{{% capture overview %}}
-Diese Seite ist eine Übersicht über Kubernetes.
-{{% /capture %}}
-
-{{% capture body %}}
-
-Kubernetes ist eine portable, erweiterbare Open-Source-Plattform zur Verwaltung von
-containerisierten Arbeitslasten und Services, die sowohl die deklarative Konfiguration als auch die Automatisierung erleichtert. 
-Es hat einen großes, schnell wachsendes Ökosystem. Kubernetes Dienstleistungen, Support und Tools sind weit verbreitet.
-
-Google hat das Kubernetes-Projekt 2014 als Open-Source-Projekt zur Verfügung gestellt. Kubernetes baut auf anderthalb Jahrzehnten 
-Erfahrung auf, die Google mit der Ausführung von Produktions-Workloads in großem Maßstab hat, kombiniert mit den besten Ideen und Praktiken der Community.
-
-## Warum brauche ich Kubernetes und was kann ich damit tun?
-
-Kubernetes hat eine Reihe von Funktionen. Es kann gesehen werden als:
-
- eine Containerplattform
- eine Microservices-Plattform
- eine portable Cloud-Plattform
-und vieles mehr.
-
-Kubernetes bietet eine **containerzentrierte** Managementumgebung. Es koordiniert die Computer-, Netzwerk- und Speicherinfrastruktur 
-im Namen der Benutzer-Workloads. Dies bietet einen Großteil der Einfachheit von Platform as a Service (PaaS) mit der Flexibilität 
-von Infrastructure as a Service (IaaS) und ermöglicht die Portabilität zwischen Infrastrukturanbietern.
-
-## Wie ist Kubernetes eine Plattform?
-
-Auch wenn Kubernetes eine Menge Funktionalität bietet, gibt es immer wieder neue Szenarien, 
-die von neuen Funktionen profitieren würden. Anwendungsspezifische Workflows können optimiert werden, 
-um die Entwicklungsgeschwindigkeit zu beschleunigen. 
-Eine zunächst akzeptable Ad-hoc-Orchestrierung erfordert oft eine robuste Automatisierung in großem Maßstab. 
-Aus diesem Grund wurde Kubernetes auch als Plattform für den Aufbau eines Ökosystems von Komponenten und Tools 
-konzipiert, um die Bereitstellung, Skalierung und Verwaltung von Anwendungen zu erleichtern.
-
-[Labels](/docs/concepts/overview/working-with-objects/labels/) ermöglichen es den Benutzern, ihre Ressourcen 
-nach Belieben zu organisieren. [Anmerkungen](/docs/concepts/overview/working-with-objects/annotations/) ermöglichen es Benutzern,
-Ressourcen mit benutzerdefinierten Informationen zu versehen, um ihre Arbeitsabläufe zu vereinfachen und eine einfache Möglichkeit
-für Managementtools zu bieten, den Status von Kontrollpunkten zu ermitteln.
-
-
-Darüber hinaus basiert die [Kubernetes-Steuerungsebene](/docs/concepts/overview/components/) auf den gleichen APIs,
-die Entwicklern und Anwendern zur Verfügung stehen. Benutzer können ihre eigenen Controller, wie z.B. 
-[Scheduler](https://github.com/kubernetes/community/blob/{{< param "githubbranch" >}}/contributors/devel/scheduler.md), mit 
-ihren [eigenen APIs](](/docs/concepts/api-extension/custom-resources/) schreiben, die von einem 
-universellen [Kommandozeilen-Tool](/docs/user-guide/kubectl-overview/) angesprochen werden können.
-
-Dieses [Design](https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md) hat es einer Reihe anderer Systeme ermöglicht, auf Kubernetes aufzubauen.
-
-## Was Kubernetes nicht ist
-
-Kubernetes ist kein traditionelles, allumfassendes PaaS (Plattform als ein Service) System. Da Kubernetes nicht auf Hardware-, 
-sondern auf Containerebene arbeitet, bietet es einige allgemein anwendbare Funktionen, die PaaS-Angeboten gemeinsam sind, 
-wie Bereitstellung, Skalierung, Lastausgleich, Protokollierung und Überwachung. 
-Kubernetes ist jedoch nicht monolithisch, und diese Standardlösungen sind optional und modular etweiterbar. 
-Kubernetes liefert die Bausteine für den Aufbau von Entwicklerplattformen, bewahrt aber die 
-Wahlmöglichkeiten und Flexibilität der Benutzer, wo es wichtig ist.
-
-Kubernetes:
-
-* Schränkt nicht die Art der unterstützten Anwendungen ein. Kubernetes zielt darauf ab, 
-  eine extrem große Vielfalt von Workloads zu unterstützen, einschließlich stateless, 
-  stateful und datenverarbeitender Workloads. Wenn eine Anwendung in einem Container ausgeführt 
-  werden kann, sollte sie auf Kubernetes hervorragend laufen.
-* Verteilt keinen Quellcode und entwickelt Ihre Anwendung nicht. 
-  Kontinuierliche Integrations-, Liefer- und Bereitstellungs-Workflows (CI/CD) werden durch 
-  Unternehmenskulturen und -präferenzen sowie technische Anforderungen bestimmt.
-* Bietet keine Dienste auf Anwendungsebene, wie Middleware (z.B. Nachrichtenbusse), 
-  Datenverarbeitungs-Frameworks (z.B. Spark), Datenbanken (z.B. mysql), Caches oder 
-  Cluster-Speichersysteme (z.B. Ceph) als eingebaute Dienste. Solche Komponenten können 
-  auf Kubernetes laufen und/oder von Anwendungen, die auf Kubernetes laufen, über 
-  portable Mechanismen wie den Open Service Broker angesprochen werden.
-* Bietet keine Konfigurationssprache bzw. kein Konfigurationssystem (z.B.[jsonnet](https://github.com/google/jsonnet)). 
-  Es bietet eine deklarative API, die von beliebigen Formen deklarativer Spezifikationen angesprochen werden kann.
-* Bietet keine umfassenden Systeme zur Maschinenkonfiguration, Wartung, Verwaltung oder Selbstheilung.
-
-Außerdem ist Kubernetes nicht nur ein *Orchestrierungssystem*. Fakt ist, dass es die Notwendigkeit einer Orchestrierung 
-überflüssig macht. Die technische Definition von *Orchestrierung* ist die Ausführung eines
-definierten Workflows: zuerst A, dann B, dann C. Im Gegensatz dazu besteht Kubernetes aus einer Reihe von unabhängigen,
-komponierbaren Steuerungsprozessen, die den aktuellen Zustand kontinuierlich in Richtung des bereitgestellten Soll-Zustandes vorantreiben. 
-Es sollte keine Rolle spielen, wie Sie von A nach C kommen. Eine zentrale Steuerung ist ebenfalls nicht erforderlich. 
-Das Ergebnis ist ein System, das einfacher zu bedienen und leistungsfähiger, robuster, widerstandsfähiger und erweiterbar ist.
-
-## Warum Container?
-
-Sie suchen nach Gründen, warum Sie Container verwenden sollten?
-
-![Why Containers?](/images/docs/why_containers.svg)
-
-Der *Altbekannte* Weg zur Bereitstellung von Anwendungen war die Installation 
-der Anwendungen auf einem Host mit dem Betriebssystempaketmanager.
-Dies hatte den Nachteil, dass die ausführbaren Dateien, Konfigurationen, 
-Bibliotheken und Lebenszyklen der Anwendungen untereinander und mit dem 
-Host-Betriebssystem verwoben waren. Man könnte unveränderliche 
-Virtual-Machine-Images erzeugen, um vorhersehbare Rollouts 
-und Rollbacks zu erreichen, aber VMs sind schwergewichtig und nicht portierbar.
-
-Der *Neue Weg* besteht darin, Container auf Betriebssystemebene und nicht auf 
-Hardware-Virtualisierung bereitzustellen. Diese Container sind voneinander 
-und vom Host isoliert: Sie haben ihre eigenen Dateisysteme, sie können die 
-Prozesse des anderen nicht sehen, und ihr Ressourcenverbrauch kann begrenzt 
-werden. Sie sind einfacher zu erstellen als VMs, und da sie von der zugrunde 
-liegenden Infrastruktur und dem Host-Dateisystem entkoppelt sind, 
-sind sie über Clouds und Betriebssystem-Distributionen hinweg portabel.
-
-Da Container klein und schnell sind, kann in jedes Containerimage eine Anwendung gepackt werden. 
-Diese 1:1-Beziehung zwischen Anwendung und Image ermöglicht es, die Vorteile von Containern 
-voll auszuschöpfen. Mit Containern können unveränderliche Container-Images eher zur Build-/Release-Zeit 
-als zur Deployment-Zeit erstellt werden, da jede Anwendung nicht mit dem Rest des Anwendungsstacks komponiert 
-werden muss und auch nicht mit der Produktionsinfrastrukturumgebung verbunden ist. Die Generierung von 
-Container-Images zum Zeitpunkt der Erstellung bzw. Freigabe ermöglicht es, eine konsistente Umgebung 
-von der Entwicklung bis zur Produktion zu gewährleisten.  
-Ebenso sind Container wesentlich transparenter als VMs, was die Überwachung und Verwaltung erleichtert. 
-Dies gilt insbesondere dann, wenn die Prozesslebenszyklen der Container von der Infrastruktur verwaltet 
-werden und nicht von einem Prozess-Supervisor im Container versteckt werden.
-Schließlich, mit einer einzigen Anwendung pro Container, wird die Verwaltung 
-der Container gleichbedeutend mit dem Management des Deployments der Anwendung.
-
-Zusammenfassung der Container-Vorteile:
-
-* **Agile Anwendungserstellung und -bereitstellung**:
-    Einfachere und effizientere Erstellung von Container-Images im Vergleich zur Verwendung von VM-Images.
-* **Kontinuierliche Entwicklung, Integration und Bereitstellung**:
-    Bietet eine zuverlässige und häufige Erstellung und Bereitstellung von Container-Images 
-    mit schnellen und einfachen Rollbacks (aufgrund der Unveränderlichkeit des Images).
-* **Dev und Ops Trennung der Bedenken**:
-    Erstellen Sie Anwendungscontainer-Images nicht zum Deployment-, sondern zum Build-Releasezeitpunkt 
-    und entkoppeln Sie so Anwendungen von der Infrastruktur.
-* **Überwachbarkeit**
-    Nicht nur Informationen und Metriken auf Betriebssystemebene werden angezeigt, 
-    sondern auch der Zustand der Anwendung und andere Signale.
-* **Umgebungskontinuität in Entwicklung, Test und Produktion**:
-    Läuft auf einem Laptop genauso wie in der Cloud.
-* **Cloud- und OS-Distribution portabilität**:
-    Läuft auf Ubuntu, RHEL, CoreOS, On-Prem, Google Kubernetes Engine und überall sonst.
-* **Anwendungsorientiertes Management**:
-    Erhöht den Abstraktionsgrad vom Ausführen eines Betriebssystems auf virtueller Hardware 
-    bis zum Ausführen einer Anwendung auf einem Betriebssystem unter Verwendung logischer Ressourcen.
-* **Locker gekoppelte, verteilte, elastische, freie [micro-services](https://martinfowler.com/articles/microservices.html)**:
-    Anwendungen werden in kleinere, unabhängige Teile zerlegt und können dynamisch bereitgestellt 
-    und verwaltet werden -- nicht ein monolithischer Stack, der auf einer großen Single-Purpose-Maschine läuft.
-* **Ressourcenisolierung**:
-    Vorhersehbare Anwendungsleistung.
-* **Ressourcennutzung**:
-    Hohe Effizienz und Dichte.
-
-## Was bedeutet Kubernetes? K8s?
-
-Der Name **Kubernetes** stammt aus dem Griechischen, beteutet *Steuermann* oder
-*Pilot*, und ist der Ursprung von *Gouverneur* und
-[cybernetic](http://www.etymonline.com/index.php?term=cybernetics). *K8s*
-ist eine Abkürzung, die durch Ersetzen der 8 Buchstaben "ubernete" mit "8" abgeleitet wird.
-
-{{% /capture %}}
-
-{{% capture whatsnext %}}
-*   [Bereit loszulegen](/docs/setup/)?
-*   Weitere Einzelheiten finden Sie in der [Kubernetes Dokumentation](/docs/home/).
-{{% /capture %}}
-
-
@@ -1,5 +0,0 @@
---
-title: "Richtlinien"
-weight: 90
---
-
@@ -1,5 +0,0 @@
---
-title: "Dienste, Lastverteilung und Netzwerkfunktionen"
-weight: 60
---
-
@@ -1,5 +0,0 @@
---
-title: "Speicher"
-weight: 70
---
-
@@ -1,5 +0,0 @@
---
-title: "Workloads"
-weight: 50
---
-
@@ -1,62 +0,0 @@
---
-content_template: templates/concept
-title: Zur Kubernets-Dokumentation beitragen
-linktitle: Mitmachen
-main_menu: true
-weight: 80
---
-
-{{% capture overview %}}
-
-Wenn Sie an der Dokumentation oder der Website von Kubernetes mitwirken möchten, freuen wir uns über Ihre Hilfe! 
-Jeder kann seinen Beitrag leisten, unabhängig davon ob Sie neu im Projekt sind oder schon lange dabei sind, und ob Sie sich als
-Entwickler, Endbenutzer oder einfach jemanden, der es einfach nicht aushält, Tippfehler zu sehen sehen.
-
-Weitere Möglichkeiten, sich in der Kubernetes-Community zu engagieren oder mehr über uns zu erfahren, finden Sie auf der [Kubernetes-Community-Seite](/community/). 
-Informationen zum Handbuch zur Dokumentation von Kubernetes finden Sie im [Gestaltungshandbuch](/docs/contribute/style/style-guide/).
-
-{{% capture body %}}
-
-## Arten von Mitwirkenden
-
- Ein _Member_ der Kubernetes Organisation, hat die [CLA unterzeichnet](/docs/contribute/start#sign-the-cla)
-  und etwas Zeit und Energie zum Projekt beigetragen. 
-  Siehe [Community-Mitgliedschaft](https://github.com/kubernetes/community/blob/master/community-membership.md) für spezifische Kriterien bezüglich der Mitgliedschaft. 
- Ein SIG Docs _Reviewer_ ist ein Mitglied der Kubernetes-Organisation, das Interesse an der Überprüfung von 
-  Dokumentationsanfragen geäußert hat und von einem SIG Docs Approver zu der entsprechenden Github-Gruppe 
-  und den `OWNERS`-Dateien im Github-Repository hinzugefügt wurde.
- Ein SIG Docs _approver_ ist ein Mitglied mit gutem Ansehen, das sich kontinuierlich für das Projekt engagiert hat. 
-  Ein Approver kann Pull-Anfragen zusammenführen und Inhalte im Namen der Kubernetes-Organisation veröffentlichen.
-  Approver können SIG Docs auch in der größeren Kubernetes-Community vertreten. Einige der Aufgaben eines SIG Docs Approvers, wie z.B. die Koordination einer Freigabe, erfordern einen erheblichen Zeitaufwand.
-
-## Möglichkeiten, einen Beitrag zu leisten
-
-Diese Liste ist in Funktionen unterteilt, die jeder tun kann, die von Mitgliedern der Kubernetes-Organisation durchgeführt werden können, und Dinge, die ein höheres Maß an Zugriff und eine bessere Kenntnis der SIG Docs-Prozesse erfordern. Wenn Sie im Laufe der Zeit einen konstanten Beitrag leisten, können Sie einige der bereits getroffenen Tools und organisatorischen Entscheidungen nachvollziehen.
-
-Dies ist keine vollständige Liste von Möglichkeiten, wie Sie zur Kubernetes-Dokumentation beitragen können, aber sie sollte Ihnen den Einstieg erleichtern.
-
- [Jeder](/docs/contribute/start/)
-  - Umsetzbare issues eröffnen
- [Member](/docs/contribute/start/)
-  - Vorhandene Dokumente verbessern
-  - Ideen zur Verbesserung in [Slack](http://slack.k8s.io/) oder der [SIG docs Mailingliste](https://groups.google.com/forum/#!forum/kubernetes-sig-docs) einbringen
-  - Den Zugriff auf Dokumente verbessern
-  - Unverbindliches Feedback zu PRs verfassen
-  - Enen Blogbeitrag oder eine Fallstudie schreiben
- [Reviewer](/docs/contribute/intermediate/)
-  - Neue Funktionen dokumentieren
-  - Auswerten und Kategorisieren von Problemen
-  - PRs überprüfen
-  - Diagramme, Grafiken und einbettbare Screencasts / Videos erstellen
-  - Lokalisierung
-  - Als Vertreter von docs zu anderen Repos beitragen
-  - An Benutzer gerichtete Zeichenfolgen im Code bearbeiten
-  - Code-Kommentare verbessern, Godoc
- [Approver](/docs/contribute/advanced/)
-  - Veröffentlichen Sie den Inhalt von Members, indem Sie PRs genehmigen und zusammenführen
-  - Nehmen Sie als Docs-Vertreter an einem Kubernetes-Release-Team teil
-  - Verbesserungsvorschläge für den Style Guide
-  - Verbesserungsvorschläge für Dokumentprüfungen vorschlagen
-  - Vorschläge für Verbesserungen der Kubernetes-Website oder anderer Tools
-
-{{% /capture %}}
@@ -1,56 +0,0 @@
---
-title: Kubernetes Dokumentation
-noedit: true
-cid: docsHome
-layout: docsportal_home
-class: gridPage
-linkTitle: "Home"
-main_menu: true
-weight: 10
-hide_feedback: true
-menu:
-  main:
-    title: "Dokumentation"
-    weight: 20
-    post: >
-      <p>Erfahren Sie, wie Sie Kubernetes mit Konzept-, Tutorial- und Referenzdokumentation verwenden. Sie können sogar zur <a href="/editdocs/" data-auto-burger-exclude>mithelfen und zur Dokumentation beitragen</a>!</p>
-overview: >
-  Kubernetes ist ein Open-Source-System zur Automatisierung der Bereitstellung, Skalierung und Verwaltung von containerisierten Anwendungen. Das Open-Source Project wird von der Cloud Native Computing Foundation (<a href="https://www.cncf.io/about">CNCF</a>) gehosted.
-cards:
- name: concepts
-  title: "Verstehen Sie die Grundlagen"
-  description: "Lernen Sie Kubernetes und seine grundlegenden Konzepte kennen."
-  button: "Konzepte lernen"
-  button_path: "/docs/concepts"
- name: tutorials
-  title: "Kubernetes ausprobieren"
-  description: "Folgen Sie den Tutorials, um zu erfahren, wie Sie Anwendungen in Kubernetes bereitstellen."
-  button: "Tutorials entdecken"
-  button_path: "/docs/tutorials"
- name: setup
-  title: "Richten Sie einen Cluster ein"
-  description: "Holen Sie sich Kubernetes basierend auf Ihren Ressourcen und Bedürfnissen."
-  button: "Kubernetes Einrichten"
-  button_path: "/docs/setup"
- name: tasks
-  title: "Erfahren Sie, wie Sie Kubernetes verwenden"
-  description: "Informieren Sie sich über häufig verwendete Aufgaben und deren Durchführung anhand einer kurzen Abfolge von Schritten."
-  button: "Tasks anzeigen"
-  button_path: "/docs/tasks"
- name: reference
-  title: Referenzinformationen nachschlagen
-  description: Durchsuchen Sie Terminologie, Befehlszeilensyntax, API-Ressourcentypen und Dokumentation zum Setup-Tool.
-  button: Referenz anzeigen
-  button_path: /docs/reference
- name: contribute
-  title: Tragen Sie zur Dokumentation bei
-  description: Jeder kann einen Beitrag leisten, unabhängig davon, ob Sie neu in dem Projekt oder schon lange dabei sind.
-  button: Zur Dokumentation beitragen
-  button_path: /docs/contribute
- name: download
-  title: Kubernetes Herunterladen
-  description: Wenn Sie Kubernetes installieren oder auf die neueste Version aktualisieren, lesen Sie die aktuellen Versionshinweise.
- name: about
-  title: Über die Dokumentation
-  description: Diese Website enthält Dokumentation zu den aktuellen und vorherigen 4 Versionen von Kubernetes.
---
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Mike Danese	571d2324db	Merge pull request #1321 from lukemarsden/official-packages Update kubeadm guide to use official stable deb and rpm repos	2016-09-27 08:07:30 -07:00
Luke Marsden	5524edba2a	Use the official 1.4.0 image.	2016-09-27 15:58:01 +01:00
Luke Marsden	cf14a29b53	Update kubeadm guide to use official stable deb and rpm repos. Thanks @mikedanese!	2016-09-27 15:51:32 +01:00
				`@@ -0,0 +1 @@`
				`{% for item in tree %}{% if item.section %}{% assign tree = item.section %}{% include tocsearch.html %}{% else %}{% if item.path == page.url %}{% assign foundTOC = thistoc %}{% assign title = item.title %}{% break %}{% endif %}{% endif %}{% endfor %}`