Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
b
big-potato-91793
12/08/2021, 7:53 PMQuestion 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?
q
quiet-wolf-18467
12/08/2021, 8:18 PMPulumi 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
b
big-potato-91793
12/08/2021, 8:30 PMPerfect! That is what I wanted to hear!
b
billowy-army-68599
12/08/2021, 10:00 PM@big-potato-91793 is this the aws load balancer controller? it's notorious for having issues with rule clean up on finalizer
b
big-potato-91793
12/08/2021, 10:01 PMYes 😞
b
billowy-army-68599
12/08/2021, 10:02 PMwhat exactly are you deleting when you run the delete? the ingress rule?
these are the related issues 😞
https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+finalizer
b
big-potato-91793
12/08/2021, 10:04 PMWe 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 😁