fix: increase timeout for informer on loki.source.podlogs #1862
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Description
This PR is to fix #1852 where on a busy Kubernetes cluster, the loki.source.podlogs component times-out after 10 seconds with error 'failed to configure informers: Timeout exceeded while configuring informers. Check the connection to the Kubernetes API is stable and that Alloy has appropriate RBAC permissions'.
Which issue(s) this PR fixes
Fixes #1852
Notes to the Reviewer
Similar issue was seen (#233) where the fix was to increase the timeout on the informer. I have validated this works on a busy K8s cluster and resolves the issue of the component not starting.
PR Checklist