Add release notes for 1.11 (#9287 )

Release docs for Kubernetes 1.11 (#9171 )
* Seperate priority and preemption (#8144) * Doc about PID pressure condition. (#8211) * Doc about PID pressure condition. Signed-off-by: Da K. Ma <klaus1982.cn@gmail.com> * "so" -> "too" * Update version selector for 1.11 * StorageObjectInUseProtection is GA (#8291) * Feature gate: StorageObjectInUseProtection is GA Update feature gate reference for 1.11 * Trivial commit to re-trigger Netlify * CRIContainerLogRotation is Beta in 1.11 (#8665) * Seperate priority and preemption (#8144) * CRIContainerLogRotation is Beta in 1.11 xref: kubernetes/kubernetes#64046 * Bring StorageObjectInUseProtection feature to GA (#8159) * StorageObjectInUseProtection is GA (#8291) * Feature gate: StorageObjectInUseProtection is GA Update feature gate reference for 1.11 * Trivial commit to re-trigger Netlify * Bring StorageObjectInUseProtection feature to GA StorageObjectInUseProtection is Beta in K8s 1.10. It's brought to GA in K8s 1.11. * Fixed typo and added feature state tags. * Remove KUBE_API_VERSIONS doc (#8292) The support to the KUBER_API_VERSIONS environment variable is completely dropped (no deprecation). This PR removes the related doc in release-1.11. xref: kubernetes/kubernetes#63165 * Remove InitialResources from admission controllers (#8293) The feature (was experimental) is dropped in 1.11. xref: kubernetes/kubernetes#58784 * Remove docs related to in-tree support to GPU (#8294) * Remove docs related to in-tree support to GPU The in-tree support to GPU is completely removed in release 1.11. This PR removes the related docs in release-1.11 branch. xref: kubernetes/kubernetes#61498 * Update content updated by PR to Hugo syntax Signed-off-by: Misty Stanley-Jones <mistyhacks@google.com> * Update the doc about extra volume in kubeadm config (#8453) Signed-off-by: Xianglin Gao <xianglin.gxl@alibaba-inc.com> * Update CRD Subresources for 1.11 (#8519) * coredns: update notes in administer-cluster/coredns.md (#8697) CoreDNS is installed by default in 1.11. Add notes on how to install kube-dns instead. Update notes about CoreDNS->CoreDNS upgrades as in 1.11 the Corefile is retained. Add example on upgrading from kube-dns to CoreDNS. * kubeadm-alpha: CoreDNS related changes (#8727) Update note about CoreDNS feature gate. This change also updates a tab as a kubeadm sub-command will change. It looks for a new generated file: generated/kubeadm_alpha_phase_addon_coredns.md instead of: generated/kubeadm_alpha_phase_addon_kube-dns.md * Update cloud controller manager docs to beta 1.11 (#8756) * Update cloud controller manager docs to beta 1.11 * Use Hugo shortcode for feature state * kubeadm-upgrade: include new command `kubeadm upgrade diff` (#8617) Also: - Include note that this was added in 1.11. - Modify the note about upgrade guidance. * independent: update CoreDNS mentions for kubeadm (#8753) Give CoreDNS instead of kube-dns examples in: - docs/setup/independent/create-cluster-kubeadm.md - docs/setup/independent/troubleshooting-kubeadm.md * update 1.11 --server-print info (#8870) * update 1.11 --server-print info * Copyedit * Mark ExpandPersistentVolumes feature to beta (#8778) * Update version selector for 1.11 * Mark ExpandPersistentVolumes Beta xref: kubernetes/kubernetes#64288 * fix shortcode, add placeholder files to fix deploy failures (#8874) * declare ipvs ga (#8850) * kubeadm: update info about CoreDNS in kubeadm-init.md (#8728) Add info to install kube-dns instead of CoreDNS, as CoreDNS is the default DNS server in 1.11. Add notes that kubeadm config images can be used to list and pull the required images in 1.11. * kubeadm: update implementation-details.md about CoreDNS (#8829) - Replace examples from kube-dns to CoreDNS - Add notes about the CoreDNS feature gate status in 1.11 - Add note that the service name for CoreDNS is also called `kube-dns` * Update block device support for 1.11 (#8895) * Update block device support for 1.11 * Copyedits * Fix typo 'fiber channel' (#8957) Signed-off-by: Misty Stanley-Jones <mistyhacks@google.com> * kubeadm-upgrade: add the 'node [config]' sub-command (#8960) - Add includes for the generated pages - Include placeholder generated pages * kubeadm-init: update the example for the MasterConfiguration (#8958) - include godocs link for MasterConfiguration - include example MasterConfiguration - add note that `kubeadm config print-default` can be used * kubeadm-config: include new commands (#8862) Add notes and includes for these new commands in 1.11: - kubeadm config print-default - kubeadm config migrate - kubeadm config images list - kubeadm config images pull Include placeholder generated files for the above. * administer-cluster/coredns: include more changes (#8985) It was requested that for this page a couple of methods should be outlined: - manual installation for CoreDNS explained at the Kubernetes section of the GitHub project for CoreDNS - installation and upgrade via kubeadm Make the above changes and also add a section "About CoreDNS". This commit also lowercases a section title. * Update CRD subresources doc for 1.11 (#8918) * Add docs for volume expansion and online resizing (#8896) * Add docs for volume expansion going beta * Copyedit * Address feedback * Update exec plugin docs with TLS credentials (#8826) * Update exec plugin docs with TLS credentials kubernetes/kubernetes#61803 implements TLS client credential support for 1.11. * Copyedit * More copyedits for clarification * Additional copyedit * Change token->credential * NodeRestriction admission prevents kubelet taint removal (#8911) * dns-custom-namerserver: break down the page into mutliple sections (#8900) * dns-custom-namerserver: break down the page into mutliple sections This page is currently about kube-dns and is a bit outdated. Introduce the heading `# Customizing kube-dns`. Introduce a separate section about CoreDNS. * Copyedits, fix headings for customizing DNS Hey Lubomir, I coypedited pretty heavily because this workflow is so much easier for docs and because I'm trying to help improve everything touching kubeadm as much as possible. But there's one outstanding issue wrt headings and intro content: you can't add a heading 1 to a topic to do what you wanted to do. The page title in the front matter is rendered as a heading 1 and everything else has to start at heading 2. (We still need to doc this better in the docs contributing content, I know.) Instead, I think we need to rewrite the top-of-page intro content to explain better the relationship between kube-dns and CoreDNS. I'm happy to write something, but I thought I'd push this commit first so you can see what I'm doing. Hope it's all clear -- ping here or on Slack with any questions ~ Jennifer * Interim fix for talking about CoreDNS * Fix CoreDNS details * PSP readOnly hostPath (#8898) * Add documentation for crictl (#8880) * Add documentation for crictl * Copyedit Signed-off-by: Misty Stanley-Jones <mistyhacks@google.com> * Final copyedit * VolumeSubpathEnvExpansion alpha feature (#8835) * Note that Heapster is deprecated (#8827) * Note that Heapster is deprecated This notes that Heapster is deprecated, and migrates the relevant docs to talk about metrics-server or other solutions by default. * Copyedits and improvements Signed-off-by: Misty Stanley-Jones <mistyhacks@google.com> * Address feedback * fix shortcode to troubleshoot deploy (#9057) * update dynamic kubelet config docs for v1.11 (#8766) * update dynamic kubelet config docs for v1.11 * Substantial copyedit * Address feedback * Reference doc for kubeadm (release-1.11) (#9044) * Reference doc for kubeadm (release-1.11) * fix shortcode to troubleshoot deploy (#9057) * Reference doc for kube-components (release-1.11) (#9045) * Reference doc for kube-components (release-1.11) * Update cloud-controller-manager.md * fix shortcode to troubleshoot deploy (#9057) * Documentation on lowercasing kubeadm init apiserver SANs (#9059) * Documentation on lowercasing kubeadm init apiserver SANs * fix shortcode to troubleshoot deploy (#9057) * Clarification in dynamic Kubelet config doc (#9061) * Promote sysctls to Beta (#8804) * Promote sysctls to Beta * Copyedits Signed-off-by: Misty Stanley-Jones <mistyhacks@google.com> * Review comments * Address feedback * More feedback * kubectl reference docs for 1.11 (#9080) * Update Kubernetes API 1.11 ref docs (#8977) * Update v1alpha1 to v1beta1. * Adjust left nav for 1.11 ref docs. * Trim list of old ref docs. * Update Federation API ref docs for 1.11. (#9064) * Update Federation API ref docs for 1.11. * Add titles. * Update definitions.html * CRD versioning Public Documentation (#8834) * CRD versioning Public Documentation * Copyedit Signed-off-by: Misty Stanley-Jones <mistyhacks@google.com> * Address feedback * More rewrites * Address feedback * Update main CRD page in light of versioning * Reorg CRD docs * Further reorg * Tweak title * CSI documentation update for raw block volume support (#8927) * CSI documetation update for raw block volume support * minor edits for "CSI raw block volume support" Some small grammar and style nits. * minor CSIBlockVolume edits * Update kubectl component ref page for 1.11. (#9094) * Update kubectl component ref page for 1.11. * Add title. Replace stevepe with username. * crd versioning doc: fix nits (#9142) * Update `DynamicKubeletConfig` feature to beta (#9110) xref: kubernetes/kubernetes#64275 * Documentation for dynamic volume limits based on node type (#8871) * add cos for storage limits * Update docs specific for aws and gce * fix some minor things * Update storage-limits.md * Add k8s version to feature-state shortcode * The Doc update for ScheduleDaemonSetPods (#8842) Signed-off-by: Da K. Ma <klaus1982.cn@gmail.com> * Update docs related to PersistentVolumeLabel admission control (#9109) The said admission controller is disabled by default in 1.11 (kubernetes/kubernetes#64326) and scheduled to be removed in future release. * client exec auth: updates for 1.11 (#9154) * Updates HA kubeadm docs (#9066) * Updates HA kubeadm docs Signed-off-by: Chuck Ha <ha.chuck@gmail.com> * kubeadm HA - Add stacked control plane steps * ssh instructions and some typos in the bash scripts Signed-off-by: Chuck Ha <ha.chuck@gmail.com> * Fix typos and copypasta errors * Fix rebase issues * Integrate more changes Signed-off-by: Chuck Ha <ha.chuck@gmail.com> * copyedits, layout and formatting fixes * final copyedits * Adds a sanity check for load balancer connection Signed-off-by: Chuck Ha <ha.chuck@gmail.com> * formatting fixes, copyedits * fix typos, formatting * Document the Pod Ready++ feature (#9180) Closes: #9107 Xref: kubernetes/kubernetes#64057 * Mention 'KubeletPluginsWatcher' feature (#9177) * Mention 'KubeletPluginsWatcher' feature This feature is more developers oriented than users oriented, so simply mention it in the feature gate should be fine. In future, when the design doc is migrated from Google doc to the kubernetes/community repo, we can add links to it for users who want to dig deeper. Closes: #9108 Xref: kubernetes/kubernetes#63328, kubernetes/kubernetes#64605 * Copyedit * Amend dynamic volume list docs (#9181) The dynamic volume list feature has been documented but the feature gate related was not there yet. Closes: #9105 * Document for service account projection (#9182) This adds docs for the service account projection feature. Xref: kubernetes/kubernetes#63819, kubernetes/community#1973 Closes: #9102 * Update pod priority and preemption user docs (#9172) * Update pod priority and preemption user docs * Copyedit * Documentation on setting node name with Kubeadm (#8925) * Documentation on setting node name with Kubeadm * copyedit * Add kubeadm upgrade docs for 1.11 (#9089) * Add kubeadm upgrade docs for 1.11 * Initial docs review feedback * Add 1-11 to outline * Fix formatting on tab blocks * Move file to correct location * Add `kubeadm upgrade node config` step * Overzealous ediffing * copyedit, fix lists and headings * clarify --force flag for fixing bad state * Get TOML ready for 1.11 release * Blog post for 1.11 release (#9254) * Blog post for 1.11 release * Update 2018-06-26-kubernetes-1.11-release-announcement.md * Update 2018-06-26-kubernetes-1.11-release-announcement.md * Update 2018-06-26-kubernetes-1.11-release-announcement.md
2018-06-27 17:13:46 -07:00 · 2018-06-27 15:26:18 -07:00 · 2018-06-27 11:24:19 -07:00 · 2018-06-26 16:22:52 -07:00 · 2018-06-26 16:19:53 -07:00 · 2018-06-26 16:18:53 -07:00
5829 changed files with 400725 additions and 867745 deletions
@@ -14,7 +14,7 @@


 **Page to Update:**
-http://kubernetes.io/...
+https://kubernetes.io/...

 <!--Optional Information (remove the comment tags around information you would like to include)-->
 <!--Kubernetes Version:-->
@@ -1,11 +1,8 @@
-> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-> For 1.9 Features: set Milestone to `1.9` and Base Branch to `release-1.9`
-> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-> NOTE: Please check the “Allow edits from maintainers” box (see image below) to
-> [allow reviewers to fix problems](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) on your patch and speed up the review process.
+>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+> For 1.11 Features: set Milestone to 1.11 and Base Branch to release-1.11
+>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+> NOTE: After opening the PR, please *un-check and re-check* the ["Allow edits from maintainers"](https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) box so that maintainers can work on your patch and speed up the review process. This is a temporary workaround to address a known issue with GitHub.> 
 >
 > Please delete this note before submitting the pull request.
->
-> NOTE: After opening the PR, please *un-check and re-check* the "Allow edits from maintainers" box. This is a temporary workaround to address a known issue with GitHub.

 ![Allow edits from maintainers checkbox](https://help.github.com/assets/images/help/pull_requests/allow-maintainers-to-make-edits-sidebar-checkbox.png)
@@ -1,11 +1,11 @@
 **/.DS_Store
 **/desktop.ini
-.jekyll-metadata
 _site/**
 .sass-cache/**
 CNAME
 .travis.yml
 .idea/
+.vscode/

 # Vim ignore
 # source: https://github.com/github/gitignore/blob/master/Global/Vim.gitignore
@@ -24,3 +24,8 @@ Session.vim
 tags

 kubernetes.github.io.iml
+
+nohup.out
+
+# Hugo output
+public/
@@ -1,20 +1,22 @@
 language: go
 go:
-  - 1.8.3
+  - 1.9.3

 # Don't want default ./... here:
 install:
 - export PATH=$GOPATH/bin:$PATH
 - mkdir -p $HOME/gopath/src/k8s.io
- mv $TRAVIS_BUILD_DIR $HOME/gopath/src/k8s.io/website
-
-# (1) Fetch dependencies for us to run the tests in test/examples_test.go
+- mv $TRAVIS_BUILD_DIR $HOME/gopath/src/k8s.io/website && cd $HOME/gopath/src/k8s.io/website
+# Fetch dependencies for us to run the tests in test/examples_test.go
 - go get -t -v k8s.io/website/test
+# Make sure we are testing against the correct branch
+- pushd $GOPATH/src/k8s.io/kubernetes && git checkout release-1.10 && popd

 # Simplified deduplication of dependencies.
 - cp -L -R $GOPATH/src/k8s.io/kubernetes/vendor/ $GOPATH/src/
 - rm -r $GOPATH/src/k8s.io/kubernetes/vendor/

 script:
- go test -v k8s.io/website/test
- ./verify-docs-format.sh
+# TODO(bep)
+- go test -v k8s.io/website/test #fixed by https://github.com/kubernetes/website/pull/8388
+#- ./verify-docs-format.sh
@@ -1,11 +0,0 @@
---
-layout: docwithnav
-title: 404 Error!
-permalink: /404.html
-no_canonical: true
-sitemap: false
---
-
-<script src="/js/redirects.js"></script>
-
-Sorry, this page was not found. :(
@@ -0,0 +1,30 @@
+# Credit to Julien Guyomard (https://github.com/jguyomard). This Dockerfile
+# is essentially based on his Dockerfile at
+# https://github.com/jguyomard/docker-hugo/blob/master/Dockerfile. The only significant
+# change is that the Hugo version is now an overridable argument rather than a fixed
+# environment variable.
+
+FROM alpine:latest
+
+MAINTAINER Luc Perkins <lperkins@linuxfoundation.org>
+
+RUN apk add --no-cache \
+    curl \
+    git \
+    openssh-client \
+    rsync
+
+ARG HUGO_VERSION
+
+RUN mkdir -p /usr/local/src && \
+    cd /usr/local/src && \
+    curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_${HUGO_VERSION}_linux-64bit.tar.gz | tar -xz && \
+    mv hugo /usr/local/bin/hugo && \
+    curl -L https://bin.equinox.io/c/dhgbqpS8Bvy/minify-stable-linux-amd64.tgz | tar -xz && \
+    mv minify /usr/local/bin && \
+    addgroup -Sg 1000 hugo && \
+    adduser -Sg hugo -u 1000 -h /src hugo
+
+WORKDIR /src
+
+EXPOSE 1313
@@ -1,53 +0,0 @@
-source "https://rubygems.org"
-
-# gem "github-pages", group: :jekyll_plugins
-
-gem "jekyll", "3.6.0"
-
-group :github_pages_compatible do
-    gem "json", "~> 1.7", ">= 1.7.7"
-    gem "coffee-script", "~> 2.4"
-    gem "coffee-script-source", "~> 1.12"
-    gem "ethon", "~> 0.10"
-    gem "execjs", "~> 2.7"
-    gem "minima", "~> 2.0"
-    gem "terminal-table", "~> 1.4"
-    gem "unicode-display_width", "~> 1.1"
-end
-
-group :jekyll_plugins do
-   gem "jekyll-feed", "~> 0.6"
-   gem "jekyll-sitemap"
-   gem "jekyll-gist"
-   gem "jekyll-paginate", "1.1.0"
-   gem "jekyll-seo-tag"
-   gem "jekyll-avatar", "~> 0.4"
-   gem "jekyll-coffeescript", "~> 1.0"
-   gem "jekyll-default-layout", "~> 0.1"
-   gem "jekyll-github-metadata", "~> 2.2"
-   gem "jekyll-optional-front-matter", "~> 0.1"
-   gem "jekyll-readme-index", "0.0.3"
-   gem "jekyll-redirect-from", "~> 0.11"
-   gem "jekyll-relative-links", "~> 0.2"
-   gem "jekyll-swiss", "~> 0.4"
-   gem "jekyll-theme-architect", "0.0.3"
-   gem "jekyll-theme-cayman", "0.0.3"
-   gem "jekyll-theme-dinky", "0.0.3"
-   gem "jekyll-theme-hacker", "0.0.3"
-   gem "jekyll-theme-leap-day", "0.0.3"
-   gem "jekyll-theme-merlot", "0.0.3"
-   gem "jekyll-theme-midnight", "0.0.3"
-   gem "jekyll-theme-minimal", "0.0.3"
-   gem "jekyll-theme-modernist", "0.0.3"
-   gem "jekyll-theme-primer", "~> 0.1"
-   gem "jekyll-theme-slate", "0.0.3"
-   gem "jekyll-theme-tactile", "0.0.3"
-   gem "jekyll-theme-time-machine", "0.0.3"
-   gem "jekyll-titles-from-headings", "~> 0.1"
-end
-
-gem "jekyll-include-cache", "~> 0.1"
-
-gem "kramdown", "~> 1.11"
-gem "rouge", "~> 2.0"
-gem "pry"
@@ -1,176 +0,0 @@
-GEM
-  remote: https://rubygems.org/
-  specs:
-    addressable (2.5.2)
-      public_suffix (>= 2.0.2, < 4.0)
-    coderay (1.1.2)
-    coffee-script (2.4.1)
-      coffee-script-source
-      execjs
-    coffee-script-source (1.12.2)
-    colorator (1.1.0)
-    ethon (0.11.0)
-      ffi (>= 1.3.0)
-    execjs (2.7.0)
-    faraday (0.13.1)
-      multipart-post (>= 1.2, < 3)
-    ffi (1.9.18)
-    forwardable-extended (2.6.0)
-    jekyll (3.6.0)
-      addressable (~> 2.4)
-      colorator (~> 1.0)
-      jekyll-sass-converter (~> 1.0)
-      jekyll-watch (~> 1.1)
-      kramdown (~> 1.14)
-      liquid (~> 4.0)
-      mercenary (~> 0.3.3)
-      pathutil (~> 0.9)
-      rouge (>= 1.7, < 3)
-      safe_yaml (~> 1.0)
-    jekyll-avatar (0.5.0)
-      jekyll (~> 3.0)
-    jekyll-coffeescript (1.0.1)
-      coffee-script (~> 2.2)
-    jekyll-default-layout (0.1.4)
-      jekyll (~> 3.0)
-    jekyll-feed (0.9.2)
-      jekyll (~> 3.3)
-    jekyll-gist (1.4.1)
-      octokit (~> 4.2)
-    jekyll-github-metadata (2.9.3)
-      jekyll (~> 3.1)
-      octokit (~> 4.0, != 4.4.0)
-    jekyll-include-cache (0.1.0)
-      jekyll (~> 3.3)
-    jekyll-optional-front-matter (0.3.0)
-      jekyll (~> 3.0)
-    jekyll-paginate (1.1.0)
-    jekyll-readme-index (0.0.3)
-      jekyll (~> 3.0)
-    jekyll-redirect-from (0.12.1)
-      jekyll (~> 3.3)
-    jekyll-relative-links (0.5.1)
-      jekyll (~> 3.3)
-    jekyll-sass-converter (1.5.0)
-      sass (~> 3.4)
-    jekyll-seo-tag (2.3.0)
-      jekyll (~> 3.3)
-    jekyll-sitemap (1.1.1)
-      jekyll (~> 3.3)
-    jekyll-swiss (0.4.0)
-    jekyll-theme-architect (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-cayman (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-dinky (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-hacker (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-leap-day (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-merlot (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-midnight (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-minimal (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-modernist (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-primer (0.5.2)
-      jekyll (~> 3.5)
-      jekyll-github-metadata (~> 2.9)
-      jekyll-seo-tag (~> 2.2)
-    jekyll-theme-slate (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-tactile (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-time-machine (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-titles-from-headings (0.5.0)
-      jekyll (~> 3.3)
-    jekyll-watch (1.5.0)
-      listen (~> 3.0, < 3.1)
-    json (1.8.6)
-    kramdown (1.15.0)
-    liquid (4.0.0)
-    listen (3.0.8)
-      rb-fsevent (~> 0.9, >= 0.9.4)
-      rb-inotify (~> 0.9, >= 0.9.7)
-    mercenary (0.3.6)
-    method_source (0.9.0)
-    minima (2.1.1)
-      jekyll (~> 3.3)
-    multipart-post (2.0.0)
-    octokit (4.7.0)
-      sawyer (~> 0.8.0, >= 0.5.3)
-    pathutil (0.16.0)
-      forwardable-extended (~> 2.6)
-    pry (0.11.2)
-      coderay (~> 1.1.0)
-      method_source (~> 0.9.0)
-    public_suffix (3.0.0)
-    rb-fsevent (0.10.2)
-    rb-inotify (0.9.10)
-      ffi (>= 0.5.0, < 2)
-    rouge (2.2.1)
-    safe_yaml (1.0.4)
-    sass (3.5.3)
-      sass-listen (~> 4.0.0)
-    sass-listen (4.0.0)
-      rb-fsevent (~> 0.9, >= 0.9.4)
-      rb-inotify (~> 0.9, >= 0.9.7)
-    sawyer (0.8.1)
-      addressable (>= 2.3.5, < 2.6)
-      faraday (~> 0.8, < 1.0)
-    terminal-table (1.8.0)
-      unicode-display_width (~> 1.1, >= 1.1.1)
-    unicode-display_width (1.3.0)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  coffee-script (~> 2.4)
-  coffee-script-source (~> 1.12)
-  ethon (~> 0.10)
-  execjs (~> 2.7)
-  jekyll (= 3.6.0)
-  jekyll-avatar (~> 0.4)
-  jekyll-coffeescript (~> 1.0)
-  jekyll-default-layout (~> 0.1)
-  jekyll-feed (~> 0.6)
-  jekyll-gist
-  jekyll-github-metadata (~> 2.2)
-  jekyll-include-cache (~> 0.1)
-  jekyll-optional-front-matter (~> 0.1)
-  jekyll-paginate (= 1.1.0)
-  jekyll-readme-index (= 0.0.3)
-  jekyll-redirect-from (~> 0.11)
-  jekyll-relative-links (~> 0.2)
-  jekyll-seo-tag
-  jekyll-sitemap
-  jekyll-swiss (~> 0.4)
-  jekyll-theme-architect (= 0.0.3)
-  jekyll-theme-cayman (= 0.0.3)
-  jekyll-theme-dinky (= 0.0.3)
-  jekyll-theme-hacker (= 0.0.3)
-  jekyll-theme-leap-day (= 0.0.3)
-  jekyll-theme-merlot (= 0.0.3)
-  jekyll-theme-midnight (= 0.0.3)
-  jekyll-theme-minimal (= 0.0.3)
-  jekyll-theme-modernist (= 0.0.3)
-  jekyll-theme-primer (~> 0.1)
-  jekyll-theme-slate (= 0.0.3)
-  jekyll-theme-tactile (= 0.0.3)
-  jekyll-theme-time-machine (= 0.0.3)
-  jekyll-titles-from-headings (~> 0.1)
-  json (~> 1.7, >= 1.7.7)
-  kramdown (~> 1.11)
-  minima (~> 2.0)
-  pry
-  rouge (~> 2.0)
-  terminal-table (~> 1.4)
-  unicode-display_width (~> 1.1)
-
-BUNDLED WITH
-   1.15.4
@@ -1,18 +1,33 @@
-.PHONY: all build build-preview help serve
+DOCKER       = docker
+HUGO_VERSION = 0.40.3
+DOCKER_IMAGE = kubernetes-hugo
+DOCKER_RUN   = $(DOCKER) run --rm --interactive --tty --volume $(PWD):/src
+
+.PHONY: all build sass build-preview help serve

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

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

+sass: # Rebuild the SASS source into CSS
+	node-sass --output-style compact ./src/sass/styles.sass ./static/css/styles.css
+	node-sass --output-style compact ./src/sass/case_study_styles.sass ./static/css/case_study_styles.css
+
 build: ## Build site with production settings and put deliverables in _site.
-	bundle exec jekyll build
+	hugo

 build-preview: ## Build site with drafts and future posts enabled.
-	bundle exec jekyll build --drafts --future
+	hugo -D -F

 serve: ## Boot the development server.
-	bundle exec jekyll serve
+	hugo server

-stage: ## Run the Jekyll staging container.
-	docker run -ti --rm -v "${PWD}":/k8sdocs -p 4000:4000 gcr.io/google-samples/k8sdocs:1.1
+docker-image:
+	$(DOCKER) build . --tag $(DOCKER_IMAGE) --build-arg HUGO_VERSION=$(HUGO_VERSION)
+
+docker-build:
+	$(DOCKER_RUN) $(DOCKER_IMAGE) hugo
+
+stage:
+	$(DOCKER_RUN) -p 1313:1313 $(DOCKER_IMAGE) hugo server --watch --bind 0.0.0.0
@@ -1,6 +1,19 @@
+# Reviewers can /lgtm /approve but not sufficient for auto-merge without an
+# approver
 reviewers:
- a-mccarthy
- abiogenesis-now
+- zhangxiaoyu-zidif
+- xiangpengzhao
+- stewart-yu
+- Rajakavitha1 
+# Approvers have all the ability of reviewers but their /approve makes
+# auto-merge happen if a /lgtm exists, or vice versa, or they can do both
+# No need for approvers to also be listed as reviewers
+approvers:
+- heckj
 - bradamant3
+- bradtopol
 - steveperry-53
 - zacharysarah
+- chenopis
+- mistyhacks
+- tengqm
@@ -0,0 +1,199 @@
+aliases:
+  sig-api-machinery: #Team: API Server; GH: sig-api-machinery-pr-reviews; e.g. Annotations, Labels
+    - lavalamp
+    - sttts
+    - liggitt
+    - smarterclayton
+    - deads2k
+  sig-apps: #Team: Workloads; GH: sig-apps-pr-reviews; e.g. ConfigMaps, CronJobs, CustomResourceDefinitions, DaemonSets, Deployments, Jobs, Secrets, StatefulSets
+    - enisoc
+    - erictune
+    - foxish
+    - janetkuo
+    - kow3ns
+    - lukaszo
+    - mfojtik
+    - smarterclayton
+    - soltysh
+    - tnozicka
+  sig-architecture: #GH: sig-architecture-pr-reviews
+    - smarterclayton
+    - bgrant0607
+  sig-auth: #GH: sig-auth-pr-reviews
+    - php-coder
+    - liggitt
+    - mikedanese
+    - ericchiang
+    - mattmoyer
+    - enj
+    - deads2k
+    - davidopp
+  sig-autoscaling: #GH: sig-autoscaling-pr-reviews
+    - DirectXMan12
+    - bskiba
+    - aleksandra-malinowska
+    - MaciekPytel
+    - davidopp
+    - mwielgus
+  sig-aws: #Amazon AWS
+    - justinsb
+    - kris-nova
+    - chrislovecnm
+    - mfburnett
+  sig-azure: #Microsoft Azure
+    - slack
+    - colemickens
+    - jdumars
+  sig-big-data: #GH: sig-big-data-pr-reviews
+    - foxish
+  sig-cli: #Team: CLI; GH: sig-cli-pr-reviews; e.g. kubectl
+    - adohe
+    - deads2k
+    - derekwaynecarr
+    - dims
+    - dshulyak
+    - eparis
+    - ericchiang
+    - ghodss
+    - mengqiy
+    - rootfs
+    - shiywang
+    - smarterclayton
+    - soltysh
+    - sttts
+  sig-cluster-lifecycle: #GH: sig-cluster-lifecycle-pr-reviews
+    - timothysc
+    - luxas
+    - roberthbailey
+    - fabriziopandini 
+  sig-cluster-ops:
+    - zehicle
+    - jdumars
+  sig-contribex: #aka Contributor Experience; GH: sig-contributor-experience-pr-reviews
+    - rmmh
+    - cblecker
+    - apelisse
+    - grodrigues3
+    - spxtr
+  sig-contributor-experience: #GH: sig-contributor-experience-pr-reviews
+    - rmmh
+    - cblecker
+    - apelisse
+    - grodrigues3
+    - spxtr
+  sig-docs: #Team: documentation; GH: sig-docs-pr-reviews
+    - bradamant3
+    - steveperry-53
+    - zacharysarah
+    - bradtopol
+    - heckj
+  sig-federation: #Team: Federation; e.g. Federated Clusters
+    - csbell
+  sig-gcp: #Google Cloud Platform; GH: sig-gcp-pr-reviews
+    - abgworrall
+  sig-instrumentation: #GH: sig-instrumentation-pr-reviews; e.g. metrics, logging, events
+    - DirectXMan12
+    - x13n
+    - kawych
+    - brancz
+    - fabxc
+    - loburm
+    - piosz
+    - fgrzadkowski
+  sig-multicluster: #GH: sig-multicluster-pr-reviews; e.g. resiliency against availability zone outages; hybrid clouds; spanning multiple cloud providers; migration to public clouds
+    - madhusudancs
+    - marun
+    - jianhuiz
+    - shashidharatd
+    - nikhiljindal
+    - quinton-hoole
+    - mwielgus
+    - csbell
+  sig-network: #Team: Network; GH: sig-network-pr-reviews; e.g. Ingress, Network Policies, Services
+    - bowei
+    - caseydavenport
+    - danwinship
+    - dcbw
+    - dnardo
+    - freehan
+    - mrhohn
+    - nicksardo
+    - thockin
+  sig-node: #Team: Node; GH: sig-node-pr-reviews; e.g. Containers, Docker, Images, OS images, Pods, Registries
+    - Random-Liu
+    - dashpole
+    - dchen1107
+    - derekwaynecarr
+    - dims
+    - feiskyer
+    - mtaufen
+    - ncdc
+    - pmorie
+    - resouer
+    - sjpotter
+    - tallclair
+    - tmrts
+    - vishh
+    - yifan-gu
+    - yujuhong
+  sig-onprem: #On-premises; GH: sig-onprem-pr-reviews
+    - zen
+    - idvoretskyi
+    - pigmej
+    - feiskyer
+    - nebril
+  sig-openstack: #GH: sig-openstack-pr-reviews
+    - hogepodge
+    - dklyle
+    - rjmorse
+  sig-pm: #aka Product Management
+    - apsinha
+    - idvoretskyi
+    - calebamiles
+  sig-product-management:
+    - apsinha
+    - idvoretskyi
+    - calebamiles
+  sig-release: #GH: sig-release-pr-reviews
+    - calebamiles
+    - enisoc
+    - pwittrock
+  sig-rktnetes:
+    - calebamiles
+  sig-scalability: #GH: sig-scalability-pr-reviews
+    - jbeda
+    - spiffxp
+    - lavalamp
+    - countspongebob
+  sig-scheduling: #Team: Sharing; GH: sig-scheduling-pr-reviews; e.g. Scheduler
+    - bsalamat
+    - davidopp
+    - jayunit100
+    - k82cn
+    - resouer
+    - timothysc
+    - wojtek-t
+  sig-service-catalog: #GH: sig-service-catalog-pr-reviews; e.g. Service Broker
+    - pmorie
+    - jessfraz
+    - pwittrock
+    - droot
+    - seans3
+  sig-storage: #Team: Storage; GH: sig-storage-pr-reviews; e.g. Volumes
+    - childsb
+    - jsafrane
+    - rootfs
+    - saad-ali
+    - matchstick
+    - msau42
+  sig-testing: #GH: sig-testing-pr-reviews
+    - fejta
+    - ixdy
+    - rmmh
+    - spiffxp
+    - spxtr
+  sig-ui: #User Interface
+    - danielromlein
+    - floreks
+  sig-windows:
+    - michmike
@@ -16,7 +16,38 @@ For more information about contributing to the Kubernetes documentation, see:
 * [Using Page Templates](http://kubernetes.io/docs/home/contribute/page-templates/)
 * [Documentation Style Guide](http://kubernetes.io/docs/home/contribute/style-guide/)

+## Building the site using Docker
+
+If you'd like, you can build the Kubernetes docs using Docker. To get started, build the image locally:
+
+```bash
+$ make docker-image
+
+# The underlying command:
+$ docker build . \
+  --tag kubernetes-hugo \
+  --build-arg HUGO_VERSION=0.40.3
+```
+
+You can create an image for a different version of Hugo by changing the value of the `HUGO_VERSION` argument for the build. You *must* specify a version or the image will not build.
+Once the `kubernetes-hugo` image has been built locally, you can build the site:
+
+```bash
+$ make docker-serve
+
+# The underlying command:
+$ docker run \
+  --rm \
+  --interactive \
+  --tty \
+  --volume $(PWD):/src \
+  kubernetes-hugo:latest \
+  hugo
+```
+
+As when building without using a Docker container, the results of the build will be published to the `public` directory (the default output directory for [Hugo](https://gohugo.io), the static site generator used to build this site).
+
 ## Thank you!

 Kubernetes thrives on community participation, and we really appreciate your
-contributions to our site and our documentation!
+contributions to our site and our documentation!
@@ -0,0 +1,15 @@
+# Defined below are the security contacts for this repo.
+#
+# They are the contact point for the Product Security Team to reach out
+# to for triaging and handling of incoming issues.
+#
+# The below names agree to abide by the
+# [Embargo Policy](https://github.com/kubernetes/sig-release/blob/master/security-release-process-documentation/security-release-process.md#embargo-policy)
+# and will be removed and replaced if they violate that agreement.
+#
+# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE
+# INSTRUCTIONS AT https://kubernetes.io/security/
+
+chenopis
+jaredbhatti
+zacharysarah
@@ -1,90 +0,0 @@
-name: Kubernetes
-title: Kubernetes
-url: https://kubernetes.io
-description: Production-Grade Container Orchestration
-markdown: kramdown
-kramdown:
-  input: GFM
-  html_to_native: true
-  hard_wrap: false
-  syntax_highlighter: rouge
-incremental: true
-
-safe: false
-lsi: false
-
-defaults:
-  -
-    scope:
-      path: ""
-    values:
-      fullversion: "v1.8.0"
-      version: "v1.8"
-      githubbranch: "master"
-      docsbranch: "master"
-      versions:
-        - fullversion: "v1.8.0"
-          version: "v1.8"
-          githubbranch: "v1.8.0"
-          docsbranch: "release-1.8"
-          url: https://kubernetes.io/docs/home/
-        - fullversion: "v1.7.6"
-          version: "v1.7"
-          githubbranch: "v1.7.6"
-          docsbranch: "release-1.7"
-          url: https://v1-7.docs.kubernetes.io/docs/home/
-        - fullversion: "v1.6.8"
-          version: "v1.6"
-          githubbranch: "v1.6.8"
-          docsbranch: "release-1.6"
-          url: https://v1-6.docs.kubernetes.io/docs/home/
-        - fullversion: "v1.5.7"
-          version: "v1.5"
-          githubbranch: "v1.5.7"
-          docsbranch: "release-1.5"
-          url: https://v1-5.docs.kubernetes.io/docs/
-        - fullversion: "v1.4.12"
-          version: "v1.4"
-          githubbranch: "v1.4.12"
-          docsbranch: "release-1.4"
-          url: https://v1-4.docs.kubernetes.io/docs/
-      deprecated: false
-      currentUrl: https://kubernetes.io/docs/home/
-      nextUrl: http://kubernetes-io-vnext-staging.netlify.com/
-  -
-    scope:
-      path: "docs"
-    values:
-      layout: docwithnav
-      showedit: true
-
-permalink: pretty
-
-plugins:
-  - jekyll-feed
-  - jekyll-sitemap
-  - jekyll-seo-tag
-  - jekyll-include-cache
-# disabled gems
-#  - jekyll-redirect-from
-
-include: [_redirects,_headers]
-
-# SEO
-logo: /images/favicon.png
-twitter:
-  username: kubernetesio
-
-# empty array for tabs
-emptyArray: []
-
-# Tables of contents, stored in the _data folder, that control the sidebar nav
-tocs:
-  - docs-home
-  - setup
-  - tasks
-  - tutorials
-  - concepts
-  - reference
-  - samples
-  - search
@@ -1,22 +0,0 @@
-bigheader: "Documentation Home"
-abstract: "Documentation for using and learning about Kubernetes."
-toc:
- docs/home/index.md
-
- title: Release Notes
-  path: https://git.k8s.io/kubernetes/CHANGELOG.md
- title: Release Roadmap
-  path: https://github.com/kubernetes/kubernetes/milestones/
-
- docs/tasks/debug-application-cluster/troubleshooting.md
-
- title: Contributing to the Kubernetes Docs
-  section:
-  - editdocs.md
-  - docs/home/contribute/create-pull-request.md
-  - docs/home/contribute/write-new-topic.md
-  - docs/home/contribute/stage-documentation-changes.md
-  - docs/home/contribute/page-templates.md
-  - docs/home/contribute/review-issues.md
-  - docs/home/contribute/style-guide.md
-  - docs/home/contribute/includes.md
@@ -1,27 +0,0 @@
-id: _example
-name: Example K8s Term
-full-link: kubernetes.io/docs/link-to-long-dedicated-docs-page
-aka:
- Slang K8s Term
- Misnomer
- Formerly Known as Prince
-related:
- id-of-less-fancy-k8s-term
- id-of-tangential-term
- id-of-commonly-used-with-term
-tags:
- Some Tag
-short-description: >
-  Required.
-  Markdown allowed (e.g. for cross-linking).
-  One or two lines that provide a minimum definition.
-  Do not repeat the term.
-  Prefer fragments.
-  End with a period.
-long-description: >
-  Optional.
-  Markdown allowed.
-  Longer additional text to appear after (in conjunction with) short description.
-  Provide where the short description is not sufficient as the intro paragraph to a topic.
-  Write complete but concise sentences.
-  **See /_includes/templates/glossary/README.md for the official style guide.**
@@ -1,9 +0,0 @@
-id: annotation
-name: Annotation
-full-link: docs/concepts/overview/working-with-objects/annotations
-tags:
- fundamental
-short-description: >
-  A key-value pair that is used to attach arbitrary non-identifying metadata to objects.
-long-description: >
-  The metadata in an annotation can be small or large, structured or unstructured, and can include characters not permitted by labels. Clients such as tools and libraries can retrieve this metadata.
@@ -1,11 +0,0 @@
-id: application-architect
-name: Application Architect
-related:
-  - application-developer
-tags:
-  - user-type
-short-description: >
-  A person responsible for the high-level design of an application.
-long-description: >
-  An architect ensures that an app's implementation allows it to interact with its surrounding components in a scalable, maintainable way.
-  Surrounding components include databases, logging infrastructure, and other microservices.
@@ -1,11 +0,0 @@
-id: application-developer
-name: Application Developer
-related:
-  - application-architect
-tags:
-  - user-type
-short-description: >
-  A person who writes an application that runs in a Kubernetes cluster.
-long-description: >
-  An application developer focuses on one part of an application.
-  The scale of their focus may vary significantly in size.
@@ -1,10 +0,0 @@
-id: approver
-name: Approver
-tags:
- community
-short-description: >
-  A person who can review and approve Kubernetes code contributions.
-long-description: >
-  While code review is focused on code quality and correctness, approval is focused on the holistic acceptance of a contribution.
-  Holistic acceptance includes backwards/forwards compatibility, adhering to API and flag conventions, subtle performance and correctness issues, interactions with other parts of the system, and others.
-  Approver status is scoped to a part of the codebase.
@@ -1,9 +0,0 @@
-id: cla
-name: CLA (Contributor License Agreement)
-full-link: https://github.com/kubernetes/community/blob/master/CLA.md
-tags:
- community
-short-description: >
-  Terms under which a {% glossary_tooltip text="contributor" term_id="contributor" %} grants a license to an open source project for their contributions.
-long-description: >
-  CLAs help resolve legal disputes involving contributed material and intellectual property (IP).
@@ -1,11 +0,0 @@
-id: cluster-architect
-name: Cluster Architect
-related:
-  - cluster
-  - cluster-operator
-tags:
-  - user-type
-short-description: >
-  A person who designs infrastructure that involves one or more Kubernetes clusters.
-long-description: >
-  Cluster architects are concerned with best practices for distributed systems, for example&#58; high availability and security.
@@ -1,15 +0,0 @@
-id: cluster-operator
-name: Cluster Operator
-aka:
-  - Cluster Administrator
-related:
-  - cluster
-  - cluster-architect
-tags:
-  - user-type
-short-description: >
-  A person who configures, controls, and monitors clusters.
-long-description: |
-  Their primary responsibility is keeping a cluster up and running, which may involve periodic maintenance activities or upgrades.<br>
-
-  **NOTE:** Cluster operators are different from the [Operator pattern](https://coreos.com/operators) that extends the Kubernetes API.
@@ -1,9 +0,0 @@
-id: cluster
-name: Cluster
-tags:
- fundamental
- operation
-short-description: >
-  A set of machines, called nodes, that run containerized applications managed by Kubernetes.
-long-description: >
-  A cluster has several worker nodes and at least one master node.
@@ -1,11 +0,0 @@
-id: code-contributor
-name: Code Contributor
-aka:
-  - Community Developer
-tags:
- community
- user-type
-short-description: >
-  A person who develops and contributes code to the Kubernetes open source codebase.
-long-description: >
-  They are also an active {% glossary_tooltip text="community member" term_id="member" %} who participates in one or more {% glossary_tooltip text="Special Interest Groups (SIGs)" term_id="sig" %}.
@@ -1,13 +0,0 @@
-id: configmap
-name: ConfigMap
-full-link: /docs/tasks/configure-pod-container/configmap/
-related:
- pod
- secret
-tags:
- core-object
-short-description: >
-  An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or config files in a {% glossary_tooltip text="volume" term_id="volume" %}.
-long-description: >
-  Allows you to decouple environment-specific configuration from your {% glossary_tooltip text="container images" term_id="container" %}, so that your applications are easily portable.
-  When storing confidential data use a [Secret](https://kubernetes.io/docs/concepts/configuration/secret/).
@@ -1,10 +0,0 @@
-id: container
-name: Container
-full-link: /docs/concepts/overview/what-is-kubernetes/#why-containers
-tags:
- fundamental
- workload
-short-description: >
-  A lightweight and portable executable image that contains software and all of its dependencies.
-long-description: >
-  Containers decouple applications from underlying host infrastructure to make deployment easier in different cloud or OS environments, and for easier scaling.
@@ -1,8 +0,0 @@
-id: contributor
-name: Contributor
-tags:
- community
-short-description: >
-  Someone who donates code, documentation, or their time to help the Kubernetes project or community.
-long-description: >
-  Contributions include pull requests (PRs), issues, feedback, {% glossary_tooltip text="special interest groups (SIG)" term_id="sig" %} participation, or organizing community events.
@@ -1,10 +0,0 @@
-id: cronjob
-name: CronJob
-full-link: /docs/concepts/workloads/controllers/cron-jobs/
-tags:
- core-object
- workload
-short-description: >
-  Manages a [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/) that runs on a periodic schedule.
-long-description: >
-  Similar to a line in a *crontab* file, a Cronjob object specifies a schedule using the [Cron](https://en.wikipedia.org/wiki/Cron) format.
@@ -1,10 +0,0 @@
-id: daemonset
-name: DaemonSet
-full-link: /docs/concepts/workloads/controllers/daemonset
-tags:
- fundamental
- workload
-short-description: >
-  Ensures a copy of a {% glossary_tooltip term_id="pod" %} is running across a set of nodes in a {% glossary_tooltip term_id="cluster" %}.
-long-description: >
-  Used to deploy system daemons such as log collectors and monitoring agents that typically must run on every {% glossary_tooltip term_id="node" %}.
@@ -1,11 +0,0 @@
-id: deployment
-name: Deployment
-full-link: /docs/concepts/workloads/controllers/deployment/
-tags:
- fundamental
- core-object
- workload
-short-description: >
-  An API object that manages a replicated application.
-long-description: >
-  Each replica is represented by a {% glossary_tooltip term_id="pod" %}, and the Pods are distributed among the nodes of a cluster.
@@ -1,11 +0,0 @@
-id: developer
-name: Developer (disambiguation)
-aka:
-  - Kubernetes Developer
-tags:
- community
- user-type
-short-description: >
-  May refer to&#58; {% glossary_tooltip text="Application Developer" term_id="application-developer" %}, {% glossary_tooltip text="Code Contributor" term_id="code-contributor" %}, or {% glossary_tooltip text="Platform Developer" term_id="platform-developer" %}.
-long-description: >
-  This overloaded term may have different meanings depending on the context
@@ -1,11 +0,0 @@
-id: downstream
-name: Downstream (disambiguation)
-related:
- upstream
-tags:
- community
-short-description: >
-  May refer to: code in the Kubernetes ecosystem that depends upon the core Kubernetes codebase or a forked repo.
-long-description: |
-  * In the **Kubernetes Community**: Conversations often use *downstream* to mean the ecosystem, code, or third-party tools that rely on the core Kubernetes codebase. For example, a new feature in Kubernetes may be adopted by applications *downstream* to improve their functionality.
-  * In **GitHub** or **git**: The convention is to refer to a forked repo as *downstream*, whereas the source repo is considered *upstream*.
@@ -1,10 +0,0 @@
-id: helm-chart
-name: Helm Chart
-full-link: https://github.com/kubernetes/helm/blob/master/docs/charts.md
-tags:
- tool
-short-description: >
-  A package of pre-configured Kubernetes resources that can be managed with the Helm tool.
-long-description: |
-  Charts provide a reproducible way of creating and sharing Kubernetes applications.
-  A single chart can be used to deploy something simple, like a memcached Pod, or something complex, like a full web app stack with HTTP servers, databases, caches, and so on.
@@ -1,15 +0,0 @@
-id: horizontal-pod-autoscaler
-name: Horizontal Pod Autoscaler
-full-link: /docs/tasks/run-application/horizontal-pod-autoscale/
-aka:
- HPA
-related:
- pod
-tags:
- operation
-short-description: >
-  An API resource that automatically scales the number of pod replicas based on targeted CPU
-  utilization or custom metric targets.
-long-description: >
-  HPA is typically used with replication controllers, deployments or replica sets and cannot be
-  applied to objects that cannot be scaled, for example DaemonSets.  
@@ -1,9 +0,0 @@
-id: image
-name: Image
-tags:
- fundamental
-short-description: >
-  Stored instance of a container that holds a set of software needed to run an application.
-long-description: >
-  A way of packaging software that allows it to be stored in a container registry, pulled to a local system, and run as an application. Meta data is included in the image that can indicate what executable to run, who built it, and other information.
-
@@ -1,13 +0,0 @@
-id: ingress
-name: Ingress
-full-link: /docs/concepts/services-networking/ingress/
-aka:
-  - Ingress controller
-tags:
- networking
- architecture
- extension
-short-description: >
-  An API object that manages external access to the services in a cluster, typically HTTP.
-long-description: >
-  Ingress can provide load balancing, SSL termination and name-based virtual hosting.
@@ -1,13 +0,0 @@
-id: istio
-name: Istio
-full-link: https://istio.io/docs/concepts/what-is-istio/overview.html
-tags:
- networking
- architecture
- extension
-short-description: >
-  An open platform (not Kubernetes-specific) that provides a uniform way to integrate microservices, manage traffic flow, enforce policies, and aggregate telemetry data.
-long-description: >
-  Adding Istio does not require changing application code.
-  It is a layer of infrastructure between a service and the network, which when combined with service deployments, is commonly referred to as a service mesh.
-  Istio's control plane abstracts away the underlying cluster management platform, which may be Kubernetes, Mesosphere, etc.
@@ -1,9 +0,0 @@
-id: job
-name: Job
-full-link: /docs/concepts/workloads/controllers/jobs-run-to-completion
-tags:
- core-object
-short-description: >
-  A finite or batch task that runs to completion.
-long-description: >
-  Creates one or more {% glossary_tooltip term_id="pod" %} objects and ensures that a specified number of them successfully terminate. As Pods successfully complete, the Job tracks the successful completions.
@@ -1,19 +0,0 @@
-id: kops
-name: Kops
-full-link: /docs/getting-started-guides/kops/
-tags:
- tool
- operation
-short-description: >
-  A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters. *NOTE&#58; Officially supports AWS only, with GCE and VMware vSphere in alpha*.
-long-description: |
-  `kops` provisions your cluster with&#58;
-
-    * Fully automated installation
-    * DNS-based cluster identification
-    * Self-healing&#58; everything runs in Auto-Scaling Groups
-    * Limited OS support (Debian preferred, Ubuntu 16.04 supported, early support for CentOS & RHEL)
-    * High availability (HA) support
-    * The ability to directly provision, or generate terraform manifests
-
-  You can also build your own cluster using {% glossary_tooltip term_id="kubeadm" %} as a building block. `kops` builds on the kubeadm work.
@@ -1,10 +0,0 @@
-id: kubeadm
-name: Kubeadm
-full-link: /docs/admin/kubeadm/
-tags:
- tool
- operation
-short-description: >
-  A tool for quickly installing Kubernetes and setting up a secure cluster.
-long-description: >
-  You can use kubeadm to install both the control plane and the worker node components.
@@ -1,10 +0,0 @@
-id: kubectl
-name: Kubectl
-full-link: /docs/user-guide/kubectl-overview/
-tags:
- tool
- fundamental
-short-description: >
-  A command line tool for communicating with a {% glossary_tooltip text="Kubernetes API" term_id="kubernetes-api" %} server.
-long-description: >
-  You can use kubectl to create, inspect, update, and delete Kubernetes objects.
@@ -1,10 +0,0 @@
-id: kubelet
-name: Kubelet
-full-link: docs/reference/generated/kubelet
-tags:
- fundamental
- core-object
-short-description: >
-  An agent that runs on each node in the cluster. It makes sure that containers are running in a pod.
-long-description: >
-  The kubelet takes a set of PodSpecs that are provided through various mechanisms and ensures that the containers described in those PodSpecs are running and healthy. The kubelet doesn’t manage containers which were not created by Kubernetes.
@@ -1,13 +0,0 @@
-id: kubernetes-api
-name: Kubernetes API
-full-link: /docs/concepts/overview/kubernetes-api/
-tags:
- fundamental
- architecture
-short-description: >
-  The application that serves Kubernetes functionality through a RESTful interface and stores the state of the cluster.
-long-description: >
-  Kubernetes resources and "records of intent" are all stored as API objects, and modified via RESTful calls to the API.
-  The API allows configuration to be managed in a declarative way.
-  Users can interact with the Kubernetes API directly, or via tools like `kubectl`.
-  The core Kubernetes API is flexible and can also be extended to support custom resources.
@@ -1,9 +0,0 @@
-id: labels
-name: Labels
-full-link: /docs/concepts/overview/working-with-objects/labels
-tags:
- fundamental
-short-description: >
-  Used to tag objects with identifying attributes that are meaningful and relevant to users.
-long-description: >
-  Labels are key/value pairs that are attached to objects, such as pods. They can be used to organize and to select subsets of objects.
@@ -1,8 +0,0 @@
-id: maintainer
-name: Maintainer
-tags:
- community
-short-description: >
-  A highly experienced {% glossary_tooltip text="contributor" term_id="contributor" %}, active in multiple areas of Kubernetes, who has cross-area ownership and write access to a project's GitHub repository.
-long-description: >
-  Maintainers work holistically across the project to maintain its health and success and have made substantial contributions, both through code development and broader organizational efforts.
@@ -1,9 +0,0 @@
-id: managed-service
-name: Managed Service
-tags:
- extension
-short-description: >
-  A software offering maintained by a third-party provider.
-long-description: >
-  Some examples of Managed Services are AWS EC2, Azure SQL Database, and GCP Pub/Sub, but they can be any software offering that can be used by an application.
-  [Service Catalog](/docs/concepts/service-catalog/) provides a way to list, provision, and bind with Managed Services offered by {% glossary_tooltip text="Service Brokers" term_id="service-broker" %}.
@@ -1,10 +0,0 @@
-id: member
-name: Member
-tags:
- community
-short-description: >
-  A continuously active {% glossary_tooltip text="contributor" term_id="contributor" %} in the K8s community.
-long-description: >
-  Members can have issues and PRs assigned to them and participate in {% glossary_tooltip text="special interest groups (SIGs)" term_id="sig" %} through GitHub teams.
-  Pre-submit tests are automatically run for members' PRs.
-  A member is expected to remain an active contributor to the community.
@@ -1,10 +0,0 @@
-id: minikube
-name: Minikube
-full-link: /docs/getting-started-guides/minikube/
-tags:
- fundamental
- tool
-short-description: >
-  A tool for running Kubernetes locally.
-long-description: >
-  Minikube runs a single-node cluster inside a VM on your computer.
@@ -1,9 +0,0 @@
-id: namespace
-name: Namespace
-full-link: /docs/concepts/overview/working-with-objects/namespaces
-tags:
- fundamental
-short-description: >
-  An abstraction used by Kubernetes to support virtual clusters on the same physical {% glossary_tooltip term_id="cluster" %}.
-long-description: >
-  Namespaces are used to organize objects in a cluster and provide a way to divide cluster resources. Names of resources need to be unique within a namespace, but not across namespaces.
@@ -1,13 +0,0 @@
-id: network-policy
-name: Network Policy
-full-link: /docs/concepts/services-networking/network-policies/
-aka:
-  - NetworkPolicy
-tags:
- networking
- architecture
- extension
-short-description: >
-  A specification of how groups of Pods are allowed to communicate with each other and with other network endpoints.
-long-description: >
-  Network Policies help you declaratively configure which Pods are allowed to connect to each other, which namespaces are allowed to communicate, and more specifically which port numbers to enforce each policy on. `NetworkPolicy` resources use labels to select Pods and define rules which specify what traffic is allowed to the selected Pods. Network Policies are implemented by a supported network plugin provided by a network provider. Be aware that creating a network resource without a controller to implement it will have no effect.
@@ -1,13 +0,0 @@
-id: node
-name: Node
-full-link: /docs/concepts/architecture/nodes/
-aka:
- Minion
-related:
- deployment
-tags:
- fundamental
-short-description: >
-  A node is a worker machine in Kubernetes.
-long-description: >
-  A worker machine may be a VM or physical machine, depending on the cluster. It has the {% glossary_tooltip text="Services" term_id="service" %} necessary to run {% glossary_tooltip text="Pods" term_id="pod" %} and is managed by the master components. The {% glossary_tooltip text="Services" term_id="service" %} on a node include Docker, kubelet and kube-proxy.
@@ -1,11 +0,0 @@
-id: platform-developer
-name: Platform Developer
-aka:
-  - Kubernetes Developer
-  - Extension Developer
-tags:
-  - user-type
-short-description: >
-  A person who customizes the Kubernetes platform to fit the needs of their project.
-long-description: >
-  A platform developer may, for example, use [Custom Resources](/docs/concepts/api-extension/custom-resources/) or [Extend the Kubernetes API with the aggregation layer](/docs/concepts/api-extension/apiserver-aggregation/) to add functionality to their instance of Kubernetes, specifically for their application.  Some Platform Developers are also {% glossary_tooltip text="contributors" term_id="contributor" %} and develop extensions which are contributed to the Kubernetes community.  Others develop closed-source commercial or site-specific extensions.
@@ -1,19 +0,0 @@
-id: pod-security-policy
-name: Pod Security Policy
-full-link: /docs/concepts/policy/pod-security-policy/
-related:
- pod
- container
- sidecar
- deployment
- statefulset
- security
-tags:
- core-object
- fundamental
-short-description: >
-  Enables fine-grained authorization of {% glossary_tooltip term_id="pod" %} creation and updates.
-long-description: >
-  A cluster-level resource that controls security sensitive aspects of the Pod specification.
-  The `PodSecurityPolicy` objects define a set of conditions that a Pod must run with in order to be accepted into the system, as well as defaults for the related fields.
-  Pod Security Policy control is implemented as an optional admission controller.
@@ -1,17 +0,0 @@
-id: pod
-name: Pod
-full-link: /docs/concepts/workloads/pods/pod-overview/
-related:
- container
- sidecar
- deployment
- statefulset
-tags:
- core-object
- fundamental
-short-description: >
-  The smallest and simplest Kubernetes object. A Pod represents a set of running {% glossary_tooltip text="containers" term_id="container" %} on your cluster.
-long-description: >
-  A Pod is typically set up to run a single primary container.
-  It can also run optional sidecar containers that add supplementary features like logging.
-  Pods are commonly managed by a {% glossary_tooltip term_id="deployment" %}.
@@ -1,10 +0,0 @@
-id: rbac
-name: RBAC (Role-Based Access Control)
-full-link: /docs/admin/authorization/rbac/
-tags:
- security
- fundamental
-short-description: >
-  Manages authorization decisions, allowing admins to dynamically configure access policies through the {% glossary_tooltip text="Kubernetes API" term_id="kubernetes-api" %}.
-long-description: >
-  RBAC utilizes *roles*, which contain permission rules, and *role bindings*, which grant the permissions defined in a role to a set of users.
@@ -1,13 +0,0 @@
-id: replica-set
-name: ReplicaSet
-full-link: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
-related:
- replication-controller
-tags:
- core-object
- architecture
-short-description: >
-  ReplicaSet is the next-generation Replication Controller.
-long-description: >
-  ReplicaSet, like ReplicationController, ensures that a specified number of pods replicas are running at one time.
-  ReplicaSet supports the new set-based selector requirements as described in the labels user guide, whereas a Replication Controller only supports equality-based selector requirements.
@@ -1,9 +0,0 @@
-id: replication-controller
-name: Replication Controller
-tags:
- fundamental
-short-description: >
-  Kubernetes service that ensures a specific number of instances of a pod are always running.
-long-description: >
-  Will automatically add or remove running instances of a pod, based on a set value for that pod. Allows the pod to return to the defined number of instances if pods are deleted or if too many are started by mistake.
-
@@ -1,11 +0,0 @@
-id: resource-quota
-name: Resource Quotas
-full-link: /docs/concepts/policy/resource-quotas/
-tags:
- fundamental
- operation
- architecture
-short-description: >
-  Provides constraints that limit aggregate resource consumption per {% glossary_tooltip term_id="namespace" %}.
-long-description: >
-  Limits the quantity of objects that can be created in a namespace by type, as well as the total amount of compute resources that may be consumed by resources in that project.
@@ -1,8 +0,0 @@
-id: reviewer
-name: Reviewer
-tags:
- community
-short-description: >
-  A person who reviews code for quality and correctness on some part of the project.
-long-description: >
-  Reviewers are knowledgeable about both the codebase and software engineering principles. Reviewer status is scoped to a part of the codebase.
@@ -1,15 +0,0 @@
-id: secret
-name: Secret
-full-link: /docs/concepts/configuration/secret/
-related:
- pods
- volume
-tags:
- core-object
- security
-short-description: >
-  Stores sensitive information, such as passwords, OAuth tokens, and ssh keys.
-long-description: >
-  Allows for more control over how sensitive information is used and reduces the risk of accidental exposure, including [encryption](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted) at rest. 
-  A {% glossary_tooltip text="Pod" term_id="pod" %} references the secret as a file in a volume mount or by the kubelet pulling images for a pod.
-  Secrets are great for confidential data and [ConfigMaps](https://kubernetes.io/docs/tasks/configure-pod-container/configmap/) for non-confidential data.
@@ -1,9 +0,0 @@
-id: security-context
-name: Security Context
-full-link: /docs/tasks/configure-pod-container/security-context/
-tags:
- security
-short-description: >
-  The securityContext field defines privilege and access control settings for a Pod or Container, including the runtime UID and GID.
-long-description: >
-  The securityContext field in a {% glossary_tooltip term_id="pod" %} (applying to all containers) or container is used to set the user (runAsUser) and group (fsGroup), capabilities, privilege settings, and security policies (SELinux/AppArmor/Seccomp) that container processes use.
@@ -1,10 +0,0 @@
-id: service-account
-name: Service Account
-full-link: /docs/tasks/configure-pod-container/configure-service-account/
-tags:
- fundamental
- core-object
-short-description: >
-  Provides an identity for processes that run in a Pod {% glossary_tooltip text="Pods" term_id="pod" %}.
-long-description: >
-  When processes inside Pods access the cluster, they are authenticated by the API server as a particular service account, for example, `default`. When you create a Pod, if you do not specify a service account, it is automatically assigned the default service account in the same namespace {% glossary_tooltip text="Namespace" term_id="namespace" %}.
@@ -1,9 +0,0 @@
-id: service-broker
-name: Service Broker
-tags:
- extension
-short-description: >
-  An endpoint for a set of {% glossary_tooltip text="Managed Services" term_id="managed-service" %} offered and maintained by a third-party.
-long-description: >
-  {% glossary_tooltip text="Service Brokers" term_id="service-broker" %} implement the [Open Service Broker API spec](https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md) and provide a standard interface for applications to use their Managed Services.
-  [Service Catalog](/docs/concepts/service-catalog/) provides a way to list, provision, and bind with Managed Services offered by Service Brokers.
@@ -1,8 +0,0 @@
-id: service-catalog
-name: Service Catalog
-tags:
- extension
-short-description: >
-  An extension API that enables applications running in Kubernetes clusters to easily use external managed software offerings, such as a datastore service offered by a cloud provider.
-long-description: >
-  Service Catalog provides a way to list, provision, and bind with external {% glossary_tooltip text="Managed Services" term_id="managed-service" %} from {% glossary_tooltip text="Service Brokers" term_id="service-broker" %} without needing detailed knowledge about how those services are created or managed.
@@ -1,10 +0,0 @@
-id: service
-name: Service
-full-link: /docs/concepts/services-networking/service/
-tags:
- fundamental
- core-object
-short-description: >
-  An API object that describes how to access applications, such as a set of {% glossary_tooltip text="Pods" term_id="pod" %}, and can describe ports and load-balancers.
-long-description: >
-  The access point can be internal or external to the cluster.
@@ -1,12 +0,0 @@
-id: sig
-name: SIG (special interest group)
-full-link: https://github.com/kubernetes/community/blob/master/sig-list.md#master-sig-list
-tags:
- community
-short-description: >
-  {% glossary_tooltip text="Community members" term_id="member" %} who collectively manage an ongoing piece or aspect of the larger Kubernetes open source project.
-long-description: |
-  Members within a SIG have a shared interest in advancing a specific area, such as architecture, API machinery, or documentation.
-  SIGs must follow the [SIG Governance](https://github.com/kubernetes/community/blob/master/sig-governance.md) guidelines but can have their own contribution policy and channels of communication.
-
-  For more information, see the [kubernetes/community](https://github.com/kubernetes/community) repo and the current list of [SIGs and Working Groups](https://github.com/kubernetes/community/blob/master/sig-list.md).
@@ -1,18 +0,0 @@
-id: statefulset
-name: StatefulSet
-full-link: /docs/concepts/workloads/controllers/statefulset/
-aka:
- PetSet
-related:
- deployment
- pod
-tags:
- core-object
- workload
- storage
-short-description: >
-  Manages the deployment and scaling of a set of {% glossary_tooltip text="Pods" term_id="pod" %}, *and provides guarantees about the ordering and uniqueness* of these Pods.
-long-description: |
-  Like a {% glossary_tooltip term_id="deployment" %}, a StatefulSet manages Pods that are based on an identical container spec. Unlike a Deployment, a StatefulSet maintains a sticky identity for each of their Pods. These pods are created from the same spec, but are not interchangeable&#58; each has a persistent identifier that it maintains across any rescheduling.
-
-  A StatefulSet operates under the same pattern as any other Controller. You define your desired state in a StatefulSet *object*, and the StatefulSet *controller* makes any necessary updates to get there from the current state.
@@ -1,11 +0,0 @@
-id: upstream
-name: Upstream (disambiguation)
-related:
- downstream
-tags:
- community
-short-description: >
-  May refer to: core Kubernetes or the source repo from which a repo was forked.
-long-description: |
-  * In the **Kubernetes Community**: Conversations often use *upstream* to mean the core Kubernetes codebase, which the general ecosystem, other code, or third-party tools relies upon. For example, [community members](#term-member) may suggest that a feature is moved upstream so that it is in the core codebase instead of in a plugin or third-party tool.
-  * In **GitHub** or **git**: The convention is to refer to a source repo as *upstream*, whereas the forked repo is considered *downstream*.
@@ -1,17 +0,0 @@
-id: volume
-name: Volume
-full-link: /docs/concepts/storage/volumes/
-related:
- pod
- container
- secret
-tags:
- core-object
- fundamental
-short-description: >
- A directory containing data, accessible to the containers in a {% glossary_tooltip text="pod" term_id="pod" %}.
-long-description: >
- A Kubernetes volume lives as long as the {% glossary_tooltip text="pod" term_id="pod" %} that encloses it.
- Consequently, a volume outlives any {% glossary_tooltip text="containers" term_id="container" %} that run within the
- {% glossary_tooltip text="pod" term_id="pod" %}, and data is preserved across
- {% glossary_tooltip text="container" term_id="container" %} restarts. 
@@ -1,11 +0,0 @@
-id: wg
-name: WG (working group)
-full-link: https://github.com/kubernetes/community/blob/master/sig-list.md#master-working-group-list
-tags:
- community
-short-description: >
-  Facilitates the discussion and/or implementation of a short-lived, narrow, or decoupled project for a committee, {% glossary_tooltip text="SIG" term_id="sig" %}, or cross-SIG effort.
-long-description: |
-  Working groups are a way of organizing people to accomplish a discrete task, and are relatively easy to create and deprecate when inactive.
-
-  For more information, see the [kubernetes/community](https://github.com/kubernetes/community) repo and the current list of [SIGs and working groups](https://github.com/kubernetes/community/blob/master/sig-list.md).
@@ -1,104 +0,0 @@
-bigheader: "Reference Documentation"
-abstract: "Design docs, concept definitions, and references for APIs and CLIs."
-toc:
- docs/reference/index.md
- docs/reference/glossary.md
-
- title: Using the API
-  section:
-  - docs/reference/api-overview.md
-  - docs/reference/client-libraries.md
-  - title: Accessing the API
-    section:
-    - docs/admin/accessing-the-api.md
-    - docs/admin/authentication.md
-    - docs/admin/bootstrap-tokens.md
-    - docs/admin/admission-controllers.md
-    - docs/admin/extensible-admission-controllers.md
-    - docs/admin/service-accounts-admin.md
-  - title: Authorization
-    section:
-    - docs/admin/authorization/index.md
-    - docs/admin/authorization/abac.md
-    - docs/admin/authorization/rbac.md
-    - docs/admin/authorization/node.md
-    - docs/admin/authorization/webhook.md
-  - docs/reference/deprecation-policy.md
-  - docs/reference/workloads-18-19.md
-
- title: API Reference
-  section:
-  - title: v1.8
-    path: /docs/api-reference/v1.8/
-  - docs/reference/labels-annotations-taints.md
-  - title: OpenAPI and Swagger
-    section:
-    - title: OpenAPI Spec
-      path: https://git.k8s.io/kubernetes/api/openapi-spec/
-    - title: Swagger Spec
-      path: https://git.k8s.io/kubernetes/api/swagger-spec/
-
- title: Federation API
-  section:
-    - docs/reference/federation/v1/operations.html
-    - docs/reference/federation/v1/definitions.html
-    - docs/reference/federation/v1beta1/operations.html
-    - docs/reference/federation/v1beta1/definitions.html
-    - docs/reference/federation/extensions/v1beta1/operations.html
-    - docs/reference/federation/extensions/v1beta1/definitions.html
-
- title: kubectl CLI
-  section:
-  - docs/reference/kubectl/overview.md
-  - docs/reference/generated/kubectl/kubectl-options.md
-  - title: kubectl Commands
-    path: /docs/reference/generated/kubectl/kubectl-commands.html
-  - docs/reference/kubectl/docker-cli-to-kubectl.md
-  - docs/reference/kubectl/conventions.md
-  - docs/reference/kubectl/jsonpath.md
-  - docs/reference/kubectl/cheatsheet.md
-
- title: Setup Tools Reference
-  section:
-  - docs/reference/generated/kubeadm.md
-  - title: Kubefed
-    section:
-    - docs/reference/generated/kubefed.md
-    - docs/reference/generated/kubefed_options.md
-    - docs/reference/generated/kubefed_init.md
-    - docs/reference/generated/kubefed_join.md
-    - docs/reference/generated/kubefed_unjoin.md
-    - docs/reference/generated/kubefed_version.md
-
- title: Command-line Tools Reference
-  section:
-  - docs/reference/generated/kubelet.md
-  - docs/admin/kubelet-authentication-authorization.md
-  - docs/reference/generated/kube-apiserver.md
-  - docs/reference/generated/kube-controller-manager.md
-  - docs/reference/generated/kube-proxy.md
-  - docs/reference/generated/kube-scheduler.md
-  - docs/admin/kubelet-tls-bootstrapping.md
-  - docs/reference/generated/cloud-controller-manager.md
-  - docs/reference/generated/federation-apiserver.md
-  - docs/reference/generated/federation-controller-manager.md
-
- title: Kubernetes Design Docs
-  section:
-  - title: Kubernetes Architecture
-    path: https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md
-  - title: Kubernetes Design Overview
-    path: https://github.com/kubernetes/kubernetes/tree/release-1.6/docs/design
-  - title: Kubernetes Identity and Access Management
-    path: https://git.k8s.io/community/contributors/design-proposals/auth/access.md
-  - docs/admin/ovs-networking.md
-  - title: Security Contexts
-    path: https://git.k8s.io/community/contributors/design-proposals/auth/security_context.md
-  - title: Security in Kubernetes
-    path: https://git.k8s.io/community/contributors/design-proposals/auth/security.md
-
- title: Kubernetes Issues and Security
-  section:
-  - title: Kubernetes Issue Tracker on GitHub
-    path: https://github.com/kubernetes/kubernetes/issues/
-  - docs/reference/security.md
@@ -1,108 +0,0 @@
-bigheader: "Setup"
-abstract: "Instructions for setting up a Kubernetes cluster."
-toc:
- docs/setup/index.md
- docs/setup/pick-right-solution.md
-
- title: Independent Solutions
-  section:
-  - docs/getting-started-guides/minikube.md
-
-  - title: Bootstrapping Clusters with kubeadm
-    section:
-    - docs/setup/independent/install-kubeadm.md
-    - docs/setup/independent/create-cluster-kubeadm.md
-    - docs/setup/independent/troubleshooting-kubeadm.md
-
-  - docs/getting-started-guides/scratch.md
-  - docs/getting-started-guides/alternatives.md
-
- title: Hosted Solutions
-  section:
-  - title: Running Kubernetes on Google Kubernetes Engine
-    path: https://cloud.google.com/kubernetes-engine/docs/before-you-begin/
-  - title: Running Kubernetes on Azure Container Service
-    path: https://docs.microsoft.com/en-us/azure/container-service/container-service-kubernetes-walkthrough
-  - title: Running Kubernetes on IBM Cloud Container Service
-    path: https://console.bluemix.net/docs/containers/container_index.html
-
- title: Turn-key Cloud Solutions
-  section:
-  - docs/getting-started-guides/gce.md
-  - docs/getting-started-guides/aws.md
-  - docs/getting-started-guides/azure.md
-  - docs/getting-started-guides/alibaba-cloud.md
-  - docs/getting-started-guides/clc.md
-  - title: Running Kubernetes on IBM Cloud
-    path: https://github.com/patrocinio/kubernetes-softlayer
-  - docs/getting-started-guides/stackpoint.md
-
- title: Custom Solutions
-
-  section:
-  - title: Custom Cloud Solutions
-    section:
-    - docs/getting-started-guides/coreos/index.md
-    - docs/getting-started-guides/ubuntu/index.md
-    - docs/getting-started-guides/kops.md
-    - docs/getting-started-guides/kubespray.md
-    - docs/getting-started-guides/running-cloud-controller.md
-
-  - title: On-Premise VMs
-    section:
-    - docs/getting-started-guides/coreos/index.md
-    - docs/getting-started-guides/cloudstack.md
-    - docs/getting-started-guides/vsphere.md
-    - docs/getting-started-guides/photon-controller.md
-    - docs/getting-started-guides/dcos.md
-    - docs/getting-started-guides/libvirt-coreos.md
-    - docs/getting-started-guides/ovirt.md
-    - docs/getting-started-guides/openstack-heat.md
-
-    - title: rkt
-      section:
-      - docs/getting-started-guides/rkt/index.md
-      - docs/getting-started-guides/rkt/notes.md
-
-    - docs/getting-started-guides/mesos/index.md
-    - docs/getting-started-guides/mesos-docker.md
-
-    - title: Bare Metal
-      section:
-      - docs/getting-started-guides/coreos/bare_metal_offline.md
-      - docs/getting-started-guides/fedora/fedora_ansible_config.md
-      - docs/getting-started-guides/fedora/fedora_manual_config.md
-      - docs/getting-started-guides/fedora/flannel_multi_node_cluster.md
-      - docs/getting-started-guides/centos/centos_manual_config.md
-      - docs/getting-started-guides/coreos/index.md
-      - docs/getting-started-guides/ubuntu/index.md
-
-      - title: Ubuntu
-        section:
-        - docs/getting-started-guides/ubuntu/index.md
-        - docs/getting-started-guides/ubuntu/validation.md
-        - docs/getting-started-guides/ubuntu/backups.md
-        - docs/getting-started-guides/ubuntu/upgrades.md
-        - docs/getting-started-guides/ubuntu/scaling.md
-        - docs/getting-started-guides/ubuntu/installation.md
-        - docs/getting-started-guides/ubuntu/monitoring.md
-        - docs/getting-started-guides/ubuntu/networking.md
-        - docs/getting-started-guides/ubuntu/security.md
-        - docs/getting-started-guides/ubuntu/storage.md
-        - docs/getting-started-guides/ubuntu/troubleshooting.md
-        - docs/getting-started-guides/ubuntu/decommissioning.md
-        - docs/getting-started-guides/ubuntu/operational-considerations.md
-        - docs/getting-started-guides/ubuntu/glossary.md
-        - docs/getting-started-guides/ubuntu/local.md
-        - docs/getting-started-guides/ubuntu/logging.md
-
-    - docs/getting-started-guides/windows/index.md
-
-  - docs/admin/node-conformance.md
-
- docs/concepts/cluster-administration/addons.md
- docs/admin/salt.md
- docs/admin/cluster-large.md
- docs/admin/multiple-zones.md
- docs/admin/high-availability/index.md
- docs/getting-started-guides/binary_release.md
@@ -1,2 +0,0 @@
-The topics in the `/docs/api-reference/` section of the Kubernetes docs
-are being moved to the [Reference](/docs/reference/) section. The content in this topic has moved to:
@@ -1,26 +0,0 @@
-{% capture samplecode %}{% include_relative {{include.file}} %}{% endcapture %}
-{% if include.k8slink %}{% capture ghlink %}https://raw.githubusercontent.com/kubernetes/kubernetes/blob/{{page.githubbranch}}{{include.k8slink}}{% endcapture %}{% endif %}
-{% if include.ghlink %}{% capture ghlink %}https://raw.githubusercontent.com/kubernetes/website/{{page.docsbranch}}{{include.ghlink}}{% endcapture %}{% endif %}
-{% capture mysample %}
-```{{include.language}}
-{{ samplecode | raw | strip }}
-```
-{: id="{{include.file | handleize}}"}
-{% endcapture %}
-<table class="includecode">
-    <thead>
-        <tr>
-            <th>
-                {% if ghlink %}<a href="{{ghlink}}" download="{{include.file}}">{% endif %}
-                    <code>{{include.file}}</code>
-                {% if ghlink %}</a>{% endif %}
-                <img src="/images/copycode.svg" style="max-height:24px" onclick="copyCode('{{include.file | handleize}}')" title="Copy {{include.file}} to clipboard">
-            </th>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>{{ mysample | markdownify }}</td>
-        </tr>
-    </tbody>
-</table>
@@ -1,12 +0,0 @@
-{% if page.deprecated %}
-<section id="deprecationWarning">
-  <main>
-    <div class="content deprecation-warning">
-      <h3>
-        Documentation for Kubernetes {{ page.version}} is no longer actively maintained. The version you are currently viewing is a static snapshot.
-        For up-to-date documentation, see the <a href="{{ page.currentUrl }}">latest</a> version.
-      </h3>
-    </div>
-  </main>
-</section>
-{% endif %}
@@ -1,28 +0,0 @@
-<a href="#" id="feature-state-dialog-link" class="ui-state-default ui-corner-all"><span class="ui-icon ui-icon-newwin"></span>{{ dialog_title }}</a>
-<div id="feature-state-dialog" class="ui-dialog-content" title="{{ dialog_title }}">
-{{ dialog_content | markdownify }}
-</div>
-{% raw %}<script>
-$(function(){
-    
-    $( "#feature-state-dialog" ).dialog({
-        autoOpen: false,
-        width: {% endraw %}{{ dialog_width | default: "600" }}{% raw %},
-        buttons: [
-            {
-                text: "Ok",
-                click: function() {
-                    $( this ).dialog( "close" );
-                }
-            }
-        ]
-    });
-
-    // Link to open the dialog
-    $( "#feature-state-dialog-link" ).click(function( event ) {
-        $( "#feature-state-dialog" ).dialog( "open" );
-        event.preventDefault();
-    });
-
-});
-</script>{% endraw %}
@@ -1,13 +0,0 @@
-{% assign dialog_title = "alpha" %}
-{% capture dialog_content %}
-This feature is currently in a *alpha* state, meaning:
-
-* The version names contain alpha (e.g. v1alpha1).
-* Might be buggy. Enabling the feature may expose bugs. Disabled by default.
-* Support for feature may be dropped at any time without notice.
-* The API may change in incompatible ways in a later software release without notice.
-* Recommended for use only in short-lived testing clusters, due to increased risk of bugs and lack of long-term support.
-
-{% endcapture %}
-
-**FEATURE STATE:** `Kubernetes {{ for_k8s_version | default: page.version }}` {% include feature-dialog.md %}
@@ -1,14 +0,0 @@
-{% assign dialog_title = "beta" %}
-{% capture dialog_content %}
-This feature is currently in a *beta* state, meaning:
-
-* The version names contain beta (e.g. v2beta3).
-* Code is well tested. Enabling the feature is considered safe. Enabled by default.
-* Support for the overall feature will not be dropped, though details may change.
-* The schema and/or semantics of objects may change in incompatible ways in a subsequent beta or stable release. When this happens, we will provide instructions for migrating to the next version. This may require deleting, editing, and re-creating API objects. The editing process may require some thought. This may require downtime for applications that rely on the feature.
-* Recommended for only non-business-critical uses because of potential for incompatible changes in subsequent releases. If you have multiple clusters that can be upgraded independently, you may be able to relax this restriction.
-* **Please do try our beta features and give feedback on them! After they exit beta, it may not be practical for us to make more changes.**
-
-{% endcapture %}
-
-**FEATURE STATE:** `Kubernetes {{ for_k8s_version | default: page.version }}` {% include feature-dialog.md %}
@@ -1,6 +0,0 @@
-{% assign dialog_title = "deprecated" %}
-{% capture dialog_content %}
-This feature is *deprecated*. For more information on this state, see the [Kubernetes Deprecation Policy](/docs/reference/deprecation-policy/).
-{% endcapture %}
-
-**DEPRECATION NOTICE:** As of `Kubernetes {{ for_k8s_version | default: page.version }}`, this has been {% include feature-dialog.md %}
@@ -1,10 +0,0 @@
-{% assign dialog_title = "stable" %}
-{% capture dialog_content %}
-This feature is *stable*, meaning:
-
-* The version name is vX where X is an integer.
-* Stable versions of features will appear in released software for many subsequent versions.
-
-{% endcapture %}
-
-**FEATURE STATE:** `Kubernetes {{ for_k8s_version | default: page.version }}` {% include feature-dialog.md %}
@@ -1,34 +0,0 @@
-<footer>
-    <main class="light-text">
-        <nav>
-            <a href="/docs/tutorials/stateless-application/hello-minikube/">Get Started</a>
-            <a href="/docs/home/">Documentation</a>
-            <a href="http://blog.kubernetes.io/">Blog</a>
-            <a href="/partners/">Partners</a>
-            <a href="/community/">Community</a>
-            <a href="/case-studies/">Case Studies</a>
-        </nav>
-        <div class="social">
-            <div>
-                <a href="https://twitter.com/kubernetesio" class="twitter"><span>twitter</span></a>
-                <a href="https://github.com/kubernetes/kubernetes" class="github"><span>Github</span></a>
-                <a href="http://slack.k8s.io/" class="slack"><span>Slack</span></a>
-            </div>
-            <div>
-                <a href="http://stackoverflow.com/questions/tagged/kubernetes" class="stack-overflow"><span>Stack Overflow</span></a>
-                <a href="https://groups.google.com/forum/#!forum/kubernetes-users" class="mailing-list"><span>Mailing List</span></a>
-                <a href="https://calendar.google.com/calendar/embed?src=nt2tcnbtbied3l6gi2h29slvc0%40group.calendar.google.com" class="calendar"><span>Events Calendar</span></a>
-            </div>
-            <div>
-                <a href="/docs/setup/pick-right-solution/" class="button">Get Kubernetes</a>
-                <a href="https://github.com/kubernetes/kubernetes" class="button">Contribute</a>
-            </div>
-        </div>
-        <div id="miceType" class="center">
-            &copy; {{ 'now' | date: "%Y" }} The Kubernetes Authors | Documentation Distributed under <a href="https://git.k8s.io/website/LICENSE" class="light-text">CC BY 4.0</a>
-        </div>
-        <div id="miceType" class="center">
-            Copyright &copy; {{ 'now' | date: "%Y" }} The Linux Foundation&reg;. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page: <a href="https://www.linuxfoundation.org/trademark-usage" class="light-text">https://www.linuxfoundation.org/trademark-usage</a>
-        </div>
-    </main>
-</footer>
@@ -1,29 +0,0 @@
-<head>
-    <meta charset="utf-8">
-    <meta name="viewport" content="width=device-width, initial-scale=1">
-    <link rel="shortcut icon" type="image/png" href="/images/favicon.png">
-    <link rel="stylesheet" type="text/css" href="https://fonts.googleapis.com/css?family=Roboto:400,100,100italic,300,300italic,400italic,500,500italic,700,700italic,900,900italic">
-    <link rel="stylesheet" type="text/css" href="https://fonts.googleapis.com/css?family=Roboto+Mono">
-    {% if page.case_study_styles %}<link rel="stylesheet" type="text/css" href="/css/case_study_styles.css"><!-- custom case_study_styles on -->{% else %}<link rel="stylesheet" type="text/css" href="/css/styles.css"><!-- default styles.css on -->{% endif %}
-    <link rel="stylesheet" type="text/css" href="/css/jquery-ui.min.css">
-    <link rel="stylesheet" type="text/css" href="/css/sweetalert.css">
-    <link rel="stylesheet" type="text/css" href="/css/callouts.css">
-    <link rel="stylesheet" type="text/css" href="/css/custom-jekyll/tags.css">
-    {% if page.deprecated %}<link rel="stylesheet" type="text/css" href="/css/deprecation-warning.css">{% endif %}
-    {% if page.class == "gridPage" %}<link rel="stylesheet" type="text/css" href="/css/gridpage.css">{% endif %}
-    {% if page.css %}<link rel="stylesheet" type="text/css" href="{{ page.css }}"><!-- custom css added -->{% else %}<!-- no custom css detected -->{% endif %}
-
-    {% if page.description %}
-    <meta name="description" content="{{ page.description }}" />
-    {% else %}
-    <meta name="description" content="{{ page.title }}" />
-    {% endif %}
-
-    <script src="/js/jquery-2.2.0.min.js"></script>
-    <script src="/js/jquery-ui.min.js"></script>
-    <script src="/js/script.js"></script>
-    <script src="/js/sweetalert.min.js"></script>
-    <script src="/js/bootstrap.min.js"></script>
-    <script src="/js/custom-jekyll/tags.js"></script>
-    {% seo %}
-</head>
@@ -1,69 +0,0 @@
-<div id="cellophane" onclick="kub.toggleMenu()"></div>
-
-<header>
-    <a href="/" class="logo"></a>
-
-    <div class="nav-buttons" data-auto-burger="primary">
-        <ul class="global-nav">
-            <li><a href="/docs/home/">Documentation</a></li>
-            <li><a href="http://blog.kubernetes.io/">Blog</a></li>
-            <li><a href="/partners/">Partners</a></li>
-            <li><a href="/community/">Community</a></li>
-            <li><a href="/case-studies/">Case Studies</a></li>
-            <li>
-                <a href="#">
-                    {{page.version}} <span class="ui-icon ui-icon-carat-1-s"></span>
-                </a>
-                <ul>
-                {% for version in page.versions %}
-                  <li><a href="{{ version.url }}">{{ version.version }}</a></li>
-                {% endfor %}
-                </ul>
-              </li>
-            </li>
-        </ul>
-        <!-- <a href="/docs/home" class="button" id="viewDocs" data-auto-burger-exclude>View Documentation</a> -->
-        <a href="/docs/tutorials/kubernetes-basics/" class="button" id="tryKubernetes" data-auto-burger-exclude>Try Kubernetes</a>
-        <button id="hamburger" onclick="kub.toggleMenu()" data-auto-burger-exclude><div></div></button>
-    </div>
-
-    <nav id="mainNav">
-        <main data-auto-burger="primary">
-        <div class="nav-box">
-            <h3><a href="/docs/tutorials/stateless-application/hello-minikube/">Get Started</a></h3>
-            <p>Ready to get your hands dirty? Build a simple Kubernetes cluster that runs "Hello World" for Node.js.</p>
-        </div>
-        <div class="nav-box">
-            <h3><a href="/docs/home/">Documentation</a></h3>
-            <p>Learn how to use Kubernetes with the use of walkthroughs, samples, and reference documentation. You can even <a href="/editdocs/" data-auto-burger-exclude>help contribute to the docs</a>!</p>
-        </div>
-        <div class="nav-box">
-            <h3><a href="/community/">Community</a></h3>
-            <p>If you need help, you can connect with other Kubernetes users and the Kubernetes authors, attend community events, and watch video presentations from around the web.</p>
-        </div>
-        <div class="nav-box">
-            <h3><a href="http://blog.kubernetes.io">Blog</a></h3>
-            <p>Read the latest news for Kubernetes and the containers space in general, and get technical how-tos hot off the presses.</p>
-        </div>
-        </main>
-        <main data-auto-burger="primary">
-        <div class="left">
-            <h5 class="github-invite">Interested in hacking on the core Kubernetes code base?</h5>
-            <a href="https://github.com/kubernetes/kubernetes" class="button" data-auto-burger-exclude>View On Github</a>
-        </div>
-
-        <div class="right">
-            <h5 class="github-invite">Explore the community</h5>
-            <div class="social">
-                <a href="https://twitter.com/kubernetesio" class="twitter"><span>Twitter</span></a>
-                <a href="https://github.com/kubernetes/kubernetes" class="github"><span>Github</span></a>
-                <a href="http://slack.k8s.io/" class="slack"><span>Slack</span></a>
-                <a href="http://stackoverflow.com/questions/tagged/kubernetes" class="stack-overflow"><span>Stack Overflow</span></a>
-                <a href="https://groups.google.com/forum/#!forum/kubernetes-users" class="mailing-list"><span>Mailing List</span></a>
-                <a href="https://calendar.google.com/calendar/embed?src=nt2tcnbtbied3l6gi2h29slvc0%40group.calendar.google.com" class="calendar"><span>Events Calendar</span></a>
-            </div>
-        </div>
-        <div class="clear" style="clear: both"></div>
-        </main>
-    </nav>
-</header>
@@ -1,15 +0,0 @@
-{% comment %} See /docs/tabs-example.md for usage example. {% endcomment %}
-{% assign tab_set_id = tab_set_name | default: "tabset" | slugify %}
-<div id="{{tab_set_id}}">
-    <ul>
-{% for name in tab_names %}
-        <li><a href="#{{tab_set_id}}-{{forloop.index0}}">{{ name | strip }}</a></li>
-{% endfor %}
-    </ul>
-{% for content in tab_contents %}
-    <div id="{{tab_set_id}}-{{forloop.index0}}">
-    {{ content | markdownify }}
-    </div>
-{% endfor %}
-</div>
-<script>$(function(){$("#{{tab_set_id}}").tabs();});</script>
@@ -1,15 +0,0 @@
-<!-- Use include_cached when incorporating this file, in order to reduce computation/build time -->
-
-{% assign glossary_terms = site.data.glossary | where_exp: "term", "term.id != '_example'" %}
-
-{% assign tag_map = "" | split: " " %}
-
-{% for tag in site.data.canonical-tags %}
-
-{% assign term_list = glossary_terms | where_exp:"term", "term.tags contains tag" | map: "id" %}
-
-{% assign tag_obj = "" | split: " " | push: tag | push: term_list %}
-
-{% assign tag_map = tag_map | push: tag_obj %}
-
-{% endfor %}
@@ -1,14 +0,0 @@
-You need to have a Kubernetes cluster, and the kubectl command-line tool must
-be configured to communicate with your cluster. If you do not already have a
-cluster, you can create one by using
-[Minikube](/docs/getting-started-guides/minikube),
-or you can use one of these Kubernetes playgrounds:
-
-* [Katacoda](https://www.katacoda.com/courses/kubernetes/playground)
-* [Play with Kubernetes](http://labs.play-with-k8s.com/)
-
-{% if page.min-kubernetes-server-version == page.version %}
-Your Kubernetes server must be version {{page.min-kubernetes-server-version}}.
-{% elsif page.min-kubernetes-server-version %}
-Your Kubernetes server must be version {{page.min-kubernetes-server-version}} or later.
-{% endif %} To check the version, enter `kubectl version`.
@@ -1,16 +0,0 @@
-### ERROR: You must define a <span style="font-family: monospace">`{{ include.missing_block }}`</span> block
-{: style="color:red" }
-
-This template requires that you provide text that {{ include.purpose }}. The text in this block will
-be displayed under the heading **{{ include.heading }}**.
-
-To get rid of this message and take advantage of this template, define the `{{ include.missing_block }}`
-variable and populate it with content.
-
-```liquid
-{% raw %}{%{% endraw %} capture {{ include.missing_block }} {% raw %}%}{% endraw %}
-Text that {{ include.purpose }}.
-{% raw %}{%{% endraw %} endcapture {% raw %}%}{% endraw %}
-```
-
-<!-- TEMPLATE_ERROR -->
@@ -1,88 +0,0 @@
-{% if concept %}<!-- check for this before going any further; if not present, skip to else at bottom -->
-
-# Overview of {{concept}}s
-
-{% if what_is %}
-
-### What is a {{ concept }}?
-
-{{ what_is }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='what_is' heading='What is a (Concept)?' purpose='explains what this concept is and its purpose.' %}
-
-{% endif %}
-
-
-{% if when_to_use %}
-
-### When to use {{ concept }}s
-
-{{ when_to_use }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='when_to_use' heading='When to use (Concept)' purpose='explains when to use this object.' %}
-
-{% endif %}
-
-
-{% if when_not_to_use %}
-
-### When not to use {{ concept }}s
-
-{{ when_not_to_use }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='when_not_to_use' heading='When not to use (Concept)' purpose='explains when not to use this object.' %}
-
-{% endif %}
-
-
-{% if status %}
-
-### {{ concept }} status
-
-{{ status }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='status' heading='Retrieving status for a (Concept)' purpose='explains how to retrieve a status description for this object.' %}
-
-{% endif %}
-
-
-{% if usage %}
-
-#### Usage
-
-{{ usage }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='usage' heading='Usage' purpose='shows the most basic, common use case for this object, in the form of a code sample, command, etc, using tabs to show multiple approaches' %}
-
-{% endif %}
-
-<!-- continuing the "if concept" if/then: -->
-
-{% else %}
-
-### ERROR: You must define a "concept" variable
-{: style="color:red" }
-
-This template requires a variable called `concept` that is simply the name of the
-concept for which you are giving an overview. This will be displayed in the 
-headings for the document.
-
-To get rid of this message and take advantage of this template, define `concept`:
-
-```liquid
-{% raw %}{% assign concept="Replication Controller" %}{% endraw %}
-```
-
-Complete this task, then we'll walk you through preparing the rest of the document.
-
-{% endif %}
@@ -1,32 +0,0 @@
-{% if overview %}
-
-{{ overview }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='overview' purpose='provides an overview of this concept.' %}
-
-{% endif %}
-
-* TOC
-{:toc}
-
-{% if body %}
-
-{{ body }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='body' purpose='supplies the body of the page content.' %}
-
-{% endif %}
-
-
-{% if whatsnext %}
-
-## What's next
-
-{{ whatsnext }}
-
-{% endif %}
-
@@ -1,64 +0,0 @@
-# Kubernetes Glossary
-
-To write a glossary snippet, start with a copy of the template, [`/_data/glossary/_example.yml`](/_data/glossary/_example.yml). Make sure to provide (or omit) values for the following fields:
-
-* (Required) `id`
-  * This field must match the name of the glossary file itself (without the `*.yml` extension). It is *not* intended to be displayed to users, and is only used programmatically.
-* (Required) `name`
-  * The name of the term.
-* (Required) `tags`
-  * Must be one of the tags listed in the [tags directory in the website repository](https://github.com/kubernetes/website/tree/master/_data/canonical-tags).
-* (Required) `short description`
-  * Make sure to replace the instructional text in the template with your content.
-* (Optional) `aka`
-  * These synonyms do not need to be glossary terms themselves (if they are deprecated), and can include spaces.
-* (Optional) `related`
-  * These should be the `id`s (not the `names`) of related glossary terms.
-* (Optional) `long description`
-  * If you do not provide a long description, remove the field -- that is, the complete key-value pair.
-
-The `_example.yml` template also contains basic information about how to write your snippet. For additional guidance, continue reading this readme.
-
-## Glossary snippet style guide
-
-This style guide supplements the guidance provided in the glossary template. It's intended to help you think about what and how to write glossary definitions. For more general guidance on style, consult [the core docs style guide](https://kubernetes.io/docs/home/contribute/style-guide/).
-
-### Minimum viable snippet:
-
-Every snippet must include at least the short description. The long description is optional, but should be provided for terms that need additional clarification. For consistency with existing *Concept* definitions, *write your definitions as if the term is plural*.
-
-**short-description** (Required): One line (or two short lines) that provides a minimum definition. Do not repeat the term. Prefer fragments. Model after tooltips. End with a period.
-
-**long-description** (Optional): Longer additional text to appear after (in conjunction with) short description. Provide in cases where the short description is not sufficient for the intro paragraph to a topic. Write complete but concise sentences.
-
-### Examples
-
-```yaml
- name: Pod
- tags:
-  - Fundamental
-  - Workload
-  - API Object
- short-description: The smallest and simplest Kubernetes objects. Represent a set of running processes on your cluster.
- long-description: Pods most often run only a single container, and are managed by a Deployment.
-```
-
-```yaml
- name: Deployment
- tags:
-  - Fundamental
-  - Workload
-  - API Object
- short-description: Controllers that provide declarative updates for Pods and ReplicaSets.
- long-description: Deployments are responsible for creating and updating instances of an application.
-```
-
-### Thinking about definitions
-
-* **Think of the short description as it would appear in a tooltip.** Is it sufficient to get the reader started? Is it short enough to be read inside a small UI element?
-
-  *Tip*: look at the API reference doc content (for example, https://kubernetes.io/docs/api-reference/v1.7/). Note, however, that this content should be used with care. The concept docs for Pod, for example, are clearer than the reference docs.
-
-* **The long description should follow the short description to make a complete introduction to a topic.** (This is the content that appears at the top of the content, before any generated TOC.) Does it provide information that's not already clear from the short description? Does it provide information that readers should have a general sense of before they dive into the details of the topic it helps introduce?
-
-  *Tip:* the long description does not need to be long; it's intended to extend but not replace the short description. Look through current related docs for ideas. (The Deployment long description is taken from a tutorial, for example.)
@@ -1,10 +0,0 @@
-### ERROR: You must define a <span style="font-family: monospace">`{{ include.missing_block }}`</span> field
-{: style="color:red" }
-
-The glossary template requires that you provide text that {{ include.purpose }}.
-
-To get rid of this message and take advantage of this template, define the `{{ include.missing_block }}`
-field for the `{{ include.term }}` glossary term and populate it with content.
-
-See `_data/glossary/_example.yml` for reference.
-<!-- TEMPLATE_ERROR -->
@@ -1,29 +0,0 @@
-{% assign term_data = site.data.glossary.[include.term_id] %}
-
-{% if include.length == "all" or include.length == "short" %}
-
-{% if term_data.short-description %}
-
-{{ term_data.short-description | liquify | markdownify }}
-
-{% else %}
-
-{% include templates/glossary/_error.md term=term_data.name missing_block='short-description' purpose='concisely describes the key term in 1-2 lines' %}
-
-{% endif %}
-
-{% endif %}
-
-{% if include.length == "all" or include.length == "long" %}
-
-{% if term_data.long-description %}
-
-{{ term_data.long-description | liquify | markdownify }}
-
-{% else %}
-
-{% include templates/glossary/_error.md term=term_data.name missing_block='long-description' purpose='describes the key term in greater depth, supplementing the short-description' %}
-
-{% endif %}
-
-{% endif %}
@@ -1,37 +0,0 @@
-{% if command %}
-
-# {% if site.data.kubectl[command].name != "kubectl" %}kubectl {% endif %}{{ site.data.kubectl[command].name }}
-
-{{ site.data.kubectl[command].synopsis }}
-
-## Description
-
-{{ site.data.kubectl[command].description }}
-
-{% if site.data.kubectl[command].options %}
-## Options
-
-| Option | Shorthand | Default Value | Usage |
-|--------------------|---------------|-------|{% for option in site.data.kubectl[command].options %}
-| `{{option.name | strip}}` | {% if option.shorthand %}`{{ option.shorthand | strip }}`{% endif %} | {% if option.default_value %}`{{option.default_value| strip}}`{% endif %} | {% if option.usage %}{{option.usage| strip | replace:'|',', '}}{% endif %} |{% endfor %}
-{% endif %}
-
-{% if site.data.kubectl[command].inherited_options %}
-## Inherited Options
-
-| Option | Shorthand | Default Value | Usage |
-|--------------------|---------------|-------|{% for option in site.data.kubectl[command].inherited_options %}
-| `{{option.name | strip}}` | {% if option.shorthand %}`{{ option.shorthand | strip }}`{% endif %} | {% if option.default_value %}`{{option.default_value| strip}}`{% endif %} | {% if option.usage %}{{option.usage| strip | replace:'|',', '}}{% endif %} |{% endfor %}
-{% endif %}
-
-## See also
-
-{% for seealso in site.data.kubectl[command].see_also %}
- [`{{ seealso }}`](/docs/kubectl/{% if seealso != "kubectl" %}kubectl_{{seealso}}{% endif %})
-{% endfor %}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='command' heading='kubectl (command)' purpose='names the kubectl command, so that the appropriate YAML file (from _data/kubectl) can be transformed into a page.' %}
-
-{% endif %}
@@ -1,55 +0,0 @@
-{% if overview %}
-
-{{ overview }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='overview' purpose='states, in one or two sentences, the purpose of this document' %}
-
-{% endif %}
-
-
-* TOC
-{: toc}
-
-
-{% if prerequisites %}
-
-## Before you begin
-
-{{ prerequisites }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='prerequisites' heading='Before you begin' purpose='lists action prerequisites and knowledge prerequisites' %}
-
-{% endif %}
-
-
-{% if steps %}
-
-{{ steps }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='steps' purpose='lists a sequence of numbered steps that accomplish the task.' %}
-
-{% endif %}
-
-
-{% if discussion %}
-
-{{ discussion }}
-
-{% else %}
-
-{% endif %}
-
-
-{% if whatsnext %}
-
-## What's next
-
-{{ whatsnext }}
-
-{% endif %}
@@ -1,68 +0,0 @@
-{% if overview %}
-
-{{ overview }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='overview' purpose='states, in one or two sentences, the purpose of this document' %}
-
-{% endif %}
-
-
-* TOC
-{: toc}
-
-
-{% if objectives %}
-
-## Objectives
-
-{{ objectives }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='objectives' heading='Objectives' purpose='lists the objectives for this tutorial.' %}
-
-{% endif %}
-
-
-{% if prerequisites %}
-
-## Before you begin
-
-{{ prerequisites }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='prerequisites' heading='Before you begin' purpose='lists action prerequisites and knowledge prerequisites' %}
-
-{% endif %}
-
-
-{% if lessoncontent %}
-
-{{ lessoncontent }}
-
-{% else %}
-
-{% include templates/_errorthrower.md missing_block='lessoncontent' purpose='provides the lesson content for this tutorial.' %}
-
-{% endif %}
-
-
-{% if cleanup %}
-
-## Cleaning up
-
-{{ cleanup }}
-
-{% endif %}
-
-
-{% if whatsnext %}
-
-## What's next
-
-{{ whatsnext }}
-
-{% endif %}
@@ -1,15 +0,0 @@
-{% capture whitespace %}
-  {% for item in include.tree %}
-    {% if found_toc %}
-      {% break %}
-    {% endif %}
-    {% if item.section %}
-      {% include tocsearch.html tree=item.section toc=include.toc %}
-    {% else %}
-      {% if item == page.path %}
-        {% assign found_toc = include.toc %}
-        {% break %}
-      {% endif %}
-    {% endif %}
-  {% endfor %}
-{% endcapture %}
@@ -1,25 +0,0 @@
-{% for item in include.tree %}
-  {% if item.section %}
-    <div class="item" data-title="{{ item.title }}">
-      <div class="container">
-        {% include_cached tree.html tree=item.section %}
-      </div>
-    </div>
-  {% else %}
-
-    {% capture whitespace %}
-      {% if item.path %}
-        {% assign path   = item.path %}
-        {% assign title  = item.title %}
-      {% else %}
-        {% assign found_page = site.pages | where: "path", item | first %}
-        {% assign title = found_page.title %}
-        {% assign path  = found_page.url %}
-      {% endif %}
-    {% endcapture %}
-
-    {% if path %}
-      <a class="item" data-title="{{ title }}" href="{{ path }}"></a>
-    {% endif %}
-  {% endif %}
-{% endfor %}
--- a/Show More
+++ b/Show More