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'm trying to deploy changes to k8s namespaces (added custom timeouts), and the pulumi planner wants to delete-replace the namespace, and that errors out - the Namespace gets stuck "Terminating" state in k8s. I think the reason is due to the fact there are deployments, etc, which depend on that namespace, and pulumi doesn't take those into account when planning

Anyone have any ideas about how deal with that?

For example, can I force pulumi to update the existing namespace as opposed to delete-repalce?

it's unlikely that it's deployments, they will do a cascading delete. It's probably a finalizer

Can pulumi update the namespace instead of replacing?