[BUG] - Cluster created with port mapping does not add host.k3d.internal to coreDNS

[fabioandreola]

What did you do

• How was the cluster created?

  • k3d cluster create my-cluster -p "8085:80@loadbalancer"

• What did you do afterwards?

  • kubectl describe configmap/coredns -n kube-system

What did you expect to happen

Mapping to my localhost IP to host.k3d.internal should be found under configmap/coredns . If the same cluster is created without the parameter"8085:80@loadbalancer" then the host.k3d.internal is added to coreDNS configuration correctly.

Screenshots or terminal output

Using k3d cluster create my-cluster -p "8085:80@loadbalancer"

Using k3d cluster create my-cluster

Which OS & Architecture

• MAC Monterey with M1 chip

Which version of k3d

k3d version v5.4.1
k3s version v1.22.7-k3s1 (default)

Which version of docker

Client:
 Cloud integration: v1.0.23
 Version:           20.10.14
 API version:       1.41
 Go version:        go1.16.15
 Git commit:        a224086
 Built:             Thu Mar 24 01:49:20 2022
 OS/Arch:           darwin/arm64
 Context:           default
 Experimental:      true

Server: Docker Desktop 4.7.1 (77678)
 Engine:
  Version:          20.10.14
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.15
  Git commit:       87a90dc
  Built:            Thu Mar 24 01:45:44 2022
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.5.11
  GitCommit:        3df54a852345ae127d1fa3092b95168e4a88e2f8
 runc:
  Version:          1.0.3
  GitCommit:        v1.0.3-0-gf46b6ba
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
```

[bijanrich]

I have the same problem. Running on Ubuntu 22.

Distributor ID: Ubuntu
Description:    Ubuntu 22.04 LTS
Release:        22.04
Codename:       jammy

k3d version v5.4.1
k3s version v1.22.7-k3s1 (default)

It sometimes works, sometimes doesn't. It always logs this though:

INFO[0013] Injecting records for hostAliases (incl. host.k3d.internal) and for 3 network members into CoreDNS configmap...

Also, after restarting the entries are gone.

It's working reliably when I don't add --registry-config "registries.yml" to the cluster create command which specifies my local registry.

[jpprins1]

Same problem, just upgraded from v5.2.2/v1.21.7-k3s1 to v5.4.1/v1.22.7-k3s1 (Ubuntu 20.04 LTS)

Note: Tried with/without registry and LB settings -> did not work in any of these cases.

[iwilltry42]

Hi @fabioandreola , thanks for opening this issue!
This is really weird. It's on the roadmap 👍