Deploy RawKV as accessible outside of cluster

How can I deploy a RawKV setup (TiKV + PD nodes only, no TiDB SQL layer) for an application like JuiceFS such that the resources (both PD and TiKV is needed by the client) are available for access by clients outside of the cluster?

JuiceFS uses a PD address as its entry point to begin communication, then it must talk to the TiKV nodes it discovers directly.

Part of the problem is that the PD will report cluster-internal DNS names for discovery to the outside if a load balancer is used to access the PD, and this behavior does not seem exposed to change in the operator.

Allowing modification of advertise-client-urls could be useful:

https://tikv.org/docs/6.1/deploy/configure/pd-command-line/#--advertise-client-urls

In some situations such as in the Docker or NAT network environment, if a client cannot access PD through the default client URLs listened to by PD, you must manually set the advertise client URLs.