Supported Releases
This page lists the status, timeline and policy for currently supported releases. Supported releases of Istio include releases that are in the active maintenance window and are patched for security and bug fixes. Subsequent patch releases on a minor release do not contain backward incompatible changes.
- Support Policy
- Naming scheme
- Support status of Istio releases
- Releases without known Common Vulnerabilities and Exposures (CVEs)
Support policy
We produce new builds of Istio for each commit. Around once a quarter, we build a minor release and run through several additional tests as well as release qualification. We release patch versions for issues found in minor releases.
The various types of releases represent a different product quality level and level of assistance from the Istio community. In this context, support means that the community will produce patch releases for critical issues and offer technical assistance. Separately, 3rd parties and partners may offer longer-term support solutions.
Type | Support Level | Quality and Recommended Use |
---|---|---|
Development Build | No support | Dangerous, may not be fully reliable. Useful to experiment with. |
Minor Release | Support is provided until 3 months after the next minor release | Safe to deploy in production. Users are encouraged to upgrade to these releases as soon as possible. |
Patch | Same as the corresponding Minor release | Users are encouraged to adopt patch releases as soon as they are available for a given release. |
Security Patch | Same as a Patch, however, it will not contain any additional code other than the security fix from the previous patch | Given the nature of security fixes, users are strongly encouraged to adopt security patches after release. |
You can find available releases on the releases page, and if you’re the adventurous type, you can learn about our development builds on the development builds wiki. You can find high-level releases notes for each minor and patch release here.
Naming scheme
Our naming scheme is as follows:
<major>.<minor>.<patch>
where <minor>
is increased for each release, and <patch>
counts the number of patches for the current <minor>
release. A patch is usually a small change relative to the <minor>
release.
Support status of Istio releases
Version | Currently Supported | Release Date | End of Life | Supported Kubernetes Versions | Tested, but not supported |
---|---|---|---|---|---|
master | No, development only | ||||
1.11 | Yes | August 2021 | ~Feb 2022 (Expected) | 1.19, 1.20, 1.21, 1.22 | 1.16, 1.17, 1.18 |
1.10 | Yes | May 18, 2021 | ~Nov 2021 (Expected) | 1.18, 1.19, 1.20, 1.21 | 1.16, 1.17, 1.22 |
1.9 | Yes | February 9, 2021 | Aug 18, 2021 | 1.17, 1.18, 1.19, 1.20 | 1.15, 1.16 |
1.8 | No | November 10, 2020 | May 12, 2021 | 1.16, 1.17, 1.18, 1.19 | 1.15 |
1.7 | No | August 21, 2020 | Feb 25, 2021 | 1.16, 1.17, 1.18 | 1.15 |
1.6 and earlier | No |
Kubernetes 1.22 removed some deprecated APIs and as a result versions of Istio prior to 1.10.0 will no longer work. If you are upgrading your Kubernetes version, make sure that your Istio version is still supported.
Supported releases without known Common Vulnerabilities and Exposures (CVEs)
Istio does not guarantee that minor releases that fall outside the support window have all known CVEs patched. Please keep up-to-date and use a supported version.
Minor Releases | Patched versions with no known CVEs |
---|---|
1.10.x | 1.10.2+ |
1.9.x | 1.9.6+ |
1.8 and earlier | None |