Explore 1.27 IpAddress API

[howardjohn]

There is now an IPAddress API in k8s. We should explore how or if we should use this in Istio.

One possible idea is persisting the auto-allocated service entry IP addresses.

This is still alpha so we can't depend on it for a while, but worth exploring

cc @ramaraochavali @costinm @hzxuzhonghu @keithmattix

[keithmattix]

Linking the referenced KEP: kubernetes/enhancements#1880

[hzxuzhonghu]

Great if can be used in istio, currently based on hash can have conflict

[hzxuzhonghu]

learned about that, it is to create a IPAddress object for each IP it allocated. It do not expose a way for other controller to require an IP. I am not sure should we create do IP allocating like like it using IPAddress. If so it looks like no diff for us to create a svc placeholder for SE directly.

[hanxiaop]

not stale

[howardjohn]

One area it can be used is to do AutoAllocation for ServiceEntry. This basically allows k8s to allocate us an IP and we persist it into the cluster. Avoids ~all our issues with autoallocation I think

[hzxuzhonghu]

no stale

[istio-policy-bot]

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2023-10-07. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.