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

Explain Service without selector is for non-Pod backends (#32602)

Browse Source 
* Minor edit for clarity

The previous phrasing didn't emphasize the point that the reason you define a Service with no selectors is to point to a backend that's not a Pod, and the emphasis on the external nature of the backend

* Add note that Services w/o selectors, but +Endpoints is the technique to use for abstracting external backends

Co-authored-by: Rey Lejano <rlejano@gmail.com>

Co-authored-by: Rey Lejano <rlejano@gmail.com>
This commit is contained in:
Tim Rosenblatt
2022-03-31 22:40:37 -07:00
committed by GitHub
parent 74c12d3bca
commit f16c446d0a
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/service.md
+3 -3
View File
@@ -158,9 +158,9 @@ Each port definition can have the same `protocol`, or a different one.
### Services without selectors ### Services without selectors
Services most commonly abstract access to Kubernetes Pods, but they can also Services most commonly abstract access to Kubernetes Pods thanks to the selector,
abstract other kinds of backends. but when used with a corresponding Endpoints object and without a selector, the Service can abstract other kinds of backends,
For example: including ones that run outside the cluster. For example:
* You want to have an external database cluster in production, but in your * You want to have an external database cluster in production, but in your
test environment you use your own databases. test environment you use your own databases.