Service to bridge Tentacles to allow jumping between networks
Imagine an environment where people normally RDP to a VM in a kind of "DMZ", in order to then be able to access other machines in the network. The VM might have two NIC's - on on the same network as the Octopus server, the other on the same network as the Tentacles that we want to deploy to.
If we had a bridge service that allowed us to "hop"/"jump" between networks, so that Octopus could send commands to the bridge that are ultimately destined for the Tentacles, it would make it possible to deploy across these disparate networks.
In Octopus, we'd need the concept of a "Bridge", and when Tentacles are registered we'd associate them with a bridge. At the comms layer we'd then know that messages destined for the Tentacle (or from the Tentacle) come via that bridge. Bridges could be behind other bridges, allowing us to traverse some pretty complicated network schemes.
Paul Stovell
shared this idea
-
Is there any reason that our existing proxy support does not meet these needs?
https://octopus.com/docs/infrastructure/windows-targets/proxy-support -
Ben Norman
commented
I am working with a Bastion Host which does not have a VPN. The Bastion is able to communicate with the deployment target hosts. Its a 2 jump access scenario. Jump to the Bastion Host and then jump to the Deployment Target host. If I had a "Jump Tenticle" on the bastion server which provided a communication pathway with the Deployment Tenticle from the Octopus Server, then that would allow listening tenticles to be installed on deployment targets and no change to the Octopus Server Network or Target Network.
