Versio.io

cri-o

Release, patch & end-of-life (EOL) insights

Release & EoL databaseAutomate patch processFree trial

Product description

Automate product release and end-of-life managementCRI-O follows the Kubernetes release cycles with respect to its minor versions (1.x.0). Patch releases (1.x.y) for CRI-O are not in sync with those from Kubernetes, because those are scheduled for each month, whereas CRI-O provides them only if necessary. If a Kubernetes release goes End of Life, then the corresponding CRI-O version can be considered in the same way.This means that CRI-O also follows the Kubernetes n-2 release version skew policy when it comes to feature graduation, deprecation or removal. This also applies to features which are independent from Kubernetes.
X
Figure: Release, patch and end-of-life cycle of product cri-o (cri-o)
 

Properties

Product
cri-o
Vendor
cri-o
Latest version
1.26.2
# Releases
21
# Versions
180
# Security affected versions (CVE)
142
Licence MIT
Apache-2.0
Last verification date
2023-03-15
 

Read more

 

Talk to us


Alex Aschauer
Alex Aschauer
Business Development Manager
P:  +49-30-221986-52
LinkedIn
Contact person
Matthias Scholze
Chief Technology Officer
P:  +49-30-221986-51
LinkedIn


Keywords

cri-o

 

cri-o

 

System component

 

Release

 

Version

 

Major

 

Minor

 

Patch

 

End-of-life

 

EOL

 

Support

 

End-of-support

 

EOS

 

Maintenance

 

Security

 

Common vulnerabilities & exposures

 

CVE

 

We use cookies to ensure that we give you the best experience on our website. Read privacy policies for more information.