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

Hey folks, we are experiencing some issues combinating pulumi and recent releases of `knative-eventing`. In detail they include a legacy kubernetes deployment with a defined replica of `0`. Unfortunately this fails the stack since `pulumi-kubernetes` executes a readiness probe after applying the resource which never fulfills. Is there any solution to this, e.g. to disable the readiness probe for a certain resource?

This is a known issue: <https://github.com/pulumi/pulumi-kubernetes/issues/605>

You should be able to work around it with the `skipAwait` annotation: <https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/#new-annotations-to-customize-kubernetes-await-logic>