From eaf4fb892a25b5a3a4e323728feeddcb949c3ccb Mon Sep 17 00:00:00 2001 From: Dylan Graham Date: Mon, 30 Apr 2018 11:43:16 +1000 Subject: [PATCH] Update service.md (#8219) * Update service.md Update from ReplicationController and rolling-update to ReplcaSet and Deployment rollout * Update service.md Remove reference to deployment --- docs/concepts/services-networking/service.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/concepts/services-networking/service.md b/docs/concepts/services-networking/service.md index d0701917b0..9b50666504 100644 --- a/docs/concepts/services-networking/service.md +++ b/docs/concepts/services-networking/service.md @@ -5,9 +5,8 @@ title: Services --- Kubernetes [`Pods`](/docs/concepts/workloads/pods/pod/) are mortal. They are born and when they die, they -are not resurrected. [`ReplicationControllers`](/docs/concepts/workloads/controllers/replicationcontroller/) in -particular create and destroy `Pods` dynamically (e.g. when scaling up or down -or when doing [rolling updates](/docs/reference/generated/kubectl/kubectl-commands#rolling-update)). While each `Pod` gets its own IP address, even +are not resurrected. [`ReplicaSets`](/docs/concepts/workloads/controllers/replicaset/) in +particular create and destroy `Pods` dynamically (e.g. when scaling up or down). While each `Pod` gets its own IP address, even those IP addresses cannot be relied upon to be stable over time. This leads to a problem: if some set of `Pods` (let's call them backends) provides functionality to other `Pods` (let's call them frontends) inside the Kubernetes