2020-04-01, 16:20–16:50, Track 1 (UTC)
Everything was fine, we were developing applications for the cloud on our local laptops, until we needed to integrate with webhooks. Then things got tricky at work, all known solutions were blocked like cryptic socat commands, SSH, Ngrok, Argo Tunnels and we had no budget for an AWS account.
We needed a Cloud Native Tunnel, but just didn’t know it yet. That’s when “inlets” began as a holiday project, which then went onto score over 5k GitHub stars and dozens of community blog posts.
That was the beginning of 2019, and now we have a whole ecosystem of tooling to support Cloud Native Tunnels directly integrated into Kubernetes via an Operator and CRD, via a CLI which provisions cloud hosts automatically and a new pro edition which is commercially supported and adds automatic TLS.
This talk introduces real-world use-cases from customers such as connecting private hospital radiography scanners to the cloud for up to 10k locations in Switzerland.
We’ll compare and contrast the inlets OSS tooling to various other solutions and with a live demo, we’ll see Minikube’s LoadBalancer turn from “pending” to a real IP from public cloud. We’ll even be able to obtain a LetsEncrypt certificate on our laptop.
This talk is different from the one at San Diego, which introduced a problem around IPv4 addresses running out, and some of the ways tunnels could help us gain IPs again. The recording at San Diego also got corrupted and was lost. This talk provides an overview of the problem and gives developers and ITOps a new, essential tool for their tool belt.
I'll also be giving examples of real-world case-studies and customer interest and adoption.