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

You can specify `dependsOn'  on the ingress resources <https://www.pulumi.com/docs/intro/concepts/programming-model/#dependson>

Ok, that didn't do it. The dependency _is_ being honored, but I'm guessing it's too fast and the controller isn't able to react to the Ingress deletion quickly enough.

Deleted resource kubernetes:extensions:Ingress • alb-istio-ingress 6 minutes ago
Deleted resource kubernetes:<http://rbac.authorization.k8s.io:ClusterRoleBinding|rbac.authorization.k8s.io:ClusterRoleBinding> • istio-system/aws-alb-ingress-controller 6 minutes ago
Deleted resource kubernetes:core:ServiceAccount • istio-system/aws-alb-ingress-controller 6 minutes ago

Deleted resource kubernetes:<http://rbac.authorization.k8s.io:ClusterRole|rbac.authorization.k8s.io:ClusterRole> • istio-system/aws-alb-ingress-controller 6 minutes ago
Deleted resource kubernetes:apps:Deployment • istio-system/aws-alb-ingress-controller 6 minutes ago

do you need the ingress controller to pick-up the deletion of the ingress if the controller itself is being deleted a well?

We just moved away from the aws alb ingress controller to `nginx-ingress` for this reason. Creating all your routes inside one ingress resource was getting troublesome.

crap. unfortunately i don't have that option.

only thing I can think of is adding a sleep inside the `.apply` method of the ingress

but that would run the sleep every time your create it as well