Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions src/pages/use-cases/cloud/routing-peers-and-kubernetes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -99,8 +99,33 @@ spec:
- NET_ADMIN
- SYS_RESOURCE
- SYS_ADMIN
livenessProbe:
exec:
command: ["netbird", "status", "--check", "live"]
initialDelaySeconds: 5
periodSeconds: 10
timeoutSeconds: 5
failureThreshold: 3
readinessProbe:
exec:
command: ["netbird", "status", "--check", "ready"]
initialDelaySeconds: 5
periodSeconds: 10
timeoutSeconds: 5
failureThreshold: 3
startupProbe:
exec:
command: ["netbird", "status", "--check", "startup"]
periodSeconds: 2
timeoutSeconds: 10
failureThreshold: 30
```

The health probes use `netbird status --check` to verify the client state:
- **live**: checks that the daemon process is responsive
- **ready**: checks that the client is not in an authentication-required state (NeedsLogin, LoginFailed, SessionExpired)
- **startup**: checks that management and signal are connected, and that at least one relay server is available if any are configured

Edit your deployment.yml file, incorporating the setup key into the relevant sections.

Apply the updated deployment file to your Kubernetes cluster using the following command:
Expand Down
Loading