Its more of a feature request than a issue.

My deployment model for Redis is in cloud where the Redis servers are running in different subnet lets say A and the redis clients are running in different subnet lets say B. Also there are some route rule restriction across the subnet and the only point of entry to the subnet A is via a preconfigured NAT Gateway(with a floating IP) where we provide the list of ports to be accepted. In this use case, we need a configuration where the NAT GW IP is configured and the Redis server will use this IP while providing response for Redis cluster commands like CLUSTER NODES, CLUSTER SLOTS. According to the current implementation, clients will receive the subnet A ip addresses in the cluster commands which aren't reachable from subnet B but if I configure the announce ip with NAT GW IP then the Redis cluster won't be able to communicate with each other.

How are we handling this currently?
As a workaround, we are maintaining a mapping table on the client side and after fetching the response of cluster commands, we are replacing the subnet A ip with the NAT GW IP and then establishing connection to Redis server.

Since Redis is powerful and is used in many use cases, still there are some challenges while deploying it over cloud.