Revert "Update links to avoid redirects." (#5617)

* Revert "Fix the doc example"

This reverts commit 2872def62b.

* Revert "add the set of sessionAffinity timeoutseconds (#5474)"

This reverts commit 657734de6f.

* Revert "pod-security-policy.md: fix broken link to PSP proposal."

This reverts commit 8db51e099f.

* Revert "fix typo"

This reverts commit 24e5383071.

* Revert "Update images.md"

This reverts commit f844a41502.

* Revert "Update links to avoid redirects. (#5614)"

This reverts commit 35c7393849.
This commit is contained in:
Steve Perry
2017-09-25 13:43:15 -07:00
committed by GitHub
parent 2872def62b
commit 7792c801e3
103 changed files with 277 additions and 277 deletions
+2 -2
View File
@@ -19,7 +19,7 @@ This document describes how to run Kubernetes using [rkt](https://github.com/cor
* The [rkt API service](https://coreos.com/rkt/docs/latest/subcommands/api-service.html) must be running on the node.
* You will need [kubelet](/docs/home/scratch/#kubelet) installed on the node, and it's recommended that you run [kube-proxy](/docs/home/scratch/#kube-proxy) on all nodes. This document describes how to set the parameters for kubelet so that it uses rkt as the runtime.
* You will need [kubelet](/docs/getting-started-guides/scratch/#kubelet) installed on the node, and it's recommended that you run [kube-proxy](/docs/getting-started-guides/scratch/#kube-proxy) on all nodes. This document describes how to set the parameters for kubelet so that it uses rkt as the runtime.
## Pod networking in rktnetes
@@ -201,7 +201,7 @@ Use rkt's [*contained network*](#rkt-contained-network) with the KVM stage1, bec
## Known issues and differences between rkt and Docker
rkt and the default node container engine have very different designs, as do rkt's native ACI and the Docker container image format. Users may experience different behaviors when switching from one container engine to the other. More information can be found [in the Kubernetes rkt notes](/docs/home/rkt/notes/).
rkt and the default node container engine have very different designs, as do rkt's native ACI and the Docker container image format. Users may experience different behaviors when switching from one container engine to the other. More information can be found [in the Kubernetes rkt notes](/docs/getting-started-guides/rkt/notes/).
## Troubleshooting