From 485fb3e788572cf39da58d85a86a08bdfc057bc8 Mon Sep 17 00:00:00 2001 From: Jonathan Boulle Date: Mon, 3 Oct 2016 20:27:18 +0200 Subject: [PATCH] docs/pods: update reference to pets Now that PetSets are implemented we can link there. --- docs/user-guide/pods/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/user-guide/pods/index.md b/docs/user-guide/pods/index.md index 4c16b66074..b5de192d83 100644 --- a/docs/user-guide/pods/index.md +++ b/docs/user-guide/pods/index.md @@ -150,7 +150,9 @@ 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) -The current best practice for pets is to create a replication controller with `replicas` equal to `1` and a corresponding service. If you find this cumbersome, please comment on [issue #260](http://issue.k8s.io/260). +There is new first-class support for pet-like pods with the [PetSet](/docs/user-guide/petset/) feature (currently in alpha). +For prior versions of Kubernetes, best practice for pets is to create a replication controller with `replicas` equal to `1` and a corresponding service. + ## Termination of Pods