Skip to content

docs: pipeline: inputs: kubernetes-events: document kube_watch_timeout - #2644

Merged
eschabell merged 1 commit into
fluent:masterfrom
eschabell:erics_in_kubernetes_events_updates
Aug 5, 2026
Merged

eschabell merged 1 commit into
fluent:masterfrom
eschabell:erics_in_kubernetes_events_updates

Conversation

@eschabell

@eschabell eschabell commented Aug 1, 2026

Copy link
Copy Markdown
Collaborator

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

    • Added the kube_watch_timeout configuration option to limit Kubernetes watch request and idle connection durations.
    • Setting the value to 0 preserves indefinite connections.
    • Reconnections resume from the last recorded resource version.
  • Documentation

    • Documented the new configuration option and its behavior.

@eschabell eschabell self-assigned this Aug 1, 2026
@eschabell
eschabell requested a review from a team as a code owner August 1, 2026 09:46
@eschabell eschabell added waiting-on-review Waiting on a review from mainteners 5.0.9 labels Aug 1, 2026
@coderabbitai

coderabbitai Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@eschabell, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a58750b3-6fa2-4a25-a34d-9d6bd9b65c37

📥 Commits

Reviewing files that changed from the base of the PR and between 8cec6cf and 17b9d61.

📒 Files selected for processing (1)
  • pipeline/inputs/kubernetes-events.md
📝 Walkthrough

Walkthrough

The Kubernetes events input documentation now describes kube_watch_timeout, its 10m default, timeout behavior, reconnection from the last resource version, and the 0 value for indefinite connections.

Changes

Kubernetes watch timeout

Layer / File(s) Summary
Document kube_watch_timeout behavior
pipeline/inputs/kubernetes-events.md
Documents server-side watch duration, client read-idle timeout, reconnection behavior, and the 0 value that disables both timeouts.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: patrick-stephens

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely identifies the documentation change for the new kube_watch_timeout parameter.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0eb06a6 and 8cec6cf.

📒 Files selected for processing (1)
  • pipeline/inputs/kubernetes-events.md

Comment thread pipeline/inputs/kubernetes-events.md Outdated
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>
@eschabell
eschabell force-pushed the erics_in_kubernetes_events_updates branch from 8cec6cf to 17b9d61 Compare August 1, 2026 09:54
@eschabell

Copy link
Copy Markdown
Collaborator Author

@patrick-stephens ready for review!

@eschabell eschabell removed the waiting-on-review Waiting on a review from mainteners label Aug 5, 2026
@eschabell
eschabell merged commit 012228c into fluent:master Aug 5, 2026
8 checks passed
@eschabell
eschabell deleted the erics_in_kubernetes_events_updates branch August 5, 2026 10:28
patrick-stephens pushed a commit that referenced this pull request Aug 7, 2026
#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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants