Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reword documentation for Service concept #14526

Merged
merged 6 commits into from
Jun 4, 2019
Merged

Reword documentation for Service concept #14526

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
7051db6
Reword glossary entry for Service
sftim May 24, 2019
ef90f8a
Improve What's Next section for Service concept
sftim May 24, 2019
d8c2296
Rename Services concept to singular
sftim May 24, 2019
c99bd4d
Reword Service concept description
sftim May 24, 2019
f04cfec
Use documentation IP address range
sftim May 24, 2019
fe46970
Write IPVS in uppercase
sftim May 27, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Use documentation IP address range 
1.2.3.4 is outside the blocks reserved for documentation.
  • Loading branch information
@sftim
sftim committed May 27, 2019
commit f04cfecbd5f2eb48e389689aa1263d25560fa67f
6 changes: 3 additions & 3 deletions content/en/docs/concepts/services-networking/service.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,7 +161,7 @@ metadata:
name: my-service
subsets:
- addresses:
- ip: 1.2.3.4
- ip: 192.0.2.42
ports:
- port: 9376
```
Expand All @@ -177,7 +177,7 @@ as a destination.

Accessing a Service without a selector works the same as if it had a selector.
In the example above, traffic will be routed to the single endpoint defined in
the YAML: `1.2.3.4:9376` (TCP).
the YAML: `192.0.2.42:9376` (TCP).

An ExternalName Service is a special case of service that does not have
selectors and uses DNS names instead. For more information, see the
Expand Down Expand Up @@ -493,7 +493,7 @@ Your service will report that allocated port in its `.spec.ports[*].nodePort` fi


If you want to specify particular IP(s) to proxy the port, you can set the `--nodeport-addresses` flag in kube-proxy to particular IP block(s); this is supported since Kubernetes v1.10.
This flag takes a comma-delimited list of IP blocks (e.g. 10.0.0.0/8, 1.2.3.4/32) to specify IP address ranges that kube-proxy should consider as local to this node.
This flag takes a comma-delimited list of IP blocks (e.g. 10.0.0.0/8, 192.0.2.0/25) to specify IP address ranges that kube-proxy should consider as local to this node.

For example, if you start kube-proxy with flag `--nodeport-addresses=127.0.0.0/8`, kube-proxy will select only the loopback interface for NodePort Services. The default for `--nodeport-addresses` is an empty list, and means that kube-proxy should consider all available network interfaces for NodePort. (That's also compatible with earlier Kubernetes releases).

Expand Down