Skip to content

OSDOCS#19367: Note runc container runtime deprecation #112351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kowen-rh wants to merge 1 commit into
base: main
Choose a base branch
from
+15 −0
Open

OSDOCS#19367: Note runc container runtime deprecation #112351

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions modules/config-container-runtime.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,11 @@ You can configure the container runtime used with new workloads on your nodes, b

For information on crun and runc, see "About the container engine and container runtime".

[WARNING]
====
Starting in {product-title} 4.22, the runc container runtime is deprecated.
====

Starting in {product-title} 4.18, crun is the default container runtime for new installations. You can change between the runtimes by using a `ContainerRuntimeConfig` object, as described in the following procedure. Changing the container runtime affects new workloads only. Existing workloads continue to use their existing container runtime.

If you updated your cluster from {product-title} 4.17, the runc container runtime remains unchanged as the default. During the upgrade, two `MachineConfig` objects, one for the control plane nodes and one for the worker nodes, were created to override the new default runtime. You can migrate the container runtime to crun, on a schedule of your choosing, by removing either or both of the `MachineConfig` objects.
Expand Down
10 changes: 10 additions & 0 deletions nodes/containers/nodes-containers-using.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,11 @@ The {product-title} documentation uses the term _container runtime_ to refer to
ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
{product-title} uses CRI-O as the container engine and runC or crun as the container runtime. The default container runtime is crun. Both container runtimes adhere to the link:https://www.opencontainers.org/[Open Container Initiative (OCI)] runtime specifications.

[WARNING]
====
Starting in {product-title} 4.22, the runc container runtime is deprecated.
====

include::snippets/about-crio-snippet.adoc[]

crun, developed by Red Hat, is a fast and low-memory container runtime fully written in C. runC, developed by Docker and maintained by the Open Container Project, is a lightweight, portable container runtime written in Go.
Expand All @@ -74,6 +79,11 @@ endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]

ifdef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
{product-title} uses CRI-O as the container engine and crun or runC as the container runtime. The default container runtime is crun.

[WARNING]
====
Starting in {product-title} 4.22, the runc container runtime is deprecated.
====
endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]

ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
Expand Down