docs: pipeline: inputs: kubernetes-events: document kube_watch_timeout - #2644
Conversation
|
Warning Review limit reached
Next review available in: 32 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Kubernetes events input documentation now describes ChangesKubernetes watch timeout
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@pipeline/inputs/kubernetes-events.md`:
- Line 36: Update the version behavior description in the Kubernetes events
documentation so Fluent Bit versions earlier than 3.1 are described as polling,
with interval_sec and interval_nsec controlling the poll interval; reserve
watch-stream reconnect semantics for version 3.1 and later.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 88cd3de9-025a-44c1-af55-4ff1918e4694
📒 Files selected for processing (1)
pipeline/inputs/kubernetes-events.md
Document the new kube_watch_timeout parameter, which bounds the lifetime of a Kubernetes watch request through the timeoutSeconds API parameter and applies a matching read idle timeout on the HTTP client. Explain that reconnection resumes from the last recorded resource version and that 0 disables both timeouts. Also, corrected interval parameter behavior by version. Note, change for code merge without corresponding docs PR. Signed-off-by: Eric D. Schabell <eric@schabell.org>
8cec6cf to
17b9d61
Compare
|
@patrick-stephens ready for review! |
#2644) Document the new kube_watch_timeout parameter, which bounds the lifetime of a Kubernetes watch request through the timeoutSeconds API parameter and applies a matching read idle timeout on the HTTP client. Explain that reconnection resumes from the last recorded resource version and that 0 disables both timeouts. Also, corrected interval parameter behavior by version. Note, change for code merge without corresponding docs PR. Signed-off-by: Eric D. Schabell <eric@schabell.org> Signed-off-by: Patrick Stephens <pat@telemetryforge.io>
Document the new kube_watch_timeout parameter, which bounds the lifetime of a Kubernetes watch request through the timeoutSeconds API parameter and applies a matching read idle timeout on the HTTP client. Explain that reconnection resumes from the last recorded resource version and that 0 disables both timeouts.
Note, change for code merge without corresponding docs PR.
Summary by CodeRabbit
New Features
kube_watch_timeoutconfiguration option to limit Kubernetes watch request and idle connection durations.0preserves indefinite connections.Documentation