Inlets, a Cloud Native Tunnel written in Go, combines a reverse proxy and websocket tunnels to expose your internal and development endpoints to the public Internet via an exit-node.
This chart bootstraps an Inlets deployment, service and ingress on a Kubernetes cluster using the Helm package manager.
For larger teams working on projects with webhooks like Stripe and Slack, it can become a little bit expensive when all members have a running exit-node to demo or test their stuff. Inlets is such a lightweight tool, and it can smoothly run in a container. When deployed on a Kubernetes cluster, many Inlets servers can share a single exit-node.
Some cloud providers, like DigitalOcean or Scaleway have quite cheap Kubernetes services. (On Scaleway you can get a single node Kubernetes cluster for €7.99/month)
An Ingress Controller (nginx-ingress, traefik, ...) up and running in your Kubernetes cluster.
A wildcard DNS (e.g. *.example.com) A record pointing to the public ip adress of your Ingress Controller
Add repository to Helm:
helm repo add inlets TODOYou can update the chart repository by running:
helm repo updateInstall an Inlets server, e.g.:
helm install bumblebee inlets/inlets --set inlets.domain example.com --set inlets.token=<your token>As soon the deployment is ready, and the ingress is picked up by the controller, you can connect to the server with an Inlets client, e.g.:
export UPSTREAM=http://127.0.0.1:8000
inlets client \
--remote=ws://bumblebee.example.com \
--token <your token> \
--upstream $UPSTREAMMost of the Ingress controllers support SSL termination. At this moment the ingress created by this chart does not support HTTPS / TLS yet.
The following table lists the configurable parameters of the inlets chart and their default values.
| Parameter | Description | Default |
|---|---|---|
inlets.domain |
your domain | |
inlets.token |
token for authentication | |
inlets.image.repository |
inlets container image repository | inlets/inlets |
inlets.image.tag |
inlets container image tag | 2.7.0 |