From 272935f010285ec7da58ebc2b52082eb5434d4b4 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Wed, 26 Feb 2025 10:34:44 -0500 Subject: [PATCH] Created Cri-O default capabilities section follow up --- modules/create-crio-default-capabilities.adoc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/modules/create-crio-default-capabilities.adoc b/modules/create-crio-default-capabilities.adoc index c6c561cb2c..497bdb2248 100644 --- a/modules/create-crio-default-capabilities.adoc +++ b/modules/create-crio-default-capabilities.adoc @@ -6,7 +6,7 @@ [id="create-crio-default-capabilities_{context}"] = Creating a drop-in file for the default CRI-O capabilities -You can change some of the settings associated with the {product-title} CRI-O runtime for the nodes associated with a specific machine config pool (MCP). By using a controller custom resource (CR), you set the configuration values and add a label to match the MCP. The MCO then rebuilds the `crio.conf` and `default.conf` configuration files on the associated nodes with the updated values. +You can change some of the settings associated with the {product-title} CRI-O runtime for the nodes associated with a specific machine config pool (MCP). By using a controller custom resource (CR), you set the configuration values and add a label to match the MCP. The Machine Config Operator (MCO) then rebuilds the `crio.conf` and `default.conf` configuration files on the associated nodes with the updated values. Earlier versions of {product-title} included specific machine configs by default. If you updated to a later version of {product-title}, those machine configs were retained to ensure that clusters running on the same {product-title} version have the same machine configs. @@ -37,6 +37,10 @@ ctr-level 5m45s [source,terminal] ---- $ cat /proc/1/status | grep Cap +---- + +[source,terminal] +---- $ capsh --decode= <1> ---- <1> Replace `` with the specific value you want to decode.