Stale NBs are left when deleting the underlying K8S cluster

General:

• Have you removed all sensitive information, including but not limited to access keys and passwords?
• Have you checked to ensure there aren't other open or closed Pull Requests for the same bug/feature/question?

Bug Reporting

When using the Linode CCM in K8S clusters and deleting the underlying cluster while not deleting the Service leaves a stable NB in the Linode account.

Expected Behavior

Explore having some kind of finalization mechanism to delete the NB when the cluster is being deleted

Actual Behavior

Stale NBs are left in place

Steps to Reproduce the Problem

1. Create a K8S cluster with the linode-ccm installed on it
2. Provision a Service of type LoadBalancer
3. Delete the control plane and nodes of the cluster

Environment Specifications

This happens for KPP clusters but also was reported by externally facing customers who are not using KPP

Additional Notes

I'm not really sure we can address this in the linode-ccm and may need to address it at a platform level but wanted to have this logged and tracked somewhere

For general help or discussion, join the Kubernetes Slack team channel #linode. To sign up, use the Kubernetes Slack inviter.

The Linode Community is a great place to get additional support.

Inizia riproducendo il problema con un cluster Kubernetes Linode CCM, un Service di tipo LoadBalancer e l'eliminazione del control plane e dei nodi mantenendo il Service. Verifica se la pulizia debba essere gestita da Linode CCM o a livello di piattaforma e determina il punto di finalizzazione appropriato. Il lavoro è completato quando il NodeBalancer sottostante viene rimosso alla cancellazione del cluster, oppure quando viene documentato il confine di ownership se CCM non può risolvere il problema.