Fluent Bit End of Life (EOL) Dates and End of Support (EOS) Dates

Latest Release: 5.2.0

Fluent Bit end of life (EOL) and end of support (EOS) dates: 25 Fluent Bit versions have reached EOL, including Fluent Bit 5.0 (EOL date: Nov 06, 2026) — no longer receiving security updates or patches. Fluent Bit 5.1 reaches its End of Support date on Feb 09, 2027 — plan your upgrade path now. Fluent Bit 5.2.0 is the current supported release. Also see cert-manager EOSL dates for related end-of-life information.

Fluent Bit end of life dates timeline — release schedule chart of the 8 most recent Fluent Bit versions, mapping security support windows against their EOL dates
Fluent Bit end of life dates and end of support (EOS) dates shown as a release schedule — support windows for the 8 most recent Fluent Bit releases of 27 total. Each bar runs from the release date to the end of security support, with the dashed line marking today. Exact Fluent Bit EOL, EOS and EOSL dates for every version are listed in the tables below.

Currently Supported Fluent Bit Releases - Active EOS/EOSL Support (1)

Release Released Support Latest
5.2 (1 week and 6 days ago) Active 5.2.0 (1 week and 6 days ago)

Fluent Bit Releases Nearing End of Life - Support Ending Soon (1)

Important: The following Fluent Bit releases will reach End of Life (EOL) within 6 months. Plan your migration to a supported release to ensure continued security updates and support.
Release Released Support Latest
5.1 (3 months ago) (in 2 months) 5.1.5 (1 month and 1 day ago)

Fluent Bit End of Life (EOL) Releases - No Longer Supported (25)

Release Released Support Latest
5.0 (7 months ago) (2 weeks and 2 days ago) 5.0.11 (1 month and 1 week ago)
4.2 (1 year ago) (4 months ago) 4.2.8 (3 months ago)
4.1 (1 year and 1 month ago) (9 months ago) 4.1.2 (11 months ago)
4.0 (1 year and 7 months ago) (10 months ago) 4.0.14 (10 months ago)
3.2 (2 years ago) (1 year and 4 months ago) 3.2.10 (1 year and 7 months ago)
3.1 (2 years and 4 months ago) (1 year and 9 months ago) 3.1.10 (2 years ago)
3.0 (2 years and 8 months ago) (2 years and 1 month ago) 3.0.7 (2 years and 5 months ago)
2.2 (3 years ago) (2 years and 5 months ago) 2.2.3 (2 years and 6 months ago)
2.1 (3 years and 7 months ago) (2 years and 9 months ago) 2.1.10 (3 years and 1 month ago)
2.0 (4 years ago) (3 years and 4 months ago) 2.0.14 (3 years and 6 months ago)
1.9 (4 years and 8 months ago) (3 years and 11 months ago) 1.9.10 (3 years and 11 months ago)
1.8 (5 years and 4 months ago) (3 years and 11 months ago) 1.8.15 (4 years and 7 months ago)
1.7 (5 years and 9 months ago) — 1.7.9 (5 years and 5 months ago)
1.6 (6 years and 1 month ago) — 1.6.10 (5 years and 10 months ago)
1.5 (6 years and 4 months ago) — 1.5.7 (6 years and 1 month ago)
1.4 (6 years and 7 months ago) — 1.4.6 (6 years and 4 months ago)
1.3 (7 years and 1 month ago) — 1.3.11 (6 years and 7 months ago)
1.2 (7 years and 4 months ago) — 1.2.2 (7 years and 4 months ago)
1.1 (7 years and 6 months ago) — 1.1.3 (7 years and 4 months ago)
1.0 (7 years and 11 months ago) — 1.0.6 (7 years and 7 months ago)
0.14 (8 years and 2 months ago) — 0.14.9 (7 years and 11 months ago)
0.13 (8 years and 6 months ago) — 0.13.8 (8 years and 3 months ago)
0.12 (9 years and 3 months ago) — 0.12.19 (8 years and 7 months ago)
0.11 (9 years and 7 months ago) — 0.11.17 (9 years and 3 months ago)
0.10 (9 years and 10 months ago) — 0.10.1 (9 years and 10 months ago)

Checking Fluent Bit end of life status before you deploy keeps the logs, metrics and telemetry flowing through this open-source CNCF project patched. Born under the Fluentd umbrella as a lightweight processor, it supports only its newest lines, so v5.1 is the current stable line and v4.2 and older are already past EOL.

Fluent Bit EOL Dates for Every Release Series

Each release series (x.y) gets patches for a limited window, then reaches end-of-life. Only one supported release line counts as the stable release, and the agent behaves the same on Linux, Windows and macOS, because it is a cross-platform binary. The table below uses the project's own dates; endoflife.date applies a rule of three months after the next series ships.

SeriesReleasedStatusMaintained until
5.1Aug 6, 2026StableCurrent
5.0Mar 31, 2026Maintenance onlyNov 30, 2026
4.2Nov 11, 2025EndedJul 30, 2026
4.1Sep 24, 2025EndedFeb 28, 2026
4.0Mar 29, 2025EndedDec 23, 2025

Third-party trackers can differ by days or weeks: endoflife.date lists 5.0 ending Nov 6, 2026. Plan around the earlier date.

How the Fluent Bit Maintenance Policy Works

The maintenance policy splits the lifecycle into nightly-build, stable and maintenance stages. The lead maintainer assigns each series its own branch on GitHub, and security timelines live in SECURITY.md.

Stable Series and Development

New work lands in master as commits for v5.2 development before anything is released. The 5.1 line is the one recommended for production.

Maintenance Mode, Backports and Maintenance Branches

A series in maintenance mode accepts critical bug fixes and security patches only. Fixes are merged into master first, then cherry-picked into older backports by the maintainer.

Fluent Bit End of Life: Releases No Longer Maintained

v4.0 reached its end on Dec 23, 2025, v4.1 on Feb 28, 2026 and v4.2 on Jul 30, 2026. Each is no longer maintained, so a Kubernetes DaemonSet or Docker image pinned to one of those tags is running unpatched software.

What Happens After Support Ends

You receive no more security updates and no low-risk fixes. Vulnerabilities found later stay open, and newer packaging changes and documentation only describe supported lines.

Planning a Fluent Bit Upgrade Before End-of-Maintenance

The newest 5.1 patch, v5.1.5, shipped on Oct 21, 2026. Read the release notes and the upgrading notes first. v5.1.4, for example, fixed multiline truncation and tightened OpenTelemetry limits. The community channel on CNCF Slack answers upgrade questions.

Reading Plugins, Filters and Outputs in Release Notes

Scan the notes for the plugins you run: filters such as Kubernetes, inputs such as Forward, and outputs such as GELF. A change there matters more than a core fix.

Contributing Fixes Across the Fluent Bit Lifecycle

Open pull requests against master. For a v5.0 backport, add Target: v5.0 to the PR. A maintenance release ships on an as-needed basis, so bug fixes from contributors can take days to reach you. To see what you run, execute fluent-bit -v.

EOL dates of related software products