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

The recreation of the Service leads to a "resource already exists" error

Or am I completely of with my assumptions?

it fails at service.go:
// Create endpoint watcher.
    endpointWatcher, err := endpointsClient.Watch(context.TODO(), metav1.ListOptions{})
    if err != nil {
        return errors.Wrapf(err,
            "Could not create watcher for Endpoint objects associated with Service %q",
            sia.config.currentInputs.GetName())
    }
    defer endpointWatcher.Stop()
line 136

See <https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/|https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/> for some details on the logic Pulumi uses to wait for resources to become ready after creation/update in Kubernetes. That post also describes a feature that can be used to disable the wait logic on an individual resource, which might be what you need here. 

<@UB3BGTV63> Thanks It gave me a lot of insight on the logic. I found the Watch implementation in the go code but I am fairly new to go and struggling to actually find where the error is coming from . I will try increasing the timeout and disabling it. I wounder though of how to distinguish why exactly it failed... Is it a permissions issue, which it seems to be I got get and list ep permissions for the k8s cluster in question but still the watcher fails immediately. The only thing which works is disabling the watcher alltogether.