From 59b6a6d2b8fb24b9842b97506e15bb2ab7b9b41e Mon Sep 17 00:00:00 2001 From: qiaolei Date: Wed, 2 Sep 2015 20:21:10 +0800 Subject: [PATCH] Fix a typo `hostNet` to `hostNetwork` Where `hostNet` should be `hostNetwork` --- cluster/addons/dns/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cluster/addons/dns/README.md b/cluster/addons/dns/README.md index 20cad420792..c6e5824cfe3 100644 --- a/cluster/addons/dns/README.md +++ b/cluster/addons/dns/README.md @@ -16,7 +16,7 @@ history of clients that, on purpose or on accident, do not respect DNS TTLs ## 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`. +have the `hostNetwork` field set to `true`. ## Supported DNS schema The following sections detail the supported record types and layout that is