An issue I noticed today is that • When I create a

kubernetes.core/v1.Namespace

, I accidently forgot to pass in a

ResourceOptions

which is supposed to contain a provider with the right kubeconfig. • Instead of raising an error, it seems that the

Namespace

just picked up a random IP address (and thinking that's the IP address to the K8s cluster), which led to very strange error messages afterwards. When I ran it through pulumi/action, it says "kubeconfig" not found; when I ran it through command line, it says "IP xx.xx.xxx.xxx timeout". (I guess they are not so strange after I figure out the cause) I wondering if Pulumi has some error checking mechnisim that I could turn on to check for trivial user mistakes like this?