Merge pull request #27500 from shuuji3/patch-4

Fix small errors on setup/best-practices/multiple-zones
Translate one sentence and fix minor errors
2021-04-14 21:19:49 -07:00 · 2021-04-11 12:37:34 +09:00
3223 changed files with 84286 additions and 466227 deletions
@@ -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
@@ -11,7 +11,7 @@
 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
+ Use the default base branch, “master”, if you're documenting existing
 features in the English localization.

 If you're working on a different localization (not English), see
@@ -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
@@ -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}"
@@ -33,8 +33,4 @@ resources/
 # Netlify Functions build output
 package-lock.json
 functions/
-node_modules/
-
-# Generated files when building with make container-build
-.config/
-.npm/
+node_modules/
@@ -1,6 +1,3 @@
 [submodule "themes/docsy"]
 	path = themes/docsy
 	url = https://github.com/google/docsy.git
-[submodule "api-ref-generator"]
-	path = api-ref-generator
-	url = https://github.com/kubernetes-sigs/reference-docs
@@ -4,7 +4,7 @@
 # change is that the Hugo version is now an overridable argument rather than a fixed
 # environment variable.

-FROM golang:1.15-alpine
+FROM alpine:latest

 LABEL maintainer="Luc Perkins <lperkins@linuxfoundation.org>"

