Update IP Spaces Floating IPs comment

[srekkas]

Describe the bug

IP comment show bad info from non existing deleted cluster.

Reproduction steps

1. Create cluster
2. Create service with Load balancer
3. Get External IP
4. Delete that cluster
5. Create new
6. Create service with Load Balancer and specify IP which was used on cluster before

Expected behavior

Comment contains new cluster and service info.

Additional context

No response

[arunmk]

CPI will not automatically delete LBs when a cluster is deleted. This is likely common to all CPIs.

Even if not, we do so by design. We delegate the responsibility uninstall LB applications to the cluster owner before deleting the cluster. We cannot auto-delete such resources since these may be sensitive (someone may have many DNS rules set on an IP, for example).

[srekkas]

CPI will not automatically delete LBs when a cluster is deleted. This is likely common to all CPIs.

Even if not, we do so by design. We delegate the responsibility uninstall LB applications to the cluster owner before deleting the cluster. We cannot auto-delete such resources since these may be sensitive (someone may have many DNS rules set on an IP, for example).

But i think it must be an option, because everything what is created dynamical, must be option to delete it dynamically.
So if we or customer create cluster from webui or something like terraform, create multiple pvc, services with load loadbalancers, and maybe everything dynamicaly with gitops. After that cluster get deleted and many do not think to cleanup everything. So Loadbalancers can use limited external IPs, which have some cost and inconveniences to cleanup everything.

And in this case, i see some comment on that IP, which says IP is used by non existing cluster, it complicates manual cleanup even further. Maybe comment can be refreshed every so often?