ovirt end of life dates — full support timeline
6 of 7 tracked ovirt releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 4.5 | 2022-03-16 | not announced | 4.5.7 | supported |
| 4.4 | 2020-05-06 | 2022-05-20 | 4.4.10.7 | ended |
| 4.3 | 2019-01-22 | 2020-05-20 | 4.3.11.4 | ended |
| 4.2 | 2017-12-04 | 2019-02-04 | 4.2.8.9 | ended |
| 4.1 | 2017-01-12 | 2017-12-17 | 4.1.11.2 | ended |
| 4.0 | 2016-05-31 | 2017-01-12 | 4.0.7.5 | ended |
| 3.6 | 2015-09-25 | 2016-06-23 | 3.6.13.5 | ended |
Who is affected
Anyone running an unsupported ovirt release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/ovirt, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next ovirt deadline
You are reading this because a ovirt release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every ovirt and related deadline as it is announced, with exact dates and primary sources.
Watch ovirt deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.