No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I could use some help solving how to write <https://www.pulumi.com/registry/packages/kubernetes/api-docs/kustomize/directory/#transformations_nodejs|kustomize transformations> to remove a namespace object from being generated by @pulumi/kubernetes's <https://www.pulumi.com/registry/packages/kubernetes/api-docs/kustomize/directory/#transformations_nodejs|kubernetes.kustomize.Directory> where the namespace object is coming in from an upstream that is out of my control.

Problem of kustomize generating the namespace object results in:
```Updating (keycloak):
     Type                                                  Name                   Status                  Info
     pulumi:pulumi:Stack                                   tkl-keycloak-keycloak  **failed**              1 error
     └─ kubernetes:kustomize:Directory                     keycloak                                       
 +      ├─ kubernetes:core/v1:Namespace                    keycloak               **creating failed**     1 error```

```transformations: [
    (obj: any, opts: pulumi.CustomResourceOptions) =&gt; {
      unset(obj.metadata.namespace)
    },```

<@UCU9C7W73> I find it confusing that the function signature for transformations on `kustomize.Directory` is different from generic Pulumi resource transformations. It took me some time to figure this out.

<@UK4HNFLCB> I didn’t know that, let me take a look :smile: