high-available tailscale networked cluster fails to start properly

I want to connect to my cluster over tailscale and use tailscale between the nodes. I don't have firewall enabled on the machines. With various configs I'm able to bootstrap the cluster, but usually address is picked up from eth0 (public ip) or any other controller fails to properly start (konnectivity doesn't come ready)

I think this is related: https://github.com/k0sproject/k0sctl/issues/760

here's one of the configs I've tried:

```yaml
apiVersion: k0sctl.k0sproject.io/v1beta1
kind: Cluster
metadata:
name: k0s-cluster
user: admin
spec:
hosts:
- ssh:
address: hetzner-tuusula-1
user: root
role: controller+worker
privateInterface: tailscale0
- ssh:
address: hetzner-tuusula-2
user: root
role: controller+worker
privateInterface: tailscale0
- ssh:
address: hetzner-tuusula-3
user: root
role: controller+worker
privateInterface: tailscale0
k0s:
config:
apiVersion: k0s.k0sproject.io/v1beta1
kind: ClusterConfig
metadata:
name: k0s
namespace: kube-system
spec:
storage:
type: kine
kine:
dataSource: postgres://postgres:asdf@asdf.eu-north-1.rds.amazonaws.com:5432/k0s
```

Start by reproducing the supplied three-controller configuration with privateInterface set to tailscale0, then inspect how k0sctl selects node addresses and how konnectivity starts. Compare the behavior with the related k0sctl issue 760. Done means the cluster consistently uses the Tailscale interface and all controllers, including konnectivity, start successfully.

Written by the indexing model from the issue text.