Skip to content

Helm Values

The strrl.dev/cloudflare-tunnel-ingress-controller chart exposes values for production hardening, observability, and connector behaviour. This table highlights the most frequently adjusted settings.

For the complete and up-to-date list of all available Helm values, refer to the values.yaml file in the repository.

ValueDefaultNotes
cloudflare.apiToken""Required when Helm creates the credential secret.
cloudflare.accountId""Required when Helm creates the credential secret.
cloudflare.tunnelName""Required when Helm creates the credential secret.
cloudflare.secretRef.*unsetPoint the chart at an existing secret managed outside Helm.
ingressClass.namecloudflare-tunnelRename if you run multiple controllers in one cluster.
ingressClass.isDefaultClassfalseSet to true only if Cloudflare Tunnel should handle every ingress by default.
cloudflared.image.taglatestPin to a specific cloudflared version for reproducible environments.
cloudflared.extraArgs[]Append extra arguments such as --post-quantum.
cloudflaredServiceMonitor.createfalseEnable when you scrape metrics with Prometheus Operator.
replicaCount1Scale the controller deployment (enable leader election for >1).
resourcesrequests/limits at 100m CPU / 128MiHarden resource guarantees for both the controller and connectors.

Most other values control standard Kubernetes objects (service account, annotations, node selectors, tolerations, affinity). Use them to integrate with your platform’s scheduling or security requirements.