Reword documentation for Service concept (#14526)
* 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 uppercasepull/14730/head
parent
b207ff8d2d
commit
62ae33b4a9
File diff suppressed because it is too large
Load Diff
|
@ -4,16 +4,15 @@ id: service
|
|||
date: 2018-04-12
|
||||
full_link: /docs/concepts/services-networking/service/
|
||||
short_description: >
|
||||
An API object that describes how to access applications, such as a set of Pods, and can describe ports and load-balancers.
|
||||
A way to expose an application running on a set of Pods as a network service.
|
||||
|
||||
aka:
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
---
|
||||
An API object that describes how to access applications, such as a set of {{< glossary_tooltip text="Pods" term_id="pod" >}}, and can describe ports and load-balancers.
|
||||
An abstract way to expose an application running on a set of {{< glossary_tooltip text="Pods" term_id="pod" >}} as a network service.
|
||||
|
||||
<!--more-->
|
||||
|
||||
The access point can be internal or external to the cluster.
|
||||
<!--more-->
|
||||
|
||||
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.
|
||||
|
|
Loading…
Reference in New Issue