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

Fix broken link:service.md

Browse Source 
Fix broken link:service.md
This commit is contained in:
Xiaoyu Zhang
2017-04-14 06:05:46 +08:00
committed by Andrew Chen
parent 07d05b7ceb
commit e7fba44d3d
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/services-networking/service.md
+1 -1
View File
@@ -7,7 +7,7 @@ title: Services
Kubernetes [`Pods`](/docs/user-guide/pods) are mortal. They are born and when they die, they Kubernetes [`Pods`](/docs/user-guide/pods) are mortal. They are born and when they die, they
are not resurrected. [`ReplicationControllers`](/docs/user-guide/replication-controller) in are not resurrected. [`ReplicationControllers`](/docs/user-guide/replication-controller) in
particular create and destroy `Pods` dynamically (e.g. when scaling up or down particular create and destroy `Pods` dynamically (e.g. when scaling up or down
or when doing [rolling updates](/docs/user-guide/kubectl/kubectl_rolling-update)). While each `Pod` gets its own IP address, even or when doing [rolling updates](/docs/user-guide/kubectl/v1.6/#rolling-update)). While each `Pod` gets its own IP address, even
those IP addresses cannot be relied upon to be stable over time. This leads to 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 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 functionality to other `Pods` (let's call them frontends) inside the Kubernetes