kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
website/content/en/docs/reference/glossary/service.md

19 lines
716 B
Markdown
Raw Normal View History

Convert site to Hugo (#8316) This commit converts content and layout to use Hugo.
2018-05-05 16:00:51 +00:00
---
title: Service
id: service
date: 2018-04-12
full_link: /docs/concepts/services-networking/service/
short_description: >
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 uppercase
2019-06-04 23:11:54 +00:00
A way to expose an application running on a set of Pods as a network service.
Convert site to Hugo (#8316) This commit converts content and layout to use Hugo.
2018-05-05 16:00:51 +00:00
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 uppercase
2019-06-04 23:11:54 +00:00
aka:
Convert site to Hugo (#8316) This commit converts content and layout to use Hugo.
2018-05-05 16:00:51 +00:00
tags:
- fundamental
- core-object
---
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 uppercase
2019-06-04 23:11:54 +00:00
An abstract way to expose an application running on a set of {{< glossary_tooltip text="Pods" term_id="pod" >}} as a network service.
Convert site to Hugo (#8316) This commit converts content and layout to use Hugo.
2018-05-05 16:00:51 +00:00
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 uppercase
2019-06-04 23:11:54 +00:00
<!--more-->
Convert site to Hugo (#8316) This commit converts content and layout to use Hugo.
2018-05-05 16:00:51 +00:00
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 uppercase
2019-06-04 23:11:54 +00:00
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.