K8S resource is silently dropped when its Kind is not known to the kind order

[0xd3e]

When adding a Kubernetes resource with a Kind that is not known to the kind order, the resource is silently dropped from the list and is therefore not present in the output.

This is because of the filtering mechanism used when ordering Kubernetes resources.

An error message would be nice to give the developer a heads up.