We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/etc/hosts
settings.network.hostname
Currently we populate/etc/hosts with entries for 127.0.0.1 and ::1 that alias to localhost.
127.0.0.1
::1
localhost
We need to populate it with an entry to alias 127.0.0.1 to the hostname.
One example: For other distros (Ubuntu) CAPI populates this entry in /etc/hosts and kube-vip appears to use /etc/hosts to resolve the hostname.
kube-vip
The text was updated successfully, but these errors were encountered:
We'll definitely need to double check that this doesn't break anything on EC2, but it doesn't seem like it would.
Here's an example of the CAPI code that runs during provisioning:
runcmd: ... - "echo \"::1 ipv6-localhost ipv6-loopback\" >/etc/hosts" - "echo \"127.0.0.1 localhost\" >>/etc/hosts" - "echo \"127.0.0.1 {{ ds.meta_data.hostname }}\" >>/etc/hosts" ...
Sorry, something went wrong.
zmrow
Successfully merging a pull request may close this issue.
Currently we populate
/etc/hosts
with entries for127.0.0.1
and::1
that alias tolocalhost
.We need to populate it with an entry to alias
127.0.0.1
to the hostname.One example: For other distros (Ubuntu) CAPI populates this entry in
/etc/hosts
andkube-vip
appears to use/etc/hosts
to resolve the hostname.The text was updated successfully, but these errors were encountered: