Merge branch 'master' of https://github.com/kubernetes/website into release-1.9

* 'master' of https://github.com/kubernetes/website: (549 commits)
  Update service.md (#7810)
  Prune inactive maintainers (#7830)
  add Amadeus to index page and add feature image (#7827)
  Update conventions.md (#7668)
  Adding Tenxcloud as KCSP and Hedvig typo (#7826)
  Update outdated documentation about secret key validation. (#7675)
  Update imperative-command.md (#7699)
  Update manage-deployment.md (#7774)
  Add the OCI runtime description. (#7769)
  fix flag (#7814)
  fix flag (#7813)
  Add files via upload (#7816)
  Remove CoreOS guide that use Kubernetes v0.15.0 (#7821)
  "Nagions" should be "Nagios“ (#7762)
  Update docker-cli-to-kubectl.md (#7748)
  adjust a note format (#7812)
  add a note when mount a configmap to pod (#7745)
  Make using sysctls a task instead of a concept (#6808)
  Partners page updates (#7802)
  Fix a missing word in endpoint reconciler section (#7804)
  ...

.dockerignore

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

.editorconfig

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

.github/ISSUE_TEMPLATE.md

@@ -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:**
+https://kubernetes.io/...
+
+<!--Optional Information (remove the comment tags around information you would like to include)-->
+<!--Kubernetes Version:-->
+
+<!--Additional Information:-->

.github/ISSUE_TEMPLATE/bug-report.md

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

.github/ISSUE_TEMPLATE/feature-request.md

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

.github/ISSUE_TEMPLATE/support.md

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

.github/OWNERS

@@ -1,7 +0,0 @@
-# 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

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,24 +1,8 @@
-<!-- 🛈
+>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+> For 1.10 Features: set Milestone to 1.10 and Base Branch to release-1.10
+>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+> NOTE: After opening the PR, please *un-check and re-check* the ["Allow edits from maintainers"](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) box so that maintainers can work on your patch and speed up the review process. This is a temporary workaround to address a known issue with GitHub.> 
+>
+> Please delete this note before submitting the pull request.
 
- Hello!
-
- Remember to ADD A DESCRIPTION and delete this note before submitting
- your pull request. The description should explain what will change,
- and why.
-
- PLEASE title the FIRST commit appropriately, so that if you squash all
- your commits into one, the combined commit message makes sense.
- For overall help on editing and submitting pull requests, visit:
-  https://kubernetes.io/docs/contribute/start/#improve-existing-content
-
- Use the default base branch, “main”, if you're documenting existing
- features in the English localization.
-
- If you're working on a different localization (not English), see
- https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use
- for advice.
-
- If you're documenting a feature that will be part of a future release, see
- https://kubernetes.io/docs/contribute/new-content/new-features/ for advice.
-
--->
+![Allow edits from maintainers checkbox](https://help.github.com/assets/images/help/pull_requests/allow-maintainers-to-make-edits-sidebar-checkbox.png)

.github/workflows/OWNERS

@@ -1,14 +0,0 @@
-# See the OWNERS docs at https://go.k8s.io/owners
-
-# When modifying this file, consider the security implications of
-# allowing listed reviewers / approvals to modify or remove any
-# configured GitHub Actions.
-#
-options:
-  no_parent_owners: true
-
-reviewers:
-- sig-docs-leads
-
-approvers:
-- sig-docs-leads

.github/workflows/netlify-periodic-build.yml

@@ -1,15 +0,0 @@
----
-name: Scheduled Netlify site build
-on:
-  schedule: # Build twice daily: shortly after midnight and noon (UTC)
-            # Offset is to be nice to the build service
-  - cron: '4 0,12 * * *'
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-    - name: Trigger build on Netlify
-      env:
-        TOKEN: ${{ secrets.NETLIFY_BUILD_HOOK_KEY }}
-      run: >-
-          curl -s -H "Accept: application/json" -H "Content-Type: application/json" -X POST -d "{}" "https://api.netlify.com/build_hooks/${TOKEN}"

.gitignore

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

.gitmodules

@@ -1,7 +0,0 @@
-[submodule "themes/docsy"]
-	path = themes/docsy
-	url = https://github.com/google/docsy.git
-	branch = v0.2.0
-[submodule "api-ref-generator"]
-	path = api-ref-generator
-	url = https://github.com/kubernetes-sigs/reference-docs

.htmltest.yml

@@ -1,16 +0,0 @@
-DirectoryPath: public/docs
-IgnoreDirectoryMissingTrailingSlash: true
-CheckExternal: false
-IgnoreAltMissing: true
-CheckImages: false
-CheckScripts: false
-CheckMeta: false
-CheckMetaRefresh: false
-CheckLinks: false
-EnforceHTML5: false
-EnforceHTTPS: false
-IgnoreDirectoryMissingTrailingSlash: false
-IgnoreInternalEmptyHash: true
-IgnoreEmptyHref: true
-IgnoreDirs:
-  - "reference/generated/kubernetes-api"

.travis.yml

@@ -0,0 +1,20 @@
+language: go
+go:
+  - 1.8.3
+
+# Don't want default ./... here:
+install:
+- export PATH=$GOPATH/bin:$PATH
+- mkdir -p $HOME/gopath/src/k8s.io
+- mv $TRAVIS_BUILD_DIR $HOME/gopath/src/k8s.io/website
+
+# (1) Fetch dependencies for us to run the tests in test/examples_test.go
+- go get -t -v k8s.io/website/test
+
+# Simplified deduplication of dependencies.
+- cp -L -R $GOPATH/src/k8s.io/kubernetes/vendor/ $GOPATH/src/
+- rm -r $GOPATH/src/k8s.io/kubernetes/vendor/
+
+script:
+- go test -v k8s.io/website/test
+- ./verify-docs-format.sh

404.md

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

CONTRIBUTING.md

@@ -9,8 +9,7 @@ These are just guidelines, not rules. Use your best judgment, and feel free to p
 
 ### Code of Conduct
 
-Kubernetes follows the [Cloud Native Computing Foundation (CNCF) Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to the
-[Kubernetes Code of Conduct Committee](https://github.com/kubernetes/community/tree/master/committee-code-of-conduct) <conduct@kubernetes.io>.
+Kubernetes follows the [Cloud Native Computing Foundation (CNCF) Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to Sarah Novotny [sarahnovotny@google.com](mailto:sarahnovotny@google.com) and/or Dan Kohn [dan@linuxfoundation.org](mailto:dan@linuxfoundation.org).
 
 ### Documentation and Site Decisions
 
@@ -18,7 +17,7 @@ The [Kubernetes SIG Docs Discussion Group](https://groups.google.com/forum/#!for
 
 ### Style Guides and Templates
 
-Before submitting a pull request to create new content, please review the [Kubernetes.io style guide](http://kubernetes.io/docs/home/contribute/style-guide/) and follow the [instructions for using page templates](https://kubernetes.io/docs/contribute/style/page-content-types/).
+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
@@ -34,6 +33,4 @@ Note that code issues should be filed against the main kubernetes repository, wh
 
 ### Submitting Documentation Pull Requests
 
-If you're fixing an issue in the existing documentation, you should submit a PR against the main branch.  Follow [these instructions to create a documentation pull request against the kubernetes.io repository](http://kubernetes.io/docs/home/contribute/create-pull-request/).
-
-For more information, see [contributing to Kubernetes docs](https://kubernetes.io/docs/contribute/).
+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/).

Dockerfile

@@ -1,49 +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 golang:1.16-alpine
-
-LABEL maintainer="Luc Perkins <lperkins@linuxfoundation.org>"
-
-RUN apk add --no-cache \
-    curl \
-    gcc \
-    g++ \
-    musl-dev \
-    build-base \
-    libc6-compat
-
-ARG HUGO_VERSION
-
-RUN mkdir $HOME/src && \
-    cd $HOME/src && \
-    curl -L https://github.com/gohugoio/hugo/archive/refs/tags/v${HUGO_VERSION}.tar.gz | tar -xz && \
-    cd "hugo-${HUGO_VERSION}" && \
-    go install --tags extended
-
-FROM golang:1.16-alpine
-
-RUN apk add --no-cache \
-    runuser \
-    git \
-    openssh-client \
-    rsync \
-    npm && \
-    npm install -D autoprefixer postcss-cli
-
-RUN mkdir -p /var/hugo && \
-    addgroup -Sg 1000 hugo && \
-    adduser -Sg hugo -u 1000 -h /var/hugo hugo && \
-    chown -R hugo: /var/hugo && \
-    runuser -u hugo -- git config --global --add safe.directory /src
-
-COPY --from=0 /go/bin/hugo /usr/local/bin/hugo
-
-WORKDIR /src
-
-USER hugo:hugo
-
-EXPOSE 1313

Gemfile

@@ -0,0 +1,53 @@
+source "https://rubygems.org"
+
+# gem "github-pages", group: :jekyll_plugins
+
+gem "jekyll", "3.6.0"
+
+group :github_pages_compatible do
+    gem "json", "~> 1.7", ">= 1.7.7"
+    gem "coffee-script", "~> 2.4"
+    gem "coffee-script-source", "~> 1.12"
+    gem "ethon", "~> 0.10"
+    gem "execjs", "~> 2.7"
+    gem "minima", "~> 2.0"
+    gem "terminal-table", "~> 1.4"
+    gem "unicode-display_width", "~> 1.1"
+end
+
+group :jekyll_plugins do
+   gem "jekyll-feed", "~> 0.6"
+   gem "jekyll-sitemap"
+   gem "jekyll-gist"
+   gem "jekyll-paginate", "1.1.0"
+   gem "jekyll-seo-tag"
+   gem "jekyll-avatar", "~> 0.4"
+   gem "jekyll-coffeescript", "~> 1.0"
+   gem "jekyll-default-layout", "~> 0.1"
+   gem "jekyll-github-metadata", "~> 2.2"
+   gem "jekyll-optional-front-matter", "~> 0.1"
+   gem "jekyll-readme-index", "0.0.3"
+   gem "jekyll-redirect-from", "~> 0.13"
+   gem "jekyll-relative-links", "~> 0.2"
+   gem "jekyll-swiss", "~> 0.4"
+   gem "jekyll-theme-architect", "0.0.3"
+   gem "jekyll-theme-cayman", "0.0.3"
+   gem "jekyll-theme-dinky", "0.0.3"
+   gem "jekyll-theme-hacker", "0.0.3"
+   gem "jekyll-theme-leap-day", "0.0.3"
+   gem "jekyll-theme-merlot", "0.0.3"
+   gem "jekyll-theme-midnight", "0.0.3"
+   gem "jekyll-theme-minimal", "0.0.3"
+   gem "jekyll-theme-modernist", "0.0.3"
+   gem "jekyll-theme-primer", "~> 0.1"
+   gem "jekyll-theme-slate", "0.0.3"
+   gem "jekyll-theme-tactile", "0.0.3"
+   gem "jekyll-theme-time-machine", "0.0.3"
+   gem "jekyll-titles-from-headings", "~> 0.1"
+end
+
+gem "jekyll-include-cache", "~> 0.1"
+
+gem "kramdown", "~> 1.11"
+gem "rouge", "~> 2.0"
+gem "pry"

Gemfile.lock

@@ -0,0 +1,176 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    addressable (2.5.2)
+      public_suffix (>= 2.0.2, < 4.0)
+    coderay (1.1.2)
+    coffee-script (2.4.1)
+      coffee-script-source
+      execjs
+    coffee-script-source (1.12.2)
+    colorator (1.1.0)
+    ethon (0.11.0)
+      ffi (>= 1.3.0)
+    execjs (2.7.0)
+    faraday (0.13.1)
+      multipart-post (>= 1.2, < 3)
+    ffi (1.9.18)
+    forwardable-extended (2.6.0)
+    jekyll (3.6.0)
+      addressable (~> 2.4)
+      colorator (~> 1.0)
+      jekyll-sass-converter (~> 1.0)
+      jekyll-watch (~> 1.1)
+      kramdown (~> 1.14)
+      liquid (~> 4.0)
+      mercenary (~> 0.3.3)
+      pathutil (~> 0.9)
+      rouge (>= 1.7, < 3)
+      safe_yaml (~> 1.0)
+    jekyll-avatar (0.5.0)
+      jekyll (~> 3.0)
+    jekyll-coffeescript (1.0.1)
+      coffee-script (~> 2.2)
+    jekyll-default-layout (0.1.4)
+      jekyll (~> 3.0)
+    jekyll-feed (0.9.2)
+      jekyll (~> 3.3)
+    jekyll-gist (1.4.1)
+      octokit (~> 4.2)
+    jekyll-github-metadata (2.9.3)
+      jekyll (~> 3.1)
+      octokit (~> 4.0, != 4.4.0)
+    jekyll-include-cache (0.1.0)
+      jekyll (~> 3.3)
+    jekyll-optional-front-matter (0.3.0)
+      jekyll (~> 3.0)
+    jekyll-paginate (1.1.0)
+    jekyll-readme-index (0.0.3)
+      jekyll (~> 3.0)
+    jekyll-redirect-from (0.13.0)
+      jekyll (~> 3.3)
+    jekyll-relative-links (0.5.1)
+      jekyll (~> 3.3)
+    jekyll-sass-converter (1.5.0)
+      sass (~> 3.4)
+    jekyll-seo-tag (2.3.0)
+      jekyll (~> 3.3)
+    jekyll-sitemap (1.1.1)
+      jekyll (~> 3.3)
+    jekyll-swiss (0.4.0)
+    jekyll-theme-architect (0.0.3)
+      jekyll (~> 3.3)
+    jekyll-theme-cayman (0.0.3)
+      jekyll (~> 3.3)
+    jekyll-theme-dinky (0.0.3)
+      jekyll (~> 3.3)
+    jekyll-theme-hacker (0.0.3)
+      jekyll (~> 3.3)
+    jekyll-theme-leap-day (0.0.3)
+      jekyll (~> 3.3)
+    jekyll-theme-merlot (0.0.3)
+      jekyll (~> 3.3)
+    jekyll-theme-midnight (0.0.3)
+      jekyll (~> 3.3)
+    jekyll-theme-minimal (0.0.3)
+      jekyll (~> 3.3)
+    jekyll-theme-modernist (0.0.3)
+      jekyll (~> 3.3)
+    jekyll-theme-primer (0.5.2)
+      jekyll (~> 3.5)
+      jekyll-github-metadata (~> 2.9)
+      jekyll-seo-tag (~> 2.2)
+    jekyll-theme-slate (0.0.3)
+      jekyll (~> 3.3)
+    jekyll-theme-tactile (0.0.3)
+      jekyll (~> 3.3)
+    jekyll-theme-time-machine (0.0.3)
+      jekyll (~> 3.3)
+    jekyll-titles-from-headings (0.5.0)
+      jekyll (~> 3.3)
+    jekyll-watch (1.5.0)
+      listen (~> 3.0, < 3.1)
+    json (1.8.6)
+    kramdown (1.15.0)
+    liquid (4.0.0)
+    listen (3.0.8)
+      rb-fsevent (~> 0.9, >= 0.9.4)
+      rb-inotify (~> 0.9, >= 0.9.7)
+    mercenary (0.3.6)
+    method_source (0.9.0)
+    minima (2.1.1)
+      jekyll (~> 3.3)
+    multipart-post (2.0.0)
+    octokit (4.7.0)
+      sawyer (~> 0.8.0, >= 0.5.3)
+    pathutil (0.16.0)
+      forwardable-extended (~> 2.6)
+    pry (0.11.2)
+      coderay (~> 1.1.0)
+      method_source (~> 0.9.0)
+    public_suffix (3.0.0)
+    rb-fsevent (0.10.2)
+    rb-inotify (0.9.10)
+      ffi (>= 0.5.0, < 2)
+    rouge (2.2.1)
+    safe_yaml (1.0.4)
+    sass (3.5.3)
+      sass-listen (~> 4.0.0)
+    sass-listen (4.0.0)
+      rb-fsevent (~> 0.9, >= 0.9.4)
+      rb-inotify (~> 0.9, >= 0.9.7)
+    sawyer (0.8.1)
+      addressable (>= 2.3.5, < 2.6)
+      faraday (~> 0.8, < 1.0)
+    terminal-table (1.8.0)
+      unicode-display_width (~> 1.1, >= 1.1.1)
+    unicode-display_width (1.3.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  coffee-script (~> 2.4)
+  coffee-script-source (~> 1.12)
+  ethon (~> 0.10)
+  execjs (~> 2.7)
+  jekyll (= 3.6.0)
+  jekyll-avatar (~> 0.4)
+  jekyll-coffeescript (~> 1.0)
+  jekyll-default-layout (~> 0.1)
+  jekyll-feed (~> 0.6)
+  jekyll-gist
+  jekyll-github-metadata (~> 2.2)
+  jekyll-include-cache (~> 0.1)
+  jekyll-optional-front-matter (~> 0.1)
+  jekyll-paginate (= 1.1.0)
+  jekyll-readme-index (= 0.0.3)
+  jekyll-redirect-from (~> 0.13)
+  jekyll-relative-links (~> 0.2)
+  jekyll-seo-tag
+  jekyll-sitemap
+  jekyll-swiss (~> 0.4)
+  jekyll-theme-architect (= 0.0.3)
+  jekyll-theme-cayman (= 0.0.3)
+  jekyll-theme-dinky (= 0.0.3)
+  jekyll-theme-hacker (= 0.0.3)
+  jekyll-theme-leap-day (= 0.0.3)
+  jekyll-theme-merlot (= 0.0.3)
+  jekyll-theme-midnight (= 0.0.3)
+  jekyll-theme-minimal (= 0.0.3)
+  jekyll-theme-modernist (= 0.0.3)
+  jekyll-theme-primer (~> 0.1)
+  jekyll-theme-slate (= 0.0.3)
+  jekyll-theme-tactile (= 0.0.3)
+  jekyll-theme-time-machine (= 0.0.3)
+  jekyll-titles-from-headings (~> 0.1)
+  json (~> 1.7, >= 1.7.7)
+  kramdown (~> 1.11)
+  minima (~> 2.0)
+  pry
+  rouge (~> 2.0)
+  terminal-table (~> 1.4)
+  unicode-display_width (~> 1.1)
+
+BUNDLED WITH
+   1.15.4

LICENSE

@@ -33,7 +33,7 @@ exhaustive, and do not form part of our licenses.
      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
+	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
@@ -48,9 +48,9 @@ exhaustive, and do not form part of our licenses.
      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
+     respect those requests where reasonable. More_considerations
+     for the public: 
+	wiki.creativecommons.org/Considerations_for_licensees
 
 =======================================================================
 
@@ -378,7 +378,7 @@ Section 8 -- Interpretation.
 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
+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
@@ -393,4 +393,3 @@ the avoidance of doubt, this paragraph does not form part of the
 public licenses.
 
 Creative Commons may be contacted at creativecommons.org.
-

Makefile

@@ -1,101 +1,18 @@
-HUGO_VERSION      = $(shell grep ^HUGO_VERSION netlify.toml | tail -n 1 | cut -d '=' -f 2 | tr -d " \"\n")
-NODE_BIN          = node_modules/.bin
-NETLIFY_FUNC      = $(NODE_BIN)/netlify-lambda
-
-# The CONTAINER_ENGINE variable is used for specifying the container engine. By default 'docker' is used
-# but this can be overridden when calling make, e.g.
-# CONTAINER_ENGINE=podman make container-image
-CONTAINER_ENGINE ?= docker
-IMAGE_REGISTRY ?= gcr.io/k8s-staging-sig-docs
-IMAGE_VERSION=$(shell scripts/hash-files.sh Dockerfile Makefile | cut -c 1-12)
-CONTAINER_IMAGE   = $(IMAGE_REGISTRY)/k8s-website-hugo:v$(HUGO_VERSION)-$(IMAGE_VERSION)
-CONTAINER_RUN     = $(CONTAINER_ENGINE) run --rm --interactive --tty --volume $(CURDIR):/src
-
-CCRED=\033[0;31m
-CCEND=\033[0m
-
 .PHONY: all build build-preview help serve
 
 help: ## Show this help.
 	@awk 'BEGIN {FS = ":.*?## "} /^[a-zA-Z_-]+:.*?## / {sub("\\\\n",sprintf("\n%22c"," "), $$2);printf "\033[36m%-20s\033[0m %s\n", $$1, $$2}' $(MAKEFILE_LIST)
 
-module-check: ## Check if all of the required submodules are correctly initialized.
-	@git submodule status --recursive | awk '/^[+-]/ {err = 1; printf "\033[31mWARNING\033[0m Submodule not initialized: \033[34m%s\033[0m\n",$$2} END { if (err != 0) print "You need to run \033[32mmake module-init\033[0m to initialize missing modules first"; exit err }' 1>&2
+all: build ## Build site with production settings and put deliverables in _site.
 
-module-init: ## Initialize required submodules.
-	@echo "Initializing submodules..." 1>&2
-	@git submodule update --init --recursive --depth 1
+build: ## Build site with production settings and put deliverables in _site.
+	bundle exec jekyll build
 
-all: build ## Build site with production settings and put deliverables in ./public
+build-preview: ## Build site with drafts and future posts enabled.
+	bundle exec jekyll build --drafts --future
 
-build: module-check ## Build site with non-production settings and put deliverables in ./public
-	hugo --minify --environment development
+serve: ## Boot the development server.
+	bundle exec jekyll serve
 
-build-preview: module-check ## Build site with drafts and future posts enabled
-	hugo --buildDrafts --buildFuture --environment preview
-
-deploy-preview: ## Deploy preview site via netlify
-	hugo --enableGitInfo --buildFuture --environment preview -b $(DEPLOY_PRIME_URL)
-
-functions-build:
-	$(NETLIFY_FUNC) build functions-src
-
-check-headers-file:
-	scripts/check-headers-file.sh
-
-production-build: module-check ## Build the production site and ensure that noindex headers aren't added
-	hugo --minify --environment production
-	HUGO_ENV=production $(MAKE) check-headers-file
-
-non-production-build: module-check ## Build the non-production site, which adds noindex headers to prevent indexing
-	hugo --enableGitInfo --environment nonprod
-
-serve: module-check ## Boot the development server.
-	hugo server --buildFuture --environment development
-
-docker-image:
-	@echo -e "$(CCRED)**** The use of docker-image is deprecated. Use container-image instead. ****$(CCEND)"
-	$(MAKE) container-image
-
-docker-build:
-	@echo -e "$(CCRED)**** The use of docker-build is deprecated. Use container-build instead. ****$(CCEND)"
-	$(MAKE) container-build
-
-docker-serve:
-	@echo -e "$(CCRED)**** The use of docker-serve is deprecated. Use container-serve instead. ****$(CCEND)"
-	$(MAKE) container-serve
-
-container-image: ## Build a container image for the preview of the website
-	$(CONTAINER_ENGINE) build . \
-		--network=host \
-		--tag $(CONTAINER_IMAGE) \
-		--build-arg HUGO_VERSION=$(HUGO_VERSION)
-
-container-build: module-check
-	$(CONTAINER_RUN) --read-only --mount type=tmpfs,destination=/tmp,tmpfs-mode=01777 $(CONTAINER_IMAGE) sh -c "npm ci && hugo --minify --environment development"
-
-container-serve: module-check ## Boot the development server using container. Run `make container-image` before this.
-	$(CONTAINER_RUN) --cap-drop=ALL --cap-add=AUDIT_WRITE --read-only --mount type=tmpfs,destination=/tmp,tmpfs-mode=01777 -p 1313:1313 $(CONTAINER_IMAGE) hugo server --buildFuture --environment development --bind 0.0.0.0 --destination /tmp/hugo --cleanDestinationDir
-
-test-examples:
-	scripts/test_examples.sh install
-	scripts/test_examples.sh run
-
-.PHONY: link-checker-setup
-link-checker-image-pull:
-	$(CONTAINER_ENGINE) pull wjdp/htmltest
-
-docker-internal-linkcheck:
-	@echo -e "$(CCRED)**** The use of docker-internal-linkcheck is deprecated. Use container-internal-linkcheck instead. ****$(CCEND)"
-	$(MAKE) container-internal-linkcheck
-
-container-internal-linkcheck: link-checker-image-pull
-	$(CONTAINER_RUN) $(CONTAINER_IMAGE) hugo --config config.toml,linkcheck-config.toml --buildFuture --environment test
-	$(CONTAINER_ENGINE) run --mount type=bind,source=$(CURDIR),target=/test --rm wjdp/htmltest htmltest
-
-clean-api-reference: ## Clean all directories in API reference directory, preserve _index.md
-	rm -rf content/en/docs/reference/kubernetes-api/*/
-
-api-reference: clean-api-reference ## Build the API reference pages. go needed
-	cd api-ref-generator/gen-resourcesdocs && \
-		go run cmd/main.go kwebsite --config-dir ../../api-ref-assets/config/ --file ../../api-ref-assets/api/swagger.json --output-dir ../../content/en/docs/reference/kubernetes-api --templates ../../api-ref-assets/templates
+stage: ## Run the Jekyll staging container.
+	docker run -ti --rm -v "${PWD}":/k8sdocs -p 4000:4000 gcr.io/google-samples/k8sdocs:1.1

OWNERS

@@ -1,19 +1,11 @@
-# See the OWNERS docs at https://go.k8s.io/owners
-
 reviewers:
-- sig-docs-en-reviews # Defined in OWNERS_ALIASES
-
+- tengqm
+- zhangxiaoyu-zidif
+- xiangpengzhao
 approvers:
-- sig-docs-en-owners # Defined in OWNERS_ALIASES
-
-emeritus_approvers:
-# - chenopis, commented out to disable PR assignments
-# - irvifa, commented out to disable PR assignments
-# - jaredbhatti, commented out to disable PR assignments
-# - kbarnard10, commented out to disable PR assignments
-# - steveperry-53, commented out to disable PR assignments
-- stewart-yu 
-# - zacharysarah, commented out to disable PR assignments
-
-labels:
-- sig/docs
+- heckj
+- bradamant3
+- bradtopol
+- steveperry-53
+- zacharysarah
+- chenopis

OWNERS_ALIASES

@@ -1,270 +1,205 @@
 aliases:
-  sig-docs-blog-owners: # Approvers for blog content
-    - onlydole
-    - mrbobbytables
-    - sftim
-  sig-docs-blog-reviewers: # Reviewers for blog content
-    - mrbobbytables
-    - onlydole
-    - sftim
-    - nate-double-u
-  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
-    - annajung
-    - bradtopol
-    - celestehorgan
-    - divya-mohan0209
-    - jimangel
-    - jlbutler
-    - kbhawkey
-    - natalisucks
-    - onlydole
-    - pi-victor
-    - reylejano
-    - savitharaghunathan
-    - sftim
-    - tengqm
-    - zacharysarah
-  sig-docs-en-reviews: # PR reviews for English content
-    - bradtopol
-    - celestehorgan
-    - daminisatya
-    - divya-mohan0209
-    - jimangel
-    - kbhawkey
-    - mehabhalodiya
-    - natalisucks
-    - onlydole
-    - rajeshdeshpande02
-    - sftim
-    - shannonxtreme
-    - tengqm
-    - zacharysarah
-  sig-docs-es-owners: # Admins for Spanish content
-    - raelga
-    - electrocucaracha
-  sig-docs-es-reviews: # PR reviews for Spanish content
-    - raelga
-    - electrocucaracha
-  sig-docs-fr-owners: # Admins for French content
-    - remyleone
-    - perriea
-    - rekcah78
-    - yastij
-    - smana
-    - rbenzair
-    - abuisine
-    - erickhun
-    - jygastaud
-    - awkif
-    - oussemos
-    - anthonydahanne
-    - feloy
-  sig-docs-fr-reviews: # PR reviews for French content
-    - remyleone
-    - perriea
-    - rekcah78
-    - yastij
-    - smana
-    - rbenzair
-    - abuisine
-    - erickhun
-    - jygastaud
-    - awkif
-    - oussemos
-    - anthonydahanne
-    - feloy
-  sig-docs-hi-owners: # Admins for Hindi content
-    - anubha-v-ardhan
-    - divya-mohan0209
-    - mittalyashu
-  sig-docs-hi-reviews: # PR reviews for Hindi content
-    - anubha-v-ardhan
-    - divya-mohan0209
-    - mittalyashu
-    - verma-kunal
-  sig-docs-id-owners: # Admins for Indonesian content
-    - ariscahyadi
-    - danninov
-    - girikuncoro
-    - habibrosyad
-    - phanama
-    - wahyuoi
-  sig-docs-id-reviews: # PR reviews for Indonesian content
-    - ariscahyadi
-    - danninov
-    - girikuncoro
-    - habibrosyad
-    - phanama
-    - wahyuoi
-  sig-docs-it-owners: # Admins for Italian content
-    - fabriziopandini
-    - Fale
-    - mattiaperi
-    - micheleberardi
-  sig-docs-it-reviews: # PR reviews for Italian content
-    - fabriziopandini
-    - Fale
-    - mattiaperi
-    - micheleberardi
-  sig-docs-ja-owners: # Admins for Japanese content
-    # cstoku
-    - inductor
-    - nasa9084
-  sig-docs-ja-reviews: # PR reviews for Japanese content
-    - bells17
-    # cstoku
-    - inductor
-    - kakts
-    - makocchi-git
-    # MasayaAoyama
-    - nasa9084
-    # oke-py
-  sig-docs-ko-owners: # Admins for Korean content
-    - ClaudiaJKang
-    - gochist
-    - ianychoi
-    - jihoon-seo
-    - seokho-son
-    - ysyukr
-  sig-docs-ko-reviews: # PR reviews for Korean content
-    - ClaudiaJKang
-    - gochist
-    - ianychoi
-    - jihoon-seo
-    - jmyung
-    - pjhwa
-    - seokho-son
-    - yoonian
-    - ysyukr
-  sig-docs-leads: # Website chairs and tech leads
-    - divya-mohan0209
-    - jimangel
-    - kbhawkey
-    - natalisucks
-    - onlydole
-    - reylejano
-    - sftim
-    - tengqm
-  sig-docs-zh-owners: # Admins for Chinese content
-    # chenopis
-    - chenrui333
-    # dchen1107
-    # haibinxie
-    # hanjiayao
-    - howieyuen
-    # lichuqiang
-    - mengjiao-liu
-    - SataQiu
-    - tanjunchen
-    - tengqm
-    - xichengliudui
-    # zhangxiaoyu-zidif
-  sig-docs-zh-reviews: # PR reviews for Chinese content
-    - chenrui333
-    - chenxuc
-    - howieyuen
-    - idealhack
-    - mengjiao-liu
-    - pigletfly
-    - SataQiu
-    - tanjunchen
-    - tengqm
-    - xichengliudui
-    # zhangxiaoyu-zidif
-  sig-docs-pt-owners: # Admins for Portuguese content
-    - edsoncelio
-    - femrtnz
-    - jailton
-    - jcjesus
-    - devlware
-    - jhonmike
-    - rikatz
-    - yagonobre
-  sig-docs-pt-reviews: # PR reviews for Portugese content
-    - edsoncelio
-    - femrtnz
-    - jailton
-    - jcjesus
-    - devlware
-    - jhonmike
-    - rikatz
-    - yagonobre
-  sig-docs-vi-owners: # Admins for Vietnamese content
-    - huynguyennovem
-    - ngtuna
-    - truongnh1992
-  sig-docs-vi-reviews: # PR reviews for Vietnamese content
-    - huynguyennovem
-    - ngtuna
-    - truongnh1992
-  sig-docs-ru-owners: # Admins for Russian content
-    - msheldyakov
-    - aisonaku
-    - potapy4
-    - dianaabv
-  sig-docs-ru-reviews: # PR reviews for Russian content
-    - Arhell
-    - msheldyakov
-    - aisonaku
-    - potapy4
-    - dianaabv
-  sig-docs-pl-owners: # Admins for Polish content
-    - mfilocha
-    - nvtkaszpir
-  sig-docs-pl-reviews: # PR reviews for Polish content
-    - mfilocha
-    - nvtkaszpir
-    - kpucynski
-  sig-docs-uk-owners: # Admins for Ukrainian content
-    - anastyakulyk
-    - butuzov
-    - MaxymVlasov
-  sig-docs-uk-reviews: # PR reviews for Ukrainian content
-    - anastyakulyk
-    - Arhell
-    - butuzov
-    - idvoretskyi
-    - MaxymVlasov
-    - Potapy4
-  # authoritative source: git.k8s.io/community/OWNERS_ALIASES
-  committee-steering: # provide PR approvals for announcements
-    - cblecker
-    - dims
-    - justaugustus
+  sig-api-machinery: #Team: API Server; GH: sig-api-machinery-pr-reviews; e.g. Annotations, Labels
+    - lavalamp
+    - sttts
     - liggitt
-    - mrbobbytables
-    - parispittman
-    - tpepper
-  # authoritative source: https://git.k8s.io/sig-release/OWNERS_ALIASES
-  sig-release-leads:
-    - cpanato # SIG Technical Lead
-    - jeremyrickard # SIG Technical Lead
-    - justaugustus # SIG Chair
-    - LappleApple # SIG Program Manager
-    - puerco # SIG Technical Lead
-    - saschagrunert # SIG Chair
-  release-engineering-approvers:
-    - cpanato # Release Manager
-    - palnabarun # Release Manager
-    - puerco # Release Manager
-    - saschagrunert # subproject owner / Release Manager
-    - justaugustus # subproject owner / Release Manager
-    - Verolop # Release Manager
-    - xmudrii # Release Manager
-  release-engineering-reviewers:
-    - ameukam # Release Manager Associate
-    - jimangel # Release Manager Associate
-    - markyjackson-taulia # Release Manager Associate
-    - mkorbi # Release Manager Associate
-    - onlydole # Release Manager Associate
-    - sethmccombs # Release Manager Associate
-    - thejoycekung # Release Manager Associate
-    - wilsonehusin # Release Manager Associate
+    - smarterclayton
+    - deads2k
+  sig-apps: #Team: Workloads; GH: sig-apps-pr-reviews; e.g. ConfigMaps, CronJobs, CustomResourceDefinitions, DaemonSets, Deployments, Jobs, Secrets, StatefulSets
+    - enisoc
+    - erictune
+    - foxish
+    - janetkuo
+    - kow3ns
+    - lukaszo
+    - mfojtik
+    - smarterclayton
+    - soltysh
+    - tnozicka
+  sig-architecture: #GH: sig-architecture-pr-reviews
+    - smarterclayton
+    - bgrant0607
+  sig-auth: #GH: sig-auth-pr-reviews
+    - php-coder
+    - liggitt
+    - mikedanese
+    - ericchiang
+    - mattmoyer
+    - enj
+    - deads2k
+    - davidopp
+  sig-autoscaling: #GH: sig-autoscaling-pr-reviews
+    - DirectXMan12
+    - bskiba
+    - aleksandra-malinowska
+    - MaciekPytel
+    - davidopp
+    - mwielgus
+  sig-aws: #Amazon AWS
+    - justinsb
+    - kris-nova
+    - chrislovecnm
+    - mfburnett
+  sig-azure: #Microsoft Azure
+    - slack
+    - colemickens
+    - jdumars
+  sig-big-data: #GH: sig-big-data-pr-reviews
+    - foxish
+  sig-cli: #Team: CLI; GH: sig-cli-pr-reviews; e.g. kubectl
+    - adohe
+    - deads2k
+    - derekwaynecarr
+    - dims
+    - dshulyak
+    - eparis
+    - ericchiang
+    - ghodss
+    - mengqiy
+    - rootfs
+    - shiywang
+    - smarterclayton
+    - soltysh
+    - sttts
+  sig-cluster-lifecycle: #GH: sig-cluster-lifecycle-pr-reviews
+    - jbeda
+    - timothysc
+    - lukemarsden
+    - pipejakob
+    - dmmcquay
+    - mattmoyer
+    - luxas
+    - roberthbailey
+    - medinatiger
+  sig-cluster-ops:
+    - zehicle
+    - jdumars
+  sig-contribex: #aka Contributor Experience; GH: sig-contributor-experience-pr-reviews
+    - rmmh
+    - cblecker
+    - apelisse
+    - grodrigues3
+    - spxtr
+  sig-contributor-experience: #GH: sig-contributor-experience-pr-reviews
+    - rmmh
+    - cblecker
+    - apelisse
+    - grodrigues3
+    - spxtr
+  sig-docs: #Team: documentation; GH: sig-docs-pr-reviews
+    - bradamant3
+    - steveperry-53
+    - zacharysarah
+    - bradtopol
+    - heckj
+  sig-federation: #Team: Federation; e.g. Federated Clusters
+    - csbell
+  sig-gcp: #Google Cloud Platform; GH: sig-gcp-pr-reviews
+    - abgworrall
+  sig-instrumentation: #GH: sig-instrumentation-pr-reviews; e.g. metrics, logging, events
+    - DirectXMan12
+    - x13n
+    - kawych
+    - crassirostris
+    - brancz
+    - fabxc
+    - loburm
+    - piosz
+    - fgrzadkowski
+  sig-multicluster: #GH: sig-multicluster-pr-reviews; e.g. resiliency against availability zone outages; hybrid clouds; spanning multiple cloud providers; migration to public clouds
+    - madhusudancs
+    - marun
+    - jianhuiz
+    - shashidharatd
+    - nikhiljindal
+    - quinton-hoole
+    - mwielgus
+    - csbell
+  sig-network: #Team: Network; GH: sig-network-pr-reviews; e.g. Ingress, Network Policies, Services
+    - bowei
+    - caseydavenport
+    - danwinship
+    - dcbw
+    - dnardo
+    - freehan
+    - mrhohn
+    - nicksardo
+    - thockin
+  sig-node: #Team: Node; GH: sig-node-pr-reviews; e.g. Containers, Docker, Images, OS images, Pods, Registries
+    - Random-Liu
+    - dashpole
+    - dchen1107
+    - derekwaynecarr
+    - dims
+    - feiskyer
+    - mtaufen
+    - ncdc
+    - pmorie
+    - resouer
+    - sjpotter
+    - tallclair
+    - tmrts
+    - vishh
+    - yifan-gu
+    - yujuhong
+  sig-onprem: #On-premises; GH: sig-onprem-pr-reviews
+    - zen
+    - idvoretskyi
+    - pigmej
+    - feiskyer
+    - nebril
+  sig-openstack: #GH: sig-openstack-pr-reviews
+    - hogepodge
+    - dklyle
+    - rjmorse
+  sig-pm: #aka Product Management
+    - apsinha
+    - idvoretskyi
+    - calebamiles
+  sig-product-management:
+    - apsinha
+    - idvoretskyi
+    - calebamiles
+  sig-release: #GH: sig-release-pr-reviews
+    - calebamiles
+    - enisoc
+    - pwittrock
+  sig-rktnetes:
+    - calebamiles
+  sig-scalability: #GH: sig-scalability-pr-reviews
+    - jbeda
+    - spiffxp
+    - lavalamp
+    - countspongebob
+  sig-scheduling: #Team: Sharing; GH: sig-scheduling-pr-reviews; e.g. Scheduler
+    - bsalamat
+    - davidopp
+    - jayunit100
+    - k82cn
+    - resouer
+    - timothysc
+    - wojtek-t
+  sig-service-catalog: #GH: sig-service-catalog-pr-reviews; e.g. Service Broker
+    - pmorie
+    - jessfraz
+    - pwittrock
+    - droot
+    - seans3
+  sig-storage: #Team: Storage; GH: sig-storage-pr-reviews; e.g. Volumes
+    - childsb
+    - jsafrane
+    - rootfs
+    - saad-ali
+    - matchstick
+    - msau42
+  sig-testing: #GH: sig-testing-pr-reviews
+    - fejta
+    - ixdy
+    - rmmh
+    - spiffxp
+    - spxtr
+  sig-ui: #User Interface
+    - danielromlein
+    - floreks
+  sig-windows:
+    - michmike

README-de.md

@@ -1,97 +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-Request, um uns darüber zu informieren.
-
-Sobald Ihre Pull-Request 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 Ihre Pull-Request entsprechend des Feedbacks, welches 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](https://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
-* [Seitenvorlagen verwenden](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [Dokumentationsstil-Handbuch](https://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)
-
-## Website 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 Website-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-Website-lokal-mit-Hugo-ausführen).
-
-Das benötigte [Docsy Hugo theme](https://github.com/google/docsy#readme) muss als git submodule installiert werden:
-
-```
-#Füge das Docsy submodule hinzu
-git submodule update --init --recursive --depth 1
-```
-
-Wenn Sie Docker [installiert](https://www.docker.com/get-started) haben, erstellen Sie das Docker-Image `kubernetes-hugo` lokal:
-
-```bash
-make container-image
-```
-
-Nachdem das Image erstellt wurde, können Sie die Website lokal öffnen:
-
-```bash
-make container-serve
-```
-
-Öffnen Sie Ihren Browser unter http://localhost:1313, um die Website anzuzeigen. Wenn Sie Änderungen an den Quelldateien vornehmen, aktualisiert Hugo die Website und erzwingt eine Browseraktualisierung.
-
-## Die Website 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.
-
-Das benötigte [Docsy Hugo-Theme](https://github.com/google/docsy#readme) muss als git submodule installiert werden:
-
-```
-#Füge das Docsy submodule hinzu
-git submodule update --init --recursive --depth 1
-```
-
-So führen Sie die Website lokal aus, wenn Sie Hugo installiert haben:
-
-```bash
-# Installieren der JavaScript Abhängigkeiten
-npm ci
-make serve
-```
-
-Dadurch wird der lokale Hugo-Server an Port 1313 gestartet. Öffnen Sie Ihren Browser unter http://localhost:1313, um die Website anzuzeigen. Wenn Sie Änderungen an den Quelldateien vornehmen, aktualisiert Hugo die Website und erzwingt eine Browseraktualisierung.
-
-## Community, Diskussion, Beteiligung und Unterstützung
-
-Erfahren Sie auf der [Community-Seite](https://kubernetes.io/community/) wie Sie mit der Kubernetes-Community interagieren können.
-
-Sie können die Betreuer dieses Projekts unter folgender Adresse erreichen:
-
-- [Slack](https://kubernetes.slack.com/messages/sig-docs)
-- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-### Verhaltensregeln
-
-Die Teilnahme an der Kubernetes-Community unterliegt dem [Kubernetes-Verhaltenskodex](code-of-conduct.md).
-
-## Vielen Dank!
-
-Kubernetes lebt vom Community-Engagement und wir freuen uns sehr über Ihre Beiträge zu unserer Website und unserer Dokumentation!

README-es.md

@@ -1,87 +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](https://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
-* [Utilizando las plantillas de las páginas](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [Guía de estilo de la documentación](https://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-kubernetesio-en-local-con-hugo).
-
-**`Nota`: Para el procedimiento de construir una imagen de Docker e iniciar el servidor.**
-El sitio web de Kubernetes utiliza Docsy Hugo theme. Se sugiere que se instale si aún no se ha hecho, los **submódulos** y otras dependencias de herramientas de desarrollo ejecutando el siguiente comando de `git`:
-
-```bash
-# pull de los submódulos del repositorio
-git submodule update --init --recursive --depth 1
-
-```
-
-Si identifica que `git` reconoce una cantidad innumerable de cambios nuevos en el proyecto, la forma más simple de solucionarlo es cerrando y volviendo a abrir el proyecto en el editor. Los submódulos son automáticamente detectados por `git`, pero los plugins usados por los editores pueden tener dificultades para ser cargados.
-
-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 container-image
-```
-
-Una vez tenga la imagen construida, puede levantar el sitio web ejecutando:
-
-```bash
-make container-serve
-```
-
-Abra su navegador y visite http://localhost:1313 para acceder a su copia local del sitio. A medida que vaya haciendo cambios en el código fuente, Hugo irá actualizando la página y forzará la actualización en el navegador.
-
-## Levantando kubernetes.io en local con Hugo
-
-Revise la [documentación oficial de Hugo](https://gohugo.io/getting-started/installing/) para obtener las instrucciones de instalación en su sistema operativo. Asegúrese de instalar la versión de Hugo especificada en la variable de entorno  `HUGO_VERSION` del fichero [`netlify.toml`](netlify.toml#L9).
-
-Para levantar el sitio localmente una vez Hugo está instalado en su sistema, puede ejecutar el siguiente comando:
-
-```bash
-make serve
-```
-
-Este comando levantará un servidor de Hugo en el puerto **1313** al que podrá acceder visitando http://localhost:1313 y dónde podrá visualizar su copia local del sitio web. A medida que vaya haciendo cambios en el código fuente, Hugo irá actualizando la página y forzará la actualización en el navegador.
-
-## Comunidad, discusión, contribuir y soporte
-
-Aprenda como participar en la comunidad de Kubernetes visitando la [página de comunidad](http://kubernetes.io/community/).
-
-Puede ponerse en contacto con los mantenedores de este proyecto en:
-
-- [Slack](https://kubernetes.slack.com/messages/sig-docs)
-- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-### Código de conducta
-
-La participación en la comunidad de Kubernetes está regulada por el [Código de Conducta de Kubernetes](code-of-conduct.md).
-
-## ¡Muchas gracias!
-
-Kubernetes es posible gracias a la participación de la comunidad y la documentación es vital para facilitar el acceso al proyecto.
-
-Agradecemos muchísimo sus contribuciones a nuestro sitio web y nuestra documentación.

README-fr.md

@@ -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 examinateurs 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/)
-* [Aperçu des modifications apportées à votre documentation](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
-* [Utilisation des modèles de page](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [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](#exécuter-le-site-localement-en-utilisant-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 container-image
-```
-
-Une fois l'image construite, vous pouvez exécuter le site localement :
-
-```bash
-make container-serve
-```
-
-Ouvrez votre navigateur à l'adresse: http://localhost:1313 pour voir le site.
-Lorsque vous apportez des modifications aux fichiers sources, Hugo met à jour le site et force le navigateur à rafraîchir la page.
-
-## Exécuter le site localement en utilisant Hugo
-
-Voir la [documentation officielle Hugo](https://gohugo.io/getting-started/installing/) pour les instructions d'installation Hugo.
-Assurez-vous d'installer la version Hugo spécifiée par la variable d'environnement `HUGO_VERSION` dans le fichier [`netlify.toml`](netlify.toml#L9).
-
-Pour exécuter le site localement lorsque vous avez Hugo installé :
-
-```bash
-make serve
-```
-
-Le serveur Hugo local démarrera sur le port 1313.
-Ouvrez votre navigateur à l'adresse: http://localhost:1313 pour voir le site.
-Lorsque vous apportez des modifications aux fichiers sources, Hugo met à jour le site et force le navigateur à rafraîchir la page.
-
-## Communauté, discussion, contribution et assistance
-
-Apprenez comment vous engager avec la communauté Kubernetes sur la [page communauté](http://kubernetes.io/community/).
-
-Vous pouvez joindre les responsables de ce projet à l'adresse :
-
-- [Slack](https://kubernetes.slack.com/messages/sig-docs)
-- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-### Code de conduite
-
-La participation à la communauté Kubernetes est régie par le [Code de conduite de Kubernetes](code-of-conduct.md).
-
-## Merci !
-
-Kubernetes prospère grâce à la participation de la communauté, et nous apprécions vraiment vos contributions à notre site et à notre documentation !

README-hi.md

@@ -1,87 +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)
-* [पेज टेम्पलेट](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [प्रलेखन शैली गाइड](http://kubernetes.io/docs/contribute/style/style-guide/)
-* [स्थानीयकरण कुबरनेट्स प्रलेखन](https://kubernetes.io/docs/contribute/localization/)
-
-## `README.md`'s स्थानीयकरण कुबरनेट्स प्रलेखन
-
-आप हिंदी स्थानीयकरण के मैन्टेनरों तक पहुँच सकते हैं:
-
-* Anubhav Vardhan ([Slack](https://kubernetes.slack.com/archives/D0261C0A3R8), [Twitter](https://twitter.com/anubha_v_ardhan), [GitHub](https://github.com/anubha-v-ardhan))
-* Divya Mohan ([Slack](https://kubernetes.slack.com/archives/D027R7BE804), [Twitter](https://twitter.com/Divya_Mohan02), [GitHub](https://github.com/divya-mohan0209))
-* 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 का उपयोग करके स्थानीय रूप से [साइट को चलाने](#hugo-का-उपयोग-करते-हुए-स्थानीय-रूप-से-साइट-चलाना) का तरीका देखें।
-
-यदि आप [डॉकर](https://www.docker.com/get-started) चला रहे हैं, तो स्थानीय रूप से `कुबेरनेट्स-ह्यूगो` Docker image बनाएँ:
-
-```bash
-make container-image
-```
-
-एक बार image बन जाने के बाद, आप साइट को स्थानीय रूप से चला सकते हैं:
-
-```bash
-make container-serve
-```
-
-साइट देखने के लिए अपने browser को `http://localhost:1313` पर खोलें। जैसा कि आप source फ़ाइलों में परिवर्तन करते हैं, Hugo साइट को अपडेट करता है और browser को refresh करने पर मजबूर करता है।
-
-## Hugo का उपयोग करते हुए स्थानीय रूप से साइट चलाना
-
-Hugo निर्देशों के लिए [आधिकारिक Hugo प्रलेखन](https://gohugo.io/getting-started/installing/) देखें। [`Netlify.toml`](netlify.toml#L9) फ़ाइल में `HUGO_VERSION` environment variable द्वारा निर्दिष्ट Hugo version को install करना सुनिश्चित करें।
-
-जब आप Hugo को install करते हैं तो स्थानीय रूप से साइट को चलाने के लिए:
-
-```bash
-make serve
-```
-
-यह पोर्ट `1313` पर Hugo सर्वर को शुरू करेगा। साइट देखने के लिए अपने browser को `http://localhost:1313` पर खोलें। जैसा कि आप source फ़ाइलों में परिवर्तन करते हैं, Hugo साइट को अपडेट करता है और एक browser को refresh करने पर मजबूर करता है।
-
-## समुदाय, चर्चा, योगदान और समर्थन
-
-[Community page](http://kubernetes.io/community/) पर कुबरनेट्स समुदाय के साथ जुड़ना सीखें।
-
-आप इस परियोजना के स्थानीयकरण तक पहुँच सकते हैं:
-
-- [Slack](https://kubernetes.slack.com/messages/sig-docs)
-- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-## कोड ओफ़ कंडक्ट
-
-कुबरनेट्स समुदाय में भागीदारी [कुबरनेट्स कोड ओफ़ कंडक्ट](https://github.com/cncf/foundation/blob/master/code-of-conduct-languages/hi.md) द्वारा शासित है.
-
-## धन्यवाद!
-
-कुबरनेट्स सामुदायिक भागीदारी पर पनपती है, और हम वास्तव में हमारी साइट और हमारे प्रलेखन में आपके योगदान की सराहना करते हैं!
-
-कुबरनेट्स आपकी भागीदारी पर निर्भर है, और हम हमारी साइट और प्रलेखन में आपके योगदान का मान करते हैं!

README-id.md

@@ -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](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [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-dengan-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 container-image
-```
-
-Setelah **image** berhasil di-**build**, kamu dapat menjalankan website tersebut pada mesin lokal-mu:
-
-```bash
-make container-serve
-```
-
-Buka **browser** kamu ke http://localhost:1313 untuk melihat laman dokumentasi. Selama kamu melakukan penambahan konten, **Hugo** akan secara otomatis melakukan perubahan terhadap laman dokumentasi apabila **browser** melakukan proses **refresh**.
-
-
-## Petunjuk untuk menjalankan website pada mesin lokal dengan menggunakan Hugo
-
-Kamu dapat melihat [dokumentasi resmi Hugo](https://gohugo.io/getting-started/installing/) untuk mengetahui langkah yang diperlukan untuk melakukan instalasi **Hugo**. Pastikan kamu melakukan instalasi versi **Hugo** sesuai dengan versi yang tersedia pada **environment variable** `HUGO_VERSION` pada **file**[`netlify.toml`](netlify.toml#L9).
-
-Untuk menjalankan laman pada mesin lokal setelah instalasi **Hugo**, kamu dapat menjalankan perintah berikut:
-
-```bash
-make serve
-```
-
-Buka **browser** kamu ke http://localhost:1313 untuk melihat laman dokumentasi. Selama kamu melakukan penambahan konten, **Hugo** akan secara otomatis melakukan perubahan terhadap laman dokumentasi apabila **browser** melakukan proses **refresh**.
-
-## Komunitas, Diskusi, Kontribusi, dan Bantuan
-
-Kamu dapat belajar bagaimana tata cara untuk ikut terlibat dalam komunitas Kubernetes melalui [laman komunitas](http://kubernetes.io/community/).
-
-Kamu dapat berinteraksi dengan **maintainers** project ini melalui:
-
-- [Slack](https://kubernetes.slack.com/messages/sig-docs)
-- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-### Etika dalam Berkontribusi
-
-Partisipasi dalam komunitas Kubernetes diatur dalam [Etika dalam Berkontribusi pada Kubernetes](code-of-conduct.md).
-
-## Terima Kasih!
-
-Kubernetes sangat menjunjung tinggi partisipasi dari komunitas, dan kami sangat mengapresiasi kontribusi kamu pada laman dan dokumentasi kami!

README-it.md

@@ -1,71 +0,0 @@
-# La documentazione di 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)
-
-Benvenuto! Questo repository contiene tutte le informazioni necessarie per creare la [documentazione e il sito web di Kubernetes](https://kubernetes.io/). Siamo onorati che tu voglia contribuire!
-
-## Come contribuire alla documentazione
-
-Puoi premere il pulsante **Fork** in alto nella parte destra dello schermo per creare una copia di questo repository sotto la tua utenza di GitHub. Questa copia è chiamata un *fork*. Puoi fare tutte le modifiche che vuoi nel tuo fork, e quando sei pronto a mandarci i cambiamenti, vai sulla pagina del tuo fork e crea una nuova pull request per farcelo sapere.
-
-Una volta che hai creato la pull request, un reviewer (revisore) Kubernetes la prenderà in carico per fornire un feedback chiaro e concretamente attuabile. Come owner della pull request, **è tua responsabilità modificare la tua pull request per rispondere al feedback che ti è stato fornito dal reviewer Kubernetes**. Inoltre, tieni presente che potresti ricevere feedback da più di un Reviewer di Kubernetes, incluse quindi persone diverse da quella che ti ha fornito il primo feedback. In alcuni casi, uno dei tuoi reviewer potrebbe richiedere una revisione tecnica da un [technical reviewer di Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) quando necessario. I reviewer faranno del loro meglio per fornire feedback in modo tempestivo, ma i tempi di risposta possono variare in base alle circostanze.
-
-Per maggiori informazioni su come contribuire alla documentazione Kubernetes, vedi:
-
-* [Cominciare a contribuire](https://kubernetes.io/docs/contribute/start/)
-* [Vedere le modifiche localmente](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
-* [Utilizzare i template delle pagine](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [Guida Stilistica per la documentazione di Kubernetes](http://kubernetes.io/docs/contribute/style/style-guide/)
-* [Tradurre la documentazione di Kubernetes](https://kubernetes.io/docs/contribute/localization/)
-
-## Eseguire il sito Web localmente usando Docker
-
-Il modo consigliato per eseguire localmente il sito Web Kubernetes prevede l'utilizzo di un'immagine [Docker](https://docker.com) inclusa nel sito e configurata con tutti i software necessari, a partire dal generatore di siti web statici [Hugo](https://gohugo.io).
-
-> Se stai utilizzando Windows, avrai bisogno di alcuni strumenti aggiuntivi che puoi installare con [Chocolatey](https://chocolatey.org). `choco install make`
-
-> Se preferisci eseguire il sito Web localmente senza Docker, vedi [Eseguire il sito Web localmente utilizzando Hugo](#eseguire-il-sito-web-localmente-utilizzando-hugo) di seguito.
-
-Se hai Docker [attivo e funzionante](https://www.docker.com/get-started), crea l'immagine Docker `kubernetes-hugo` localmente:
-
-```bash
-make container-image
-```
-
-Dopo aver creato l'immagine, è possibile eseguire il sito Web localmente:
-
-```bash
-make container-serve
-```
-
-Apri il tuo browser su http://localhost:1313 per visualizzare il sito Web. Mentre modifichi i file sorgenti, Hugo aggiorna automaticamente il sito Web e forza un aggiornamento della pagina visualizzata nel browser.
-
-## Eseguire il sito Web localmente utilizzando Hugo
-
-Vedi la [documentazione ufficiale di Hugo](https://gohugo.io/getting-started/installing/) per le istruzioni di installazione di Hugo. Assicurati di installare esattamente la versione di Hugo specificata dalla variabile d'ambiente `HUGO_VERSION` nel file [`netlify.toml`](netlify.toml#L9).
-
-Per eseguire il sito Web localmente dopo aver installato Hugo:
-
-```bash
-make serve
-```
-
-Questo comando avvierà il server Hugo locale sulla porta 1313. Apri il tuo browser su http://localhost:1313 per visualizzare il sito Web. Mentre apporti modifiche ai file di origine, Hugo aggiorna il sito Web e forza un aggiornamento del browser.
-
-## Community, discussioni, contribuire e supporto
-
-Scopri come interagire con la community di Kubernetes nella [pagina della community](http://kubernetes.io/community/).
-
-Puoi contattare i maintainers di questo progetto su:
-
-- [Slack](https://kubernetes.slack.com/messages/sig-docs)
-- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-### Codice di condotta
-
-La partecipazione alla comunità Kubernetes è regolata dal [Codice di condotta di Kubernetes](code-of-conduct.md).
-
-## Grazie!
-
-Kubernetes prospera grazie alla partecipazione della comunity e apprezziamo i tuoi contributi al nostro sito Web e alla nostra documentazione!

README-ja.md

@@ -1,193 +0,0 @@
-# Kubernetesのドキュメント
-
-[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-main-staging/deploys) [![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-このリポジトリには、[KubernetesのWebサイトとドキュメント](https://kubernetes.io/)をビルドするために必要な全アセットが格納されています。貢献に興味を持っていただきありがとうございます！
-
-- [ドキュメントに貢献する](#contributing-to-the-docs)
-- [翻訳された`README.md`一覧](#localization-readmemds)
-
-# リポジトリの使い方
-
-Hugo(Extended version)を使用してWebサイトをローカルで実行することも、コンテナランタイムで実行することもできます。コンテナランタイムを使用することを強くお勧めします。これにより、本番Webサイトとのデプロイメントの一貫性が得られます。
-
-## 前提条件
-
-このリポジトリを使用するには、以下をローカルにインストールする必要があります。
-
-- [npm](https://www.npmjs.com/)
-- [Go](https://golang.org/)
-- [Hugo(Extended version)](https://gohugo.io/)
-- [Docker](https://www.docker.com/)などのコンテナランタイム
-
-開始する前に、依存関係をインストールしてください。リポジトリのクローンを作成し、ディレクトリに移動します。
-
-```
-git clone https://github.com/kubernetes/website.git
-cd website
-```
-
-KubernetesのWebサイトではDocsyというHugoテーマを使用しています。コンテナでWebサイトを実行する場合でも、以下を実行して、サブモジュールおよびその他の開発依存関係をプルすることを強くお勧めします。
-
-```
-# pull in the Docsy submodule
-git submodule update --init --recursive --depth 1
-```
-
-## コンテナを使ってウェブサイトを動かす
-
-コンテナ内でサイトを構築するには、以下を実行してコンテナイメージを構築し、実行します。
-
-```
-make container-image
-make container-serve
-```
-
-お使いのブラウザにて http://localhost:1313 にアクセスしてください。リポジトリ内のソースファイルに変更を加えると、HugoがWebサイトの内容を更新してブラウザに反映します。
-
-## Hugoを使ってローカル環境でWebサイトを動かす
-
-[`netlify.toml`](netlify.toml#L10)ファイルに記述されている`HUGO_VERSION`と同じExtended versionのHugoをインストールするようにしてください。
-
-ローカルでサイトを構築してテストするには、次のコマンドを実行します。
-
-```bash
-# install dependencies
-npm ci
-make serve
-```
-
-これで、Hugoのサーバーが1313番ポートを使って開始します。お使いのブラウザにて http://localhost:1313 にアクセスしてください。リポジトリ内のソースファイルに変更を加えると、HugoがWebサイトの内容を更新してブラウザに反映します。
-
-## API reference pagesをビルドする
-
-`content/en/docs/reference/kubernetes-api`に配置されているAPIリファレンスページは<https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs>を使ってSwagger仕様書からビルドされています。
-
-新しいKubernetesリリースのためにリファレンスページをアップデートするには、次の手順を実行します:
-
-1. `api-ref-generator`サブモジュールをプルする:
-
-   ```bash
-   git submodule update --init --recursive --depth 1
-   ```
-
-2. Swagger仕様書を更新する:
-
-   ```bash
-   curl 'https://raw.githubusercontent.com/kubernetes/kubernetes/master/api/openapi-spec/swagger.json' > api-ref-assets/api/swagger.json
-   ```
-
-3. 新しいリリースの変更を反映するため、`api-ref-assets/config/`で`toc.yaml`と`fields.yaml`を適用する。
-
-4. 次に、ページをビルドする:
-
-   ```bash
-   make api-reference
-   ```
-
-   コンテナイメージからサイトを作成・サーブする事でローカルで結果をテストすることができます:
-
-   ```bash
-   make container-image
-   make container-serve
-   ```
-
-   APIリファレンスを見るために、ブラウザで<http://localhost:1313/docs/reference/kubernetes-api/>を開いてください。
-
-5. 新しいコントラクトのすべての変更が設定ファイル`toc.yaml`と`fields.yaml`に反映されたら、新しく生成されたAPIリファレンスページとともにPull Requestを作成します。
-
-## トラブルシューティング
-
-### error: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): this feature is not available in your current Hugo version
-
-Hugoは、技術的な理由から2種類のバイナリがリリースされています。現在のウェブサイトは**Hugo Extended**バージョンのみに基づいて運営されています。[リリースページ](https://github.com/gohugoio/hugo/releases)で名前に「extended」が含まれるアーカイブを探します。確認するには、`hugo version`を実行し、「extended」という単語を探します。
-
-### macOSにてtoo many open filesというエラーが表示される
-
-macOS上で`make serve`を実行した際に以下のエラーが表示される場合
-
-```
-ERROR 2020/08/01 19:09:18 Error: listen tcp 127.0.0.1:1313: socket: too many open files
-make: *** [serve] Error 1
-```
-
-OS上で同時に開けるファイルの上限を確認してください。
-
-`launchctl limit maxfiles`
-
-続いて、以下のコマンドを実行します(https://gist.github.com/tombigel/d503800a282fcadbee14b537735d202c より引用)。
-
-```
-#!/bin/sh
-
-# These are the original gist links, linking to my gists now.
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxfiles.plist
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxproc.plist
-
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxfiles.plist
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxproc.plist
-
-sudo mv limit.maxfiles.plist /Library/LaunchDaemons
-sudo mv limit.maxproc.plist /Library/LaunchDaemons
-
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxfiles.plist
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxproc.plist
-
-sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist
-```
-
-こちらはmacOSのCatalinaとMojaveで動作を確認しています。
-
-## SIG Docsに参加する
-
-[コミュニティのページ](https://github.com/kubernetes/community/tree/master/sig-docs#meetings)をご覧になることで、SIG Docs Kubernetesコミュニティとの関わり方を学ぶことができます。
-
-本プロジェクトのメンテナーには以下の方法で連絡することができます:
-
-- [Slack](https://kubernetes.slack.com/messages/kubernetes-docs-ja)
-- [メーリングリスト](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-## ドキュメントに貢献する {#contributing-to-the-docs}
-
-GitHubの画面右上にある**Fork**ボタンをクリックすると、お使いのGitHubアカウントに紐付いた本リポジトリのコピーが作成され、このコピーのことを*フォーク*と呼びます。フォークリポジトリの中ではお好きなように変更を加えていただいて構いません。加えた変更をこのリポジトリに追加したい任意のタイミングにて、フォークリポジトリからPull Reqeustを作成してください。
-
-Pull Requestが作成されると、レビュー担当者が責任を持って明確かつ実用的なフィードバックを返します。Pull Requestの所有者は作成者であるため、**ご自身で作成したPull Requestを編集し、フィードバックに対応するのはご自身の役目です。**
-
-また、状況によっては2人以上のレビュアーからフィードバックが返されたり、アサインされていないレビュー担当者からのフィードバックが来ることがある点もご注意ください。
-
-さらに、特定のケースにおいては、レビュー担当者がKubernetesの技術的なレビュアーに対してレビューを依頼することもあります。レビュー担当者はタイムリーにフィードバックを提供するために最善を尽くしますが、応答時間は状況に応じて異なる場合があります。
-
-Kubernetesのドキュメントへの貢献に関する詳細については以下のページをご覧ください:
-
-* [Kubernetesのドキュメントへの貢献](https://kubernetes.io/ja/docs/contribute/)
-* [ページコンテントタイプ](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [ドキュメントのスタイルガイド](https://kubernetes.io/docs/contribute/style/style-guide/)
-* [Kubernetesドキュメントの翻訳方法](https://kubernetes.io/docs/contribute/localization/)
-
-### New Contributor Ambassadors
-
-コントリビュートする時に何か助けが必要なら、[New Contributor Ambassadors](https://kubernetes.io/docs/contribute/advanced/#serve-as-a-new-contributor-ambassador)に聞いてみると良いでしょう。彼らはSIG Docsのapproverで、最初の数回のPull Requestを通して新しいコントリビューターを指導し助けることを責務としています。New Contributors Ambassadorsにコンタクトするには、[Kubernetes Slack](https://slack.k8s.io)が最適な場所です。現在のSIG DocsのNew Contributor Ambassadorは次の通りです:
-
-| 名前                       | Slack                      | GitHub                     |                   
-| -------------------------- | -------------------------- | -------------------------- |
-| Arsh Sharma                | @arsh                      | @RinkiyaKeDad              |
-
-## 翻訳された`README.md`一覧 {#localization-readmemds}
-
-| Language  | Language |
-|---|---|
-|[中国語](README-zh.md)|[韓国語](README-ko.md)|
-|[フランス語](README-fr.md)|[ポーランド語](README-pl.md)|
-|[ドイツ語](README-de.md)|[ポルトガル語](README-pt.md)|
-|[ヒンディー語](README-hi.md)|[ロシア語](README-ru.md)|
-|[インドネシア語](README-id.md)|[スペイン語](README-es.md)|
-|[イタリア語](README-it.md)|[ウクライナ語](README-uk.md)|
-|[日本語](README-ja.md)|[ベトナム語](README-vi.md)|
-
-### 行動規範
-
-Kubernetesコミュニティへの参加については、[CNCFの行動規範](https://github.com/cncf/foundation/blob/master/code-of-conduct.md)によって管理されています。
-
-## ありがとうございます！
-
-Kubernetesはコミュニティの参加によって成長しています。Webサイトおよびドキュメンテーションへの皆さんの貢献に感謝します！

README-ko.md

@@ -1,144 +0,0 @@
-# 쿠버네티스 문서화
-
-[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-main-staging/deploys) [![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-이 저장소에는 [쿠버네티스 웹사이트 및 문서](https://kubernetes.io/)를 빌드하는 데 필요한 자산이 포함되어 있습니다. 기여해주셔서 감사합니다!
-
-# 저장소 사용하기
-
-Hugo(확장 버전)를 사용하여 웹사이트를 로컬에서 실행하거나, 컨테이너 런타임에서 실행할 수 있습니다. 라이브 웹사이트와의 배포 일관성을 제공하므로, 컨테이너 런타임을 사용하는 것을 적극 권장합니다.
-
-## 사전 준비 사항
-
-이 저장소를 사용하기 위해, 로컬에 다음의 소프트웨어들이 설치되어 있어야 합니다.
-
-- [npm](https://www.npmjs.com/)
-- [Go](https://golang.org/)
-- [Hugo(확장 버전)](https://gohugo.io/)
-- [도커](https://www.docker.com/)와 같은 컨테이너 런타임.
-
-시작하기 전에 의존성이 있는 소프트웨어를 설치합니다. 저장소를 복제(clone)하고 디렉터리로 이동합니다.
-
-```
-git clone https://github.com/kubernetes/website.git
-cd website
-```
-
-쿠버네티스 웹사이트는 [Docsy Hugo 테마](https://github.com/google/docsy#readme)를 사용합니다. 웹사이트를 컨테이너에서 실행하려는 경우에도, 다음을 실행하여 하위 모듈 및 기타 개발 종속성을 가져오는 것이 좋습니다.
-
-```
-# Docsy 하위 모듈 가져오기
-git submodule update --init --recursive --depth 1
-```
-
-## 컨테이너를 사용하여 웹사이트 실행하기
-
-컨테이너에서 사이트를 빌드하려면, 다음을 실행하여 컨테이너 이미지를 빌드하고 실행합니다.
-
-```
-make container-image
-make container-serve
-```
-
-웹사이트를 보려면 브라우저를 http://localhost:1313 으로 엽니다. 소스 파일을 변경하면 Hugo가 웹사이트를 업데이트하고 브라우저를 강제로 새로 고칩니다.
-
-## Hugo를 사용하여 로컬에서 웹사이트 실행하기
-
-[`netlify.toml`](netlify.toml#L10) 파일의 `HUGO_VERSION` 환경 변수에 지정된 Hugo 확장 버전을 설치해야 합니다.
-
-사이트를 로컬에서 빌드하고 테스트하려면, 다음을 실행합니다.
-
-```bash
-# 의존성 있는 소프트웨어 설치
-npm ci
-make serve
-```
-
-그러면 포트 1313에서 로컬 Hugo 서버가 시작됩니다. 웹사이트를 보려면 http://localhost:1313 으로 브라우저를 엽니다. 소스 파일을 변경하면, Hugo가 웹사이트를 업데이트하고 브라우저를 강제로 새로 고칩니다.
-
-## 문제 해결
-### error: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): this feature is not available in your current Hugo version
-
-Hugo는 기술적인 이유로 2개의 바이너리 세트로 제공됩니다. 현재 웹사이트는 **Hugo 확장** 버전 기반에서만 실행됩니다. [릴리스 페이지](https://github.com/gohugoio/hugo/releases)에서 이름에 `extended` 가 포함된 아카이브를 찾습니다. 확인하려면, `hugo version` 을 실행하고 `extended` 라는 단어를 찾습니다.
-
-### too many open files 이슈에 대한 macOS 문제 해결
-
-macOS에서 `make serve` 를 실행하면 다음의 오류 메시지가 출력됩니다.
-
-```
-ERROR 2020/08/01 19:09:18 Error: listen tcp 127.0.0.1:1313: socket: too many open files
-make: *** [serve] Error 1
-```
-
-파일 오픈 개수에 대한 현재 제한값을 확인합니다.
-
-`launchctl limit maxfiles`
-
-그리고 다음의 명령을 실행합니다(https://gist.github.com/tombigel/d503800a282fcadbee14b537735d202c 를 참고하여 적용).
-
-```
-#!/bin/sh
-
-# 코멘트 처리한 것은 원래 gist 링크들이며, 그 아래는 수정된 tombigel의 gist 링크입니다.
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxfiles.plist
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxproc.plist
-
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxfiles.plist
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxproc.plist
-
-sudo mv limit.maxfiles.plist /Library/LaunchDaemons
-sudo mv limit.maxproc.plist /Library/LaunchDaemons
-
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxfiles.plist
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxproc.plist
-
-sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist
-```
-
-이 내용은 Catalina와 Mojave macOS에서 작동합니다.
-
-
-# SIG Docs에 참여하기
-
-[커뮤니티 페이지](https://github.com/kubernetes/community/tree/master/sig-docs#meetings)에서 SIG Docs 쿠버네티스 커뮤니티 및 회의에 대한 자세한 내용을 확인합니다.
-
-이 프로젝트의 메인테이너에게 연락을 할 수도 있습니다.
-
-- [슬랙](https://kubernetes.slack.com/messages/sig-docs) [슬랙에 초대 받기](https://slack.k8s.io/)
-- [메일링 리스트](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-# 문서에 기여하기
-
-이 저장소에 대한 복제본을 여러분의 GitHub 계정에 생성하기 위해 화면 오른쪽 위 영역에 있는 **Fork** 버튼을 클릭하면 됩니다. 이 복제본은 *fork* 라고 부릅니다. 여러분의 fork에서 원하는 임의의 변경 사항을 만들고, 해당 변경 사항을 보낼 준비가 되었다면, 여러분의 fork로 이동하여 새로운 풀 리퀘스트를 만들어 우리에게 알려주시기 바랍니다.
-
-여러분의 풀 리퀘스트가 생성된 이후에는, 쿠버네티스 리뷰어가 명료하고 실행 가능한 피드백을 제공하는 책임을 담당할 것입니다. 풀 리퀘스트의 오너로서, **쿠버네티스 리뷰어로부터 제공받은 피드백을 수용하기 위해 풀 리퀘스트를 수정하는 것은 여러분의 책임입니다.**
-
-또한, 참고로 한 명 이상의 쿠버네티스 리뷰어가 여러분에게 피드백을 제공하는 상황이거나, 또는 원래 여러분에게 피드백을 제공하기로 할당된 사람이 아닌 다른 쿠버네티스 리뷰어로부터 피드백을 받는 상황도 있습니다.
-
-그뿐만 아니라, 몇몇 상황에서는, 필요에 따라 리뷰어 중 한 명이 [쿠버네티스 기술 리뷰어](https://github.com/kubernetes/website/wiki/Tech-reviewers)로부터의 기술 리뷰를 요청할지도 모릅니다. 리뷰어는 제시간에 피드백을 제공하기 위해 최선을 다할 것이지만, 응답 시간은 상황에 따라 달라질 수도 있습니다.
-
-쿠버네티스 문서화에 기여하기와 관련된 보다 자세한 정보는, 다음을 참고합니다.
-
-* [쿠버네티스 문서에 기여하기](https://kubernetes.io/docs/contribute/)
-* [페이지 콘텐트 타입](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [문서화 스타일 가이드](http://kubernetes.io/docs/contribute/style/style-guide/)
-* [쿠버네티스 문서 현지화](https://kubernetes.io/docs/contribute/localization/)
-
-# `README.md`에 대한 쿠버네티스 문서 현지화(localization)
-
-## 한국어
-
-`README.md` 번역 및 한국어 기여자를 위한 보다 자세한 가이드는 [쿠버네티스 문서 한글화 가이드](https://kubernetes.io/ko/docs/contribute/localization_ko/)를 참고합니다.
-
-한국어 번역 메인테이너에게 다음을 통해 연락할 수 있습니다.
-
-* 손석호 ([GitHub - @seokho-son](https://github.com/seokho-son))
-* [슬랙 채널](https://kubernetes.slack.com/messages/kubernetes-docs-ko)
-
-# 행동 강령
-
-쿠버네티스 커뮤니티 참여는 [CNCF 행동 강령](https://github.com/cncf/foundation/blob/master/code-of-conduct-languages/ko.md)을 따릅니다.
-
-# 감사합니다!
-
-쿠버네티스는 커뮤니티 참여를 통해 번창하며, 우리는 웹사이트 및 문서화에 대한 당신의 기여에 감사드립니다!

README-pl.md

@@ -1,155 +0,0 @@
-# Dokumentacja projektu Kubernetes
-
-[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-main-staging/deploys) [![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-W tym repozytorium znajdziesz wszystko, czego potrzebujesz do zbudowania [strony internetowej Kubernetesa wraz z dokumentacją](https://kubernetes.io/). Bardzo nam miło, że chcesz wziąć udział w jej współtworzeniu!
-
-+ [Twój wkład w dokumentację](#twój-wkład-w-dokumentację)
-+ [Informacje o wersjach językowych](#różne-wersje-językowe-readmemd)
-
-## Jak używać tego repozytorium
-
-Możesz uruchomić serwis lokalnie poprzez Hugo (Extended version) lub ze środowiska kontenerowego. Zdecydowanie zalecamy korzystanie z kontenerów, bo dzięki temu lokalna wersja będzie spójna z tym, co jest na oficjalnej stronie.
-
-## Wymagania wstępne
-
-Aby móc skorzystać z tego repozytorium, musisz lokalnie zainstalować:
-
-- [npm](https://www.npmjs.com/)
-- [Go](https://golang.org/)
-- [Hugo (Extended version)](https://gohugo.io/)
-- Środowisko obsługi kontenerów, np. [Dockera](https://www.docker.com/).
-
-Przed rozpoczęciem zainstaluj niezbędne zależności. Sklonuj repozytorium i przejdź do odpowiedniego katalogu:
-
-```bash
-git clone https://github.com/kubernetes/website.git
-cd website
-```
-
-Strona Kubernetesa używa [Docsy Hugo theme](https://github.com/google/docsy#readme). Nawet jeśli planujesz uruchomić serwis w środowisku kontenerowym, zalecamy pobranie podmodułów i innych zależności za pomocą polecenia:
-
-```bash
-# pull in the Docsy submodule
-git submodule update --init --recursive --depth 1
-```
-
-## Uruchomienie serwisu w kontenerze
-
-Aby zbudować i uruchomić serwis wewnątrz środowiska kontenerowego, wykonaj następujące polecenia:
-
-```bash
-make container-image
-make container-serve
-```
-
-Jeśli widzisz błędy, prawdopodobnie kontener z Hugo nie dysponuje wystarczającymi zasobami. Aby rozwiązać ten problem, zwiększ ilość dostępnych zasobów CPU i pamięci dla Dockera na Twojej maszynie ([MacOSX](https://docs.docker.com/docker-for-mac/#resources) i [Windows](https://docs.docker.com/docker-for-windows/#resources)).
-
-Aby obejrzeć zawartość serwisu, otwórz w przeglądarce adres <http://localhost:1313>. Po każdej zmianie plików źródłowych, Hugo automatycznie aktualizuje stronę i odświeża jej widok w przeglądarce.
-
-## Jak uruchomić lokalną kopię strony przy pomocy Hugo?
-
-Upewnij się, że zainstalowałeś odpowiednią wersję Hugo "extended", określoną przez zmienną środowiskową `HUGO_VERSION` w pliku [`netlify.toml`](netlify.toml#L10).
-
-Aby uruchomić i przetestować serwis lokalnie, wykonaj:
-
-```bash
-# install dependencies
-npm ci
-make serve
-```
-
-Zostanie uruchomiony lokalny serwer Hugo na porcie 1313. Otwórz w przeglądarce adres <http://localhost:1313>, aby obejrzeć zawartość serwisu. Po każdej zmianie plików źródłowych, Hugo automatycznie aktualizuje stronę i odświeża jej widok w przeglądarce.
-
-## Budowanie dokumentacji źródłowej API
-
-Budowanie dokumentacji źródłowej API zostało opisane w [angielskiej wersji pliku README.md](README.md#building-the-api-reference-pages).
-
-## Rozwiązywanie problemów
-
-### error: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): this feature is not available in your current Hugo version
-
-Z przyczyn technicznych, Hugo jest rozprowadzany w dwóch wersjach. Aktualny serwis używa tylko wersji **Hugo Extended**. Na stronie z [wydaniami](https://github.com/gohugoio/hugo/releases) poszukaj archiwum z `extended` w nazwie. Dla potwierdzenia, uruchom `hugo version` i poszukaj słowa `extended`.
-
-### Błąd w środowisku macOS: "too many open files"
-
-Jeśli po uruchomieniu `make serve` na macOS widzisz następujący błąd:
-
-```bash
-ERROR 2020/08/01 19:09:18 Error: listen tcp 127.0.0.1:1313: socket: too many open files
-make: *** [serve] Error 1
-```
-
-sprawdź aktualny limit otwartych plików:
-
-`launchctl limit maxfiles`
-
-Uruchom następujące polecenia: (na podstawie https://gist.github.com/tombigel/d503800a282fcadbee14b537735d202c):
-
-```shell
-#!/bin/sh
-
-# These are the original gist links, linking to my gists now.
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxfiles.plist
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxproc.plist
-
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxfiles.plist
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxproc.plist
-
-sudo mv limit.maxfiles.plist /Library/LaunchDaemons
-sudo mv limit.maxproc.plist /Library/LaunchDaemons
-
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxfiles.plist
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxproc.plist
-
-sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist
-```
-
-Przedstawiony sposób powinien działać dla MacOS w wersjach Catalina i Mojave.
-
-## Zaangażowanie w prace SIG Docs
-
-O społeczności SIG Docs i terminach spotkań dowiesz z [jej strony](https://github.com/kubernetes/community/tree/master/sig-docs#meetings).
-
-Możesz kontaktować się z gospodarzami projektu za pomocą:
-
-- [Komunikatora Slack](https://kubernetes.slack.com/messages/sig-docs)
-  - [Tutaj możesz dostać zaproszenie do tej grupy Slacka](https://slack.k8s.io/)
-- [List dyskusyjnych](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-## Twój wkład w dokumentację
-
-Możesz kliknąć w przycisk **Fork** w prawym górnym rogu ekranu, aby stworzyć kopię tego repozytorium na swoim koncie GitHub. Taki rodzaj kopii (odgałęzienia) nazywa się *fork*. Zmieniaj w nim, co chcesz, a kiedy będziesz już gotowy/a przesłać te zmiany do nas, przejdź do swojej kopii i stwórz nowy *pull request*, abyśmy zostali o tym poinformowani.
-
-Po stworzeniu *pull request*, jeden z recenzentów projektu Kubernetes podejmie się przekazania jasnych wskazówek pozwalających podjąć następne działania. Na Tobie, jako właścicielu *pull requesta*, **spoczywa odpowiedzialność za wprowadzenie poprawek zgodnie z uwagami recenzenta.**
-
-Może też się zdarzyć, że swoje uwagi zgłosi więcej niż jeden recenzent, lub że recenzję będzie robił ktoś inny, niż ten, kto został przydzielony na początku.
-
-W niektórych przypadkach, jeśli zajdzie taka potrzeba, recenzent może poprosić dodatkowo o recenzję jednego z recenzentów technicznych. Recenzenci zrobią wszystko, aby odpowiedzieć sprawnie, ale konkretny czas odpowiedzi zależy od wielu czynników.
-
-Więcej informacji na temat współpracy przy tworzeniu dokumentacji znajdziesz na stronach:
-
-- [Udział w rozwijaniu dokumentacji](https://kubernetes.io/docs/contribute/)
-- [Rodzaje stron](https://kubernetes.io/docs/contribute/style/page-content-types/)
-- [Styl pisania dokumentacji](http://kubernetes.io/docs/contribute/style/style-guide/)
-- [Lokalizacja dokumentacji Kubernetesa](https://kubernetes.io/docs/contribute/localization/)
-
-## Różne wersje językowe `README.md`
-
-| Język  | Język |
-|---|---|
-| [angielski](README.md)       | [francuski](README-fr.md)    |
-| [koreański](README-ko.md)    | [niemiecki](README-de.md)    |
-| [portugalski](README-pt.md)  | [hindi](README-hi.md)        |
-| [hiszpański](README-es.md)   | [indonezyjski](README-id.md) |
-| [chiński](README-zh.md)      | [japoński](README-ja.md)     |
-| [wietnamski](README-vi.md)   | [rosyjski](README-ru.md)     |
-| [włoski](README-it.md)       | [ukraiński](README-uk.md)    |
-
-## Zasady postępowania
-
-Udział w działaniach społeczności Kubernetesa jest regulowany przez [Kodeks postępowania CNCF](https://github.com/cncf/foundation/blob/master/code-of-conduct-languages/pl.md).
-
-## Dziękujemy!
-
-Kubernetes rozkwita dzięki zaangażowaniu społeczności — doceniamy twój wkład w tworzenie naszego serwisu i dokumentacji!

README-pt.md

@@ -1,193 +0,0 @@
-# A documentação do Kubernetes
-
-[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-main-staging/deploys) [![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-Bem-vindos! Este repositório contém todos os recursos necessários para criar o [website e documentação do Kubernetes](https://kubernetes.io/). Estamos muito satisfeitos por você querer contribuir!
-
-# Utilizando este repositório
-
-Você pode executar o website localmente utilizando o Hugo (versão Extended), ou você pode executa-ló em um container runtime. É altamente recomendável utilizar um container runtime, pois garante a consistência na implantação do website real.
-
-## Pré-requisitos
-
-Para usar este repositório, você precisa instalar:
-
-- [npm](https://www.npmjs.com/)
-- [Go](https://golang.org/)
-- [Hugo (versão Extended)](https://gohugo.io/)
-- Um container runtime, por exemplo [Docker](https://www.docker.com/).
-
-Antes de você iniciar, instale as dependências, clone o repositório e navegue até o diretório:
-
-```
-git clone https://github.com/kubernetes/website.git
-cd website
-```
-
-O website do Kubernetes utiliza o [tema Docsy Hugo](https://github.com/google/docsy#readme). Mesmo se você planeje executar o website em um container, é altamente recomendado baixar os submódulos e outras dependências executando o seguinte comando:
-
-```
-# Baixar o submódulo Docsy
-git submodule update --init --recursive --depth 1
-```
-
-## Executando o website usando um container
-
-Para executar o build do website em um container, execute o comando abaixo para criar a imagem do container e executa-lá:
-
-```
-make container-image
-make container-serve
-```
-
-Abra seu navegador em http://localhost:1313 para visualizar o website. Conforme você faz alterações nos arquivos fontes, o Hugo atualiza o website e força a atualização do navegador.
-
-## Executando o website localmente utilizando o Hugo
-
-Consulte 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 build e testar o website localmente, execute:
-
-```bash
-# instalar dependências
-npm ci
-make serve
-```
-
-Isso iniciará localmente o Hugo na porta 1313. Abra o seu navegador em http://localhost:1313 para visualizar o website. Conforme você faz alterações nos arquivos fontes, o Hugo atualiza o website e força uma atualização no navegador.
-
-## Construindo a página de referência da API
-
-A página de referência da API localizada em `content/en/docs/reference/kubernetes-api` é construída a partir da especificação do Swagger utilizando https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs.
-
-Siga os passos abaixo para atualizar a página de referência para uma nova versão do Kubernetes:
-
-OBS: modifique o "v1.20" no exemplo a seguir pela versão a ser atualizada
-
-1. Obter o submódulo `kubernetes-resources-reference`:
-
-```
-git submodule update --init --recursive --depth 1
-```
-
-2. Criar a nova versão da API no submódulo e adicionar à especificação do Swagger:
-
-```
-mkdir api-ref-generator/gen-resourcesdocs/api/v1.20
-curl 'https://raw.githubusercontent.com/kubernetes/kubernetes/master/api/openapi-spec/swagger.json' > api-ref-generator/gen-resourcesdocs/api/v1.20/swagger.json
-```
-
-3. Copiar o sumário e os campos de configuração para a nova versão a partir da versão anterior:
-
-```
-mkdir api-ref-generator/gen-resourcesdocs/api/v1.20
-cp api-ref-generator/gen-resourcesdocs/api/v1.19/* api-ref-generator/gen-resourcesdocs/api/v1.20/
-```
-
-4. Ajustar os arquivos `toc.yaml` e `fields.yaml` para refletir as mudanças entre as duas versões.
-
-5. Em seguida, gerar as páginas:
-
-```
-make api-reference
-```
-
-Você pode validar o resultado localmente gerando e disponibilizando o site a partir da imagem do container:
-
-```
-make container-image
-make container-serve
-```
-
-Abra o seu navegador em http://localhost:1313/docs/reference/kubernetes-api/ para visualizar a página de referência da API.
-
-6. Quando todas as mudanças forem refletidas nos arquivos de configuração `toc.yaml` e `fields.yaml`, crie um pull request com a nova página de referência de API.
-
-## Troubleshooting
-### error: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): this feature is not available in your current Hugo version
-
-Por motivos técnicos, o Hugo é disponibilizado em dois conjuntos de binários. O website atual funciona apenas na versão **Hugo Extended**. Na [página de releases](https://github.com/gohugoio/hugo/releases) procure por arquivos com `extended` no nome. Para confirmar, execute `hugo version` e procure pela palavra `extended`.
-
-### Troubleshooting macOS for too many open files
-
-Se você executar o comando `make serve` no macOS e retornar o seguinte erro:
-
-```
-ERROR 2020/08/01 19:09:18 Error: listen tcp 127.0.0.1:1313: socket: too many open files
-make: *** [serve] Error 1
-```
-
-Verifique o limite atual para arquivos abertos:
-
-`launchctl limit maxfiles`
-
-Em seguida, execute os seguintes comandos (adaptado de https://gist.github.com/tombigel/d503800a282fcadbee14b537735d202c):
-
-```shell
-#!/bin/sh
-
-# Esse são os links do gist original, vinculados ao meu gists agora.
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxfiles.plist
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxproc.plist
-
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxfiles.plist
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxproc.plist
-
-sudo mv limit.maxfiles.plist /Library/LaunchDaemons
-sudo mv limit.maxproc.plist /Library/LaunchDaemons
-
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxfiles.plist
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxproc.plist
-
-sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist
-```
-
-Esta solução funciona tanto para o MacOS Catalina quanto para o MacOS Mojave.
-
-### Erro de "Out of Memory"
-
-Se você executar o comando `make container-serve` e retornar o seguinte erro:
-```
-make: *** [container-serve] Error 137
-```
-
-Verifique a quantidade de memória disponível para o agente de execução de contêiner. No caso do Docker Desktop para macOS, abra o menu "Preferences..." -> "Resources..." e tente disponibilizar mais memória.
-
-# Comunidade, discussão, contribuição e apoio
-
-Saiba mais sobre a comunidade Kubernetes SIG Docs e reuniões na [página da comunidade](http://kubernetes.io/community/).
-
-Você também pode entrar em contato com os mantenedores deste projeto em:
-
-- [Slack](https://kubernetes.slack.com/messages/sig-docs) ([Obter o convide para o este slack](https://slack.k8s.io/))
-- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-# 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 um novo **pull request** para nos informar sobre isso.
-
-Depois que seu **pull request** for criado, um revisor do Kubernetes assumirá a responsabilidade de fornecer um feedback claro e objetivo. Como proprietário do pull request, **é sua responsabilidade modificar seu pull request para atender ao 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 outro revisor do Kubernetes diferente daquele originalmente designado para lhe fornecer o feedback.
-
-Além disso, em alguns casos, um de seus revisores pode solicitar uma revisão técnica de um [revisor técnico do Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) quando necessário. Os revisores farão o melhor para fornecer feedbacks 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:
-
-* [Contribua com a documentação do Kubernetes](https://kubernetes.io/docs/contribute/)
-* [Tipos de conteúdo de página](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [Guia de Estilo da Documentação](http://kubernetes.io/docs/contribute/style/style-guide/)
-* [Localizando documentação do Kubernetes](https://kubernetes.io/docs/contribute/localization/)
-
-Você pode contatar os mantenedores da localização em Português em:
-
-* Felipe ([GitHub - @femrtnz](https://github.com/femrtnz))
-* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-pt)
-
-# Código de conduta
-
-A participação na comunidade Kubernetes é regida pelo [Código de Conduta da Kubernetes](code-of-conduct.md).
-
-# Obrigado!
-
-O Kubernetes prospera com a participação da comunidade e nós realmente agradecemos suas contribuições para o nosso website e nossa documentação!

README-ru.md

@@ -1,142 +0,0 @@
-# Документация по Kubernetes
-
-[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-main-staging/deploys) [![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-Данный репозиторий содержит все необходимые файлы для сборки [сайта Kubernetes и документации](https://kubernetes.io/). Мы благодарим вас за желание внести свой вклад!
-
-# Использование этого репозитория
-
-Запустить сайт локально можно с помощью Hugo (Extended version) или же в исполняемой среде для контейнеров. Мы настоятельно рекомендуем воспользоваться контейнерной средой, поскольку она обеспечивает консистивность развёртывания с оригинальным сайтом.
-
-## Предварительные требования
-
-Чтобы работать с этим репозиторием, понадобятся следующие компоненты, установленные локально:
-
-- [npm](https://www.npmjs.com/)
-- [Go](https://golang.org/)
-- [Hugo (Extended version)](https://gohugo.io/)
-- Исполняемая среда для контейнеров вроде [Docker](https://www.docker.com/)
-
-Перед тем, как начать, установите зависимости. Склонируйте репозиторий и перейдите в его директорию:
-
-```
-git clone https://github.com/kubernetes/website.git
-cd website
-```
-
-Сайт Kubernetes использует [тему для Hugo под названием Docsy](https://github.com/google/docsy). Даже если вы планируете запускать сайт в контейнере, мы настоятельно рекомендуем загрузить соответствующий подмодуль и другие зависимости для разработки, выполнив следующую команду:
-
-```
-# загружаем Git-подмодуль Docsy
-git submodule update --init --recursive --depth 1
-```
-
-## Запуск сайта в контейнере
-
-Чтобы собрать сайт в контейнере, выполните следующие команды — они собирают образ контейнера и запускают его:
-
-```
-make container-image
-make container-serve
-```
-
-Откройте браузер и перейдите по ссылке http://localhost:1313, чтобы увидеть сайт. Если вы отредактируете исходные файлы сайта, Hugo автоматически обновит сам сайт и выполнит обновление страницы в браузере.
- 
-## Запуск сайта с помощью Hugo
-
-Убедитесь, что вы установили расширенную версию Hugo (extended version): она определена в переменной окружения `HUGO_VERSION` в файле [`netlify.toml`](netlify.toml#L10).
-
-Чтобы собрать и протестировать сайт локально, выполните:
-
-```bash
-# install dependencies
-npm ci
-make serve
-```
-
-Эти команды запустят локальный сервер Hugo на порту 1313. Откройте браузер и перейдите по ссылке http://localhost:1313, чтобы увидеть сайт. Если вы отредактируете исходные файлы сайта, Hugo автоматически обновит сам сайт и выполнит обновление страницы в браузере.
-
-## Решение проблем
-### error: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): this feature is not available in your current Hugo version
-
-По техническим причинам Hugo поставляется с двумя наборами бинарников. Текущий сайт Kubernetes работает только в версии **Hugo Extended**. На [странице релизов](https://github.com/gohugoio/hugo/releases) ищите архивы со словом `extended` в названии. Чтобы убедиться в корректности, запустите команду `hugo version` и найдите в выводе слово `extended`.
-
-### Решение проблемы на macOS с "too many open files"
-
-Если вы запускаете `make serve` на macOS и получаете следующую ошибку:
-
-```
-ERROR 2020/08/01 19:09:18 Error: listen tcp 127.0.0.1:1313: socket: too many open files
-make: *** [serve] Error 1
-```
-
-Попробуйте проверить текущий лимит для открытых файлов:
-
-`launchctl limit maxfiles`
-
-Затем выполните следующие команды (они взяты и адаптированы из https://gist.github.com/tombigel/d503800a282fcadbee14b537735d202c):
-
-```shell
-#!/bin/sh
-
-# Ссылки на оригинальные gist-файлы закомментированы в пользу моих адаптированных.
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxfiles.plist
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxproc.plist
-
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxfiles.plist
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxproc.plist
-
-sudo mv limit.maxfiles.plist /Library/LaunchDaemons
-sudo mv limit.maxproc.plist /Library/LaunchDaemons
-
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxfiles.plist
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxproc.plist
-
-sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist
-```
-
-Данное решение работает для macOS Catalina и Mojave.
-
-# Участие в SIG Docs
-
-Узнайте о Kubernetes-сообществе SIG Docs и его встречах на [странице сообщества](https://github.com/kubernetes/community/tree/master/sig-docs#meetings).
-
-Вы можете связаться с сопровождающими этот проект по следующим ссылкам:
-
-- [Канал в Slack](https://kubernetes.slack.com/messages/sig-docs) ([получите приглашение в этот Slack](https://slack.k8s.io/))
-- [Почтовая рассылка](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-# Вклад в документацию
-
-Нажмите на кнопку **Fork** в правом верхнем углу, чтобы создать копию этого репозитория для вашего GitHub-аккаунта. Эта копия называется *форк-репозиторием*. Делайте любые изменения в своем форк-репозитории и, когда будете готовы опубликовать изменения, зайдите в свой форк-репозиторий и создайте новый pull-запрос (PR), чтобы уведомить нас.
-
-После того, как вы отправите pull-запрос, ревьювер из проекта Kubernetes даст по нему обратную связь. Вы, как автор pull-запроса, **должны обновить свой PR после его рассмотрения ревьювером Kubernetes.**
-
-Вполне возможно, что более одного ревьювера Kubernetes оставят свои комментарии. Может быть даже так, что вы будете получать обратную связь уже не от того ревьювера, что был первоначально вам назначен. Кроме того, в некоторых случаях один из ревьюверов может запросить техническую рецензию от [технического ревьювера Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers), если это потребуется. Ревьюверы сделают все возможное, чтобы как можно оперативнее оставить свои предложения и пожелания, но время ответа может варьироваться в зависимости от обстоятельств.
-
-Узнать подробнее о том, как поучаствовать в документации Kubernetes, вы можете по ссылкам ниже:
-
-* [Начните вносить свой вклад](https://kubernetes.io/docs/contribute/)
-* [Использование шаблонов страниц](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [Руководство по оформлению документации](https://kubernetes.io/docs/contribute/style/style-guide/)
-* [Руководство по локализации Kubernetes](https://kubernetes.io/docs/contribute/localization/)
-
-# Файл `README.md` на других языках
-
-|           другие языки        |       другие языки            |
-|-------------------------------|-------------------------------|
-| [Английский](README.md)       | [Немецкий](README-de.md)      |
-| [Вьетнамский](README-vi.md)   | [Польский]( README-pl.md)     |
-| [Индонезийский](README-id.md) | [Португальский](README-pt.md) |
-| [Испанский](README-es.md)     | [Украинский](README-uk.md)    |
-| [Итальянский](README-it.md)   | [Французский](README-fr.md)   |
-| [Китайский](README-zh.md)     | [Хинди](README-hi.md)         |
-| [Корейский](README-ko.md)     | [Японский](README-ja.md)      |
-
-# Кодекс поведения
-
-Участие в сообществе Kubernetes регулируется [кодексом поведения CNCF](https://github.com/cncf/foundation/blob/master/code-of-conduct-languages/ru.md).
-
-# Спасибо!
-
-Kubernetes процветает благодаря сообществу и мы ценим ваш вклад в сайт и документацию!

README-uk.md

@@ -1,86 +0,0 @@
-<!-- # The Kubernetes documentation -->
-# Документація Kubernetes
-
-[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-main-staging/deploys) [![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-<!-- This repository contains the assets required to build the [Kubernetes website and documentation](https://kubernetes.io/). We're glad that you want to contribute! -->
-Вітаємо! В цьому репозиторії міститься все необхідне для роботи над [сайтом і документацією Kubernetes](https://kubernetes.io/). Ми щасливі, що ви хочете зробити свій внесок!
-
-<!-- ## Running the website locally using Hugo -->
-## Запуск сайту локально зa допомогою Hugo
-
-<!-- See the [official Hugo documentation](https://gohugo.io/getting-started/installing/) for Hugo installation instructions. Make sure to install the Hugo extended version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L10) file. -->
-Для інструкцій з встановлення Hugo дивіться [офіційну документацію](https://gohugo.io/getting-started/installing/). Обов’язково встановіть розширену версію Hugo, яка позначена змінною оточення `HUGO_VERSION` у файлі [`netlify.toml`](netlify.toml#L10).
-
-<!-- To run the website locally when you have Hugo installed: -->
-Після встановлення Hugo, запустіть сайт локально командою:
-
-```bash
-git clone https://github.com/kubernetes/website.git
-cd website
-git submodule update --init --recursive --depth 1
-make serve
-```
-
-<!-- This will start the local Hugo server on port 1313. Open up your browser to http://localhost:1313 to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh. -->
-Команда запустить локальний Hugo-сервер на порту 1313. Відкрийте у своєму браузері http://localhost:1313, щоб побачити сайт. По мірі того, як ви змінюєте вихідний код, Hugo актуалізує сайт відповідно до внесених змін і оновлює сторінку у браузері.
-
-<!-- ## Get involved with SIG Docs -->
-## Спільнота, обговорення, внесок і підтримка
-
-<!-- Learn more about SIG Docs Kubernetes community and meetings on the [community page](https://github.com/kubernetes/community/tree/master/sig-docs#meetings). -->
-Дізнайтеся, як долучитися до спільноти Kubernetes на [сторінці спільноти](http://kubernetes.io/community/).
-
-<!-- You can also reach the maintainers of this project at: -->
-Для зв’язку із супроводжуючими проекту скористайтеся:
-
-- [Slack](https://kubernetes.slack.com/messages/sig-docs)
-- [Поштова розсилка](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-<!-- ## Contributing to the docs -->
-## Внесок у документацію
-
-<!-- You can click the **Fork** button in the upper-right area of the screen to create a copy of this repository in your GitHub account. This copy is called a *fork*. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it. -->
-Ви можете створити копію цього репозиторія у своєму акаунті на GitHub, натиснувши на кнопку **Fork**, що розташована справа зверху. Ця копія називатиметься *fork* (відгалуження). Зробіть будь-які необхідні зміни у своєму відгалуженні. Коли ви будете готові надіслати їх нам, перейдіть до свого відгалуження і створіть новий pull request, щоб сповістити нас.
-
-<!-- Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback.  As the owner of the pull request, **it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer.** -->
-Після того, як ви створили pull request, рецензент Kubernetes зобов’язується надати вам по ньому чіткий і конструктивний коментар. **Ваш обов’язок як творця pull request - відкоригувати його відповідно до зауважень рецензента Kubernetes.**
-
-<!-- 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. -->
-Також, зауважте: може статися так, що ви отримаєте коментарі від декількох рецензентів Kubernetes або від іншого рецензента, ніж той, якого вам було призначено від початку.
-
-<!-- Furthermore, in some cases, one of your reviewers might ask for a technical review from a Kubernetes tech reviewer when needed.  Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances. -->
-Крім того, за потреби один із ваших рецензентів може запросити технічну перевірку від одного з технічних рецензентів Kubernetes, коли це необхідно. Рецензенти намагатимуться відреагувати вчасно, проте час відповіді може відрізнятися в залежності від обставин.
-
-<!-- For more information about contributing to the Kubernetes documentation, see: -->
-Більше інформації про внесок у документацію Kubernetes ви знайдете у наступних джерелах:
-
-* [Внесок: з чого почати](https://kubernetes.io/docs/contribute/)
-* [Використання шаблонів сторінок](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [Керівництво зі стилю оформлення документації](http://kubernetes.io/docs/contribute/style/style-guide/)
-* [Переклад документації Kubernetes іншими мовами](https://kubernetes.io/docs/contribute/localization/)
-
-<!-- ## Localization `README.md`'s -->
-## Файл `README.md` іншими мовами
-
-| інші мови  | інші мови |
-|-------------------------------|-------------------------------|
-| [Англійська](README.md)       | [Французька](README-fr.md)    |
-| [Корейська](README-ko.md)     | [Німецька](README-de.md)      |
-| [Португальська](README-pt.md) | [Хінді](README-hi.md)         |
-| [Іспанська](README-es.md)     | [Індонезійська](README-id.md) |
-| [Китайська](README-zh.md)     | [Японська](README-ja.md)      |
-| [В'єтнамська](README-vi.md)   | [Російська](README-ru.md)     |
-| [Італійська](README-it.md)    | [Польська](README-pl.md)      |
-
-<!-- ## Code of conduct -->
-## Кодекс поведінки
-
-<!-- Participation in the Kubernetes community is governed by the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). -->
-Участь у спільноті Kubernetes визначається правилами [Кодексу поведінки СNCF](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
-
-<!-- ## Thank you! -->
-## Дякуємо!
-
-<!-- Kubernetes thrives on community participation, and we appreciate your contributions to our website and our documentation! -->
-Долучення до спільноти - запорука успішного розвитку Kubernetes. Ми цінуємо ваш внесок у наш сайт і документацію!

README-vi.md

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

README-zh.md

@@ -1,259 +0,0 @@
-# Kubernetes 文档
-
-<!--
-# The Kubernetes documentation
--->
-
-[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-main-staging/deploys) [![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
-
-<!--
-This repository contains the assets required to build the [Kubernetes website and documentation](https://kubernetes.io/). We're glad that you want to contribute!
--->
-本仓库包含了所有用于构建 [Kubernetes 网站和文档](https://kubernetes.io/) 的软件资产。
-我们非常高兴您想要参与贡献！
-
-<!--
-# Using this repository
-
-You can run the website locally using Hugo (Extended version), or you can run it in a container runtime. We strongly recommend using the container runtime, as it gives deployment consistency with the live website.
--->
-## 使用这个仓库
-
-可以使用 Hugo（扩展版）在本地运行网站，也可以在容器中运行它。强烈建议使用容器，因为这样可以和在线网站的部署保持一致。
-
-<!--
-## Prerequisites
-
-To use this repository, you need the following installed locally:
-
-- [npm](https://www.npmjs.com/)
-- [Go](https://golang.org/)
-- [Hugo (Extended version)](https://gohugo.io/)
-- A container runtime, like [Docker](https://www.docker.com/).
-
--->
-## 前提条件
-
-使用这个仓库，需要在本地安装以下软件：
-
-- [npm](https://www.npmjs.com/)
-- [Go](https://golang.org/)
-- [Hugo (Extended version)](https://gohugo.io/)
-- 容器运行时，比如 [Docker](https://www.docker.com/).
-
-<!--
-Before you start, install the dependencies. Clone the repository and navigate to the directory:
--->
-开始前，先安装这些依赖。克隆本仓库并进入对应目录：
-
-```
-git clone https://github.com/kubernetes/website.git
-cd website
-```
-
-<!--
-The Kubernetes website uses the [Docsy Hugo theme](https://github.com/google/docsy#readme). Even if you plan to run the website in a container, we strongly recommend pulling in the submodule and other development dependencies by running the following:
--->
-
-Kubernetes 网站使用的是 [Docsy Hugo 主题](https://github.com/google/docsy#readme)。 即使你打算在容器中运行网站，我们也强烈建议你通过运行以下命令来引入子模块和其他开发依赖项：
-
-```
-# pull in the Docsy submodule
-git submodule update --init --recursive --depth 1
-```
-
-<!--
-## Running the website using a container
-
-To build the site in a container, run the following to build the container image and run it:
-
--->
-## 在容器中运行网站
-
-要在容器中构建网站，请通过以下命令来构建容器镜像并运行：
-
-```
-make container-image
-make container-serve
-```
-
-<!--
-Open up your browser to http://localhost:1313 to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
--->
-启动浏览器，打开 http://localhost:1313 来查看网站。
-当你对源文件作出修改时，Hugo 会更新网站并强制浏览器执行刷新操作。
-
-<!--
-## Running the website locally using Hugo
-
-Make sure to install the Hugo extended version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L10) file.
-
-To build and test the site locally, run:
--->
-## 在本地使用 Hugo 来运行网站
-
-请确保安装的是 [`netlify.toml`](netlify.toml#L10) 文件中环境变量 `HUGO_VERSION` 所指定的
-Hugo 扩展版本。
-
-若要在本地构造和测试网站，请运行：
-
-```bash
-# install dependencies
-npm ci
-make serve
-```
-
-<!--
-This will start the local Hugo server on port 1313. Open up your browser to http://localhost:1313 to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
--->
-上述命令会在端口 1313 上启动本地 Hugo 服务器。
-启动浏览器，打开 http://localhost:1313 来查看网站。
-当你对源文件作出修改时，Hugo 会更新网站并强制浏览器执行刷新操作。
-
-<!--
-## Troubleshooting
-### error: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): this feature is not available in your current Hugo version
-
-Hugo is shipped in two set of binaries for technical reasons. The current website runs based on the **Hugo Extended** version only. In the [release page](https://github.com/gohugoio/hugo/releases) look for archives with `extended` in the name. To confirm, run `hugo version` and look for the word `extended`.
-
--->
-## 故障排除
-
-###  error: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): this feature is not available in your current Hugo version
-
-由于技术原因，Hugo 会发布两套二进制文件。
-当前网站仅基于 **Hugo Extended** 版本运行。
-在 [发布页面](https://github.com/gohugoio/hugo/releases) 中查找名称为 `extended` 的归档。可以运行 `hugo version` 查看是否有单词 `extended` 来确认。
-
-<!--
-### Troubleshooting macOS for too many open files
-
-If you run `make serve` on macOS and receive the following error:
-
--->
-### 对 macOS 上打开太多文件的故障排除
-
-如果在 macOS 上运行 `make serve` 收到以下错误：
-
-```
-ERROR 2020/08/01 19:09:18 Error: listen tcp 127.0.0.1:1313: socket: too many open files
-make: *** [serve] Error 1
-```
-
-试着查看一下当前打开文件数的限制：
-
-`launchctl limit maxfiles`
-
-然后运行以下命令（参考https://gist.github.com/tombigel/d503800a282fcadbee14b537735d202c）：
-
-```
-#!/bin/sh
-
-# These are the original gist links, linking to my gists now.
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxfiles.plist
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxproc.plist
-
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxfiles.plist
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxproc.plist
-
-sudo mv limit.maxfiles.plist /Library/LaunchDaemons
-sudo mv limit.maxproc.plist /Library/LaunchDaemons
-
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxfiles.plist
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxproc.plist
-
-sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist
-```
-
-这适用于 Catalina 和 Mojave macOS。
-
-<!--
-## Get involved with SIG Docs
-
-Learn more about SIG Docs Kubernetes community and meetings on the [community page](https://github.com/kubernetes/community/tree/master/sig-docs#meetings).
-
-You can also reach the maintainers of this project at:
-
-- [Slack](https://kubernetes.slack.com/messages/sig-docs) [Get an invite for this Slack](https://slack.k8s.io/)
-- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
--->
-# 参与 SIG Docs 工作
-
-通过 [社区页面](https://github.com/kubernetes/community/tree/master/sig-docs#meetings)
-进一步了解 SIG Docs Kubernetes 社区和会议信息。
-
-你也可以通过以下渠道联系本项目的维护人员：
-
-- [Slack](https://kubernetes.slack.com/messages/sig-docs) [加入Slack](https://slack.k8s.io/)
-- [邮件列表](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-<!--
-## Contributing to the docs
-
-You can click the **Fork** button in the upper-right area of the screen to create a copy of this repository in your GitHub account. This copy is called a *fork*. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.
-
-Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback.  As the owner of the pull request, **it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer.**
--->
-# 为文档做贡献
-
-你也可以点击屏幕右上方区域的 **Fork** 按钮，在你自己的 GitHub
-账号下创建本仓库的拷贝。此拷贝被称作 *fork*。
-你可以在自己的拷贝中任意地修改文档，并在你已准备好将所作修改提交给我们时，
-在你自己的拷贝下创建一个拉取请求（Pull Request），以便让我们知道。
-
-一旦你创建了拉取请求，某个 Kubernetes 评审人会负责提供明确的、可执行的反馈意见。
-作为拉取请求的拥有者，*修改拉取请求以解决 Kubernetes
-评审人所提出的反馈是你的责任*。
-
-<!--
-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 when needed.  Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances.
--->
-还要提醒的一点，有时可能会有不止一个 Kubernetes 评审人为你提供反馈意见。
-有时候，某个评审人的意见和另一个最初被指派的评审人的意见不同。
-
-更进一步，在某些时候，评审人之一可能会在需要的时候请求 Kubernetes
-技术评审人来执行技术评审。
-评审人会尽力及时地提供反馈意见，不过具体的响应时间可能会因时而异。
-
-<!--
-For more information about contributing to the Kubernetes documentation, see:
-
-* [Contribute to Kubernetes docs](https://kubernetes.io/docs/contribute/)
-* [Page Content Types](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [Documentation Style Guide](https://kubernetes.io/docs/contribute/style/style-guide/)
-* [Localizing Kubernetes Documentation](https://kubernetes.io/docs/contribute/localization/)
--->
-有关为 Kubernetes 文档做出贡献的更多信息，请参阅：
-
-* [贡献 Kubernetes 文档](https://kubernetes.io/docs/contribute/)
-* [页面内容类型](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [文档风格指南](https://kubernetes.io/docs/contribute/style/style-guide/)
-* [本地化 Kubernetes 文档](https://kubernetes.io/docs/contribute/localization/)
-
-# 中文本地化
-
-可以通过以下方式联系中文本地化的维护人员：
-
-* Rui Chen ([GitHub - @chenrui333](https://github.com/chenrui333))
-* He Xiaolong ([GitHub - @markthink](https://github.com/markthink))
-* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-zh)
-
-<!--
-### Code of conduct
-
-Participation in the Kubernetes community is governed by the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
--->
-# 行为准则
-
-参与 Kubernetes 社区受 [CNCF 行为准则](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) 约束。
-
-<!--
-## Thank you!
-
-Kubernetes thrives on community participation, and we appreciate your contributions to our website and our documentation!
--->
-# 感谢！
-
-Kubernetes 因为社区的参与而蓬勃发展，感谢您对我们网站和文档的贡献！

README.md

@@ -1,196 +1,22 @@
-# The Kubernetes documentation
+## Instructions for Contributing to the Kubernetes Documentation
 
-[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-main-staging/deploys) [![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 Kubernetes documentation.
 
-This repository contains 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 this repository in your GitHub account called a *fork*. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.
 
-- [Contributing to the docs](#contributing-to-the-docs)
-- [Localization ReadMes](#localization-readmemds)
-
-## Using this repository
-
-You can run the website locally using Hugo (Extended version), or you can run it in a container runtime. We strongly recommend using the container runtime, as it gives deployment consistency with the live website.
-
-## Prerequisites
-
-To use this repository, you need the following installed locally:
-
-- [npm](https://www.npmjs.com/)
-- [Go](https://golang.org/)
-- [Hugo (Extended version)](https://gohugo.io/)
-- A container runtime, like [Docker](https://www.docker.com/).
-
-Before you start, install the dependencies. Clone the repository and navigate to the directory:
-
-```bash
-git clone https://github.com/kubernetes/website.git
-cd website
-```
-
-The Kubernetes website uses the [Docsy Hugo theme](https://github.com/google/docsy#readme). Even if you plan to run the website in a container, we strongly recommend pulling in the submodule and other development dependencies by running the following:
-
-```bash
-# pull in the Docsy submodule
-git submodule update --init --recursive --depth 1
-```
-
-## Running the website using a container
-
-To build the site in a container, run the following to build the container image and run it:
-
-```bash
-make container-image
-make container-serve
-```
-
-If you see errors, it probably means that the hugo container did not have enough computing resources available. To solve it, increase the amount of allowed CPU and memory usage for Docker on your machine ([MacOSX](https://docs.docker.com/docker-for-mac/#resources) and [Windows](https://docs.docker.com/docker-for-windows/#resources)).
-
-Open up your browser to <http://localhost:1313> to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
-
-## Running the website locally using Hugo
-
-Make sure to install the Hugo extended version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L10) file.
-
-To build and test the site locally, run:
-
-```bash
-# install dependencies
-npm ci
-make serve
-```
-
-This will start the local Hugo server on port 1313. Open up your browser to <http://localhost:1313> to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh.
-
-## Building the API reference pages
-
-The API reference pages located in `content/en/docs/reference/kubernetes-api` are built from the Swagger specification, using <https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs>.
-
-To update the reference pages for a new Kubernetes release follow these steps:
-
-1. Pull in the `api-ref-generator` submodule:
-
-   ```bash
-   git submodule update --init --recursive --depth 1
-   ```
-
-2. Update the Swagger specification:
-
-   ```bash
-   curl 'https://raw.githubusercontent.com/kubernetes/kubernetes/master/api/openapi-spec/swagger.json' > api-ref-assets/api/swagger.json
-   ```
-
-3. In `api-ref-assets/config/`, adapt the files `toc.yaml` and `fields.yaml` to reflect the changes of the new release.
-
-4. Next, build the pages:
-
-   ```bash
-   make api-reference
-   ```
-
-   You can test the results locally by making and serving the site from a container image:
-
-   ```bash
-   make container-image
-   make container-serve
-   ```
-
-   In a web browser, go to <http://localhost:1313/docs/reference/kubernetes-api/> to view the API reference.
-
-5. When all changes of the new contract are reflected into the configuration files `toc.yaml` and `fields.yaml`, create a Pull Request with the newly generated API reference pages.
-
-## Troubleshooting
-
-### error: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): this feature is not available in your current Hugo version
-
-Hugo is shipped in two set of binaries for technical reasons. The current website runs based on the **Hugo Extended** version only. In the [release page](https://github.com/gohugoio/hugo/releases) look for archives with `extended` in the name. To confirm, run `hugo version` and look for the word `extended`.
-
-### Troubleshooting macOS for too many open files
-
-If you run `make serve` on macOS and receive the following error:
-
-```bash
-ERROR 2020/08/01 19:09:18 Error: listen tcp 127.0.0.1:1313: socket: too many open files
-make: *** [serve] Error 1
-```
-
-Try checking the current limit for open files:
-
-`launchctl limit maxfiles`
-
-Then run the following commands (adapted from <https://gist.github.com/tombigel/d503800a282fcadbee14b537735d202c>):
-
-```shell
-#!/bin/sh
-
-# These are the original gist links, linking to my gists now.
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxfiles.plist
-# curl -O https://gist.githubusercontent.com/a2ikm/761c2ab02b7b3935679e55af5d81786a/raw/ab644cb92f216c019a2f032bbf25e258b01d87f9/limit.maxproc.plist
-
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxfiles.plist
-curl -O https://gist.githubusercontent.com/tombigel/d503800a282fcadbee14b537735d202c/raw/ed73cacf82906fdde59976a0c8248cce8b44f906/limit.maxproc.plist
-
-sudo mv limit.maxfiles.plist /Library/LaunchDaemons
-sudo mv limit.maxproc.plist /Library/LaunchDaemons
-
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxfiles.plist
-sudo chown root:wheel /Library/LaunchDaemons/limit.maxproc.plist
-
-sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist
-```
-
-This works for Catalina as well as Mojave macOS.
-
-## Get involved with SIG Docs
-
-Learn more about SIG Docs Kubernetes community and meetings on the [community page](https://github.com/kubernetes/community/tree/master/sig-docs#meetings).
-
-You can also reach the maintainers of this project at:
-
-- [Slack](https://kubernetes.slack.com/messages/sig-docs)
-  - [Get an invite for this Slack](https://slack.k8s.io/)
-- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
-
-## Contributing to the docs
-
-You can click the **Fork** button in the upper-right area of the screen to create a copy of this repository in your GitHub account. This copy is called a _fork_. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.
-
-Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback. As the owner of the pull request, **it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer.**
-
-Also, note that you may end up having more than one Kubernetes reviewer provide you feedback or you may end up getting feedback from a Kubernetes reviewer that is different than the one initially assigned to provide you feedback.
-
-Furthermore, in some cases, one of your reviewers might ask for a technical review from a Kubernetes tech reviewer when needed. Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances.
+Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback.  As the owner of the pull request, **it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer.**  Also note that you may end up having more than one Kubernetes reviewer provide you feedback or you may end up getting feedback from a Kubernetes reviewer that is different than the one originally assigned to provide you feedback. Furthermore, in some cases, one of your reviewers might ask for a technical review from a [Kubernetes tech reviewer](https://github.com/kubernetes/website/wiki/Tech-reviewers) when needed.  Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances.
 
 For more information about contributing to the Kubernetes documentation, see:
 
-- [Contribute to Kubernetes docs](https://kubernetes.io/docs/contribute/)
-- [Page Content Types](https://kubernetes.io/docs/contribute/style/page-content-types/)
-- [Documentation Style Guide](https://kubernetes.io/docs/contribute/style/style-guide/)
-- [Localizing Kubernetes Documentation](https://kubernetes.io/docs/contribute/localization/)
+* [Contributing to the Kubernetes Documentation](http://kubernetes.io/editdocs/)
+* [Creating a Documentation Pull Request](http://kubernetes.io/docs/home/contribute/create-pull-request/)
+* [Writing a New Topic](http://kubernetes.io/docs/home/contribute/write-new-topic/)
+* [Review Issues](http://kubernetes.io/docs/home/contribute/review-issues/)
+* [Staging Your Documentation Changes](http://kubernetes.io/docs/home/contribute/stage-documentation-changes/)
+* [Using Page Templates](http://kubernetes.io/docs/home/contribute/page-templates/)
+* [Documentation Style Guide](http://kubernetes.io/docs/home/contribute/style-guide/)
 
-### New contributor ambassadors
+## Thank you!
 
-If you need help at any point when contributing, the [New Contributor Ambassadors](https://kubernetes.io/docs/contribute/advanced/#serve-as-a-new-contributor-ambassador) are a good point of contact. These are SIG Docs approvers whose responsibilities include mentoring new contributors and helping them through their first few pull requests. The best place to contact the New Contributors Ambassadors would be on the [Kubernetes Slack](https://slack.k8s.io/). Current New Contributors Ambassadors for SIG Docs:
-
-| Name                       | Slack                      | GitHub                     |                   
-| -------------------------- | -------------------------- | -------------------------- |
-| Arsh Sharma                | @arsh                      | @RinkiyaKeDad              |
-
-## Localization `README.md`'s
-
-| Language                   | Language                   |
-| -------------------------- | -------------------------- |
-| [Chinese](README-zh.md)    | [Korean](README-ko.md)     |
-| [French](README-fr.md)     | [Polish](README-pl.md)     |
-| [German](README-de.md)     | [Portuguese](README-pt.md) |
-| [Hindi](README-hi.md)      | [Russian](README-ru.md)    |
-| [Indonesian](README-id.md) | [Spanish](README-es.md)    |
-| [Italian](README-it.md)    | [Ukrainian](README-uk.md)  |
-| [Japanese](README-ja.md)   | [Vietnamese](README-vi.md) |
-
-## Code of conduct
-
-Participation in the Kubernetes community is governed by the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
-
-## 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!

SECURITY.md

@@ -1,19 +0,0 @@
-# Security Policy
-
-## Security Announcements
-
-Join the [kubernetes-security-announce] group for security and vulnerability announcements.
-
-## Reporting a Vulnerability
-
-Instructions for reporting a vulnerability can be found on the
-[Kubernetes Security and Disclosure Information] page.
-
-## Supported Versions
-
-Information about supported Kubernetes versions can be found on the
-[Kubernetes version and version skew support policy] page on the Kubernetes website.
-
-[kubernetes-security-announce]: https://groups.google.com/forum/#!forum/kubernetes-security-announce
-[Kubernetes version and version skew support policy]: https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-versions
-[Kubernetes Security and Disclosure Information]: https://kubernetes.io/docs/reference/issues-security/security/#report-a-vulnerability

SECURITY_CONTACTS

@@ -1,15 +0,0 @@
-# Defined below are the security contacts for this repo.
-#
-# They are the contact point for the Security Response 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/
-
-divya-mohan0209
-jimangel
-sftim

_config.yml

@@ -0,0 +1,92 @@
+name: Kubernetes
+title: Kubernetes
+url: https://kubernetes.io
+description: Production-Grade Container Orchestration
+markdown: kramdown
+kramdown:
+  input: GFM
+  html_to_native: true
+  hard_wrap: false
+  syntax_highlighter: rouge
+incremental: true
+
+safe: false
+lsi: false
+
+latest: "v1.9"
+defaults:
+  -
+    scope:
+      path: ""
+    values:
+      fullversion: "v1.9.0"
+      version: "v1.9"
+      githubbranch: "master"
+      docsbranch: "master"
+      versions:
+        - fullversion: "v1.9.0"
+          version: "v1.9"
+          githubbranch: "v1.9.0"
+          docsbranch: "release-1.9"
+          url: https://kubernetes.io
+        - fullversion: "v1.8.4"
+          version: "v1.8"
+          githubbranch: "v1.8.4"
+          docsbranch: "release-1.8"
+          url: https://v1-8.docs.kubernetes.io
+        - fullversion: "v1.7.6"
+          version: "v1.7"
+          githubbranch: "v1.7.6"
+          docsbranch: "release-1.7"
+          url: https://v1-7.docs.kubernetes.io
+        - fullversion: "v1.6.8"
+          version: "v1.6"
+          githubbranch: "v1.6.8"
+          docsbranch: "release-1.6"
+          url: https://v1-6.docs.kubernetes.io
+        - fullversion: "v1.5.7"
+          version: "v1.5"
+          githubbranch: "v1.5.7"
+          docsbranch: "release-1.5"
+          url: https://v1-5.docs.kubernetes.io
+      deprecated: false
+      currentUrl: https://kubernetes.io/docs/home/
+      nextUrl: http://kubernetes-io-vnext-staging.netlify.com/
+  -
+    scope:
+      path: "docs"
+    values:
+      layout: docwithnav
+      showedit: true
+
+permalink: pretty
+
+plugins:
+  - jekyll-feed
+  - jekyll-sitemap
+  - jekyll-seo-tag
+  - jekyll-include-cache
+# disabled gems
+#  - jekyll-redirect-from
+
+include: [_redirects,_headers]
+
+# SEO
+logo: /images/favicon.png
+twitter:
+  username: kubernetesio
+
+# empty array for tabs
+emptyArray: []
+
+# Tables of contents, stored in the _data folder, that control the sidebar nav
+tocs:
+  - docs-home
+  - setup
+  - tasks
+  - tutorials
+  - concepts
+  - reference
+  - samples
+  - search
+  - imported

_data/concepts.yml

@@ -0,0 +1,127 @@
+bigheader: "Concepts"
+abstract: "Detailed explanations of Kubernetes system concepts and abstractions."
+landing_page: /docs/concepts/index/
+toc:
+- docs/concepts/index.md
+
+- title: Overview
+  landing_page: /docs/concepts/overview/what-is-kubernetes/
+  section:
+  - docs/concepts/overview/what-is-kubernetes.md
+  - docs/concepts/overview/components.md
+  - docs/concepts/overview/kubernetes-api.md
+  - title: Working with Kubernetes Objects
+    section:
+    - docs/concepts/overview/working-with-objects/kubernetes-objects.md
+    - docs/concepts/overview/working-with-objects/names.md
+    - docs/concepts/overview/working-with-objects/namespaces.md
+    - docs/concepts/overview/working-with-objects/labels.md
+    - docs/concepts/overview/working-with-objects/annotations.md
+  - title: Object Management Using kubectl
+    section:
+    - docs/concepts/overview/object-management-kubectl/overview.md
+    - docs/concepts/overview/object-management-kubectl/imperative-command.md
+    - docs/concepts/overview/object-management-kubectl/imperative-config.md
+    - docs/concepts/overview/object-management-kubectl/declarative-config.md
+
+- title: Kubernetes Architecture
+  landing_page: /docs/concepts/architecture/nodes/
+  section:
+  - docs/concepts/architecture/nodes.md
+  - docs/concepts/architecture/master-node-communication.md
+  - docs/concepts/architecture/cloud-controller.md
+
+- title: Extending Kubernetes
+  landing_page: /docs/concepts/api-extension/custom-resources/
+  section:
+  - docs/concepts/overview/extending.md
+  - title: Extending the Kubernetes API
+    section:
+    - docs/concepts/api-extension/apiserver-aggregation.md
+    - docs/concepts/api-extension/custom-resources.md
+  - title: Compute, Storage, and Networking Extensions
+    section:
+    - docs/concepts/cluster-administration/network-plugins.md
+    - docs/concepts/cluster-administration/device-plugins.md
+  - docs/concepts/service-catalog/index.md
+
+- title: Containers
+  landing_page: /docs/concepts/containers/images/
+  section:
+  - docs/concepts/containers/images.md
+  - docs/concepts/containers/container-environment-variables.md
+  - docs/concepts/containers/container-lifecycle-hooks.md
+
+- title: Workloads
+  landing_page: /docs/concepts/workloads/pods/pod-overview/
+  section:
+  - title: Pods
+    section:
+    - docs/concepts/workloads/pods/pod-overview.md
+    - docs/concepts/workloads/pods/pod.md
+    - docs/concepts/workloads/pods/pod-lifecycle.md
+    - docs/concepts/workloads/pods/init-containers.md
+    - docs/concepts/workloads/pods/podpreset.md
+    - docs/concepts/workloads/pods/disruptions.md
+  - title: Controllers
+    section:
+    - docs/concepts/workloads/controllers/replicaset.md
+    - docs/concepts/workloads/controllers/replicationcontroller.md
+    - docs/concepts/workloads/controllers/deployment.md
+    - docs/concepts/workloads/controllers/statefulset.md
+    - docs/concepts/workloads/controllers/daemonset.md
+    - docs/concepts/workloads/controllers/garbage-collection.md
+    - docs/concepts/workloads/controllers/jobs-run-to-completion.md
+    - docs/concepts/workloads/controllers/cron-jobs.md
+
+- title: Configuration
+  landing_page: /docs/concepts/configuration/overview/
+  section:
+  - docs/concepts/configuration/overview.md
+  - docs/concepts/configuration/manage-compute-resources-container.md
+  - docs/concepts/configuration/assign-pod-node.md
+  - docs/concepts/configuration/taint-and-toleration.md
+  - docs/concepts/configuration/secret.md
+  - docs/concepts/configuration/organize-cluster-access-kubeconfig.md
+  - docs/concepts/configuration/pod-priority-preemption.md
+
+- title: Services, Load Balancing, and Networking
+  landing_page: /docs/concepts/services-networking/service/
+  section:
+  - docs/concepts/services-networking/service.md
+  - docs/concepts/services-networking/dns-pod-service.md
+  - docs/concepts/services-networking/connect-applications-service.md
+  - docs/concepts/services-networking/ingress.md
+  - docs/concepts/services-networking/network-policies.md
+  - docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md
+
+- title: Storage
+  landing_page: /docs/concepts/storage/volumes/
+  section:
+  - docs/concepts/storage/volumes.md
+  - docs/concepts/storage/persistent-volumes.md
+  - docs/concepts/storage/storage-classes.md
+  - docs/concepts/storage/dynamic-provisioning.md
+
+- title: Cluster Administration
+  landing_page: /docs/concepts/cluster-administration/cluster-administration-overview/
+  section:
+  - docs/concepts/cluster-administration/cluster-administration-overview.md
+  - docs/concepts/cluster-administration/certificates.md
+  - docs/concepts/cluster-administration/cloud-providers.md
+  - docs/concepts/cluster-administration/manage-deployment.md
+  - docs/concepts/cluster-administration/networking.md
+  - docs/concepts/cluster-administration/network-plugins.md
+  - docs/concepts/cluster-administration/logging.md
+  - docs/concepts/cluster-administration/kubelet-garbage-collection.md
+  - docs/concepts/cluster-administration/federation.md
+  - docs/concepts/cluster-administration/sysctl-cluster.md
+  - docs/concepts/cluster-administration/authenticate-across-clusters-kubeconfig.md
+  - docs/concepts/cluster-administration/master-node-communication.md
+  - docs/concepts/cluster-administration/proxies.md
+  - docs/concepts/cluster-administration/controller-metrics.md
+  - docs/concepts/cluster-administration/device-plugins.md
+  - title: Policies
+    section:
+    - docs/concepts/policy/resource-quotas.md
+    - docs/concepts/policy/pod-security-policy.md

_data/docs-home.yml

@@ -0,0 +1,28 @@
+bigheader: "About"
+abstract: "Documentation for using and learning about Kubernetes."
+toc:
+- docs/home/index.md
+
+- title: Supported Doc Versions
+  path: /docs/home/supported-doc-versions/
+
+- title: Contributing to the Kubernetes Docs
+  landing_page: /editdocs/
+  section:
+  - editdocs.md
+  - docs/home/contribute/participating.md
+  - docs/home/contribute/create-pull-request.md
+  - docs/home/contribute/write-new-topic.md
+  - docs/home/contribute/stage-documentation-changes.md
+  - docs/home/contribute/page-templates.md
+  - docs/home/contribute/review-issues.md
+  - docs/home/contribute/style-guide.md
+  - docs/home/contribute/includes.md
+  - docs/home/contribute/localization.md
+
+  - title: Updating Automatically Generated Reference Pages
+    section:
+    - docs/home/contribute/generated-reference/kubernetes-components.md
+    - docs/home/contribute/generated-reference/kubectl.md
+    - docs/home/contribute/generated-reference/kubernetes-api.md
+    - docs/home/contribute/generated-reference/federation-api.md

_data/globals.yml

@@ -0,0 +1,11 @@
+tocs:
+- docs-home
+- guides
+- setup
+- tasks
+- tutorials
+- concepts
+- reference
+- samples
+- support
+- imported

_data/glossary/_example.yml

@@ -0,0 +1,27 @@
+id: _example
+name: Example K8s Term
+full-link: /docs/link-to-long-dedicated-docs-page
+aka:
+- Slang K8s Term
+- Misnomer
+- Formerly Known as Prince
+related:
+- id-of-less-fancy-k8s-term
+- id-of-tangential-term
+- id-of-commonly-used-with-term
+tags:
+- Some Tag
+short-description: >
+  Required.
+  Markdown allowed (e.g. for cross-linking).
+  One or two lines that provide a minimum definition.
+  Do not repeat the term.
+  Prefer fragments.
+  End with a period.
+long-description: >
+  Optional.
+  Markdown allowed.
+  Longer additional text to appear after (in conjunction with) short description.
+  Provide where the short description is not sufficient as the intro paragraph to a topic.
+  Write complete but concise sentences.
+  **See /_includes/templates/glossary/README.md for the official style guide.**

_data/glossary/annotation.yaml

@@ -0,0 +1,9 @@
+id: annotation
+name: Annotation
+full-link: /docs/concepts/overview/working-with-objects/annotations
+tags:
+- fundamental
+short-description: >
+  A key-value pair that is used to attach arbitrary non-identifying metadata to objects.
+long-description: >
+  The metadata in an annotation can be small or large, structured or unstructured, and can include characters not permitted by labels. Clients such as tools and libraries can retrieve this metadata.

_data/glossary/application-architect.yaml

@@ -0,0 +1,11 @@
+id: application-architect
+name: Application Architect
+related:
+  - application-developer
+tags:
+  - user-type
+short-description: >
+  A person responsible for the high-level design of an application.
+long-description: >
+  An architect ensures that an app's implementation allows it to interact with its surrounding components in a scalable, maintainable way.
+  Surrounding components include databases, logging infrastructure, and other microservices.

_data/glossary/application-developer.yaml

@@ -0,0 +1,11 @@
+id: application-developer
+name: Application Developer
+related:
+  - application-architect
+tags:
+  - user-type
+short-description: >
+  A person who writes an application that runs in a Kubernetes cluster.
+long-description: >
+  An application developer focuses on one part of an application.
+  The scale of their focus may vary significantly in size.

_data/glossary/approver.yaml

@@ -0,0 +1,10 @@
+id: approver
+name: Approver
+tags:
+- community
+short-description: >
+  A person who can review and approve Kubernetes code contributions.
+long-description: >
+  While code review is focused on code quality and correctness, approval is focused on the holistic acceptance of a contribution.
+  Holistic acceptance includes backwards/forwards compatibility, adhering to API and flag conventions, subtle performance and correctness issues, interactions with other parts of the system, and others.
+  Approver status is scoped to a part of the codebase.

_data/glossary/certificate.yaml

@@ -0,0 +1,11 @@
+id: certificate
+name: Certificate
+full-link: /docs/tasks/tls/managing-tls-in-a-cluster/
+tags:
+- security
+short-description: >
+  A cryptographically secure file used to validate access to the Kubernetes cluster.
+long-description: >
+  Certificates enable applications within a Kubernetes
+  cluster to access the Kubernetes API securely. Certificates validate that
+  clients are allowed to access the API.

_data/glossary/cla.yaml

@@ -0,0 +1,9 @@
+id: cla
+name: CLA (Contributor License Agreement)
+full-link: https://github.com/kubernetes/community/blob/master/CLA.md
+tags:
+- community
+short-description: >
+  Terms under which a {% glossary_tooltip text="contributor" term_id="contributor" %} grants a license to an open source project for their contributions.
+long-description: >
+  CLAs help resolve legal disputes involving contributed material and intellectual property (IP).

_data/glossary/cloud-controller-manager.yml

@@ -0,0 +1,13 @@
+id: cloud-controller-manager
+name: Cloud Controller Manager
+full-link: https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/
+tags:
+- core-object
+- architecture
+- operation
+short-description: >
+  Cloud Controller Manager is an alpha feature in 1.8. In upcoming releases it will be the preferred way to integrate Kubernetes with any cloud.
+long-description: >
+  Kubernetes v1.6 contains a new binary called cloud-controller-manager. cloud-controller-manager is a daemon that embeds cloud-specific control loops. 
+  These cloud-specific control loops were originally in the kube-controller-manager. Since cloud providers develop and release at a different pace compared to the Kubernetes 
+  project, abstracting the provider-specific code to the cloud-controller-manager binary allows cloud vendors to evolve independently from the core Kubernetes code.

_data/glossary/cloud-provider.yaml

@@ -0,0 +1,10 @@
+id: cloud-provider
+name: Cloud Provider
+full-link: /docs/concepts/cluster-administration/cloud-providers
+tags:
+- community
+short-description: >
+  Cloud provider is a company that offers cloud computing platform that can run Kubernetes clusters.
+long-description: >
+  Cloud providers or sometime called Cloud Service Provider (CSPs) provides cloud computing platforms.  They may offer services such as Infrastructure as a Service (IaaS) or Platform as a Service (PaaS).  Cloud providers host the Kubernetes cluster and also provide services that interact with the cluster, such as Load Balancers, Storage Classes etc. 
+

_data/glossary/cluster-architect.yaml

@@ -0,0 +1,11 @@
+id: cluster-architect
+name: Cluster Architect
+related:
+  - cluster
+  - cluster-operator
+tags:
+  - user-type
+short-description: >
+  A person who designs infrastructure that involves one or more Kubernetes clusters.
+long-description: >
+  Cluster architects are concerned with best practices for distributed systems, for example: high availability and security.

_data/glossary/cluster-operator.yaml

@@ -0,0 +1,15 @@
+id: cluster-operator
+name: Cluster Operator
+aka:
+  - Cluster Administrator
+related:
+  - cluster
+  - cluster-architect
+tags:
+  - user-type
+short-description: >
+  A person who configures, controls, and monitors clusters.
+long-description: |
+  Their primary responsibility is keeping a cluster up and running, which may involve periodic maintenance activities or upgrades.<br>
+
+  **NOTE:** Cluster operators are different from the [Operator pattern](https://coreos.com/operators) that extends the Kubernetes API.

_data/glossary/cluster.yaml

@@ -0,0 +1,9 @@
+id: cluster
+name: Cluster
+tags:
+- fundamental
+- operation
+short-description: >
+  A set of machines, called nodes, that run containerized applications managed by Kubernetes.
+long-description: >
+  A cluster has several worker nodes and at least one master node.

_data/glossary/code-contributor.yaml

@@ -0,0 +1,12 @@
+id: code-contributor
+name: Code Contributor
+full-link: /docs/imported/community/devel/
+aka:
+  - Community Developer
+tags:
+- community
+- user-type
+short-description: >
+  A person who develops and contributes code to the Kubernetes open source codebase.
+long-description: >
+  They are also an active {% glossary_tooltip text="community member" term_id="member" %} who participates in one or more {% glossary_tooltip text="Special Interest Groups (SIGs)" term_id="sig" %}.

_data/glossary/configmap.yaml

@@ -0,0 +1,13 @@
+id: configmap
+name: ConfigMap
+full-link: /docs/tasks/configure-pod-container/configure-pod-configmap/
+related:
+- pod
+- secret
+tags:
+- core-object
+short-description: >
+  An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or config files in a {% glossary_tooltip text="volume" term_id="volume" %}.
+long-description: >
+  Allows you to decouple environment-specific configuration from your {% glossary_tooltip text="container images" term_id="container" %}, so that your applications are easily portable.
+  When storing confidential data use a [Secret](https://kubernetes.io/docs/concepts/configuration/secret/).

_data/glossary/container-env-variables.yaml

@@ -0,0 +1,9 @@
+id: container-env-variables
+name: Container Environment Variables
+full-link: /docs/concepts/containers/container-environment-variables.md
+tags:
+- fundamental
+short-description: >
+  Container environment variables are name/value pairs that provide useful information into containers running in a Pod.
+long-description: >
+  Container environment variables provide information that is required by the running containerized applications along with information about important resources to the [Containers] {% glossary_tooltip text="Containers" term_id="container" %}. For example, file system, information about the container itself and other cluster resources such as service endpoints, etc.

_data/glossary/container.yaml

@@ -0,0 +1,10 @@
+id: container
+name: Container
+full-link: /docs/concepts/overview/what-is-kubernetes/#why-containers
+tags:
+- fundamental
+- workload
+short-description: >
+  A lightweight and portable executable image that contains software and all of its dependencies.
+long-description: >
+  Containers decouple applications from underlying host infrastructure to make deployment easier in different cloud or OS environments, and for easier scaling.

_data/glossary/contributor.yaml

@@ -0,0 +1,8 @@
+id: contributor
+name: Contributor
+tags:
+- community
+short-description: >
+  Someone who donates code, documentation, or their time to help the Kubernetes project or community.
+long-description: >
+  Contributions include pull requests (PRs), issues, feedback, {% glossary_tooltip text="special interest groups (SIG)" term_id="sig" %} participation, or organizing community events.

_data/glossary/controller.yaml

@@ -0,0 +1,12 @@
+id: controller
+name: Controller
+full-link: /docs/admin/kube-controller-manager/
+related:
+- controller-manager
+tags:
+- architecture
+- fundamental
+short-description: >
+  A control loop that watches the shared state of the cluster through the {% glossary_tooltip text="apiserver" term_id="kube-apiserver" %} and makes changes attempting to move the current state towards the desired state.
+long-description: >
+  Examples of controllers that ship with Kubernetes today are the replication controller, endpoints controller, namespace controller, and serviceaccounts controller.

_data/glossary/cronjob.yaml

@@ -0,0 +1,10 @@
+id: cronjob
+name: CronJob
+full-link: /docs/concepts/workloads/controllers/cron-jobs/
+tags:
+- core-object
+- workload
+short-description: >
+  Manages a [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/) that runs on a periodic schedule.
+long-description: >
+  Similar to a line in a *crontab* file, a Cronjob object specifies a schedule using the [Cron](https://en.wikipedia.org/wiki/Cron) format.

_data/glossary/customresourcedefinition.yaml

@@ -0,0 +1,14 @@
+id: CustomResourceDefinition
+name: CustomResourceDefinition
+aka: 
+- CRD
+- Formerly Known as ThirdPartyResources (TPR)
+tags:
+- fundamental
+- operation
+- extension
+full-link: docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/
+short-description: >
+  Custom code that defines a resource to add to your Kubernetes API server without building a complete custom server.
+long-description: >
+  Custom Resource Definitions let you extend the Kubernetes API for your environment if the publicly supported API resources can't meet your needs. 

_data/glossary/daemonset.yaml

@@ -0,0 +1,11 @@
+id: daemonset
+name: DaemonSet
+full-link: /docs/concepts/workloads/controllers/daemonset
+tags:
+- fundamental
+- core-object
+- workload
+short-description: >
+  Ensures a copy of a {% glossary_tooltip text="Pod" term_id="pod" %} is running across a set of nodes in a {% glossary_tooltip text="cluster" term_id="cluster" %}.
+long-description: >
+  Used to deploy system daemons such as log collectors and monitoring agents that typically must run on every {% glossary_tooltip term_id="node" %}.

_data/glossary/deployment.yaml

@@ -0,0 +1,11 @@
+id: deployment
+name: Deployment
+full-link: /docs/concepts/workloads/controllers/deployment/
+tags:
+- fundamental
+- core-object
+- workload
+short-description: >
+  An API object that manages a replicated application.
+long-description: >
+  Each replica is represented by a {% glossary_tooltip term_id="pod" %}, and the Pods are distributed among the nodes of a cluster.

_data/glossary/developer.yaml

@@ -0,0 +1,11 @@
+id: developer
+name: Developer (disambiguation)
+aka:
+  - Kubernetes Developer
+tags:
+- community
+- user-type
+short-description: >
+  May refer to: {% glossary_tooltip text="Application Developer" term_id="application-developer" %}, {% glossary_tooltip text="Code Contributor" term_id="code-contributor" %}, or {% glossary_tooltip text="Platform Developer" term_id="platform-developer" %}.
+long-description: >
+  This overloaded term may have different meanings depending on the context

_data/glossary/docker.yaml

@@ -0,0 +1,9 @@
+id: docker
+name: docker
+full-link: /docs/reference/kubectl/docker-cli-to-kubectl/
+tags:
+- fundamental
+short-description: >
+  Docker is a software technology providing operating-system-level virtualization also known as containers.
+long-description: >
+  Docker uses the resource isolation features of the Linux kernel such as cgroups and kernel namespaces, and a union-capable file system such as OverlayFS and others to allow independent "containers" to run within a single Linux instance, avoiding the overhead of starting and maintaining virtual machines (VMs).

_data/glossary/downstream.yaml

@@ -0,0 +1,11 @@
+id: downstream
+name: Downstream (disambiguation)
+related:
+- upstream
+tags:
+- community
+short-description: >
+  May refer to: code in the Kubernetes ecosystem that depends upon the core Kubernetes codebase or a forked repo.
+long-description: |
+  * In the **Kubernetes Community**: Conversations often use *downstream* to mean the ecosystem, code, or third-party tools that rely on the core Kubernetes codebase. For example, a new feature in Kubernetes may be adopted by applications *downstream* to improve their functionality.
+  * In **GitHub** or **git**: The convention is to refer to a forked repo as *downstream*, whereas the source repo is considered *upstream*.

_data/glossary/dynamic-volume-provisioning.yaml

@@ -0,0 +1,11 @@
+id: dynamicvolumeprovisioning
+name: Dynamic Volume Provisioning
+full-link: /docs/concepts/storage/dynamic-provisioning
+tags:
+- core-object
+- storage
+short-description: >
+  Allows users to request automatic creation of storage  {% glossary_tooltip text="Volumes" term_id="volume" %}.
+long-description: >
+  Dynamic provisioning eliminates the need for cluster administrators to pre-provision storage. Instead, it automatically provisions storage by user request.
+  Dynamic volume provisioning is based on an API object, {% glossary_tooltip text="StorageClass" term_id="storage-class" %}, referring to a {% glossary_tooltip text="Volume Plugin" term_id="volume-plugin" %} that provisions a {% glossary_tooltip text="Volume" term_id="volume" %} and the set of parameters to pass to the Volume Plugin.

_data/glossary/etcd.yaml

@@ -0,0 +1,11 @@
+id: etcd
+name: etcd
+full-link: /docs/tasks/administer-cluster/configure-upgrade-etcd/
+tags:
+- architecture
+- storage
+short-description: >
+  Consistent and highly-available key value store used as Kubernetes' backing store for all cluster data.
+long-description: >
+  Always have a backup plan for etcd's data for your Kubernetes cluster.
+  For in-depth information on etcd, see [etcd documentation](https://github.com/coreos/etcd/blob/master/Documentation/docs.md).

_data/glossary/helm-chart.yaml

@@ -0,0 +1,10 @@
+id: helm-chart
+name: Helm Chart
+full-link: https://github.com/kubernetes/helm/blob/master/docs/charts.md
+tags:
+- tool
+short-description: >
+  A package of pre-configured Kubernetes resources that can be managed with the Helm tool.
+long-description: |
+  Charts provide a reproducible way of creating and sharing Kubernetes applications.
+  A single chart can be used to deploy something simple, like a memcached Pod, or something complex, like a full web app stack with HTTP servers, databases, caches, and so on.

_data/glossary/horizontal-pod-autoscaler.yaml

@@ -0,0 +1,17 @@
+id: horizontal-pod-autoscaler
+name: Horizontal Pod Autoscaler
+full-link: /docs/tasks/run-application/horizontal-pod-autoscale/
+aka:
+- HPA
+related:
+- pod
+- replication-controller
+- deployment
+tags:
+- operation
+short-description: >
+  An API resource that automatically scales the number of pod replicas based on targeted CPU
+  utilization or custom metric targets.
+long-description: >
+  HPA is typically used with {% glossary_tooltip text="Replication Controllers" term_id="replication-controller" %}, {% glossary_tooltip text="Deployments" term_id="deployment" %}, or Replica Sets.
+  It cannot be applied to objects that cannot be scaled, for example {% glossary_tooltip text="DaemonSets" term_id="daemonset" %}.

_data/glossary/image.yaml

@@ -0,0 +1,9 @@
+id: image
+name: Image
+tags:
+- fundamental
+short-description: >
+  Stored instance of a container that holds a set of software needed to run an application.
+long-description: >
+  A way of packaging software that allows it to be stored in a container registry, pulled to a local system, and run as an application. Meta data is included in the image that can indicate what executable to run, who built it, and other information.
+

_data/glossary/ingress.yaml

@@ -0,0 +1,13 @@
+id: ingress
+name: Ingress
+full-link: /docs/concepts/services-networking/ingress/
+aka:
+  - Ingress controller
+tags:
+- networking
+- architecture
+- extension
+short-description: >
+  An API object that manages external access to the services in a cluster, typically HTTP.
+long-description: >
+  Ingress can provide load balancing, SSL termination and name-based virtual hosting.

_data/glossary/init-container.yaml

@@ -0,0 +1,8 @@
+id: init-container
+name: Init Container
+tags:
+- fundamental
+short-description: >
+  One or more initialization containers that must run to completion before any app containers run. 
+long-description: >
+  Initialization (init) containers are like regular app containers, with one difference: init containers must run to completion before any app containers can start. Init containers run in series: each init container must run to completion before the next init container begins.  

_data/glossary/istio.yaml

@@ -0,0 +1,13 @@
+id: istio
+name: Istio
+full-link: https://istio.io/docs/concepts/what-is-istio/overview.html
+tags:
+- networking
+- architecture
+- extension
+short-description: >
+  An open platform (not Kubernetes-specific) that provides a uniform way to integrate microservices, manage traffic flow, enforce policies, and aggregate telemetry data.
+long-description: >
+  Adding Istio does not require changing application code.
+  It is a layer of infrastructure between a service and the network, which when combined with service deployments, is commonly referred to as a service mesh.
+  Istio's control plane abstracts away the underlying cluster management platform, which may be Kubernetes, Mesosphere, etc.

_data/glossary/job.yaml

@@ -0,0 +1,11 @@
+id: job
+name: Job
+full-link: /docs/concepts/workloads/controllers/jobs-run-to-completion
+tags:
+- fundamental
+- core-object
+- workload
+short-description: >
+  A finite or batch task that runs to completion.
+long-description: >
+  Creates one or more {% glossary_tooltip term_id="pod" %} objects and ensures that a specified number of them successfully terminate. As Pods successfully complete, the Job tracks the successful completions.

_data/glossary/kops.yaml

@@ -0,0 +1,19 @@
+id: kops
+name: Kops
+full-link: /docs/getting-started-guides/kops/
+tags:
+- tool
+- operation
+short-description: >
+  A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters. *NOTE: Officially supports AWS only, with GCE and VMware vSphere in alpha*.
+long-description: |
+  `kops` provisions your cluster with:
+
+    * Fully automated installation
+    * DNS-based cluster identification
+    * Self-healing: everything runs in Auto-Scaling Groups
+    * Limited OS support (Debian preferred, Ubuntu 16.04 supported, early support for CentOS & RHEL)
+    * High availability (HA) support
+    * The ability to directly provision, or generate terraform manifests
+
+  You can also build your own cluster using {% glossary_tooltip term_id="kubeadm" %} as a building block. `kops` builds on the kubeadm work.

_data/glossary/kube-apiserver.yaml

@@ -0,0 +1,12 @@
+id: kube-apiserver
+name: kube-apiserver
+full-link: /docs/reference/generated/kube-apiserver/
+aka:
+- apiserver
+tags:
+- architecture
+- fundamental
+short-description: >
+  Component on the master that exposes the Kubernetes API. It is the front-end for the Kubernetes control plane. 
+long-description: >
+  It is designed to scale horizontally -- that is, it scales by deploying more instances. See [Building High-Availability Clusters](/docs/admin/high-availability/).

_data/glossary/kube-controller-manager.yaml

@@ -0,0 +1,14 @@
+id: kube-controller-manager
+name: kube-controller-manager
+full-link: /docs/reference/generated/kube-controller-manager/
+aka:
+- controller-manager
+related:
+- controller
+tags:
+- architecture
+- fundamental
+short-description: >
+  Component on the master that runs {% glossary_tooltip text="controllers" term_id="controller" %}.
+long-description: >
+  Logically, each {% glossary_tooltip text="controller" term_id="controller" %} is a separate process, but to reduce complexity, they are all compiled into a single binary and run in a single process.

_data/glossary/kube-proxy.yaml

@@ -0,0 +1,10 @@
+id: kube proxy
+name: kube-proxy
+full-link: /docs/reference/generated/kube-proxy
+tags:
+- fundamental
+- core-object
+short-description: >
+  `kube-proxy` is a network proxy that runs on each node in the cluster.
+long-description: >
+  `kube-proxy` is responsible for request forwarding. `kube-proxy` allows TCP and UDP stream forwarding or round robin TCP and UDP forwarding across a set of backend functions.

_data/glossary/kube-scheduler.yaml

@@ -0,0 +1,13 @@
+id: kube-scheduler
+name: kube-scheduler
+full-link: /docs/reference/generated/kube-scheduler/
+aka:
+- scheduler
+tags:
+- architecture
+short-description: >
+  Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
+long-description: >
+  Factors taken into account for scheduling decisions include individual and collective resource requirements, 
+  hardware/software/policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference
+  and deadlines.

_data/glossary/kubeadm.yaml

@@ -0,0 +1,10 @@
+id: kubeadm
+name: Kubeadm
+full-link: /docs/admin/kubeadm/
+tags:
+- tool
+- operation
+short-description: >
+  A tool for quickly installing Kubernetes and setting up a secure cluster.
+long-description: >
+  You can use kubeadm to install both the control plane and the worker node components.

_data/glossary/kubectl.yaml

@@ -0,0 +1,10 @@
+id: kubectl
+name: Kubectl
+full-link: /docs/user-guide/kubectl-overview/
+tags:
+- tool
+- fundamental
+short-description: >
+  A command line tool for communicating with a {% glossary_tooltip text="Kubernetes API" term_id="kubernetes-api" %} server.
+long-description: >
+  You can use kubectl to create, inspect, update, and delete Kubernetes objects.

_data/glossary/kubelet.yaml

@@ -0,0 +1,10 @@
+id: kubelet
+name: Kubelet
+full-link: /docs/reference/generated/kubelet
+tags:
+- fundamental
+- core-object
+short-description: >
+  An agent that runs on each node in the cluster. It makes sure that containers are running in a pod.
+long-description: >
+  The kubelet takes a set of PodSpecs that are provided through various mechanisms and ensures that the containers described in those PodSpecs are running and healthy. The kubelet doesn’t manage containers which were not created by Kubernetes.

_data/glossary/kubernetes-api.yaml

@@ -0,0 +1,13 @@
+id: kubernetes-api
+name: Kubernetes API
+full-link: /docs/concepts/overview/kubernetes-api/
+tags:
+- fundamental
+- architecture
+short-description: >
+  The application that serves Kubernetes functionality through a RESTful interface and stores the state of the cluster.
+long-description: >
+  Kubernetes resources and "records of intent" are all stored as API objects, and modified via RESTful calls to the API.
+  The API allows configuration to be managed in a declarative way.
+  Users can interact with the Kubernetes API directly, or via tools like `kubectl`.
+  The core Kubernetes API is flexible and can also be extended to support custom resources.

_data/glossary/label.yaml

@@ -0,0 +1,10 @@
+id: label
+name: Label
+full-link: /docs/concepts/overview/working-with-objects/labels
+tags:
+- fundamental
+short-description: >
+  Tags objects with identifying attributes that are meaningful and relevant to users.
+long-description: >
+  Labels are key/value pairs that are attached to objects such as {% glossary_tooltip text="Pods" term_id="pod" %}.
+  They are used to organize and to select subsets of objects.