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 fb16b51dbf..e1a1e1c8ed 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?