steep-portugal-3753911/03/2021, 4:08 PM
on the ingresses to be be
so that pulumi understands that the ingresses have a dependency on these 2 Helm charts. It doesn’t seem to completely have helped.
A delay option would be nice, because then the 2 Helm charts can delete the resources within the given delay time, and only then be removed from the cluster.
future-refrigerator-8886911/03/2021, 11:51 PM
steep-portugal-3753911/04/2021, 1:08 AM
steep-portugal-3753911/04/2021, 3:03 AM
future-refrigerator-8886911/04/2021, 9:01 AM
steep-portugal-3753911/04/2021, 6:50 PM
future-refrigerator-8886911/04/2021, 6:54 PM
steep-portugal-3753911/04/2021, 8:00 PM
steep-portugal-3753911/04/2021, 8:06 PM
future-refrigerator-8886911/04/2021, 8:14 PM
steep-portugal-3753911/04/2021, 8:25 PM
which has a proper status field populated with a load balancer address. So when you delete an ingress, the controller deployment only has to update the backing traefik or nginx config, it doesn't have to reconcile any external resources
steep-portugal-3753911/05/2021, 3:35 AM
, and to the ingresses as well. I usually have to manually remove the finalizers, as pulumi gets into a stuck state of not being able to delete the
CRD. Once i remove the finalizers, it is destroyed, and then I have to do the same for the ingresses. Then pulumi is able to move on. I also have to manually delete the Loadbalancers in AWS as well as the target groups.