With docker edition, to setup cache refresh, we point the oxTrust server
by IP, using the Node IP that docker assigns to it.
With something like Kubernetes on Docker, if the pod gets destroyed and
new one is created, it will have a new IP address.
This means that in order for the Cache Refresh to work in the
docker/kubernetes environment I would need to update the cache refresh
config with a new IP address. The change is not automated. Otherwise
cache refresh will stop working.
In a regular deployment scenario cluster manager would handle updating
that bit when new oxTrust server needs to become a cache refresh