External Reflector Deployment
A static reflector can run inside the Kubernetes cluster, or outside on an external server host. When deployed outside of Kubernetes, the static reflector is delivered as a child process of ICE Agent. Install ICE Agent on Linux, Windows, macOS or Docker, and start the reflector using the agent external reflector command (consult the product guide for details).
As is true for patch servers, the agent assumes responsibility for communications with the ICE Server and supplying configuration data to the reflector. Similarly, the two containers communicate with each other through configuration and status files written to a shared mount point :
The agent writes conf/ice_reflector_peers.json with a set of channels to be reflected and conf/ice_reflector_config.json with process-level configuration similar to that provided for patch servers.The reflector writes status/ice_reflector_status.json with the server's operational report (viewable in human readable form in ICE Desktop 'Static Reflectors' settings).Under the hood, a static reflector is a specially configured Rallypoint. You’re advised to ignore this technical implementation detail, though. These 'Rallypoints' should not be substituted for real Rallypoints in your network.