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

Question for k8s folks at Pulumi. We have hit a weird bug with our loadbalancer controller. We were wondering if pulumi is waiting on the finalizer to completed the deleting of a resource?

Pulumi speaks to the API server and the API server won't return the response until the finalizers have passed

So if there's a finalizer, you’ll definitely be waiting 

<@UH7UWDRC6> is this the aws load balancer controller? it's notorious for having issues with rule clean up on finalizer

what exactly are you deleting when you run the delete? the ingress rule?

these are the related issues :disappointed:
<https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+finalizer>

We have big cluster and multiples peoples can do stuff on it. We reproduced the error with helm. That create to put the controller in a stuck mode :grin: