Change version selector to retain current page when switching versions (#19470)

6:16:23 PM:     [FAILURE] The Hugo version set in the Makefile is 0.53 while the version in netlify.toml is 0.57.2
6:16:23 PM:     [FAILURE] Please update these versions so that they are same (consider the higher of the two versions as

.dockerignore

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

.editorconfig

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

.github/ISSUE_TEMPLATE.md

@@ -1,4 +1,5 @@
 <!-- Thanks for filing an issue! Before submitting, please fill in the following information. -->
+<!-- See https://kubernetes.io/docs/contribute/start/ for guidance on writing an actionable issue description. -->
 
 <!--Required Information-->
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,8 +1,16 @@
 >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-> 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.
-
-![Allow edits from maintainers checkbox](https://help.github.com/assets/images/help/pull_requests/allow-maintainers-to-make-edits-sidebar-checkbox.png)
+>
+> For 1.14 Features: set Milestone to 1.14 and Base Branch to dev-1.14
+> 
+> For Chinese localization, base branch to release-1.12
+>
+> For Korean Localization: set Base Branch to dev-1.13-ko.<latest team milestone>
+>
+> Help editing and submitting pull requests:
+> https://kubernetes.io/docs/contribute/start/#improve-existing-content.
+>
+> Help choosing which branch to use:
+> https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use.
+>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+>

.gitignore

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

.travis.yml

@@ -1,20 +1,22 @@
+env:
+  global:
+    - KUBE_VERSION: 1.13
 language: go
 go:
-  - 1.8.3
+  - 1.11.5
 
-# Don't want default ./... here:
-install:
-- export PATH=$GOPATH/bin:$PATH
-- mkdir -p $HOME/gopath/src/k8s.io
-- mv $TRAVIS_BUILD_DIR $HOME/gopath/src/k8s.io/website
-
-# (1) Fetch dependencies for us to run the tests in test/examples_test.go
-- go get -t -v k8s.io/website/test
-
-# Simplified deduplication of dependencies.
-- cp -L -R $GOPATH/src/k8s.io/kubernetes/vendor/ $GOPATH/src/
-- rm -r $GOPATH/src/k8s.io/kubernetes/vendor/
-
-script:
-- go test -v k8s.io/website/test
-- ./verify-docs-format.sh
+jobs:
+  include:
+    - name: "Testing examples"
+      cache:
+        directories:
+          - $HOME/.cache/go-build
+      install:
+      - bash scripts/test_examples.sh install
+      script:
+      - bash scripts/test_examples.sh run
+    - name: "Hugo build"
+      install:
+      - make travis-hugo-build
+      script:
+      - hugo

404.md

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

CONTRIBUTING.md

@@ -9,7 +9,8 @@ These are just guidelines, not rules. Use your best judgment, and feel free to p
 
 ### Code of Conduct
 
-Kubernetes follows the [Cloud Native Computing Foundation (CNCF) Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to Sarah Novotny [sarahnovotny@google.com](mailto:sarahnovotny@google.com) and/or Dan Kohn [dan@linuxfoundation.org](mailto:dan@linuxfoundation.org).
+Kubernetes follows the [Cloud Native Computing Foundation (CNCF) Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to the
+[Kubernetes Code of Conduct Committee](https://github.com/kubernetes/community/tree/master/committee-code-of-conduct) <conduct@kubernetes.io>.
 
 ### Documentation and Site Decisions
 

Dockerfile

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

Gemfile

@@ -1,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.13"
-   gem "jekyll-relative-links", "~> 0.2"
-   gem "jekyll-swiss", "~> 0.4"
-   gem "jekyll-theme-architect", "0.0.3"
-   gem "jekyll-theme-cayman", "0.0.3"
-   gem "jekyll-theme-dinky", "0.0.3"
-   gem "jekyll-theme-hacker", "0.0.3"
-   gem "jekyll-theme-leap-day", "0.0.3"
-   gem "jekyll-theme-merlot", "0.0.3"
-   gem "jekyll-theme-midnight", "0.0.3"
-   gem "jekyll-theme-minimal", "0.0.3"
-   gem "jekyll-theme-modernist", "0.0.3"
-   gem "jekyll-theme-primer", "~> 0.1"
-   gem "jekyll-theme-slate", "0.0.3"
-   gem "jekyll-theme-tactile", "0.0.3"
-   gem "jekyll-theme-time-machine", "0.0.3"
-   gem "jekyll-titles-from-headings", "~> 0.1"
-   gem "jekyll-include-cache", "~> 0.1"
-   gem 'jekyll-youtube', '~> 1.0'
-end
-
-gem "kramdown", "~> 1.11"
-gem "rouge", "~> 2.0"
-gem "pry"

Gemfile.lock

@@ -1,183 +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.14.0)
-      multipart-post (>= 1.2, < 3)
-    ffi (1.9.21)
-    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.3)
-      jekyll (~> 3.3)
-    jekyll-gist (1.5.0)
-      octokit (~> 4.2)
-    jekyll-github-metadata (2.9.4)
-      jekyll (~> 3.1)
-      octokit (~> 4.0, != 4.4.0)
-    jekyll-include-cache (0.1.0)
-      jekyll (~> 3.3)
-    jekyll-optional-front-matter (0.3.0)
-      jekyll (~> 3.0)
-    jekyll-paginate (1.1.0)
-    jekyll-readme-index (0.0.3)
-      jekyll (~> 3.0)
-    jekyll-redirect-from (0.13.0)
-      jekyll (~> 3.3)
-    jekyll-relative-links (0.5.2)
-      jekyll (~> 3.3)
-    jekyll-sass-converter (1.5.2)
-      sass (~> 3.4)
-    jekyll-seo-tag (2.4.0)
-      jekyll (~> 3.3)
-    jekyll-sitemap (1.2.0)
-      jekyll (~> 3.3)
-    jekyll-swiss (0.4.0)
-    jekyll-theme-architect (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-cayman (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-dinky (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-hacker (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-leap-day (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-merlot (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-midnight (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-minimal (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-modernist (0.0.3)
-      jekyll (~> 3.3)
-    jekyll-theme-primer (0.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.1)
-      jekyll (~> 3.3)
-    jekyll-watch (1.5.1)
-      listen (~> 3.0)
-    jekyll-youtube (1.0.0)
-      jekyll
-    json (1.8.6)
-    kramdown (1.16.2)
-    liquid (4.0.0)
-    listen (3.1.5)
-      rb-fsevent (~> 0.9, >= 0.9.4)
-      rb-inotify (~> 0.9, >= 0.9.7)
-      ruby_dep (~> 1.2)
-    mercenary (0.3.6)
-    method_source (0.9.0)
-    minima (2.3.0)
-      jekyll (~> 3.5)
-      jekyll-feed (~> 0.9)
-      jekyll-seo-tag (~> 2.1)
-    multipart-post (2.0.0)
-    octokit (4.8.0)
-      sawyer (~> 0.8.0, >= 0.5.3)
-    pathutil (0.16.1)
-      forwardable-extended (~> 2.6)
-    pry (0.11.3)
-      coderay (~> 1.1.0)
-      method_source (~> 0.9.0)
-    public_suffix (3.0.2)
-    rb-fsevent (0.10.2)
-    rb-inotify (0.9.10)
-      ffi (>= 0.5.0, < 2)
-    rouge (2.2.1)
-    ruby_dep (1.5.0)
-    safe_yaml (1.0.4)
-    sass (3.5.5)
-      sass-listen (~> 4.0.0)
-    sass-listen (4.0.0)
-      rb-fsevent (~> 0.9, >= 0.9.4)
-      rb-inotify (~> 0.9, >= 0.9.7)
-    sawyer (0.8.1)
-      addressable (>= 2.3.5, < 2.6)
-      faraday (~> 0.8, < 1.0)
-    terminal-table (1.8.0)
-      unicode-display_width (~> 1.1, >= 1.1.1)
-    unicode-display_width (1.3.0)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  coffee-script (~> 2.4)
-  coffee-script-source (~> 1.12)
-  ethon (~> 0.10)
-  execjs (~> 2.7)
-  jekyll (= 3.6.0)
-  jekyll-avatar (~> 0.4)
-  jekyll-coffeescript (~> 1.0)
-  jekyll-default-layout (~> 0.1)
-  jekyll-feed (~> 0.6)
-  jekyll-gist
-  jekyll-github-metadata (~> 2.2)
-  jekyll-include-cache (~> 0.1)
-  jekyll-optional-front-matter (~> 0.1)
-  jekyll-paginate (= 1.1.0)
-  jekyll-readme-index (= 0.0.3)
-  jekyll-redirect-from (~> 0.13)
-  jekyll-relative-links (~> 0.2)
-  jekyll-seo-tag
-  jekyll-sitemap
-  jekyll-swiss (~> 0.4)
-  jekyll-theme-architect (= 0.0.3)
-  jekyll-theme-cayman (= 0.0.3)
-  jekyll-theme-dinky (= 0.0.3)
-  jekyll-theme-hacker (= 0.0.3)
-  jekyll-theme-leap-day (= 0.0.3)
-  jekyll-theme-merlot (= 0.0.3)
-  jekyll-theme-midnight (= 0.0.3)
-  jekyll-theme-minimal (= 0.0.3)
-  jekyll-theme-modernist (= 0.0.3)
-  jekyll-theme-primer (~> 0.1)
-  jekyll-theme-slate (= 0.0.3)
-  jekyll-theme-tactile (= 0.0.3)
-  jekyll-theme-time-machine (= 0.0.3)
-  jekyll-titles-from-headings (~> 0.1)
-  jekyll-youtube (~> 1.0)
-  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.16.1

Makefile

@@ -1,18 +1,58 @@
-.PHONY: all build build-preview help serve
+DOCKER       = docker
+HUGO_VERSION = 0.57.2
+DOCKER_IMAGE = kubernetes-hugo
+DOCKER_RUN   = $(DOCKER) run --rm --interactive --tty --volume $(CURDIR):/src
+NODE_BIN     = node_modules/.bin
+NETLIFY_FUNC = $(NODE_BIN)/netlify-lambda
+
+.PHONY: all build sass build-preview help serve
 
 help: ## Show this help.
 	@awk 'BEGIN {FS = ":.*?## "} /^[a-zA-Z_-]+:.*?## / {sub("\\\\n",sprintf("\n%22c"," "), $$2);printf "\033[36m%-20s\033[0m %s\n", $$1, $$2}' $(MAKEFILE_LIST)
 
-all: build ## Build site with production settings and put deliverables in _site.
+all: build ## Build site with production settings and put deliverables in ./public
 
-build: ## Build site with production settings and put deliverables in _site.
-	bundle exec jekyll build
+build: ## Build site with production settings and put deliverables in ./public
+	hugo --minify
 
-build-preview: ## Build site with drafts and future posts enabled.
-	bundle exec jekyll build --drafts --future --trace
+build-preview: ## Build site with drafts and future posts enabled
+	hugo --buildDrafts --buildFuture
+
+functions-build:
+	$(NETLIFY_FUNC) build functions-src
+
+check-headers-file:
+	scripts/check-headers-file.sh
+
+production-build: check-hugo-versions build check-headers-file ## Build the production site and ensure that noindex headers aren't added
+
+non-production-build: check-hugo-versions ## Build the non-production site, which adds noindex headers to prevent indexing
+	hugo --enableGitInfo
+
+sass-build:
+	scripts/sass.sh build
+
+sass-develop:
+	scripts/sass.sh develop
 
 serve: ## Boot the development server.
-	bundle exec jekyll serve
+	hugo server --buildFuture
 
-stage: ## Run the Jekyll staging container.
-	docker run -ti --rm -v "${PWD}":/k8sdocs -p 4000:4000 gcr.io/google-samples/k8sdocs:1.1
+docker-image:
+	$(DOCKER) build . --tag $(DOCKER_IMAGE) --build-arg HUGO_VERSION=$(HUGO_VERSION)
+
+docker-build:
+	$(DOCKER_RUN) $(DOCKER_IMAGE) hugo
+
+docker-serve:
+	$(DOCKER_RUN) -p 1313:1313 $(DOCKER_IMAGE) hugo server --buildFuture --bind 0.0.0.0
+
+# This command is used only by Travis CI; do not run this locally
+travis-hugo-build:
+	curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_${HUGO_VERSION}_linux-64bit.tar.gz | tar -xz
+	mkdir -p ${TRAVIS_HOME}/bin
+	mv hugo ${TRAVIS_HOME}/bin
+	export PATH=${TRAVIS_HOME}/bin:$PATH
+
+check-hugo-versions:
+	scripts/hugo-version-check.sh $(HUGO_VERSION)

OWNERS

@@ -1,12 +1,10 @@
+# See the OWNERS docs at https://go.k8s.io/owners
+
 reviewers:
-- tengqm
-- zhangxiaoyu-zidif
-- xiangpengzhao
-- bradtopol
+- sig-docs-en-reviews # Defined in OWNERS_ALIASES
+
 approvers:
-- heckj
-- bradamant3
-- bradtopol
-- steveperry-53
-- zacharysarah
-- chenopis
+- sig-docs-en-owners # Defined in OWNERS_ALIASES
+
+labels:
+- sig/docs

OWNERS_ALIASES

@@ -1,204 +1,137 @@
 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
-    - jbeda
+  sig-cluster-lifecycle-kubeadm-approvers: # Approving changes to kubeadm documentation
     - timothysc
     - lukemarsden
-    - pipejakob
-    - dmmcquay
-    - mattmoyer
     - luxas
     - roberthbailey
-    - medinatiger
-  sig-cluster-ops:
-    - zehicle
-    - jdumars
-  sig-contribex: #aka Contributor Experience; GH: sig-contributor-experience-pr-reviews
-    - rmmh
-    - cblecker
-    - apelisse
-    - grodrigues3
-    - spxtr
-  sig-contributor-experience: #GH: sig-contributor-experience-pr-reviews
-    - rmmh
-    - cblecker
-    - apelisse
-    - grodrigues3
-    - spxtr
-  sig-docs: #Team: documentation; GH: sig-docs-pr-reviews
-    - bradamant3
-    - steveperry-53
-    - zacharysarah
-    - bradtopol
-    - heckj
-  sig-federation: #Team: Federation; e.g. Federated Clusters
-    - csbell
-  sig-gcp: #Google Cloud Platform; GH: sig-gcp-pr-reviews
-    - abgworrall
-  sig-instrumentation: #GH: sig-instrumentation-pr-reviews; e.g. metrics, logging, events
-    - DirectXMan12
-    - x13n
-    - kawych
-    - 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
+    - fabriziopandini
+  sig-cluster-lifecycle-kubeadm-reviewers: # Reviewing kubeadm documentation
     - timothysc
-    - wojtek-t
-  sig-service-catalog: #GH: sig-service-catalog-pr-reviews; e.g. Service Broker
-    - pmorie
-    - jessfraz
+    - lukemarsden
+    - luxas
+    - roberthbailey
+    - fabriziopandini
+    - kad
+    - xiangpengzhao
+    - stealthybox
+    - liztio
+    - chuckha
+    - detiber
+    - dixudx
+  sig-docs-en-owners: # Admins for English content
+    - bradamant3
+    - bradtopol
+    - chenopis
+    - cody-clark
+    - jaredbhatti
+    - jimangel
+    - kbarnard10
+    - mistyhacks
+    - rajakavitha1
+    - ryanmcginnis
+    - steveperry-53
+    - stewart-yu
+    - tengqm
+    - tfogo
+    - zacharysarah
+    - zhangxiaoyu-zidif
+    - zparnold
+  sig-docs-en-reviews: # PR reviews for English content
+    - jimangel
+    - rajakavitha1
+    - stewart-yu
+    - xiangpengzhao
+    - zhangxiaoyu-zidif
+  sig-docs-fr-owners: # Admins for French content
+    - sieben
+    - perriea
+    - rekcah78
+    - lledru
+    - yastij
+    - smana
+    - rbenzair
+    - abuisine
+    - erickhun
+    - jygastaud
+    - awkif
+    - oussemos
+  sig-docs-fr-reviews: # PR reviews for French content
+    - sieben
+    - perriea
+    - rekcah78
+    - lledru
+    - yastij
+    - smana
+    - rbenzair
+    - abuisine
+    - erickhun
+    - jygastaud
+    - awkif
+    - oussemos
+  sig-docs-it-owners: # Admins for Italian content
+    - rlenferink
+    - lledru
+    - micheleberardi
+  sig-docs-it-reviews: # PR reviews for Italian content
+    - rlenferink
+    - lledru
+    - micheleberardi
+  sig-docs-ja-owners: # Admins for Japanese content 
+    - cstoku
+    - nasa9084
+    - tnir
+    - zacharysarah
+  sig-docs-ja-reviews: # PR reviews for Italian content 
+    - cstoku
+    - makocchi-git
+    - MasayaAoyama
+    - nasa9084
+    - tnir
+  sig-docs-ko-owners: # Admins for Korean content
+    - ClaudiaJKang
+    - gochist
+    - ianychoi
+    - zacharysarah
+  sig-docs-ko-reviews: # PR reviews for Korean content
+    - ClaudiaJKang
+    - gochist
+    - ianychoi
+  sig-docs-maintainers: # Website maintainers
+    - bradamant3
+    - chenopis
+    - jaredbhatti
+    - jimangel
+    - kbarnard10
+    - mistyhacks
     - pwittrock
-    - 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
+    - steveperry-53
+    - tengqm
+    - zacharysarah
+    - zparnold
+  sig-docs-zh-owners: # Admins for Chinese content
+    - bradtopol
+    - chenopis
+    - chenrui333
+    - dchen1107
+    - haibinxie
+    - hanjiayao
+    - lichuqiang
+    - lucperkins
+    - markthink
+    - SataQiu
+    - tengqm
+    - xiangpengzhao
+    - xichengliudui
+    - zacharysarah
+    - zhangxiaoyu-zidif
+  sig-docs-zh-reviews: # PR reviews for Chinese content
+    - chenrui333
+    - idealhack
+    - markthink
+    - SataQiu
+    - tengqm
+    - xiangpengzhao
+    - xichengliudui
+    - zhangxiaoyu-zidif
+    - pigletfly
+  

README-fr.md

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

README-ko.md

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

README.md

@@ -1,22 +1,82 @@
-## Instructions for Contributing to the Kubernetes Documentation
+# The Kubernetes documentation
 
-Welcome! We are very pleased you want to contribute to the Kubernetes documentation.
+[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website)
+[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest)
 
-You can click the **Fork** button in the upper-right area of the screen to create a copy of this repository in your GitHub account called a *fork*. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.
+Welcome! This repository houses all of the assets required to build the [Kubernetes website and documentation](https://kubernetes.io/). We're very pleased that you want to contribute!
+
+## Contributing to the docs
+
+You can click the **Fork** button in the upper-right area of the screen to create a copy of this repository in your GitHub account. This copy is called a *fork*. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.
 
 Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback.  As the owner of the pull request, **it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer.**  Also note that you may end up having more than one Kubernetes reviewer provide you feedback or you may end up getting feedback from a Kubernetes reviewer that is different than the one originally assigned to provide you feedback. Furthermore, in some cases, one of your reviewers might ask for a technical review from a [Kubernetes tech reviewer](https://github.com/kubernetes/website/wiki/Tech-reviewers) when needed.  Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances.
 
 For more information about contributing to the Kubernetes documentation, see:
 
-* [Contributing to the Kubernetes Documentation](http://kubernetes.io/editdocs/)
-* [Creating a Documentation Pull Request](http://kubernetes.io/docs/home/contribute/create-pull-request/)
-* [Writing a New Topic](http://kubernetes.io/docs/home/contribute/write-new-topic/)
-* [Review Issues](http://kubernetes.io/docs/home/contribute/review-issues/)
-* [Staging Your Documentation Changes](http://kubernetes.io/docs/home/contribute/stage-documentation-changes/)
-* [Using Page Templates](http://kubernetes.io/docs/home/contribute/page-templates/)
-* [Documentation Style Guide](http://kubernetes.io/docs/home/contribute/style-guide/)
+* [Start contributing](https://kubernetes.io/docs/contribute/start/)
+* [Staging Your Documentation Changes](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally)
+* [Using Page Templates](http://kubernetes.io/docs/contribute/style/page-templates/)
+* [Documentation Style Guide](http://kubernetes.io/docs/contribute/style/style-guide/)
+* [Localizing Kubernetes Documentation](https://kubernetes.io/docs/contribute/localization/)
+
+## `README.md`'s Localizing Kubernetes Documentation
+
+### Korean
+
+See translation of `README.md` and more detail guidance for Korean contributors on the [Korean README](README-ko.md) page.
+
+You can reach the maintainers of Korean localization at:
+
+* June Yi ([GitHub - @gochist](https://github.com/gochist))
+* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-ko)
+
+## Running the site locally using Docker
+
+The recommended way to run the Kubernetes website locally is to run a specialized [Docker](https://docker.com) image that includes the [Hugo](https://gohugo.io) static site generator.
+
+> If you are running on Windows, you'll need a few more tools which you can install with [Chocolatey](https://chocolatey.org). `choco install make`
+
+> If you'd prefer to run the website locally without Docker, see [Running the site locally using Hugo](#running-the-site-locally-using-hugo) below.
+
+If you have Docker [up and running](https://www.docker.com/get-started), build the `kubernetes-hugo` Docker image locally:
+
+```bash
+make docker-image
+```
+
+Once the image has been built, you can run the site locally:
+
+```bash
+make docker-serve
+```
+
+Open up your browser to http://localhost:1313 to view the site. As you make changes to the source files, Hugo updates the site and forces a browser refresh.
+
+## Running the site locally using Hugo
+
+See the [official Hugo documentation](https://gohugo.io/getting-started/installing/) for Hugo installation instructions. Make sure to install the Hugo version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L9) file.
+
+To run the site locally when you have Hugo installed:
+
+```bash
+make serve
+```
+
+This will start the local Hugo server on port 1313. Open up your browser to http://localhost:1313 to view the site. As you make changes to the source files, Hugo updates the site and forces a browser refresh.
+
+## Community, discussion, contribution, and support
+
+Learn how to engage with the Kubernetes community on the [community page](http://kubernetes.io/community/).
+
+You can reach the maintainers of this project at:
+
+- [Slack](https://kubernetes.slack.com/messages/sig-docs)
+- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)
+
+### Code of conduct
+
+Participation in the Kubernetes community is governed by the [Kubernetes Code of Conduct](code-of-conduct.md).
 
 ## Thank you!
 
-Kubernetes thrives on community participation, and we really appreciate your
-contributions to our site and our documentation!
+Kubernetes thrives on community participation, and we really appreciate your contributions to our site and our documentation!

SECURITY_CONTACTS

@@ -0,0 +1,15 @@
+# Defined below are the security contacts for this repo.
+#
+# They are the contact point for the Product Security Committee to reach out
+# to for triaging and handling of incoming issues.
+#
+# The below names agree to abide by the
+# [Embargo Policy](https://git.k8s.io/security/private-distributors-list.md#embargo-policy)
+# and will be removed and replaced if they violate that agreement.
+#
+# DO NOT REPORT SECURITY VULNERABILITIES DIRECTLY TO THESE NAMES, FOLLOW THE
+# INSTRUCTIONS AT https://kubernetes.io/security/
+
+chenopis
+bradamant3
+zacharysarah

_config.yml

@@ -1,99 +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
-
-latest: "v1.10"
-
-paginate: 7
-paginate_path: "/blog/page:num/"
-
-defaults:
-  -
-    scope:
-      path: ""
-    values:
-      fullversion: "v1.10.0"
-      version: "v1.10"
-      githubbranch: "master"
-      docsbranch: "master"
-      versions:
-        - fullversion: "v1.10.0"
-          version: "v1.10"
-          githubbranch: "v1.10.0"
-          docsbranch: "release-1.10"
-          url: https://kubernetes.io
-        - fullversion: "v1.9.0"
-          version: "v1.9"
-          githubbranch: "v1.9.0"
-          docsbranch: "release-1.9"
-          url: https://v1-9.docs.kubernetes.io
-        - fullversion: "v1.8.4"
-          version: "v1.8"
-          githubbranch: "v1.8.4"
-          docsbranch: "release-1.8"
-          url: https://v1-8.docs.kubernetes.io
-        - fullversion: "v1.7.6"
-          version: "v1.7"
-          githubbranch: "v1.7.6"
-          docsbranch: "release-1.7"
-          url: https://v1-7.docs.kubernetes.io
-        - fullversion: "v1.6.8"
-          version: "v1.6"
-          githubbranch: "v1.6.8"
-          docsbranch: "release-1.6"
-          url: https://v1-6.docs.kubernetes.io
-      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
-  - jekyll-paginate
-  - jekyll-youtube
-# disabled gems
-#  - jekyll-redirect-from
-
-include: [_redirects,_headers]
-
-# SEO
-logo: /images/favicon.png
-twitter:
-  username: kubernetesio
-
-# empty array for tabs
-emptyArray: []
-
-# Tables of contents, stored in the _data folder, that control the sidebar nav
-tocs:
-  - docs-home
-  - setup
-  - tasks
-  - tutorials
-  - concepts
-  - reference
-  - samples
-  - search
-  - imported
-  - blog

_data/glossary/_example.yml

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

_data/glossary/annotation.yaml

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

_data/glossary/application-architect.yaml

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

_data/glossary/application-developer.yaml

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

_data/glossary/approver.yaml

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

_data/glossary/certificate.yaml

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

_data/glossary/cla.yaml

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

_data/glossary/cloud-controller-manager.yml

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

_data/glossary/cloud-provider.yaml

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

_data/glossary/cluster-architect.yaml

@@ -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: high availability and security.

_data/glossary/cluster-operator.yaml

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

_data/glossary/cluster.yaml

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

_data/glossary/code-contributor.yaml

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

_data/glossary/configmap.yaml

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

_data/glossary/container-env-variables.yaml

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

_data/glossary/container.yaml

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

_data/glossary/contributor.yaml

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

_data/glossary/controller.yaml

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

_data/glossary/cronjob.yaml

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

_data/glossary/customresourcedefinition.yaml

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

_data/glossary/daemonset.yaml

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

_data/glossary/deployment.yaml

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

_data/glossary/developer.yaml

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

_data/glossary/docker.yaml

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

_data/glossary/downstream.yaml

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

_data/glossary/dynamic-volume-provisioning.yaml

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

_data/glossary/etcd.yaml

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

_data/glossary/helm-chart.yaml

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

_data/glossary/horizontal-pod-autoscaler.yaml

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

_data/glossary/image.yaml

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

_data/glossary/ingress.yaml

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

_data/glossary/init-container.yaml

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

_data/glossary/istio.yaml

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

_data/glossary/job.yaml

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

_data/glossary/kops.yaml

@@ -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: Officially supports AWS only, with GCE and VMware vSphere in alpha*.
-long-description: |
-  `kops` provisions your cluster with:
-
-    * Fully automated installation
-    * DNS-based cluster identification
-    * Self-healing: everything runs in Auto-Scaling Groups
-    * Limited OS support (Debian preferred, Ubuntu 16.04 supported, early support for CentOS & RHEL)
-    * High availability (HA) support
-    * The ability to directly provision, or generate terraform manifests
-
-  You can also build your own cluster using {% glossary_tooltip term_id="kubeadm" %} as a building block. `kops` builds on the kubeadm work.

_data/glossary/kube-apiserver.yaml

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

_data/glossary/kube-controller-manager.yaml

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

_data/glossary/kube-proxy.yaml

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

_data/glossary/kube-scheduler.yaml

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

_data/glossary/kubeadm.yaml

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

_data/glossary/kubectl.yaml

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

_data/glossary/kubelet.yaml

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

_data/glossary/kubernetes-api.yaml

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

_data/glossary/label.yaml

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

_data/glossary/maintainer.yaml

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

_data/glossary/managed-service.yaml

@@ -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" %}.

_data/glossary/member.yaml

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

_data/glossary/minikube.yaml

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

_data/glossary/name.yaml

@@ -1,10 +0,0 @@
-id: name
-name: Name
-full-link: /docs/concepts/overview/working-with-objects/names
-tags:
-  - fundamental
-short-description: >
-  A client-provided string that refers to an object in a resource URL, such as `/api/v1/pods/some-name`.
-long-description: >
-  Only one object of a given kind can have a given name at a time.
-  However, if you delete the object, you can make a new object with the same name.

_data/glossary/namespace.yaml

@@ -1,10 +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 multiple virtual clusters on the same physical {% glossary_tooltip text="cluster" 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.

_data/glossary/network-policy.yaml

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

_data/glossary/node.yaml

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

_data/glossary/persistent-volume-claim.yaml

@@ -1,15 +0,0 @@
-id: persistent-volume-claim
-name: Persistent Volume Claim
-full-link: /docs/concepts/storage/persistent-volumes/
-related:
-- persistent-volume
-- statefulset
-- deployment
-- pod
-tags:
-- core-object
-- storage
-short-description: >
-  Claims storage resources defined in a PersistentVolume so that it can be mounted as a volume in a container.
-long-description: |
-  Specifies the amount of storage, how the storage will be accessed (read-only, read-write and/or exclusive) and how it is reclaimed (retained, recycled or deleted). Details of the storage itself are in the PersistentVolume specification.

_data/glossary/persistent-volume.yaml

@@ -1,17 +0,0 @@
-id: persistent-volume
-name: Persistent Volume
-full-link: /docs/concepts/storage/persistent-volumes/
-related:
-- statefulset
-- deployment
-- persistent-volume-claim
-- pod
-tags:
-- core-object
-- storage
-short-description: >
-  An API object that represents a piece of storage in the cluster. Available as a general, pluggable resource that persists beyond the lifecycle of any individual {% glossary_tooltip text="Pod" term_id="pod" %}.
-long-description: |
-  PersistentVolumes (PVs) provide an API that abstracts details of how storage is provided from how it is consumed.
-  PVs are used directly in scenarios where storage can be created ahead of time (static provisioning).
-  For scenarios that require on-demand storage (dynamic provisioning), PersistentVolumeClaims (PVCs) are used instead.

_data/glossary/platform-developer.yaml

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

_data/glossary/pod-security-policy.yaml

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

_data/glossary/pod.yaml

@@ -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" %}.

_data/glossary/podpreset.yaml

@@ -1,12 +0,0 @@
-id: podpreset
-name: PodPreset
-tags:
-- operation
-short-description: >
-  An API object that injects information such as secrets, volume mounts,
-  and environment variables into pods at creation time.
-long-description: >
-  This object chooses the pods to inject information into using
-  standard selectors. This allows the podspec definitions to be
-  nonspecific, decoupling the podspec from environment specific
-  configuration.

_data/glossary/rbac.yaml

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

_data/glossary/replica-set.yml

@@ -1,14 +0,0 @@
-id: replica-set
-name: ReplicaSet
-full-link: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
-related:
-- replication-controller
-tags:
-- fundamental
-- core-object
-- workload
-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.

_data/glossary/replication-controller.yaml

@@ -1,10 +0,0 @@
-id: replication-controller
-name: Replication Controller
-tags:
-- workload
-- core-object
-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.
-

_data/glossary/resource-quota.yaml

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

_data/glossary/reviewer.yaml

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

_data/glossary/secret.yml

@@ -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/configure-pod-configmap/) for non-confidential data.

_data/glossary/security-context.yaml

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

_data/glossary/selector.yaml

@@ -1,13 +0,0 @@
-id: selector
-name: Selector
-full-link: /docs/concepts/overview/working-with-objects/labels/
-related:
-- label
-tags:
-- fundamental
-short-description: >
-  Allows users to filter a list of resources based on labels.
-long-description: >
-  Selectors are applied when querying lists of resources to filter
-  them by {% glossary_tooltip text="Labels" term_id="label"
-  %}.

_data/glossary/service-account.yaml

@@ -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 {% glossary_tooltip text="Pod" 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" %}.

_data/glossary/service-broker.yaml

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

_data/glossary/service-catalog.yaml

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

_data/glossary/service.yaml

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

_data/glossary/sig.yaml

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

_data/glossary/statefulset.yml

@@ -1,17 +0,0 @@
-id: statefulset
-name: StatefulSet
-full-link: /docs/concepts/workloads/controllers/statefulset/
-related:
-- deployment
-- pod
-tags:
-- fundamental
-- 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: 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.

_data/glossary/storage-class.yaml

@@ -1,11 +0,0 @@
-id: storageclass
-name: Storage Class
-full-link: /docs/concepts/storage/storage-classes
-tags:
-- core-object
-- storage
-short-description: >
-  A StorageClass provides a way for administrators to describe different available storage types.
-long-description: >
-  StorageClasses can map to quality-of-service levels, backup policies, or to arbitrary policies determined by cluster administrators.
-  Each StorageClass contains the fields `provisioner`, `parameters`, and `reclaimPolicy`, which are used when a {% glossary_tooltip text="Persistent Volume" term_id="persistent-volume" %} belonging to the class needs to be dynamically provisioned. Users can request a particular class using the name of a StorageClass object.

_data/glossary/uid.yaml

@@ -1,10 +0,0 @@
-id: uid
-name: UID
-full-link: /docs/concepts/overview/working-with-objects/names
-tags:
-  - fundamental
-short-description: >
-  A Kubernetes systems-generated string to uniquely identify objects.
-long-description: >
-  Every object created over the whole lifetime of a Kubernetes cluster has a distinct UID.
-  It is intended to distinguish between historical occurrences of similar entities.

_data/glossary/upstream.yaml

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

_data/glossary/volume-plugin.yaml

@@ -1,11 +0,0 @@
-id: volumeplugin
-name: Volume Plugin
-tags:
-- core-object
-- storage
-short-description: >
-  A Volume Plugin enables integration of storage within a {% glossary_tooltip text="Pod" term_id="pod" %}.
-long-description: >
-  A Volume Plugin lets you attach and mount storage volumes for use by a {% glossary_tooltip text="Pod" term_id="pod" %}.
-  Volume plugins can be _in tree_ or _out of tree_. _In tree_ plugins are part of the Kubernetes code repository and follow its release cycle. _Out of tree_ plugins are developed independently.
-

_data/glossary/volume.yaml

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

_data/glossary/wg.yaml

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

_data/imported.yml

@@ -1,11 +0,0 @@
-bigheader: "Imported Docs"
-abstract: "Docs imported from other Kubernetes SIGs and repos."
-toc:
-- docs/imported/index.md
-
-- title: Community
-  section:
-  - docs/imported/community/guide.md
-  - docs/imported/community/devel.md
-  - docs/imported/community/mentoring.md
-  - docs/imported/community/keps.md

_data/user-personas/contributors/code-contributor.yaml

@@ -1,19 +0,0 @@
-id: code-contributor
-name: Code Contributor
-glossary_id: code-contributor
-index: 0
-foundational:
-  - label: "Read the Developer Guide"
-    icon: fa-book
-    url: "/docs/imported/community/devel/"
-intermediate:
-  - label: "Learn about the Kubernetes Enhancement Proposal (KEP) process"
-    icon: fa-upload
-    url: "/docs/imported/community/keps/"
-  - label: "Understand the API conventions"
-    icon: fa-map-o
-    url: "https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md"
-advanced:
-  - label: "Learn about the release process"
-    icon: fa-code-fork
-    url: "https://github.com/kubernetes/release/blob/master/README.md"

_includes/CommunityHangout/Apr3.html

@@ -1,227 +0,0 @@
-<div>
-<span style="font-family: Open Sans;"><span style="font-size: 13px; line-height: 17.9400005340576px; white-space: pre-wrap;"><br /></span></span></div>
-<div>
-<span style="font-family: 'Open Sans'; font-size: 13px; line-height: 17.9400005340576px; white-space: pre-wrap;">Every week the Kubernetes contributing community meet virtually over Google Hangouts. We want anyone who's interested to know what's discussed in this forum.</span></div>
-<div>
-<span style="font-family: 'Open Sans'; font-size: 13px; line-height: 17.9400005340576px; white-space: pre-wrap;"><br /></span></div>
-<div>
-<span style="font-family: Open Sans;"><span style="font-size: 13px; line-height: 17.9400005340576px; white-space: pre-wrap;">Agenda:</span></span></div>
-<ul style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: disc; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Quinton - Cluster federation</span></div>
-</li>
-<ul style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: Arial; font-size: 15px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 15px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">doc: </span><a href="http://tinyurl.com/ubernetes" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 15px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">http://tinyurl.com/ubernetes</span></a></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: Arial; font-size: 15px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<a href="https://docs.google.com/presentation/d/1dWKNzjYM6ZYjFXpPwamikC6_BV3PDe33NAK9zR_M7jg/edit?usp=sharing" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 15px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">slides</span></a></div>
-</li>
-</ul>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: disc; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Satnam - Performance benchmarking update</span></div>
-</li>
-</ul>
-<b id="docs-internal-guid-ae742fb5-80cb-c8b0-6fc8-e1dc4853480c" style="font-weight: normal;"><br /></b>
-<div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Notes from meeting:</span></div>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Quinton - Cluster federation</span></div>
-</li>
-<ul style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Ideas floating around after meetup in SF</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Document: </span><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 15px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">doc: </span><a href="http://tinyurl.com/ubernetes" style="text-decoration: none;"><span style="background-color: transparent; color: #1155cc; font-family: Arial; font-size: 15px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: underline; vertical-align: baseline; white-space: pre-wrap;">http://tinyurl.com/ubernetes</span></a></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Please read and comment</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Not 1.0, but put a doc together to show roadmap</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Can be built outside of Kubernetes</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">API to control things across multiple clusters, include some logic</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Auth(n)(z)</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Scheduling Policies</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">&#8230;</span></div>
-</li>
-</ol>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Different reasons for cluster federation</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Zone (un) availability : Resilient to zone failures</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Hybrid cloud: some in cloud, some on prem. for various reasons</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Avoid cloud provider lock-in. &nbsp;For various reasons</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">&#8220;Cloudbursting&#8221; - automatic overflow into the cloud</span></div>
-</li>
-</ol>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Hard problems</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Location affinity. &nbsp;How close do pods need to be? </span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Workload coupling</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Absolute location (e.g. eu data needs to be in eu)</span></div>
-</li>
-</ol>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Cross cluster service discovery</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">How does service/DNS work across clusters</span></div>
-</li>
-</ol>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Cross cluster workload migration</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">How do you move an application piece by piece across clusters?</span></div>
-</li>
-</ol>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Cross cluster scheduling</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">How do know enough about clusters to know where to schedule</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Possibly use a cost function to achieve affinities with minimal complexity</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Can also use cost to determine where to schedule (under used clusters are cheaper than over-used clusters)</span></div>
-</li>
-</ol>
-</ol>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Implicit requirements</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Cross cluster integration shouldn&#8217;t create cross-cluster failure modes</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Independently usable in a disaster situation where Ubernetes dies.</span></div>
-</li>
-</ol>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Unified visibility</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Want to have unified monitoring, alerting, logging, introspection, ux, etc.</span></div>
-</li>
-</ol>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Unified quota and identity management</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Want to have user database and auth(n)/(z) in a single place</span></div>
-</li>
-</ol>
-</ol>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Important to note, most causes of software failure are not the infrastructure</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Botched software upgrades</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Botched config upgrades</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Botched key distribution</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Overload</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Failed external dependencies</span></div>
-</li>
-</ol>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Discussion:</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Where do you draw the &#8220;ubernetes&#8221; line</span></div>
-</li>
-<ol style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Likely at the availability zone, but could be at the rack, or the region</span></div>
-</li>
-</ol>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: lower-roman; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Important to not pigeon hole and prevent other users</span></div>
-</li>
-</ol>
-</ul>
-</ol>
-<br />
-<ol start="2" style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Satnam - Soak Test</span></div>
-</li>
-<ul style="margin-bottom: 0pt; margin-top: 0pt;">
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Want to measure things that run for a long time to make sure that the cluster is stable over time. &nbsp;Performance doesn&#8217;t degrade, no memory leaks, etc.</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">github.com/GoogleCloudPlatform/kubernetes/test/soak/&#8230;</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Single binary, puts lots of pods on each node, and queries each pod to make sure that it is running.</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Pods are being created much, much more quickly (even in the past week) to make things go more quickly.</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Once the pods are up running, we hit the pods via the proxy. &nbsp;Decision to hit the proxy was deliberate so that we test the kubernetes apiserver.</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Code is already checked in.</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Pin pods to each node, exercise every pod, make sure that you get a response for each node.</span></div>
-</li>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: circle; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Single binary, run forever.</span></div>
-</li>
-</ul>
-<li dir="ltr" style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; list-style-type: decimal; text-decoration: none; vertical-align: baseline;"><div dir="ltr" style="line-height: 1.38; margin-bottom: 0pt; margin-top: 0pt;">
-<span style="background-color: transparent; color: black; font-family: 'Open Sans'; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">Brian - v1beta3 is enabled by default, v1beta1 and v1beta2 deprecated, turned off &nbsp;in June. &nbsp;Should still work with upgrading existing clusters, etc.</span></div>
-</li>
-</ol>
-<div style='clear: both;'></div>