[Feature] add metadata.google.internal to hosts when running on GCE
knisbet opened this issue · 0 comments
knisbet commented
Feature Request
Some customers use google cloud VMs but not googles DNS, which prevents nodes from being able to resolve the metadata api. This combines with a problem with kubelet, where even when set to on-premises, will detect it's running on a gcloud VM and hang during startup trying to resolve and connect to the metadata api to collect information about the node.
A workaround for this scenario would be to add metadata.google.internal to the hosts entry within planet. Although if the node is firewalled from the metadata API, this workaround will be ineffective.
Motivation
To try and fix a particular customer that is specifically impacted by this setup.
Who's it for?
Customer M