Tim Bannister
62ae33b4a9
* Reword glossary entry for Service New wording should be more suitable for inclusion via a glossary_definition shortcode. * Improve What's Next section for Service concept * Rename Services concept to singular This matches other concept documentation, eg Deployment. * Use documentation IP address range 1.2.3.4 is outside the blocks reserved for documentation. * Reword Service concept description Services direct traffic to Pods, not containers * Write IPVS in uppercase
716 B
Executable File
716 B
Executable File
title, id, date, full_link, short_description, aka, tags
| title | id | date | full_link | short_description | aka | tags | ||
|---|---|---|---|---|---|---|---|---|
| Service | service | 2018-04-12 | /docs/concepts/services-networking/service/ | A way to expose an application running on a set of Pods as a network service. |
|
An abstract way to expose an application running on a set of {{< glossary_tooltip text="Pods" term_id="pod" >}} as a network service.
The set of Pods targeted by a Service is (usually) determined by a {{< glossary_tooltip text="selector" term_id="selector" >}}. If more Pods are added or removed, the set of Pods matching the selector will change. The Service makes sure that network traffic can be directed to the current set of Pods for the workload.