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

Update service.md (#8219)

Browse Source 
* Update service.md

Update from ReplicationController and rolling-update to ReplcaSet and Deployment rollout

* Update service.md

Remove reference to deployment
This commit is contained in:
Dylan Graham
2018-04-30 11:43:16 +10:00
committed by k8s-ci-robot
parent 43bb7f45ca
commit eaf4fb892a
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/services-networking/service.md
+2 -3
View File
@@ -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