Unexpected behavior for kinD nodes when using the --node-selector option

[simcod]

To reproduce this issue, the following codebase can be used.
The creation of the kinD clusters can be used in combination with the --node-selector option:

sudo containerlab deploy --topo topo.yaml --node-filter k01

However, destruction is not possible:

sudo containerlab destroy --topo topo.yaml --node-filter k01

# Output
INFO[0000] no containerlab containers found

The expected behaviour would be that containerlab only destroys the node k01.

The following commands are working as expected for the node srl01:

sudo containerlab deploy --topo topo.yaml --node-filter srl01

sudo containerlab destroy --topo topo.yaml --node-filter srl01

[hellt]

Yes, node filters feature has some issues, and I presume mostly with nodes deployed outside of containerlab (like kind nodes).

[simcod]

@hellt Thanks for your quick reply.