Bug Description

As described here kubelet manages the /etc/hosts file. This is causing issues (at least on GKE), where the VM pods can get into a state where they can no longer connect to istiod:

2022-05-18T20:34:11.815583Z	warn	sds	failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on 8.8.8.8:53: no such host"

It's not exactly clear when kubelet will overwrite /etc/hosts, but bouncing the pod seems to reproduce the problem reliably for me on GKE.

The current echo VM deployment overwrites the /etc/hosts here. It appears that we need an alternative way of configuring this that will work in all environments.

Version

master

Additional Information

No response