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

CustomResource if fire and forget. You can to use a kubernetes API client in the instance apply method. Or you can create a dummy pulumi resource that dependsOn the item and does the same on Create and Update.

The first is executed always. For reading a status this is fine and simpler, but for reading events (which disappear 1 hour later by default) it could cause issues. This is why I am moving to the latter.