← ← Back to all products
Apache Flink
Active
Middleware Latest Version: 2.2.0 Latest Release: Dec 3, 2025
Apache Flink is a framework for stateful computations over unbounded and bounded data streams.
Versions
7
Latest Version
2.2.0
Active Support
5
EOL
2
Lifecycle Timeline
Today ↓
2.2
2.2
2.1
2.1
2.0
2.0
1.20
1.20
1.19
1.19
1.18
1.18
1.17
1.17
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2.2 | Dec 4, 2025 | - | No | 2.2.0 | No | Active |
| 2.1 | Jul 29, 2025 | - | No | 2.1.1 | No | Active |
| 2.0 | Mar 19, 2025 | - | No | 2.0.1 | No | Active |
| 1.20 | Aug 1, 2024 | - | No | 1.20.3 | Yes | Active |
| 1.19 | Mar 15, 2024 | - | No | 1.19.3 | No | Active |
| 1.18 | Oct 24, 2023 | - | Mar 24, 2025 | 1.18.1 | No | EOL |
| 1.17 | Mar 23, 2023 | - | Aug 1, 2024 | 1.17.2 | No | EOL |
Frequently Asked Questions
Which versions of Apache Flink have reached end of life?
The following Apache Flink versions have reached end of life and no longer receive security updates: 1.18, 1.17. It is recommended to upgrade to a supported version.
Is it safe to continue using Apache Flink 1.18?
Apache Flink 1.18 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Apache Flink?
The latest version of Apache Flink is 2.2.0, released in the 2.2 release cycle.
How many versions of Apache Flink are currently supported?
Apache Flink currently has 5 actively supported version(s): 2.2, 2.1, 2.0, 1.20, 1.19.
When does Apache Flink 2.2 reach end of life?
Apache Flink 2.2 does not have a specific end-of-life date announced yet.
What should I do when Apache Flink reaches end of life?
When a Apache Flink version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.