Expose or proxy internal IPs of workers for Prometheus monitoring

In some deployments, like Fargate container deploys, it can be impossible for an external Prometheus monitoring host to directly reach workers on their published, yet private/internal network, IPs.

It would be useful if the scheduler or a process alongside the scheduler, perhaps using the "sidecar container pattern," could proxy requests to the workers from public IP/ports.