Skip to content

Commit a750a25

Browse files
committed
Minor change to intro page
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
1 parent 16377c8 commit a750a25

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

docs/uplink/index.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,19 @@ In the first case, of accessing private customer services, you have have already
1515

1616
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.
1717

18+
## Inlets works from behind restrictive networks
19+
1820
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.
1921

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
2131

2232
* The management solution is built-in, self-hosted and runs on your own Kubernetes cluster
2333
* 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
2838
* By default all tunnels are private and only available for access by your own applications
2939
* Tunnels can also be managed through Helm, ArgoCD or Flux for a GitOps workflow
3040

41+
Support via email is included for the installation and operation of your inlets-uplink installation.
42+
3143
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).
3244

3345
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

Comments
 (0)