steep-portugal-37539
11/03/2021, 4:08 PMdependsOn
on the ingresses to be be [ALB, ED]
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-88869
11/03/2021, 11:51 PMsteep-portugal-37539
11/04/2021, 1:08 AMbillowy-army-68599
11/04/2021, 1:56 AMsteep-portugal-37539
11/04/2021, 3:03 AMfuture-refrigerator-88869
11/04/2021, 9:01 AMsteep-portugal-37539
11/04/2021, 6:50 PMfuture-refrigerator-88869
11/04/2021, 6:54 PMindex
and TraefikRoute
steep-portugal-37539
11/04/2021, 8:00 PMbillowy-army-68599
11/04/2021, 8:05 PMsteep-portugal-37539
11/04/2021, 8:06 PMfuture-refrigerator-88869
11/04/2021, 8:14 PMsteep-portugal-37539
11/04/2021, 8:25 PMbillowy-army-68599
11/04/2021, 9:09 PMtype=LoadBalancer
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 resourcessteep-portugal-37539
11/05/2021, 3:35 AMtargetgroupbindings.elbv2.k8s.aws
, 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 targetgroupbindings.elbv2.k8s.aws
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.