Add the ablity to specify extra labels in the config file about kind HOT 3 OPEN

I would recommend tracking this out of band?

I see that Provider.List() returns a []string so I can probably create a filter like...

func filter(s []string) []string {
	prefix := "foo-"
	var ns []string
	for _, i := range s {
		if strings.HasPrefix(i, prefix) {
			ns = append(ns, i)
		}
	}
	return ns
}

I would have to mutate the name passed to me (because I still allow that in my wrapper utility)

from kind.

This is going to be clunky to support portably, because of varying restrictions in the underlying tools on what labels can be in the node runtimes, the current labels are a technically undocumented implementation detail and if we had to support a new node backend with compat issues for our internal usage we could use some other technique entirely (or base64 encode or ...).

I would recommend tracking this out of band?

from kind.

When using KIND as a library, there's no way to distinguish which ones are created by KIND itself, or if it was created by another tool using KIND as a library.

I mean, to the kind CLI and to the packages, that's working as intended? These just indicate that the kind code should be able to manipulate the container-nodes and stores some internal metadata used by the packages/cli.

Usually people pick reasonably unique cluster names like istio-test or something.

from kind.