Update 1.12 from Master (#9693)

* Syntax fixes for Cassandra doc

* Fix indentation issues

* convert unnecessary note admonition to normal text

* Modify Resource Types section in kubectl cheat sheet

* Fix error in command syntax

* Change header level

* Change code block type to bash from console

* Add me to the OWNERS file (#9511)

* Revert "Add me to the OWNERS file (#9511)" (#9512)

This reverts commit fe9d5b6.

* Adds ryanmcginnis to OWNERS (#9513)

* Fix NetworkPolicy api link (#9427)

* Document CustomResourceDefinition additionalPrinterColumns (#9143)

* Add Kubernetes 1.11 release manager interview (#9496)

* Add Kubernetes 1.11 release manager interview

* fix typo

* add Adam's surname

* apply suggested fixes

* apply suggested fixes

* apply suggested fixes

* apply suggested fixes

* Fix broken link in note (#9535)

* Add descripitons of --service-account-max-token-expiration option (#9500)

* fix relative link and remove redirect link (#9468)

* Update device-plugins.md to add Example link (#9531)

Added link to Intel device plugins repo. 
Minor grammar/punctuation edits to make Example bullets parallel.

* removed backtick that was breaking the format (#9530)

* Fix `--allow-privileged` and `--alsologtostderr` descriptions (#9507)

* Update pull-image-private-registry.md (#9153)

`-d` does not work on mac, `--decode` should work cross platform

* Remove download steps (#9494)

* Fix:direct link in tasks/configure-pod-container/translate-compose-kubernetes (#9369)

* change direct link to relative link

* Update translate-compose-kubernetes.md

* Add another Lisp client library (#8994)

* Update extensible-admission-controllers.md (#8975)

* Update extensible-admission-controllers.md

* update per review comments

update the url to the final redirect to url.

* Update k8s101.md (#9043)

* Fix some notes for Azure users (#9159)

* Fix some notes for Azure users

As is said in the docs (https://docs.microsoft.com/en-us/azure/aks/static-ip#create-static-ip-address), it must be the cluster node's resource group, not the cluster's resource group.

* A few minor changes to adhere to the style guide

* Format the auto-generate list(catalog) and update the render style (#9069)

* fix some broken link in /docs/setup (#9256)

* Fixed broken Link to Salt setup documentation (#9264)

* set anchor links in "Types of Volumes" section (#9294)

* Fix a typo in running cloud controller doc (#9325)

* Update manage-compute-resources-container.md (#9326)

Fix formatting that is thrown off by starting at "```shell{% raw %}"

* Update training overview (#9378)

Added Pluralsight getting started course

* update homepage banner so it's less cropped (#9391)

* Format code style (#9055)

* Add code format

* Format code display

* Render style error

* apply content_template (#9136)

* apply task template

* change content_template to task from concept

* very minor change to url syntax (#9543)

The URL for k/k included the text after ("repo"). This PR formats it to not include the text after.

* Reworked API reference doc (#9536)

This PR contains API reference docs generated from the reworked
generator (see:
kubernetes-sigs/reference-docs#53).
The main purpose is to rework the way how examples are shown.
When we are happy with the revised version, we can move the CSS and
fonts file to the static directory. We only need to change the HTML
and the `navData.js` file in the future.

Related Issues: #9271, #4015

* Fix typo in persistent-volumes.md (#9550)

* Fix id string for kube-proxy glossary term (#9551)

-Added hyphen to id string so that glossary term displays
extension text.

* Update horizontal-pod-autoscale.md (#9546)

Small typo. Missing "from" for sentence to make sense.

* Update feature-gates.md (#9320)

* Replacing the example IP address by something that could exists. (#9120)

The example `123.45.678.9` was an invalid IP address.

* Fix doc (#9564)

Added line break to: "KUBECONFIG=/etc/kubernetes/admin.conf [NEWLINE HERE] kubectl ..."; Also added export to variables declaration.

* Update service.md (#9562)

I think the writer means "reuse" here instead of "replace". Since the idea behind choosing your own IP is to avoid having to make any changes to the DNS.

* Add when storage key name changed (#9532)

It seems the name changed in k8s 1.8 which was reflected in #5490 but the last section still mentions the old name without saying it has changed.

* Fix issues in configure-volume-storage (#9521)

* ps command not found

Signed-off-by: Jamie Zhuang <lanchongyizu@gmail.com>

* change to "host namespaces" and remove command prompts (#9553)

* changing button spacing (#8963)

* Fix link to website in Airflow Blogpost (#9338)

* Blog: 11 Ways (Not) to Get Hacked (#8914)

* feat: add 11 Ways (Not) to Get Hacked

* Update and rename 2018-06-05-11-ways-not-to-get-hacked.md to 2018-07-18-11-ways-not-to-get-hacked.md

* updates to Pearson case study content (#9483)

* updates to Pearson case study content

* updates to Pearson

* apply templates/concept and fix code snippets (#9540)

* updates to order of case studies (#9545)

* updates to order of case studies

* update

* fix some dumplication_problem (#9235)

* Update extensible admission controller links (#9459)

* update extensible-admission-controller links

* correct what-are-initializers link

* Add kublr to list of solutions (#9544)

* statefulset.md - Beta remnants removed (#9522)

* Fix some error about fluentd config file (#9528)

1.Fix error about source path is not equal to autdit-log-path
2.Fix error about filter type set

Signed-off-by: pengdake <19921207pq@gmail.com>

* Fix type in docs (#8939)

* Fix type in docs

* Address code review comments.

* Update authentication.md (#9565)

minor grammar correction

* Fix doc references to Kubernetes services provided by AWS, Azure and GCE (#9508)

* update authorization-node links (#9462)

* include supported version skew (#9501)

* Update create-pull-request.md (#9488)

Remove link to stage-documentation-change. 
(@misty says: The old page doesn't exist anymore and is now redirected to the current page.)

* Update authorization links (#9465)

* update authorization links

* remove cn content and fix link targets

* update bootstrap-token links (#9456)

* Make macOS standard usage (#9422)

* Add note for fluentd plugin installation (#9451)

* Add note for fluentd plugin installation

Fluentd plugin installation is different from fluentd installation,
so we need to tell user how to solve it.

Signed-off-by: pengdake <19921207pq@gmail.com>

* add space in note

* add period

* Add guide for getting token and discovery-token-ca-cert-hash (#9017)

* Add guide for getting token and discovery-token-ca-cert-hash

* Fix code snippet style

* apply content template (#9232)

* Environment variable for etcd quorum is singular (#9302)

See
https://github.com/kubernetes/kubernetes/blob/f8c4907bec4fcb7d86d955c06b9c362b61e58933/cluster/gce/config-default.sh#L109

* Drop {% raw %} block in manage-compute-resources-container (#9428)

This was breaking rendering the end of the page.

* Fixes to example for connecting with curl (#9337)

* Fixes to example for connecting with curl

Example for getting cluster token
- does not work with multiple entries in kubeconfig
- does not work with Istio installed

Fix both

* also need to change the tr from tabs to spaces

* Fix the semantically very broken search box (#9408)

This was very annoyingly very broken. *Very* broken.

Two primary issues:

1. Autofocus. Autofocus should only be used on a field when it is the
   expected action on the page, because it steals keyboard events such
   as the arrow keys and Space for navigation, and causes users of
   screen readers confusion as they’re thrown into a strange place.

   It’d be just barely OK to use it on search pages, but used on
   *every* page in the documentation, it’s just *super* annoying.

2. Not being a form. I have *no* idea why anyone would ever have
   written it the way it was—it’s just awful from end to end, a bad
   reimplementation of a subset of native browser functionality.
   It’s a form, let it *be* a form.

   Possibly the most baffling part of it was the use of location.replace
   which breaks the back button. I just… why!?

   While I was at it, I gave the search box an aria-label for good
   measure, but I didn’t change its type to "search" because that has
   UI implications on some platforms that I’m too lazy to deal with.

This is still pretty bad, because that magnifying glass is done in CSS
rather than being a fair dinkum submit button, but I just wanted a
quick fix because the autofocus issue is annoying me *so much*.

* apply templates/concept (#9539)

* update service-accounts-admin links (#9461)

* Trivial: Make the authentication doc consistent (#9472)

On the content, user categories are defined as service account and
normal user. However regular user is written at one place instead
of normal user. This replaces the regular user with normal user
for the consistency.

The option --authentication-token-webhook-config-file is for specifying
the configuration file which uses the kubeconfig file format, so this
replaces kubeconfig with configuration for avoiding confusions.

The last change is updating the order of 'clusters' and 'users' for
fitting the following example to read easily.

* Update authorization-rbac links (#9463)

* update authorization-rbac links

* fix broken links

* undo modification of cn content

* reorganize kubeadm files, part 1 (#9439)

* reorganize kubeadm files, part 1

* edit troubleshooting kubeadm for layout and content

* Update admission controller links (#9386)

* update admission-controller links

(cherry picked from commit 3704399)

* updated links found using greedier regex

(cherry picked from commit 45c6d4c)

* correct link in cn/docs/admin/authorization/_index.md

* fix incorrect changes introduced in eac3619

* undo update of cn content

* fix link

* fix admission webhook link

* The command to copy the decoded certificate to the server.crt (#9448)

* The command to copy the decoded certificate to the server.crt

* -D to --decode

* apply templates/concept and fix code snippets (#9542)

* Change formatting of Stackpoint turnkey doc (#9493)

* Change formatting of Stackpoint turnkey doc

* s/Running/Run

* fix formatting glitch

* use template

* Add env var example (#9486)

* Adding anchor links to partner page (#9411)

* adding anchor links

* updating link names

* Add CNCF logo to homepage  (#9375)

* add CNCF logo on homepage

* edits

* Fix dead links and apply template (#9476)

* fix dead links and apply template

* fix conflicts

* re-fix dead links

* Revert "re-fix dead links"

This reverts commit 3eb8292.

* Adding redirects for turnkey docs. (#9426)

These documents were moved in #8937.

* Update fedora_manual_config.md (#9416)

removal of 
  # Add your own!
  KUBELET_ARGS=""
this line causes line with args in it to be over writen

removal of flag "--require-kubeconfig" as it prevents the service from starting with error "F0708 18:41:17.411350   11725 server.go:145] unknown flag: --require-kubeconfig"

this is with v1.10.1

* update the go client usage to prevent common error. (#9414)

* fix-manage-compute-resources-container-view (#9402)

* Fix typo in example script (#9381)

Variable reference should be $ETCDHOSTS, not $ETCDHOST

* fix html

* add a space

* tweak crictl.md (#9349)

* Enhance documentation of .spec.startingDeadlineSeconds (#9296)

* Update cron-jobs.md

* Update automated-tasks-with-cron-jobs.md

* Update cron-jobs.md

* Reword added documentation and add info about error message.

* Fix grammatical typo.

* adjust grammar and punctuation

* adjust grammar and punctuation

* adjust tense

* Supplement documentation of ExternalName service types (#9435)

* Re-organize doc

* Remove section on multiple namespaces

* add NOTE to callout

* inline code block is not displayed (#8940)

* inline code block is not displayed

Using `kubectl get storageclass` instead of 

```
       kubectl get storageclass
```

correctly shows the code markup.

* Update change-default-storage-class.md

* reformat markdown for nested list

* Recommend --watch flag for obtaining external IP information (issue 8483) (#9129)

* Use --watch flag instead of checking multiple times

* Wording changes

* Update references to Federation-v2 progress (#9116)

* Update references to Federation-v2 progress

Added resources to the whats next section as there has been significant progress over the past few months with the alpha release of Federation-v2 expected in the next few weeks.

* remove <federation> in link

* Add new field selectors doc (#9174)

* Add new field selectors doc

* Address wording issues and remove warning

* add note on = and ==

Signed-off-by: lucperkins <lucperkins@gmail.com>

* fix double bullets in TOC (#9175)

* docs/concepts: add search paths for docker config (#9085)

previous document suggests to put config to /root/.docker/config.json
which is not always the case, and only works when the HOME=/root is
set for kubelet. Besides, that's not always the most recommended way
considering the potential risk when someone overrides this config
with another `docker login` on the same node. this change explicitly
lists all the possible locations where the configuration can be put.

* Add L10n repo branch structure info (#9206)

* Trivial Doc Fix (#9580)

This fixes the spelling of "default".

* fix: blog post clarity (#9578)

- rephrase Istio release info
- update RBAC for GKE vs hosted

* Trivial typo fix (#9575)

This PR takes over changes in #8980.

* Remove rkt-api-endpoint and rkt-path arguments in the doc (#9538) (#9576)

Kubelet help return not exist rkt-api-endpoint and rkt-path arguments,
So delete not exist arguments.

Signed-off-by: Yuanbin.Chen <cybing4@gmail.com>

* Fix reference to install-kubeadm docs (#9573)

The install-kubeadm doc has recently been moved from tasks to setup. Fix the references and remove an incorrect redict.

* updates to ING quotes (#9582)

* updates to ING quotes

* update

* Fix deployment.md with wrong READY numbers (#9584)

The status of READY number should be 2 instead of 0, described
in the first line of table

* oscon post (#9586)

* Add mention of NGINX Ingress Controller for Kubernetes (#9228)

* Update cron-jobs.md (#9234)

* Update cron-jobs.md

Removed bullet point indicating that a `CronJob` can run "Once at a specified point in time", since this use case is either not possible, or not documented at all.

* change wording

* Add Kontena Pharos as K8s solutions (#9166)

* adding cni.md (#8760)

* adding cni.md

* apply Zach's feedback

* update from GCE to GKE (#8881)

* Fix pipe to base64 -d to -D (#8943)

* Fix pipe to base64 -d to -D

Mac: `-d` does not work -D does

Eg. echo "c3R...zE2" | base64 -D

* use --decode instead of -D or -d

* Fix command highlight in port-forward-access-application-cluster (#8705)

* fix command highlight in port-forward-access-application-cluster

* Fix structure and add some sentences

* modify the wording

* update wording

* fix: typo, reword (#9587)

Apologies @kbarnard10, made this morning's correction with a typo >.<

* Add ICP license to the site footer (#9589)

* adding oscon post (#9595)

* Update pod-lifecycle.md (#9593)

Merging these two paragraphs, which both describe the fields included in the PodConditions. The first one mentions 6 fields, but only defines 3 of them. The second one defines two of the remaining three. The missing 6th element ("reason") has been added. Now we have the full list in one single section. Easier to understand.

* Update /docs/concepts/containers/images/ (#9596)

* wrap notes by shortcodes and remove command prompts

* tweak shell command

* remove command prompts and tweak shell commands (#9597)

* apply content_template (#9598)

* apply content_template (#9599)

* Updated dns-pod-service.md (#9552)

* Updated dns-pod-service.md

Added a note on A records creation

* Updated dns-pod-service.md

Added Hugo  {{ note }} shortcode

* Update dns-pod-service.md

Changed wording

* tighten up the wording

* kubeadm-install: modify the note about kubelet cgroup drivers (#9541)

* Make the command work with multiple pods too (#9454)

* Make the command work with multiple pods too

if the user has 2 or more pods the original command line give the following error:
```error: only one of -c or an inline [CONTAINER] arg is allowed
See 'kubectl logs -h' for help and examples.```

* Remove dollar sign to respect style guidelines

* Note on missing/incorrect labels and scheduler behaviour with pod anti-affinity (#8973)

* fix replicaset example (#9603)

* Fix display of lists in scheduling-gpus.md (#9609)

The lists are misparsed and displayed as normal paragraphs, add empty
lines so that they are parsed as proper lists.

* Fix contribution guide about adding code samples (#9574)

We have consolidated all YAML examples into `content/en/examples`
directory. This PR updates the contribution guide so that people know
where to put their sample YAML files when adding/changing topics.

* Blog Post: CPU Manager (#9632)

* adding oscon post

* CPU Manager Blog Post

* s/bash/shell (revert to previous)

* More language fixes

* Update information on master node size on GKE/AWS (#9226)

* Update information on master node size on GKE/AWS

* clean up passive language

* `this` instead of `the` to make it sound better. (#9629)

* Use Hugo for Sass processing (#9404)

* Move all Sass into a common /assets directory

* Remove node-sass make command

* Change head partial to accommodate full Sass rules

* Bump Hugo version in Netlify config

* Use separate partial for CSS imports

* Bump Hugo version

* Remove PostCSS from the pipeline

* Un-bump version

* Update Hugo version to 0.44

* Update Hugo version in Makefile

* Update production Hugo version

* Fix misspelled variable name

* Add ./resources folder to Git

* Update Hugo version in Netlify config to 0.45.1

* Use un-cached css.html partial

* Re-work extra CSS logic for .Params.css

* Update CSS generation logic in css.html partial

* Fix homepage image loading issue

* Fix quota documentation (#9648)

* Fix configure-service-account doc set permissions link error (#9653)

Issuse record: #9650

Signed-off-by: Yuanbin.Chen <cybing4@gmail.com>

* Change stage target to docker-serve in Makefile (#9216)

* Change stage target to docker-serve in Makefile

docker-serve is documented in the readme (from #9128).

* Update underlying command for make docker-serve

The underlying command listed in the README wasn't exactly the
same as the command in the Makefile.

* Remove old Dockerfile for Jekyll site

PR #9128 added a new Dockerfile for the Hugo site. The old
staging container is no longer needed.

* Add debugging information to pod priority and preemption (#9568)

* Add debugging information to Pod priority and preemption

* mdformat the page

* keep feature-state shortcodes together

* Add one more potential bug in preemption

* Addressed reviewer comments

* Keep packages back from package manager upgrades (#9509)

* Keep packages back from package manager upgrades

closes kubernetes/kubeadm#954

* copy edit revision

* Blog post, outlines KubeVirt's usage k8s extension features (#9324)

* Blog post about how KubeVirt extends Kubernetes using CRDs and other k8s extension features

* Update blog post to reflect k8s v1.11 crd versioning support

* Update and rename 2018-07-24-kubevirt-crds-for-virtualization.md to 2018-07-27-kubevirt-crds-for-virtualization.md

* Tidy up blog post to reflect reviewer feedback

* add pinterest case study (#9633)

* add pinterest case study

* fix

* fixes

* Update configure-service-account.md (#9657)

Fixed the broken link listed in : #9650

* Update scale-intro.html (#9659)

reduce --> increase

* Auto _headers file generation logic (#9225)

* Standardize code formatting

* change image assets to https (#9660)

* change image assets to https

* fix in docs

* fix remaining image links

* Localization instructions (#9192)

* Begin re-working localization instructions

* Fix dangling sentence

* Re-arrange sections plus new content

* Fix TOC issue with misplaced capture directive

* Create new shortcodes for versions and language repos

* Add more translation instructions

* Remove translation docs added as an example

* Finish draft of localization doc

* Remove extraneous note

* fix description about kubeadm (#9646)

* add note shortcodes (#9673)

* Change "dotation" to "dot notation" in two places (#9678)

* Document update (#9675)

Adding a link to redis replicated so users of this example have a better understanding of what redis replicated is

* Update downward-api-volume-expose-pod-information.md (#9567)

dapi-volume-resources.yaml
Added divisor field in resourceFieldRef for DownwardAPIVolumeFiles
to clarify the format in which values are returned.

Issue: kubernetes/kubernetes#64579

* update default value of kubelet flag pod-infra-container-image (#9611)

* kubeadm-upgrade-1.11: fix wrong flag for feature gates (#9619)

* kubeadm: fix broken link for ha-etcd doc (#9624)

* fix the command output (#9636)

I have verified on version v1.10.0
[root@huan30:~]$ kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0-1", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"archive", BuildDate:"2018-06-13T04:29:49Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0-1", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"archive", BuildDate:"2018-06-13T04:22:05Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

* Add Alibaba Cloud in pick-right-solution.md (#9644)

Add Alibaba Cloud in pick-right-solution.md to give users more options.

* Add a note CPU change handling in CPU manager. (#9671)

This relates to PR kubernetes/kubernetes#66718
which validates that CPU manager state and current set CPUs are in sync.

* fix description about custom resource (#9676)

* JSONPaths with spaces must be double-quoted on Windows (#9679)

* Fix links to example YAMLs (#9680)

There are a few cases which were missed during previous effort on
consolidating all example YAML files. This PR fixes them all in the
English version.

Closes: #9674

* Remove redundant parenthesis (#9681)

Closes: #9665

* Correct minor error (#9690)

Technically speaking SRV targets are address record names, not CNAMEs.  In fact, the SRV RFC states that SRV targets must point to an address record name, and cannot be an alias (e.g. CNAME).

* fix the command output (#9695)

I have verified on version v1.11
[root@huan40:~]$ kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.1", GitCommit:"b1b29978270dc22fecc592ac55d903350454310a", GitTreeState:"clean", BuildDate:"2018-07-17T18:53:20Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.1", GitCommit:"b1b29978270dc22fecc592ac55d903350454310a", GitTreeState:"clean", BuildDate:"2018-07-17T18:43:26Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

* fix the command output (#9697)

fix the command output

* Disable excludes when installing kube packages (#9670)

We should not exclude kubernetes packages when installing them.

* add link to nvidia gpu scheduling guide at end of device plugin document (#9685)

* Fix persistentVolumeClaim link (#9700)

* DamonSet typo (#9705)

* config: Get mediaTypes config in line with the Hugo version (#9704)

This gets rid of the big WARNING when building.

Note that this is only Netlify related, so it is backwards compatible.

* fix the command output (#9668)

I have verified on version v1.11.

Author: zparnold

Makefile

@@ -1,5 +1,5 @@
 DOCKER       = docker
-HUGO_VERSION = 0.40.3
+HUGO_VERSION = 0.44
 DOCKER_IMAGE = kubernetes-hugo
 DOCKER_RUN   = $(DOCKER) run --rm --interactive --tty --volume $(PWD):/src
 
@@ -10,24 +10,20 @@ help: ## Show this help.
 
 all: build ## Build site with production settings and put deliverables in _site.
 
-sass: # Rebuild the SASS source into CSS
-	node-sass --output-style compact ./src/sass/styles.sass ./static/css/styles.css
-	node-sass --output-style compact ./src/sass/case_study_styles.sass ./static/css/case_study_styles.css
-
 build: ## Build site with production settings and put deliverables in _site.
 	hugo
 
 build-preview: ## Build site with drafts and future posts enabled.
 	hugo -D -F
 
 serve: ## Boot the development server.
-	hugo server
+	hugo server --ignoreCache --disableFastRender
 
 docker-image:
 	$(DOCKER) build . --tag $(DOCKER_IMAGE) --build-arg HUGO_VERSION=$(HUGO_VERSION)
 
 docker-build:
 	$(DOCKER_RUN) $(DOCKER_IMAGE) hugo
 
-stage:
+docker-serve:
 	$(DOCKER_RUN) -p 1313:1313 $(DOCKER_IMAGE) hugo server --watch --bind 0.0.0.0

OWNERS

@@ -15,6 +15,7 @@ approvers:
 - chenopis
 - kbarnard10
 - mistyhacks
+- ryanmcginnis
 - steveperry-53
 - tengqm
 - zacharysarah

README.md

@@ -43,7 +43,9 @@ docker run \
   --volume $(PWD):/src \
   -p 1313:1313 \
   kubernetes-hugo \
-  hugo server --watch --bind 0.0.0.0
+  hugo server \
+  --watch \
+  --bind 0.0.0.0
 ```
 
 As when building without using a Docker container, the results of the build will be published to the `public` directory (the default output directory for [Hugo](https://gohugo.io), the static site generator used to build this site).

src/sass/_base.sass assets/sass/_base.sass

@@ -1133,7 +1133,7 @@ $feature-box-div-margin-bottom: 40px
 #video
 	width: 100%
 	position: relative
-	background-image: url(/images/kub_video_banner_box.jpg)
+	background-image: url(/images/kub_video_banner_homepage.jpg)
 	background-position: center center
 	background-size: cover
 

src/sass/_case-studies.sass assets/sass/_case-studies.sass

@@ -138,7 +138,7 @@ $video-section-height: 550px
 	#video
 		height: $video-section-height
 		position: relative
-		background-image: url(../images/kub_video_banner_box.jpg)
+		background-image: url(../images/kub_video_banner_homepage.jpg)
 		background-position: center center
 		background-size: cover
 

src/sass/_desktop.sass assets/sass/_desktop.sass

@@ -4,4 +4,4 @@
 // media queries
 @import "base"
 @import "tablet"
-@import "desktop"
+@import "desktop"

src/sass/_reset.sass assets/sass/_reset.sass

@@ -34,14 +34,26 @@ blog = "/:section/:year/:month/:day/:slug/"
 
 # Be explicit about the output formats. We (currently) only want an RSS feed for the home page.
 [outputs]
-home = [ "HTML", "RSS"]
+home = [ "HTML", "RSS", "HEADERS" ]
 page = [ "HTML"]
 section = [ "HTML"]
 
+# Add a "text/netlify" media type for auto-generating the _headers file
+[mediaTypes]
+[mediaTypes."text/netlify"]
+delimiter = ""
+
 [outputFormats]
 [outputFormats.RSS]
 baseName = "feed"
 
+# _headers file output (uses the template at layouts/index.headers)
+[outputFormats.HEADERS]
+mediatype = "text/netlify"
+baseName = "_headers"
+isPlainText = true
+notAlternative = true
+
 [params]
 
 time_format_blog = "Monday, January 02, 2006"
@@ -67,6 +79,17 @@ githubbranch = "v1.11.0"
 docsbranch = "release-1.11"
 url = "https://kubernetes.io"
 
+[params.pushAssets]
+css = [
+  "callouts",
+  "styles",
+  "custom-jekyll/tags"
+]
+js = [
+  "custom-jekyll/tags",
+  "script"
+]
+
 [[params.versions]]
 fullversion = "v1.10.3"
 version = "v1.10"
@@ -95,7 +118,6 @@ githubbranch = "v1.7.6"
 docsbranch = "release-1.7"
 url = "https://v1-7.docs.kubernetes.io"
 
-
 # Language definitions.
 
 [languages]
@@ -108,8 +130,7 @@ weight = 1
 [languages.cn]
 title = "Kubernetes"
 description = "Production-Grade Container Orchestration"
-languageName ="Chinese"
+languageName = "Chinese"
 weight = 2
 contentDir = "content/cn"
 
-

src/sass/_size.sass assets/sass/_size.sass

@@ -104,7 +104,7 @@ $ kubectl create -f ./secret.yaml
 secret "mysecret" created
 ```
 
-**编码注意：** secret 数据的序列化 JSON 和 YAML 值使用 base64 编码成字符串。换行符在这些字符串中无效，必须省略。当在 Darwin/OS X 上使用 `base64` 实用程序时，用户应避免使用 `-b` 选项来拆分长行。另外，对于 Linux 用户如果 `-w` 选项不可用的话，应该添加选项 `-w 0` 到 `base64` 命令或管道 `base64 | tr -d '\n' ` 。
+**编码注意：** secret 数据的序列化 JSON 和 YAML 值使用 base64 编码成字符串。换行符在这些字符串中无效，必须省略。当在 Darwin/macOS 上使用 `base64` 实用程序时，用户应避免使用 `-b` 选项来拆分长行。另外，对于 Linux 用户如果 `-w` 选项不可用的话，应该添加选项 `-w 0` 到 `base64` 命令或管道 `base64 | tr -d '\n' ` 。
 
 #### 解码 Secret
 

src/sass/_skin.sass assets/sass/_skin.sass

@@ -4,7 +4,7 @@ metadata:
   name: default-mem-demo-2
 spec:
   containers:
-  - name: defalt-mem-demo-2-ctr
+  - name: default-mem-demo-2-ctr
     image: nginx
     resources:
       limits:

src/sass/_tablet.sass assets/sass/_tablet.sass

@@ -47,6 +47,7 @@ <h2>The Challenges of Migrating 150+ Microservices to Kubernetes</h2>
         <button id="desktopShowVideoButton" onclick="kub.showVideo()">Watch Video</button>
         <br>
         <br>
+        <br>
         <a href="https://www.lfasiallc.com/events/kubecon-cloudnativecon-china-2018/" button id= "desktopKCButton">Attend KubeCon in Shanghai on Nov. 14-15, 2018</a>
         <br>
         <br>
@@ -121,20 +122,21 @@ <h4><a href="/docs/concepts/workloads/controllers/jobs-run-to-completion/">Batch
         <h3>Case Studies</h3>
         <div id="caseStudiesWrapper">
           <div>
-              <p>Supporting Fast Decisioning Applications with Kubernetes</p>
-              <a href="/case-studies/capital-one">Read more</a>
+              <p>Pinning Its Past, Present, and Future on Cloud Native</p>
+              <a href="/case-studies/pinterest">Read more</a>
           </div>
           <div>
-              <p>Driving Banking Innovation with Cloud Native</p>
-              <a href="/case-studies/ing">Read more</a>
+              <p>Reinventing the World’s Largest Education Company With Kubernetes</p>
+              <a href="/case-studies/pearson">Read more</a>
           </div>
+         
           <div>
-              <p>Cloud Native at Northwestern Mutual</p>
-              <a href="/case-studies/northwestern-mutual/">Read more</a>
+              <p>Supporting Fast Decisioning Applications with Kubernetes</p>
+              <a href="/case-studies/capital-one">Read more</a>
           </div>
           <div>
-              <p>Launching and Scaling Up Experiments, Made Simple</p>
-              <a href="/case-studies/openai/">Read more</a>
+              <p>Driving Banking Innovation with Cloud Native</p>
+              <a href="/case-studies/ing">Read more</a>
           </div>
 
         </div>
@@ -162,8 +164,16 @@ <h3>Case Studies</h3>
             <!--</div>-->
         <!--</div>-->
         <h5 style="text-align: center"><a href="/case-studies/" style="color: #3371E3; font-weight: 400">View all case studies</a></h5>
-    </main>
-</section>
+      </main>
+  </section>
+        <section id="cncf">
+            <main>
+        <center>
+        <p>We are a <a href="https://cncf.io/">CNCF</a> graduated project</p>
+        </center>
+      </main>
+  </section>
+
 
 
 

src/sass/case_study_styles.sass assets/sass/case_study_styles.sass

@@ -7,7 +7,7 @@ url: /blog/2015/05/Kubernetes-On-Openstack
 
 
 
-[![](http://3.bp.blogspot.com/-EOrCHChZJZE/VVZzq43g6CI/AAAAAAAAF-E/JUilRHk369E/s400/Untitled%2Bdrawing.jpg)](http://3.bp.blogspot.com/-EOrCHChZJZE/VVZzq43g6CI/AAAAAAAAF-E/JUilRHk369E/s1600/Untitled%2Bdrawing.jpg)
+[![](https://3.bp.blogspot.com/-EOrCHChZJZE/VVZzq43g6CI/AAAAAAAAF-E/JUilRHk369E/s400/Untitled%2Bdrawing.jpg)](https://3.bp.blogspot.com/-EOrCHChZJZE/VVZzq43g6CI/AAAAAAAAF-E/JUilRHk369E/s1600/Untitled%2Bdrawing.jpg)
 
 
 

src/sass/styles.sass assets/sass/styles.sass

@@ -17,7 +17,7 @@ In the spirit of minimum viability, the first version of Jenkins-on-Kubernetes I
 
 Here’s a visual of that first version:
 
-[![](http://1.bp.blogspot.com/-ccmpTmulrng/VaVxOs7gysI/AAAAAAAAAU8/bCEzgGGm-pE/s400/0.png)](http://1.bp.blogspot.com/-ccmpTmulrng/VaVxOs7gysI/AAAAAAAAAU8/bCEzgGGm-pE/s1600/0.png)
+[![](https://1.bp.blogspot.com/-ccmpTmulrng/VaVxOs7gysI/AAAAAAAAAU8/bCEzgGGm-pE/s400/0.png)](https://1.bp.blogspot.com/-ccmpTmulrng/VaVxOs7gysI/AAAAAAAAAU8/bCEzgGGm-pE/s1600/0.png)
 
 
 
@@ -156,7 +156,7 @@ The pod will have a service exposing TCP 80 and 443 to a public load balancer. H
 
 And here’s an overview with the SSL termination proxy in place. Notice that Jenkins is no longer directly exposed to the public Internet:
 
-[![](http://3.bp.blogspot.com/-0B1BEQo_fWc/VaVxVUBkf3I/AAAAAAAAAVE/5yCCnA29C88/s400/0%2B%25281%2529.png)](http://3.bp.blogspot.com/-0B1BEQo_fWc/VaVxVUBkf3I/AAAAAAAAAVE/5yCCnA29C88/s1600/0%2B%25281%2529.png)
+[![](https://3.bp.blogspot.com/-0B1BEQo_fWc/VaVxVUBkf3I/AAAAAAAAAVE/5yCCnA29C88/s400/0%2B%25281%2529.png)](https://3.bp.blogspot.com/-0B1BEQo_fWc/VaVxVUBkf3I/AAAAAAAAAVE/5yCCnA29C88/s1600/0%2B%25281%2529.png)
 
 
 

config.toml

@@ -8,7 +8,7 @@ At Devoxx Belgium and Devoxx Morocco, Ray Tsang and I showed a Raspberry Pi clus
 
 ### Wait! Why the heck build a Raspberry Pi cluster running Kubernetes? 
 
-We had two big reasons to build the Pi cluster at Quintor. First of all we wanted to experiment with container technology at scale on real hardware. You can try out container technology using virtual machines, but Kubernetes runs great on on bare metal too. To explore what that’d be like, we built a Raspberry Pi cluster just like we would build a cluster of machines in a production datacenter. This allowed us to understand and simulate how Kubernetes would work when we move it to our data centers.  
+We had two big reasons to build the Pi cluster at Quintor. First of all we wanted to experiment with container technology at scale on real hardware. You can try out container technology using virtual machines, but Kubernetes runs great on bare metal too. To explore what that’d be like, we built a Raspberry Pi cluster just like we would build a cluster of machines in a production datacenter. This allowed us to understand and simulate how Kubernetes would work when we move it to our data centers.  
 
 Secondly, we did not want to blow the budget to do this exploration. And what is cheaper than a Raspberry Pi! If you want to build a cluster comprising many nodes, each node should have a good cost to performance ratio. Our Pi cluster has 20 CPU cores, which is more than many servers, yet cost us less than $400. Additionally, the total power consumption is low and the form factor is small, which is great for these kind of demo systems.  
 

content/cn/docs/concepts/configuration/secret.md

@@ -6,7 +6,7 @@ url: /blog/2015/11/Kubernetes-As-Foundation-For-Cloud-Native-Paas
 ---
 With Kubernetes continuing to gain momentum as a critical tool for building and scaling container based applications, we’ve been thrilled to see a growing number of platform as a service (PaaS) offerings adopt it as a foundation. PaaS developers have been drawn to Kubernetes by its rapid rate of maturation, the soundness of its core architectural concepts, and the strength of its contributor community. The [Kubernetes ecosystem](https://kubernetes.io/blog/2015/07/the-growing-kubernetes-ecosystem) continues to grow, and these PaaS projects are great additions to it.
 
-[![](http://1.bp.blogspot.com/-xX93tnoIlGo/Vjj2fSc_CDI/AAAAAAAAAi0/lvTkT9jyFog/s400/k8%2Bipaas%2B1.png)](http://1.bp.blogspot.com/-xX93tnoIlGo/Vjj2fSc_CDI/AAAAAAAAAi0/lvTkT9jyFog/s1600/k8%2Bipaas%2B1.png)
+[![](https://1.bp.blogspot.com/-xX93tnoIlGo/Vjj2fSc_CDI/AAAAAAAAAi0/lvTkT9jyFog/s400/k8%2Bipaas%2B1.png)](https://1.bp.blogspot.com/-xX93tnoIlGo/Vjj2fSc_CDI/AAAAAAAAAi0/lvTkT9jyFog/s1600/k8%2Bipaas%2B1.png)
 
 
 
@@ -23,7 +23,7 @@ With Kubernetes continuing to gain momentum as a critical tool for building and
 
 
 
-[![](http://1.bp.blogspot.com/-1XZFGRHGb34/Vjj2wUtA6pI/AAAAAAAAAi8/SD-qRhVIiIs/s400/k8%2Bipaas%2B2.png)](http://1.bp.blogspot.com/-1XZFGRHGb34/Vjj2wUtA6pI/AAAAAAAAAi8/SD-qRhVIiIs/s1600/k8%2Bipaas%2B2.png)
+[![](https://1.bp.blogspot.com/-1XZFGRHGb34/Vjj2wUtA6pI/AAAAAAAAAi8/SD-qRhVIiIs/s400/k8%2Bipaas%2B2.png)](https://1.bp.blogspot.com/-1XZFGRHGb34/Vjj2wUtA6pI/AAAAAAAAAi8/SD-qRhVIiIs/s1600/k8%2Bipaas%2B2.png)
 
 
 
@@ -38,7 +38,7 @@ With Kubernetes continuing to gain momentum as a critical tool for building and
 
 
 
-[![](http://2.bp.blogspot.com/-t3L1CANyhUs/Vjj28Zpf9WI/AAAAAAAAAjE/Ef-PLLmHGvU/s400/k8%2Bipaas%2B3.png)](http://2.bp.blogspot.com/-t3L1CANyhUs/Vjj28Zpf9WI/AAAAAAAAAjE/Ef-PLLmHGvU/s1600/k8%2Bipaas%2B3.png)
+[![](https://2.bp.blogspot.com/-t3L1CANyhUs/Vjj28Zpf9WI/AAAAAAAAAjE/Ef-PLLmHGvU/s400/k8%2Bipaas%2B3.png)](https://2.bp.blogspot.com/-t3L1CANyhUs/Vjj28Zpf9WI/AAAAAAAAAjE/Ef-PLLmHGvU/s1600/k8%2Bipaas%2B3.png)
 
 
 
@@ -64,7 +64,7 @@ Huawei has made Kubernetes the core runtime engine for container based applicati
 
 
 
-[![](http://2.bp.blogspot.com/-Ys0Zn4IQzn0/Vjj3JIE0BVI/AAAAAAAAAjM/ktwltzVa1GE/s400/k8%2Bipaas%2B4.png)](http://2.bp.blogspot.com/-Ys0Zn4IQzn0/Vjj3JIE0BVI/AAAAAAAAAjM/ktwltzVa1GE/s1600/k8%2Bipaas%2B4.png)
+[![](https://2.bp.blogspot.com/-Ys0Zn4IQzn0/Vjj3JIE0BVI/AAAAAAAAAjM/ktwltzVa1GE/s400/k8%2Bipaas%2B4.png)](https://2.bp.blogspot.com/-Ys0Zn4IQzn0/Vjj3JIE0BVI/AAAAAAAAAjM/ktwltzVa1GE/s1600/k8%2Bipaas%2B4.png)
 
 
 

content/cn/docs/tasks/administer-cluster/memory-defaults-pod-2.yaml

@@ -27,7 +27,7 @@ The easiest way to take advantage of sysdig’s Kubernetes support is by launchi
 Now that csysdig is running, hit F2 to bring up the views panel, and you'll notice the presence of a bunch of new views. The **k8s Namespaces** view can be used to see the list of namespaces and observe the amount of CPU, memory, network and disk resources each of them is using on this machine:  
 
 
-[![](http://2.bp.blogspot.com/-9kXfpo76r0k/Vkz8AkpctEI/AAAAAAAAAss/yvf9oc759Wg/s640/sisdig%2B6.png)](http://2.bp.blogspot.com/-9kXfpo76r0k/Vkz8AkpctEI/AAAAAAAAAss/yvf9oc759Wg/s1600/sisdig%2B6.png)
+[![](https://2.bp.blogspot.com/-9kXfpo76r0k/Vkz8AkpctEI/AAAAAAAAAss/yvf9oc759Wg/s640/sisdig%2B6.png)](https://2.bp.blogspot.com/-9kXfpo76r0k/Vkz8AkpctEI/AAAAAAAAAss/yvf9oc759Wg/s1600/sisdig%2B6.png)
 
 
 
@@ -40,7 +40,7 @@ Now that csysdig is running, hit F2 to bring up the views panel, and you'll noti
 Similarly, you can select **k8s Services** to see the same information broken up by service:  
 
 
-[![](http://2.bp.blogspot.com/-Ya1W3Z_ETcs/Vkz8AN3XtfI/AAAAAAAAAs8/HNv_TvHpfHU/s640/sisdig%2B2.png)](http://2.bp.blogspot.com/-Ya1W3Z_ETcs/Vkz8AN3XtfI/AAAAAAAAAs8/HNv_TvHpfHU/s1600/sisdig%2B2.png)
+[![](https://2.bp.blogspot.com/-Ya1W3Z_ETcs/Vkz8AN3XtfI/AAAAAAAAAs8/HNv_TvHpfHU/s640/sisdig%2B2.png)](https://2.bp.blogspot.com/-Ya1W3Z_ETcs/Vkz8AN3XtfI/AAAAAAAAAs8/HNv_TvHpfHU/s1600/sisdig%2B2.png)
 
 
 
@@ -53,7 +53,7 @@ Similarly, you can select **k8s Services** to see the same information broken up
 or **k8s Controllers** to see the replication controllers:  
 
 
-[![](http://3.bp.blogspot.com/-gGkgXRC5P6g/Vkz8A1RVyAI/AAAAAAAAAtQ/SFlHQeNrDjQ/s640/sysdig%2B1.png)](http://3.bp.blogspot.com/-gGkgXRC5P6g/Vkz8A1RVyAI/AAAAAAAAAtQ/SFlHQeNrDjQ/s1600/sysdig%2B1.png)
+[![](https://3.bp.blogspot.com/-gGkgXRC5P6g/Vkz8A1RVyAI/AAAAAAAAAtQ/SFlHQeNrDjQ/s640/sysdig%2B1.png)](https://3.bp.blogspot.com/-gGkgXRC5P6g/Vkz8A1RVyAI/AAAAAAAAAtQ/SFlHQeNrDjQ/s1600/sysdig%2B1.png)
 
 
 
@@ -66,15 +66,15 @@ or **k8s Controllers** to see the replication controllers:
 or **k8s Pods** to see the list of pods running on this machine and the resources they use:  
 
 
-[![](http://3.bp.blogspot.com/-PrDfWzi9F3c/Vkz8H6rPlII/AAAAAAAAAtc/f46tE6EKvoo/s640/sisdig%2B7.png)](http://3.bp.blogspot.com/-PrDfWzi9F3c/Vkz8H6rPlII/AAAAAAAAAtc/f46tE6EKvoo/s1600/sisdig%2B7.png)
+[![](https://3.bp.blogspot.com/-PrDfWzi9F3c/Vkz8H6rPlII/AAAAAAAAAtc/f46tE6EKvoo/s640/sisdig%2B7.png)](https://3.bp.blogspot.com/-PrDfWzi9F3c/Vkz8H6rPlII/AAAAAAAAAtc/f46tE6EKvoo/s1600/sisdig%2B7.png)
 
 
 
 ### Drill Down-Based Navigation 
 A cool feature in csysdig is the ability to drill down: just select an element, click on enter and – boom – now you're looking inside it. Drill down is also aware of the Kubernetes hierarchy, which means I can start from a service, get the list of its pods, see which containers run inside one of the pods, and go inside one of the containers to explore files, network connections, processes or even threads. Check out the video below.  
 
 
-[![](http://1.bp.blogspot.com/-lQ-P2gLywlY/Vkz9MOoTgGI/AAAAAAAAAtk/UB6pW7sUbQA/s640/image09.gif)](http://1.bp.blogspot.com/-lQ-P2gLywlY/Vkz9MOoTgGI/AAAAAAAAAtk/UB6pW7sUbQA/s1600/image09.gif)
+[![](https://1.bp.blogspot.com/-lQ-P2gLywlY/Vkz9MOoTgGI/AAAAAAAAAtk/UB6pW7sUbQA/s640/image09.gif)](https://1.bp.blogspot.com/-lQ-P2gLywlY/Vkz9MOoTgGI/AAAAAAAAAtk/UB6pW7sUbQA/s1600/image09.gif)
 
 
 ### Actions! 
@@ -90,7 +90,7 @@ Let’s start with a quick review of Kubernetes’ architecture. From the physic
 
 On the other hand, from the logical/application point of view, Kubernetes clusters are arranged in the hierarchical fashion shown in this picture:  
 
-[![](http://1.bp.blogspot.com/-p_x0bLRdFJo/Vkz8IPR5q4I/AAAAAAAAAtg/D9UU2MfPmcI/s640/sisdig%2B4.png)](http://1.bp.blogspot.com/-p_x0bLRdFJo/Vkz8IPR5q4I/AAAAAAAAAtg/D9UU2MfPmcI/s1600/sisdig%2B4.png)
+[![](https://1.bp.blogspot.com/-p_x0bLRdFJo/Vkz8IPR5q4I/AAAAAAAAAtg/D9UU2MfPmcI/s640/sisdig%2B4.png)](https://1.bp.blogspot.com/-p_x0bLRdFJo/Vkz8IPR5q4I/AAAAAAAAAtg/D9UU2MfPmcI/s1600/sisdig%2B4.png)
 
 
 
@@ -123,7 +123,7 @@ One of the core features of Sysdig Cloud is groups, which allow you to define th
 
 If you’re interested in the utilization of your underlying physical resource – e.g., identifying noisy neighbors – then the physical hierarchy is great. But if you’re looking to explore the performance of your applications and microservices, then the logical hierarchy is often the best place to start. 
 
-[![](http://4.bp.blogspot.com/-80u3oSEi_Fw/Vkz8AZgE6eI/AAAAAAAAAtE/3iRDMJKBNmc/s640/sisdig%2B5.png)](http://4.bp.blogspot.com/-80u3oSEi_Fw/Vkz8AZgE6eI/AAAAAAAAAtE/3iRDMJKBNmc/s1600/sisdig%2B5.png)
+[![](https://4.bp.blogspot.com/-80u3oSEi_Fw/Vkz8AZgE6eI/AAAAAAAAAtE/3iRDMJKBNmc/s640/sisdig%2B5.png)](https://4.bp.blogspot.com/-80u3oSEi_Fw/Vkz8AZgE6eI/AAAAAAAAAtE/3iRDMJKBNmc/s1600/sisdig%2B5.png)
 
 
 
@@ -148,7 +148,7 @@ If you’re interested in the utilization of your underlying physical resource&n
 
 For example: here you can see the overall performance of our WordPress service: 
 
-[![](http://4.bp.blogspot.com/-QAsedrM2UxI/Vkz8Aas-26I/AAAAAAAAAtM/9B7Z33vUQrg/s640/sisdig%2B3.png)](http://4.bp.blogspot.com/-QAsedrM2UxI/Vkz8Aas-26I/AAAAAAAAAtM/9B7Z33vUQrg/s1600/sisdig%2B3.png)
+[![](https://4.bp.blogspot.com/-QAsedrM2UxI/Vkz8Aas-26I/AAAAAAAAAtM/9B7Z33vUQrg/s640/sisdig%2B3.png)](https://4.bp.blogspot.com/-QAsedrM2UxI/Vkz8Aas-26I/AAAAAAAAAtM/9B7Z33vUQrg/s1600/sisdig%2B3.png)
 
 Keep in mind that the pods implementing this service are scattered across multiple machines, but we can still total request counts, response times and URL statistics aggregated together for this service. And don’t forget: this doesn’t require any configuration or instrumentation of wordpress, apache, or the underlying containers! 
 
@@ -162,7 +162,7 @@ And from this view, I can now easily create alerts for these service-level metri
 
 We’ve also included Kubernetes awareness in Sysdig Cloud’s famous topology view, at both the physical and logical level. 
 
-[![](http://2.bp.blogspot.com/-2is-UJatmPk/Vk0AtdfvYvI/AAAAAAAAAt0/9SEsl2LCpYI/s640/image02.gif)](http://2.bp.blogspot.com/-2is-UJatmPk/Vk0AtdfvYvI/AAAAAAAAAt0/9SEsl2LCpYI/s1600/image02.gif)
+[![](https://2.bp.blogspot.com/-2is-UJatmPk/Vk0AtdfvYvI/AAAAAAAAAt0/9SEsl2LCpYI/s640/image02.gif)](https://2.bp.blogspot.com/-2is-UJatmPk/Vk0AtdfvYvI/AAAAAAAAAt0/9SEsl2LCpYI/s1600/image02.gif)
 
 
 
@@ -188,7 +188,7 @@ We’ve also included Kubernetes awareness in Sysdig Cloud’s famous topology v
 
 
 
-[![](http://2.bp.blogspot.com/-hGQtaIV9XTA/Vk0RnwtlcGI/AAAAAAAAAuM/7ndiyAWpSvU/s640/image08.gif)](http://2.bp.blogspot.com/-hGQtaIV9XTA/Vk0RnwtlcGI/AAAAAAAAAuM/7ndiyAWpSvU/s1600/image08.gif)
+[![](https://2.bp.blogspot.com/-hGQtaIV9XTA/Vk0RnwtlcGI/AAAAAAAAAuM/7ndiyAWpSvU/s640/image08.gif)](https://2.bp.blogspot.com/-hGQtaIV9XTA/Vk0RnwtlcGI/AAAAAAAAAuM/7ndiyAWpSvU/s1600/image08.gif)