Oh the Proxy-ibilities! 

Well, this is a new one. So I want to start experimenting with Foundry VTT, but to properly test it, one must have it exposed to the world, or at least to the local GPS region. This was slightly problematic because the external facing port was being taking by a different website, and I was using my K8S cluster to host the Foundry VTT app. This meant that I would have to setup a proxy box to forward the correct traffic to each of the different "devices". 

Luckily, as a friend of mine pointed out, K8S already has proxy-ing ability built in. So I didn't need to setup a whole new box, but instead mock a service that exists outside the cluster as an internal service. This, at first, seemed like something that K8S was not designed to do, but I was pleasantly surprised by my friend, who had gone through the process of doing that already. So he sent me his configs for a baseline to work with, and walked me through much of the customisation for my own cluster. 

So now, I have both Foundry VTT and the original website running on the external port. I still need to experiment with Foundry, as I haven't used it much past "does this run", which isn't a valid testing amount. But I'm excited to have it running, and have the ability to start using it in a public sense.