mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-08-02 08:17:26 +00:00
Clarify where resolution works.
This commit is contained in:
parent
8c2cc9fd61
commit
1c1272a3e4
@ -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
|
||||||
|
Loading…
Reference in New Issue
Block a user