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

image.png

It could be that your service was deleted by someone with access to the cluster and because you've not used `--refresh` with `pulumi up`  it's currently unaware of that out of band change.

yeah that was my explanation too, but the service was there and only missing when the deployment is complete

then it appears the recommended approach is always `--refresh` for deployment ?