After removing Strimzi cluster with external loadbalancer, the Kubernetes Frontend IP configuration will not be deleted

[FlowsenAusMonotown]

I have the following configuration:

...
listeners:
        - name: external
          port: 9093
          type: loadbalancer
          tls: true
          authentication:
            type: tls
          configuration:
            bootstrap:
              annotations:
                "service.beta.kubernetes.io/azure-load-balancer-ipv4": ${azurerm_public_ip.instance_kafka_ip.ip_address}
              loadBalancerIP: ${azurerm_public_ip.instance_kafka_ip.ip_address}
            brokerCertChainAndKey:
              secretName: ${local.external-kafka-cert-secret-name}
              certificate: tls.crt
              key: tls.key
...

When removing the Kafka cluster the Kubernetes Frontend IP configuration will left over and the deletion of the public IP address will fail. How I can make sure, if the Kafka cluster is removed, that the Kubernetes Frontend IP configuration is also be deleted?

[scholzj]

I have no idea what Kubernetes Frontend IP is to be honest. But all Strimzi can do is delete the Kubernetes type: LoadBalancer service. The actual management of any load balancers or IPs is up to Kubernetes and their cloud provider.

What you can try is to add the finalizers field with the service.kubernetes.io/load-balancer-cleanup finalizer which should help Kubernetes clean all the resources when the Load balancer type service is deleted. But whether ti helps in your environment and with your problem or not, I'm not sure. You would need to try it.

[FlowsenAusMonotown]

This was it. Now the public IP address could be deleted. Thx for the fast help.