From bc805bd7ee983006b278a7f312cd2e72287debd9 Mon Sep 17 00:00:00 2001 From: Ricky Pai Date: Tue, 26 Sep 2017 19:39:18 -0700 Subject: [PATCH] update on state of HostAlias in 1.8 with hostNetwork Pod support (#5644) --- .../add-entries-to-pod-etc-hosts-with-host-aliases.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md b/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md index fb16b51dbf3fb..e1a1e1c8ed3d7 100644 --- a/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md +++ b/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md @@ -80,7 +80,11 @@ With the additional entries specified at the bottom. ## Limitations -As of 1.7, Pods with hostNetwork enabled will not be able to use this feature. This is because kubelet only manages the hosts file for non-hostNetwork Pods. There are ongoing discussions to change this. +HostAlias is only supported in 1.7+. + +HostAlias support in 1.7 is limited to non-hostNetwork Pods because kubelet only manages the hosts file for non-hostNetwork Pods. + +In 1.8, HostAlias is supported for all Pods regardless of network configuration. ## Why Does Kubelet Manage the Hosts File?