K3d: [BUG] failed to delete cluster

[tuxtof]

What did you do?

try to delete cluster

• How was the cluster created?

  • k3d c -a 0.0.0.0:6445 -n cluster2

• What did you do afterwards?
  delete the cluster

What did you expect to happen?

k3d d cluster2
FATA[0000] No cluster(s) found

Concise description of what you expected to happen after doing what you described above.

Screenshots or terminal output

k3d l
+-----------------+-------------------------------+---------+---------+
| NAME | IMAGE | STATUS | WORKERS |
+-----------------+-------------------------------+---------+---------+
| cluster2 | docker.io/rancher/k3s:v0.10.0 | running | 0/0 |
| cluster1 | docker.io/rancher/k3s:v0.10.0 | running | 0/0 |
| control-cluster | docker.io/rancher/k3s:v0.10.0 | running | 0/0 |
+-----------------+-------------------------------+---------+---------+
~> k3d d cluster2
FATA[0000] No cluster(s) found

same problem with other cluster

Which OS & Architecture?

MacOS 10.15

Which version of k3d?

k3d version v1.3.4

Which version of docker?
Client: Docker Engine - Community
Version: 19.03.4
API version: 1.40
Go version: go1.12.10
Git commit: 9013bf5
Built: Thu Oct 17 23:44:48 2019
OS/Arch: darwin/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 19.03.4
API version: 1.40 (minimum version 1.12)
Go version: go1.12.10
Git commit: 9013bf5
Built: Thu Oct 17 23:50:38 2019
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.2.10
GitCommit: b34a5c8af56e510852c35414db4c1f4fa6172339
runc:
Version: 1.0.0-rc8+dev
GitCommit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
docker-init:
Version: 0.18.0
GitCommit: fec3683

[iwilltry42]

Hi @tuxtof, thanks for opening this issue.
In your description you write k3d d cluster2 where it should be k3d d -n cluster2 to delete only the cluster named cluster2 or k3d d -a to delete all clusters.

[tuxtof]

Hi @iwilltry42 , good catch
I was misled by the message "no cluster found"
maybe we need to thrown an error and ask to specify -n XXX or -a

[iwilltry42]

@tuxtof, I see, that this can be confusing/misleading.
However, when you don't specify a -n <NAME> in a k3d command, it will fallback to the default cluster name k3s-default

[tuxtof]

yes i see that so we can imagine replace the message with something like
'cluster k3s-default not found'
but it better to give an error
because k3d d cluster2 is invalid syntax

[iwilltry42]

The next release will include more verbose error messages for delete and get-kubeconfig if neither --all nor --name was specified and no cluster was found.
Syntax checks (additional unused args) will come with the next major version (new CLI framework).