Open rurus9 opened 3 months ago
cc: @ryanohnemus
This was fixed in 3.1.5
Indeed, in version 3.1.5 it works properly, after the error, it resumed working after some time.
[2024/09/09 11:09:28] [error] [input:kubernetes_events:input:kubernetes_events] http_status=410:
{"kind":"Status","apiVersion":"v1","metadata":{"continue":REDACTED"},"status":"Failure","message":"The provided continue parameter is too old to display a consistent list result. You can start a new list without the continue parameter, or use the continue token in this response to retrieve the remainder of the results. Continuing with the provided token results in an inconsistent list - objects that were created, modified, or deleted between the time the first chunk was returned and now may show up in the list.","reason":"Expired","code":410}
[2024/09/09 11:17:53] [ info] [input:kubernetes_events:input:kubernetes_events] Requesting /api/v1/events?watch=1&resourceVersion=917334540
Thank you!
Bug Report
With this config:
fluent-bit stop reading new events after error http_status=410 from API (and it is quite a hard-working K8s cluster):
Expected behavior fluent-bit should deal with this error