default vs unspecified namespaces

[esnible]

Kubernetes YAML can leave the namespace unspecified. In this case, kubectl applies the namespace from the kubectl config.

k8snetpolicy list sets the namespace to "default", (metav1.NamespaceDefault), if the namespace is blank.

This means k8snetpolicy list gives the same output when the input contains namespace: "default" or leaves the namespace off. I found this confusing. Some other tools I use preserved the blank namespace.

It might be worthwhile to treat "" like a valid real namespace, and preserve it, even though we don't know what it will be.
(Alternately it might be good to pick up up from the kubectl context. I'd prefer a blank namespace in the output, though.)