Skip to content

Commit d79fac7

Browse files
authored
Update kubernetes.mdx
Correction to indentation
1 parent 6eb34fc commit d79fac7

File tree

1 file changed

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

1 file changed

+46
-46
lines changed

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

Lines changed: 46 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -221,52 +221,52 @@ To run the Cloudflare Tunnel in Kubernetes:
221221
apiVersion: apps/v1
222222
kind: Deployment
223223
metadata:
224-
name: cloudflared-deployment
225-
namespace: default
224+
name: cloudflared-deployment
225+
namespace: default
226226
spec:
227-
replicas: 2
228-
selector:
229-
matchLabels:
230-
pod: cloudflared
231-
template:
232-
metadata:
233-
labels:
234-
pod: cloudflared
235-
spec:
236-
securityContext:
237-
sysctls:
238-
# Allows ICMP traffic (ping, traceroute) to resources behind cloudflared.
239-
- name: net.ipv4.ping_group_range
240-
value: "65532 65532"
241-
containers:
242-
- image: cloudflare/cloudflared:latest
243-
name: cloudflared
244-
env:
245-
# Defines an environment variable for the tunnel token.
246-
- name: TUNNEL_TOKEN
247-
valueFrom:
248-
secretKeyRef:
249-
name: tunnel-token
250-
key: token
251-
command:
252-
# Configures tunnel run parameters
253-
- cloudflared
254-
- tunnel
255-
- --no-autoupdate
256-
- --loglevel
257-
- debug
258-
- --metrics
259-
- 0.0.0.0:2000
260-
- run
261-
livenessProbe:
262-
httpGet:
263-
# Cloudflared has a /ready endpoint which returns 200 if and only if
264-
# it has an active connection to Cloudflare's network.
265-
path: /ready
266-
port: 2000
267-
failureThreshold: 1
268-
initialDelaySeconds: 10
269-
periodSeconds: 10
227+
replicas: 2
228+
selector:
229+
matchLabels:
230+
pod: cloudflared
231+
template:
232+
metadata:
233+
labels:
234+
pod: cloudflared
235+
spec:
236+
securityContext:
237+
sysctls:
238+
# Allows ICMP traffic (ping, traceroute) to resources behind cloudflared.
239+
- name: net.ipv4.ping_group_range
240+
value: "65532 65532"
241+
containers:
242+
- image: cloudflare/cloudflared:latest
243+
name: cloudflared
244+
env:
245+
# Defines an environment variable for the tunnel token.
246+
- name: TUNNEL_TOKEN
247+
valueFrom:
248+
secretKeyRef:
249+
name: tunnel-token
250+
key: token
251+
command:
252+
# Configures tunnel run parameters
253+
- cloudflared
254+
- tunnel
255+
- --no-autoupdate
256+
- --loglevel
257+
- debug
258+
- --metrics
259+
- 0.0.0.0:2000
260+
- run
261+
livenessProbe:
262+
httpGet:
263+
# Cloudflared has a /ready endpoint which returns 200 if and only if
264+
# it has an active connection to Cloudflare's network.
265+
path: /ready
266+
port: 2000
267+
failureThreshold: 1
268+
initialDelaySeconds: 10
269+
periodSeconds: 10
270270
```
271271

272272
2. Deploy `cloudflared` to the cluster:
@@ -342,4 +342,4 @@ Now that the tunnel is up and running, we can use the Zero Trust dashboard to ro
342342

343343
To test, open a new browser tab and go to `httpbin.<your-domain>.com`. You should see the httpbin homepage.
344344

345-
You can optionally [create an Access application](/cloudflare-one/applications/configure-apps/self-hosted-public-app/) to control who can access the service.
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)