Skip to content

Commit 122dfb2

Browse files
committed
Fix typo
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
1 parent 8acb1f3 commit 122dfb2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/uplink/ingress-for-tunnels.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88

99
Each inlets uplink tunnel is provisioned with a ClusterIP service that you can access internally within the cluster. The same service can be used to expose the tunnel to the public Internet using an Ingress resource. This approach is recommended for new users for dozens of tunnels.
1010

11-
Alternatively, the data-router component can be used along with a wild-card DNS reocrd and TLS certificate to expose many tunnels with a single Ingress record or Istio Gateway. This approach requires additional setup because the DNS01 challenge requires a special cert-manager Issuer with a secret for the DNS provider's API. It is recommended for users with many tunnels, but is more complex to setup.
11+
Alternatively, the data-router component can be used along with a wild-card DNS record and TLS certificate to expose many tunnels with a single Ingress record or Istio Gateway. This approach requires additional setup because the DNS01 challenge requires a special cert-manager Issuer with a secret for the DNS provider's API. It is recommended for users with many tunnels, but is more complex to setup.
1212

1313
## Quick start
1414

0 commit comments

Comments
 (0)