Add more overrides for rpc bind address and server broadcast address

[the-glu]

This PR adds optional options to overrides the rpc bind address on master and tserver, and server_broadcast_address on the master (already present on the tserver).

[kv83821-yb]

Hi @the-glu
Can you please add some more context on this ?
Right now, we set the rpc_bind_address as the POD_IP except for Multi-Cluster cases.
The broadcast address is set to pod fqdn. Are you trying to work with any specific MCS setup ?

[the-glu]

Hello,

Right now, we set the rpc_bind_address as the POD_IP except for Multi-Cluster cases. The broadcast address is set to pod fqdn. Are you trying to work with any specific MCS setup ?

Yes, I'm trying to do a multi cluster setup and yugaybe is using the private_rpc_address even with use_public_ip=never: yugabyte/yugabyte-db#27367

With thoses I'm able to work around the issue by forcing the private_rpc_address to a public one :)

[kv83821-yb]

Which mcs flavor is this ? we can perhaps try to add support for that itself instead of providing direct overrides ? cc: @amannijhawan

Right now we support gke, istio, ocp mcs

[the-glu]

I did try with gke and eks, but I'm not sure it's directly related to the provider

[amannijhawan]

How will this work in case of multiple masters? Are we mostly setting it to 0.0.0.0?

[the-glu]

It's a override in case of someone would like to update it. Without anything set, it will use the server_broadcast_address template, who include the server fqdn

[amannijhawan]

Added a comment, How will this work if we have more than 1 master deployed with the chart ?