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

I'm deploying a nginx-ingress helm chart on AKS to provision a private loadbalancer.
```new k8s.helm.v3.Chart(name, {
    chart: "nginx-ingress",
    version: "1.36.3",
    fetchOpts: {
        repo: "<https://kubernetes-charts.storage.googleapis.com>",
    },
    values: {
        controller: {
            service: {
                loadBalancerIP: props.backendIpAddress,
                annotations: {
                    "<http://service.beta.kubernetes.io/azure-load-balancer-internal|service.beta.kubernetes.io/azure-load-balancer-internal>": "true"
                }
            },
        }
    },
})```
In my case the cluster gets recreated and the Kubernetes provider tries to deploy the helm chart on the new cluster with the same IP address.
Because the IP address is still allocated by the old loadbalancer, it will fail.
Do you got any ideas on how to delete the old service/loadbalancer before the new one gets created?