Skip to content

Commit 92080b8

Browse files
committed
tunnel route
1 parent e6fa85c commit 92080b8

File tree

1 file changed

+39
-4
lines changed
  • src/content/docs/cloudflare-one/connections/connect-networks/deployment-guides

1 file changed

+39
-4
lines changed

src/content/docs/cloudflare-one/connections/connect-networks/deployment-guides/kubernetes.mdx

Lines changed: 39 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -163,7 +163,7 @@ A pod represents an instance of a running process in the cluster. In this exampl
163163

164164
8. Instead of running the installation command, copy just the token value rather than the whole command. The token value is of the form `eyJhIjoiNWFiNGU5Z...` You will need the token for the Kubernetes manifest file.
165165

166-
Leave this browser tab open while we finish up the Kubernetes deployment.
166+
Leave the Cloudflare Tunnel browser tab open while we focus on the Kubernetes deployment.
167167

168168
## 4. Store the tunnel token
169169

@@ -303,8 +303,43 @@ Create a [Kubernetes secret](https://kubernetes.io/docs/concepts/configuration/s
303303

304304
You should see two `cloudflared` pods and two `httpbin` pods with a `Running` status. If your `cloudflared` pods keep restarting, make sure that your `cloudflared` [parameters](/cloudflare-one/connections/connect-networks/configure-tunnels/cloudflared-parameters/run-parameters/) are in the correct position relative to the `run` command.
305305

306-
## Verify tunnel status
306+
## 6. Verify tunnel status
307307

308-
## Add a tunnel route
308+
To print logs for a `cloudflared` instance:
309309

310-
## Test the connection
310+
```sh
311+
kubectl logs pod/cloudflared-deployment-6d5f9f9666-85l5w
312+
```
313+
314+
```sh output
315+
2025-06-11T22:00:47Z INF Starting tunnel tunnelID=64c359b6-e111-40ec-a3a9-199c2a656613
316+
2025-06-11T22:00:47Z INF Version 2025.6.0 (Checksum 72f233bb55199093961bf099ad62d491db58819df34b071ab231f622deff33ce)
317+
2025-06-11T22:00:47Z INF GOOS: linux, GOVersion: go1.24.2, GoArch: amd64
318+
2025-06-11T22:00:47Z INF Settings: map[loglevel:debug metrics:0.0.0.0:2000 no-autoupdate:true token:*****]
319+
2025-06-11T22:00:47Z INF Generated Connector ID: aff7c4a0-85a3-4ac9-8475-1e0aa1af8d94
320+
2025-06-11T22:00:47Z DBG Fetched protocol: quic
321+
2025-06-11T22:00:47Z INF Initial protocol quic
322+
...
323+
```
324+
325+
You can also verify the connection status in the Zero Trust dashboard.
326+
327+
## 7. Add a tunnel route
328+
329+
Now that the tunnel is up and running, we can use the Zero Trust dashboard to route the httpbin service through the tunnel.
330+
331+
1. Switch to the browser tab where you were configuring Cloudflare Tunnel.
332+
333+
2. Go to the **Route tunnel** step and select the **Public hostnames** tab.
334+
335+
3. Enter a hostname for the application (for example, `httpbin.<your-domain>.com`).
336+
337+
4. Under **Service**, enter `http://httpbin-service`
338+
339+
5. Select **Complete setup**.
340+
341+
## 8. Test the connection
342+
343+
To test, open a new browser tab and go to `httpbin.<your-domain>.com`. You should see the httpbin homepage.
344+
345+
You can optionally [create an Access application](/cloudflare-one/applications/configure-apps/self-hosted-public-app/) to control who can access the service.

0 commit comments

Comments
 (0)