We're working on the better solutions, but they're very much in progress. For now that's probably the best we have.
c
careful-mouse-48712
02/17/2023, 8:02 PM
Thanks (for the response and the work)! It seems though i spoke a bit too soon. I have 1 ubuntu-notebook where the /etc/hosts entry seems to directly propagate to any running pod and resolve 192-168-5-15.nip.io also to 127.0.0.1. Any idea how that happens and to stop it?
careful-mouse-48712
02/18/2023, 7:14 AM
Ah culprit found systemd-resolved ...again should probably leave that thing at a bus stop.;) Adding 'ReadEtcHosts=no' in /etc/systemd/resolved.conf seems to solve this problem.