Skip to content

Commit b5ed101

Browse files
committed
update link
1 parent 571cb50 commit b5ed101

File tree

1 file changed

+2
-4
lines changed
  • src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability

1 file changed

+2
-4
lines changed

src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/index.mdx

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -69,10 +69,8 @@ This will output your tunnel UUID as well as two Connector IDs, one for each `cl
6969

7070
You can run the same tunnel across various `cloudflared` processes for up to 100 connections (25 replicas) per tunnel. Cloudflare Load Balancers and DNS records can still point to the tunnel and its UUID. Traffic will be sent to all `cloudflared` processes associated with the tunnel.
7171

72-
:::note[Deploy replicas with Kubernetes]
73-
74-
For information about running `cloudflared` instances in a Kubernetes deployment, refer to our guides for tunnels managed [remotely via the dashboard](/cloudflare-one/connections/connect-networks/deployment-guides/kubernetes/) or [locally via the CLI](/cloudflare-one/tutorials/many-cfd-one-tunnel/).
75-
72+
:::note[Deploy replicas in Kubernetes]
73+
For information about running `cloudflared` in a Kubernetes deployment, refer to the [Kubernetes guide](/cloudflare-one/connections/connect-networks/deployment-guides/kubernetes/).
7674
:::
7775

7876
## Cloudflare Load Balancers

0 commit comments

Comments
 (0)