whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
* 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
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/workloads/pods/pod.md
+1 -1
View File
@@ -150,7 +150,7 @@ Pod is exposed as a primitive in order to facilitate:
* clean composition of Kubelet-level functionality with cluster-level functionality — Kubelet is effectively the "pod controller"
* high-availability applications, which will expect pods to be replaced in advance of their termination and certainly in advance of deletion, such as in the case of planned evictions, image prefetching, or live pod migration [#3949](http://issue.k8s.io/3949)
There is new first-class support for stateful pods with the [StatefulSet](/docs/concepts/workloads/controllers/statefulset/) controller (currently in beta). The feature was alpha in 1.4 and was called [PetSet](/docs/concepts/workloads/controllers/petset/). For prior versions of Kubernetes, best practice for having stateful pods is to create a replication controller with `replicas` equal to `1` and a corresponding service, see [this MySQL deployment example](/docs/tutorials/stateful-application/run-stateful-application/).
There is new first-class support for stateful pods with the [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets/) controller (currently in beta). The feature was alpha in 1.4 and was called [PetSet](/docs/concepts/workloads/controllers/petset/). For prior versions of Kubernetes, best practice for having stateful pods is to create a replication controller with `replicas` equal to `1` and a corresponding service, see [this MySQL deployment example](/docs/tutorials/stateful-application/run-stateful-application/).
## Termination of Pods