Retrying pod delete when ips failed to be fetched is not expected to succeed on retry, but floods the logs:
2023-01-14T14:14:31.659423834+00:00 stderr F I0114 14:14:31.659419       1 obj_retry.go:1066] *factory.peerPodForNamespaceAndPodSelector retry delete failed for lfs-development-arm-1/app-flex-pricer-fcp-544467c47d-rnhw9,\
 will try again later: pod lfs-development-arm-1/app-flex-pricer-fcp-544467c47d-rnhw9: no pod IPs found
2023-01-14T14:14:31.659429534+00:00 stderr F I0114 14:14:31.659423       1 obj_retry.go:1045] *factory.peerPodForNamespaceAndPodSelector lfs-development-arm-1/app-flex-pricer-eli-66b97dd566-42hft: retry object setup
2023-01-14T14:14:31.659435734+00:00 stderr F I0114 14:14:31.659428       1 obj_retry.go:1060] *factory.peerPodForNamespaceAndPodSelector retry: removing old object for lfs-development-arm-1/app-flex-pricer-eli-66b97dd566\
-42hft
2023-01-14T14:14:31.659441334+00:00 stderr F I0114 14:14:31.659436       1 obj_retry.go:1066] *factory.peerPodForNamespaceAndPodSelector retry delete failed for lfs-development-arm-1/app-flex-pricer-eli-66b97dd566-42hft,\
 will try again later: pod lfs-development-arm-1/app-flex-pricer-eli-66b97dd566-42hft: no pod IPs found
❯ grep -c 'retry delete failed for ' *
2.log.20230114-140543:64184
2.log.20230114-140934:63979
2.log.20230114-141325:65260
2.log.20230114-141717:62881

1.
2.
3.