whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #21439 from sftim/20200602_tidy_hostaliases_task

Browse Source 
Tidy task page about using hostAliases
This commit is contained in:
Kubernetes Prow Robot
2020-06-12 22:01:55 -07:00
committed by GitHub
parent edafb080e6 5d358120fb
commit d1d752e0e1
1 changed files with 29 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases.md
+29 -27
View File
@@ -5,27 +5,29 @@ reviewers:
title: Adding entries to Pod /etc/hosts with HostAliases title: Adding entries to Pod /etc/hosts with HostAliases
content_type: concept content_type: concept
weight: 60 weight: 60
min-kubernetes-server-version: 1.7
--- ---
{{< toc >}} {{< toc >}}
<!-- overview --> <!-- overview -->
Adding entries to a Pod's /etc/hosts file provides Pod-level override of hostname resolution when DNS and other options are not applicable. In 1.7, users can add these custom entries with the HostAliases field in PodSpec.
Modification not using HostAliases is not suggested because the file is managed by Kubelet and can be overwritten on during Pod creation/restart. Adding entries to a Pod's `/etc/hosts` file provides Pod-level override of hostname resolution when DNS and other options are not applicable. You can add these custom entries with the HostAliases field in PodSpec.
Modification not using HostAliases is not suggested because the file is managed by the kubelet and can be overwritten on during Pod creation/restart.
<!-- body --> <!-- body -->
## Default Hosts File Content ## Default hosts file content
Let's start an Nginx Pod which is assigned a Pod IP: Start an Nginx Pod which is assigned a Pod IP:
```shell ```shell
kubectl run nginx --image nginx --generator=run-pod/v1 kubectl run nginx --image nginx --generator=run-pod/v1
``` ```
```shell ```
pod/nginx created pod/nginx created
``` ```
@@ -35,7 +37,7 @@ Examine a Pod IP:
kubectl get pods --output=wide kubectl get pods --output=wide
``` ```
```shell ```
NAME READY STATUS RESTARTS AGE IP NODE NAME READY STATUS RESTARTS AGE IP NODE
nginx 1/1 Running 0 13s 10.200.0.4 worker0 nginx 1/1 Running 0 13s 10.200.0.4 worker0
``` ```
@@ -46,7 +48,7 @@ The hosts file content would look like this:
kubectl exec nginx -- cat /etc/hosts kubectl exec nginx -- cat /etc/hosts
``` ```
```none ```
# Kubernetes-managed hosts file. # Kubernetes-managed hosts file.
127.0.0.1 localhost 127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback ::1 localhost ip6-localhost ip6-loopback
@@ -60,43 +62,44 @@ fe00::2 ip6-allrouters
By default, the `hosts` file only includes IPv4 and IPv6 boilerplates like By default, the `hosts` file only includes IPv4 and IPv6 boilerplates like
`localhost` and its own hostname. `localhost` and its own hostname.
## Adding Additional Entries with HostAliases ## Adding additional entries with hostAliases
In addition to the default boilerplate, we can add additional entries to the In addition to the default boilerplate, you can add additional entries to the
`hosts` file to resolve `foo.local`, `bar.local` to `127.0.0.1` and `foo.remote`, `hosts` file.
`bar.remote` to `10.1.2.3`, we can by adding HostAliases to the Pod under For example: to resolve `foo.local`, `bar.local` to `127.0.0.1` and `foo.remote`,
`bar.remote` to `10.1.2.3`, you can configure HostAliases for a Pod under
`.spec.hostAliases`: `.spec.hostAliases`:
{{< codenew file="service/networking/hostaliases-pod.yaml" >}} {{< codenew file="service/networking/hostaliases-pod.yaml" >}}
This Pod can be started with the following commands: Yoyu can start a Pod with that configuration by running:
```shell ```shell
kubectl apply -f hostaliases-pod.yaml kubectl apply -f https://k8s.io/examples/service/networking/hostaliases-pod.yaml
``` ```
```shell ```
pod/hostaliases-pod created pod/hostaliases-pod created
``` ```
Examine a Pod IP and status: Examine a Pod's details to see its IPv4 address and its status:
```shell ```shell
kubectl get pod --output=wide kubectl get pod --output=wide
``` ```
```shell ```
NAME READY STATUS RESTARTS AGE IP NODE NAME READY STATUS RESTARTS AGE IP NODE
hostaliases-pod 0/1 Completed 0 6s 10.200.0.5 worker0 hostaliases-pod 0/1 Completed 0 6s 10.200.0.5 worker0
``` ```
The `hosts` file content would look like this: The `hosts` file content looks like this:
```shell ```shell
kubectl logs hostaliases-pod kubectl logs hostaliases-pod
``` ```
```none ```
# Kubernetes-managed hosts file. # Kubernetes-managed hosts file.
127.0.0.1 localhost 127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback ::1 localhost ip6-localhost ip6-loopback
@@ -111,19 +114,18 @@ fe00::2 ip6-allrouters
10.1.2.3 foo.remote bar.remote 10.1.2.3 foo.remote bar.remote
``` ```
With the additional entries specified at the bottom. with the additional entries specified at the bottom.
## Why Does Kubelet Manage the Hosts File? ## Why does the kubelet manage the hosts file? {#why-does-kubelet-manage-the-hosts-file}
Kubelet [manages](https://github.com/kubernetes/kubernetes/issues/14633) the The kubelet [manages](https://github.com/kubernetes/kubernetes/issues/14633) the
`hosts` file for each container of the Pod to prevent Docker from `hosts` file for each container of the Pod to prevent Docker from
[modifying](https://github.com/moby/moby/issues/17190) the file after the [modifying](https://github.com/moby/moby/issues/17190) the file after the
containers have already been started. containers have already been started.
Because of the managed-nature of the file, any user-written content will be {{< caution >}}
overwritten whenever the `hosts` file is remounted by Kubelet in the event of Avoid making manual changes to the hosts file inside a container.
a container restart or a Pod reschedule. Thus, it is not suggested to modify
the contents of the file.
If you make manual changes to the hosts file,
those changes are lost when the container exits.
{{< /caution >}}