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

Workaround I'm thinking of is to use `pulumi.Command` + the `deleted_with` option on the Namespace, so that I can do a soft delete with `kubectl` directly (ie, mark as terminated, and let the cluster take care of it once all the finalizers are finished)

Having `skipAwait` specific to creation/update/delete steps would be handy, though!

Using a different workaround with `NamespacePatch`, but requires refreshes before the update that deletes the NS.

For reference:
```k8s.core.v1.NamespacePatch(
    self.name,
    opts=self._default_opts.merge(p.ResourceOptions(depends_on=[ns], deleted_with=ns)),
    metadata=k8s.meta.v1.ObjectMetaArgs(
        name=ns.metadata["name"],
        annotations={
            "<http://pulumi.com/skipAwait|pulumi.com/skipAwait>": "true",
        },
    ),
)```


(`_default_opts` is just `parent=self` in this case)