openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Code Issues Releases Activity

Created Cri-O default capabilities section follow up

Browse Source
This commit is contained in:
Michael Burke
2025-02-26 10:34:44 -05:00
parent 8830df0571
commit 272935f010
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
modules/create-crio-default-capabilities.adoc
View File

@@ -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=<decode_CapBnd_value> <1>
----
<1> Replace `<decode_CapBnd_value>` with the specific value you want to decode.