save up to $754 USD (2).png

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:
save up to $754 USD (2).png

Latest stories

Canary Release vs Blue-Green Deployments

Choosing the right deployment strategy is crucial to the availability and quality of your services. …

How Disaster Ready Are Your Backup Systems, Really?

In this blog post, we’ll help you ensure that your backup systems will perform as …

8 Best Practices to Boost Your CI/CD Performance

This article discusses the best practices that boost your CI/CD performance and how each impacts …