v3.1.3

Bugfixes/Enhancements

fix: k3d cluster create --network somenet selected network by prefix instead of exact match

fix: cannot create k3s v1.19+ clusters with multiple server nodes

Problem: k3s v1.19 ships with embedded etcd (instead of dqlite), which only allows one learner node at a time
Solution: wait for preceding server node to emit "k3s is up and running" before joining the next one (which would fail)

Consequence: creating multi-server clusters becomes a little slower

"Benchmark" (Ubuntu 20.04, Docker 19.03, i7-9750H, 32GiB RAM) for 4 server nodes

embedded DB	k3s version	time to cluster with parallel server creation	time to cluster with serial server creation	difference
dqlite	v1.18.9-k3s1	30.508s	37.034s	6.526s
etcd	v1.19.2-k3s1	didn't work	52.169s	-

This k3d version passed end-to-end tests for the following k3s image versions:

Injection of the host.k3d.internal into the CoreDNS ConfigMap does not work on rancher/k3s:v1.19.2-k3s1, because the image is missing the used xargs command (to be fixed).