inlets
- 5 skills
- 0 followers
- 14 hours ago last updated
- ▌ Use Inletsctl · inletsCreates and manages inlets tunnel exit-servers on cloud VMs using inletsctl. Use when asked to provision, create, or delete tunnel servers on cloud providers like DigitalOcean, AWS EC2, GCE, Azure, Linode, Hetzner, Scaleway, OVH, or Vultr.
- ▌ Use Inlets Pro · inlets bundleConfigures, runs, secures, and troubleshoots standalone Inlets Pro HTTP and TCP tunnel servers and clients. Use for raw TCP forwarding, single or multiple HTTP upstreams, automated TLS/HTTPS with DNS, shared-token control-plane authentication, HTTP Basic/Bearer/OAuth protection, IP filtering, systemd, or Kubernetes manifests.
- ▌ Use Inlets Cloud · inlets bundleCreates, connects, secures, and manages hosted Inlets Cloud HTTP and ingress tunnels with the inlets-pro cloud CLI. Use for CLI/dashboard onboarding, access-token login, generated tryinlets.dev or verified custom domains, HTTPS exposure, Bearer-protected HTTP upstreams, one-command directory sharing, snimux access to multiple SSH hosts or K3s APIs, systemd/launchd services, ACLs, or tunnel lifecycle operations.
- ▌ Use Inlets Uplink · inlets bundleCreates, connects, inspects, updates, and removes Inlets Uplink tunnels through the Kubernetes Tunnel CRD, inlets-pro tunnel CLI plugin, or REST API. Use for single or multiple TCP and HTTP upstreams, mixed-protocol tunnels, tenant namespaces, client deployment, Uplink API authentication, entitlement, or billing-capacity questions.
- ▌ Use Inlets Operator · inlets bundleInstalls, inspects, and operates the inlets-operator lifecycle for Kubernetes LoadBalancer Services and Tunnel CRs. Use when exposing a private cluster Service with a cloud VM/public IP, checking operator resources with kubectl, recreating a tunnel, or safely deleting operator-managed infrastructure.