cloudflare / cloudflare/argo-tunnel-examples
What's the reason your liveness check interval is 10 seconds?
Open
- Dominant language
- HCL
- Stars
- 244
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
In this example:
https://github.com/cloudflare/argo-tunnel-examples/blob/86a2dccc880669ef3b5f9f2e6c2f034242c08f12/named-tunnel-k8s/cloudflared.yaml#L27-L35
Wouldn't this result in a potential 10 second outage?
Is there a reason it is not set to 1?
Contributor guide
Research direction
Inspect named-tunnel-k8s/cloudflared.yaml at lines 27-35, starting with the liveness check configuration. Determine whether the 10-second interval is intentional and document the rationale or adjust the example if the interval should be different; done means the example and its explanation clearly address the possible outage window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100