🐛 Talos does not change the network configuration before installation

[uhthomas]

Bug Report

Description

It's usually a good idea to use DNS instead of an IP address for the control plane endpoint, but higher the barrier for entry given the need for an external DNS provider.

A simple solution to avoid this is to use extraHostEntries which resolves the domain name locally. Unfortunately, this is not possible to do during installation as the network configuration is not updated.

Logs

Lots of logs about not being able to resolve the domain name, I don't have a picture - sorry.

Environment

• Talos version: v1.5.3
• Kubernetes version: N/A
• Platform: bare metal

[smira]

something I could look into at some point, but with KubePrism changing control plane should be super easy and non-disruptive

[smira]

I can't reproduce the issue in this ticket, a hostname added to extraHostEntries works even before the install is executed, it might take a retry attempt for it to be available, but it works.

[devantler]

@smira Hi, it seems the /etc/hosts is not populated during installation, and thus:

a hostname added to extraHostEntries works even before the install is executed no longer is true.

This is a bit problematic for us, as we aim to use Talos in an airgapped environment, where DNS and NTP is not available at install. We rely on the extraHostEntries to reach a docker registry that can provide the installation images.

We use Talos v1.7.4.

@trarbr

[smira]

First of all, please open a new issue and submit the logs which describe the issue. It's quite impossible to understand what is going on so far.

Plus, for docker images you can use registry mirrors feature to redirect.

I'm pretty sure that /etc/hosts is populated, so I need to see the actual logs to understand the problem better.

[devantler]

That makes sense! I will create an issue with the necessary context/logs next week :-)