Expose services without relying on a SaaS.

UK
Joined October 2019
Release Friday for @inletsdev tunnels (0.10.0)! 👉 Add OAuth/Basic Auth/Bearer Tokens to local HTTP endpoints 👉 Modify HTTP request/response headers v0 was used to make the HTML pretty for the OAuth flow, link below 👇
1
1
11
4,051
WIP: Add OAuth to any HTTP endpoint exposed over an @inletsdev tunnel. Think Prometheus, a draft blog post, a fileserver (as pictured). Only your friends or colleagues that you specify can get in with their GitHub / Gmail etc.
1
5
897
We had an email from a new @inletsdev customer asking how to expose the @argoproj dashboard from his local KinD cluster using @IstioMesh Here's a quick walkthrough on how you can do it too: inlets.dev/blog/tutorial/202…
1
4
753
Replying to @denicmarko
Use @inletsdev by @alexellisuk or the #ngrok to permit the world to access your fresh new project 😇
1
2
351
The on-prem movement is happening for realllll 😳 All you folks are talking about cl0udflare but a highly underrated tech is @inletsdev Literally the tunnel for all your connectivity needs. It solves the load-balancer requirement for Kubernetes nicely.
5
1
15
824
通过 K8s 集群访问本地 Ollama 模型 @inletsdev + @ollama 作者 @alexellisuk 的文章主要讨论了如何使用私有隧道技术将本地 Ollama 服务连接到远程 K8s 集群, 为希望利用本地 GPU 资源, 同时需要云端弹性的用户提供了解决方案。 为什么不应使用 VPN 将本地主机直接加入云端 K8s 集群: - K8s 设计用于低延迟、可预测的网络环境, 不适合跨 WAN 使用 - 会导致 API 访问延迟高 - 需要大量带宽, 会产生额外费用 - 本地节点完全暴露给云集群, 缺乏安全边界 - 需要复杂的调度规则 使用 inlets 隧道的优势: - 最小化带宽使用 - 降低本地网络风险, 只暴露特定端口和端点 - 易于通过普通 ClusterIP 访问隧道服务 设置步骤: - 在本地机器上设置 K3s 和 nvidia-containerd - 创建云端 K8s 集群 - 打包并部署 Ollama 及模型到本地 K3s 集群 - 在公共 K8s 集群上创建 HTTPS 隧道服务器 - 在本地 K3s 集群上创建 HTTPS 隧道客户端 - 在公共集群中启动 curl Pod, 通过隧道调用 Ollama 模型 原文链接: inlets.dev/blog/2024/08/09/l…
3
13
3,157
I just met with developers at an AI start-up, who'd used @inletsdev just like in this blog post to connect cheaper GPU-enabled services into their AWS EKS clusters in prod & dev inlets.dev/blog/2024/08/09/l…
1
3
2
15
5,536
I just tried out a demo of @inletsdev cloud - hosted tunnels for Kubernetes ingress. After signing in and verifying a domain with a TXT record, you can hook up your ingress controller by pasting in some YAML.
1
1
7
1,169
I just walked a customer through how to expose Kubernetes Ingress from a private production cluster using EC2 with @inletsdev. We did everything manually to understand the moving pieces. Here's the automated way with @Hetzner_Online in ~ 30s. inlets.dev/blog/2024/08/15/i…
1
1
14
1,045
"How do I connect my local GPU node to my cloud Kubernetes cluster to run @ollama?" That might be the wrong question. REST APIs or message queues are a better fit than adding a high latency node to a K8s cluster over a VPN inlets.dev/blog/2024/08/09/l…
1
11
939
Want to get a public LoadBalancer for ingress-nginx, Kong, Traefik, Istio, etc from any K8s cluster? Reply and I'll send you free access to try out @inletsdev as a SaaS, where we host the tunnel server for you.
1
1
6
3,701
Just gave this a try to get ingress for my OpenFaaS development gateway running in a private k3d cluster.
1
2
2
850
About 30s from creating a Service with type LoadBalancer, to a fully working endpoint. And I'm sat in a cafe running KinD with WiFi.
1
1
2
989
Some general maintenance on @inletsdev tooling: ✅ Ubuntu 22.04 for tunnel hosts ✅ Civo / Equinix Metal are dropped as providers ✅Moved to the new CX22 instance on @Hetzner_Online Thanks to J R Hilling for a great review of the inlets-operator on @gumroad 👌
1
1
8
1,863
I was on a call yesterday with someone who wanted to expose ~ 5 services each from different on-premises tenant Kubernetes clusters. Here's a brief guide without any automation, to see all the moving parts with @inletsdev inlets.dev/blog/2024/06/06/t…
1
4
959
Here's the video on @inletsdev if you're interested in seeing what it looks like: youtube.com/watch?v=SdKsy35s…
1
1
857
When I first created inletsctl to provision TCP/HTTPS tunnel server VMs - I thought that it'd be mainly for personal use in your own account @fruit_case told us a story last week of how the auto-generated name meant a team-mate deleted his tunnel server! Let's fix that.
1
1
11
1,886