This message was deleted.

The current workflow for that is a bit clunky. You can do a two-step update: 1. Import the namespace 2. On a subsequent update, change the resource definition to your target state and run another update Alternatively, you could shell out to

kubectl

or a native k8s client in a “dynamic provider” workflow. This is related: https://github.com/pulumi/pulumi-kubernetes/issues/264

Yeah, that what I figured - can you share the docs to running native k8s client commands? I subscribed to the issue, look like our exact problem

Here's an example of running

kubectl

in a dynamic provider - https://github.com/pulumi/pulumi-eks/blob/db4b59d65b0f339f66a7c298dc890389eb56e13e/nodejs/eks/cni.ts#L183-L196.

thanks!