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
docs(k8s): Simplify tunnel secret creation in deployment guide (cloudflare#25751)
-In the Kubernetes deployment guide for Cloudflare Tunnel, this change simplifies how the tunnel token is stored in a secret.
-The guide is updated to use the `stringData` field instead of the `data` field in the Kubernetes Secret manifest.
-This allows users to provide the tunnel token as a plain string without needing to manually base64 encode it, making the process easier and less prone to errors.
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/connections/connect-networks/deployment-guides/kubernetes.mdx
+7-19Lines changed: 7 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -169,38 +169,26 @@ Leave the Cloudflare Tunnel browser tab open while we focus on the Kubernetes de
169
169
170
170
## 4. Store the tunnel token
171
171
172
-
`cloudflared` uses a tunnel token to run a remotely-managed Cloudflare Tunnel. You can store the tunnel token in a [Kubernetes secret](https://kubernetes.io/docs/concepts/configuration/secret/), which requires data to be encoded as a base64-encoded string. The encoding is not meant to protect the token from being read but to allow for the safe handling of binary data within Kubernetes.
172
+
`cloudflared` uses a tunnel token to run a remotely-managed Cloudflare Tunnel. You can store the tunnel token in a [Kubernetes secret](https://kubernetes.io/docs/concepts/configuration/secret/).
173
173
174
-
1. Convert the tunnel token into base64 format:
175
-
176
-
```sh
177
-
'eyJhIjoiNWFiNGU5Z...'| base64
178
-
```
179
-
180
-
```sh output
181
-
ZXlKa...NKOQo=
182
-
```
183
-
184
-
2. In GKE Cloud Shell, create a `tunnel-token.yaml` file with the following content. Make sure to replace `<base64_tunnel_token>` with your base64-encoded token value (`ZXlKa...NKOQo=`).
174
+
1. In GKE Cloud Shell, create a `tunnel-token.yaml` file with the following content. Make sure to replace `<YOUR_TUNNEL_TOKEN>` with your tunnel token (`eyJhIjoiNWFiNGU5Z...`).
0 commit comments