k3s: k3 does not support mDNS

Environmental Info: K3s Version:

k3s version v1.18.6+k3s1 (6f56fa1d)

Node(s) CPU architecture, OS, and Version:

intended master: Linux nanopct4 5.4.49-rockchip64 #20.05.7 SMP PREEMPT Sun Jun 28 18:17:52 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux intended worker: Linux nanopineo2 5.4.45-sunxi64 #20.05.4 SMP Sun Jun 14 23:12:39 CEST 2020 aarch64 aarch64 aarch64 GNU/Linux

Both are Armbian, fresh installs

Cluster Configuration:

under construction

Describe the bug:

The documentation https://rancher.com/docs/k3s/latest/en/quick-start/ says that I can create a worker by running the curl | sh with a couple of environment variables. The machines don’t seem to see each other.

Steps To Reproduce:

• Installed K3s:

  curl -sfL https://get.k3s.io | KS3_URL=https://192.168.2.9:6443 K3S_TOKEN=**** sh -

• checked nodes

  k3s kubectl get nodes

Expected behavior:

Multiple nodes shown, or errors during initialization (neither happened)

Actual behavior:

[INFO]  Finding release for channel stable
[INFO]  Using v1.18.6+k3s1 as release
[INFO]  Downloading hash https://github.com/rancher/k3s/releases/download/v1.18.6+k3s1/sha256sum-arm64.txt
[INFO]  Downloading binary https://github.com/rancher/k3s/releases/download/v1.18.6+k3s1/k3s-arm64
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  Creating /usr/local/bin/ctr symlink to k3s
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
Created symlink /etc/systemd/system/multi-user.target.wants/k3s.service → /etc/systemd/system/k3s.service.
[INFO]  systemd: Starting k3s
root@seven:~# k3s kubectl get nodes
NAME    STATUS   ROLES    AGE   VERSION
seven   Ready    master   65s   v1.18.6+k3s1

Additional context / logs:

is the entire contents of the node-token file supposed to go into the environment variable? This is never explained one way or another.