Question: How does fly's proxy not send traffic to flame instances? #84
Description
This could be a question we need to ask to the Fly support team, but I'm assuming that the person/people working on this might know the answer.
Scenario:
We have a phoenix application that uses flame to spin up dynamic machines to process CPU intensive tasks. This app isn't exposed to the internet directly. We have another fly application that acts as a reverse proxy and proxies traffic to this phoenix application amongst others. We use the flycast address (described here). My understanding that this utilizes fly's internal proxy that will handle load balancing between machines, dynamically spinning up sleeping machines and such.
The question:
How does fly distinguish between normal machines and flame machines when determining where to send traffic? Is there some configuration on the fly side or flame side to prevent that proxy from proxying traffic to the flame machines?
I've gone through fly support to try and get this question answered, but they didn't seem super interested in digging into it with me and seemed to write it off as doing unsupported things. If running flame this way is unsupported, that would also be good to know.