Feature request: Support adding HostAliases from ConfigMap

[tangblue]

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
According to the following kubernetes document, the host entries can be added to Pod /etc/hosts with HostAliases.
https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/

With ConfigMap, the configuration artifacts can be decoupled from image content. But the HostAliases can not be set by ConfigMap. It makes the custom host entries can be only set in the image content.

What you expected to happen:
Add new field(e.g. hostAliasesFrom) in PodSpec and the custom host entries can be added by the Pod's .spec.hostAliasesFrom which is a reference of a ConfigMap key.

[dims]

/sig node
/sig network

[smarterclayton]

Can’t you mount a configmap at /etc/hosts with a subpath? That’s more in line with the customization to control this that I would expect.

[tangblue]

/etc/hosts is created by kubernetes runtime. It seems like mounting ConfigMap at /etc/hosts is not a safe way.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Prussia]

What is the final solution for it?