Clarify where resolution works.

This commit is contained in:
Eric Tune 2015-06-03 17:01:43 -07:00
parent 8c2cc9fd61
commit 1c1272a3e4

View File

@ -13,6 +13,11 @@ crashes or scheduling changes). This maps well to DNS, which has a long
history of clients that, on purpose or on accident, do not respect DNS TTLs history of clients that, on purpose or on accident, do not respect DNS TTLs
(see previous remark about Pod IPs changing). (see previous remark about Pod IPs changing).
## Where does resolution work?
Kubernetes Service DNS names can be resolved using standard methods (e.g. [`gethostbyname`](
http://linux.die.net/man/3/gethostbyname)) inside any pod, except pods which
have the `hostNet` field set to `true`.
## Supported DNS schema ## Supported DNS schema
The following sections detail the supported record types and layout that is The following sections detail the supported record types and layout that is
supported. Any other layout or names or queries that happen to work are supported. Any other layout or names or queries that happen to work are