Nginx Fabric Gateway doesn't support addresses specification

[nowjean]

Is your enhancement request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

When i set addresses value to spec, i got error: spec.addresses: Forbidden: addresses are not supported

What would you like to be added:
A clear and concise description of what you would like to be added.

Gateway support addresses specification for ip addresses.

Why this is needed:
Explain why this enhancement is needed.
It's supported by Gateway.
Please refer to refer to https://gateway-api.sigs.k8s.io/reference/spec/#gatewayspecaddress

Additional context
Add any other context or screenshots about the enhancement request here.

Helm chart only supports, one loadBalancerIP. from v2.0, each Gateway needed own ip address.

[nginx-bot]

Hi @nowjean! Welcome to the project! 🎉

Thanks for opening this issue!
Be sure to check out our Contributing Guidelines and the Issue Lifecycle while you wait for someone on the team to take a look at this.

[sklirg]

I think this is the same as this: #2944
Although that one is a bit vague in which field it actually wants to implement, I understand it to be Gateway.spec.addresses.

[mpstefan]

Hey @nowjean, we do have an issue for it above as @sklirg pointed out, slotted for 2.2 currently. It will be Gateway.spec.addresses, yes.

As a follow up question, what are you looking at using this feature for? Does this enable a use case for you that isn't possible without it?

[nowjean]

Hey @nowjean, we do have an issue for it above as @sklirg pointed out, slotted for 2.2 currently. It will be Gateway.spec.addresses, yes.

As a follow up question, what are you looking at using this feature for? Does this enable a use case for you that isn't possible without it?

@mpstefan Hi. Yes, I want to assign a specific IP address to each Gateway LoadBalancer service. I expect v2.2 👍

[ciarams87]

Hi @nowjean

With the new architecture, we support configuring the LoadBalancer IP for the Gateway service through the Service Spec in the NginxProxy resource.

I think this should work for your use case?