The Dell team was initially running tunnels on Windows VMs and providing a set of static tunnels for users, configured to access various test environments. They used custom DNS servers to access test environments, and the DNS server settings of SauceConnect to control name resolution for those tunnels. They needed more flexibility in name resolution, so we tried using HOSTS files, but all tunnels on a single VM would have to use the same HOSTS file, limiting the flexibility. Using Kubernetes containers allows the team to run a single tunnel in its own container, with its own HOSTS file, thus allowing users to have custom tunnels with fully controlled DNS resolution. In this session, Morgan Vergara explains how this enabled them to set up an infrastructure that allows users to set up custom tunnels on demand.

1. SauceConnect Tunnels
on Kubernetes
Providing tunnels on demand

2. © Copyright 2019 Dell Inc.2 of Y
The problem

3. © Copyright 2019 Dell Inc.3 of Y
The solution… or part of it

4. © Copyright 2019 Dell Inc.4 of Y
The other parts of the solution

5. © Copyright 2019 Dell Inc.5 of Y
Behind the scenes
• Tunnel Manager
A web application that allows users to manually create tunnels ad-hoc.
• Tunnel Arbiter
A web application that shows a list of existing tunnels, and also runs a periodic process to shutdown
expired tunnels.
• TunnelCLI
A command line utility used in the CI/CD pipeline that calls the web service to create tunnels.

6. © Copyright 2019 Dell Inc.6 of Y
Questions?