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

it's only at the resource level:
<https://www.pulumi.com/registry/packages/kubernetes/installation-configuration/#annotations>

How does your link relate to this one: <https://www.pulumi.com/docs/intro/concepts/resources/#customtimeouts>

custom timeouts are available for all resources, but our Kubernetes provider also has custom await options which can be overridden via annotations

There's some nuances to each option. Timeouts at the resource level are for resource CRUD operations. Timeouts on Kubernetes annotations allow finer control over the lifecycle / readiness of those resources. SkipAwait might be what you're looking for and I'd love to see this available at a provider level. Leave it with me :grinning: