NAT-aware Public-Private GSLB

[charri]

As stated in the GSLB docs:

Typically, the VIP configured in a local virtual service (configured as a GSLB pool member) is a private IP address. But this IP address may not always be reachable by the client.
In the GSLB pool member configuration, an optional public IP address can be specified

Currently this setup is not configurable with AMKO.
It would be great if there way to specify a mapping (via configmap key: internal ip, value: external ip) or extend the current GSLBConfig/GlobalDeploymentPolicy.

As a temp workaround I am setting the values via the API, but this leaves a window where requests are not answered on the gslb for external clients.

[tofele]

I would like to emphasize that this is still an important topic for us and would appreciate if this would get some attention.

[swathinsankaran]

Hi @charri, @tofele, This feature is merged to the AMKO and it will be available in the next release which is 1.10.1.
Thanks,
Swathin