-
Notifications
You must be signed in to change notification settings - Fork 1
Closed
Labels
enhancementNew feature or requestNew feature or request
Description
Description
Add optional DaemonSet deployment mode as an alternative to Deployment.
Why is this needed?
Running cloudflared as a DaemonSet (one pod per node) can help:
- Avoid ephemeral port exhaustion when multiple pods run on the same node
- Ensure consistent tunnel presence across all nodes
- Follow Cloudflare's recommendation of limiting instances per node
Implementation details
- Add
daemonset.enabledflag in values.yaml (default: false) - Create conditional logic to deploy either Deployment or DaemonSet
- Ensure all relevant settings work with both modes
- Add corresponding tests
Reference
- Upstream PR: Optional Daemonset deployment cloudflare/helm-charts#87
- Cloudflare docs: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/deploy-tunnels/system-requirements/#recommendations
Acceptance Criteria
- DaemonSet template created (or conditional deployment)
- Values.yaml updated with daemonset options
- Tests added for both modes
- Documentation updated with use cases
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request