@@ -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.
-
@@ -6,9 +6,8 @@ NETLIFY_FUNC      = $(NODE_BIN)/netlify-lambda
 # 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_IMAGE   = kubernetes-hugo:v$(HUGO_VERSION)-$(IMAGE_VERSION)
 CONTAINER_RUN     = $(CONTAINER_ENGINE) run --rm --interactive --tty --volume $(CURDIR):/src

 CCRED=\033[0;31m
@@ -20,11 +19,7 @@ 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:
-	@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
-
-module-init:
-	@echo "Initializing submodules..." 1>&2
-	@git submodule update --init --recursive --depth 1
+	@git submodule status --recursive | awk '/^[+-]/ {printf "\033[31mWARNING\033[0m Submodule not initialized: \033[34m%s\033[0m\n",$$2}' 1>&2

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

@@ -63,7 +58,7 @@ 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-image:
 	$(CONTAINER_ENGINE) build . \
 		--network=host \
 		--tag $(CONTAINER_IMAGE) \
@@ -72,8 +67,8 @@ container-image: ## Build a container image for the preview of the website
 container-build: module-check
 	$(CONTAINER_RUN) --read-only --mount type=tmpfs,destination=/tmp,tmpfs-mode=01777 $(CONTAINER_IMAGE) sh -c "npm ci && hugo --minify"

-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 --bind 0.0.0.0 --destination /tmp/hugo --cleanDestinationDir
+container-serve: module-check
+	$(CONTAINER_RUN) --read-only --mount type=tmpfs,destination=/tmp,tmpfs-mode=01777 -p 1313:1313 $(CONTAINER_IMAGE) hugo server --buildFuture --bind 0.0.0.0 --destination /tmp/hugo --cleanDestinationDir

 test-examples:
 	scripts/test_examples.sh install
@@ -90,10 +85,3 @@ docker-internal-linkcheck:
 container-internal-linkcheck: link-checker-image-pull
 	$(CONTAINER_RUN) $(CONTAINER_IMAGE) hugo --config config.toml,linkcheck-config.toml --buildFuture
 	$(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
@@ -8,12 +8,10 @@ approvers:

 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
+- zacharysarah

 labels:
 - sig/docs
@@ -1,11 +1,18 @@
 aliases:
  sig-docs-blog-owners: # Approvers for blog content
+    - castrojo
+    - kbarnard10
    - onlydole
+    - zacharysarah
    - mrbobbytables
  sig-docs-blog-reviewers: # Reviewers for blog content
+    - castrojo
+    - cody-clark
+    - kbarnard10
    - mrbobbytables
    - onlydole
-    - sftim
+    - parispittman
+    - vonguard
  sig-docs-de-owners: # Admins for German content
    - bene2k1
    - mkorbi
@@ -18,34 +25,37 @@ aliases:
    - annajung
    - bradtopol
    - celestehorgan
-    - divya-mohan0209
+    - irvifa
    - jimangel
-    - jlbutler
+    - kbarnard10
    - kbhawkey
    - onlydole
-    - pi-victor
-    - reylejano
    - savitharaghunathan
    - sftim
+    - steveperry-53
    - tengqm
+    - zacharysarah
+    - zparnold
  sig-docs-en-reviews: # PR reviews for English content
    - bradtopol
    - celestehorgan
    - daminisatya
-    - divya-mohan0209
    - jimangel
+    - kbarnard10
    - kbhawkey
-    - mehabhalodiya
    - onlydole
    - rajeshdeshpande02
    - sftim
-    - shannonxtreme
+    - steveperry-53
    - tengqm
+    - zparnold
  sig-docs-es-owners: # Admins for Spanish content
    - raelga
-    - electrocucaracha
+    - alexbrand
  sig-docs-es-reviews: # PR reviews for Spanish content
    - raelga
+    - alexbrand
+    # glo-pena
    - electrocucaracha
  sig-docs-fr-owners: # Admins for French content
    - remyleone
@@ -76,28 +86,22 @@ aliases:
    - anthonydahanne
    - feloy
  sig-docs-hi-owners: # Admins for Hindi content
-    - anubha-v-ardhan
-    - divya-mohan0209
+    - avidLearnerInProgress
+    - daminisatya
    - mittalyashu
  sig-docs-hi-reviews: # PR reviews for Hindi content
-    - anubha-v-ardhan
-    - divya-mohan0209
+    - avidLearnerInProgress
+    - daminisatya
    - mittalyashu
-    - verma-kunal
  sig-docs-id-owners: # Admins for Indonesian content
-    - ariscahyadi
-    - danninov
    - girikuncoro
-    - habibrosyad
-    - phanama
-    - wahyuoi
+    - irvifa
  sig-docs-id-reviews: # PR reviews for Indonesian content
-    - ariscahyadi
-    - danninov
    - girikuncoro
-    - habibrosyad
-    - phanama
+    - irvifa
    - wahyuoi
+    - phanama
+    - danninov
  sig-docs-it-owners: # Admins for Italian content
    - fabriziopandini
    - Fale
@@ -116,11 +120,10 @@ aliases:
    - bells17
    # cstoku
    - inductor
-    - kakts
    - makocchi-git
    # MasayaAoyama
    - nasa9084
-    # oke-py
+    - oke-py
  sig-docs-ko-owners: # Admins for Korean content
    - ClaudiaJKang
    - gochist
@@ -131,15 +134,13 @@ aliases:
    - ClaudiaJKang
    - gochist
    - ianychoi
-    - jihoon-seo
-    - jmyung
-    - pjhwa
    - seokho-son
-    - yoonian
    - ysyukr
+    - pjhwa
  sig-docs-leads: # Website chairs and tech leads
-    - divya-mohan0209
+    - irvifa
    - jimangel
+    - kbarnard10
    - kbhawkey
    - onlydole
    - sftim
@@ -157,10 +158,8 @@ aliases:
    # zhangxiaoyu-zidif
  sig-docs-zh-reviews: # PR reviews for Chinese content
    - chenrui333
-    - chenxuc
    - howieyuen
    - idealhack
-    - mengjiao-liu
    - pigletfly
    - SataQiu
    - tanjunchen
@@ -168,23 +167,15 @@ aliases:
    - 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
@@ -222,39 +213,3 @@ aliases:
    - idvoretskyi
    - MaxymVlasov
    - Potapy4
-  # authoritative source: git.k8s.io/community/OWNERS_ALIASES
-  committee-steering: # provide PR approvals for announcements
-    - cblecker
-    - dims
-    - justaugustus
-    - liggitt
-    - mrbobbytables
-    - parispittman
-    - tpepper
-  # authoritative source: https://git.k8s.io/sig-release/OWNERS_ALIASES
-  sig-release-leads:
-    - cpanato # SIG Technical Lead
-    - hasheddan # 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
-    - hasheddan # subproject owner / Release Manager
-    - puerco # Release Manager
-    - saschagrunert # subproject owner / Release Manager
-    - justaugustus # subproject owner / 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
-    - palnabarun # Release Manager Associate
-    - onlydole # Release Manager Associate
-    - sethmccombs # Release Manager Associate
-    - thejoycekung # Release Manager Associate
-    - verolop # Release Manager Associate
-    - wilsonehusin # Release Manager Associate
@@ -9,14 +9,14 @@ Herzlich willkommen! Dieses Repository enthält alle Assets, die zur Erstellung

 Sie können auf die Schaltfläche **Fork** im oberen rechten Bereich des Bildschirms klicken, um eine Kopie dieses Repositorys in Ihrem GitHub-Konto zu erstellen. Diese Kopie wird als *Fork* bezeichnet. Nehmen Sie die gewünschten Änderungen an Ihrem Fork vor. Wenn Sie bereit sind, diese Änderungen an uns zu senden, gehen Sie zu Ihrem Fork und erstellen Sie eine neue Pull-Anforderung, um uns darüber zu informieren.

-Sobald Ihre Pull-Anfrage erstellt wurde, übernimmt ein Rezensent von Kubernetes die Verantwortung für klares, umsetzbares Feedback. Als Eigentümer des Pull-Request **liegt es in Ihrer Verantwortung Ihren Pull-Reqest entsprechend des Feedbacks, dass Sie vom Kubernetes-Reviewer erhalten haben abzuändern.** Beachten Sie auch, dass Sie am Ende mehr als einen Rezensenten von Kubernetes erhalten, der Ihnen Feedback gibt, oder dass Sie Rückmeldungen von einem Rezensenten von Kubernetes erhalten, der sich von demjenigen unterscheidet, der ursprünglich für das Feedback zugewiesen wurde. In einigen Fällen kann es vorkommen, dass einer Ihrer Prüfer bei Bedarf eine technische Überprüfung von einem [Kubernetes Tech-Reviewer](https://github.com/kubernetes/website/wiki/tech-reviewers) anfordert. Reviewer geben ihr Bestes, um zeitnah Feedback zu geben, die Antwortzeiten können jedoch je nach den Umständen variieren.
+Sobald Ihre Pull-Anfrage erstellt wurde, übernimmt ein Rezensent von Kubernetes die Verantwortung für klares, umsetzbares Feedback. Als Eigentümer des Pull-Request **liegt es in Ihrer Verantwortung Ihren Pull-Reqest enstsprechend des Feedbacks, dass Sie vom Kubernetes-Reviewer erhalten haben abzuändern.** Beachten Sie auch, dass Sie am Ende mehr als einen Rezensenten von Kubernetes erhalten, der Ihnen Feedback gibt, oder dass Sie Rückmeldungen von einem Rezensenten von Kubernetes erhalten, der sich von demjenigen unterscheidet, der ursprünglich für das Feedback zugewiesen wurde. In einigen Fällen kann es vorkommen, dass einer Ihrer Prüfer bei Bedarf eine technische Überprüfung von einem [Kubernetes Tech-Reviewer](https://github.com/kubernetes/website/wiki/tech-reviewers) anfordert. Reviewer geben ihr Bestes, um zeitnah Feedback zu geben, die Antwortzeiten können jedoch je nach den Umständen variieren.

 Weitere Informationen zum Beitrag zur Kubernetes-Dokumentation finden Sie unter:

 * [Mitwirkung beginnen](https://kubernetes.io/docs/contribute/start/)
-* [Ihre Dokumentationsänderungen bereitstellen](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/)
+* [Ihre Dokumentationsänderungen bereitstellen](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Seitenvorlagen verwenden](http://kubernetes.io/docs/contribute/style/page-content-types/)
+* [Dokumentationsstil-Handbuch](http://kubernetes.io/docs/contribute/style/style-guide/)
 * [Übersetzung der Kubernetes-Dokumentation](https://kubernetes.io/docs/contribute/localization/)

 ## `README.md`'s Localizing Kubernetes Documentation
@@ -37,13 +37,6 @@ Um die Kubernetes-Website lokal laufen zu lassen, empfiehlt es sich, ein speziel

 > Wenn Sie die Website lieber lokal ohne Docker ausführen möchten, finden Sie weitere Informationen unter [Website lokal mit Hugo ausführen](#Die-Site-lokal-mit-Hugo-ausführen).

-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
@@ -62,18 +55,9 @@ make container-serve

 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 Site lokal aus, wenn Sie Hugo installiert haben:

 ```bash
-# Installieren der JavaScript Abhängigkeiten
-npm ci
 make serve
 ```

@@ -81,7 +65,7 @@ Dadurch wird der lokale Hugo-Server an Port 1313 gestartet. Öffnen Sie Ihren Br

 ## 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.
+Erfahren Sie auf der [Community-Seite](http://kubernetes.io/community/) wie Sie mit der Kubernetes-Community interagieren können.

 Sie können die Betreuer dieses Projekts unter folgender Adresse erreichen:

@@ -17,9 +17,9 @@ Los revisores harán todo lo posible para proporcionar toda la información nece
 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/)
+* [Visualizando sus cambios en su entorno local](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Utilizando las plantillas de las páginas](http://kubernetes.io/docs/contribute/style/page-content-types/)
+* [Guía de estilo de la documentación](http://kubernetes.io/docs/contribute/style/style-guide/)
 * [Traduciendo la documentación de Kubernetes](https://kubernetes.io/docs/contribute/localization/)

 ## Levantando el sitio web kubernetes.io en su entorno local con Docker
@@ -30,17 +30,6 @@ El método recomendado para levantar una copia local del sitio web kubernetes.io

 > 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
@@ -84,4 +73,4 @@ La participación en la comunidad de Kubernetes está regulada por el [Código d

 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.
+Agradecemos muchísimo sus contribuciones a nuestro sitio web y nuestra documentación.
@@ -7,7 +7,7 @@

 ## डॉक्स में योगदान देना

-आप अपने GitHub खाते में इस रिपॉजिटरी की एक copy बनाने के लिए स्क्रीन के ऊपरी-दाएँ क्षेत्र में **Fork** बटन पर क्लिक करें। इस copy को *Fork* कहा जाता है। अपने fork में परिवर्तन करने के बाद जब आप उनको हमारे पास भेजने के लिए तैयार हों, तो अपने fork पर जाएं और हमें इसके बारे में बताने के लिए एक नया pull request बनाएं।
+आप अपने GitHub खाते में इस रिपॉजिटरी की एक copy बनाने के लिए स्क्रीन के ऊपरी-दाएँ क्षेत्र में **Fork** बटन पर क्लिक करें। इस copy को *Fork* कहा जाता है। अपने fork में कोई भी परिवर्तन करना चाहते हैं, और जब आप उन परिवर्तनों को हमारे पास भेजने के लिए तैयार हों, तो अपने fork पर जाएं और हमें इसके बारे में बताने के लिए एक नया pull request बनाएं।

 एक बार जब आपका pull request बन जाता है, तो एक कुबरनेट्स समीक्षक स्पष्ट, कार्रवाई योग्य प्रतिक्रिया प्रदान करने की जिम्मेदारी लेगा। pull request के मालिक के रूप में, **यह आपकी जिम्मेदारी है कि आप कुबरनेट्स समीक्षक द्वारा प्रदान की गई प्रतिक्रिया को संबोधित करने के लिए अपने pull request को संशोधित करें।**

@@ -23,12 +23,9 @@

 ## `README.md`'s स्थानीयकरण कुबरनेट्स प्रलेखन

-आप हिंदी स्थानीयकरण के मैन्टेनरों तक पहुँच सकते हैं:
+आप पर हिंदी स्थानीयकरण के maintainers तक पहुँच सकते हैं:

-* 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)

 ## स्थानीय रूप से डॉकर का उपयोग करके साइट चलाना
@@ -1,6 +1,6 @@
 # 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)
+[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-master-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/)をビルドするために必要な全アセットが格納されています。貢献に興味を持っていただきありがとうございます！

@@ -1,144 +1,69 @@
 # 쿠버네티스 문서화

-[![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)
+[![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/)를 빌드하는 데 필요한 자산이 포함되어 있습니다. 기여해주셔서 감사합니다!
+환영합니다! 이 저장소는 쿠버네티스 웹사이트 및 문서화를 만드는 데 필요로 하는 모든 asset에 대한 공간을 제공합니다. 여러분이 기여를 원한다는 사실에 매우 기쁩니다!

-# 저장소 사용하기
+## 문서에 기여하기

-Hugo(확장 버전)를 사용하여 웹사이트를 로컬에서 실행하거나, 컨테이너 런타임에서 실행할 수 있습니다. 라이브 웹사이트와의 배포 일관성을 제공하므로, 컨테이너 런타임을 사용하는 것을 적극 권장합니다.
+이 저장소에 대한 복제본을 여러분의 GitHub 계정에 생성하기 위해 화면 오른쪽 위 영역에 있는 **Fork** 버튼을 클릭 가능합니다. 이 복제본은 *fork* 라고 부릅니다. 여러분의 fork에서 원하는 임의의 변경 사항을 만들고, 해당 변경 사항을 보낼 준비가 되었다면, 여러분의 fork로 이동하여 새로운 풀 리퀘스트를 만들어 우리에게 알려주시기 바랍니다.

-## 사전 준비 사항
+여러분의 풀 리퀘스트가 생성된 이후에는, 쿠버네티스 리뷰어가 명료하고 실행 가능한 피드백을 제공하는 책임을 담당할 것입니다. 풀 리퀘스트의 오너로서, **쿠버네티스 리뷰어로부터 제공받은 피드백을 수용하기 위해 풀 리퀘스트를 수정하는 것은 여러분의 책임입니다.** 또한, 참고로 한 명 이상의 쿠버네티스 리뷰어가 여러분에게 피드백을 제공하는 상황에 처하거나, 또는 여러분에게 피드백을 제공하기로 원래 할당된 사람이 아닌 다른 쿠버네티스 리뷰어로부터 피드백을 받는 상황에 처할 수도 있습니다.  그뿐만 아니라, 몇몇 상황에서는, 필요에 따라 리뷰어 중 한 명이 [쿠버네티스 기술 리뷰어](https://github.com/kubernetes/website/wiki/Tech-reviewers)로부터의 기술 리뷰를 요청할지도 모릅니다. 리뷰어는 제시간에 피드백을 제공하기 위해 최선을 다할 것이지만, 응답 시간은 상황에 따라 달라질 수도 있습니다.

-이 저장소를 사용하기 위해, 로컬에 다음의 소프트웨어들이 설치되어 있어야 합니다.
+쿠버네티스 문서화에 기여하기와 관련된 보다 자세한 정보는, 다음을 살펴봅니다:

- [npm](https://www.npmjs.com/)
- [Go](https://golang.org/)
- [Hugo(확장 버전)](https://gohugo.io/)
- [도커](https://www.docker.com/)와 같은 컨테이너 런타임.
+* [기여 시작하기](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/)

-시작하기 전에 의존성이 있는 소프트웨어를 설치합니다. 저장소를 복제(clone)하고 디렉터리로 이동합니다.
+## `README.md`에 대한 쿠버네티스 문서화 번역

-```
-git clone https://github.com/kubernetes/website.git
-cd website
-```
+### 한국어

-쿠버네티스 웹사이트는 [Docsy Hugo 테마](https://github.com/google/docsy#readme)를 사용합니다. 웹사이트를 컨테이너에서 실행하려는 경우에도, 다음을 실행하여 하위 모듈 및 기타 개발 종속성을 가져오는 것이 좋습니다.
+`README.md` 번역 및 한국어 기여자를 위한 보다 자세한 가이드를 [한국어 README](README-ko.md) 페이지 혹은 [쿠버네티스 문서 한글화 가이드](https://kubernetes.io/ko/docs/contribute/localization_ko/)에서 살펴봅니다.

-```
-# Docsy 하위 모듈 가져오기
-git submodule update --init --recursive --depth 1
-```
+한국어 번역 메인테이너에게 다음을 통해 연락 가능합니다.

-## 컨테이너를 사용하여 웹사이트 실행하기
+* 이덕준 ([GitHub - @gochist](https://github.com/gochist))
+* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-ko)

-컨테이너에서 사이트를 빌드하려면, 다음을 실행하여 컨테이너 이미지를 빌드하고 실행합니다.
+## 도커를 사용하여 사이트를 로컬에서 실행하기

-```
+쿠버네티스 웹사이트를 로컬에서 실행하기 위한 추천하는 방식은 [Hugo](https://gohugo.io) 정적 사이트 생성기를 포함하는 특별한 [도커](https://docker.com) 이미지를 실행하는 것입니다.
+
+> Windows에서 실행하는 경우, [Chocolatey](https://chocolatey.org)로 설치할 수 있는 명명 추가 도구를 필요로 할 것입니다. `choco install make`
+
+> 도커를 사용하지 않고 웹사이트를 로컬에서 실행하기를 선호하는 경우에는, 아래 [Hugo를 사용한 로컬 사이트 실행하기](#hugo를-사용한-로컬-사이트-실행하기)를 살펴봅니다.
+
+도커 [동작 및 실행](https://www.docker.com/get-started) 환경이 있는 경우, 로컬에서 `kubernetes-hugo` 도커 이미지를 빌드 합니다:
+
+```bash
 make container-image
+```
+
+해당 이미지가 빌드 된 이후, 사이트를 로컬에서 실행할 수 있습니다:
+
+```bash
 make container-serve
 ```

-웹사이트를 보려면 브라우저를 http://localhost:1313 으로 엽니다. 소스 파일을 변경하면 Hugo가 웹사이트를 업데이트하고 브라우저를 강제로 새로 고칩니다.
+브라우저에서 http://localhost:1313 를 열어 사이트를 살펴봅니다. 소스 파일에 변경 사항이 있을 때, Hugo는 사이트를 업데이트하고 브라우저를 강제로 새로고침합니다.

-## Hugo를 사용하여 로컬에서 웹사이트 실행하기
+## Hugo를 사용한 로컬 사이트 실행하기

-[`netlify.toml`](netlify.toml#L10) 파일의 `HUGO_VERSION` 환경 변수에 지정된 Hugo 확장 버전을 설치해야 합니다.
+Hugo 설치 안내를 위해서는 [공식 Hugo 문서화](https://gohugo.io/getting-started/installing/)를 살펴봅니다. [`netlify.toml`](netlify.toml#L9) 파일에 있는 `HUGO_VERSION` 환경 변수에서 지정된 Hugo 버전이 설치되었는지를 확인합니다.

-사이트를 로컬에서 빌드하고 테스트하려면, 다음을 실행합니다.
+Hugo가 설치되었을 때 로컬에서 사이트를 실행하기 위해 (다음을 실행합니다):

 ```bash
-# 의존성 있는 소프트웨어 설치
-npm ci
 make serve
 ```

-그러면 포트 1313에서 로컬 Hugo 서버가 시작됩니다. 웹사이트를 보려면 http://localhost:1313 으로 브라우저를 엽니다. 소스 파일을 변경하면, Hugo가 웹사이트를 업데이트하고 브라우저를 강제로 새로 고칩니다.
+이를 통해 로컬 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는 기술적인 이유로 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)을 따릅니다.
-
-# 감사합니다!
-
-쿠버네티스는 커뮤니티 참여를 통해 번창하며, 우리는 웹사이트 및 문서화에 대한 당신의 기여에 감사드립니다!
+쿠버네티스는 커뮤니티 참여와 함께 생존하며, 우리는 사이트 및 문서화에 대한 여러분의 컨트리뷰션에 대해 정말 감사하게 생각합니다!
@@ -1,154 +1,90 @@
 # 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)
+[![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)
+
+Witamy!

 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](#informacje-o-wersjach-językowych)
+## Twój wkład w dokumentację

-# Jak używać tego repozytorium
+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.

-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.
+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](https://github.com/kubernetes/website/wiki/Tech-reviewers). Recenzenci zrobią wszystko, aby odpowiedzieć sprawnie, ale konkretny czas odpowiedzi zależy od wielu czynników.

-## Wymagania wstępne
+Więcej informacji na temat współpracy przy tworzeniu dokumentacji znajdziesz na stronach:

-Aby móc skorzystać z tego repozytorium, musisz lokalnie zainstalować:
+* [Jak rozpocząć współpracę](https://kubernetes.io/docs/contribute/start/)
+* [Podgląd wprowadzanych zmian w dokumentacji](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Szablony stron](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [Styl pisania dokumentacji](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [Lokalizacja dokumentacji Kubernetes](https://kubernetes.io/docs/contribute/localization/)

- [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/).
+## Różne wersje językowe `README.md`

-Przed rozpoczęciem zainstaluj niezbędne zależności. Sklonuj repozytorium i przejdź do odpowiedniego katalogu:
+|                                        |                                        |
+|----------------------------------------|----------------------------------------|
+| [README po angielsku](README.md)       | [README po francusku](README-fr.md)    |
+| [README po koreańsku](README-ko.md)    | [README po niemiecku](README-de.md)    |
+| [README po portugalsku](README-pt.md)  | [README w hindi](README-hi.md)        |
+| [README po hiszpańsku](README-es.md)   | [README po indonezyjsku](README-id.md) |
+| [README po chińsku](README-zh.md)      | [README po japońsku](README-ja.md)     |
+| [README po wietnamsku](README-vi.md)   | [README po rosyjsku](README-ru.md)     |
+| [README po włosku](README-it.md)       | [README po ukraińsku](README-uk.md)    |
+|                                        |                                        |

-```
-git clone https://github.com/kubernetes/website.git
-cd website
+## Jak uruchomić lokalną kopię strony przy pomocy Dockera?
+
+Zalecaną metodą uruchomienia serwisu internetowego Kubernetesa lokalnie jest użycie specjalnego obrazu [Dockera](https://docker.com), który zawiera generator stron statycznych [Hugo](https://gohugo.io).
+
+> Użytkownicy Windows będą potrzebowali dodatkowych narzędzi, które mogą zainstalować przy pomocy [Chocolatey](https://chocolatey.org).
+
+```bash
+choco install make
 ```

-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:
+> Jeśli wolisz uruchomić serwis lokalnie bez Dockera, przeczytaj [jak uruchomić serwis lokalnie przy pomocy Hugo](#jak-uruchomić-lokalną-kopię-strony-przy-pomocy-hugo) poniżej.

-```
-# pull in the Docsy submodule
-git submodule update --init --recursive --depth 1
-```
+Jeśli [zainstalowałeś i uruchomiłeś](https://www.docker.com/get-started) już Dockera, zbuduj obraz `kubernetes-hugo` lokalnie:

-## Uruchomienie serwisu w kontenerze
-
-Aby zbudować i uruchomić serwis wewnątrz środowiska kontenerowego, wykonaj następujące polecenia:
-
-```
+```bash
 make container-image
+```
+
+Po zbudowaniu obrazu, możesz uruchomić serwis lokalnie:
+
+```bash
 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.
+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).
+Zajrzyj do [oficjalnej dokumentacji Hugo](https://gohugo.io/getting-started/installing/) po instrukcję instalacji. Upewnij się, że instalujesz rozszerzoną wersję Hugo, określoną przez zmienną środowiskową `HUGO_VERSION` w pliku [`netlify.toml`](netlify.toml#L9).

-Aby uruchomić i przetestować serwis lokalnie, wykonaj:
+Aby uruchomić serwis lokalnie po instalacji Hugo, napisz:

 ```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
+## Społeczność, listy dyskusyjne, uczestnictwo i wsparcie

-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:
-
-```
-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 wersji 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).
+Zajrzyj na stronę [społeczności](http://kubernetes.io/community/), aby dowiedzieć się, jak możesz zaangażować się w jej działania.

 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 Slack-a](https://slack.k8s.io/)
- [List dyskusyjnych](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+* [Komunikatora Slack](https://kubernetes.slack.com/messages/sig-docs)
+* [List dyskusyjnych](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)

-# Twój wkład w dokumentację
+### Zasady postępowania

-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.
+Udział w działaniach społeczności Kubernetes jest regulowany przez [Kodeks postępowania](code-of-conduct.md).

-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](https://github.com/kubernetes/website/wiki/Tech-reviewers). 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 Kubernetes](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!
+## Dziękujemy!

 Kubernetes rozkwita dzięki zaangażowaniu społeczności — doceniamy twój wkład w tworzenie naszego serwisu i dokumentacji!
@@ -1,193 +1,76 @@
 # 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)
+[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website)
+[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)

-Bem-vindos! Este repositório 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!
+Bem vindos! Este repositório abriga todos os recursos necessários para criar o [site e documentação do Kubernetes](https://kubernetes.io/). Estamos muito satisfeitos por você querer contribuir!

-# Utilizando este repositório
+## Contribuindo com os documentos

-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.
+Você pode clicar no botão **Fork** na área superior direita da tela para criar uma cópia desse repositório na sua conta do GitHub. Esta cópia é chamada de *fork*. Faça as alterações desejadas no seu fork e, quando estiver pronto para enviar as alterações para nós, vá até o fork e crie uma nova solicitação de pull para nos informar sobre isso.

-## 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.
+Depois que seu **pull request** for criado, um revisor do Kubernetes assumirá a responsabilidade de fornecer um feedback claro e objetivo. Como proprietário do pull request, **é sua responsabilidade modificar seu pull request para abordar o feedback que foi fornecido a você pelo revisor do Kubernetes.** Observe também que você pode acabar tendo mais de um revisor do Kubernetes para fornecer seu feedback ou você pode acabar obtendo feedback de um revisor do Kubernetes que é diferente daquele originalmente designado para lhe fornecer feedback. Além disso, em alguns casos, um de seus revisores pode solicitar uma revisão técnica de um [revisor de tecnologia Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) quando necessário. Os revisores farão o melhor para fornecer feedback em tempo hábil, mas o tempo de resposta pode variar de acordo com as circunstâncias.

 Para mais informações sobre como contribuir com a documentação do Kubernetes, consulte:

-* [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/)
+* [Comece a contribuir](https://kubernetes.io/docs/contribute/start/)
+* [Preparando suas alterações na documentação](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Usando Modelos de Página](http://kubernetes.io/docs/contribute/style/page-templates/)
 * [Guia de Estilo da Documentação](http://kubernetes.io/docs/contribute/style/style-guide/)
 * [Localizando documentação do Kubernetes](https://kubernetes.io/docs/contribute/localization/)

-Você pode contatar os mantenedores da localização em Português em:
+Você pode contactar os mantenedores da localização em Português em:

 * Felipe ([GitHub - @femrtnz](https://github.com/femrtnz))
 * [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-pt)

-# Código de conduta
+## Executando o site localmente usando o Docker
+
+A maneira recomendada de executar o site do Kubernetes localmente é executar uma imagem especializada do [Docker](https://docker.com) que inclui o gerador de site estático [Hugo](https://gohugo.io).
+
+> Se você está rodando no Windows, você precisará de mais algumas ferramentas que você pode instalar com o [Chocolatey](https://chocolatey.org). `choco install make`
+
+> Se você preferir executar o site localmente sem o Docker, consulte [Executando o site localmente usando o Hugo](#executando-o-site-localmente-usando-o-hugo) abaixo.
+
+Se você tiver o Docker [em funcionamento](https://www.docker.com/get-started), crie a imagem do Docker do `kubernetes-hugo` localmente:
+
+```bash
+make container-image
+```
+
+Depois que a imagem foi criada, você pode executar o site localmente:
+
+```bash
+make container-serve
+```
+
+Abra seu navegador para http://localhost:1313 para visualizar o site. Conforme você faz alterações nos arquivos de origem, Hugo atualiza o site e força a atualização do navegador.
+
+## Executando o site localmente usando o Hugo
+
+Veja a [documentação oficial do Hugo](https://gohugo.io/getting-started/installing/) para instruções de instalação do Hugo. Certifique-se de instalar a versão do Hugo especificada pela variável de ambiente `HUGO_VERSION` no arquivo [`netlify.toml`](netlify.toml#L9).
+
+Para executar o site localmente quando você tiver o Hugo instalado:
+
+```bash
+make serve
+```
+
+Isso iniciará o servidor Hugo local na porta 1313. Abra o navegador para http://localhost:1313 para visualizar o site. Conforme você faz alterações nos arquivos de origem, Hugo atualiza o site e força a atualização do navegador.
+
+## Comunidade, discussão, contribuição e apoio
+
+Aprenda a se envolver com a comunidade do Kubernetes na [página da comunidade](http://kubernetes.io/community/).
+
+Você pode falar com os mantenedores deste projeto:
+
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+### Código de conduta

 A participação na comunidade Kubernetes é regida pelo [Código de Conduta da Kubernetes](code-of-conduct.md).

-# Obrigado!
+## 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!
+O Kubernetes conta com a participação da comunidade e nós realmente agradecemos suas contribuições para o nosso site e nossa documentação!
@@ -1,118 +1,39 @@
 # Документация по 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)
+[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-master-staging/deploys) [![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)

-Данный репозиторий содержит все необходимые файлы для сборки [сайта Kubernetes и документации](https://kubernetes.io/). Мы благодарим вас за желание внести свой вклад!
+Добро пожаловать! Данный репозиторий содержит все необходимые файлы для сборки [сайта 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).
+Обратитесь к [официальной документации Hugo](https://gohugo.io/getting-started/installing/), чтобы установить Hugo. Убедитесь, что вы установили правильную версию Hugo, которая устанавливается в переменной окружения `HUGO_VERSION` в файле [`netlify.toml`](netlify.toml#L10).

-Чтобы собрать и протестировать сайт локально, выполните:
+После установки Hugo, чтобы запустить сайт, выполните в консоли:

 ```bash
-# install dependencies
-npm ci
-make serve
+git clone https://github.com/kubernetes/website.git
+cd website
+hugo server --buildFuture
 ```

-Эти команды запустят локальный сервер Hugo на порту 1313. Откройте браузер и перейдите по ссылке http://localhost:1313, чтобы увидеть сайт. Если вы отредактируете исходные файлы сайта, Hugo автоматически обновит сам сайт и выполнит обновление страницы в браузере.
+Эта команда запустит сервер 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`.
+Узнайте, как поучаствовать в жизни сообщества Kubernetes на [странице сообщества](http://kubernetes.io/community/).

-### Решение проблемы на macOS с "too many open files"
+Вы можете связаться с сопровождающими этого проекта по следующим ссылкам:

-Если вы запускаете `make serve` на macOS и получаете следующую ошибку:
+- [Канал в Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Рассылка](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)

-```
-ERROR 2020/08/01 19:09:18 Error: listen tcp 127.0.0.1:1313: socket: too many open files
-make: *** [serve] Error 1
-```
+## Вклад в документацию

-Попробуйте проверить текущий лимит для открытых файлов:
+Нажмите на кнопку **Fork** в правом верхнем углу, чтобы создать копию этого репозитория в ваш GitHub-аккаунт. Эта копия называется *форк-репозиторием*. Делайте любые изменения в вашем форк-репозитории, и когда вы будете готовы опубликовать изменения, откройте форк-репозиторий и создайте новый пулреквест, чтобы уведомить нас.

-`launchctl limit maxfiles`
+После того, как вы отправите пулреквест, ревьювер Kubernetes даст по нему обратную связь. Вы, как автор пулреквеста, **должны обновить свой пулреквест после его рассмотрения ревьювером Kubernetes.**

-Затем выполните следующие команды (они взяты и адаптированы из 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 оставят свои комментарии или даже может быть так, что новый комментарий ревьювера Kubernetes будет отличаться от первоначального назначенного ревьювера. Кроме того, в некоторых случаях один из ревьюверов может запросить технический обзор у [технического ревьювера Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers), если это будет необходимо. Ревьюверы сделают все возможное, чтобы как можно оперативно оставить свои предложения и пожелания, но время ответа может варьироваться в зависимости от обстоятельств.

 Узнать подробнее о том, как поучаствовать в документации Kubernetes, вы можете по ссылкам ниже:

@@ -121,22 +42,21 @@ sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist
 * [Руководство по оформлению документации](https://kubernetes.io/docs/contribute/style/style-guide/)
 * [Руководство по локализации Kubernetes](https://kubernetes.io/docs/contribute/localization/)

-# Файл `README.md` на других языках
-
+## Файл `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)      |
+| [Английский](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-it.md)   |
+| [Польский]( README-pl.md)     | [Украинский](README-uk.md)    |

-# Кодекс поведения
+### Кодекс поведения

-Участие в сообществе Kubernetes регулируется [кодексом поведения CNCF](https://github.com/cncf/foundation/blob/master/code-of-conduct-languages/ru.md).
+Участие в сообществе Kubernetes регулируется [кодексом поведения CNCF](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).

-# Спасибо!
+## Спасибо!

 Kubernetes процветает благодаря сообществу и мы ценим ваш вклад в сайт и документацию!
@@ -1,7 +1,7 @@
 <!-- # 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)
+[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-master-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/). Ми щасливі, що ви хочете зробити свій внесок!
@@ -18,8 +18,7 @@
 ```bash
 git clone https://github.com/kubernetes/website.git
 cd website
-git submodule update --init --recursive --depth 1
-make serve
+hugo server --buildFuture
 ```

 <!-- 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. -->
@@ -83,4 +82,4 @@ make serve
 ## Дякуємо!

 <!-- Kubernetes thrives on community participation, and we appreciate your contributions to our website and our documentation! -->
-Долучення до спільноти - запорука успішного розвитку Kubernetes. Ми цінуємо ваш внесок у наш сайт і документацію!
+Долучення до спільноти - запорука успішного розвитку Kubernetes. Ми цінуємо ваш внесок у наш сайт і документацію!
@@ -15,7 +15,7 @@ Một khi Pull Request của bạn được tạo, reviewer sẽ chịu trách n

 * [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/)
+* [Sử dụng các trang templates](http://kubernetes.io/docs/contribute/style/page-templates/)
 * [Hướng dẫn biểu mẫu tài liệu](http://kubernetes.io/docs/contribute/style/style-guide/)
 * [Địa phương hóa tài liệu Kubernetes](https://kubernetes.io/docs/contribute/localization/)

@@ -4,7 +4,7 @@
 # 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)
+[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-master-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!
@@ -13,94 +13,52 @@ This repository contains the assets required to build the [Kubernetes website an
 我们非常高兴您想要参与贡献！

 <!--
-# Using this repository
+## Running the website locally using Hugo

-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.
+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 来运行网站

-可以使用 Hugo（扩展版）在本地运行网站，也可以在容器中运行它。强烈建议使用容器，因为这样可以和在线网站的部署保持一致。
+请参考 [Hugo 的官方文档](https://gohugo.io/getting-started/installing/)了解 Hugo 的安装指令。
+请确保安装的是 [`netlify.toml`](netlify.toml#L10) 文件中环境变量 `HUGO_VERSION` 所指定的
+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/).
-
+Before building the site, clone the Kubernetes website repository:
 -->
-## 前提条件
+在构造网站之前，先克隆 Kubernetes website 仓库：

-使用这个仓库，需要在本地安装以下软件：
-
- [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:
-->
-开始前，先安装这些依赖。克隆本仓库并进入对应目录：
-
-```
+```bash
 git clone https://github.com/kubernetes/website.git
 cd website
+git submodule update --init --recursive
 ```

 <!--
-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:
+**Note:**  The Kubernetes website deploys the [Docsy Hugo theme](https://github.com/google/docsy#readme).
+If you have not updated your website repository, the `website/themes/docsy` directory is empty.
+The site cannot build without a local copy of the theme.
+
+Update the website theme:
 -->
+**注意：** Kubernetes 网站要部署 [Docsy Hugo 主题](https://github.com/google/docsy#readme).
+如果你还没有更新你本地的 website 仓库，目录 `website/themes/docsy`
+会是空目录。
+在本地没有主题副本的情况下，网站无法正常构造。

-Kubernetes 网站使用的是 [Docsy Hugo 主题](https://github.com/google/docsy#readme)。 即使你打算在容器中运行网站，我们也强烈建议你通过运行以下命令来引入子模块和其他开发依赖项：
+使用下面的命令更新网站主题：

-```
-# pull in the Docsy submodule
+```bash
 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
+hugo server --buildFuture
 ```

 <!--
@@ -110,63 +68,6 @@ This will start the local Hugo server on port 1313. Open up your browser to http
 启动浏览器，打开 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` 的归档。可以运行 `huge 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

@@ -174,17 +75,17 @@ Learn more about SIG Docs Kubernetes community and meetings on the [community pa

 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/)
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
 - [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
 -->
-# 参与 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/)
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
 - [邮件列表](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)

 <!--
@@ -194,7 +95,7 @@ You can click the **Fork** button in the upper-right area of the screen to creat

 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*。
@@ -228,11 +129,11 @@ For more information about contributing to the Kubernetes documentation, see:
 有关为 Kubernetes 文档做出贡献的更多信息，请参阅：

 * [贡献 Kubernetes 文档](https://kubernetes.io/docs/contribute/)
-* [页面内容类型](https://kubernetes.io/docs/contribute/style/page-content-types/)
-* [文档风格指南](https://kubernetes.io/docs/contribute/style/style-guide/)
+* [页面内容类型](http://kubernetes.io/docs/contribute/style/page-content-types/)
+* [文档风格指南](http://kubernetes.io/docs/contribute/style/style-guide/)
 * [本地化 Kubernetes 文档](https://kubernetes.io/docs/contribute/localization/)

-# 中文本地化
+## 中文本地化

 可以通过以下方式联系中文本地化的维护人员：

@@ -245,15 +146,15 @@ For more information about contributing to the Kubernetes documentation, see:

 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) 约束。
+参与 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 因为社区的参与而蓬勃发展，感谢您对我们网站和文档的贡献！
@@ -1,13 +1,10 @@
 # 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)
+[![Netlify Status](https://api.netlify.com/api/v1/badges/be93b718-a6df-402a-b4a4-855ba186c97d/deploy-status)](https://app.netlify.com/sites/kubernetes-io-master-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!

- [Contributing to the docs](#contributing-to-the-docs)
- [Localization ReadMes](#localization-readmemds)
-
-## Using this repository
+# 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.

@@ -22,14 +19,14 @@ To use this repository, you need the following installed locally:

 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
 ```
@@ -38,14 +35,12 @@ git submodule update --init --recursive --depth 1

 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.
+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

@@ -59,47 +54,9 @@ 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 (replace v1.20 in the following examples with the release to update to):
-
-1. Pull the `kubernetes-resources-reference` submodule:
-
-   ```bash
-   git submodule update --init --recursive --depth 1
-   ```
-
-2. Update the Swagger specification:
-
-```
-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.
+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.

 ## 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`.
@@ -108,7 +65,7 @@ Hugo is shipped in two set of binaries for technical reasons. The current websit

 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
 ```
@@ -117,9 +74,9 @@ Try checking the current limit for open files:

 `launchctl limit maxfiles`

-Then run the following commands (adapted from <https://gist.github.com/tombigel/d503800a282fcadbee14b537735d202c>):
+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.
@@ -140,49 +97,49 @@ sudo launchctl load -w /Library/LaunchDaemons/limit.maxfiles.plist

 This works for Catalina as well as Mojave macOS.

-## Get involved with SIG Docs
+
+# 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/)
+- [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
+# 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.
+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.**
+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.
+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.

 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/)
+* [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/)

-## Localization `README.md`'s
+# 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) |
+| 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
+# 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
+# Thank you!

 Kubernetes thrives on community participation, and we appreciate your contributions to our website and our documentation!
@@ -4,6 +4,8 @@

 Join the [kubernetes-security-announce] group for security and vulnerability announcements.

+You can also subscribe to an RSS feed of the above using [this link][kubernetes-security-announce-rss].
+
 ## Reporting a Vulnerability

 Instructions for reporting a vulnerability can be found on the
@@ -15,5 +17,6 @@ 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-security-announce-rss]: https://groups.google.com/forum/feed/kubernetes-security-announce/msgs/rss_v2_0.xml?num=50
 [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
@@ -1,6 +1,6 @@
 # Defined below are the security contacts for this repo.
 #
-# They are the contact point for the Security Response Committee to reach out
+# They are the contact point for the Product Security Committee to reach out
 # to for triaging and handling of incoming issues.
 #
 # The below names agree to abide by the
@@ -10,6 +10,7 @@
 # DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE
 # INSTRUCTIONS AT https://kubernetes.io/security/

-divya-mohan0209
+irvifa
 jimangel
-sftim
+kbarnard10
+sftim
@@ -1,696 +0,0 @@
- definition: io.k8s.api.core.v1.PodSpec
-  field_categories:
-  - name: Containers
-    fields:
-    - containers
-    - initContainers
-    - imagePullSecrets
-    - enableServiceLinks
-  - name: Volumes
-    fields:
-    - volumes
-  - name: Scheduling
-    fields:
-    - nodeSelector
-    - nodeName
-    - affinity
-    - tolerations
-    - schedulerName
-    - runtimeClassName
-    - priorityClassName
-    - priority
-    - topologySpreadConstraints
-  - name: Lifecycle
-    fields:
-    - restartPolicy
-    - terminationGracePeriodSeconds
-    - activeDeadlineSeconds
-    - readinessGates
-  - name: Hostname and Name resolution
-    fields:
-    - hostname
-    - setHostnameAsFQDN
-    - subdomain
-    - hostAliases
-    - dnsConfig
-    - dnsPolicy
-  - name: Hosts namespaces
-    fields:
-    - hostNetwork
-    - hostPID
-    - hostIPC
-    - shareProcessNamespace
-  - name: Service account
-    fields:
-    - serviceAccountName
-    - automountServiceAccountToken
-  - name: Security context
-    fields:
-    - securityContext
-  - name: Beta level
-    fields:
-    - preemptionPolicy
-    - overhead
-  - name: Alpha level
-    fields:
-    - ephemeralContainers
-  - name: Deprecated
-    fields:
-    - serviceAccount
-
- definition: io.k8s.api.core.v1.PodSecurityContext
-  field_categories:
-  - fields:
-    - runAsUser
-    - runAsNonRoot
-    - runAsGroup
-    - supplementalGroups
-    - fsGroup
-    - fsGroupChangePolicy
-    - seccompProfile
-    - seLinuxOptions
-    - sysctls
-    - windowsOptions
-
- definition: io.k8s.api.core.v1.Toleration
-  field_categories:
-  - fields:
-    - key
-    - operator
-    - value
-    - effect
-    - tolerationSeconds
-
- definition: io.k8s.api.core.v1.PodStatus
-  field_categories:
-  - fields:
-    - nominatedNodeName
-    - hostIP
-    - startTime
-    - phase
-    - message
-    - reason
-    - podIP
-    - podIPs
-    - conditions
-    - qosClass
-    - initContainerStatuses
-    - containerStatuses
-    - ephemeralContainerStatuses
-
- definition: io.k8s.api.core.v1.Container
-  field_categories:
-  - fields:
-    - name
-  - name: Image
-    fields:
-    - image
-    - imagePullPolicy
-  - name: Entrypoint
-    fields:
-    - command
-    - args
-    - workingDir
-  - name: Ports
-    fields:
-    - ports
-  - name: Environment variables
-    fields:
-    - env
-    - envFrom
-  - name: Volumes
-    fields:
-    - volumeMounts
-    - volumeDevices
-  - name: Resources
-    fields:
-    - resources
-  - name: Lifecycle
-    fields:
-    - lifecycle
-    - terminationMessagePath
-    - terminationMessagePolicy
-    - livenessProbe
-    - readinessProbe
-    - startupProbe
-  - name: Security Context
-    fields:
-    - securityContext
-  - name: Debugging
-    fields:
-    - stdin
-    - stdinOnce
-    - tty
-
- definition: io.k8s.api.core.v1.Probe
-  field_categories:
-  - fields:
-    - exec
-    - httpGet
-    - tcpSocket
-    - initialDelaySeconds
-    - terminationGracePeriodSeconds
-    - periodSeconds
-    - timeoutSeconds
-    - failureThreshold
-    - successThreshold
-
- definition: io.k8s.api.core.v1.SecurityContext
-  field_categories:
-  - fields:
-    - runAsUser
-    - runAsNonRoot
-    - runAsGroup
-    - readOnlyRootFilesystem
-    - procMount
-    - privileged
-    - allowPrivilegeEscalation
-    - capabilities
-    - seccompProfile
-    - seLinuxOptions
-    - windowsOptions
-
- definition: io.k8s.api.core.v1.ContainerStatus
-  field_categories:
-  - fields:
-    - name
-    - image
-    - imageID
-    - containerID
-    - state
-    - lastState
-    - ready
-    - restartCount
-    - started
-
- definition: io.k8s.api.core.v1.ContainerStateTerminated
-  field_categories:
-  - fields:
-    - containerID
-    - exitCode
-    - startedAt
-    - finishedAt
-    - message
-    - reason
-    - signal
-
- definition: io.k8s.api.core.v1.EphemeralContainer
-  field_categories:
-  - fields:
-    - name
-    - targetContainerName
-  - name: Image
-    fields:
-    - image
-    - imagePullPolicy
-  - name: Entrypoint
-    fields:
-    - command
-    - args
-    - workingDir
-  - name: Environment variables
-    fields:
-    - env
-    - envFrom
-  - name: Volumes
-    fields:
-    - volumeMounts
-    - volumeDevices
-  - name: Lifecycle
-    fields:
-    - terminationMessagePath
-    - terminationMessagePolicy
-  - name: Debugging
-    fields:
-    - stdin
-    - stdinOnce
-    - tty
-  - name: Not allowed
-    fields:
-    - ports
-    - resources
-    - lifecycle
-    - livenessProbe
-    - readinessProbe
-    - securityContext
-    - startupProbe
-
- definition: io.k8s.api.core.v1.ReplicationControllerSpec
-  field_categories:
-  - fields:
-    - selector
-    - template
-    - replicas
-    - minReadySeconds
-
- definition: io.k8s.api.core.v1.ReplicationControllerStatus
-  field_categories:
-  - fields:
-    - replicas
-    - availableReplicas
-    - readyReplicas
-    - fullyLabeledReplicas
-    - conditions
-    - observedGeneration
-
- definition: io.k8s.api.apps.v1.ReplicaSetSpec
-  field_categories:
-  - fields:
-    - selector
-    - template
-    - replicas
-    - minReadySeconds
-
- definition: io.k8s.api.apps.v1.ReplicaSetStatus
-  field_categories:
-  - fields:
-    - replicas
-    - availableReplicas
-    - readyReplicas
-    - fullyLabeledReplicas
-    - conditions
-    - observedGeneration
-
- definition: io.k8s.api.apps.v1.DeploymentSpec
-  field_categories:
-  - fields:
-    - selector
-    - template
-    - replicas
-    - minReadySeconds
-    - strategy
-    - revisionHistoryLimit
-    - progressDeadlineSeconds
-    - paused
-
- definition: io.k8s.api.apps.v1.DeploymentStatus
-  field_categories:
-  - fields:
-    - replicas
-    - availableReplicas
-    - readyReplicas
-    - unavailableReplicas
-    - updatedReplicas
-    - collisionCount
-    - conditions
-    - observedGeneration
-
- definition: io.k8s.api.apps.v1.DeploymentStrategy
-  field_categories:
-  - fields:
-    - type
-    - rollingUpdate
-
- definition: io.k8s.api.apps.v1.StatefulSetSpec
-  field_categories:
-  - fields:
-    - serviceName
-    - selector
-    - template
-    - replicas
-    - updateStrategy
-    - podManagementPolicy
-    - revisionHistoryLimit
-    - volumeClaimTemplates
-    - minReadySeconds
-
- definition: io.k8s.api.apps.v1.StatefulSetUpdateStrategy
-  field_categories:
-  - fields:
-    - type
-    - rollingUpdate
-
- definition: io.k8s.api.apps.v1.StatefulSetStatus
-  field_categories:
-  - fields:
-    - replicas
-    - readyReplicas
-    - currentReplicas
-    - updatedReplicas
-    - availableReplicas
-    - collisionCount
-    - conditions
-    - currentRevision
-    - updateRevision
-    - observedGeneration
-
- definition: io.k8s.api.apps.v1.DaemonSetSpec
-  field_categories:
-  - fields:
-    - selector
-    - template
-    - minReadySeconds
-    - updateStrategy
-    - revisionHistoryLimit
-
- definition: io.k8s.api.apps.v1.DaemonSetUpdateStrategy
-  field_categories:
-  - fields:
-    - type
-    - rollingUpdate
-
- definition: io.k8s.api.apps.v1.DaemonSetStatus
-  field_categories:
-  - fields:
-    - numberReady
-    - numberAvailable
-    - numberUnavailable
-    - numberMisscheduled
-    - desiredNumberScheduled
-    - currentNumberScheduled
-    - updatedNumberScheduled
-    - collisionCount
-    - conditions
-    - observedGeneration
-
- definition: io.k8s.api.batch.v1.JobSpec
-  field_categories:
-  - name: Replicas
-    fields:
-    - template
-    - parallelism
-  - name: Lifecycle
-    fields:
-    - completions
-    - completionMode
-    - backoffLimit
-    - activeDeadlineSeconds
-    - ttlSecondsAfterFinished
-    - suspend
-  - name: Selector
-    fields:
-    - selector
-    - manualSelector
-
- definition: io.k8s.api.batch.v1.JobStatus
-  field_categories:
-  - fields:
-    - startTime
-    - completionTime
-    - active
-    - failed
-    - succeeded
-    - completedIndexes
-    - conditions
-    - uncountedTerminatedPods
-
- definition: io.k8s.api.batch.v1.CronJobSpec
-  field_categories:
-  - fields:
-    - jobTemplate
-    - schedule
-    - concurrencyPolicy
-    - startingDeadlineSeconds
-    - suspend
-    - successfulJobsHistoryLimit
-    - failedJobsHistoryLimit
-
- definition: io.k8s.api.autoscaling.v2beta2.HorizontalPodAutoscalerSpec
-  field_categories:
-  - fields:
-    - maxReplicas
-    - scaleTargetRef
-    - minReplicas
-    - behavior
-    - metrics
-
- definition: io.k8s.api.autoscaling.v2beta2.HPAScalingPolicy
-  field_categories:
-  - fields:
-    - type
-    - value
-    - periodSeconds
-
- definition: io.k8s.api.core.v1.ServiceSpec
-  field_categories:
-  - fields:
-    - selector
-    - ports
-    - type
-    - ipFamilies
-    - ipFamilyPolicy
-    - clusterIP
-    - clusterIPs
-    - externalIPs
-    - sessionAffinity
-    - loadBalancerIP
-    - loadBalancerSourceRanges
-    - loadBalancerClass
-    - externalName
-    - externalTrafficPolicy
-    - internalTrafficPolicy
-    - healthCheckNodePort
-    - publishNotReadyAddresses
-    - sessionAffinityConfig
-    - allocateLoadBalancerNodePorts
-
- definition: io.k8s.api.core.v1.ServicePort
-  field_categories:
-  - fields:
-    - port
-    - targetPort
-    - protocol
-    - name
-    - nodePort
-    - appProtocol
-
- definition: io.k8s.api.core.v1.EndpointSubset
-  field_categories:
-  - fields:
-    - addresses
-    - notReadyAddresses
-    - ports
-
- definition: io.k8s.api.core.v1.EndpointPort
-  field_categories:
-  - fields:
-    - port
-    - protocol
-    - name
-    - appProtocol
-
- definition: io.k8s.api.discovery.v1.EndpointPort
-  field_categories:
-  - fields:
-    - port
-    - protocol
-    - name
-    - appProtocol
-
- definition: io.k8s.api.core.v1.Volume
-  field_categories:
-  - fields:
-    - name
-  - name: Exposed Persistent volumes
-    fields:
-    - persistentVolumeClaim
-  - name: Projections
-    fields:
-    - configMap
-    - secret
-    - downwardAPI
-    - projected
-  - name: Local / Temporary Directory
-    fields:
-    - emptyDir
-    - hostPath
-  - name: Persistent volumes
-    fields:
-    - awsElasticBlockStore
-    - azureDisk
-    - azureFile
-    - cephfs
-    - cinder
-    - csi
-    - fc
-    - flexVolume
-    - flocker
-    - gcePersistentDisk
-    - glusterfs
-    - iscsi
-    - nfs
-    - photonPersistentDisk
-    - portworxVolume
-    - quobyte
-    - rbd
-    - scaleIO
-    - storageos
-    - vsphereVolume
-  - name: Alpha level
-    fields:
-    - ephemeral
-  - name: Deprecated
-    fields:
-    - gitRepo
-
- definition: io.k8s.api.core.v1.ConfigMapVolumeSource
-  field_categories:
-  - fields:
-    - name
-    - optional
-    - defaultMode
-    - items
-
- definition: io.k8s.api.core.v1.SecretVolumeSource
-  field_categories:
-  - fields:
-    - secretName
-    - optional
-    - defaultMode
-    - items
-
- definition: io.k8s.api.core.v1.ConfigMapProjection
-  field_categories:
-  - fields:
-    - name
-    - optional
-    - items
-
- definition: io.k8s.api.core.v1.SecretProjection
-  field_categories:
-  - fields:
-    - name
-    - optional
-    - items
-
- definition: io.k8s.api.core.v1.ProjectedVolumeSource
-  field_categories:
-  - fields:
-    - defaultMode
-    - sources
-
- definition: io.k8s.api.core.v1.PersistentVolumeClaimSpec
-  field_categories:
-  - fields:
-    - accessModes
-    - selector
-    - resources
-    - volumeName
-    - storageClassName
-    - volumeMode
-  - name: Alpha level
-    fields:
-    - dataSource
-    - dataSourceRef
-
- definition: io.k8s.api.core.v1.PersistentVolumeSpec
-  field_categories:
-  - fields:
-    - accessModes
-    - capacity
-    - claimRef
-    - mountOptions
-    - nodeAffinity
-    - persistentVolumeReclaimPolicy
-    - storageClassName
-    - volumeMode
-  - name: Local
-    fields:
-    - hostPath
-    - local
-  - name: Persistent volumes
-    fields:
-    - awsElasticBlockStore
-    - azureDisk
-    - azureFile
-    - cephfs
-    - cinder
-    - csi
-    - fc
-    - flexVolume
-    - flocker
-    - gcePersistentDisk
-    - glusterfs
-    - iscsi
-    - nfs
-    - photonPersistentDisk
-    - portworxVolume
-    - quobyte
-    - rbd
-    - scaleIO
-    - storageos
-    - vsphereVolume
-
- definition: io.k8s.api.rbac.v1.PolicyRule
-  field_categories:
-  - fields:
-    - apiGroups
-    - resources
-    - verbs
-    - resourceNames
-    - nonResourceURLs
-
- definition: io.k8s.api.networking.v1.NetworkPolicySpec
-  field_categories:
-  - fields:
-    - podSelector
-    - policyTypes
-    - ingress
-    - egress
-
- definition: io.k8s.api.networking.v1.NetworkPolicyEgressRule
-  field_categories:
-  - fields:
-    - to
-    - ports
-
- definition: io.k8s.api.networking.v1.NetworkPolicyPort
-  field_categories:
-  - fields:
-    - port
-    - endPort
-    - protocol
-
- definition: io.k8s.api.policy.v1beta1.PodSecurityPolicySpec
-  field_categories:
-  - fields:
-    - runAsUser
-    - runAsGroup
-    - fsGroup
-    - supplementalGroups
-    - seLinux
-    - readOnlyRootFilesystem
-    - privileged
-    - allowPrivilegeEscalation
-    - defaultAllowPrivilegeEscalation
-    - allowedCSIDrivers
-    - allowedCapabilities
-    - requiredDropCapabilities
-    - defaultAddCapabilities
-    - allowedFlexVolumes
-    - allowedHostPaths
-    - allowedProcMountTypes
-    - allowedUnsafeSysctls
-    - forbiddenSysctls
-    - hostIPC
-    - hostNetwork
-    - hostPID
-    - hostPorts
-    - runtimeClass
-    - volumes
-
- definition: io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
-  field_categories:
-  - fields:
-    - name
-    - generateName
-    - namespace
-    - labels
-    - annotations
-  - name: System
-    fields:
-    - finalizers
-    - managedFields
-    - ownerReferences
-  - name: Read-only
-    fields:
-    - creationTimestamp
-    - deletionGracePeriodSeconds
-    - deletionTimestamp
-    - generation
-    - resourceVersion
-    - selfLink
-    - uid
-  - name: Ignored
-    fields:
-    - clusterName
@@ -1,267 +0,0 @@
-# Copyright 2016 The Kubernetes Authors.
-# Copyright 2020 Philippe Martin
-# 
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-# 
-#     http://www.apache.org/licenses/LICENSE-2.0
-# 
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-parts:
- name: Workload Resources
-  chapters:
-  - name: Pod
-    group: ""
-    version: v1
-    otherDefinitions:
-    - PodSpec
-    - Container
-    - EphemeralContainer
-    - Handler
-    - NodeAffinity
-    - PodAffinity
-    - PodAntiAffinity
-    - Probe
-    - PodStatus
-    - PodList
-  - name: PodTemplate
-    group: ""
-    version: v1
-  - name: ReplicationController
-    group: ""
-    version: v1
-  - name: ReplicaSet
-    group: apps
-    version: v1
-  - name: Deployment
-    group: apps
-    version: v1
-  - name: StatefulSet
-    group: apps
-    version: v1
-  - name: ControllerRevision
-    group: apps
-    version: v1
-  - name: DaemonSet
-    group: apps
-    version: v1
-  - name: Job
-    group: batch
-    version: v1
-  - name: CronJob
-    group: batch
-    version: v1
-  - name: HorizontalPodAutoscaler
-    group: autoscaling
-    version: v1
-  - name: HorizontalPodAutoscaler
-    group: autoscaling
-    version: v2beta2
-  - name: PriorityClass
-    group: scheduling.k8s.io
-    version: v1
- name: Service Resources
-  chapters:
-  - name: Service
-    group: ""
-    version: v1
-  - name: Endpoints
-    group: ""
-    version: v1
-  - name: EndpointSlice
-    group: discovery.k8s.io
-    version: v1
-  - name: Ingress
-    group: networking.k8s.io
-    version: v1
-    otherDefinitions:
-    - IngressSpec
-    - IngressBackend
-    - IngressStatus
-    - IngressList
-  - name: IngressClass
-    group: networking.k8s.io
-    version: v1
- name: Config and Storage Resources
-  chapters:
-  - name: ConfigMap
-    group: ""
-    version: v1
-  - name: Secret
-    group: ""
-    version: v1
-  - name: Volume
-    key: io.k8s.api.core.v1.Volume
-    otherDefinitions:
-    - DownwardAPIVolumeFile
-    - KeyToPath
-  - name: PersistentVolumeClaim
-    group: ""
-    version: v1
-  - name: PersistentVolume
-    group: ""
-    version: v1
-  - name: StorageClass
-    group: storage.k8s.io
-    version: v1
-  - name: VolumeAttachment
-    group: storage.k8s.io
-    version: v1
-  - name: CSIDriver
-    group: storage.k8s.io
-    version: v1
-  - name: CSINode
-    group: storage.k8s.io
-    version: v1
-  - name: CSIStorageCapacity
-    group: storage.k8s.io
-    version: v1beta1
- name: Authentication Resources
-  chapters:
-  - name: ServiceAccount
-    group: ""
-    version: v1
-  - name: TokenRequest
-    group: authentication.k8s.io
-    version: v1
-  - name: TokenReview
-    group: authentication.k8s.io
-    version: v1
-  - name: CertificateSigningRequest
-    group: certificates.k8s.io
-    version: v1
- name: Authorization Resources
-  chapters:
-  - name: LocalSubjectAccessReview
-    group: authorization.k8s.io
-    version: v1
-  - name: SelfSubjectAccessReview
-    group: authorization.k8s.io
-    version: v1
-  - name: SelfSubjectRulesReview
-    group: authorization.k8s.io
-    version: v1
-  - name: SubjectAccessReview
-    group: authorization.k8s.io
-    version: v1
-  - name: ClusterRole
-    group: rbac.authorization.k8s.io
-    version: v1
-  - name: ClusterRoleBinding
-    group: rbac.authorization.k8s.io
-    version: v1
-  - name: Role
-    group: rbac.authorization.k8s.io
-    version: v1
-  - name: RoleBinding
-    group: rbac.authorization.k8s.io
-    version: v1
- name: Policy Resources
-  chapters:
-  - name: LimitRange
-    group: ""
-    version: v1
-  - name: ResourceQuota
-    group: ""
-    version: v1
-  - name: NetworkPolicy
-    group: networking.k8s.io
-    version: v1
-  - name: PodDisruptionBudget
-    group: policy
-    version: v1
-  - name: PodSecurityPolicy
-    group: policy
-    version: v1beta1
- name: Extend Resources
-  chapters:
-  - name: CustomResourceDefinition
-    group: apiextensions.k8s.io
-    version: v1
-    otherDefinitions:
-    - CustomResourceDefinitionSpec
-    - JSONSchemaProps
-    - CustomResourceDefinitionStatus
-    - CustomResourceDefinitionList
-  - name: MutatingWebhookConfiguration
-    group: admissionregistration.k8s.io
-    version: v1
-  - name: ValidatingWebhookConfiguration
-    group: admissionregistration.k8s.io
-    version: v1
- name: Cluster Resources
-  chapters:
-  - name: Node
-    group: ""
-    version: v1
-  - name: Namespace
-    group: ""
-    version: v1
-  - name: Event
-    group: events.k8s.io
-    version: v1
-  - name: APIService
-    group: apiregistration.k8s.io
-    version: v1
-  - name: Lease
-    group: coordination.k8s.io
-    version: v1
-  - name: RuntimeClass
-    group: node.k8s.io
-    version: v1
-  - name: FlowSchema
-    group: flowcontrol.apiserver.k8s.io
-    version: v1beta1
-  - name: PriorityLevelConfiguration
-    group: flowcontrol.apiserver.k8s.io
-    version: v1beta1
-  - name: Binding
-    group: ""
-    version: v1
-  - name: ComponentStatus
-    group: ""
-    version: v1
- name: Common Definitions
-  chapters:
-  - name: DeleteOptions
-    key: io.k8s.apimachinery.pkg.apis.meta.v1.DeleteOptions
-  - name: LabelSelector
-    key: io.k8s.apimachinery.pkg.apis.meta.v1.LabelSelector
-  - name: ListMeta
-    key: io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta
-  - name: LocalObjectReference
-    key: io.k8s.api.core.v1.LocalObjectReference
-  - name: NodeSelectorRequirement
-    key: io.k8s.api.core.v1.NodeSelectorRequirement
-  - name: ObjectFieldSelector
-    key: io.k8s.api.core.v1.ObjectFieldSelector
-  - name: ObjectMeta
-    key: io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta
-  - name: ObjectReference
-    key: io.k8s.api.core.v1.ObjectReference
-  - name: Patch
-    key: io.k8s.apimachinery.pkg.apis.meta.v1.Patch
-  - name: Quantity
-    key: "io.k8s.apimachinery.pkg.api.resource.Quantity"
-  - name: ResourceFieldSelector
-    key: io.k8s.api.core.v1.ResourceFieldSelector
-  - name: Status
-    key: io.k8s.apimachinery.pkg.apis.meta.v1.Status
-  - name: TypedLocalObjectReference
-    key: io.k8s.api.core.v1.TypedLocalObjectReference
-skippedResources:
- APIGroup
- APIGroupList
- APIResourceList
- APIVersions
- Eviction
- Scale
- Status
- StorageVersion
- StorageVersionList
@@ -1,83 +0,0 @@
---
-api_metadata:
-  apiVersion: "{{.ApiVersion}}"
-  import: "{{.Import}}"
-  kind: "{{.Kind}}"
-content_type: "api_reference"
-description: "{{.Metadata.Description}}"
-title: "{{.Metadata.Title}}"
-weight: {{.Metadata.Weight}}
-auto_generated: true
---
-
-<!--
-The file is auto-generated from the Go source code of the component using a generic
-[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
-to generate the reference documentation, please read
-[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
-To update the reference content, please follow the 
-[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
-guide. You can file document formatting bugs against the
-[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
-
-{{if .ApiVersion}}`apiVersion: {{.ApiVersion}}`{{end}}
-
-{{if .Import}}`import "{{.Import}}"`{{end}}
-
-{{range .Sections}}
-{{.Description | replace "<" "\\<" }}
-
-<hr>
-{{range .Fields}}
-{{ ""  | indent .Indent | indent .Indent}}- {{.Name}}{{if .Value}}: {{.Value}}{{end}}
-{{if .Description}}
-{{.Description | replace "<" "\\<" | indent 2 | indent .Indent | indent .Indent}}
-{{- end}}
-{{if .TypeDefinition}}
-{{ ""  | indent .Indent | indent .Indent}}  <a name="{{.Type}}"></a>
-{{.TypeDefinition | indent 2 | indent .Indent | indent .Indent}}
-{{end}}
-{{- end}}{{/* range .Fields */}}
-
-{{range .FieldCategories}}
-### {{.Name}} {#{{"-" | regexReplaceAll "[^a-zA-Z0-9]+" .Name }}}{{/* explicitly set fragment to keep capitalization */}}
-
-{{range .Fields}}
-{{ ""  | indent .Indent | indent .Indent}}- {{.Name}}{{if .Value}}: {{.Value}}{{end}}
-{{if .Description}}
-{{.Description | replace "<" "\\<" | indent 2 | indent .Indent | indent .Indent}}
-{{- end}}
-{{if .TypeDefinition}}
-{{ ""  | indent .Indent | indent .Indent}}  <a name="{{.Type}}"></a>
-{{.TypeDefinition | indent 2 | indent .Indent | indent .Indent}}
-{{end}}
-{{- end}}{{/* range .Fields */}}
-
-{{- end}}{{/* range .FieldCategories */}}
-
-{{range .Operations}}
-
-### `{{.Verb}}` {{.Title}}
-
-#### HTTP Request
-
-{{.RequestMethod}} {{.RequestPath}}
-
-#### Parameters
-
-{{range .Parameters}}
- {{.Title}}
-
-{{.Description | indent 2}}
-
-{{end}}{{/* range .Parameters */}}
-
-#### Response
-
-{{range .Responses}}
-{{.Code}}{{if .Type}} ({{.Type}}){{end}}: {{.Description}}
-{{end}}{{/* range .Responses */}}
-
-{{- end}}{{/* range .Operations */}}
-{{- end}}{{/* range .Sections */}}
@@ -1,85 +0,0 @@
---
-api_metadata:
-  apiVersion: "{{.ApiVersion}}"
-  import: "{{.Import}}"
-  kind: "{{.Kind}}"
-content_type: "api_reference"
-description: "{{.Metadata.Description}}"
-title: "{{.Metadata.Title}}"
-weight: {{.Metadata.Weight}}
-auto_generated: true
---
-
-<!--
-The file is auto-generated from the Go source code of the component using a generic
-[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
-to generate the reference documentation, please read
-[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
-To update the reference content, please follow the 
-[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
-guide. You can file document formatting bugs against the
-[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
-
-{{if .ApiVersion}}`apiVersion: {{.ApiVersion}}`{{end}}
-
-{{if .Import}}`import "{{.Import}}"`{{end}}
-
-{{range .Sections}}
-## {{.Name}} {#{{"-" | regexReplaceAll "[^a-zA-Z0-9]+" .Name }}}{{/* explicitly set fragment to keep capitalization */}}
-
-{{.Description | replace "<" "\\<" }}
-
-<hr>
-{{range .Fields}}
-{{ ""  | indent .Indent | indent .Indent}}- {{.Name}}{{if .Value}}: {{.Value}}{{end}}
-{{if .Description}}
-{{.Description | replace "<" "\\<" | indent 2 | indent .Indent | indent .Indent}}
-{{- end}}
-{{if .TypeDefinition}}
-{{ ""  | indent .Indent | indent .Indent}}  <a name="{{.Type}}"></a>
-{{.TypeDefinition | indent 2 | indent .Indent | indent .Indent}}
-{{end}}
-{{- end}}{{/* range .Fields */}}
-
-{{range .FieldCategories}}
-### {{.Name}}
-
-{{range .Fields}}
-{{ ""  | indent .Indent | indent .Indent}}- {{.Name}}{{if .Value}}: {{.Value}}{{end}}
-{{if .Description}}
-{{.Description | replace "<" "\\<" | indent 2 | indent .Indent | indent .Indent}}
-{{- end}}
-{{if .TypeDefinition}}
-{{ ""  | indent .Indent | indent .Indent}}  <a name="{{.Type}}"></a>
-{{.TypeDefinition | indent 2 | indent .Indent | indent .Indent}}
-{{end}}
-{{- end}}{{/* range .Fields */}}
-
-{{- end}}{{/* range .FieldCategories */}}
-
-{{range .Operations}}
-
-### `{{.Verb}}` {{.Title}}
-
-#### HTTP Request
-
-{{.RequestMethod}} {{.RequestPath}}
-
-#### Parameters
-
-{{range .Parameters}}
- {{.Title}}
-
-{{.Description | indent 2}}
-
-{{end}}{{/* range .Parameters */}}
-
-#### Response
-
-{{range .Responses}}
-{{.Code}}{{if .Type}} ({{.Type}}){{end}}: {{.Description}}
-{{end}}{{/* range .Responses */}}
-
-{{- end}}{{/* range .Operations */}}
-{{- end}}{{/* range .Sections */}}
@@ -1,17 +0,0 @@
---
-title: "{{.Title}}"
-weight: {{.Weight}}
-auto_generated: true
---
-
-<!--
-The file is auto-generated from the Go source code of the component using a generic
-[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
-to generate the reference documentation, please read
-[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
-To update the reference content, please follow the 
-[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
-guide. You can file document formatting bugs against the
-[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
-
@@ -1,61 +0,0 @@
---
-layout: blog
-title: "{{ replace .Name "-" " " | title }}"
-date: {{ .Date }}
-draft: true
-slug: <seo-friendly-version-of-title-separated-by-dashes>
---
-
-**Author:** <your name> (<your organization name>), <another author's name> (<their organization>)
-
-<!--  
-Instructions:
- Replace these instructions and the following text with your content.
- Replace `<angle bracket placeholders>` with actual values. For example, you would update `date: <yyyy>-<mm>-<dd>` to look something like `date: 2021-10-21`.
- For convenience, use third-party tools to author and collaborate on your content.
- To save time and effort in reviews, check your content's spelling, grammar, and style before contributing.
- Feel free to ask for assistance in the Kubernetes Slack channel, [#sig-docs-blog](https://kubernetes.slack.com/archives/CJDHVD54J).
-->
-
-Replace this first line of your content with one to three sentences that summarize the blog post.
-
-## This is a section heading
-
-To help the reader, organize your content into sections that contain about three to six paragraphs.
-
-If you're documenting commands, separate the commands from the outputs, like this:
-
-1. Verify that the Secret exists by running the following command:
-
-      ```shell
-      kubectl get secrets
-      ```
-
-      The response should be like this:
-
-      ```shell
-      NAME                    TYPE                                  DATA   AGE
-      mysql-pass-c57bb4t7mf   Opaque                                1      9s
-      ```
-
-You're free to create any sections you like. Below are a few common patterns we see at the end of blog posts.
-
-## What’s next?
-
-This optional section describes the future of the thing you've just described in the post.
-
-## How can I learn more?
-
-This optional section provides links to more information. Please avoid promoting and over-represent your organization.
-
-## How do I get involved?
-
-An optional section that links to resources for readers to get involved, and acknowledgments of individual contributors, such as:
-
-* [The name of a channel on Slack, #a-channel](https://<a-workspace>.slack.com/messages/<a-channel>)
-
-* [A link to a "contribute" page with more information](<https://github.com/kubernetes/community/blob/master/sig-storage/README.md#contact>).
-
-* Acknowledgements and thanks to the contributors. <person's name> ([<github id>](https://github.com/<github id>)) who did X, Y, and Z.
-
-* Those interested in getting involved with the design and development of <project>, join the [<name of the SIG>](https://github.com/project/community/tree/master/<sig-group>). We’re rapidly growing and always welcome new contributors.
@@ -88,20 +88,6 @@ footer {
  }
 }

-main {
-  .button {
-    display: inline-block;
-    border-radius: 6px;
-    padding: 6px 20px;
-    line-height: 1.3rem;
-    color: white;
-    background-color: $blue;
-    text-decoration: none;
-    font-size: 1rem;
-    border: 0px;
-  }
-}
-
 // HEADER

 #hamburger {
@@ -810,12 +796,6 @@ section#cncf {
  }
 }

-// Header filler size adjustment
-
-.header-hero.filler {
-  height: $hero-padding-top;
-}
-
 // Docs specific

 #editPageButton {
@@ -858,21 +838,13 @@ section#cncf {

 /* DOCUMENTATION */

-// nav-tabs and tab-content
-.nav-tabs {
-  border-bottom: none !important;
-}
-
-.td-content .tab-content .highlight {
-  margin: 0;
-}
-
-.tab-pane {
-  border-radius: 0.25rem;
-  padding: 0 16px 16px;
-
-  border: 1px solid #dee2e6;
-  &:first-of-type.active {
-    border-top-left-radius: 0;
-  }
+body.td-documentation {
+    header > .header-filler {
+      height: $hero-padding-top;
+      background-color: black;
+    }
+    /* Special case for if an announcement is active */
+    header section#announcement ~ .header-filler {
+      display: none;
+    }
 }
@@ -26,10 +26,6 @@ $announcement-size-adjustment: 8px;
  }
 }

-.header-hero #quickstartButton.button {
-  margin-top: 1em;
-}
-
 section {
  .main-section {
    @media only screen and (min-width: 1024px) {
@@ -38,11 +34,8 @@ section {
  }
 }

-body {
-  header + .td-outer {
-    min-height: 50vh;
-    height: auto;
-  }
+.td-outer {
+  padding: 0 !important;
 }


@@ -78,22 +71,6 @@ body.td-404 main .error-details {
  max-width: 80%;
  border: 1px solid rgb(222, 226, 230);
  border-radius: 5px;
-  margin-bottom: 1rem;
-  padding-top: 1rem;
-  padding-bottom: 1rem;
-
-  // mermaid diagram - sequence diagram
-  .actor {
-    fill: #326ce5 !important;
-  }
-  text.actor {
-    font-size: 18px !important;
-    stroke: white !important;
-    fill: white !important;
-  }
-  .activation0 {
-    fill: #c9e9ec !important;
-  }
 }

 /* HEADER */
@@ -320,68 +297,37 @@ main {

 // blockquotes and callouts

-body {
-  .alert {
-    // Override Docsy styles
+.td-content, body {
+  blockquote.callout {
    padding: 0.4rem 0.4rem 0.4rem 1rem;
-    border-top: 1px solid #eee;
-    border-bottom: 1px solid #eee;
-    border-right: 1px solid #eee;
-    border-radius: 0.25em;
-    border-left-width: 0.5em; // fallback in case calc() is missing
+    border: 1px solid #eee;
+    border-left-width: 0.5em;
    background: #fff;
    color: #000;
    margin-top: 0.5em;
    margin-bottom: 0.5em;
  }
-  // Set minimum width and radius for alert color
-  .alert {
-      border-left-width: calc(max(0.5em, 4px));
-      border-top-left-radius: calc(max(0.5em, 4px));
-      border-bottom-left-radius: calc(max(0.5em, 4px));
+  blockquote.callout {
+    border-radius: calc(1em/3);
  }
-  .alert.callout.caution {
+  .callout.caution {
    border-left-color: #f0ad4e;
  }
-  .alert.callout.note {
+
+  .callout.note {
    border-left-color: #428bca;
  }
-  .alert.callout.warning {
+
+  .callout.warning {
    border-left-color: #d9534f;
  }
-  .alert.third-party-content {
-    border-left-color: #444;
-  }

-  h1:first-of-type + .alert.callout {
+  h1:first-of-type + blockquote.callout {
    margin-top: 1.5em;
  }
 }

-// Special color for third party content disclaimers
-.alert.third-party-content { border-left-color: #222 };
-
-// Highlight disclaimer when targeted as a fragment
-
-#third-party-content-disclaimer {
-  color: #000;
-  background: #f8f9fa;
-  transition: all 0.5s ease;
-}
-
-@keyframes disclaimer-highlight {
-  from { background: #f8f922; color: #000; }
-  50% { background: #f8f944; color: #000; }
-  to { background: #f8f9cb; color: #000; }
-}
-
-#third-party-content-disclaimer:target {
-  color: #000;
-  animation: disclaimer-highlight 1.25s ease;
-  background: #f8f9cb;
-}
-
-.deprecation-warning, .pageinfo.deprecation-warning {
+.deprecation-warning {
    padding: 20px;
    margin: 20px 0;
    background-color: #faf5b6;
@@ -392,12 +338,6 @@ body.td-home .deprecation-warning, body.td-blog .deprecation-warning, body.td-do
    border-radius: 3px;
 }

-
-.td-documentation .td-content > .highlight {
-  max-width: initial;
-  width: 100%;
-}
-
 body.td-home #deprecation-warning {
    max-width: 1000px;
    margin-top: 2.5rem;
@@ -488,7 +428,7 @@ body.cid-community > #deprecation-warning > .deprecation-warning > * {
 .td-sidebar__inner {
  form.td-sidebar__search {

-    .td-sidebar__toggle {
+    button.td-sidebar__toggle {
      &:hover {
        color: #000000;
      }
@@ -526,6 +466,10 @@ main.content {

 .td-blog {

+  .td-sidebar-nav {
+    max-height: calc(100vh - 8rem);
+  }
+
  .widget-link {
    margin-bottom: 1rem;

@@ -568,6 +512,34 @@ main.content {
  }
 }

+/* ANNOUNCEMENTS */
+section#fp-announcement ~ .header-hero {
+    padding: $announcement-size-adjustment  0;
+
+    > div {
+       margin-top: $announcement-size-adjustment;
+       margin-bottom: $announcement-size-adjustment;
+    }
+
+    h1, h2, h3, h4, h5 {
+      margin: $announcement-size-adjustment 0;
+    }
+}
+
+section#announcement ~ .header-hero {
+    padding: #{$announcement-size-adjustment / 2} 0;
+
+    > div {
+       margin-top: #{$announcement-size-adjustment / 2};
+       margin-bottom: #{$announcement-size-adjustment / 2};
+       padding-bottom: #{$announcement-size-adjustment / 2};
+    }
+
+    h1, h2, h3, h4, h5 {
+      margin: #{$announcement-size-adjustment / 2} 0;
+    }
+}
+
 /* DOCUMENTATION */

 /* Don't show lead text */
@@ -590,199 +562,3 @@ body.td-documentation {
  color: black;
  text-decoration: none !important;
 }
-
-@media print {
-  /* Do not print announcements */
-  #announcement {
-    display: none;
-  }
-}
-
-#announcement {
-  > * {
-    color: inherit;
-    background: transparent;
-  }
-
-  a {
-    color: inherit;
-    border-bottom: 1px solid #fff;
-  }
-
-  a:hover {
-    color: inherit;
-    border-bottom: none;
-  }
-}
-
-.header-hero {
-  padding-top: 40px;
-}
-
-#announcement {
-  .announcement-main {
-    margin-left: auto;
-    margin-right: auto;
-    margin-bottom: 0px;
-
-    // for padding-top see _size.scss
-    padding-bottom: calc(max(2em, 2rem));
-
-    max-width: calc(min(1200px - 8em, 80vw));
-  }
-
-
-  /* always white */
-  h1, h2, h3, h4, h5, h6, p * {
-    color: #ffffff;
-    background: transparent;
-
-    img.event-logo {
-      display: inline-block;
-      max-height: calc(min(80px, 8em));
-      max-width: calc(min(240px, 33vw));
-      float: right;
-    }
-  }
-}
-
-#announcement + .header-hero {
-  padding-top: 2em;
-}
-
-// Extra padding for anything except wide viewports
-@media (min-width: 992px) {
-  #announcement aside { // more specific
-    .announcement-main {
-      padding-top: calc(max(8em, 8rem));
-    }
-  }
-}
-
-@media (max-width: 768px) {
-  #announcement {
-    padding-top: 4rem;
-    padding-bottom: 4rem;
-    .announcement-main, aside .announcement-main {
-      padding-top: calc(min(2rem,2em));
-    }
-  }
-}
-
-@media (max-width: 480px) {
-  #announcement {
-    padding-bottom: 0.5em;
-  }
-  #announcement aside {
-    h1, h2, h3, h4, h5, h6 {
-      img.event-logo {
-        margin-left: auto;
-        margin-right: auto;
-        margin-bottom: 0.75em;
-        display: block;
-        max-height: initial;
-        max-width: calc(min(calc(100vw - 2em), 240px));
-        float: initial;
-      }
-    }
-  }
-}
-
-#announcement + .header-hero.filler {
-  display: none;
-}
-
-@media (min-width: 768px) {
-  #announcement + .header-hero {
-    display: none;
-  }
-}
-
-
-// Match Docsy-imposed max width on text body
-@media (min-width: 1200px) {
-  body.td-blog main .td-content > figure {
-    max-width: 80%;
-  }
-}
-
-.td-content {
-  table code {
-    background-color: inherit !important;
-    color: inherit !important;
-    font-size: inherit !important;
-  }
-}
-
-/* Force size constraints on figures */
-figure {
-  &.diagram-small img {
-    max-height: clamp(20mm,12em,80vh);
-    margin-left: auto;
-    margin-right: auto;
-    display: block;
-  }
-  &.diagram-medium img {
-    max-height: clamp(25mm,20em,80vh);
-    margin-left: auto;
-    margin-right: auto;
-    display: block;
-  }
-  &.diagram-large img {
-    max-width: clamp(0vw, 95vw, 100%);
-    max-height: calc(80vh - 8rem);
-  }
-}
-
-@media only screen and (min-width: 768px) {
-  figure {
-    &.diagram-small, &.diagram-medium {
-      max-width: 80%;
-    }
-    &.diagram-large {
-      max-width: 100%;
-      width: 100%;
-    }
-    &.diagram-small img {
-      max-width: clamp(30rem, 45ch, 100mm);
-    }
-    &.diagram-medium img {
-      max-width: clamp(50rem, 20ch, 160mm);
-    }
-    &.diagram-large img {
-      max-width: clamp(25vw, 95vw, 100%);
-      max-height: calc(100vh - 10rem);
-    }
-  }
-}
-
-// Indent definition lists
-dl {
-  padding-left: 1.5em;
-
-  // Add vertical space before definitions
-  > *:not(dt) + dt, dt:first-child {
-    margin-top: 1.5em;
-  }
-}
-
-.release-details {
-  padding-left: 2em;
-
-  > :not(p) {
-    font-size: 1.125em;
-  }
-
-  .release-inline-heading, .release-inline-value {
-    display: inline-block
-  }
-
-  .release-inline-value {
-    padding-left: 0.25em;
-  }
-
-  p {
-     margin-top: 1em;
-     margin-bottom: 1em;
-  }
-}
@@ -18,11 +18,3 @@ section,
  line-height: $vendor-strip-height;
  font-size: $vendor-strip-font-size;
 }
-
-#announcement {
-  min-height: $hero-padding-top;
-
-  .announcement-main {
-    padding-top: calc(max(8em, 8rem, #{$hero-padding-top} / 3));
-  }
-}
@@ -77,6 +77,7 @@ $feature-box-div-width: 45%;
      position: relative;
      clear: both;
      display: table;
+      height: 160px;

      .content {
        display: table-cell;
@@ -123,7 +124,6 @@ $feature-box-div-width: 45%;
          position: relative;
          display: block;
          float: none;
-          text-align: center;
          max-width: 100%;
          transform: none;
        }
@@ -1,25 +0,0 @@
-# See https://cloud.google.com/cloud-build/docs/build-config
-
-# this must be specified in seconds. If omitted, defaults to 600s (10 mins)
-timeout: 1200s
-# this prevents errors if you don't use both _GIT_TAG and _PULL_BASE_REF,
-# or any new substitutions added in the future.
-options:
-  substitution_option: ALLOW_LOOSE
-steps:
-    # It's fine to bump the tag to a recent version, as needed
-  - name: "gcr.io/k8s-staging-test-infra/gcb-docker-gcloud:v20210917-12df099d55"
-    entrypoint: make
-    env:
-      - DOCKER_CLI_EXPERIMENTAL=enabled
-      - TAG=$_GIT_TAG
-      - BASE_REF=$_PULL_BASE_REF
-    args:
-      - container-image
-substitutions:
-  # _GIT_TAG will be filled with a git-based tag for the image, of the form vYYYYMMDD-hash, and
-  # can be used as a substitution
-  _GIT_TAG: "12345"
-  # _PULL_BASE_REF will contain the ref that was pushed to to trigger this build -
-  # a branch like 'master' or 'release-0.2', or a tag like 'v0.2'.
-  _PULL_BASE_REF: "master"
@@ -13,7 +13,7 @@ disableBrowserError = true

 disableKinds = ["taxonomy", "taxonomyTerm"]

-ignoreFiles = [ "(?:^|/)OWNERS$", "README[-]+[a-z]*\\.md", "^node_modules$", "content/en/docs/doc-contributor-tools" ]
+ignoreFiles = [ "^OWNERS$", "README[-]+[a-z]*\\.md", "^node_modules$", "content/en/docs/doc-contributor-tools" ]

 timeout = 3000

@@ -91,7 +91,7 @@ blog = "/:section/:year/:month/:day/:slug/"
 [outputs]
 home = [ "HTML", "RSS", "HEADERS" ]
 page = [ "HTML"]
-section = [ "HTML", "print" ]
+section = [ "HTML"]

 # Add a "text/netlify" media type for auto-generating the _headers file
 [mediaTypes]
@@ -123,7 +123,6 @@ id = "UA-00000000-0"
 [params]
 copyright_k8s = "The Kubernetes Authors"
 copyright_linux =  "Copyright © 2020 The Linux Foundation ®."
-
 # privacy_policy = "https://policies.google.com/privacy"

 # First one is picked as the Twitter card image if not set on page.
@@ -139,13 +138,13 @@ time_format_default = "January 02, 2006 at 3:04 PM PST"
 description = "Production-Grade Container Orchestration"
 showedit = true

-latest = "v1.23"
+latest = "v1.19"

-fullversion = "v1.22.4"
-version = "v1.22"
-githubbranch = "v1.22.4"
-docsbranch = "release-1.22"
-deprecated = true
+fullversion = "v1.19.0"
+version = "v1.19"
+githubbranch = "master"
+docsbranch = "master"
+deprecated = false
 currentUrl = "https://kubernetes.io/docs/home/"
 nextUrl = "https://kubernetes-io-vnext-staging.netlify.com/"

@@ -155,6 +154,11 @@ githubWebsiteRaw = "raw.githubusercontent.com/kubernetes/website"
 # GitHub repository link for editing a page and opening issues.
 github_repo = "https://github.com/kubernetes/website"

+# param for displaying an announcement block on every page.
+# See /i18n/en.toml for message text and title.
+announcement = true
+announcement_bg = "#3f0374" # choose a dark color – text is white
+
 #Searching
 k8s_search = true

@@ -179,46 +183,45 @@ js = [
 ]

 [[params.versions]]
-fullversion = "v1.23.0"
-version = "v1.23"
-githubbranch = "v1.23.0"
-docsbranch = "main"
+fullversion = "v1.19.0"
+version = "v1.19"
+githubbranch = "v1.19.0"
+docsbranch = "master"
 url = "https://kubernetes.io"

 [[params.versions]]
-fullversion = "v1.22.4"
-version = "v1.22"
-githubbranch = "v1.22.4"
-docsbranch = "release-1.22"
-url = "https://v1-22.docs.kubernetes.io"
+fullversion = "v1.18.8"
+version = "v1.18"
+githubbranch = "v1.18.8"
+docsbranch = "release-1.18"
+url = "https://v1-18.docs.kubernetes.io"

 [[params.versions]]
-fullversion = "v1.21.7"
-version = "v1.21"
-githubbranch = "v1.21.7"
-docsbranch = "release-1.21"
-url = "https://v1-21.docs.kubernetes.io"
+fullversion = "v1.17.11"
+version = "v1.17"
+githubbranch = "v1.17.11"
+docsbranch = "release-1.17"
+url = "https://v1-17.docs.kubernetes.io"

 [[params.versions]]
-fullversion = "v1.20.13"
-version = "v1.20"
-githubbranch = "v1.20.13"
-docsbranch = "release-1.20"
-url = "https://v1-20.docs.kubernetes.io"
+fullversion = "v1.16.14"
+version = "v1.16"
+githubbranch = "v1.16.14"
+docsbranch = "release-1.16"
+url = "https://v1-16.docs.kubernetes.io"

 [[params.versions]]
-fullversion = "v1.19.16"
-version = "v1.19"
-githubbranch = "v1.19.16"
-docsbranch = "release-1.19"
-url = "https://v1-19.docs.kubernetes.io"
+fullversion = "v1.15.12"
+version = "v1.15"
+githubbranch = "v1.15.12"
+docsbranch = "release-1.15"
+url = "https://v1-15.docs.kubernetes.io"
+

 # User interface configuration
 [params.ui]
 # Enable to show the side bar menu in its compact state.
 sidebar_menu_compact = false
-# https://github.com/gohugoio/hugo/issues/8918#issuecomment-903314696
-sidebar_cache_limit = 1
 #  Set to true to disable breadcrumb navigation.
 breadcrumb_disable = false
 #  Set to true to hide the sidebar search box (the top nav search box will still be displayed if search is enabled)
@@ -401,15 +404,15 @@ time_format_blog = "02.01.2006"
 # A list of language codes to look for untranslated content, ordered from left to right.
 language_alternatives = ["en"]

-[languages.pt-br]
+[languages.pt]
 title = "Kubernetes"
 description = "Orquestração de contêineres em nível de produção"
 languageName ="Português"
 weight = 9
-contentDir = "content/pt-br"
+contentDir = "content/pt"
 languagedirection = "ltr"

-[languages.pt-br.params]
+[languages.pt.params]
 time_format_blog = "02.01.2006"
 # A list of language codes to look for untranslated content, ordered from left to right.
 language_alternatives = ["en"]
@@ -9,7 +9,7 @@ cid: home
 {{% blocks/feature image="flower" %}}
 ### [Kubernetes (K8s)]({{< relref "/docs/concepts/overview/what-is-kubernetes" >}}) ist ein Open-Source-System zur Automatisierung der Bereitstellung, Skalierung und Verwaltung von containerisierten Anwendungen.

-Es gruppiert Container, aus denen sich eine Anwendung zusammensetzt, in logische Einheiten, um die Verwaltung und Erkennung zu erleichtern. Kubernetes baut auf [15 Jahre Erfahrung in Bewältigung von Produktions-Workloads bei Google](http://queue.acm.org/detail.cfm?id=2898444), kombiniert mit Best-of-Breed-Ideen und Praktiken aus der Community.
+Es gruppiert Container, aus denen sich eine Anwendung zusammensetzt, in logische Einheiten, um die Verwaltung und Erkennung zu erleichtern. Kubernetes baut auf [15 Jahre Erfahrung in Bewältigung von Produktions-Workloads bei Google] (http://queue.acm.org/detail.cfm?id=2898444), kombiniert mit Best-of-Breed-Ideen und Praktiken aus der Community.
 {{% /blocks/feature %}}

 {{% blocks/feature image="scalable" %}}
@@ -42,12 +42,12 @@ Kubernetes ist Open Source und bietet Dir die Freiheit, die Infrastruktur vor Or
        <button id="desktopShowVideoButton" onclick="kub.showVideo()">Video ansehen</button>
        <br>
        <br>
-        <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/?utm_source=kubernetes.io&utm_medium=nav&utm_campaign=kccncna21" button id="desktopKCButton">Besuche die KubeCon North America vom 11. bis 15. Oktober 2021</a>
+        <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/?utm_source=kubernetes.io&utm_medium=nav&utm_campaign=kccnceu20" button id="desktopKCButton">Besuche die KubeCon - 13-16 August 2020 in Amsterdam</a>
        <br>
        <br>
        <br>
        <br>
-        <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe-2022/?utm_source=kubernetes.io&utm_medium=nav&utm_campaign=kccnceu22" button id="desktopKCButton">Besuche die KubeCon Europe vom 17. bis 20. Mai 2022</a>
+        <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/?utm_source=kubernetes.io&utm_medium=nav&utm_campaign=kccncna20" button id="desktopKCButton">Besuche die KubeCon - 17-20 November 2020 in Boston</a>
 </div>
 <div id="videoPlayer">
    <iframe data-url="https://www.youtube.com/embed/H06qrNmGqyE?autoplay=1" frameborder="0" allowfullscreen></iframe>
@@ -57,4 +57,4 @@ Kubernetes ist Open Source und bietet Dir die Freiheit, die Infrastruktur vor Or

 {{< blocks/kubernetes-features >}}

-{{< blocks/case-studies >}}
+{{< blocks/case-studies >}}
@@ -4,253 +4,58 @@ layout: basic
 cid: community
 ---

-<div class="newcommunitywrapper">
-<div class="banner1">
-  <img src="/images/community/kubernetes-community-final-02.jpg" alt="Kubernetes-Konferenz Galerie" style="width:100%;padding-left:0px" class="desktop">
-  <img src="/images/community/kubernetes-community-02-mobile.jpg" alt="Kubernetes-Konferenz Galerie" style="width:100%;padding-left:0px" class="mobile">
-</div>
+<section id="mainContent">
+    <main>
+        <div class="content">
+            <h3>Die Gewissheit, dass Kubernetes überall und für alle gut funktioniert.</h3>
+            <p>Verbinden Sie sich mit der Kubernetes-Community in unserem <a href="http://slack.k8s.io/">Slack Kanal</a>, <a href="https://discuss.kubernetes.io/">Diskussionsforum</a>, oder beteiligen Sie sich an der <a href="https://groups.google.com/forum/#!forum/kubernetes-dev"> Kubernetes-dev-Google-Gruppe</a>. Eine wöchentliches Community-Meeting findet per Videokonferenz statt, um den Stand der Dinge zu diskutieren, folgen Sie
+		<a href="https://github.com/kubernetes/community/blob/master/events/community-meeting.md">diesen Anweisungen</a> für Informationen wie Sie teilnehmen können.</p>
+            <p>Sie können Kubernetes auch auf der ganzen Welt über unsere
+                <a href="https://www.meetup.com/topics/kubernetes/">Kubernetes Meetup Community</a> und der
+                <a href="https://www.meetup.com/Kubernetes-Cloud-Native-Online-Meetup/">Kubernetes Cloud Native Meetup Community</a> beitreten.</p>
+          </div>
+        <div class="content">
+            <h3>Special Interest Groups (SIGs)</h3>
+            <p>Haben Sie ein besonderes Interesse daran, wie Kubernetes mit einer anderen Technologie arbeitet?  Werfen Sie einen Blick auf unsere kontinuierlich wachsende
+                <a href="https://git.k8s.io/community/sig-list.md">Listen von SIGs</a>, von AWS und Openstack bis hin zu Big Data und Skalierbarkeit, es gibt einen Platz für Sie, an dem Sie mitwirken können, und Anweisungen zur Gründung einer neuen SIG finden, wenn Ihr besonderes Interesse (noch) nicht abgedeckt ist.
+            </p>

-<div class="intro">
-<br class="mobile">
-<p>Die Kubernetes-Community - Nutzer, Mitwirkende und die Kultur, die wir gemeinsam aufgebaut haben - ist einer der Hauptgründe für den kometenhaften Aufstieg dieses Open-Source-Projekts. Unsere Kultur und unsere Werte wachsen und entwickeln sich mit dem Wachstum und der Veränderung des Projekts selbst. Wir alle arbeiten gemeinsam an der ständigen Verbesserung des Projekts und der Art und Weise, wie wir daran arbeiten.
-<br><br>Wir sind die Leute, die Probleme und Pull-Requests einreichen, an SIG-Treffen (Special Interest Groups), Kubernetes-Treffen und der KubeCon teilnehmen, sich für die Einführung und Innovation von Kubernetes einsetzen, <code>kubectl get pods</code> ausführen und auf tausend andere wichtige Arten beitragen. Lies weiter, um zu erfahren, wie Du dich engagieren und Teil dieser faszinierenden Gemeinschaft werden kannst.</p>
-<br class="mobile">
-</div>
+            <p>Als Mitglied der Kubernetes-Community sind Sie herzlich eingeladen, an allen SIG-Treffen teilzunehmen, die Sie interessieren. Eine Registrierung ist nicht erforderlich.</p>

-<div class="community__navbar">
+        </div>

-<a href="#values">Gemeinschaftswerte</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<a href="#conduct">Verhaltenskodex </a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<a href="#videos">Videos</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<a href="#discuss">Diskussionen</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<a href="#events">Veranstaltungen und meetups</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<a href="#news">Neuigkeiten</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-<a href="/releases">Releases</a>
+        <div class="content">
+          <h3>Verhaltensregeln</h3>
+          <p>Die Kubernetes-Community schätzt Respekt und Inklusivität und setzt einen <a href="code-of-conduct/">Verhaltenskodex</a>
+            in allen Interaktionen durch. Wenn Sie einen Verstoß gegen den Verhaltenskodex bei einer Veranstaltung oder Sitzung,
+            in Slack oder in einem anderen Kommunikationsmechanismus feststellen, wenden Sie sich
+            bitte an das <a href="https://github.com/kubernetes/community/tree/master/committee-code-of-conduct">Kubernetes Code of Conduct Committee</a> <a href="mailto:conduct@kubernetes.io">conduct@kubernetes.io</a>. Ihre Anonymität wird geschützt.
+          </p>
+         </div>
+    </main>
+</section>

-</div>
-<br class="mobile"><br class="mobile">
-<div class="imagecols">
-<br class="mobile">
-  <div class="imagecol">
-    <img src="/images/community/kubernetes-community-final-03.jpg" alt="Kubernetes-Konferenz Galerie" style="width:100%" class="desktop">
-  </div>
-
-  <div class="imagecol">
-    <img src="/images/community/kubernetes-community-final-04.jpg" alt="Kubernetes-Konferenz Galerie" style="width:100%" class="desktop">
-  </div>
-
-  <div class="imagecol" style="margin-right:0% important">
-    <img src="/images/community/kubernetes-community-final-05.jpg" alt="Kubernetes-Konferenz Galerie" style="width:100%;margin-right:0% important" class="desktop">
-  </div>
-  <img src="/images/community/kubernetes-community-04-mobile.jpg" alt="Kubernetes-Konferenz Galerie" style="width:100%;margin-bottom:3%" class="mobile">
-<a name="values"></a>
-</div>
-
-<div><a name="values"></a></div>
-<div class="conduct">
-<div class="conducttext">
-<br class="mobile"><br class="mobile">
-<br class="tablet"><br class="tablet">
-<div class="conducttextnobutton" style="margin-bottom:2%"><h1>Gemeinschaftswerte</h1>
-Die Werte der Kubernetes-Community sind der Grundstein für den anhaltenden Erfolg des Projekts.<br>
-Diese Prinzipien leiten jeden Aspekt des Kubernetes-Projekts.
-<br>
-<a href="/community/values/">
-<br class="mobile"><br class="mobile">
-<span class="fullbutton">
-  MEHR ERFAHREN
-</span>
-</a>
-</div><a name="conduct"></a>
-</div>
-</div>
-
-
-
-<div class="conduct">
-<div class="conducttext">
-<br class="mobile"><br class="mobile">
-<br class="tablet"><br class="tablet">
-<div class="conducttextnobutton" style="margin-bottom:2%"><h1>Verhaltenskodex</h1>
-Die Kubernetes-Gemeinschaft legt Wert auf Respekt und Inklusivität und setzt bei allen Interaktionen einen Verhaltenskodex durch. Wenn Du einen Verstoß gegen den Verhaltenskodex bei einer Veranstaltung oder einem Treffen, in Slack oder in einem anderen Kommunikationsmechanismus bemerkst, wende dich an das Kubernetes Code of Conduct Committee unter <a href="mailto:conduct@kubernetes.io" style="color:#0662EE;font-weight:300">conduct@kubernetes.io</a>. Alle Berichte werden vertraulich behandelt. Du kannst&nbsp;<a href="https://github.com/kubernetes/community/tree/master/committee-code-of-conduct" style="color:#0662EE;font-weight:300">hier</a> mehr über den Ausschuss erfahren.
-<br>
-<a href="https://kubernetes.io/de/community/code-of-conduct/">
-<br class="mobile"><br class="mobile">
-
-<span class="fullbutton">
-MEHR ERFAHREN
-</span>
-</a>
-</div><a name="videos"></a>
-</div>
-</div>
-
-
-
-<div class="videos">
-<br class="mobile"><br class="mobile">
-<br class="tablet"><br class="tablet">
-<h1 style="margin-top:0px">Videos</h1>
-
-<div style="margin-bottom:4%;font-weight:300;text-align:center;padding-left:10%;padding-right:10%">Wir sind auf YouTube, und zwar oft. Abonniere uns für eine Vielzahl von&nbsp;Themen.</div>
-
-<div class="videocontainer">
-
-<div class="video">
-
-  <iframe width="100%" height="250" src="https://www.youtube.com/embed/videoseries?list=PL69nYSiGNLP3azFUvYJjGn45YbF6C-uIg" title="Monatliche Bürozeiten" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
-
-<a href="https://www.youtube.com/playlist?list=PL69nYSiGNLP3azFUvYJjGn45YbF6C-uIg">
-<div class="videocta">
-Monatliche Bürozeiten ansehen&nbsp;&#9654;</div>
-</a>
-</div>
-
-<div class="video">
-  <iframe width="100%" height="250" src="https://www.youtube.com/embed/videoseries?list=PL69nYSiGNLP1pkHsbPjzAewvMgGUpkCnJ" title="Wöchentliche Treffen der Gemeinschaft" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
-<a href="https://www.youtube.com/playlist?list=PL69nYSiGNLP1pkHsbPjzAewvMgGUpkCnJ">
-<div class="videocta">
-Wöchentliche Treffen der Gemeinschaft ansehen&nbsp;&#9654;
-</div>
-</a>
-</div>
-
-<div class="video">
-
-<iframe width="100%" height="250" src="https://www.youtube.com/embed/videoseries?list=PL69nYSiGNLP3QpQrhZq_sLYo77BVKv09F" title="Vortrag eines Mitglieds der Gemeinschaft" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
-
-<a href="https://www.youtube.com/playlist?list=PL69nYSiGNLP3QpQrhZq_sLYo77BVKv09F">
-<div class="videocta">
-Vortrag eines Mitglieds der Gemeinschaft ansehen&nbsp;&#9654;
-</div>
-
-</a>
-<a name="discuss"></a>
-</div>
-</div>
-</div>
-
-
-<div class="resources">
-<br class="mobile"><br class="mobile">
-<br class="tablet"><br class="tablet">
-<h1 style="padding-top:1%">Diskussionen</h1>
-
-<div style="font-weight:300;text-align:center">Wir reden gerne und viel. Triff uns auf einer dieser Plattformen und beteilige dich an den Diskussionen.</div>
-
-<div class="resourcecontainer">
-
-<div class="resourcebox">
-<img src="/images/community/discuss.png" alt=Forum" style="width:80%;padding-bottom:2%">
-<a href="https://discuss.kubernetes.io/" style="color:#0662EE;display:block;margin-top:1%">
-forum&nbsp;&#9654;
-</a>
-<div class="resourceboxtext" style="font-size:12px;text-transform:none !important;font-weight:300;line-height:1.4em;color:#333333;margin-top:4%">
-Themenbezogene technische Diskussionen, die eine Brücke zu Docs, StackOverflow und vielem mehr schlagen.
-</div>
-</div>
-
-<div class="resourcebox">
-<img src="/images/community/twitter.png" alt="Twitter" style="width:80%;padding-bottom:2%">
-<a href="https://twitter.com/kubernetesio" style="color:#0662EE;display:block;margin-top:1%">
-twitter&nbsp;&#9654;
-</a>
-<div class="resourceboxtext" style="font-size:12px;text-transform:none !important;font-weight:300;line-height:1.4em;color:#333333;margin-top:4%">Echtzeit-Ankündigungen von Blogeinträgen, Veranstaltungen, Neuigkeiten und Ideen
-</div>
-</div>
-
-<div class="resourcebox">
-<img src="/images/community/github.png" alt="GitHub" style="width:80%;padding-bottom:2%">
-<a href="https://github.com/kubernetes/kubernetes" style="color:#0662EE;display:block;margin-top:1%">
-github&nbsp;&#9654;
-</a>
-<div class="resourceboxtext" style="font-size:12px;text-transform:none !important;font-weight:300;line-height:1.4em;color:#333333;margin-top:4%">
-Die gesamte Projekt- und Problemverfolgung und natürlich der Code
-</div>
-</div>
-
-<div class="resourcebox">
-<img src="/images/community/stack.png" alt="Stack Overflow" style="width:80%;padding-bottom:2%">
-<a href="https://stackoverflow.com/search?q=kubernetes" style="color:#0662EE;display:block;margin-top:1%">
-stack overflow&nbsp;&#9654;
-</a>
-<div class="resourceboxtext" style="font-size:12px;text-transform:none !important;font-weight:300;line-height:1.4em;color:#333333;margin-top:4%">
-  Technische Problemlösung für jeden Anwendungsfall
-  <a name="events"></a>
-</div>
-</div>
-
-<!--
-<div class="resourcebox">
-
-<img src="/images/community/slack.png" style="width:80%">
-
-slack&nbsp;&#9654;
-
-<div class="resourceboxtext" style="font-size:11px;text-transform:none !important;font-weight:200;line-height:1.4em;color:#333333;margin-top:4%">
-With 170+ channels, you'll find one that fits your needs.
-</div>
-
-</div>-->
-
-</div>
-</div>
-<div class="events">
-  <br class="mobile"><br class="mobile">
-  <br class="tablet"><br class="tablet">
-<div class="eventcontainer">
- <h1 style="color:white !important">Bevorstehende Veranstaltungen</h1>
-    {{< upcoming-events >}}
-</div>
-</div>
-
-<div class="meetups">
-<div class="meetupcol">
-<div class="meetuptext">
-<h1 style="text-align:left">Globale Gemeinschaft</h1>
-Mit mehr als 150 Treffen auf der ganzen Welt, Tendenz steigend, solltest du deine lokalen Kube-Leute finden. Wenn keins in der Nähe ist, nimm die Sache in die Hand und gründe dein eigenes.
-</div>
-<a href="https://www.meetup.com/topics/kubernetes/">
-<div class="button">
-EIN MEETUP FINDEN
-</div>
-</a>
-<a name="news"></a>
-</div>
-</div>
-
-
-<!--
-<div class="contributor">
-<div class="contributortext">
-<br>
-<h1 style="text-align:left">
-New Contributors Site
- </h1>
-Text about new contributors site.
-
-<br><br>
-
-<div class="button">
-VISIT SITE
-</div>
-</div>
-</div>
-
-->
-
-<div class="news">
-<br class="mobile"><br class="mobile">
-<br class="tablet"><br class="tablet">
-<h1 style="margin-bottom:2%">Aktuelle Neuigkeiten</h1>
-
-<br>
-<div class="twittercol1">
-<a class="twitter-timeline" data-tweet-limit="1" href="https://twitter.com/kubernetesio?ref_src=twsrc%5Etfw">Tweets von kubernetesio</a> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
-</div>
-
-<br>
-<br><br><br><br>
-</div>
-
-</div>
+<section id="talkToUs">
+    <main>
+        <h3>Talk to Us!</h3>
+        <h4>Wir würden uns freuen, von Ihnen zu hören, wie Sie Kubernetes verwenden<br>und was wir tun können, um es besser zu machen.</h4>
+        <div id="bigSocial">
+            <div>
+                <a href="https://twitter.com/kubernetesio">@kubernetesio</a>
+                <p>Erhalten Sie die neuesten Nachrichten und Updates.</p>
+            </div>
+            <div>
+                <a href="https://github.com/kubernetes/kubernetes">Github Project</a>
+                <p>Informieren Sie sich über das Projekt und erwägen Sie, einen Beitrag zu leisten.</p>
+            </div>
+            <div>
+                <a href="http://slack.k8s.io/">#kubernetes-users</a>
+                <p>Unser Slack-Kanal ist der beste Weg, um unsere Ingenieure zu kontaktieren und Ihre Ideen mit ihnen zu teilen.</p>
+            </div>
+            <div>
+                <a href="http://stackoverflow.com/questions/tagged/kubernetes">Stack Overflow</a>
+                <p>Unser Benutzerforum ist ein großartiger Ort, um Community-Support zu erhalten.</p>
+            </div>
+        </div>
+    </main>
+</section>
@@ -23,7 +23,7 @@ Dieser Verhaltenskodex gilt sowohl innerhalb von Projekträumen als auch in öff

 Fälle von missbräuchlichem, belästigendem oder anderweitig unzumutbarem Verhalten in Kubernetes können gemeldet werden, indem Sie sich an das [Kubernetes Komitee für Verhaltenskodex](https://git.k8s.io/community/committee-code-of-conduct) wenden unter <conduct@kubernetes.io>. Für andere Projekte wenden Sie sich bitte an einen CNCF-Projektbetreuer oder an unseren Mediator, Mishi Choudhary <mishi@linux.com>.

-Dieser Verhaltenskodex wurde aus dem Contributor Covenant übernommen (https://contributor-covenant.org), Version 1.2.0, verfügbar unter https://contributor-covenant.org/version/1/2/0/
+Dieser Verhaltenskodex wurde aus dem Contributor Covenant übernommen (http://contributor-covenant.org), Version 1.2.0, verfügbar unter http://contributor-covenant.org/version/1/2/0/

 ### CNCF Verhaltenskodex für Veranstaltungen

@@ -6,7 +6,7 @@ weight: 10

 <!-- overview -->

-Ein Knoten (Node in Englisch) ist eine Arbeitsmaschine in Kubernetes. Ein Node
+Ein Knoten (Node in Englisch) ist eine Arbeitsmaschine in Kubernetes, früher als `minion` bekannt. Ein Node
 kann je nach Cluster eine VM oder eine physische Maschine sein. Jeder Node enthält
 die für den Betrieb von [Pods](/docs/concepts/workloads/pods/pod/) notwendigen Dienste
 und wird von den Master-Komponenten verwaltet.
@@ -147,8 +147,7 @@ Die zweite ist, die interne Node-Liste des Node Controllers mit der Liste der ve
 Wenn ein Node in einer Cloud-Umgebung ausgeführt wird und sich in einem schlechten Zustand befindet, fragt der Node Controller den Cloud-Anbieter, ob die virtuelle Maschine für diesen Node noch verfügbar ist. Wenn nicht, löscht der Node Controller den Node aus seiner Node-Liste.

 Der dritte ist die Überwachung des Zustands der Nodes. Der Node Controller ist dafür verantwortlich,
-die NodeReady-Bedingung von NodeStatus auf ConditionUnknown zu aktualisieren, wenn ein Node unerreichbar wird (der Node Controller empfängt aus irgendeinem Grund keine Herzschläge mehr, z.B. weil der Node heruntergefahren ist) und später alle Pods aus dem Node zu entfernen (und diese ordnungsgemäss zu beenden), wenn der Node weiterhin unzugänglich ist. (Die Standard-Timeouts sind 40s, um ConditionUnknown zu melden und 5 Minuten, um mit der Evakuierung der Pods zu beginnen).
-
+die NodeReady-Bedingung von NodeStatus auf ConditionUnknown zu aktualisieren, wenn ein wenn ein Node unerreichbar wird (der Node Controller empfängt aus irgendeinem Grund keine Herzschläge mehr, z.B. weil der Node heruntergefahren ist) und später alle Pods aus dem Node zu entfernen (und diese ordnungsgemäss zu beenden), wenn der Node weiterhin unzugänglich ist. (Die Standard-Timeouts sind 40s, um ConditionUnknown zu melden und 5 Minuten, um mit der Evakuierung der Pods zu beginnen).
 Der Node Controller überprüft den Zustand jedes Nodes alle `--node-monitor-period` Sekunden.


@@ -26,7 +26,7 @@ Die Add-Ons in den einzelnen Kategorien sind alphabetisch sortiert - Die Reihenf
 * [CNI-Genie](https://github.com/Huawei-PaaS/CNI-Genie) ermöglicht das nahtlose Verbinden von Kubernetes mit einer Reihe an CNI-Plugins wie z.B. Calico, Canal, Flannel, Romana, oder Weave.
 * [Contiv](http://contiv.github.io) bietet konfigurierbares Networking (Native L3 auf BGP, Overlay mit vxlan, Klassisches L2, Cisco-SDN/ACI) für verschiedene Anwendungszwecke und auch umfangreiches Policy-Framework. Das Contiv-Projekt ist vollständig [Open Source](http://github.com/contiv). Der [installer](http://github.com/contiv/install) bietet sowohl kubeadm als auch nicht-kubeadm basierte Installationen.
 * [Contrail](http://www.juniper.net/us/en/products-services/sdn/contrail/contrail-networking/), basierend auf [Tungsten Fabric](https://tungsten.io), ist eine Open Source, multi-Cloud Netzwerkvirtualisierungs- und Policy-Management Plattform. Contrail und Tungsten Fabric sind mit Orechstratoren wie z.B. Kubernetes, OpenShift, OpenStack und Mesos integriert und bieten Isolationsmodi für Virtuelle Maschinen, Container (bzw. Pods) und Bare Metal workloads.
-* [Flannel](https://github.com/flannel-io/flannel#deploying-flannel-manually) ist ein Overlay-Network-Provider der mit Kubernetes genutzt werden kann.
+* [Flannel](https://github.com/coreos/flannel/blob/master/Documentation/kubernetes.md) ist ein Overlay-Network-Provider der mit Kubernetes genutzt werden kann.
 * [Knitter](https://github.com/ZTE/Knitter/) ist eine Network-Lösung die Mehrfach-Network in Kubernetes ermöglicht.
 * [Multus](https://github.com/Intel-Corp/multus-cni) ist ein Multi-Plugin für Mehrfachnetzwerk-Unterstützung um alle CNI-Plugins (z.B. Calico, Cilium, Contiv, Flannel), zusätzlich zu SRIOV-, DPDK-, OVS-DPDK- und VPP-Basierten Workloads in Kubernetes zu unterstützen.
 * [NSX-T](https://docs.vmware.com/en/VMware-NSX-T/2.0/nsxt_20_ncp_kubernetes.pdf) Container Plug-in (NCP) bietet eine Integration zwischen VMware NSX-T und einem Orchestator wie z.B. Kubernetes. Außerdem bietet es eine Integration zwischen NSX-T und Containerbasierten CaaS/PaaS-Plattformen wie z.B. Pivotal Container Service (PKS) und OpenShift.
@@ -1,369 +0,0 @@
---
-title: Pods
-content_type: concept
-weight: 10
-no_list: true
-card:
- name: concepts
- weight: 60
---
-
-<!-- overview -->
-
-_Pods_ sind die kleinsten einsetzbaren Einheiten, die in Kubernetes
-erstellt und verwaltet werden können.
-
-Ein _Pod_ (übersetzt Gruppe/Schote, wie z. B. eine Gruppe von Walen oder eine 
-Erbsenschote) ist eine Gruppe von einem oder mehreren 
-{{< glossary_tooltip text="Containern" term_id="container" >}} mit gemeinsam 
-genutzten Speicher- und Netzwerkressourcen und einer Spezifikation für die 
-Ausführung der Container. Die Ressourcen eines Pods befinden sich immer auf dem 
-gleichen (virtuellen) Server, werden gemeinsam geplant und in einem
-gemeinsamen Kontext ausgeführt. Ein Pod modelliert einen anwendungsspezifischen 
-"logischen Server": Er enthält eine oder mehrere containerisierte Anwendungen, 
-die relativ stark voneinander abhängen. 
-In Nicht-Cloud-Kontexten sind Anwendungen, die auf
-demselben physischen oder virtuellen Server ausgeführt werden, vergleichbar zu 
-Cloud-Anwendungen, die auf demselben logischen Server ausgeführt werden.
-
-Ein Pod kann neben Anwendungs-Containern auch sogenannte 
-[Initialisierungs-Container](/docs/concepts/workloads/pods/init-containers/)
-enthalten, die beim Starten des Pods ausgeführt werden.
-Es können auch 
-kurzlebige/[ephemere Container](/docs/concepts/workloads/pods/ephemeral-containers/)
-zum Debuggen gestartet werden, wenn dies der Cluster anbietet.
-
-<!-- body -->
-
-## Was ist ein Pod?
-
-{{< note >}}
-Obwohl Kubernetes abgesehen von [Docker](https://www.docker.com/) auch andere
-{{<glossary_tooltip text="Container-Laufzeitumgebungen" 
-term_id="container-runtime">}} unterstützt, ist Docker am bekanntesten und
- es ist hilfreich, Pods mit der Terminologie von Docker zu beschreiben.
-{{< /note >}}
-
-Der gemeinsame Kontext eines Pods besteht aus einer Reihe von Linux-Namespaces, 
-Cgroups und möglicherweise anderen Aspekten der Isolation, also die gleichen
-Dinge, die einen Dockercontainer isolieren. Innerhalb des Kontexts eines Pods 
-können die einzelnen Anwendungen weitere Unterisolierungen haben. 
-
-Im Sinne von Docker-Konzepten ähnelt ein Pod einer Gruppe von Docker-Containern, 
-die gemeinsame Namespaces und Dateisystem-Volumes nutzen.
-
-## Pods verwenden
-
-Normalerweise müssen keine Pods erzeugt werden, auch keine Singleton-Pods. 
-Stattdessen werden sie mit Workload-Ressourcen wie {{<glossary_tooltip 
-text="Deployment" term_id="deployment">}} oder {{<glossary_tooltip 
-text="Job" term_id="job">}} erzeugt. Für Pods, die von einem Systemzustand
-abhängen, ist die Nutzung von {{<glossary_tooltip text="StatefulSet" 
-term_id="statefulset">}}-Ressourcen zu erwägen.
-
-Pods in einem Kubernetes-Cluster werden hauptsächlich auf zwei Arten verwendet:
-
-* **Pods, die einen einzelnen Container ausführen**. Das 
-"Ein-Container-per-Pod"-Modell ist der häufigste Kubernetes-Anwendungsfall. In 
-diesem Fall kannst du dir einen einen Pod als einen Behälter vorstellen, der einen 
-einzelnen Container enthält; Kubernetes verwaltet die Pods anstatt die 
-Container direkt zu verwalten.
-* **Pods, in denen mehrere Container ausgeführt werden, die zusammenarbeiten
-müssen**. Wenn eine Softwareanwendung aus co-lokaliserten Containern besteht, 
-die sich gemeinsame Ressourcen teilen und stark voneinander abhängen, kann ein 
-Pod die Container verkapseln. 
-Diese Container bilden eine einzelne zusammenhängende 
-Serviceeinheit, z. B. ein Container, der Daten in einem gemeinsam genutzten 
-Volume öffentlich verfügbar macht, während ein separater _Sidecar_-Container 
-die Daten aktualisiert. Der Pod fasst die Container, die Speicherressourcen
-und eine kurzlebiges Netzwerk-Identität als eine Einheit zusammen.
-
-{{< note >}}
-Das Gruppieren mehrerer gemeinsam lokalisierter und gemeinsam verwalteter
-Container in einem einzigen Pod ist ein relativ fortgeschrittener 
-Anwendungsfall. Du solltest diese Architektur nur in bestimmten  Fällen 
-verwenden, wenn deine Container stark voneinander abhängen.
-{{< /note >}}
-
-Jeder Pod sollte eine einzelne Instanz einer gegebenen Anwendung ausführen. Wenn 
-du deine Anwendung horizontal skalieren willst (um mehr Instanzen auszuführen
-und  dadurch mehr Gesamtressourcen bereitstellen), solltest du mehrere Pods 
-verwenden, einen für jede Instanz. 
-In Kubernetes wird dies typischerweise als Replikation bezeichnet.
-Replizierte Pods werden normalerweise als eine Gruppe durch eine 
-Workload-Ressource und deren 
-{{<glossary_tooltip text="Controller" term_id="controller">}} erstellt 
-und verwaltet.
-
-Der Abschnitt [Pods und Controller](#pods-und-controller) beschreibt, wie 
-Kubernetes Workload-Ressourcen und deren Controller verwendet, um Anwendungen 
-zu skalieren und zu heilen.
-
-### Wie Pods mehrere Container verwalten
-
-Pods unterstützen mehrere kooperierende Prozesse (als Container), die eine 
-zusammenhängende Serviceeinheit bilden. Kubernetes plant und stellt automatisch 
-sicher, dass sich die Container in einem Pod  auf demselben physischen oder 
-virtuellen Server im Cluster befinden. Die Container können Ressourcen und
-Abhängigkeiten gemeinsam nutzen, miteinander kommunizieren und
-ferner koordinieren wann und wie sie beendet werden.
-
-Zum Beispiel könntest du einen Container haben, der als Webserver für Dateien in
-einem gemeinsamen Volume arbeitet. Und ein separater "Sidecar" -Container 
-aktualisiert die Daten von einer externen Datenquelle, siehe folgenden 
-Abbildung:
-
-{{< figure src="/images/docs/pod.svg" alt="Pod-Beispieldiagramm" width="50%" >}}
-
-Einige Pods haben sowohl {{<glossary_tooltip text="Initialisierungs-Container" 
-term_id="init-container">}} als auch {{<glossary_tooltip 
-text="Anwendungs-Container" term_id="app-container">}}. 
-Initialisierungs-Container werden gestartet und beendet bevor die 
-Anwendungs-Container gestartet werden.
-
-Pods stellen standardmäßig zwei Arten von gemeinsam Ressourcen für die 
-enthaltenen Container bereit:
-[Netzwerk](#pod-netzwerk) und [Speicher](#datenspeicherung-in-pods).
-
-
-## Mit Pods arbeiten
-
-Du wirst selten einzelne Pods direkt in Kubernetes erstellen, selbst 
-Singleton-Pods. Das liegt daran, dass Pods als relativ kurzlebige 
-Einweg-Einheiten konzipiert sind. Wann Ein Pod erstellt wird (entweder direkt 
-von Ihnen oder indirekt von einem
-{{<glossary_tooltip text="Controller" term_id="controller">}}), wird die 
-Ausführung auf einem {{<glossary_tooltip term_id="node">}} in Ihrem Cluster 
-geplant. Der Pod bleibt auf diesem (virtuellen) Server, bis entweder der Pod die
-Ausführung beendet hat, das Pod-Objekt gelöscht wird, der Pod aufgrund 
-mangelnder Ressourcen *evakuiert* wird oder oder der Node ausfällt. 
-
-{{< note >}}
-Das Neustarten eines Containers in einem Pod sollte nicht mit dem Neustarten 
-eines Pods verwechselt werden. Ein Pod ist kein Prozess, sondern eine Umgebung 
-zur Ausführung von Containern. Ein Pod bleibt bestehen bis er gelöscht wird.
-{{< /note >}}
-
-Stelle beim Erstellen des Manifests für ein Pod-Objekt sicher, dass der 
-angegebene Name ein gültiger
-[DNS-Subdomain-Name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)
-ist.
-
-### Pods und Controller
-
-Mit Workload-Ressourcen kannst du mehrere Pods erstellen und verwalten. Ein 
-Controller für die Ressource kümmert sich um Replikation, Roll-Out sowie 
-automatische Wiederherstellung im Fall von versagenden Pods. Wenn beispielsweise ein Node 
-ausfällt, bemerkt ein Controller, dass die Pods auf dem Node nicht mehr laufen 
-und plant die Ausführung eines Ersatzpods auf einem funktionierenden Node.
-Hier sind einige Beispiele für Workload-Ressourcen, die einen oder mehrere Pods 
-verwalten:
-
-* {{< glossary_tooltip text="Deployment" term_id="deployment" >}}
-* {{< glossary_tooltip text="StatefulSet" term_id="statefulset" >}}
-* {{< glossary_tooltip text="DaemonSet" term_id="daemonset" >}}
-
-### Pod Vorlagen
-
-Controller für 
-{{<glossary_tooltip text="Workload" term_id="workload">}}-Ressourcen 
-erstellen Pods von einer _Pod Vorlage_ und verwalten diese Pods für dich.
-
-Pod Vorlagen sind Spezifikationen zum Erstellen von Pods und sind in 
-Workload-Ressourcen enthalten wie z. B.
-[Deployments](/docs/concepts/workloads/controllers/deployment/),
-[Jobs](/docs/concepts/workloads/controllers/job/), and
-[DaemonSets](/docs/concepts/workloads/controllers/daemonset/).
-
-Jeder Controller für eine Workload-Ressource verwendet die Pod Vorlage innerhalb 
-des Workload-Objektes, um Pods zu erzeugen. Die Pod Vorlage ist Teil des 
-gewünschten Zustands der Workload-Ressource, mit der du deine Anwendung 
-ausgeführt hast.
-
-Das folgende Beispiel ist ein Manifest für einen einfachen Job mit einer 
-`Vorlage`, die einen Container startet. Der Container in diesem Pod druckt 
-eine Nachricht und pausiert dann.
-
-```yaml
-apiVersion: batch/v1
-kind: Job
-metadata:
- name: hello
-spec:
- template:
- # Dies is the Pod Vorlage
- spec:
- containers:
- - name: hello
- image: busybox
- command: ['sh', '-c', 'echo "Hello, Kubernetes!" && sleep 3600']
- restartPolicy: OnFailure
- # Die Pod Vorlage endet hier
-```
-Das Ändern der Pod Vorlage oder der Wechsel zu einer neuen Pod Vorlage hat keine 
-direkten Auswirkungen auf bereits existierende Pods. Wenn du die Pod Vorlage für
-eine Workload-Ressource änderst, dann muss diese Ressource die Ersatz-Pods
-erstellen, welche die aktualisierte Vorlage verwenden. 
-
-Beispielsweise stellt der StatefulSet-Controller sicher, dass für jedes
-StatefulSet-Objekt die ausgeführten Pods mit der aktueller Pod Vorlage 
-übereinstimmen. Wenn du das StatefulSet bearbeitest und die Vorlage änderst, 
-beginnt das StatefulSet mit der Erstellung neuer Pods basierend auf der 
-aktualisierten Vorlage. Schließlich werden alle alten Pods durch neue Pods 
-ersetzt, und das Update ist abgeschlossen.
-
-Jede Workload-Ressource implementiert eigenen Regeln für die Umsetzung von 
-Änderungen der Pod Vorlage. Wenn du mehr über StatefulSet erfahren möchtest, 
-dann lese die Seite
-[Update-Strategien](/docs/tutorials/stateful-application/basic-stateful-set/#updating-statefulsets) 
-im Tutorial StatefulSet Basics.
-
-
-Auf Nodes beobachtet oder verwaltet das 
-{{< glossary_tooltip term_id="kubelet" text="Kubelet" >}}
-nicht direkt die Details zu Pod Vorlagen und Updates. Diese Details sind 
-abstrahiert. Die Abstraktion und Trennung von Aufgaben vereinfacht die 
-Systemsemantik und ermöglicht so das Verhalten des Clusters zu ändern ohne 
-vorhandenen Code zu ändern.
-
-## Pod Update und Austausch
-
-Wie im vorherigen Abschnitt erwähnt, erstellt der Controller neue Pods basierend
-auf der aktualisierten Vorlage, wenn die Pod Vorlage für eine Workload-Ressource
-geändert wird anstatt die vorhandenen Pods zu aktualisieren oder zu patchen.
-
-Kubernetes hindert dich nicht daran, Pods direkt zu verwalten. Es ist möglich, 
-einige Felder eines laufenden Pods zu aktualisieren. Allerdings haben 
-Pod-Aktualisierungsvorgänge wie zum Beispiel
-[`patch`](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#patch-pod-v1-core), 
-und
-[`replace`](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#replace-pod-v1-core)
-einige Einschränkungen:
-
- Die meisten Metadaten zu einem Pod können nicht verändert werden. Zum Beispiel kannst
-  du nicht die Felder `namespace`, `name`, `uid`, oder `creationTimestamp` 
-  ändern. Das `generation`-Feld muss eindeutig sein. Es werden nur Aktualisierungen 
-  akzeptiert, die den Wert des Feldes inkrementieren.
- Wenn das Feld `metadata.deletionTimestamp` gesetzt ist, kann kein neuer 
-  Eintrag zur Liste `metadata.finalizers` hinzugefügt werden.
- Pod-Updates dürfen keine Felder ändern, die Ausnahmen sind 
-  `spec.containers[*].image`,
- `spec.initContainers[*].image`,` spec.activeDeadlineSeconds` oder
- `spec.tolerations`. Für `spec.tolerations` kannnst du nur neue Einträge 
-  hinzufügen.
- Für `spec.activeDeadlineSeconds` sind nur zwei Änderungen erlaubt:
-
-  1. ungesetztes Feld in eine positive Zahl
-  1. positive Zahl in eine kleinere positive Zahl, die nicht negativ ist
-  
-## Gemeinsame Nutzung von Ressourcen und Kommunikation 
-
-Pods ermöglichen den Datenaustausch und die Kommunikation zwischen den 
-Containern, die im Pod enthalten sind.
-
-### Datenspeicherung in Pods
-
-Ein Pod kann eine Reihe von gemeinsam genutzten Speicher-
-{{<glossary_tooltip text="Volumes" term_id="volume">}} spezifizieren. Alle 
-Container im Pod können auf die gemeinsamen Volumes zugreifen und dadurch Daten 
-austauschen. Volumes ermöglichen auch, dass Daten ohne Verlust gespeichert 
-werden, falls einer der Container neu gestartet werden muss. 
-Im Kapitel [Datenspeicherung](/docs/concepts/storage/) findest du weitere 
-Informationen, wie Kubernetes gemeinsam genutzten Speicher implementiert und 
-Pods zur Verfügung stellt.
-
-### Pod-Netzwerk
-
-Jedem Pod wird für jede Adressenfamilie eine eindeutige IP-Adresse zugewiesen. 
-Jeder Container in einem Pod nutzt den gemeinsamen Netzwerk-Namespace, 
-einschließlich der IP-Adresse und der Ports. In einem Pod (und **nur** dann) 
-können die Container, die zum Pod gehören, über `localhost` miteinander 
-kommunizieren. Wenn Container in einem Pod mit Entitäten *außerhalb des Pods* 
-kommunizieren, müssen sie koordinieren, wie die gemeinsam genutzten 
-Netzwerkressourcen (z. B. Ports) verwenden werden. Innerhalb eines Pods teilen 
-sich Container eine IP-Adresse und eine Reihe von Ports und können sich 
-gegenseitig über `localhost` finden. Die Container in einem Pod können auch die 
-üblichen Kommunikationsverfahren zwischen Prozessen nutzen, wie z. B. 
-SystemV-Semaphoren oder "POSIX Shared Memory". Container in verschiedenen Pods 
-haben unterschiedliche IP-Adressen und können nicht per IPC ohne 
-[spezielle Konfiguration](/docs/concepts/policy/pod-security-policy/) 
-kommunizieren. Container, die mit einem Container in einem anderen Pod 
-interagieren möchten, müssen IP Netzwerke verwenden.
-
-Für die Container innerhalb eines Pods stimmt der "hostname" mit dem 
-konfigurierten `Namen` des Pods überein. Mehr dazu im Kapitel 
-[Netzwerke](/docs/concepts/cluster-administration/networking/).
-
-## Privilegierter Modus für Container
-
-Jeder Container in einem Pod kann den privilegierten Modus aktivieren, indem 
-das Flag `privileged` im 
-[Sicherheitskontext](/docs/tasks/configure-pod-container/security-context/)
-der Container-Spezifikation verwendet wird.
-Dies ist nützlich für Container, die Verwaltungsfunktionen des Betriebssystems 
-verwenden möchten, z. B. das Manipulieren des Netzwerk-Stacks oder den Zugriff 
-auf Hardware. Prozesse innerhalb eines privilegierten Containers erhalten fast 
-die gleichen Rechte wie sie Prozessen außerhalb eines Containers zur Verfügung 
-stehen.
-
-{{< note >}}
-Ihre 
-{{<glossary_tooltip text="Container-Umgebung" term_id="container-runtime">}} 
-muss das Konzept eines privilegierten Containers unterstützen, damit diese 
-Einstellung relevant ist.
-{{< /note >}}
-
-
-## Statische Pods
-
-_Statische Pods_ werden direkt vom Kubelet-Daemon auf einem bestimmten Node 
-verwaltet ohne dass sie vom 
-{{<glossary_tooltip text="API Server" term_id="kube-apiserver">}} überwacht 
-werden.
-
-Die meisten Pods werden von der Kontrollebene verwaltet (z. B.
-{{< glossary_tooltip text="Deployment" term_id="deployment" >}}). Aber für 
-statische Pods überwacht das Kubelet jeden statischen Pod direkt (und startet 
-ihn neu, wenn er ausfällt).
-
-Statische Pods sind immer an ein {{<glossary_tooltip term_id="kubelet">}} auf 
-einem bestimmten Node gebunden. Der Hauptanwendungsfall für statische Pods 
-besteht darin, eine selbst gehostete Steuerebene auszuführen. Mit anderen 
-Worten: Das Kubelet dient zur Überwachung der einzelnen 
-[Komponenten der Kontrollebene](/docs/concepts/overview/components/#control-plane-components).
-
-Das Kubelet versucht automatisch auf dem Kubernetes API-Server für jeden 
-statischen Pod einen spiegelbildlichen Pod 
-(im Englischen: {{<glossary_tooltip text="mirror pod" term_id="mirror-pod">}}) 
-zu erstellen.
-Das bedeutet, dass die auf einem Node ausgeführten Pods auf dem API-Server 
-sichtbar sind jedoch von dort nicht gesteuert werden können.
-
-## {{% heading "whatsnext" %}}
-
-* Verstehe den 
-  [Lebenszyklus eines Pods](/docs/concepts/workloads/pods/pod-lifecycle/).
-* Erfahre mehr über [RuntimeClass](/docs/concepts/containers/runtime-class/) 
-  und wie du damit verschiedene Pods mit unterschiedlichen 
-  Container-Laufzeitumgebungen konfigurieren kannst.
-* Mehr zum Thema 
-  [Restriktionen für die Verteilung von Pods](/docs/concepts/workloads/pods/pod-topology-spread-constraints/).
-* Lese
-  [Pod-Disruption-Budget](/docs/concepts/workloads/pods/disruptions/) 
-  und wie du es verwenden kannst, um die Verfügbarkeit von Anwendungen bei 
-  Störungen zu verwalten. Die 
-  [Pod](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#pod-v1-core)
-  -Objektdefinition beschreibt das Objekt im Detail.
-* [The Distributed System Toolkit: Patterns for Composite Containers](https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns) 
-  erläutert allgemeine Layouts für Pods mit mehr als einem Container.
-
-Um den Hintergrund zu verstehen, warum Kubernetes eine gemeinsame Pod-API in 
-andere Ressourcen, wie z. B. 
-{{< glossary_tooltip text="StatefulSets" term_id="statefulset" >}} 
-oder {{< glossary_tooltip text="Deployments" term_id="deployment" >}} einbindet, 
-kannst du Artikel zu früheren Technologien lesen, unter anderem: 
- * [Aurora](https://aurora.apache.org/documentation/latest/reference/configuration/#job-schema)
- * [Borg](https://research.google.com/pubs/pub43438.html)
- * [Marathon](https://mesosphere.github.io/marathon/docs/rest-api.html)
- * [Omega](https://research.google/pubs/pub41684/)
- * [Tupperware](https://engineering.fb.com/data-center-engineering/tupperware/).
@@ -9,7 +9,7 @@ content_type: concept

 Diese Sektion umfasst verschiedene Optionen zum Einrichten und Betrieb von Kubernetes.

-Verschiedene Kubernetes Lösungen haben verschiedene Anforderungen:  Einfache Wartung, Sicherheit, Kontrolle, verfügbare Resourcen und erforderliches Fachwissen zum Betrieb und zur Verwaltung. Das folgende Diagramm zeigt die möglichen Abstraktionen eines Kubernetes-Clusters und ob eine Abstraktion selbst verwaltet oder von einem Anbieter verwaltet wird.
+Verschiedene Kubernetes Lösungen haben verschiedene Anforderungen:  Einfache Wartung, Sicherheit, Kontrolle, verfügbare Resourcen und erforderliches Fachwissen zum Betrieb und zur Verwaltung dess folgende Diagramm zeigt die möglichen Abstraktionen eines Kubernetes-Clusters und ob eine Abstraktion selbst verwaltet oder von einem Anbieter verwaltet wird.

 Sie können einen Kubernetes-Cluster auf einer lokalen Maschine, Cloud, On-Prem Datacenter bereitstellen; oder wählen Sie einen verwalteten Kubernetes-Cluster. Sie können auch eine individuelle Lösung über eine grosse Auswahl an Cloud Anbietern oder Bare-Metal-Umgebungen nutzen.

@@ -69,7 +69,7 @@ sudo mv minikube /usr/local/bin
 ### Linux

 {{< note >}}
-Dieses Dokument zeigt Ihnen, wie Sie Minikube mit einer statischen Binärdatei unter Linux installieren. Für alternative Linux-Installationsmethoden siehe [Andere Installationsmethoden](https://minikube.sigs.k8s.io/docs/start/) im offiziellen Minikube-GitHub-Repository.
+Dieses Dokument zeigt Ihnen, wie Sie Minikube mit einer statischen Binärdatei unter Linux installieren. Für alternative Linux-Installationsmethoden siehe [Andere Installationsmethoden](https://github.com/kubernetes/minikube#other-ways-to-install) im offiziellen Minikube-GitHub-Repository.
 {{< /note >}}

 Sie können Minikube unter Linux installieren, indem Sie eine statische Binärdatei herunterladen:
@@ -50,8 +50,6 @@ Bevor Sie die einzelnen Lernprogramme durchgehen, möchten Sie möglicherweise e

 * [AppArmor](/docs/tutorials/clusters/apparmor/)

-* [seccomp](/docs/tutorials/clusters/seccomp/)
-
 ## Services

 * [Source IP verwenden](/docs/tutorials/services/source-ip/)
@@ -5,7 +5,7 @@ weight: 20

 <!DOCTYPE html>

-<html lang="de">
+<html lang="en">

 <body>

@@ -5,7 +5,7 @@ weight: 20

 <!DOCTYPE html>

-<html lang="de">
+<html lang="en">

 <body>

@@ -5,7 +5,7 @@ weight: 10

 <!DOCTYPE html>

-<html lang="de">
+<html lang="en">

 <body>

@@ -5,7 +5,7 @@ weight: 20

 <!DOCTYPE html>

-<html lang="de">
+<html lang="en">

 <body>

@@ -5,7 +5,7 @@ weight: 10

 <!DOCTYPE html>

-<html lang="de">
+<html lang="en">

 <body>

@@ -5,7 +5,7 @@ weight: 20

 <!DOCTYPE html>

-<html lang="de">
+<html lang="en">

 <body>

@@ -5,7 +5,7 @@ weight: 10

 <!DOCTYPE html>

-<html lang="de">
+<html lang="en">

 <body>

@@ -1,201 +0,0 @@
-/*  SECTIONS  */
-.section {
-	clear: both;
-	padding: 0px;
-	margin-bottom: 2em;
-}
-
-.kcsp_section {
-	clear: both;
-	padding: 0px;
-	margin-bottom: 2em;
-}
-
-/*  COLUMN SETUP  */
-.col {
-	display: block;
-	float:left;
-	margin: 1% 0 1% 1.6%;
-	background-color: #f9f9f9;
-}
-.col:first-child { margin-left: 0; }
-
-
-/*  GROUPING  */
-.group:before,
-.group:after {
-	content:"";
-	display:table;
-}
-.group:after {
-	clear:both;
-}
-.group {
-    zoom:1; /* For IE 6/7 */
-}
-
-/*  GRID OF THREE  */
-.span_3_of_3 {
-	width: 35%;
-	background-color: #f9f9f9;
-	padding: 20px;
-}
-.span_2_of_3 {
-	width: 35%;
-	background-color: #f9f9f9;
-	padding: 20px;
-}
-.span_1_of_3 {
-	width: 35%;
-	background-color: #f9f9f9;
-	padding: 20px;
-}
-
-.col-container {
-    display: table; /* Make the container element behave like a table */
-    width: 100%; /* Set full-width to expand the whole page */
-		padding-bottom: 30px;
-}
-
-.col-nav {
-    display: table-cell; /* Make elements inside the container behave like table cells */
-		width: 18%;
-		background-color: #f9f9f9;
-		padding: 20px;
-		border: 5px solid white;
-}
-
-/*  GO FULL WIDTH AT LESS THAN 480 PIXELS */
-
-@media only screen and (max-width: 480px) {
-	.col { margin: 1% 0 1% 0%;}
-	.span_3_of_3, .span_2_of_3, .span_1_of_3 { width: 100%; }
-}
-
-@media only screen and (max-width: 650px) {
-    .col-nav {
-        display: block;
-        width: 100%;
-    }
-}
-
-.button{
-  max-width: 100%;
-	box-sizing: border-box;
-	margin: 0;
-	display: inline-block;
-	border-radius: 6px;
-	padding: 0 20px;
-	line-height: 40px;
-	color: #ffffff;
-	font-size: 16px;
-	background-color: #3371e3;
-	text-decoration: none;
- }
-
-h5 {
-	font-size: 16px;
-	line-height: 1.5em;
-	margin-bottom: 2em;
-}
-
-#usersGrid a {
-	display: inline-block;
-	background-color: #f9f9f9;
-}
-
-#ktpContainer, #distContainer, #kcspContainer, #isvContainer, #servContainer {
-	position: relative;
-	width: 100%;
-	display: flex;
-	justify-content: space-between;
-	flex-wrap: wrap;
-}
-
-#isvContainer {
-	margin-bottom: 80px;
-}
-
-#kcspContainer {
-	margin-bottom: 80px;
-}
-
-#distContainer {
-	margin-bottom: 80px;
-}
-
-#ktpContainer {
-	margin-bottom: 80px;
-}
-
-.partner-box {
-	position: relative;
-	width: 47%;
-	max-width: 48%;
-	min-width: 48%;
-	margin-bottom: 20px;
-	padding: 20px;
-	flex: 1;
-	display: flex;
-	justify-content: left;
-	align-items: flex-start;
-}
-
-.partner-box img {
-	background-color: #f9f9f9;
-}
-
-.partner-box > div {
-	margin-left: 30px;
-}
-
-.partner-box a {
-	color: #3576E3;
-}
-
-@media screen and (max-width: 1024px) {
-	.partner-box {
-		flex-direction: column;
-		justify-content: flex-start;
-	}
-
-	.partner-box > div {
-		margin: 20px 0 0;
-	}
-}
-
-@media screen and (max-width: 568px) {
-	#ktpContainer, #distContainter, #kcspContainer, #isvContainer, #servContainer {
-		justify-content: center;
-	}
-
-	.partner-box {
-		flex-direction: column;
-		justify-content: flex-start;
-		width: 100%;
-		max-width: 100%;
-		min-width: 100%;
-	}
-
-	.partner-box > div {
-		margin: 20px 0 0;
-	}
-}
-
-@media screen and (max-width: 568px) {
-	#ktpContainer, #distContainer, #kcspContainer, #isvContainer, #servContainer {
-		justify-content: center;
-	}
-
-	.partner-box {
-		flex-direction: column;
-		justify-content: flex-start;
-		width: 100%;
-		max-width: 100%;
-		min-width: 100%;
-	}
-
-	.partner-box > div {
-		margin: 20px 0 0;
-	}
-}
@@ -1,53 +1,91 @@
 ---
 title: Partner
 bigheader: Kubernetes Partner
-abstract: Erweiterung des Kubernetes-Ökosystems.
+abstract: Entwicklung des Kubernetes-Ökosystems.
 class: gridPage
 cid: partners
 ---

 <section id="users">
-    <h5>Kubernetes arbeitet mit Partnern zusammen, um eine starke, lebendige Codebasis zu schaffen, die ein Spektrum von ergänzenden Plattformen unterstützt.</h5>
-    <div class="col-container">
-      <div class="col-nav">
-        <center>
-          <h5>
-            <b>Kubernetes-zertifizierte Service-Anbieter</b>
-          </h5>
-          <br>Geprüfte Dienstleister mit umfassender Erfahrung bei der erfolgreichen Einführung von Kubernetes in Unternehmen.
-          <br><br><br>
-          <button class="button landscape-trigger landscape-default" data-landscape-types="kubernetes-certified-service-provider" id="kcsp">KCSP Partner anzeigen</button>
-          <br><br>Interessiert daran, ein
-          <a href="https://www.cncf.io/certification/kcsp/">KCSP</a> zu werden?
-        </center>
-      </div>
-      <div class="col-nav">
-        <center>
-          <h5>
-            <b>Zertifizierte Kubernetes-Distributionen, gehostete Plattformen und Installationssysteme</b>
-          </h5>Die Softwarekonformität stellt sicher, dass die Kubernetes-Version eines jeden Anbieters die erforderlichen APIs unterstützt.
-          <br><br><br>
-          <button class="button landscape-trigger" data-landscape-types="certified-kubernetes-distribution,certified-kubernetes-hosted,certified-kubernetes-installer" id="conformance">Konforme Partner anzeigen</button>
-          <br><br>Interessiert daran,
-          <a href="https://www.cncf.io/certification/software-conformance/">Kubernetes Zertifiziert</a> zu werden?
-        </center>
-      </div>
-      <div class="col-nav">
-        <center>
-          <h5>
-            <b>Kubernetes Schulungspartner</b>
-          </h5>
-          <br>Geprüfte Schulungsanbieter mit umfassender Erfahrung in der Weiterbildung im Bereich Cloud Native Technology.
-          <br><br><br>
-          <button class="button landscape-trigger" data-landscape-types="kubernetes-training-partner" id="ktp">KTP Partner anzeigen</button>
-          <br><br>Interessiert daran, ein
-          <a href="https://www.cncf.io/certification/training/">KTP</a> zu werden?
-        </center>
-      </div>
+    <main>
+        <h5>Kubernetes arbeitet mit Partnern zusammen, um eine starke, dynamische Codebasis zu schaffen, die ein Spektrum von aufeinander abgestimmten Plattformen unterstützt.</h5>
+        <div class="col-container">
+          <div class="col-nav">
+            <center>
+              <h5>
+                <b>Kubernetes zertifizierte Service Provider</b>
+              </h5>
+              <br>Geprüfte Service Provider mit großer Erfahrung, die Unternehmen bei der erfolgreichen Einführung von Kubernetes unterstützen.
+              <br><br><br>
+              <button id="kcsp" class="button" onClick="updateSrc(this.id)">KCSP-Partner anzeigen</button>
+              <br><br>Interessiert daran, ein <a href="https://www.cncf.io/certification/kcsp/">KCSP</a> zu werden?
+            </center>
+          </div>
+          <div class="col-nav">
+            <center>
+              <h5>
+                <b>Kubernetes-Distributionen, gehostete Plattformen und zertifizierte Installateure</b>
+              </h5>Software-Konformität stellt sicher, dass die Kubernetes-Versionen aller Hersteller die erforderlichen APIs unterstützen.
+              <br><br><br>
+              <button id="conformance" class="button" onClick="updateSrc(this.id)">Zertifizierte Partner anzeigen</button>
+              <br><br>Interessiert daran, <a href="https://www.cncf.io/certification/software-conformance/">Kubernetes zertifiziert</a> zu werden?
+            </center>
+          </div>
+          <div class="col-nav">
+            <center>
+              <h5><b>Kubernetes Training Partner</b></h5>
+              <br>Geprüfte Schulungsanbieter, die über umfassende Erfahrung in Cloud Native Technologietrainings verfügen.
+              <br><br><br><br>
+              <button id="ktp" class="button" onClick="updateSrc(this.id)">KTP Partner anzeigen</button>
+              <br><br>Interessiert daran, ein <a href="https://www.cncf.io/certification/training/">KTP</a> zu werden?
+            </center>
+          </div>
+        </div>
+<script src="https://code.jquery.com/jquery-3.3.1.min.js" integrity="sha256-FgpCb/KJQlLNfOu91ta32o/NMZxltwRo8QtmkMRdAu8=" crossorigin="anonymous"></script>
+<script type="text/javascript">
+
+			var defaultLink = "https://landscape.cncf.io/category=kubernetes-certified-service-provider&format=card-mode&grouping=category&embed=yes";
+			var firstLink = "https://landscape.cncf.io/category=certified-kubernetes-distribution,certified-kubernetes-hosted,certified-kubernetes-installer&format=card-mode&grouping=category&embed=yes";
+      var secondLink = "https://landscape.cncf.io/category=kubernetes-training-partner&format=card-mode&grouping=category&embed=yes";
+
+      function updateSrc(buttonId) {
+      	if (buttonId == "kcsp") {
+        		$("#landscape").attr("src",defaultLink);
+            window.location.hash = "#kcsp";
+        }
+        if (buttonId == "conformance") {
+         		$("#landscape").attr("src",firstLink);
+            window.location.hash = "#conformance";
+        }
+        if (buttonId == "ktp") {
+        		$("#landscape").attr("src",secondLink);
+            window.location.hash = "#ktp";
+        }
+      }
+
+      // Automatically load the correct iframe based on the URL fragment
+      document.addEventListener('DOMContentLoaded', function() {
+        var showContent = "kcsp";
+        if (window.location.hash) {
+          console.log('hash is:', window.location.hash.substring(1));
+          showContent = window.location.hash.substring(1);
+        }
+        updateSrc(showContent);
+      });
+</script>
+<body>
+    <div id="frameHolder">
+      <iframe id="landscape" frameBorder="0" scrolling="no" style="width: 1px; min-width: 100%" src=""></iframe>
+      <script src="https://landscape.cncf.io/iframeResizer.js"></script>
    </div>
-    {{< cncf-landscape helpers=true >}}
+</body>
+    </main>
 </section>

 <style>
    {{< include "partner-style.css" >}}
-</style>
+</style>
+
+<script>
+    {{< include "partner-script.js" >}}
+</script>
@@ -1,137 +0,0 @@
---
-title: Schulungen
-bigheader: Kubernetes Schulungen und Zertifizierungen
-abstract: Schulungsprogramme, Zertifizierungen und Partner.
-layout: basic
-cid: training
-class: training
---
-
-<section class="call-to-action">
-  <div class="main-section">
-    <div class="call-to-action" id="cta-certification">
-      <div class="cta-text">
-        <h2>Gestalte deine Cloud Native Karriere</h2>
-        <p>Kubernetes ist das Herzstück der Cloud Native-Bewegung. Mit den Schulungen und Zertifizierungen der Linux Foundation und unserer Schulungspartner kannst Du in deine Karriere investieren, Kubernetes lernen und deine Cloud Native-Projekte zum Erfolg führen.</p>
-      </div>
-      <div class="logo-certification cta-image" id="logo-kcnf">
-        <img src="/images/training/kubernetes-kcnf-white.svg" />
-      </div>
-      <div class="logo-certification cta-image" id="logo-cka">
-        <img src="/images/training/kubernetes-cka-white.svg"/>
-      </div>
-      <div class="logo-certification cta-image" id="logo-ckad">
-        <img src="/images/training/kubernetes-ckad-white.svg"/>
-      </div>
-      <div class="logo-certification cta-image" id="logo-cks">
-        <img src="/images/training/kubernetes-cks-white.svg"/>
-      </div>
-    </div>
-  </div>
-</section>
-
-<section>
-  <div class="main-section padded">
-    <center>
-      <h2>Nimm an einen kostenlosen Kurs bei edX teil</h2>
-    </center>
-  <div class="col-container">
-    <div class="col-nav">
-      <center>
-        <h5>
-          <b>Einf&uuml;hrung in Kubernetes <br> &nbsp;</b>
-        </h5>
-        <p>M&ouml;chtest Du Kubernetes lernen? Erfahre alles über dieses leistungsstarke System zur Verwaltung von Containeranwendungen.</p>
-        <br>
-        <a href="https://www.edx.org/course/introduction-to-kubernetes" target="_blank" class="button">Zum Kurs</a>
-      </center>
-    </div>
-    <div class="col-nav">
-      <center>
-        <h5>
-          <b>Einführung in Cloud-Infrastruktur Technologien</b>
-        </h5>
-        <p>Lerne die Grundlagen für den Aufbau und die Verwaltung von Cloud-Technologien direkt von der Linux Foundation, dem Marktführer im Bereich Open Source.</p>
-        <br>
-        <a href="https://www.edx.org/course/introduction-to-cloud-infrastructure-technologies" target="_blank" class="button">Zum Kurs</a>
-      </center>
-    </div>
-    <div class="col-nav">
-      <center>
-        <h5>
-          <b>Einf&uuml;hrung in Linux</b>
-        </h5>
-        <p>Du hast nie Linux gelernt? Willst du eine Auffrischung? Erarbeite dir gute Linux-Kenntnisse über die grafische Oberfläche und die Kommandozeile der wichtigsten Linux-Distributionen.</p>
-        <br>
-        <a href="https://www.edx.org/course/introduction-to-linux" target="_blank" class="button">Zum Kurs</a>
-      </center>
-    </div>
-  </div>
-</section>
-
-<div class="padded lighter-gray-bg">
-  <div class="main-section two-thirds-centered">
-    <center>
-      <h2>Mit der Linux Foundation lernen</h2>
-      <p>Die Linux Foundation bietet Kurse für alle Aspekte der Entwicklung und des Betriebs von Kubernetes-Anwendungen an, die entweder von Lehrkräften geleitet werden oder zum Selbststudium geeignet sind.</p>
-      <br/><br/>
-      <a href="https://training.linuxfoundation.org/training/course-catalog/?_sft_technology=kubernetes" target="_blank" class="button">Kurse anzeigen</a>
-    </center>
-  </div>
-</div>
-
-<section id="get-certified">
-  <div class="main-section padded">
-    <h2>Werde Kubernetes zertifiziert</h2>
-    <div class="col-container">
-      <div class="col-nav">
-        <h5>
-          <b>Kubernetes and Cloud Native Associate (KCNA)</b>
-        </h5>
-        <p>Die Prüfung zum Kubernetes and Cloud Native Associate (KCNA) weist die grundlegenden Kenntnisse und Fähigkeiten eines Benutzers in Kubernetes und dem breiteren Cloud Native-Ökosystem nach.</p>
-        <p>Ein zertifizierter KCNA bestätigt konzeptionelles Wissen über das gesamte Cloud Native Ecosystem, mit besonderem Fokus auf Kubernetes.</p>
-        <br>
-        <a href="https://training.linuxfoundation.org/certification/kubernetes-cloud-native-associate/" target="_blank" class="button">Zur Zertifizierung</a>
-      </div>
-      <div class="col-nav">
-          <h5>
-            <b>Certified Kubernetes Application Developer (CKAD)</b>
-          </h5>
-          <p>Die Prüfung zum Certified Kubernetes Application Developer (Zertifizierter Kubernetes-Anwendungsentwickler) bescheinigt, dass Teilnehmer Cloud Native-Anwendungen für Kubernetes entwerfen, erstellen, konfigurieren und bereitstellen können.</p>
-          <p>Ein CKAD kann Anwendungsressourcen definieren und zentrale Elemente verwenden, um skalierbare Anwendungen und Tools in Kubernetes zu erstellen, zu überwachen und Fehler zu beheben.</p>
-          <br>
-          <a href="https://training.linuxfoundation.org/certification/certified-kubernetes-application-developer-ckad/" target="_blank" class="button">Zur Zertifizierung</a>
-      </div>
-      <div class="col-nav">
-          <h5>
-            <b>Certified Kubernetes Administrator (CKA)</b>
-          </h5>
-          <p>Das Certified Kubernetes Administrator (CKA)-Programm garantiert, dass CKAs die Fähigkeiten, das Wissen und die Kompetenz besitzen, um die Aufgaben eines Kubernetes-Administrators zu erfüllen.</p>
-          <p>Ein zertifizierter Kubernetes-Administrator hat nachgewiesen, dass er in der Lage ist, grundlegende Installationen durchzuführen sowie Kubernetes-Cluster in einer Produktionsumgebung zu konfigurieren und zu verwalten.</p>
-          <br>
-          <a href="https://training.linuxfoundation.org/certification/certified-kubernetes-administrator-cka/" target="_blank" class="button">Zur Zertifizierung</a>
-      </div>
-      <div class="col-nav">
-          <h5>
-            <b>Certified Kubernetes Security Specialist (CKS)</b>
-          </h5>
-          <p>Das Programm Certified Kubernetes Security Specialist (CKS) bietet die Gewissheit, dass der Zertifikatsinhaber mit einem breiten Spektrum an Best Practices vertraut ist und diese beherrscht. Die CKS-Zertifizierung umfasst Fähigkeiten zur Sicherung von Container-basierten Anwendungen und Kubernetes-Plattformen während der Erstellung, Bereitstellung und Laufzeit.</p>
-          <p><em>Kandidaten für den CKS müssen über eine aktuelle Zertifizierung als Certified Kubernetes Administrator (CKA) verfügen, um nachzuweisen, dass sie über ausreichende Kubernetes-Kenntnisse verfügen, bevor sie sich für den CKS anmelden.</em></p>
-          <br>
-          <a href="https://training.linuxfoundation.org/certification/certified-kubernetes-security-specialist/" target="_blank" class="button">Zur Zertifizierung</a>
-      </div>
-    </div>
-  </div>
-</section>
-
-<div class="padded lighter-gray-bg">
-  <div class="main-section two-thirds-centered">
-    <center>
-      <h2>Kubernetes Schulungspartner</h2>
-      <p>Unser Netzwerk von Kubernetes-Schulungspartnern bietet Schulungsangebote für Kubernetes- und Cloud Native-Projekte.</p>
-    </center>
-  </div>
-  <div class="main-section landscape-section">
-    {{< cncf-landscape helpers=false category="kubernetes-training-partner" >}}
-  </div>
-</div>
@@ -8,7 +8,7 @@ sitemap:

 {{< blocks/section id="oceanNodes" >}}
 {{% blocks/feature image="flower" %}}
-[Kubernetes]({{< relref "/docs/concepts/overview/what-is-kubernetes" >}}), also known as K8s, is an open-source system for automating deployment, scaling, and management of containerized applications.
+[Kubernetes (K8s)]({{< relref "/docs/concepts/overview/what-is-kubernetes" >}}) is an open-source system for automating deployment, scaling, and management of containerized applications.

 It groups containers that make up an application into logical units for easy management and discovery. Kubernetes builds upon [15 years of experience of running production workloads at Google](http://queue.acm.org/detail.cfm?id=2898444), combined with best-of-breed ideas and practices from the community.
 {{% /blocks/feature %}}
@@ -28,7 +28,7 @@ Whether testing locally or running a global enterprise, Kubernetes flexibility g
 {{% /blocks/feature %}}

 {{% blocks/feature image="suitcase" %}}
-#### Run K8s Anywhere
+#### Run Anywhere

 Kubernetes is open source giving you the freedom to take advantage of on-premises, hybrid, or public cloud infrastructure, letting you effortlessly move workloads to where it matters to you.

@@ -43,12 +43,12 @@ Kubernetes is open source giving you the freedom to take advantage of on-premise
        <button id="desktopShowVideoButton" onclick="kub.showVideo()">Watch Video</button>
        <br>
        <br>
-        <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe-2022/?utm_source=kubernetes.io&utm_medium=nav&utm_campaign=kccnceu22" button id="desktopKCButton">Attend KubeCon Europe on May 17-20, 2022</a>
+        <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/?utm_source=kubernetes.io&utm_medium=nav&utm_campaign=kccncna20" button id="desktopKCButton">Attend KubeCon NA virtually on November 17-20, 2020</a>
        <br>
        <br>
        <br>
        <br>
-        <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/?utm_source=kubernetes.io&utm_medium=nav&utm_campaign=kccncna21" button id="desktopKCButton">Attend KubeCon North America on October 24-28, 2022</a>
+        <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/?utm_source=kubernetes.io&utm_medium=nav&utm_campaign=kccnceu21" button id="desktopKCButton">Attend KubeCon EU virtually on May 4 – 7, 2021</a>
 </div>
 <div id="videoPlayer">
    <iframe data-url="https://www.youtube.com/embed/H06qrNmGqyE?autoplay=1" frameborder="0" allowfullscreen></iframe>
@@ -58,4 +58,4 @@ Kubernetes is open source giving you the freedom to take advantage of on-premise

 {{< blocks/kubernetes-features >}}

-{{< blocks/case-studies >}}
+{{< blocks/case-studies >}}
@@ -26,7 +26,7 @@ On the other hand, CNI is more philosophically aligned with Kubernetes. It's far

 Additionally, it's trivial to wrap a CNI plugin and produce a more customized CNI plugin — it can be done with a simple shell script. CNM is much more complex in this regard. This makes CNI an attractive option for rapid development and iteration. Early prototypes have proven that it's possible to eject almost 100% of the currently hard-coded network logic in kubelet into a plugin.  

-We investigated [writing a "bridge" CNM driver](https://groups.google.com/g/kubernetes-sig-network/c/5MWRPxsURUw) for Docker that ran CNI drivers. This turned out to be very complicated. First, the CNM and CNI models are very different, so none of the "methods" lined up. We still have the global vs. local and key-value issues discussed above. Assuming this driver would declare itself local, we have to get info about logical networks from Kubernetes.  
+We investigated [writing a "bridge" CNM driver](https://groups.google.com/forum/#!topic/kubernetes-sig-network/5MWRPxsURUw) for Docker that ran CNI drivers. This turned out to be very complicated. First, the CNM and CNI models are very different, so none of the "methods" lined up. We still have the global vs. local and key-value issues discussed above. Assuming this driver would declare itself local, we have to get info about logical networks from Kubernetes.  

 Unfortunately, Docker drivers are hard to map to other control planes like Kubernetes. Specifically, drivers are not told the name of the network to which a container is being attached — just an ID that Docker allocates internally. This makes it hard for a driver to map back to any concept of network that exists in another system.  

@@ -34,6 +34,6 @@ This and other issues have been brought up to Docker developers by network vendo

 For all of these reasons we have chosen to invest in CNI as the Kubernetes plugin model. There will be some unfortunate side-effects of this. Most of them are relatively minor (for example, `docker inspect` will not show an IP address), but some are significant. In particular, containers started by `docker run` might not be able to communicate with containers started by Kubernetes, and network integrators will have to provide CNI drivers if they want to fully integrate with Kubernetes. On the other hand, Kubernetes will get simpler and more flexible, and a lot of the ugliness of early bootstrapping (such as configuring Docker to use our bridge) will go away.  

-As we proceed down this path, we’ll certainly keep our eyes and ears open for better ways to integrate and simplify. If you have thoughts on how we can do that, we really would like to hear them — find us on [slack](http://slack.k8s.io/) or on our [network SIG mailing-list](https://groups.google.com/g/kubernetes-sig-network).  
+As we proceed down this path, we’ll certainly keep our eyes and ears open for better ways to integrate and simplify. If you have thoughts on how we can do that, we really would like to hear them — find us on [slack](http://slack.k8s.io/) or on our [network SIG mailing-list](https://groups.google.com/forum/#!forum/kubernetes-sig-network).  

 Tim Hockin, Software Engineer, Google
@@ -125,7 +125,7 @@ You may wish to, but you cannot create a hierarchy of namespaces. Namespaces can



-Namespaces are easy to create and use but it’s also easy to deploy code inadvertently into the wrong namespace. Good DevOps hygiene suggests documenting and automating processes where possible and this will help. The other way to avoid using the wrong namespace is to set a [kubectl context](/docs/reference/generated/kubectl/kubectl-commands#-em-set-context-em-).&nbsp;
+Namespaces are easy to create and use but it’s also easy to deploy code inadvertently into the wrong namespace. Good DevOps hygiene suggests documenting and automating processes where possible and this will help. The other way to avoid using the wrong namespace is to set a [kubectl context](/docs/user-guide/kubectl/kubectl_config_set-context/).&nbsp;



@@ -5,11 +5,6 @@ slug: visualize-kubelet-performance-with-node-dashboard
 url: /blog/2016/11/Visualize-Kubelet-Performance-With-Node-Dashboard
 ---

-_Since this article was published, the Node Performance Dashboard was retired and is no longer available._
-
-_This retirement happened in early 2019, as part of the_ `kubernetes/contrib`
-_[repository deprecation](https://github.com/kubernetes-retired/contrib/issues/3007)_.
-
 In Kubernetes 1.4, we introduced a new node performance analysis tool, called the _node performance dashboard_, to visualize and explore the behavior of the Kubelet in much richer details. This new feature will make it easy to understand and improve code performance for Kubelet developers, and lets cluster maintainer set configuration according to provided Service Level Objectives (SLOs).  

 **Background**  
@@ -37,7 +37,7 @@ If you run your storage application on high-end hardware or extra-large instance
 [ZooKeeper](https://zookeeper.apache.org/doc/current/) is an interesting use case for StatefulSet for two reasons. First, it demonstrates that StatefulSet can be used to run a distributed, strongly consistent storage application on Kubernetes. Second, it's a prerequisite for running workloads like [Apache Hadoop](http://hadoop.apache.org/) and [Apache Kakfa](https://kafka.apache.org/) on Kubernetes. An [in-depth tutorial](/docs/tutorials/stateful-application/zookeeper/) on deploying a ZooKeeper ensemble on Kubernetes is available in the Kubernetes documentation, and we’ll outline a few of the key features below.  

 **Creating a ZooKeeper Ensemble**  
-Creating an ensemble is as simple as using [kubectl create](/docs/reference/generated/kubectl/kubectl-commands#create) to generate the objects stored in the manifest.  
+Creating an ensemble is as simple as using [kubectl create](/docs/user-guide/kubectl/kubectl_create/) to generate the objects stored in the manifest.  


 ```
@@ -297,7 +297,7 @@ zk-0      0/1       Terminating   0         15m



-You can use [kubectl apply](/docs/reference/generated/kubectl/kubectl-commands#apply) to recreate the zk StatefulSet and redeploy the ensemble.
+You can use [kubectl apply](/docs/user-guide/kubectl/kubectl_apply/) to recreate the zk StatefulSet and redeploy the ensemble.



@@ -20,14 +20,21 @@ For example, if we want to require scheduling on a node that is in the us-centra


 ```
-  affinity:
-    nodeAffinity:
-      requiredDuringSchedulingIgnoredDuringExecution:
-        nodeSelectorTerms:
-          - matchExpressions:
-            - key: "failure-domain.beta.kubernetes.io/zone"
-              operator: In
-              values: ["us-central1-a"]
+affinity:
+
+  nodeAffinity:
+
+    requiredDuringSchedulingIgnoredDuringExecution:
+
+      nodeSelectorTerms:
+
+        - matchExpressions:
+
+          - key: "failure-domain.beta.kubernetes.io/zone"
+
+            operator: In
+
+            values: ["us-central1-a"]
 ```


@@ -37,14 +44,21 @@ Preferred rules mean that if nodes match the rules, they will be chosen first, a


 ```
-  affinity:
-    nodeAffinity:
-      preferredDuringSchedulingIgnoredDuringExecution:
-        nodeSelectorTerms:
-          - matchExpressions:
-            - key: "failure-domain.beta.kubernetes.io/zone"
-              operator: In
-              values: ["us-central1-a"]
+affinity:
+
+  nodeAffinity:
+
+    preferredDuringSchedulingIgnoredDuringExecution:
+
+      nodeSelectorTerms:
+
+        - matchExpressions:
+
+          - key: "failure-domain.beta.kubernetes.io/zone"
+
+            operator: In
+
+            values: ["us-central1-a"]
 ```


@@ -53,14 +67,21 @@ Node anti-affinity can be achieved by using negative operators. So for instance


 ```
-  affinity:
-    nodeAffinity:
-      requiredDuringSchedulingIgnoredDuringExecution:
-        nodeSelectorTerms:
-          - matchExpressions:
-            - key: "failure-domain.beta.kubernetes.io/zone"
-              operator: NotIn
-              values: ["us-central1-a"]
+affinity:
+
+  nodeAffinity:
+
+    requiredDuringSchedulingIgnoredDuringExecution:
+
+      nodeSelectorTerms:
+
+        - matchExpressions:
+
+          - key: "failure-domain.beta.kubernetes.io/zone"
+
+            operator: NotIn
+
+            values: ["us-central1-a"]
 ```


@@ -78,7 +99,7 @@ The kubectl command allows you to set taints on nodes, for example:

 ```
 kubectl taint nodes node1 key=value:NoSchedule
-```
+ ```


 creates a taint that marks the node as unschedulable by any pods that do not have a toleration for taint with key key, value value, and effect NoSchedule. (The other taint effects are PreferNoSchedule, which is the preferred version of NoSchedule, and NoExecute, which means any pods that are running on the node when the taint is applied will be evicted unless they tolerate the taint.) The toleration you would add to a PodSpec to have the corresponding pod tolerate this taint would look like this  
@@ -86,11 +107,15 @@ creates a taint that marks the node as unschedulable by any pods that do not hav


 ```
-  tolerations:
-  - key: "key"
-    operator: "Equal"
-    value: "value"
-    effect: "NoSchedule"
+tolerations:
+
+- key: "key"
+
+  operator: "Equal"
+
+  value: "value"
+
+  effect: "NoSchedule"
 ```


@@ -113,13 +138,21 @@ Let’s look at an example. Say you have front-ends in service S1, and they comm

 ```
 affinity:
+
    podAffinity:
+
      requiredDuringSchedulingIgnoredDuringExecution:
+
      - labelSelector:
+
          matchExpressions:
+
          - key: service
+
            operator: In
+
            values: [“S1”]
+
        topologyKey: failure-domain.beta.kubernetes.io/zone
 ```

@@ -139,15 +172,25 @@ Here we have a Pod where we specify the schedulerName field:

 ```
 apiVersion: v1
+
 kind: Pod
+
 metadata:
+
  name: nginx
+
  labels:
+
    app: nginx
+
 spec:
+
  schedulerName: my-scheduler
+
  containers:
+
  - name: nginx
+
    image: nginx:1.10
 ```

@@ -56,13 +56,13 @@ Cri-containerd uses containerd to manage the full container lifecycle and all co

 Let’s use an example to demonstrate how cri-containerd works for the case when Kubelet creates a single-container pod:  

-1. Kubelet calls cri-containerd, via the CRI runtime service API, to create a pod;
-2. cri-containerd uses containerd to create and start a special [pause container](https://www.ianlewis.org/en/almighty-pause-container) (the _sandbox container_) and put that container inside the pod’s cgroups and namespace (steps omitted for brevity);
-3. cri-containerd configures the pod’s network namespace using CNI;
-4. Kubelet subsequently calls cri-containerd, via the CRI image service API, to pull the application container image;
-5. cri-containerd further uses containerd to pull the image if the image is not present on the node;
-6. Kubelet then calls cri-containerd, via the CRI runtime service API, to create and start the application container inside the pod using the pulled container image;
-7. cri-containerd finally calls containerd to create the application container, put it inside the pod’s cgroups and namespace, then to start the pod’s new application container.
+1. 1.Kubelet calls cri-containerd, via the CRI runtime service API, to create a pod;
+2. 2.cri-containerd uses containerd to create and start a special [pause container](https://www.ianlewis.org/en/almighty-pause-container) (the _sandbox container_) and put that container inside the pod’s cgroups and namespace (steps omitted for brevity);
+3. 3.cri-containerd configures the pod’s network namespace using CNI;
+4. 4.Kubelet subsequently calls cri-containerd, via the CRI image service API, to pull the application container image;
+5. 5.cri-containerd further uses containerd to pull the image if the image is not present on the node;
+6. 6.Kubelet then calls cri-containerd, via the CRI runtime service API, to create and start the application container inside the pod using the pulled container image;
+7. 7.cri-containerd finally calls containerd to create the application container, put it inside the pod’s cgroups and namespace, then to start the pod’s new application container.
 After these steps, a pod and its corresponding application container is created and running.


@@ -95,7 +95,7 @@ The core workloads API surface is stable, but it’s still software, and softwar
 --Kenneth Owens, Software Engineer, Google  


- [Download](https://get.k8s.io/) Kubernetes
+- [Download](http://get.k8s.io/) Kubernetes
 - Get involved with the Kubernetes project on [GitHub](https://github.com/kubernetes/kubernetes)
 - Post questions (or answer questions) on [Stack Overflow](http://stackoverflow.com/questions/tagged/kubernetes)
 - Connect with the community on [Slack](http://slack.k8s.io/)
@@ -140,7 +140,7 @@ The local persistent volume beta feature is not complete by far. Some notable en

 ## Complementary features

-[Pod priority and preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/) is another Kubernetes feature that is complementary to local persistent volumes. When your application uses local storage, it must be scheduled to the specific node where the local volume resides. You can give your local storage workload high priority so if that node ran out of room to run your workload, Kubernetes can preempt lower priority workloads to make room for it.
+[Pod priority and preemption](/docs/concepts/configuration/pod-priority-preemption/) is another Kubernetes feature that is complementary to local persistent volumes. When your application uses local storage, it must be scheduled to the specific node where the local volume resides. You can give your local storage workload high priority so if that node ran out of room to run your workload, Kubernetes can preempt lower priority workloads to make room for it.

 [Pod disruption budget](/docs/concepts/workloads/pods/disruptions/) is also very important for those workloads that must maintain quorum. Setting a disruption budget for your workload ensures that it does not drop below quorum due to voluntary disruption events, such as node drains during upgrade.

@@ -94,7 +94,7 @@ JOSH BERKUS: That goes into release notes. I mean, keep in mind that one of the

 However, stuff happens, and we do occasionally have to do those. And so far, our main way to identify that to people actually is in the release notes. If you look at [the current release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md#no-really-you-must-do-this-before-you-upgrade), there are actually two things in there right now that are sort of breaking changes. 

-One of them is the bit with [priority and preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/) in that preemption being on by default now allows badly behaved users of the system to cause trouble in new ways. I'd actually have to look at the release notes to see what the second one was...
+One of them is the bit with [priority and preemption](/docs/concepts/configuration/pod-priority-preemption/) in that preemption being on by default now allows badly behaved users of the system to cause trouble in new ways. I'd actually have to look at the release notes to see what the second one was...

 TIM PEPPER: The [JSON capitalization case sensitivity](https://github.com/kubernetes/kubernetes/issues/64612). 

@@ -104,7 +104,7 @@ Master and Worker nodes should be protected from overload and resource exhaustio

 Resource consumption by the control plane will correlate with the number of pods and the pod churn rate. Very large and very small clusters will benefit from non-default [settings](/docs/reference/command-line-tools-reference/kube-apiserver/) of kube-apiserver request throttling and memory. Having these too high can lead to request limit exceeded and out of memory errors.

-On worker nodes, [Node Allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/) should be configured based on a reasonable supportable workload density at each node. Namespaces can be created to subdivide the worker node cluster into multiple virtual clusters with resource CPU and memory [quotas](/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/). Kubelet handling of [out of resource](/docs/concepts/scheduling-eviction/node-pressure-eviction/) conditions can be configured.
+On worker nodes, [Node Allocatable](/docs/tasks/administer-cluster/reserve-compute-resources/) should be configured based on a reasonable supportable workload density at each node. Namespaces can be created to subdivide the worker node cluster into multiple virtual clusters with resource CPU and memory [quotas](/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/). Kubelet handling of [out of resource](/docs/tasks/administer-cluster/out-of-resource/) conditions can be configured.

 ## Security

@@ -166,7 +166,7 @@ Some critical state is held outside etcd. Certificates, container images, and ot
 * Cloud provider specific account and configuration data

 ## Considerations for your production workloads
-Anti-affinity specifications can be used to split clustered services across backing hosts, but at this time the settings are used only when the pod is scheduled. This means that Kubernetes can restart a failed node of your clustered application, but does not have a native mechanism to rebalance after a fail back. This is a topic worthy of a separate blog, but supplemental logic might be useful to achieve optimal workload placements after host or worker node recoveries or expansions. The [Pod Priority and Preemption feature](/docs/concepts/scheduling-eviction/pod-priority-preemption/) can be used to specify a preferred triage in the event of resource shortages caused by failures or bursting workloads.
+Anti-affinity specifications can be used to split clustered services across backing hosts, but at this time the settings are used only when the pod is scheduled. This means that Kubernetes can restart a failed node of your clustered application, but does not have a native mechanism to rebalance after a fail back. This is a topic worthy of a separate blog, but supplemental logic might be useful to achieve optimal workload placements after host or worker node recoveries or expansions. The [Pod Priority and Preemption feature](/docs/concepts/configuration/pod-priority-preemption/) can be used to specify a preferred triage in the event of resource shortages caused by failures or bursting workloads.

 For stateful services, external attached volume mounts are the standard Kubernetes recommendation for a non-clustered service (e.g., a typical SQL database). At this time Kubernetes managed snapshots of these external volumes is in the category of a [roadmap feature request](https://docs.google.com/presentation/d/1dgxfnroRAu0aF67s-_bmeWpkM1h2LCxe6lB1l1oS0EQ/edit#slide=id.g3ca07c98c2_0_47), likely to align with the Container Storage Interface (CSI) integration. Thus performing backups of such a service would involve application specific, in-pod activity that is beyond the scope of this document. While awaiting better Kubernetes support for a snapshot and backup workflow, running your database service in a VM rather than a container, and exposing it to your Kubernetes workload may be worth considering.

@@ -176,7 +176,7 @@ Cluster-distributed stateful services (e.g., Cassandra) can benefit from splitti

 [Logs](/docs/concepts/cluster-administration/logging/) and [metrics](/docs/tasks/debug-application-cluster/resource-usage-monitoring/) (if collected and persistently retained) are valuable to diagnose outages, but given the variety of technologies available it will not be addressed in this blog. If Internet connectivity is available, it may be desirable to retain logs and metrics externally at a central location.

-Your production deployment should utilize an automated installation, configuration and update tool (e.g., [Ansible](https://github.com/kubernetes-incubator/kubespray), [BOSH](https://github.com/cloudfoundry-incubator/kubo-deployment), [Chef](https://github.com/chef-cookbooks/kubernetes), [Juju](/docs/getting-started-guides/ubuntu/installation/), [kubeadm](/docs/reference/setup-tools/kubeadm/), [Puppet](https://forge.puppet.com/puppetlabs/kubernetes), etc.). A manual process will have repeatability issues, be labor intensive, error prone, and difficult to scale. [Certified distributions](https://www.cncf.io/certification/software-conformance/#logos) are likely to include a facility for retaining configuration settings across updates, but if you implement your own install and config toolchain, then retention, backup and recovery of the configuration artifacts is essential. Consider keeping your deployment components and settings under a version control system such as Git.
+Your production deployment should utilize an automated installation, configuration and update tool (e.g., [Ansible](https://github.com/kubernetes-incubator/kubespray), [BOSH](https://github.com/cloudfoundry-incubator/kubo-deployment), [Chef](https://github.com/chef-cookbooks/kubernetes), [Juju](/docs/getting-started-guides/ubuntu/installation/), [kubeadm](/docs/reference/setup-tools/kubeadm/kubeadm/), [Puppet](https://forge.puppet.com/puppetlabs/kubernetes), etc.). A manual process will have repeatability issues, be labor intensive, error prone, and difficult to scale. [Certified distributions](https://www.cncf.io/certification/software-conformance/#logos) are likely to include a facility for retaining configuration settings across updates, but if you implement your own install and config toolchain, then retention, backup and recovery of the configuration artifacts is essential. Consider keeping your deployment components and settings under a version control system such as Git.

 ## Outage recovery

@@ -17,7 +17,7 @@ Let’s dive into the key features of this release:

 ## Simplified Kubernetes Cluster Management with kubeadm in GA

-Most people who have gotten hands-on with Kubernetes have at some point been hands-on with kubeadm. It's an essential tool for managing the cluster lifecycle, from creation to configuration to upgrade; and now kubeadm is officially GA. [kubeadm](/docs/reference/setup-tools/kubeadm/) handles the bootstrapping of production clusters on existing hardware and configuring the core Kubernetes components in a best-practice-manner to providing a secure yet easy joining flow for new nodes and supporting easy upgrades. What’s notable about this GA release are the now graduated advanced features, specifically around pluggability and configurability. The scope of kubeadm is to be a toolbox for both admins and automated, higher-level system and this release is a significant step in that direction.
+Most people who have gotten hands-on with Kubernetes have at some point been hands-on with kubeadm. It's an essential tool for managing the cluster lifecycle, from creation to configuration to upgrade; and now kubeadm is officially GA. [kubeadm](/docs/reference/setup-tools/kubeadm/kubeadm/) handles the bootstrapping of production clusters on existing hardware and configuring the core Kubernetes components in a best-practice-manner to providing a secure yet easy joining flow for new nodes and supporting easy upgrades. What’s notable about this GA release are the now graduated advanced features, specifically around pluggability and configurability. The scope of kubeadm is to be a toolbox for both admins and automated, higher-level system and this release is a significant step in that direction.

 ## Container Storage Interface (CSI) Goes GA

@@ -66,7 +66,6 @@ Vagrant.configure("2") do |config|
            end
        end
    end
-end
 ```

 ### Step 2: Create an Ansible playbook for Kubernetes master.
@@ -144,9 +144,10 @@ ways to address it.
 - Specifically add an iptables rule to drop the packets that are marked as
  *INVALID*, so it won’t reach to client pod and cause harm.

-The [fix](https://github.com/kubernetes/kubernetes/pull/74840) is available in v1.15+.
-However, for the users that are affected by this bug, there is a way to mitigate the
-problem by applying the following rule in your cluster.
+The fix is drafted (https://github.com/kubernetes/kubernetes/pull/74840), but
+unfortunately it didn’t catch the v1.14 release window. However, for the users
+that are affected by this bug, there is a way to mitigate the problem by applying
+the following rule in your cluster.

 ```yaml
 apiVersion: extensions/v1beta1
@@ -8,11 +8,11 @@ date: 2019-04-16

 Kubernetes is well-known for running scalable workloads. It scales your workloads based on their resource usage. When a workload is scaled up, more instances of the application get created. When the application is critical for your product, you want to make sure that these new instances are scheduled even when your cluster is under resource pressure. One obvious solution to this problem is to over-provision your cluster resources to have some amount of slack resources available for scale-up situations. This approach often works, but costs more as you would have to pay for the resources that are idle most of the time.

-[Pod priority and preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/) is a scheduler feature made generally available in Kubernetes 1.14 that allows you to achieve high levels of scheduling confidence for your critical workloads without overprovisioning your clusters. It also provides a way to improve resource utilization in your clusters without sacrificing the reliability of your essential workloads.
+[Pod priority and preemption](https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/) is a scheduler feature made generally available in Kubernetes 1.14 that allows you to achieve high levels of scheduling confidence for your critical workloads without overprovisioning your clusters. It also provides a way to improve resource utilization in your clusters without sacrificing the reliability of your essential workloads.

 ## Guaranteed scheduling with controlled cost

-[Kubernetes Cluster Autoscaler](https://github.com/kubernetes/autoscaler/) is an excellent tool in the ecosystem which adds more nodes to your cluster when your applications need them. However, cluster autoscaler has some limitations and may not work for all users:
+[Kubernetes Cluster Autoscaler](https://kubernetes.io/docs/tasks/administer-cluster/cluster-management/#cluster-autoscaling) is an excellent tool in the ecosystem which adds more nodes to your cluster when your applications need them. However, cluster autoscaler has some limitations and may not work for all users:

 - It does not work in physical clusters.
 - Adding more nodes to the cluster costs more.
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Kubernetes Prow Robot	53ff5add0f	Merge pull request #27500 from shuuji3/patch-4 Fix small errors on setup/best-practices/multiple-zones	2021-04-14 21:19:49 -07:00
TAKAHASHI Shuuji	468fa917d8	Translate one sentence and fix minor errors	2021-04-11 12:37:34 +09:00