This is my use case:
We have multiple clusters in multiple regions from which we have the ability to announce public anycast IPs.
We have successfully done so adding the advertisement to BGPConfiguration (we do need to set the community for these IPs).
However, this brings the need for service team to sync with the team managing the cluster if they need to stop the service in one region for whatever reason. Otherwise, the IPs are still advertised from a cluster that has no service backing them anymore.
We are pleased about how those ClusterIP announcements work/perform, so we would like to keep using services of type ClusterIP, but we want to be able to make developers own when those IPs are advertised from the cluster.