CRI-O Follows up on Latest Kubernetes Release

CRI-O v1.22 features automatic certificate availability and eliminates memory flooding


The CRI-O development team, on August 25, 2021, released the update of its container runtime interface, CRI-O version 1.22. This was an expected follow-up to the upgrade of its mother project, Kubernetes.

Container runtime interface v1.22 will not have metrics flooding a user's project memory.
Container runtime interface v1.22 will not have metrics flooding a user's project memory.
Key Facts
  1. 1

    In terms of security, enhancements are pretty minor in v1.22.

  2. 2

    V1.22 automatically generates backup certificates in any case of deficit.

  3. 3

    CRI-O can be executed even without certificates stored on a disk.

  4. 4

    Users can forget about metrics flooding.


Following the release of Kubernetes 1.22, the CRI-O development team updated the container runtime interface(CRI) in RedHat's wing of Kubernetes distribution, OpenShift, to version 1.22.

Minor security changes and enhancements around data and activity logging are perceived as the main focus of this newest upgrade. The team has imbued certificate date validation in CRI-O; a necessary Enterprise for the TLS security endpoints. If the specified certificates and keys are missing, version 1.22 automatically generates self-signed certificates and keys for the secure metrics endpoint, allowing CRI-O launch regardless of certificate status on disks. This would also serve as an automatic reload mechanism for the metrics TLS certificate and key in case of unanticipated changes.

Container runtime interface v1.22 will not have metrics flooding a user's project memory. It has been configured with CLI nodes that disable the collection of specific metrics making data collection far less arduous. Other changes include the container start featuring the container/sandbox ID alongside the related process ID in compliance with the VM runtime path configuration selection. It's also being imbued with more container and pod annotations to indicate values like the default blockio class and a container's RDT class and the inclusion of bug fixes.

Static binary dependencies also saw indiscriminate upgrades, with crun upgrade to version 0.20.1 and runc, having hit the 1.0 mark, moving an inch up to 1.0.1. In terms of deprecation, the internal_wipe option has been removed.

Get similar news in your inbox weekly, for free

Share this news:

Latest stories

How ManageEngine Applications Manager Can Help Overcome Challenges In Kubernetes Monitoring

We tested ManageEngine Applications Manager to monitor different Kubernetes clusters. This post shares our review …

AIOps with Site24x7: Maximizing Efficiency at an Affordable Cost

In this post we'll dive deep into integrating AIOps in your business suing Site24x7 to …

A Review of Zoho ManageEngine

Zoho Corp., formerly known as AdventNet Inc., has established itself as a major player in …

Should I learn Java in 2023? A Practical Guide

Java is one of the most widely used programming languages in the world. It has …

The fastest way to ramp up on DevOps

You probably have been thinking of moving to DevOps or learning DevOps as a beginner. …

Why You Need a Blockchain Node Provider

In this article, we briefly cover the concept of blockchain nodes provider and explain why …

Top 5 Virtual desktop Provides in 2022

Here are the top 5 virtual desktop providers who offer a range of benefits such …

Why Your Business Should Connect Directly To Your Cloud

Today, companies make the most use of cloud technology regardless of their size and sector. …

7 Must-Watch DevSecOps Videos

Security is a crucial part of application development and DevSecOps makes it easy and continuous.The …