GCP IpRange Reconciler fails with error "Service Networking Operation error : Allocated IP range 'ip-a2202b1' not found in network."

[ravi-shankar-sap]

Description
This issue was identified in the staging environment while de-provisioning a skr cluster. https://github.tools.sap/kyma/backlog/issues/6082

The user actions leading to the problem was provided as part of this gardener ticket: https://github.tools.sap/kubernetes-live/issues-live/issues/5472

Expected result

When the Allocated IpAddress Range was manually deleted, the reconciler should have re-created it again, and the IpRange should have gone into Ready state.

Actual result

The GCP IpRange Reconciler could not able to add the Ip Address Range to the Service Connection. It was continuously failing with the error message Service Networking Operation error : Allocated IP range 'ip-a2202b1' not found in network.

Steps to reproduce

Troubleshooting

[ravi-shankar-sap]

Analysis of the issue:

• The IpRange was created before the fix for unique name issue (GcpNfsVolume provisioning failed #372) was applied.
• GCP Address Range was originally created with the name ip-a2202b1
• When this address was manually deleted in GCP, the reconciler detected the missing address range, and created the new Address Range with the new naming convention cm-<kcp-ip-range> i.e. cm-389395ad-812a-49fa-a269-6f94acc95233
• The reconciler was able to add this address in GCP, but not able to add this address name to the PSA Service Connection. It was caused as GCP validates the names in the list and the request still has the old name ip-a2202b1 in the list.