This message was deleted.

This is likely related to https://github.com/pulumi/pulumi-kubernetes/issues/520 - we’re currently working on fixes for several related issues. Current workaround would be removing the resource and then recreating in the new namespace.

Okay thanks. Is it part of the current milestone ?

Yes, and fixes are in progress

If you have a namespace tranformation, that's could be an issue, because ClusterRoleBinding is namespace independent, but when adding namespace to it, pulumi will use that during naming, so changing the namespace, force recreate the resource, we had the same problem, recreated it without the namespace, so next time we won't have this problem and made our transformation code a little bit smarter

When you say recreated without a namespace, you mean it went into the default or whatever the helm chart put as default for namespace ? @cold-coat-35200

Recreated without the metadata.namespace field, so it went to whatever kubernetes put cluster wide resources, but with this change the pulumi does not contained the namespace anymore

Okay got it