You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/uplink/index.md
+13-1Lines changed: 13 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,19 @@ In the first case, of accessing private customer services, you have have already
15
15
16
16
The first two options involve considerable work both up front and in the long run. VPNs require firewall changes, specific network conditions, additional paperwork, and can have prohibitive costs associated with them.
17
17
18
+
## Inlets works from behind restrictive networks
19
+
18
20
The Inlets Uplink runs inside a private network to connect to a public server endpoint using an outbound HTTP connection. Once established, the TLS-encrypted connection is upgraded to a websocket for bi-directional communication. This means it works over NAT, firewalls, and HTTP proxies.
19
21
20
-
Here are some of the other differences between stand-alone Inlets Pro and Inlets Uplink:
22
+
## Private or Public tunnels
23
+
24
+
Depending on your use-case, you can keep the data-plane private or expose it to the Internet on a per-tunnel basis.
25
+
26
+
By default, the data-plane for each inlets-uplink tunnel is kept private and can only be accessed from within the Kubernetes cluster where inlets-uplink is installed.
27
+
28
+
You can then expose the data-plane for any tunnel to the Public Internet if required.
29
+
30
+
## Features & benefits
21
31
22
32
* The management solution is built-in, self-hosted and runs on your own Kubernetes cluster
23
33
* You can create a tunnel almost instantly via CLI, REST API or the "Tunnel" Custom Resource
@@ -28,6 +38,8 @@ Here are some of the other differences between stand-alone Inlets Pro and Inlets
28
38
* By default all tunnels are private and only available for access by your own applications
29
39
* Tunnels can also be managed through Helm, ArgoCD or Flux for a GitOps workflow
30
40
41
+
Support via email is included for the installation and operation of your inlets-uplink installation.
42
+
31
43
You can read more about why we created inlets uplink [in the product announcement](https://inlets.dev/blog/2022/11/16/service-provider-uplinks.html).
32
44
33
45
Reach out to us if you have questions or would like to see a demo: [Contact the inlets team](https://inlets.dev/contact)
0 commit comments