inlets

Expose services without relying on a SaaS.

[inlets @inletsdev]

Quick demo of HTTPS tunnels with a generated domain

Europe, Asia or US East
Automated HTTP to HTTPS
Instantly up and ready

https://t.co/nrivS20XIt

[inlets @inletsdev]

Here's what it looks like exposing node_exporter from a local machine - the HTTP endpoint got TLS terminated with a randomly generated domain

Sign up for access: https://t.co/gwHX9enpfS

[inlets @inletsdev]

We've rolled out a couple of new features on inlets cloud today:

1) Use our domain for your tunnels, so you don't have to verify one to try it out.
2) HTTP tunnels where we terminate TLS for you via Let's Encrypt, instead of using Caddy or K8s Ingress

[Alex Ellis @alexellisuk]

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 👇

[Alex Ellis @alexellisuk]

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.

[Alex Ellis @alexellisuk]

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:
https://t.co/T71vm8tiG8

[dadideo 🌍 framapiaf.org 🐘&🟦 @dadideo]

@denicmarko Use @inletsdev by @alexellisuk or the #ngrok to permit the world to access your fresh new project 😇

[inlets @inletsdev]

@virtualized6ix Thanks Marino 🙏

Have you tried the cloud hosted version yet? It's free in beta and means you don't need to host your tunnel server.

With a US, Asia and EU region - you can expose kubectl, Istio, Ingress, Caddy/Nginx and SSH. Just copy/paste the client YAML or command line

[inlets @inletsdev]

SSH Into Any Private Host With Inlets Cloud

#remoteaccess #saas #multiplexer #itsupport
https://t.co/IyuRQTm5Mg

[meng shao @shao__meng]

通过 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 模型

原文链接:
https://t.co/Bk7P2270K7

[Alex Ellis @alexellisuk]

Getting real client IPs from your @inletsdev tunnel with @caddyserver, @traefik and @IngressNGINX

#tunnels #selfhosting #homelab #proxyprotocol
https://t.co/G1NOB69tcO

[inlets @inletsdev]

Create Highly Available Tunnels With A Load Balancer and Proxy Protocol

#tunnels #selfhosted #privacy #highlyavailable
https://t.co/aKdY1qGsjV

[Alex Ellis @alexellisuk]

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

https://t.co/ddSXOcRKcl

[Alex Ellis @alexellisuk]

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.

[Alex Ellis @alexellisuk]

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.
https://t.co/rKrS0w2z21

[inlets @inletsdev]

Is creating a distributed Kubernetes cluster with a VPN the right approach? @alexellisuk shows a demo of an alternative using a HTTP REST API and @ollama as an example

https://t.co/omTufOmFj2

[Alex Ellis @alexellisuk]

"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
https://t.co/ddSXOcSi1T

[Alex Ellis @alexellisuk]

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.

[inlets @inletsdev]

The same inlets experience, but with a hosted tunnel that you don't have to manage or think about

#expose #kubernetes #ingress #istio
https://t.co/DbCo4Mu5YA