https://pulumi.com logo
Title
q

quiet-motorcycle-76742

04/01/2021, 3:50 PM
Hey all, I recently deployed the aws-load-balancer-controller chart into an EKS cluster with Pulumi. The actual deploy worked great, but now every
pulumi preview
is convinced that it needs to delete all the resources deployed by that chart:
└─ kubernetes:<http://helm.sh/v3:Chart|helm.sh/v3:Chart>                                                   aws-load-balancer-controller                                                 
 -      ├─ kubernetes:<http://rbac.authorization.k8s.io/v1:Role|rbac.authorization.k8s.io/v1:Role>                               default/aws-load-balancer-controller-leader-election-role         delete     
 -      ├─ kubernetes:core/v1:Secret                                                  default/aws-load-balancer-tls                                     delete     
 -      ├─ kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding>                 aws-load-balancer-controller-rolebinding                          delete     
 -      ├─ kubernetes:core/v1:ServiceAccount                                          default/aws-load-balancer-controller                              delete     
 -      ├─ kubernetes:<http://rbac.authorization.k8s.io/v1:RoleBinding|rbac.authorization.k8s.io/v1:RoleBinding>                        default/aws-load-balancer-controller-leader-election-rolebinding  delete     
 -      ├─ kubernetes:core/v1:Service                                                 default/aws-load-balancer-webhook-service                         delete     
 -      ├─ kubernetes:<http://admissionregistration.k8s.io/v1:ValidatingWebhookConfiguration|admissionregistration.k8s.io/v1:ValidatingWebhookConfiguration>  aws-load-balancer-webhook                                         delete     
 -      ├─ kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole>                        aws-load-balancer-controller-role                                 delete     
 -      ├─ kubernetes:<http://admissionregistration.k8s.io/v1:MutatingWebhookConfiguration|admissionregistration.k8s.io/v1:MutatingWebhookConfiguration>    aws-load-balancer-webhook                                         delete     
 -      ├─ kubernetes:apps/v1:Deployment                                              default/aws-load-balancer-controller                              delete     
 -      └─ kubernetes:<http://apiextensions.k8s.io/v1beta1:CustomResourceDefinition|apiextensions.k8s.io/v1beta1:CustomResourceDefinition>           targetgroupbindings.elbv2.k8s.aws                                 delete
If you actually go through with the
pulumi up
though, it (correctly) leaves all those resources alone. Has anyone seen anything like this recently? I saw a few old issues about
pulumi preview
being wrong, but none that were presently open.
b

billowy-army-68599

04/01/2021, 7:28 PM
can you share your code?
q

quiet-motorcycle-76742

04/01/2021, 7:39 PM
If you’re looking to get someone on the case, I can definitely whittle down to a small reprodution!
b

billowy-army-68599

04/01/2021, 7:51 PM
i can't see anything immediately obvious, I'm wondering if it's the transformation? can you try comment that out and see if it still tries to delete?
q

quiet-motorcycle-76742

04/01/2021, 7:54 PM
Yeah, I had the same thought earlier. Commenting it out doesn’t help unfortunately. Let me get you a small reproducer.
I figured I’d file an issue now that there’s a nice small reproduction: https://github.com/pulumi/pulumi-kubernetes/issues/1513
Actually, found a workaround, and thus improved my diagnosis. For posterity: https://github.com/pulumi/pulumi/issues/6693