KeyID is the KMS key ID to use for encryption. It is optional because buckets are encrypted by default on Google Cloud. This allows for the use of a custom encryption key.</td>\n</tr>\n</tbody>\n</table>\n\n## 3.3. CONFIGURING THE REGISTRY FOR OPENSTACK USER-PROVISIONED INFRASTRUCTURE\n\nYou can configure the registry of a cluster that runs on your own Red Hat OpenStack Platform (RHOSP) infrastructure.\n\n### 3.3.1. Configuring Image Registry Operator redirects\n\nBy disabling redirects, you can configure the Image Registry Operator to control whether clients such as OpenShift Container Platform cluster builds or external systems like developer machines are redirected to pull images directly from Red Hat OpenStack Platform (RHOSP) Swift storage. This configuration is optional and depends on whether the clients trust the storage's SSL/TLS certificates.\n\n#### NOTE\n\nIn situations where clients do not trust the storage certificate, setting the **disableRedirect** option can be set to **true** proxies traffic through the image registry. Consequently, however, the image registry might require more resources, especially network bandwidth, to handle the increased load.\n\nAlternatively, if clients trust the storage certificate, the registry can allow redirects. This reduces resource demand on the registry itself.\n\nSome users might prefer to configure their clients to trust their self-signed certificate authorities (CAs) instead of disabling redirects. If you are using a self-signed CA, you must decide between trusting the custom CAs or disabling redirects.\n\n#### Procedure- • To ensure that the image registry proxies traffic instead of relying on Swift storage, change the value of the **spec.disableRedirect** field in the **config.imageregistry** object to **true** by running the following command:\n\n```\n$ oc patch configs.imageregistry.operator.openshift.io cluster --type merge --patch '{\"spec\":{\"disableRedirect\":\"true\"}}'\n```\n\n### 3.3.2. Configuring a secret for the Image Registry Operator\n\nIn addition to the **configs.imageregistry.operator.openshift.io** and ConfigMap resources, configuration is provided to the Operator by a separate secret resource located within the **openshift-image-registry** namespace.\n\nThe **image-registry-private-configuration-user** secret provides credentials needed for storage access and management. It overrides the default credentials used by the Operator, if default credentials were found.\n\nFor Swift on Red Hat OpenStack Platform (RHOSP) storage, the secret is expected to contain the following two keys:\n\n- • **REGISTRY\\_STORAGE\\_SWIFT\\_USERNAME**\n- • **REGISTRY\\_STORAGE\\_SWIFT\\_PASSWORD**\n\n#### Procedure\n\n- • Create an OpenShift Container Platform secret that contains the required keys.\n\n```\n$ oc create secret generic image-registry-private-configuration-user --from-literal=REGISTRY_STORAGE_SWIFT_USERNAME=<username> --from-literal=REGISTRY_STORAGE_SWIFT_PASSWORD=<password> -n openshift-image-registry\n```\n\n### 3.3.3. Registry storage for RHOSP with user-provisioned infrastructure\n\nIf the Registry Operator cannot create a Swift bucket, you must set up the storage medium manually and configure the settings in the registry custom resource (CR).\n\n#### Prerequisites\n\n- • A cluster on Red Hat OpenStack Platform (RHOSP) with user-provisioned infrastructure.\n- • To configure registry storage for RHOSP, you need to provide Registry Operator cloud credentials.\n- • For Swift on RHOSP storage, the secret is expected to contain the following two keys:\n - ◦ **REGISTRY\\_STORAGE\\_SWIFT\\_USERNAME**\n - ◦ **REGISTRY\\_STORAGE\\_SWIFT\\_PASSWORD**\n\n#### Procedure\n\n- • Fill in the storage configuration in **configs.imageregistry.operator.openshift.io/cluster**:```\n$ oc edit configs.imageregistry.operator.openshift.io/cluster\n```\n\n### Example configuration\n\n```\napiVersion: imageregistry.operator.openshift.io/v1\nkind: Config\nmetadata:\n name: cluster\nspec:\n storage:\n swift:\n container: <container_id>\n```\n\n### 3.3.4. Image Registry Operator configuration parameters for RHOSP Swift\n\nThe following parameters are available for you to configure your Red Hat OpenStack Platform (RHOSP) Swift registry storage.\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>authURL</b></td>\n<td>Defines the URL for obtaining the authentication token. This value is optional.</td>\n</tr>\n<tr>\n<td><b>authVersion</b></td>\n<td>Specifies the Auth version of RHOSP, for example, <b>authVersion: \"3\"</b>. This value is optional.</td>\n</tr>\n<tr>\n<td><b>container</b></td>\n<td>Defines the name of a Swift container for storing registry data. This value is optional.</td>\n</tr>\n<tr>\n<td><b>domain</b></td>\n<td>Specifies the RHOSP domain name for the Identity v3 API. This value is optional.</td>\n</tr>\n<tr>\n<td><b>domainID</b></td>\n<td>Specifies the RHOSP domain ID for the Identity v3 API. This value is optional.</td>\n</tr>\n<tr>\n<td><b>tenant</b></td>\n<td>Defines the RHOSP tenant name to be used by the registry. This value is optional.</td>\n</tr>\n<tr>\n<td><b>tenantID</b></td>\n<td>Defines the RHOSP tenant ID to be used by the registry. This value is optional.</td>\n</tr>\n<tr>\n<td><b>regionName</b></td>\n<td>Defines the RHOSP region in which the container exists. This value is optional.</td>\n</tr>\n</tbody>\n</table>\n\n## 3.4. CONFIGURING THE REGISTRY FOR AZURE USER-PROVISIONED INFRASTRUCTURE\n\nSave your container images to a durable storage location by configuring the built-in image registry to use dedicated Azure storage. This setup provides persistent scalable storage for your registry, separate from ephemeral cluster storage.\n\n### 3.4.1. Configuring a secret for the Image Registry OperatorIn addition to the **configs.imageregistry.operator.openshift.io** and ConfigMap resources, configuration is provided to the Operator by a separate secret resource located within the **openshift-image-registry** namespace.\n\nThe **image-registry-private-configuration-user** secret provides credentials needed for storage access and management. It overrides the default credentials used by the Operator, if default credentials were found.\n\nFor Azure registry storage, the secret is expected to contain one key whose value is the contents of a credentials file provided by Azure:\n\n- • **REGISTRY\\_STORAGE\\_AZURE\\_ACCOUNTKEY**\n\n### Procedure\n\n- • Create an OpenShift Container Platform secret that contains the required key.\n\n```\n$ oc create secret generic image-registry-private-configuration-user --from-literal=REGISTRY_STORAGE_AZURE_ACCOUNTKEY=<accountkey> --namespace openshift-image-registry\n```\n\n## 3.4.2. Configuring registry storage for Azure\n\nDuring installation, your cloud credentials are sufficient to create Azure Blob Storage, and the Registry Operator automatically configures storage.\n\n### Prerequisites\n\n- • A cluster on Azure with user-provisioned infrastructure.\n- • To configure registry storage for Azure, provide Registry Operator cloud credentials.\n- • For Azure storage the secret is expected to contain one key:\n - ◦ **REGISTRY\\_STORAGE\\_AZURE\\_ACCOUNTKEY**\n\n### Procedure\n\n1. 1. Create an [Azure storage container](#).\n2. 2. Fill in the storage configuration in **configs.imageregistry.operator.openshift.io/cluster**:\n\n```\n$ oc edit configs.imageregistry.operator.openshift.io/cluster\n```\n\n### Example configuration\n\n```\napiVersion: imageregistry.operator.openshift.io/v1\nkind: Config\nmetadata:\n name: cluster\nspec:\n storage:\n``````\nazure:\n accountName: <storage_account_name>\n container: <container_name>\n```\n\n### 3.4.3. Configuring registry storage for Azure Government\n\nDuring installation, your cloud credentials are sufficient to create Azure Blob Storage, and the Registry Operator automatically configures storage.\n\n#### Prerequisites\n\n- • A cluster on Azure with user-provisioned infrastructure in a government region.\n- • To configure registry storage for Azure, provide Registry Operator cloud credentials.\n- • For Azure storage, the secret is expected to contain one key:\n - ◦ **REGISTRY\\_STORAGE\\_AZURE\\_ACCOUNTKEY**\n\n#### Procedure\n\n1. 1. Create an [Azure storage container](#).\n2. 2. Fill in the storage configuration in **configs.imageregistry.operator.openshift.io/cluster**:\n\n```\n$ oc edit configs.imageregistry.operator.openshift.io/cluster\n```\n\n#### Example configuration\n\n```\nstorage:\n azure:\n accountName: <storage-account-name>\n container: <container-name>\n cloudName: AzureUSGovernmentCloud\n```\n\n**cloudName** is the name of the Azure cloud environment, which can be used to configure the Azure SDK with the appropriate Azure API endpoints. Defaults to **AzurePublicCloud**. You can also set **cloudName** to **AzureUSGovernmentCloud**, **AzureChinaCloud**, or **AzureGermanCloud** with sufficient credentials.\n\n## 3.5. CONFIGURING THE REGISTRY FOR RHOSP\n\nYou configure the image registry to use custom storage on clusters that run on RHOSP. You must configure custom storage to use a Cinder volume in a specific availability zone.\n\n### 3.5.1. Configuring an image registry with custom storage on clusters that run on RHOSP\n\nAfter you install a cluster on Red Hat OpenStack Platform (RHOSP), you can use a Cinder volume that is in a specific availability zone for registry storage.\n\n#### Procedure1. 1. Create a YAML file that specifies the storage class and availability zone to use. For example:\n\n```\napiVersion: storage.k8s.io/v1\nkind: StorageClass\nmetadata:\n name: custom-csi-storageclass\nprovisioner: cinder.csi.openstack.org\nvolumeBindingMode: WaitForFirstConsumer\nallowVolumeExpansion: true\nparameters:\n availability: <availability_zone_name>\n```\n\n#### NOTE\n\nOpenShift Container Platform does not verify the existence of the availability zone you choose. Verify the name of the availability zone before you apply the configuration.\n\n1. 2. From a command line, apply the configuration:\n\n```\n$ oc apply -f <storage_class_file_name>\n```\n\n#### Example output\n\n```\nstorageclass.storage.k8s.io/custom-csi-storageclass created\n```\n\n1. 3. Create a YAML file that specifies a persistent volume claim (PVC) that uses your storage class and the **openshift-image-registry** namespace. For example:\n\n```\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n name: csi-pvc-imageregistry\n namespace: openshift-image-registry\n annotations:\n imageregistry.openshift.io: \"true\"\nspec:\n accessModes:\n - ReadWriteOnce\n volumeMode: Filesystem\n resources:\n requests:\n storage: 100Gi\n storageClassName: <your_custom_storage_class>\n```\n\nwhere:\n\n#### metadata.namespace\n\nSpecifying the **openshift-image-registry** namespace allows the Cluster Image Registry Operator to consume the PVC.\n\n#### spec.resources.requests.storage\n\nThis optional field adjusts the volume size."},"html":{"kind":"string","value":"<h1>OpenShift Container Platform 4.21</h1><h2>Registry</h2><p>Configuring registries for OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Registry</h1><hr/><p>Configuring registries for OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.</p><p>Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.</p><p>Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.</p><p>Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.</p><p>XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.</p><p>The OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.</p><p>All other trademarks are the property of their respective owners.</p><h2>Abstract</h2><p>This document provides instructions for configuring and managing the internal registry for OpenShift Container Platform. It also provides a general overview of registries associated with OpenShift Container Platform.</p>\n<h1>Table of Contents</h1>\n\n<table>\n<tr>\n<td><b>CHAPTER 1. OPENSHIFT IMAGE REGISTRY OVERVIEW</b> .....</td>\n<td><b>4</b></td>\n</tr>\n<tr>\n<td> 1.1. GLOSSARY OF COMMON TERMS FOR OPENSHIFT IMAGE REGISTRY</td>\n<td>4</td>\n</tr>\n<tr>\n<td> 1.2. INTEGRATED OPENSHIFT IMAGE REGISTRY</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.3. AUTOMATICALLY PRUNING IMAGES</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.4. CREATING CONTAINERS BY USING IMAGES FROM THIRD-PARTY REGISTRIES</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 1.5. RED HAT QUAY REGISTRIES</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 1.6. AUTHENTICATION ENABLED RED HAT REGISTRY</td>\n<td>8</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. IMAGE REGISTRY OPERATOR IN OPENSHIFT CONTAINER PLATFORM</b> .....</td>\n<td><b>10</b></td>\n</tr>\n<tr>\n<td> 2.1. IMAGE REGISTRY ON CLOUD PLATFORMS AND OPENSTACK</td>\n<td>10</td>\n</tr>\n<tr>\n<td> 2.2. IMAGE REGISTRY ON BARE METAL, NUTANIX, AND VSPHERE</td>\n<td>10</td>\n</tr>\n<tr>\n<td> 2.2.1. Image registry removed during installation</td>\n<td>10</td>\n</tr>\n<tr>\n<td> 2.3. IMAGE REGISTRY OPERATOR DISTRIBUTION ACROSS AVAILABILITY ZONES</td>\n<td>11</td>\n</tr>\n<tr>\n<td> 2.4. ADDITIONAL RESOURCES</td>\n<td>11</td>\n</tr>\n<tr>\n<td> 2.5. IMAGE REGISTRY OPERATOR CONFIGURATION PARAMETERS</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 2.6. ENABLING THE IMAGE REGISTRY DEFAULT ROUTE BY USING A CRD</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 2.7. CONFIGURING ADDITIONAL TRUST STORES FOR IMAGE REGISTRY ACCESS</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 2.8. CONFIGURING STORAGE CREDENTIALS FOR THE IMAGE REGISTRY OPERATOR</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.9. ADDITIONAL RESOURCES</td>\n<td>16</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. SETTING UP AND CONFIGURING THE REGISTRY</b> .....</td>\n<td><b>17</b></td>\n</tr>\n<tr>\n<td> 3.1. CONFIGURING THE REGISTRY FOR AWS USER-PROVISIONED INFRASTRUCTURE</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 3.1.1. Configuring a secret for the Image Registry Operator</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 3.1.2. Configuring registry storage for AWS with user-provisioned infrastructure</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 3.1.3. Image Registry Operator configuration parameters for AWS S3</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 3.2. CONFIGURING THE REGISTRY FOR GOOGLE CLOUD USER-PROVISIONED INFRASTRUCTURE</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.1. Configuring a secret for the Image Registry Operator</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.2. Configuring the registry storage for Google Cloud with user-provisioned infrastructure</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 3.2.3. Image Registry Operator configuration parameters for Google Cloud GCS</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.3. CONFIGURING THE REGISTRY FOR OPENSTACK USER-PROVISIONED INFRASTRUCTURE</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.3.1. Configuring Image Registry Operator redirects</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.3.2. Configuring a secret for the Image Registry Operator</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 3.3.3. Registry storage for RHOSP with user-provisioned infrastructure</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 3.3.4. Image Registry Operator configuration parameters for RHOSP Swift</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.4. CONFIGURING THE REGISTRY FOR AZURE USER-PROVISIONED INFRASTRUCTURE</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.4.1. Configuring a secret for the Image Registry Operator</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.4.2. Configuring registry storage for Azure</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.4.3. Configuring registry storage for Azure Government</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.5. CONFIGURING THE REGISTRY FOR RHOSP</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.5.1. Configuring an image registry with custom storage on clusters that run on RHOSP</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.6. CONFIGURING THE REGISTRY FOR BARE METAL</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.6.1. Image registry removed during installation</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.6.2. Changing the image registry's management state</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.6.3. Image registry storage configuration</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.6.3.1. Configuring registry storage for bare metal and other manual installations</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.6.3.2. Configuring storage for the image registry in non-production clusters</td>\n<td>30</td>\n</tr>\n<tr>\n<td> 3.6.3.3. Configuring block registry storage for bare metal</td>\n<td>30</td>\n</tr>\n<tr>\n<td> 3.6.3.4. Configuring the Image Registry Operator to use Ceph RGW storage with Red Hat OpenShift Data Foundation</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.6.3.5. Configuring the Image Registry Operator to use Noobaa storage with Red Hat OpenShift Data Foundation</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.6.4. Configuring the Image Registry Operator to use CephFS storage with Red Hat OpenShift Data</td>\n<td></td>\n</tr>\n</table>\n\n<table>\n<tr>\n<td>Foundation</td>\n<td>35</td>\n</tr>\n<tr>\n<td>3.6.5. Additional resources</td>\n<td>36</td>\n</tr>\n<tr>\n<td><b>3.7. CONFIGURING THE REGISTRY FOR VSPHERE</b></td>\n<td><b>36</b></td>\n</tr>\n<tr>\n<td>3.7.1. Image registry removed during installation</td>\n<td>36</td>\n</tr>\n<tr>\n<td>3.7.2. Changing the image registry's management state</td>\n<td>36</td>\n</tr>\n<tr>\n<td>3.7.3. Image registry storage configuration</td>\n<td>37</td>\n</tr>\n<tr>\n<td>3.7.3.1. Configuring registry storage for VMware vSphere</td>\n<td>37</td>\n</tr>\n<tr>\n<td>3.7.3.2. Configuring storage for the image registry in non-production clusters</td>\n<td>38</td>\n</tr>\n<tr>\n<td>3.7.3.3. Configuring block registry storage for VMware vSphere</td>\n<td>39</td>\n</tr>\n<tr>\n<td>3.7.3.4. Configuring the Image Registry Operator to use Ceph RGW storage with Red Hat OpenShift Data Foundation</td>\n<td>40</td>\n</tr>\n<tr>\n<td>3.7.3.5. Configuring the Image Registry Operator to use Noobaa storage with Red Hat OpenShift Data Foundation</td>\n<td>42</td>\n</tr>\n<tr>\n<td>3.7.4. Configuring the Image Registry Operator to use CephFS storage with Red Hat OpenShift Data Foundation</td>\n<td>43</td>\n</tr>\n<tr>\n<td>3.7.5. Additional resources</td>\n<td>44</td>\n</tr>\n<tr>\n<td><b>3.8. CONFIGURING THE REGISTRY FOR RED HAT OPENSHIFT DATA FOUNDATION</b></td>\n<td><b>45</b></td>\n</tr>\n<tr>\n<td>3.8.1. Configuring the Image Registry Operator to use Ceph RGW storage with Red Hat OpenShift Data Foundation</td>\n<td>45</td>\n</tr>\n<tr>\n<td>3.8.2. Configuring the Image Registry Operator to use Noobaa storage with Red Hat OpenShift Data Foundation</td>\n<td>46</td>\n</tr>\n<tr>\n<td>3.8.3. Configuring the Image Registry Operator to use CephFS storage with Red Hat OpenShift Data Foundation</td>\n<td>48</td>\n</tr>\n<tr>\n<td>3.8.4. Additional resources</td>\n<td>49</td>\n</tr>\n<tr>\n<td><b>3.9. CONFIGURING THE REGISTRY FOR NUTANIX</b></td>\n<td><b>49</b></td>\n</tr>\n<tr>\n<td>3.9.1. Image registry removed during installation</td>\n<td>49</td>\n</tr>\n<tr>\n<td>3.9.2. Changing the image registry's management state</td>\n<td>49</td>\n</tr>\n<tr>\n<td>3.9.3. Image registry storage configuration</td>\n<td>49</td>\n</tr>\n<tr>\n<td>3.9.3.1. Configuring registry storage for Nutanix</td>\n<td>50</td>\n</tr>\n<tr>\n<td>3.9.3.2. Configuring storage for the image registry in non-production clusters</td>\n<td>51</td>\n</tr>\n<tr>\n<td>3.9.3.3. Configuring block registry storage for Nutanix volumes</td>\n<td>52</td>\n</tr>\n<tr>\n<td>3.9.3.4. Configuring the Image Registry Operator to use Ceph RGW storage with Red Hat OpenShift Data Foundation</td>\n<td>53</td>\n</tr>\n<tr>\n<td>3.9.3.5. Configuring the Image Registry Operator to use Noobaa storage with Red Hat OpenShift Data Foundation</td>\n<td>55</td>\n</tr>\n<tr>\n<td>3.9.4. Configuring the Image Registry Operator to use CephFS storage with Red Hat OpenShift Data Foundation</td>\n<td>56</td>\n</tr>\n<tr>\n<td>3.9.5. Additional resources</td>\n<td>57</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. ACCESSING THE REGISTRY</b> .....</td>\n<td><b>58</b></td>\n</tr>\n<tr>\n<td>4.1. PREREQUISITES</td>\n<td>58</td>\n</tr>\n<tr>\n<td>4.2. ACCESSING THE REGISTRY DIRECTLY FROM THE CLUSTER</td>\n<td>58</td>\n</tr>\n<tr>\n<td>4.3. CHECKING THE STATUS OF THE REGISTRY PODS</td>\n<td>60</td>\n</tr>\n<tr>\n<td>4.4. VIEWING REGISTRY LOGS</td>\n<td>60</td>\n</tr>\n<tr>\n<td>4.5. ACCESSING REGISTRY METRICS</td>\n<td>60</td>\n</tr>\n<tr>\n<td>4.6. ADDITIONAL RESOURCES</td>\n<td>62</td>\n</tr>\n<tr>\n<td><b>CHAPTER 5. EXPOSING THE REGISTRY</b> .....</td>\n<td><b>63</b></td>\n</tr>\n<tr>\n<td>5.1. EXPOSING A DEFAULT REGISTRY MANUALLY</td>\n<td>63</td>\n</tr>\n<tr>\n<td>5.2. EXPOSING A SECURE REGISTRY MANUALLY</td>\n<td>64</td>\n</tr>\n</table>\n<h1>CHAPTER 1. OPENSHIFT IMAGE REGISTRY OVERVIEW</h1><p>OpenShift Container Platform can build images from your source code, deploy them, and manage their lifecycle. OpenShift Container Platform provides an internal, integrated container image registry that can be deployed in your OpenShift Container Platform environment to locally manage images. The overview section includes OpenShift image registry reference information and links for registries commonly used with OpenShift Container Platform.</p><h2>1.1. GLOSSARY OF COMMON TERMS FOR OPENSHIFT IMAGE REGISTRY</h2><p>This glossary defines the common terms that are used in the registry content.</p><h3><b>container</b></h3><p>Lightweight and executable images that consist of software and all its dependencies. Because containers virtualize the operating system, you can run containers in a data center, a public or private cloud, or your local host.</p><h3><b>image repository</b></h3><p>An image repository is a collection of related container images and tags identifying images.</p><h3><b>mirror registry</b></h3><p>The mirror registry is a registry that holds the mirror of OpenShift Container Platform images.</p><h3><b>namespace</b></h3><p>A namespace isolates groups of resources within a single cluster.</p><h3><b>pod</b></h3><p>The pod is the smallest logical unit in Kubernetes. A pod consists of one or more containers to run in a compute node.</p><h3><b>private registry</b></h3><p>A registry is a server that implements the container image registry API. A private registry is a registry that requires authentication so that users can access the content of the registry.</p><h3><b>public registry</b></h3><p>A registry is a server that implements the container image registry API. A public registry is a registry that serves its content publicly.</p><h3><b>Quay.io</b></h3><p>A public Red Hat Quay Container Registry instance provided and maintained by Red Hat, which serves most of the container images and Operators to OpenShift Container Platform clusters.</p><h3><b>OpenShift image registry</b></h3><p>OpenShift image registry is the registry provided by OpenShift Container Platform to manage images.</p><h3><b>registry authentication</b></h3><p>To push and pull images to and from private image repositories, the registry needs to authenticate its users with credentials.</p><h3><b>route</b></h3><p>Exposes a service to allow for network access to pods from users and applications outside the OpenShift Container Platform instance.</p><h3><b>scale down</b></h3><p>To decrease the number of replicas.</p><b>scale up</b><p>To increase the number of replicas.</p><b>service</b><p>A service exposes a running application on a set of pods.</p><h2>1.2. INTEGRATED OPENSHIFT IMAGE REGISTRY</h2><p>OpenShift Container Platform provides a built-in container image registry that runs as a standard workload on the cluster. The registry is configured and managed by an infrastructure Operator. The registry provides an out-of-the-box solution that runs on top of existing cluster infrastructure, so that you can manage the images that run workloads.</p><p>You can scale the registry up or down like any other cluster workload and the registry does not require specific infrastructure provisioning. The registry also integrates into the cluster user authentication and authorization system, which means that defining user permissions on image resources controls access to create and retrieve images.</p><p>The registry is typically used as a publication target for images built on the cluster and as a source of images for workloads running on the cluster. When you push a new image to the registry, a notification gets sent to the cluster of the new image so that other components can react to and consume the updated image.</p><p>Image data is stored in two locations. The actual image data is stored in a configurable storage location, such as cloud storage or a filesystem volume. The image metadata, which is exposed by the standard cluster APIs and is used to perform access control, is stored as standard API resources, specifically images and image streams.</p><b>Additional resources</b><ul><li>• <a href=\"#\">Image Registry Operator in OpenShift Container Platform</a></li></ul><h2>1.3. AUTOMATICALLY PRUNING IMAGES</h2><p>Images from the OpenShift image registry that are no longer required by the system because of age, status, or exceed limits being automatically pruned. As a cluster administrator, can configure or suspend the pruning Custom Resource (CR).</p><b>Prerequisites</b><ul><li>• You have access to an OpenShift Container Platform cluster using an account with cluster administrator permissions.</li><li>• Install the <b>oc</b> CLI.</li></ul>\n<h2>IMPORTANT</h2>\n\n<p>The behavior of the Image Registry Operator for managing the pruner is independent to the <b>managementState</b> specified on the <b>ClusterOperator</b> object of the Image Registry Operator. If the Image Registry Operator is not in the <b>Managed</b> state, the image pruner can still be configured and managed by the Pruning Custom Resource.</p>\n\n<p>However, the <b>managementState</b> of the Image Registry Operator alters the behavior of the deployed image pruner job:</p>\n\n<ul>\n<li>• <b>Managed</b>: the <b>--prune-registry</b> flag for the image pruner is set to <b>true</b>.</li>\n<li>• <b>Removed</b>: the <b>--prune-registry</b> flag for the image pruner is set to <b>false</b>, meaning it only prunes image metadata in etcd.</li>\n</ul>\n\n<h2>Procedure</h2>\n\n<ul>\n<li>• Verify that the object named <b>imagepruners.imageregistry.operator.openshift.io/cluster</b> contains the following <b>spec</b> and <b>status</b> fields:</li>\n</ul>\n\n<pre>spec:\n schedule: 0 0 * * *\n suspend: false\n keepTagRevisions: 3\n keepYoungerThanDuration: 60m\n keepYoungerThan: 3600000000000\n resources: {}\n affinity: {}\n nodeSelector: {}\n tolerations: []\n successfulJobsHistoryLimit: 3\n failedJobsHistoryLimit: 3\nstatus:\n observedGeneration: 2\n conditions:\n - type: Available\n status: \"True\"\n lastTransitionTime: 2019-10-09T03:13:45\n reason: Ready\n message: \"Periodic image pruner has been created.\"\n - type: Scheduled\n status: \"True\"\n lastTransitionTime: 2019-10-09T03:13:45\n reason: Scheduled\n message: \"Image pruner job has been scheduled.\"\n - type: Failed\n status: \"False\"\n lastTransitionTime: 2019-10-09T03:13:45\n reason: Succeeded\n message: \"Most recent image pruning job succeeded.\"</pre>\n\n<ul>\n<li>• <b>schedule</b>: <b>CronJob</b> formatted schedule. This is an optional field, default is daily at midnight.</li>\n<li>• <b>suspend</b>: If set to <b>true</b>, the <b>CronJob</b> running pruning is suspended. This is an optional field, default is <b>false</b>. The initial value on new clusters is <b>false</b>.</li>\n</ul>\n\n<ul>\n<li>• <b>keepTagRevisions</b>: The number of revisions per tag to keep. This is an optional field, default is <b>3</b>. The initial value is <b>3</b>.</li>\n<li>• <b>keepYoungerThanDuration</b>: Retain images younger than this duration. This is an optional field. If a value is not specified, either <b>keepYoungerThan</b> or the default value <b>60m</b> (60 minutes) is used.</li>\n<li>• <b>keepYoungerThan</b>: Deprecated. The same as <b>keepYoungerThanDuration</b>, but the duration is specified as an integer in nanoseconds. This is an optional field. When <b>keepYoungerThanDuration</b> is set, this field is ignored.</li>\n<li>• <b>resources</b>: Standard pod resource requests and limits. This is an optional field.</li>\n<li>• <b>affinity</b>: Standard pod affinity. This is an optional field.</li>\n<li>• <b>nodeSelector</b>: Standard pod node selector. This is an optional field.</li>\n<li>• <b>tolerations</b>: Standard pod tolerations. This is an optional field.</li>\n<li>• <b>successfulJobsHistoryLimit</b>: The maximum number of successful jobs to retain. Must be greater than or equal to <b>1</b> to ensure metrics are reported. This is an optional field, default is <b>3</b>. The initial value is <b>3</b>.</li>\n<li>• <b>failedJobsHistoryLimit</b>: The maximum number of failed jobs to retain. Must be greater than or equal to <b>1</b> to ensure metrics are reported. This is an optional field, default is <b>3</b>. The initial value is <b>3</b>.</li>\n<li>• <b>observedGeneration</b>: The generation observed by the Operator.</li>\n<li>• <b>conditions</b>: The standard condition objects with the following types:\n <ul>\n<li>◦ <b>Available</b>: Indicates if the pruning job has been created. Reasons can be <b>Ready</b> or <b>Error</b>.</li>\n<li>◦ <b>Scheduled</b>: Indicates if the next pruning job has been scheduled. Reasons can be <b>Scheduled</b>, <b>Suspended</b>, or <b>Error</b>.</li>\n<li>◦ <b>Failed</b>: Indicates if the most recent pruning job failed.</li>\n</ul>\n</li>\n</ul>\n\n<h2>1.4. CREATING CONTAINERS BY USING IMAGES FROM THIRD-PARTY REGISTRIES</h2>\n\n<p>Some container image registries require access authorization. Podman is an open source tool for managing containers and container images and interacting with image registries. You can use Podman to authenticate your credentials, pull the registry image, and store local images in a local file system. The procedure provides a generic example of authenticating the registry with Podman.</p>\n\n<p>OpenShift Container Platform can communicate with registries to access private image repositories by using credentials supplied by the user. This allows OpenShift Container Platform to push and pull images to and from private repositories.</p>\n\n<p>OpenShift Container Platform can create containers by using images from third-party registries, but these registries unlikely offer the same image notification support as the integrated OpenShift image registry. In this situation, OpenShift Container Platform fetches tags from the remote registry upon image stream creation. To refresh the fetched tags, run <b>oc import-image <stream></b>. When new images are detected, the previously described build and deployment reactions occur.</p>\n<h2>Procedure</h2><ol><li>1. Use the <a href=\"#\">Red Hat Ecosystem Catalog</a> to search for specific container images from the Red Hat Repository and select the required image.</li><li>2. Click <b>Get this image</b> to find the command for your container image.</li><li>3. Log in by running the following command and entering your username and password to authenticate. Example output is shown for demonstrative purposes.</li></ol><pre>$ podman login registry.redhat.io</pre><pre>Username:<your_registry_account_username><br/>Password:<your_registry_account_password></pre><ol><li>4. Download the image and save it locally by running the following command:</li></ol><pre>$ podman pull registry.redhat.io/<repository_name></pre><h2>1.5. RED HAT QUAY REGISTRIES</h2><p>If you need an enterprise-quality container image registry, Red Hat Quay is available both as a hosted service and as software that you can install in your own data center or cloud environment. Advanced features in Red Hat Quay include geo-replication, image scanning, and the ability to roll back images.</p><p>Visit the <a href=\"#\">Quay.io</a> site to set up your own hosted Quay registry account. After that, follow the Quay Tutorial to log in to the Quay registry and start managing your images.</p><p>You can access your Red Hat Quay registry from OpenShift Container Platform, similar to any remote container image registry.</p><h3>Additional resources</h3><ul><li>• <a href=\"#\">Red Hat Quay product documentation</a></li></ul><h2>1.6. AUTHENTICATION ENABLED RED HAT REGISTRY</h2><p>All container images available through the Container images section of the Red Hat Ecosystem Catalog are hosted on an image registry, <b>registry.redhat.io</b>. The registry, <b>registry.redhat.io</b>, requires authentication for access to images and hosted content on OpenShift Container Platform.</p><h3>NOTE</h3><p>OpenShift Container Platform pulls images from <b>registry.redhat.io</b>, so you must configure your cluster to use it.</p><p>The new registry uses standard OAuth mechanisms for authentication, with the following methods:</p><ul><li>• <b>Authentication token.</b> Tokens, which are generated by administrators, are service accounts that give systems the ability to authenticate against the container image registry. Service accounts are not affected by changes in user accounts, so the token authentication method is reliable and resilient. This is the only supported authentication option for production clusters.</li></ul><ul><li>● <b>Web username and password.</b> This is the standard set of credentials you use to log in to resources such as <b>access.redhat.com</b>. While you could use this authentication method with OpenShift Container Platform, Red Hat does not support the method for production deployments. Restrict this authentication method to standalone projects outside OpenShift Container Platform.</li></ul><p>You can use <b>podman login</b> with your credentials, either username and password or authentication token, to access content on the new registry.</p><p>All image streams point to the new registry, which uses the installation pull secret to authenticate.</p><p>You must place your credentials in either of the following places:</p><ul><li>● <b>openshift namespace.</b> Your credentials must exist in the <b>openshift</b> namespace so that the image streams in the <b>openshift</b> namespace can import.</li><li>● <b>Your host.</b> Your credentials must exist on your host because Kubernetes uses the credentials from your host when it goes to pull images.</li></ul><h4>Additional resources</h4><ul><li>● <a href=\"#\">Registry service accounts</a></li></ul><h1>CHAPTER 2. IMAGE REGISTRY OPERATOR IN OPENSHIFT CONTAINER PLATFORM</h1><h2>2.1. IMAGE REGISTRY ON CLOUD PLATFORMS AND OPENSTACK</h2><p>The Image Registry Operator installs a single instance of the OpenShift image registry and manages all registry configuration, including setting up registry storage.</p><h3>NOTE</h3><p>Storage is only automatically configured when you install an installer-provisioned infrastructure cluster on AWS, Azure, Google Cloud, IBM®, or RHOSP.</p><p>When you install or upgrade an installer-provisioned infrastructure cluster on AWS, Azure, Google Cloud, IBM®, or RHOSP, the Image Registry Operator sets the <b>spec.storage.managementState</b> parameter to <b>Managed</b>. If the <b>spec.storage.managementState</b> parameter is set to <b>Unmanaged</b>, the Image Registry Operator takes no action related to storage.</p><p>After the control plane deploys in the management cluster, the Operator creates a default <b>configs.imageregistry.operator.openshift.io</b> custom resource (CR) instance based on configuration detected in the cluster.</p><p>If insufficient information is available to define a complete <b>configs.imageregistry.operator.openshift.io</b> CR, the incomplete resource is defined and the Operator updates the resource status with information about what is missing.</p><h3>IMPORTANT</h3><p>The Image Registry Operator's behavior for managing the pruner is orthogonal to the <b>managementState</b> specified on the <b>ClusterOperator</b> object for the Image Registry Operator. If the Image Registry Operator is not in the <b>Managed</b> state, the image pruner can still be configured and managed by the <b>Pruning</b> custom resource.</p><p>However, the <b>managementState</b> of the Image Registry Operator alters the behavior of the deployed image pruner job:</p><ul><li>● <b>Managed</b>: the <b>--prune-registry</b> flag for the image pruner is set to <b>true</b>.</li><li>● <b>Removed</b>: the <b>--prune-registry</b> flag for the image pruner is set to <b>false</b>, meaning the image pruner job only prunes image metadata in etc.</li></ul><h2>2.2. IMAGE REGISTRY ON BARE METAL, NUTANIX, AND VSPHERE</h2><h3>2.2.1. Image registry removed during installation</h3><p>On platforms that do not provide shareable object storage, the OpenShift Image Registry Operator bootstraps itself as <b>Removed</b>. This allows <b>openshift-installer</b> to complete installations on these platform types.</p><p>After installation, you must edit the Image Registry Operator configuration to switch the <b>managementState</b> from <b>Removed</b> to <b>Managed</b>. When this has completed, you must configure storage.</p>\n<h2>2.3. IMAGE REGISTRY OPERATOR DISTRIBUTION ACROSS AVAILABILITY ZONES</h2>\n\n<p>The default configuration of the Image Registry Operator spreads image registry pods across topology zones to prevent delayed recovery times in case of a complete zone failure where all pods are impacted. Reference the following YAML to understand the default parameter values that the Image Registry Operator uses when the Operator deploys with a zone-related topology constraint:</p>\n\n<pre>topologySpreadConstraints:\n- labelSelector:\n matchLabels:\n docker-registry: default\n maxSkew: 1\n topologyKey: kubernetes.io/hostname\n whenUnsatisfiable: DoNotSchedule\n- labelSelector:\n matchLabels:\n docker-registry: default\n maxSkew: 1\n topologyKey: node-role.kubernetes.io/worker\n whenUnsatisfiable: DoNotSchedule\n- labelSelector:\n matchLabels:\n docker-registry: default\n maxSkew: 1\n topologyKey: topology.kubernetes.io/zone\n whenUnsatisfiable: DoNotSchedule</pre>\n\n<p>Reference the following YAML to understand the default parameter value that the Image Registry Operator uses when the Operator deploys with a zone-related topology constraint, which applies to bare metal and vSphere instances:</p>\n\n<pre>topologySpreadConstraints:\n- labelSelector:\n matchLabels:\n docker-registry: default\n maxSkew: 1\n topologyKey: kubernetes.io/hostname\n whenUnsatisfiable: DoNotSchedule\n- labelSelector:\n matchLabels:\n docker-registry: default\n maxSkew: 1\n topologyKey: node-role.kubernetes.io/worker\n whenUnsatisfiable: DoNotSchedule</pre>\n\n<p>As a cluster administrator, you can override the default <b>topologySpreadConstraints</b> section values by configuring the <b>configs.imageregistry.operator.openshift.io/cluster</b> spec file.</p>\n\n<h2>2.4. ADDITIONAL RESOURCES</h2>\n\n<ul>\n<li>• <a href=\"#\">Configuring pod topology spread constraints</a></li>\n</ul>\n\n<h2>2.5. IMAGE REGISTRY OPERATOR CONFIGURATION PARAMETERS</h2>\n\n<p>You can configure the Image Registry Operator using the <b>configs.imageregistry.operator.openshift.io</b> resource. The resource provides parameters for managing registry state, storage, logging, routing, and deployment settings.</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th data-bbox=\"88 148 312 183\">Parameter</th>\n<th data-bbox=\"312 148 905 183\">Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td data-bbox=\"88 183 312 315\"><b>managementState</b></td>\n<td data-bbox=\"312 183 905 315\">\n<p><b>Managed:</b> The Operator updates the registry as configuration resources are updated.</p>\n<p><b>Unmanaged:</b> The Operator ignores changes to the configuration resources.</p>\n<p><b>Removed:</b> The Operator removes the registry instance and tear down any storage that the Operator provisioned.</p>\n</td>\n</tr>\n<tr>\n<td data-bbox=\"88 315 312 513\"><b>logLevel</b></td>\n<td data-bbox=\"312 315 905 513\">\n<p>Sets <b>logLevel</b> of the registry instance. Defaults to <b>Normal</b>.</p>\n<p>The following values for <b>logLevel</b> are supported:</p>\n<ul style=\"list-style-type: none;\">\n<li>• <b>Normal</b></li>\n<li>• <b>Debug</b></li>\n<li>• <b>Trace</b></li>\n<li>• <b>TraceAll</b></li>\n</ul>\n</td>\n</tr>\n<tr>\n<td data-bbox=\"88 513 312 551\"><b>httpSecret</b></td>\n<td data-bbox=\"312 513 905 551\">Value needed by the registry to secure uploads, generated by default.</td>\n</tr>\n<tr>\n<td data-bbox=\"88 551 312 813\"><b>operatorLogLevel</b></td>\n<td data-bbox=\"312 551 905 813\">\n<p>The <b>operatorLogLevel</b> configuration parameter provides intent-based logging for the Operator itself and a simple way to manage coarse-grained logging choices that Operators must interpret for themselves. This configuration parameter defaults to <b>Normal</b>. It does not provide fine-grained control.</p>\n<p>The following values for <b>operatorLogLevel</b> are supported:</p>\n<ul style=\"list-style-type: none;\">\n<li>• <b>Normal</b></li>\n<li>• <b>Debug</b></li>\n<li>• <b>Trace</b></li>\n<li>• <b>TraceAll</b></li>\n</ul>\n</td>\n</tr>\n<tr>\n<td data-bbox=\"88 813 312 851\"><b>proxy</b></td>\n<td data-bbox=\"312 813 905 851\">Defines the Proxy to be used when calling master API and upstream registries.</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th data-bbox=\"91 48 312 84\">Parameter</th>\n<th data-bbox=\"312 48 909 84\">Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td data-bbox=\"91 84 312 221\"><b>affinity</b></td>\n<td data-bbox=\"312 84 909 221\">\n<p>You can use the <b>affinity</b> parameter to configure pod scheduling preferences and constraints for Image Registry Operator pods.</p>\n<p>Affinity settings can use the <b>podAffinity</b> or <b>podAntiAffinity</b> spec. Both options can use either <b>preferredDuringSchedulingIgnoredDuringExecution</b> rules or <b>requiredDuringSchedulingIgnoredDuringExecution</b> rules.</p>\n</td>\n</tr>\n<tr>\n<td data-bbox=\"91 221 312 276\"><b>storage</b></td>\n<td data-bbox=\"312 221 909 276\"><b>StorageType</b>: Details for configuring registry storage, for example S3 bucket coordinates. Normally configured by default.</td>\n</tr>\n<tr>\n<td data-bbox=\"91 276 312 328\"><b>readOnly</b></td>\n<td data-bbox=\"312 276 909 328\">Indicates whether the registry instance should reject attempts to push new images or delete existing ones.</td>\n</tr>\n<tr>\n<td data-bbox=\"91 328 312 381\"><b>requests</b></td>\n<td data-bbox=\"312 328 909 381\">API Request Limit details. Controls how many parallel requests a given registry instance will handle before queuing additional requests.</td>\n</tr>\n<tr>\n<td data-bbox=\"91 381 312 436\"><b>defaultRoute</b></td>\n<td data-bbox=\"312 381 909 436\">Determines whether or not an external route is defined using the default hostname. If enabled, the route uses re-encrypt encryption. Defaults to <b>false</b>.</td>\n</tr>\n<tr>\n<td data-bbox=\"91 436 312 491\"><b>routes</b></td>\n<td data-bbox=\"312 436 909 491\">Array of additional routes to create. You provide the hostname and certificate for the route.</td>\n</tr>\n<tr>\n<td data-bbox=\"91 491 312 546\"><b>rolloutStrategy</b></td>\n<td data-bbox=\"312 491 909 546\">Defines rollout strategy for the image registry deployment. Defaults to <b>RollingUpdate</b>.</td>\n</tr>\n<tr>\n<td data-bbox=\"91 546 312 584\"><b>replicas</b></td>\n<td data-bbox=\"312 546 909 584\">Replica count for the registry.</td>\n</tr>\n<tr>\n<td data-bbox=\"91 584 312 636\"><b>disableRedirect</b></td>\n<td data-bbox=\"312 584 909 636\">Controls whether to route all data through the registry, rather than redirecting to the back end. Defaults to <b>false</b>.</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th data-bbox=\"88 48 311 83\">Parameter</th>\n<th data-bbox=\"311 48 906 83\">Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td data-bbox=\"88 83 311 446\"><b>spec.storage.managementState</b></td>\n<td data-bbox=\"311 83 906 446\">\n<p>The Image Registry Operator sets the <b>spec.storage.managementState</b> parameter to <b>Managed</b> on new installations or upgrades of clusters using installer-provisioned infrastructure on AWS or Azure.</p>\n<ul style=\"list-style-type: none;\">\n<li>● <b>Managed</b>: Determines that the Image Registry Operator manages underlying storage. If the Image Registry Operator's <b>managementState</b> is set to <b>Removed</b>, then the storage is deleted.\n<ul style=\"list-style-type: none;\">\n<li>○ If the <b>managementState</b> is set to <b>Managed</b>, the Image Registry Operator attempts to apply some default configuration on the underlying storage unit. For example, if set to <b>Managed</b>, the Operator tries to enable encryption on the S3 bucket before making it available to the registry. If you do not want the default settings to be applied on the storage you are providing, make sure the <b>managementState</b> is set to <b>Unmanaged</b>.</li>\n</ul>\n</li>\n<li>● <b>Unmanaged</b>: Determines that the Image Registry Operator ignores the storage settings. If the Image Registry Operator's <b>managementState</b> is set to <b>Removed</b>, then the storage is not deleted. If you provided an underlying storage unit configuration, such as a bucket or container name, and the <b>spec.storage.managementState</b> is not yet set to any value, then the Image Registry Operator configures it to <b>Unmanaged</b>.</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.6. ENABLING THE IMAGE REGISTRY DEFAULT ROUTE BY USING A CRD</h2>\n\n<p>In OpenShift Container Platform, the <b>Registry</b> Operator controls the OpenShift image registry feature and you define this Operator in the <b>configs.imageregistry.operator.openshift.io</b> Custom Resource Definition (CRD). If you need to automatically enable the Image Registry default route, patch the Image Registry Operator CRD.</p>\n\n<h3>Procedure</h3>\n\n<ul style=\"list-style-type: none;\">\n<li>● Patch the Image Registry Operator CRD:</li>\n</ul>\n\n<pre>$ oc patch configs.imageregistry.operator.openshift.io/cluster --type merge -p '{\"spec\": {\"defaultRoute\":true}}'</pre>\n\n<h2>2.7. CONFIGURING ADDITIONAL TRUST STORES FOR IMAGE REGISTRY ACCESS</h2>\n\n<p>You can add references to a config map that has additional certificate authorities (CAs) to be trusted during image registry access to the <b>image.config.openshift.io/cluster</b> custom resource (CR).</p>\n\n<h3>Prerequisites</h3>\n\n<ul style=\"list-style-type: none;\">\n<li>● The certificate authorities (CAs) must be PEM-encoded.</li>\n</ul>\n\n<h3>Procedure</h3>\n\n<ol>\n<li>1. Create a config map in the <b>openshift-config</b> namespace, then and use the config map name in the <b>AdditionalTrustedCA</b> parameter of the <b>image.config.openshift.io</b> CR. This adds CAs that should be trusted when the cluster contacts external image registries.</li>\n</ol>\n\n<h3>Image registry CA config map example</h3>\n\n<pre>apiVersion: v1\nkind: ConfigMap\nmetadata:\n name: my-registry-ca\ndata:\n registry.example.com: |\n -----BEGIN CERTIFICATE-----\n ...\n -----END CERTIFICATE-----\n registry-with-port.example.com..5000: |\n -----BEGIN CERTIFICATE-----\n ...\n -----END CERTIFICATE-----</pre>\n\n<p>where:</p>\n\n<h4><b>data:registry.example.com:</b></h4>\n\n<p>An example hostname of a registry for which this CA is to be trusted.</p>\n\n<h4><b>data:registry-with-port.example.com..5000:</b></h4>\n\n<p>An example hostname of a registry with the port for which this CA is to be trusted. If the registry has a port, such as <b>registry-with-port.example.com:5000</b>, : must be replaced with ...<br/>The PEM certificate content is the value for each additional registry CA to trust.</p>\n\n<ol>\n<li>2. Optional. Configure an additional CA by running the following command:</li>\n</ol>\n\n<pre>$ oc create configmap registry-config --from-file=<external_registry_address>=ca.crt -n openshift-config</pre>\n\n<pre>$ oc edit image.config.openshift.io cluster</pre>\n\n<pre>spec:\n additionalTrustedCA:\n name: registry-config</pre>\n\n<h2>2.8. CONFIGURING STORAGE CREDENTIALS FOR THE IMAGE REGISTRY OPERATOR</h2>\n\n<p>In addition to the <b>configs.imageregistry.operator.openshift.io</b> Custom Resource (CR) and ConfigMap resources, storage credential configuration is provided to the Operator by a separate secret resource. This resource is located within the <b>openshift-image-registry</b> namespace.</p>\n\n<p>You can create an <b>image-registry-private-configuration-user</b> secret that in turn creates custom credentials needed for storage access and management. If default credentials exist, the custom credentials override the default credentials used by the Operator.</p>\n<h2>Procedure</h2><ul><li>• Create an OpenShift Container Platform secret that contains the required keys.</li></ul><pre>$ oc create secret generic image-registry-private-configuration-user --from-literal=KEY1=value1 --from-literal=KEY2=value2 --namespace openshift-image-registry</pre><h2>2.9. ADDITIONAL RESOURCES</h2><ul><li>• <a href=\"#\">Configuring the registry for AWS user-provisioned infrastructure</a></li><li>• <a href=\"#\">Configuring the registry for Google Cloud user-provisioned infrastructure</a></li><li>• <a href=\"#\">Configuring the registry for Azure user-provisioned infrastructure</a></li><li>• <a href=\"#\">Configuring the registry for bare metal</a></li><li>• <a href=\"#\">Configuring the registry for vSphere</a></li><li>• <a href=\"#\">Configuring the registry for RHOSP</a></li><li>• <a href=\"#\">Configuring the registry for Red Hat OpenShift Data Foundation</a></li><li>• <a href=\"#\">Configuring the registry for Nutanix</a></li></ul>\n<h2>CHAPTER 3. SETTING UP AND CONFIGURING THE REGISTRY</h2>\n\n<h3>3.1. CONFIGURING THE REGISTRY FOR AWS USER-PROVISIONED INFRASTRUCTURE</h3>\n\n<p>Save your container images to a durable storage location by configuring the built-in image registry to use dedicated AWS storage. This setup provides persistent scalable storage for your registry, separate from ephemeral cluster storage.</p>\n\n<h4>3.1.1. Configuring a secret for the Image Registry Operator</h4>\n\n<p>In addition to the <b>configs.imageregistry.operator.openshift.io</b> and ConfigMap resources, configuration is provided to the Operator by a separate secret resource located within the <b>openshift-image-registry</b> namespace.</p>\n\n<p>The <b>image-registry-private-configuration-user</b> secret provides credentials needed for storage access and management. It overrides the default credentials used by the Operator, if default credentials were found.</p>\n\n<p>For S3 on AWS storage, the secret is expected to contain two keys:</p>\n\n<ul>\n<li>• <b>REGISTRY_STORAGE_S3_ACCESSKEY</b></li>\n<li>• <b>REGISTRY_STORAGE_S3_SECRETKEY</b></li>\n</ul>\n\n<h4>Procedure</h4>\n\n<ul>\n<li>• Create an OpenShift Container Platform secret that contains the required keys.</li>\n</ul>\n\n<pre>$ oc create secret generic image-registry-private-configuration-user --from-literal=REGISTRY_STORAGE_S3_ACCESSKEY=myaccesskey --from-literal=REGISTRY_STORAGE_S3_SECRETKEY=mysecretkey --namespace openshift-image-registry</pre>\n\n<h4>3.1.2. Configuring registry storage for AWS with user-provisioned infrastructure</h4>\n\n<p>During installation, your cloud credentials are sufficient to create an Amazon S3 bucket and the Registry Operator will automatically configure storage.</p>\n\n<p>If the Registry Operator cannot create an S3 bucket and automatically configure storage, you can create an S3 bucket and configure storage with the following procedure.</p>\n\n<h4>WARNING</h4>\n\n<p>To secure your registry images in AWS, <a href=\"#\">block public access</a> to the S3 bucket.</p>\n\n<h4>Prerequisites</h4>\n\n<ul>\n<li>• You have a cluster on AWS with user-provisioned infrastructure.</li>\n<li>• For Amazon S3 storage, the secret is expected to contain two keys:\n <ul>\n<li>◦ <b>REGISTRY_STORAGE_S3_ACCESSKEY</b></li>\n<li>◦ <b>REGISTRY_STORAGE_S3_SECRETKEY</b></li>\n</ul>\n</li>\n</ul>\n\n<h3>Procedure</h3>\n\n<ol>\n<li>1. Set up a <a href=\"#\">Bucket Lifecycle Policy</a> to abort incomplete multipart uploads that are one day old.</li>\n<li>2. Fill in the storage configuration in <b>configs.imageregistry.operator.openshift.io/cluster</b>:</li>\n</ol>\n\n<pre>$ oc edit configs.imageregistry.operator.openshift.io/cluster</pre>\n\n<h3>Example configuration</h3>\n\n<pre>apiVersion: imageregistry.operator.openshift.io/v1\nkind: Config\nmetadata:\n name: cluster\nspec:\n storage:\n s3:\n bucket: <bucket_name>\n region: <region_name></pre>\n\n<h3>3.1.3. Image Registry Operator configuration parameters for AWS S3</h3>\n\n<p>The following configuration parameters are available for AWS S3 registry storage.</p>\n\n<p>The image registry <b>spec.storage.s3</b> configuration parameter holds the information to configure the registry to use the AWS S3 service for back-end storage. See the <a href=\"#\">S3 storage driver documentation</a> for more information.</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>bucket</b></td>\n<td>Bucket is the bucket name in which you want to store the registry's data. It is optional and is generated if not provided.</td>\n</tr>\n<tr>\n<td><b>chunkSizeMiB</b></td>\n<td>ChunkSizeMiB is the size of the multipart upload chunks of the S3 API. The default is <b>10</b> MiB with a minimum of <b>5</b> MiB.</td>\n</tr>\n<tr>\n<td><b>region</b></td>\n<td>Region is the AWS region in which your bucket exists. It is optional and is set based on the installed AWS Region.</td>\n</tr>\n<tr>\n<td><b>regionEndpoint</b></td>\n<td>RegionEndpoint is the endpoint for S3 compatible storage services. It is optional and defaults based on the Region that is provided.</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>virtualHostedStyle</b></td>\n<td>VirtualHostedStyle enables using S3 virtual hosted style bucket paths with a custom RegionEndpoint. It is optional and defaults to false.<br/><br/>Set this parameter to deploy OpenShift Container Platform to hidden regions.</td>\n</tr>\n<tr>\n<td><b>encrypt</b></td>\n<td>Encrypt specifies whether or not the registry stores the image in encrypted format. It is optional and defaults to false.</td>\n</tr>\n<tr>\n<td><b>keyID</b></td>\n<td>KeyID is the KMS key ID to use for encryption. It is optional. Encrypt must be true, or this parameter is ignored.</td>\n</tr>\n<tr>\n<td><b>cloudFront</b></td>\n<td>CloudFront configures Amazon Cloudfront as the storage middleware in a registry. It is optional.</td>\n</tr>\n<tr>\n<td><b>trustedCA</b></td>\n<td>The namespace for the config map referenced by <b>trustedCA</b> is <b>openshift-config</b>. The key for the bundle in the config map is <b>ca-bundle.crt</b>. It is optional.</td>\n</tr>\n</tbody>\n</table>\n\n<h4>NOTE</h4>\n\n<p>When the value of the <b>regionEndpoint</b> parameter is configured to a URL of a Rados Gateway, an explicit port must not be specified. For example:</p>\n\n<pre>regionEndpoint: http://rook-ceph-rgw-ocs-storagecluster-cephobjectstore.openshift-storage.svc.cluster.local</pre>\n\n<h2>3.2. CONFIGURING THE REGISTRY FOR GOOGLE CLOUD USER-PROVISIONED INFRASTRUCTURE</h2>\n\n<p>Save your container images to a durable storage location by configuring the built-in image registry to use dedicated Google Cloud storage. This setup provides persistent scalable storage for your registry, separate from ephemeral cluster storage.</p>\n\n<h3>3.2.1. Configuring a secret for the Image Registry Operator</h3>\n\n<p>In addition to the <b>configs.imageregistry.operator.openshift.io</b> and ConfigMap resources, configuration is provided to the Operator by a separate secret resource located within the <b>openshift-image-registry</b> namespace.</p>\n\n<p>The <b>image-registry-private-configuration-user</b> secret provides credentials needed for storage access and management. It overrides the default credentials used by the Operator, if default credentials were found.</p>\n\n<p>For GCS on Google Cloud storage, the secret is expected to contain one key whose value is the contents of a credentials file provided by Google Cloud:</p>\n\n<ul>\n<li>• <b>REGISTRY_STORAGE_GCS_KEYFILE</b></li>\n</ul>\n<h2>Procedure</h2><ul><li>• Create an OpenShift Container Platform secret that contains the required keys.</li></ul><pre>$ oc create secret generic image-registry-private-configuration-user --from-file=REGISTRY_STORAGE_GCS_KEYFILE=<path_to_keyfile> --namespace openshift-image-registry</pre><h3>3.2.2. Configuring the registry storage for Google Cloud with user-provisioned infrastructure</h3><p>If the Registry Operator cannot create a Google Cloud bucket, you must set up the storage medium manually and configure the settings in the registry custom resource (CR).</p><h4>Prerequisites</h4><ul><li>• A cluster on Google Cloud with user-provisioned infrastructure.</li><li>• To configure registry storage for Google Cloud, you need to provide Registry Operator cloud credentials.</li><li>• For GCS on Google Cloud storage, the secret is expected to contain one key whose value is the contents of a credentials file provided by Google Cloud:<ul><li>◦ <b>REGISTRY_STORAGE_GCS_KEYFILE</b></li></ul></li></ul><h4>WARNING</h4><p>You can secure your registry images that use a Google Cloud Storage bucket by setting <a href=\"#\">public access prevention</a>.</p><h2>Procedure</h2><ol><li>1. Set up an <a href=\"#\">Object Lifecycle Management policy</a> to abort incomplete multipart uploads that are one day old.</li><li>2. Fill in the storage configuration in <b>configs.imageregistry.operator.openshift.io/cluster</b>:</li></ol><pre>$ oc edit configs.imageregistry.operator.openshift.io/cluster</pre><h4>Example configuration</h4><pre>apiVersion: imageregistry.operator.openshift.io/v1\nkind: Config\nmetadata:\n name: cluster\nspec:\n storage:\n gcs:</pre>\n<pre>bucket: <bucket_name>\nprojectId: <project_id>\nregion: <region_name></pre>\n\n<h3>3.2.3. Image Registry Operator configuration parameters for Google Cloud GCS</h3>\n\n<p>The following parameters configure are available to configure your Google Cloud GCS registry storage.</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>bucket</b></td>\n<td>Bucket is the bucket name in which you want to store the registry's data. It is optional and is generated if not provided.</td>\n</tr>\n<tr>\n<td><b>region</b></td>\n<td>Region is the GCS location in which your bucket exists. It is optional and is set based on the installed GCS Region.</td>\n</tr>\n<tr>\n<td><b>projectId</b></td>\n<td>ProjectID is the Project ID of the Google Cloud project that this bucket should be associated with. It is optional.</td>\n</tr>\n<tr>\n<td><b>keyID</b></td>\n<td>KeyID is the KMS key ID to use for encryption. It is optional because buckets are encrypted by default on Google Cloud. This allows for the use of a custom encryption key.</td>\n</tr>\n</tbody>\n</table>\n\n<h2>3.3. CONFIGURING THE REGISTRY FOR OPENSTACK USER-PROVISIONED INFRASTRUCTURE</h2>\n\n<p>You can configure the registry of a cluster that runs on your own Red Hat OpenStack Platform (RHOSP) infrastructure.</p>\n\n<h3>3.3.1. Configuring Image Registry Operator redirects</h3>\n\n<p>By disabling redirects, you can configure the Image Registry Operator to control whether clients such as OpenShift Container Platform cluster builds or external systems like developer machines are redirected to pull images directly from Red Hat OpenStack Platform (RHOSP) Swift storage. This configuration is optional and depends on whether the clients trust the storage's SSL/TLS certificates.</p>\n\n<h4>NOTE</h4>\n\n<p>In situations where clients do not trust the storage certificate, setting the <b>disableRedirect</b> option can be set to <b>true</b> proxies traffic through the image registry. Consequently, however, the image registry might require more resources, especially network bandwidth, to handle the increased load.</p>\n\n<p>Alternatively, if clients trust the storage certificate, the registry can allow redirects. This reduces resource demand on the registry itself.</p>\n\n<p>Some users might prefer to configure their clients to trust their self-signed certificate authorities (CAs) instead of disabling redirects. If you are using a self-signed CA, you must decide between trusting the custom CAs or disabling redirects.</p>\n\n<h4>Procedure</h4>\n\n<ul>\n<li>• To ensure that the image registry proxies traffic instead of relying on Swift storage, change the value of the <b>spec.disableRedirect</b> field in the <b>config.imageregistry</b> object to <b>true</b> by running the following command:</li>\n</ul>\n\n<pre>$ oc patch configs.imageregistry.operator.openshift.io cluster --type merge --patch '{\"spec\":{\"disableRedirect\":\"true\"}}'</pre>\n\n<h3>3.3.2. Configuring a secret for the Image Registry Operator</h3>\n\n<p>In addition to the <b>configs.imageregistry.operator.openshift.io</b> and ConfigMap resources, configuration is provided to the Operator by a separate secret resource located within the <b>openshift-image-registry</b> namespace.</p>\n\n<p>The <b>image-registry-private-configuration-user</b> secret provides credentials needed for storage access and management. It overrides the default credentials used by the Operator, if default credentials were found.</p>\n\n<p>For Swift on Red Hat OpenStack Platform (RHOSP) storage, the secret is expected to contain the following two keys:</p>\n\n<ul>\n<li>• <b>REGISTRY_STORAGE_SWIFT_USERNAME</b></li>\n<li>• <b>REGISTRY_STORAGE_SWIFT_PASSWORD</b></li>\n</ul>\n\n<h4>Procedure</h4>\n\n<ul>\n<li>• Create an OpenShift Container Platform secret that contains the required keys.</li>\n</ul>\n\n<pre>$ oc create secret generic image-registry-private-configuration-user --from-literal=REGISTRY_STORAGE_SWIFT_USERNAME=<username> --from-literal=REGISTRY_STORAGE_SWIFT_PASSWORD=<password> -n openshift-image-registry</pre>\n\n<h3>3.3.3. Registry storage for RHOSP with user-provisioned infrastructure</h3>\n\n<p>If the Registry Operator cannot create a Swift bucket, you must set up the storage medium manually and configure the settings in the registry custom resource (CR).</p>\n\n<h4>Prerequisites</h4>\n\n<ul>\n<li>• A cluster on Red Hat OpenStack Platform (RHOSP) with user-provisioned infrastructure.</li>\n<li>• To configure registry storage for RHOSP, you need to provide Registry Operator cloud credentials.</li>\n<li>• For Swift on RHOSP storage, the secret is expected to contain the following two keys:\n <ul>\n<li>◦ <b>REGISTRY_STORAGE_SWIFT_USERNAME</b></li>\n<li>◦ <b>REGISTRY_STORAGE_SWIFT_PASSWORD</b></li>\n</ul>\n</li>\n</ul>\n\n<h4>Procedure</h4>\n\n<ul>\n<li>• Fill in the storage configuration in <b>configs.imageregistry.operator.openshift.io/cluster</b>:</li>\n</ul>\n\n<pre>$ oc edit configs.imageregistry.operator.openshift.io/cluster</pre>\n\n<h3>Example configuration</h3>\n\n<pre>apiVersion: imageregistry.operator.openshift.io/v1\nkind: Config\nmetadata:\n name: cluster\nspec:\n storage:\n swift:\n container: <container_id></pre>\n\n<h3>3.3.4. Image Registry Operator configuration parameters for RHOSP Swift</h3>\n\n<p>The following parameters are available for you to configure your Red Hat OpenStack Platform (RHOSP) Swift registry storage.</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>authURL</b></td>\n<td>Defines the URL for obtaining the authentication token. This value is optional.</td>\n</tr>\n<tr>\n<td><b>authVersion</b></td>\n<td>Specifies the Auth version of RHOSP, for example, <b>authVersion: \"3\"</b>. This value is optional.</td>\n</tr>\n<tr>\n<td><b>container</b></td>\n<td>Defines the name of a Swift container for storing registry data. This value is optional.</td>\n</tr>\n<tr>\n<td><b>domain</b></td>\n<td>Specifies the RHOSP domain name for the Identity v3 API. This value is optional.</td>\n</tr>\n<tr>\n<td><b>domainID</b></td>\n<td>Specifies the RHOSP domain ID for the Identity v3 API. This value is optional.</td>\n</tr>\n<tr>\n<td><b>tenant</b></td>\n<td>Defines the RHOSP tenant name to be used by the registry. This value is optional.</td>\n</tr>\n<tr>\n<td><b>tenantID</b></td>\n<td>Defines the RHOSP tenant ID to be used by the registry. This value is optional.</td>\n</tr>\n<tr>\n<td><b>regionName</b></td>\n<td>Defines the RHOSP region in which the container exists. This value is optional.</td>\n</tr>\n</tbody>\n</table>\n\n<h2>3.4. CONFIGURING THE REGISTRY FOR AZURE USER-PROVISIONED INFRASTRUCTURE</h2>\n\n<p>Save your container images to a durable storage location by configuring the built-in image registry to use dedicated Azure storage. This setup provides persistent scalable storage for your registry, separate from ephemeral cluster storage.</p>\n\n<h3>3.4.1. Configuring a secret for the Image Registry Operator</h3>\n<p>In addition to the <b>configs.imageregistry.operator.openshift.io</b> and ConfigMap resources, configuration is provided to the Operator by a separate secret resource located within the <b>openshift-image-registry</b> namespace.</p><p>The <b>image-registry-private-configuration-user</b> secret provides credentials needed for storage access and management. It overrides the default credentials used by the Operator, if default credentials were found.</p><p>For Azure registry storage, the secret is expected to contain one key whose value is the contents of a credentials file provided by Azure:</p><ul><li>• <b>REGISTRY_STORAGE_AZURE_ACCOUNTKEY</b></li></ul><h3>Procedure</h3><ul><li>• Create an OpenShift Container Platform secret that contains the required key.</li></ul><pre>$ oc create secret generic image-registry-private-configuration-user --from-literal=REGISTRY_STORAGE_AZURE_ACCOUNTKEY=<accountkey> --namespace openshift-image-registry</pre><h2>3.4.2. Configuring registry storage for Azure</h2><p>During installation, your cloud credentials are sufficient to create Azure Blob Storage, and the Registry Operator automatically configures storage.</p><h3>Prerequisites</h3><ul><li>• A cluster on Azure with user-provisioned infrastructure.</li><li>• To configure registry storage for Azure, provide Registry Operator cloud credentials.</li><li>• For Azure storage the secret is expected to contain one key:<ul><li>◦ <b>REGISTRY_STORAGE_AZURE_ACCOUNTKEY</b></li></ul></li></ul><h3>Procedure</h3><ol><li>1. Create an <a href=\"#\">Azure storage container</a>.</li><li>2. Fill in the storage configuration in <b>configs.imageregistry.operator.openshift.io/cluster</b>:</li></ol><pre>$ oc edit configs.imageregistry.operator.openshift.io/cluster</pre><h3>Example configuration</h3><pre>apiVersion: imageregistry.operator.openshift.io/v1\nkind: Config\nmetadata:\n name: cluster\nspec:\n storage:</pre>\n<pre>azure:\n accountName: <storage_account_name>\n container: <container_name></pre>\n\n<h3>3.4.3. Configuring registry storage for Azure Government</h3>\n\n<p>During installation, your cloud credentials are sufficient to create Azure Blob Storage, and the Registry Operator automatically configures storage.</p>\n\n<h4>Prerequisites</h4>\n\n<ul>\n<li>• A cluster on Azure with user-provisioned infrastructure in a government region.</li>\n<li>• To configure registry storage for Azure, provide Registry Operator cloud credentials.</li>\n<li>• For Azure storage, the secret is expected to contain one key:\n <ul>\n<li>◦ <b>REGISTRY_STORAGE_AZURE_ACCOUNTKEY</b></li>\n</ul>\n</li>\n</ul>\n\n<h4>Procedure</h4>\n\n<ol>\n<li>1. Create an <a href=\"#\">Azure storage container</a>.</li>\n<li>2. Fill in the storage configuration in <b>configs.imageregistry.operator.openshift.io/cluster</b>:</li>\n</ol>\n\n<pre>$ oc edit configs.imageregistry.operator.openshift.io/cluster</pre>\n\n<h4>Example configuration</h4>\n\n<pre>storage:\n azure:\n accountName: <storage-account-name>\n container: <container-name>\n cloudName: AzureUSGovernmentCloud</pre>\n\n<p><b>cloudName</b> is the name of the Azure cloud environment, which can be used to configure the Azure SDK with the appropriate Azure API endpoints. Defaults to <b>AzurePublicCloud</b>. You can also set <b>cloudName</b> to <b>AzureUSGovernmentCloud</b>, <b>AzureChinaCloud</b>, or <b>AzureGermanCloud</b> with sufficient credentials.</p>\n\n<h2>3.5. CONFIGURING THE REGISTRY FOR RHOSP</h2>\n\n<p>You configure the image registry to use custom storage on clusters that run on RHOSP. You must configure custom storage to use a Cinder volume in a specific availability zone.</p>\n\n<h3>3.5.1. Configuring an image registry with custom storage on clusters that run on RHOSP</h3>\n\n<p>After you install a cluster on Red Hat OpenStack Platform (RHOSP), you can use a Cinder volume that is in a specific availability zone for registry storage.</p>\n\n<h4>Procedure</h4>\n<ol><li>1. Create a YAML file that specifies the storage class and availability zone to use. For example:</li></ol><pre>apiVersion: storage.k8s.io/v1\nkind: StorageClass\nmetadata:\n name: custom-csi-storageclass\nprovisioner: cinder.csi.openstack.org\nvolumeBindingMode: WaitForFirstConsumer\nallowVolumeExpansion: true\nparameters:\n availability: <availability_zone_name></pre><h4>NOTE</h4><p>OpenShift Container Platform does not verify the existence of the availability zone you choose. Verify the name of the availability zone before you apply the configuration.</p><ol><li>2. From a command line, apply the configuration:</li></ol><pre>$ oc apply -f <storage_class_file_name></pre><h4>Example output</h4><pre>storageclass.storage.k8s.io/custom-csi-storageclass created</pre><ol><li>3. Create a YAML file that specifies a persistent volume claim (PVC) that uses your storage class and the <b>openshift-image-registry</b> namespace. For example:</li></ol><pre>apiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n name: csi-pvc-imageregistry\n namespace: openshift-image-registry\n annotations:\n imageregistry.openshift.io: \"true\"\nspec:\n accessModes:\n - ReadWriteOnce\n volumeMode: Filesystem\n resources:\n requests:\n storage: 100Gi\n storageClassName: <your_custom_storage_class></pre><p>where:</p><h4>metadata.namespace</h4><p>Specifying the <b>openshift-image-registry</b> namespace allows the Cluster Image Registry Operator to consume the PVC.</p><h4>spec.resources.requests.storage</h4><p>This optional field adjusts the volume size.</p>"},"page_stats":{"kind":"list like","value":[{"page_number":1,"error":false,"token_count":248,"num_chunks":5},{"page_number":2,"error":false,"token_count":48,"num_chunks":1},{"page_number":3,"error":false,"token_count":87,"num_chunks":2},{"page_number":4,"error":false,"token_count":604,"num_chunks":11},{"page_number":5,"error":false,"token_count":2036,"num_chunks":4},{"page_number":6,"error":false,"token_count":1572,"num_chunks":3},{"page_number":7,"error":false,"token_count":110,"num_chunks":2},{"page_number":8,"error":false,"token_count":1459,"num_chunks":30},{"page_number":9,"error":false,"token_count":955,"num_chunks":17},{"page_number":10,"error":false,"token_count":1053,"num_chunks":11},{"page_number":11,"error":false,"token_count":1079,"num_chunks":7},{"page_number":12,"error":false,"token_count":1198,"num_chunks":21},{"page_number":13,"error":false,"token_count":543,"num_chunks":9},{"page_number":14,"error":false,"token_count":1278,"num_chunks":20},{"page_number":15,"error":false,"token_count":802,"num_chunks":10},{"page_number":16,"error":false,"token_count":980,"num_chunks":5},{"page_number":17,"error":false,"token_count":1001,"num_chunks":3},{"page_number":18,"error":false,"token_count":1205,"num_chunks":13},{"page_number":19,"error":false,"token_count":1106,"num_chunks":17},{"page_number":20,"error":false,"token_count":474,"num_chunks":7},{"page_number":21,"error":false,"token_count":1159,"num_chunks":20},{"page_number":22,"error":false,"token_count":1006,"num_chunks":12},{"page_number":23,"error":false,"token_count":1134,"num_chunks":14},{"page_number":24,"error":false,"token_count":934,"num_chunks":17},{"page_number":25,"error":false,"token_count":1162,"num_chunks":16},{"page_number":26,"error":false,"token_count":1203,"num_chunks":18},{"page_number":27,"error":false,"token_count":958,"num_chunks":11},{"page_number":28,"error":false,"token_count":1001,"num_chunks":18},{"page_number":29,"error":false,"token_count":1131,"num_chunks":18},{"page_number":30,"error":false,"token_count":977,"num_chunks":18}],"string":"[\n {\n \"page_number\": 1,\n \"error\": false,\n \"token_count\": 248,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 2,\n \"error\": false,\n \"token_count\": 48,\n \"num_chunks\": 1\n },\n {\n \"page_number\": 3,\n \"error\": false,\n \"token_count\": 87,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 4,\n \"error\": false,\n \"token_count\": 604,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 5,\n \"error\": false,\n \"token_count\": 2036,\n \"num_chunks\": 4\n },\n {\n \"page_number\": 6,\n \"error\": false,\n \"token_count\": 1572,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 7,\n \"error\": false,\n \"token_count\": 110,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 8,\n \"error\": false,\n \"token_count\": 1459,\n \"num_chunks\": 30\n },\n {\n \"page_number\": 9,\n \"error\": false,\n \"token_count\": 955,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 10,\n \"error\": false,\n \"token_count\": 1053,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 11,\n \"error\": false,\n \"token_count\": 1079,\n \"num_chunks\": 7\n },\n {\n \"page_number\": 12,\n \"error\": false,\n \"token_count\": 1198,\n \"num_chunks\": 21\n },\n {\n \"page_number\": 13,\n \"error\": false,\n \"token_count\": 543,\n \"num_chunks\": 9\n },\n {\n \"page_number\": 14,\n \"error\": false,\n \"token_count\": 1278,\n \"num_chunks\": 20\n },\n {\n \"page_number\": 15,\n \"error\": false,\n \"token_count\": 802,\n \"num_chunks\": 10\n },\n {\n \"page_number\": 16,\n \"error\": false,\n \"token_count\": 980,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 17,\n \"error\": false,\n \"token_count\": 1001,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 18,\n \"error\": false,\n \"token_count\": 1205,\n \"num_chunks\": 13\n },\n {\n \"page_number\": 19,\n \"error\": false,\n \"token_count\": 1106,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 20,\n \"error\": false,\n \"token_count\": 474,\n \"num_chunks\": 7\n },\n {\n \"page_number\": 21,\n \"error\": false,\n \"token_count\": 1159,\n \"num_chunks\": 20\n },\n {\n \"page_number\": 22,\n \"error\": false,\n \"token_count\": 1006,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 23,\n \"error\": false,\n \"token_count\": 1134,\n \"num_chunks\": 14\n },\n {\n \"page_number\": 24,\n \"error\": false,\n \"token_count\": 934,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 25,\n \"error\": false,\n \"token_count\": 1162,\n \"num_chunks\": 16\n },\n {\n \"page_number\": 26,\n \"error\": false,\n \"token_count\": 1203,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 27,\n \"error\": false,\n \"token_count\": 958,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 28,\n \"error\": false,\n \"token_count\": 1001,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 29,\n \"error\": false,\n \"token_count\": 1131,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 30,\n \"error\": false,\n \"token_count\": 977,\n \"num_chunks\": 18\n }\n]","isConversational":false}}},{"rowIdx":90,"cells":{"source_id":{"kind":"string","value":"OpenShift_Container_Platform-4.21-Release_notes-en-US"},"pdf_url":{"kind":"string","value":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/release_notes/OpenShift_Container_Platform-4.21-Release_notes-en-US.pdf"},"status":{"kind":"string","value":"success"},"processed_at":{"kind":"string","value":"2026-04-15T18:31:41.548281+00:00"},"elapsed_seconds":{"kind":"number","value":66.43,"string":"66.43"},"num_pages":{"kind":"number","value":64,"string":"64"},"num_pages_processed":{"kind":"number","value":30,"string":"30"},"max_pages_per_paper":{"kind":"number","value":30,"string":"30"},"pdf_exceeds_page_limit":{"kind":"bool","value":true,"string":"true"},"failed_pages":{"kind":"list like","value":[],"string":"[]","isConversational":false},"prompt_type":{"kind":"string","value":"ocr_layout"},"model_id":{"kind":"string","value":"datalab-to/chandra-ocr-2"},"script_version":{"kind":"timestamp","value":"2026-04-15T00:00:00","string":"2026-04-15T00:00:00"},"markdown":{"kind":"string","value":"# OpenShift Container Platform 4.21\n\n## Release notes\n\nHighlights of what is new and what has changed with this OpenShift Container Platform release# OpenShift Container Platform 4.21 Release notes\n\n---\n\nHighlights of what is new and what has changed with this OpenShift Container Platform release## Legal Notice\n\nCopyright © Red Hat.\n\nExcept as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.\n\nRed Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.\n\nRed Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.\n\nLinux ® is the registered trademark of Linus Torvalds in the United States and other countries.\n\nXFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.\n\nThe OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.\n\nAll other trademarks are the property of their respective owners.\n\n## Abstract\n\nThe release notes for OpenShift Container Platform summarize all new features and enhancements, notable technical changes, major corrections from the previous version, and any known bugs upon general availability.# Table of Contents\n\n<table>\n<tr>\n<td><b>CHAPTER 1. OPENSHIFT CONTAINER PLATFORM 4.21 RELEASE NOTES .....</b></td>\n<td><b>4</b></td>\n</tr>\n<tr>\n<td>1.1. ABOUT THIS RELEASE</td>\n<td>4</td>\n</tr>\n<tr>\n<td>1.2. OPENSHIFT CONTAINER PLATFORM LAYERED AND DEPENDENT COMPONENT SUPPORT AND COMPATIBILITY</td>\n<td>4</td>\n</tr>\n<tr>\n<td>1.3. NEW FEATURES AND ENHANCEMENTS</td>\n<td>4</td>\n</tr>\n<tr>\n<td> 1.3.1. API server</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.3.2. Authentication and authorization</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.3.3. Autoscaling</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.3.4. Edge computing</td>\n<td>6</td>\n</tr>\n<tr>\n<td> 1.3.5. etcd</td>\n<td>6</td>\n</tr>\n<tr>\n<td> 1.3.6. Extensions (OLM v1)</td>\n<td>6</td>\n</tr>\n<tr>\n<td> 1.3.7. IBM Power</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 1.3.8. IBM Z and IBM LinuxONE</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 1.3.9. Installation and update</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 1.3.10. Machine Config Operator</td>\n<td>10</td>\n</tr>\n<tr>\n<td> 1.3.11. Machine management</td>\n<td>11</td>\n</tr>\n<tr>\n<td> 1.3.12. Monitoring</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 1.3.13. Networking</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 1.3.14. Nodes</td>\n<td>13</td>\n</tr>\n<tr>\n<td> 1.3.15. OpenShift CLI (oc)</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.3.16. Operator development</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.3.17. Postinstallation configuration</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.3.18. Scalability and performance</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.3.19. Storage</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 1.3.20. Web console</td>\n<td>17</td>\n</tr>\n<tr>\n<td>1.4. NOTABLE TECHNICAL CHANGES</td>\n<td>17</td>\n</tr>\n<tr>\n<td>1.5. DEPRECATED AND REMOVED FEATURES</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 1.5.1. Images deprecated and removed features</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 1.5.2. Installation deprecated and removed features</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 1.5.3. Machine Management deprecated and removed features</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 1.5.4. Networking deprecated and removed features</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 1.5.5. Node deprecated and removed features</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 1.5.6. OpenShift CLI (oc) deprecated and removed features</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 1.5.7. Operator lifecycle and development deprecated and removed features</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 1.5.8. Storage deprecated and removed features</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 1.5.9. Web console deprecated and removed features</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 1.5.10. Workloads deprecated and removed features</td>\n<td>20</td>\n</tr>\n<tr>\n<td>1.6. DEPRECATED FEATURES</td>\n<td>20</td>\n</tr>\n<tr>\n<td>1.7. REMOVED FEATURES</td>\n<td>20</td>\n</tr>\n<tr>\n<td>1.8. FIXED ISSUES</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.8.1. Installer</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.8.2. Kube Controller Manager</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.8.3. Kube Scheduler</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.8.4. Networking</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.8.5. Clock state metrics degrade correctly after upstream clock loss</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 1.8.6. Node Tuning Operator</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 1.8.7. OpenShift API Server</td>\n<td>22</td>\n</tr>\n<tr>\n<td>1.9. TECHNOLOGY PREVIEW FEATURES STATUS</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 1.9.1. Authentication and authorization Technology Preview features</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 1.9.2. Edge computing Technology Preview features</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 1.9.3. Extensions Technology Preview features</td>\n<td>23</td>\n</tr>\n</table><table>\n<tr><td>1.9.4. Installation Technology Preview features</td><td>24</td></tr>\n<tr><td>1.9.5. Machine Config Operator Technology Preview features</td><td>25</td></tr>\n<tr><td>1.9.6. Machine management Technology Preview features</td><td>25</td></tr>\n<tr><td>1.9.7. Multi-Architecture Technology Preview features</td><td>26</td></tr>\n<tr><td>1.9.8. Networking Technology Preview features</td><td>27</td></tr>\n<tr><td>1.9.9. Node Technology Preview features</td><td>29</td></tr>\n<tr><td>1.9.10. OpenShift CLI (oc) Technology Preview features</td><td>29</td></tr>\n<tr><td>1.9.11. Operator lifecycle and development Technology Preview features</td><td>29</td></tr>\n<tr><td>1.9.12. Red Hat OpenStack Platform (RHOSP) Technology Preview features</td><td>30</td></tr>\n<tr><td>1.9.13. Scalability and performance Technology Preview features</td><td>30</td></tr>\n<tr><td>1.9.14. Storage Technology Preview features</td><td>30</td></tr>\n<tr><td>1.9.15. Web console Technology Preview features</td><td>32</td></tr>\n<tr><td>1.10. KNOWN ISSUES</td><td>32</td></tr>\n<tr><td>1.11. ASYNCHRONOUS ERRATA UPDATES</td><td>34</td></tr>\n<tr><td>1.11.1. RHBA-2026:6561 - OpenShift Container Platform 4.21.9 fixed issues advisory</td><td>34</td></tr>\n<tr><td>1.11.1.1. Fixed issues</td><td>34</td></tr>\n<tr><td>1.11.1.2. Updating</td><td>36</td></tr>\n<tr><td>1.11.2. RHBA-2026:5926 - OpenShift Container Platform 4.21.8 fixed issues advisory</td><td>37</td></tr>\n<tr><td>1.11.2.1. Enhancements</td><td>37</td></tr>\n<tr><td>1.11.2.2. Known issues</td><td>37</td></tr>\n<tr><td>1.11.2.3. Fixed issues</td><td>37</td></tr>\n<tr><td>1.11.2.4. Updating</td><td>38</td></tr>\n<tr><td>1.11.3. RHSA-2026:5174 - OpenShift Container Platform 4.21.7 fixed issues advisory</td><td>38</td></tr>\n<tr><td>1.11.3.1. Fixed issues</td><td>38</td></tr>\n<tr><td>1.11.3.2. Updating</td><td>39</td></tr>\n<tr><td>1.11.4. RHBA-2026:4420 - OpenShift Container Platform 4.21.6 fixed issues</td><td>39</td></tr>\n<tr><td>1.11.4.1. New features</td><td>40</td></tr>\n<tr><td>1.11.4.2. Known issues</td><td>40</td></tr>\n<tr><td>1.11.4.3. Fixed issues</td><td>40</td></tr>\n<tr><td>1.11.4.4. Updating</td><td>41</td></tr>\n<tr><td>1.11.5. RHBA-2026:3881 - OpenShift Container Platform 4.21.5 fixed issues</td><td>41</td></tr>\n<tr><td>1.11.5.1. Fixed issues</td><td>42</td></tr>\n<tr><td>1.11.5.2. Updating</td><td>42</td></tr>\n<tr><td>1.11.6. RHSA-2026:3402 - OpenShift Container Platform 4.21.4 image release, fixed issues, and security update</td><td>43</td></tr>\n<tr><td>1.11.6.1. Fixed issues</td><td>43</td></tr>\n<tr><td>1.11.6.2. Updating</td><td>44</td></tr>\n<tr><td>1.11.7. RHSA-2026:2984 - OpenShift Container Platform 4.21.3 fixed issues and security update</td><td>44</td></tr>\n<tr><td>1.11.7.1. Known issues</td><td>44</td></tr>\n<tr><td>1.11.7.2. Fixed issues</td><td>44</td></tr>\n<tr><td>1.11.7.3. Updating</td><td>45</td></tr>\n<tr><td>1.11.8. RHBA-2026:2637 - OpenShift Container Platform 4.21.2 fixed issues</td><td>45</td></tr>\n<tr><td>1.11.8.1. Enhancements</td><td>45</td></tr>\n<tr><td>1.11.8.2. Fixed issues</td><td>45</td></tr>\n<tr><td>1.11.8.3. Updating</td><td>46</td></tr>\n<tr><td>1.11.9. RHSA-2026:2129 - OpenShift Container Platform 4.21.1 fixed issues and security update</td><td>46</td></tr>\n<tr><td>1.11.9.1. Enhancements</td><td>47</td></tr>\n<tr><td>1.11.9.2. Known issues</td><td>47</td></tr>\n<tr><td>1.11.9.3. Fixed issues</td><td>48</td></tr>\n<tr><td>1.11.9.4. Updating</td><td>58</td></tr>\n<tr><td><b>CHAPTER 2. ADDITIONAL RELEASE NOTES</b> .....</td><td><b>59</b></td></tr>\n</table># CHAPTER 1. OPENSHIFT CONTAINER PLATFORM 4.21 RELEASE NOTES\n\nRed Hat OpenShift Container Platform provides developers and IT organizations with a hybrid cloud application platform for deploying both new and existing applications on secure, scalable resources with minimal configuration and management. OpenShift Container Platform supports a wide selection of programming languages and frameworks, such as Java, JavaScript, Python, Ruby, and PHP.\n\nBuilt on Red Hat Enterprise Linux (RHEL) and Kubernetes, OpenShift Container Platform provides a more secure and scalable multitenant operating system for today's enterprise-class applications, while delivering integrated application runtimes and libraries. OpenShift Container Platform enables organizations to meet security, privacy, compliance, and governance requirements.\n\n## 1.1. ABOUT THIS RELEASE\n\nOpenShift Container Platform ([RHBA-2026:1481](#)) is now available. This release uses [Kubernetes 1.34](#) with CRI-O runtime. New features, changes, and known issues that pertain to OpenShift Container Platform 4.21 are included in this topic.\n\nOpenShift Container Platform 4.21 clusters are available at <https://console.redhat.com/openshift>. From the Red Hat Hybrid Cloud Console, you can deploy OpenShift Container Platform clusters to either on-premises or cloud environments.\n\nYou must use RHCOS machines for the control plane and for the compute machines.\n\nStarting from OpenShift Container Platform 4.14, the Extended Update Support (EUS) phase for even-numbered releases increases the total available lifecycle to 24 months on all supported architectures, including **x86\\_64**, 64-bit ARM (**aarch64**), IBM Power® (**ppc64le**), and IBM Z® (**s390x**) architectures. Beyond this, Red Hat also offers a 12-month additional EUS add-on, denoted as *Additional EUS Term 2*, that extends the total available lifecycle from 24 months to 36 months. The Additional EUS Term 2 is available on all architecture variants of OpenShift Container Platform. For more information about support for all versions, see the [Red Hat OpenShift Container Platform Life Cycle Policy](#).\n\nOpenShift Container Platform is designed for FIPS. When running Red Hat Enterprise Linux (RHEL) or Red Hat Enterprise Linux CoreOS (RHCOS) booted in FIPS mode, OpenShift Container Platform core components use the RHEL cryptographic libraries that have been submitted to NIST for FIPS 140-2/140-3 Validation on only the **x86\\_64**, **ppc64le**, and **s390x** architectures.\n\nFor more information about the NIST validation program, see [Cryptographic Module Validation Program](#). For the latest NIST status for the individual versions of RHEL cryptographic libraries that have been submitted for validation, see [Compliance Activities and Government Standards](#).\n\n## 1.2. OPENSHIFT CONTAINER PLATFORM LAYERED AND DEPENDENT COMPONENT SUPPORT AND COMPATIBILITY\n\nThe scope of support for layered and dependent components of OpenShift Container Platform changes independently of the OpenShift Container Platform version. To determine the current support status and compatibility for an add-on, refer to its release notes. For more information, see the [Red Hat OpenShift Container Platform Life Cycle Policy](#).\n\n## 1.3. NEW FEATURES AND ENHANCEMENTS\n\nThis release adds improvements related to the following components and concepts:### 1.3.1. API server\n\n#### Dynamic updates to storage performance parameters by using VolumeAttributesClass\n\nBefore this release, updating storage performance parameters such as IOPS or throughput often required manual volume reprovisioning, complex snapshot migrations, or application downtime. With this release, OpenShift Container Platform supports the **VolumeAttributesClass** (VAC) API, enabling you to modify and dynamically scale storage parameters by updating the VAC assigned to a **PersistentVolumeClaim** (PVC). This support allows on-demand performance tuning without service interruption.\n\n### 1.3.2. Authentication and authorization\n\n#### Using the Azurekubelogin plugin for direct authentication with Microsoft Entra ID\n\nRed Hat tested authenticating to OpenShift Container Platform by using the Azure **kubelogin** plugin. This validation covers environments where Microsoft Entra ID is configured as the external OIDC provider for direct authentication. The following login modes for **kubelogin** were tested:\n\n- • Device code grant\n- • Service principal authentication\n- • Interactive web browser flow\n\nFor more information, see [Enabling direct authentication with an external OIDC identity provider](#) .\n\n#### ConsoleLink support for email links\n\nThe **ConsoleLink** Custom Resource Definition supports **mailto:** links. You can create email links in the OpenShift web console that open the default email client.\n\n#### Impersonating a user with multiple group memberships in the console\n\nCluster administrators can impersonate a user with multiple group memberships at the same time in the OpenShift web console. This supports reproducing effective permissions for RBAC troubleshooting.\n\n#### Customizing the Code Editor theme and font size in the console\n\nWith this update, users can customize the Code Editor theme and adjust the font size. By default, the Code Editor theme follows the active OpenShift Console theme, but users can now set it independently. These options improve productivity and reduce the need for frequent changes.\n\n#### Quick starts for Trusted Profile Analyzer and Trusted Artifact Signer\n\nWith this update, the OpenShift Console adds two quick starts for Trusted Profile Analyzer and Trusted Artifact Signer to the Overview page, making them easier to find and use. This change simplifies the user journey, improves the user experience, and strengthens product integration by highlighting Red Hat's security ecosystem within the platform.\n\n#### Grouping Helm charts under the Ecosystem header\n\nBefore this update, the OpenShift Console introduced the unified view in 4.19, and the **Helm** UI displayed in the **Admin** view but outside the **Ecosystem** menu. With this update, the OpenShift Console displays **Helm** under **Ecosystem**, centralizing software management navigation in one location within the unified view.\n\n### 1.3.3. Autoscaling\n\n#### Network policy support for Autoscaling OperatorsThe following Operators now have multiple network policies that control network traffic to and from the Operator and operand pods. These policies restrict traffic to only traffic that is explicitly allowed or required.\n\n- • Cluster Resource Override Operator\n- • Cluster Autoscaler\n- • Vertical Pod Autoscaler\n- • Horizontal Pod Autoscaler\n\n### Applying VPA recommendations without pod re-creation\n\nYou can now configure a Vertical Pod Autoscaler Operator (VPA) in the **InPlaceOrRecreate** mode. In this mode, the VPA attempts to apply the recommended updates without re-creating pods. If the VPA is unable to update the pods in place, the VPA falls back to re-creating the pods. For more information, see [About the Vertical Pod Autoscaler Operator modes](#).\n\n### Cluster Autoscaler Operator can now cordon nodes before removing the node\n\nBy default, when the Cluster Autoscaler Operator removes a node, it does not cordon the node when draining the pods from the node. You can configure the Operator to cordon the node before draining and moving the pods. For more information, see [About the cluster autoscaler](#).\n\n## 1.3.4. Edge computing\n\n### ClusterInstance CR replaces SiteConfig CR for GitOps ZTP deployments\n\nIn earlier releases, the **SiteConfig** custom resource (CR) was deprecated. This release removes support for the **SiteConfig** CR. You must now use the **ClusterInstance** CR to deploy managed clusters with GitOps ZTP. For more information, see [Deploying a managed cluster with ClusterInstance and GitOps ZTP](#).\n\n### Support for removing devices and device classes from a volume group\n\nYou can remove the device paths in the **deviceSelector.paths** field and the **deviceClass** object from the **LVMCluster** resource. For more information, see [About removing devices and device classes from a volume group](#)\n\n## 1.3.5. etcd\n\n### Manage etcd size by limiting the time-to-live (TTL) duration for Kubernetes events (Technology Preview)\n\nWith this release, you can manage etcd size by setting the **eventTTLMinutes** property. Having too many stale Kubernetes events in an etcd database can degrade performance. By setting the **eventTTLMinutes** property, you can specify how long an event can stay in the database before it is purged. For more information, see [Managing etcd size by limiting the duration of Kubernetes events](#).\n\n## 1.3.6. Extensions (OLM v1)\n\n### Cluster extension support for webhooks in bundles\n\nWith this update, OLM v1 supports Operators that use webhooks for validation, mutation, or conversion. For more information, see [Webhook support](#).\n\n### Support for **SingleNamespace** and **OwnNamespace** install modes by using the configuration API (Technology Preview)If an Operator supports the **SingleNamespace** or **OwnNamespace** install modes, you can configure the Operator to watch a specified namespace. For more information, see [Extension configuration](#).\n\n### OLM v1 software catalog in the web console (Technology Preview)\n\nWith this update, you can preview the OLM v1 software catalog in the web console. Select **Ecosystem → Software Catalog → Operators** to preview this feature. To see the OLM (Classic) software catalog, click the **Enable OLM v1 (Tech Preview)** toggle.\n\n## 1.3.7. IBM Power\n\n### The IBM Power® release on OpenShift Container Platform 4.21 adds improvements and new capabilities to OpenShift Container Platform components\n\nThis release introduces support for the following features on IBM Power:\n\n- • Enable Installer-Provisioned Infrastructure (IPI) support for PowerVC [Technology Preview]\n- • Enable Spyre Accelerator on IBM Power®\n\n### The IBM Power® release for OpenShift Container Platform 4.21 adds support for the following operator\n\n- • CIFS/SMB CSI Driver Operator\n- • Kernel Module Management Operator (KMMO)\n- • Red Hat build of Kueue\n\n### IMPORTANT\n\nWhen using **kdump** on IBM Power®, the following limitations apply:\n\n- • Firmware-assisted dump (**fadump**) is not supported.\n- • Persistent memory dump is not supported.\n\n## 1.3.8. IBM Z and IBM LinuxONE\n\n### The IBM Z® and IBM® LinuxONE release on OpenShift Container Platform 4.21 adds improvements and new capabilities to OpenShift Container Platform components\n\nThis release introduces support for the following features on IBM Z® and IBM® LinuxONE:\n\n- • Enable Spyre Accelerator on IBM Z®\n\n### The IBM Z® release for OpenShift Container Platform 4.21 adds support for the following operator\n\n- • Kernel Module Management Operator (KMMO)\n- • Red Hat build of Kueue\n\n## 1.3.9. Installation and update\n\n### Restricting service account impersonation to the compute nodes service account\n\nWhen you install a Google Cloud and configure it to use Google Cloud Workload Identity, you cannow restrict the Google Cloud **iam.serviceAccounts.actAs** permission that the Cloud Credential Operator utility grants the Machine API controller service account at the project level to only the compute nodes service account.\n\nFor more information, see [Restricting service account impersonation to the compute nodes service account](#).\n\n### Configuring image mode for OpenShift during installation is now supported\n\nYou can now apply a custom layered image to your nodes during OpenShift Container Platform installation. For more information, see [Applying a custom layered image during OpenShift Container Platform installation](#).\n\n### Installing a cluster on Google Cloud with a user-provisioned DNS is generally available\n\nYou can enable a user-provisioned domain name server (DNS) instead of the default cluster-provisioned DNS solution. For example, your organization's security policies might not allow the use of public DNS services such as Google Cloud DNS. You can manage your DNS only for the IP addresses of the API and Ingress servers. If you use this feature, you must provide your own DNS solution that includes records for **api.<cluster\\_name>.<base\\_domain>.** and **\\*.apps.<cluster\\_name>.<base\\_domain>..**\n\nInstalling a cluster on Google Cloud with a user-provisioned DNS was introduced in OpenShift Container Platform 4.19 with Technology Preview status. In OpenShift Container Platform 4.21, it is now generally available.\n\nFor more information, see [Enabling a user-managed DNS](#) and [Provisioning your own DNS records](#).\n\n### Installing a cluster on Microsoft Azure uses Marketplace images by default\n\nAs of this update, the OpenShift Container Platform installation program uses Marketplace images by default when installing a cluster on Azure. This speeds up the installation by removing the need to upload a virtual hard disk to Azure and create an image during installation. This feature is not supported on Azure Stack Hub, or for Azure installations that use Confidential VMs.\n\n### The **ccocntl** utility supports preserving custom Microsoft Azure role assignments\n\nThe Cloud Credential Operator utility (**ccocntl**) can now preserve custom role assignments by using the **--preserve-existing-roles** flag. Previously, the tool removed role assignments that were not defined in the `CredentialsRequest`, including those manually added by administrators.\n\n### Managing your own firewall rules when installing a cluster on Google Cloud into an existing VPC\n\nAs of this update, you can manage your own firewall rules when installing a cluster on Google Cloud into an existing VPC by enabling the **firewallRulesManagement** parameter in the **install-config.yaml** file. You can limit the permissions that you grant to the installation program by managing your own firewall rules.\n\nFor more information, see [Managing your own firewall rules](#).\n\n### The **ccocntl** utility supports Amazon Web Services permissions boundaries\n\nThe Cloud Credential Operator utility (**ccocntl**) now supports attaching an AWS permissions boundary to the IAM roles that it creates. You can use this feature to meet organizational security requirements that restrict the maximum permissions of created roles.\n\n### Throughput customization for Amazon Web Services gp3 drives\n\nWith this update, you can now customize the maximum throughput for gp3 **rootVolume** drives when installing a cluster on Amazon Web Services. This customization is set by modifying the **compute.platform.aws.rootVolume.throughput** or **controlPlane.platform.aws.rootVolume.throughput** parameters in the **install-config.yaml** file.\n\nFor more information, see [Optional AWS configuration parameters](#).## Support for VMware vSphere Foundation 9 and VMware Cloud Foundation 9\n\nYou can now install OpenShift Container Platform on VMware vSphere Foundation (VVF) 9 and VMware Cloud Foundation (VCF) 9.\n\n### NOTE\n\nThe following additional VCF and VVF components are outside the scope of Red Hat support:\n\n- • Management: VCF Operations, VCF Automation, VCF Fleet Management, and VCF Identity Broker.\n- • Networking: VMware NSX Container Plugin (NCP).\n- • Migration: VMware HCX.\n\n## Support for installing OpenShift Container Platform on Oracle Database Appliance (ODA)\n\nWith this update, you can install a cluster on Oracle Database Appliance using the Assisted Installer. For more information, see [Installing a cluster on Oracle Database Appliance by using the Assisted Installer](#).\n\n## Installing a dual-stack cluster on Red Hat OpenStack Platform (RHOSP) when the machine network is IPv6-only\n\nFrom RHOSP 17.1, you can deploy a dual-stack OpenShift Container Platform cluster when your RHOSP machine network is IPv6-only; the cluster still uses IPv4 for internal cluster and service networks.\n\nFor more information, see [Configuring a cluster with dual-stack networking](#).\n\n## Installing a cluster on AWS with a user-provisioned DNS (Technology Preview)\n\nYou can enable a user-provisioned domain name server (DNS) instead of the default cluster-provisioned DNS solution. For example, your organization's security policies might not allow the use of public DNS services such as Amazon Web Services (AWS) DNS. As a result, you can manage the API and Ingress DNS records in your own system rather than adding the records to the DNS of the cloud. If you use this feature, you must provide your own DNS solution that includes records for **api.<cluster\\_name>.<base\\_domain>**. and **\\*.apps.<cluster\\_name>.<base\\_domain>**. Enabling a user-provisioned DNS is available as a Technology Preview feature.\n\nFor more information, see [Enabling a user-managed DNS](#) and [Provisioning your own DNS records](#).\n\n## Installing a cluster on Microsoft Azure using NAT Gateways\n\nWith this update, you can install a cluster on Azure using NAT Gateways as your outbound routing strategy. NAT Gateways can minimize the risk of SNAT port exhaustion that can occur with other outbound routing strategies. You can configure NAT Gateways using the **platform.azure.outboundType** parameter in the **install-config.yaml** file.\n\nFor more information, see [Additional Azure configuration parameters](#).\n\n## Installing a cluster using Google Cloud private and restricted API endpoints\n\nWith this release, you can use Google Cloud Private Service Connect (PSC) endpoints when installing your OpenShift Container Platform cluster so that your installation meets your organization's strict regulatory policies.\n\nFor more information, see [Optional configuration parameters](#).### Dell iDRAC10 supported for bare metal installation using Redfish virtual media\n\nDell iDRAC10 versions 1.20.25.00, 1.20.60.50, and 1.20.70.50 have been tested and verified to work for installer-provisioned OpenShift Container Platform clusters deployed by using Redfish virtual media. iDRAC10 has not been tested with installations that use a provisioning network. For more information, see [Firmware requirements for installing with virtual media](#).\n\n### Providing a local or self-signed CA certificate for Baseboard Management Controllers (BMCs) when installing a cluster on bare metal\n\nWith this update, you can provide your own local or self-signed CA certificate to secure communication with BMCs when installing a cluster on bare metal. You can configure this certificate using the **platform.baremetal.bmcCACert** parameter in the `install-config.yaml` file. If you do not use a trusted CA certificate, you can secure BMC communication by providing your own CA certificate. You can also configure a local or self-signed CA certificate after installation, whether the cluster was installed with a different BMC CA certificate or with no BMC CA certificate.\n\nFor more information, see [Additional installation configuration parameters](#) and [Configuring a local or self-signed Baseboard Management Controller CA certificate](#).\n\n### Running firmware upgrades for hosts in deployed bare metal clusters (Generally Available)\n\nFor hosts in deployed bare metal clusters, you can update firmware attributes and the firmware image. As a result, you can run firmware upgrades and update BIOS settings for hosts that are already provisioned without fully deprovisioning them. Performing a live update to the **HostFirmwareComponents**, **HostFirmwareSettings**, or **HostUpdatePolicy** resource can be a destructive and destabilizing action. Perform these updates only after careful consideration. This feature was introduced in OpenShift Container Platform 4.18 with Technology Preview status. This feature is now supported as generally available in OpenShift Container Platform 4.21.\n\nFor more information, see [Performing a live update to the HostFirmwareSettings resource](#), [Performing a live update to the HostFirmwareComponents resource](#), and [Setting the HostUpdatePolicy resource](#).\n\n### Testing for Amazon Web Services m7 instance type\n\nAs of OpenShift Container Platform 4.21, m7 instance types have been tested for installations on Amazon Web Services. For more information about tested instance types, see [Tested instance types for AWS](#).\n\n### Installing a cluster on Microsoft Azure with a user-provisioned DNS (Technology Preview)\n\nYou can enable a user-provisioned domain name server (DNS) instead of the default cluster-provisioned DNS solution. For example, your organization's security policies might not allow the use of public DNS services such as Microsoft Azure DNS. You can manage your DNS only for the IP addresses of the API and Ingress servers. If you use this feature, you must provide your own DNS solution that includes records for **api.<cluster\\_name>.<base\\_domain>** and **\\*.apps.<cluster\\_name>.<base\\_domain>**. Enabling a user-provisioned DNS is available as a Technology Preview feature.\n\nFor more information, see [Enabling a user-managed DNS](#) and [Provisioning your own DNS records](#).\n\n## 1.3.10. Machine Config Operator\n\n### Boot image management for Azure and vSphere clusters promoted to GA\n\nUpdating boot images has been promoted to GA for Microsoft Azure and VMware vSphere clusters. For more information, see [Boot image management](#).\n\n### Configuring image mode for OpenShift during installation is now supportedYou can now apply a custom layered image to your nodes during OpenShift Container Platform installation. For more information, see [Applying a custom layered image during OpenShift Container Platform installation](#).\n\n### Image mode for OpenShift status reporting improvements\n\nThe output of the **oc describe machineconfignodes <mcp\\_name>** now contains an **ImageBuildDegraded** error that indicates if an image mode for OpenShift failed. For more information, see [About node status during updates](#).\n\n### Image mode for OpenShift status reporting improvements (Technology preview)\n\nThe **oc describe machineconfigpool <mcp\\_name>** output, as a Technology Preview feature, now includes the following fields that report the status of machine config updates when image mode for OpenShift is enabled:\n\n- • **Spec.ConfigImage.DesiredImage**. This is the desired image for that node.\n- • **Status.ConfigImage.CurrentImage**. This is the current image on that node.\n- • **Status.Conditions.ImagePulledFromRegistry**. This reports whether an image is able to pull correctly in an image mode update.\n\nFor more information, see [About node status during updates](#).\n\n### Boot image management for control plane nodes is now supported (Technology Preview)\n\nUpdating boot images is now supported as a Technology Preview feature for VMware vSphere clusters. This feature allows you to configure your cluster to update the node boot image whenever you update your cluster. Previously, updating boot images was supported for worker nodes. For more information, see [Boot image management](#).\n\n### Overriding storage or partition setup (Technology preview)\n\nYou can now use a **MachineConfig** object to change the installed disk partition schema, file systems, and RAID configurations for new nodes. Previously, for security reasons, you were blocked from changing these configurations from what was established during the cluster installation. For more information, see \"Overriding storage and partition setup\".\n\n## 1.3.11. Machine management\n\n### Creating Google Cloud Spot VMs by using compute machine sets\n\nWith this release, OpenShift Container Platform supports deploying Machine API compute machines on Spot VMs in Google Cloud clusters. Google Cloud recommends using Spot VMs over their predecessor, preemptible VMs, because they include new features that preemptible VMs do not support.\n\nFor more information, see [Machine sets that deploy machines as Spot VMs](#).\n\n### Additional control plane machine set failure domain options for Azure\n\nThis release includes additional configuration options for control plane machine set failure domains on Microsoft Azure.\n\nFor more information, see [Sample Azure failure domain configuration](#).\n\n### Configuration of throughput for Amazon Web Services gp3 volumes on EBS devices\n\nThis release includes support for configuring the maximum throughput for gp3 drives on EBS devices for clusters installed on Amazon Web Services (AWS).\n\nFor more information, see [Configuring storage throughput for gp3 drives \\(Machine API\\)](#) and [Configuring storage throughput for gp3 drives \\(Cluster API\\)](#).In OpenShift Container Platform version 4.21.1 and later, this feature also works with [control plane machine sets](#).\n\n### Bare-metal nodes on VMware vSphere clusters (Technology Preview)\n\nYou can now add bare-metal compute machines to an existing OpenShift Container Platform cluster on vSphere. This capability enables you to migrate workloads to physical hardware without reinstalling the cluster. For instructions on adding these machines, see [Adding bare-metal compute machines to a vSphere cluster](#).\n\n### 1.3.12. Monitoring\n\n#### NOTE\n\nThe monitoring stack documentation is now available as a separate documentation set. The 4.21 monitoring release notes are available at [Release notes for OpenShift monitoring](#).\n\n### 1.3.13. Networking\n\n#### MetalLB Operator status reporting\n\nYou can now use enhanced MetalLB Operator reporting features to view real-time operational data for IP address allocation and Border Gateway Protocol (BGP) connectivity. Previously, viewing this information required manual log inspection across multiple controllers. With this release, you can monitor your network health and resolve connectivity issues directly through the following custom resources:\n\n- ● **IPAddressPool**: Monitor cluster-wide IP address allocation through the **status** field to track usage and prevent address exhaustion.\n- ● **ServiceBGPSStatus**: Verify which service IP addresses are announced to specific BGP peers to ensure correct route advertisements.\n- ● **BGPSessionStatus**: Check the real-time state of BGP and Bidirectional Forwarding Detection sessions to quickly identify connectivity drops.\n\nFor more information, see [Monitoring MetalLB configuration status](#).\n\n#### Applying unassisted holdover for boundary clocks and time synchronous clocks\n\nOpenShift Container Platform 4.20 introduced unassisted holdover for boundary clocks and time synchronous clocks as a Technology Preview feature. This feature is now Generally Available (GA). For more information, see [Applying unassisted holdover for boundary clocks and time slave clocks](#).\n\n#### SR-IOV Operator supports ARM architecture\n\nThe Single Root I/O Virtualization (SR-IOV) Operator can now communicate with ARM hardware. You can now complete tasks such as configure network cards that are already plugged into an ARM server and use these cards in your applications. For instructions on how to search for ARM hardware that the SR-IOV Operator supports, see [About Single Root I/O Virtualization \\(SR-IOV\\) hardware networks](#).\n\n#### Support for Red Hat OpenShift Service Mesh version 3.2\n\nOpenShift Container Platform 4.21 updates Service Mesh to version 3.2. This version update incorporates essential CVE fixes and ensures that your OpenShift Container Platform instances receive the latest fixes, features, and enhancements. See the [Service Mesh 3.2 release notes](#) for more information.### PTP Operator introduces GNSS-to-NTP failover for high-precision timing\n\nWith this release, the PTP Operator introduces an active GNSS-to-NTP failover configuration to ensure time synchronization continuity in environments requiring extremely high time accuracy. When the primary Global Navigation Satellite System (GNSS) signal is lost or compromised, for example because of satellite jamming, the system automatically fails over to Network Time Protocol (NTP) to maintain time accuracy. When the GNSS signal is restored, the system automatically recovers back to using GNSS as the primary time source.\n\nThis feature is particularly important in telco environments that require high precision time synchronization with built-in redundancy. To enable GNSS to NTP failover, you configure the **PtpConfig** resource with the **ntpfailover** plugin enabled and configure both **chronyd** and **ts2phc** settings.\n\nFor more information, see [Configuring GNSS failover to NTP for time synchronization continuity](#) .\n\n### Network policies for additional namespaces\n\nWith this release, OpenShift Container Platform continues to deploy Kubernetes network policies to additional system namespaces to control ingress and egress traffic. It is anticipated that future releases might include network policies for additional system namespaces and Red Hat Operators.\n\n### Ingress network flow analysis with the commatrix plugin\n\nWith this release, you can use the **commatrix** plugin to generate ingress network flow data from your cluster. You can also use the plugin to identify any differences between open ports on the host and expected ingress flows for your environment.\n\nFor more information, see [Ingress network flow analysis with the commatrix plugin](#)\n\n### Configure the dnsRecordsType parameter (Technology preview)\n\nDuring cluster installation, you can specify the **dnsRecordsType** parameter in the **install-config.yaml** file to set if the internal DNS service or an external source provides the necessary records for **api**, **api-int**, and **ingress** DNS records. For more information about DNS requirements, see [User-provisioned DNS requirements](#).\n\n## 1.3.14. Nodes\n\n### Allocating specific GPUs to pods (DRA) is now generally available\n\nAttribute-Based GPU Allocation, which allows pods to request GPUs based on specific device attributes by using a Dynamic Resource Allocation (DRA) driver, is now generally available. For more information, see [Allocating GPUs to Pods](#) .\n\n### The default openshift cluster image policy is now generally available\n\nThe default **openshift** cluster image policy is now generally available and active by default. For more information, see [Manage secure signatures with sigstore](#) .\n\nIf your OpenShift Container Platform 4.20 or earlier cluster has a cluster image policy named **openshift**, the upgrade to OpenShift Container Platform marks the cluster as not updatable (**Upgradeable=False**) because of this default **openshift** cluster image policy. You must remove your **openshift** cluster image policy to clear the **Upgradeable=False** condition and proceed with the update. You can optionally create your own cluster image policy with a different name before removing your **openshift** cluster image policy.\n\n### Support for sigstore BYOPKI is now generally available\n\nSupport for using a certificate from your own public key infrastructure as a Sigstore root of trust is now generally available. For more information, see [Manage secure signatures with sigstore](#) .## Automatically calculate and apply CPU and memory resources for system components\n\nOpenShift Container Platform now automatically calculates and reserves a portion of the CPU and memory resources for use by the underlying node and system components. Previously, you needed to enable the feature by creating a **KubeletConfig** custom resource (CR) with the **autoSizingReserved: true** parameter. For clusters updated to OpenShift Container Platform 4.21, you can enable the feature by deleting the **50-worker-auto-sizing-disabled** machine config. After you delete the machine config, the nodes reboot with the new resource settings. If you manually configured system reserved CPU or memory resources, these settings remain upon update and do not change. For more information on this new feature, see [Automatically allocating resources for nodes](#).\n\n## Linux PSI monitoring can now be enabled\n\nYou can now enable Linux Pressure Stall Information (PSI) monitoring, which makes PSI metrics for CPU, memory, and I/O available for your cluster, by using a **MachineConfig** object. For more information, see [Enabling Pressure Stall Information \\(PSI\\) monitoring](#).\n\n### 1.3.15. OpenShift CLI (oc)\n\n#### Signature mirroring enabled by default for oc-mirror v2\n\nWith this update, the oc-mirror v2 plugin mirrors image signatures by default. This enhancement ensures that image integrity is automatically preserved during the mirroring process without requiring additional configuration. If your environment does not require signature validation, you can manually disable this feature by using the **--remove-signatures** command-line flag. For more information, see [Disabling signature mirroring for oc-mirror plugin v2](#).\n\n### 1.3.16. Operator development\n\n#### Supported Operator base images\n\nWith this release, the following base images for Operator projects are updated for compatibility with OpenShift Container Platform 4.21. The runtime functionality and configuration APIs for these base images are supported for bug fixes and for addressing CVEs.\n\n- • The base image for Ansible-based Operator projects\n- • The base image for Helm-based Operator projects\n\nFor more information, see [Updating the base image for existing Ansible- or Helm-based Operator projects for OpenShift Container Platform 4.19 and later](#) (Red Hat Knowledgebase).\n\n### 1.3.17. Postinstallation configuration\n\n#### Enabling hardware metrics monitoring on bare-metal clusters (Technology Preview)\n\nWith this update, you can enable your cluster to collect hardware metrics from the Redfish-compatible baseboard management controllers of your bare-metal nodes. Metrics include temperature, power consumption, fan status, and drive health. You enable this Technology Preview feature by enabling the Ironic Prometheus Exporter in your cluster as a postinstallation task. For more information, see [Hardware metrics in the Monitoring stack](#).\n\n### 1.3.18. Scalability and performance\n\n#### Pod-level IRQ affinity introduces housekeeping modeFor latency-sensitive workloads, you can now configure the **irq-load-balancing.crio.io** pod annotation to use **housekeeping** mode. This mode enables a subset of pinned CPUs to handle system interrupts while isolating the remaining pinned CPUs for latency-sensitive workloads. This reduces the overall CPU footprint by eliminating the need for dedicated housekeeping CPUs for IRQ handling. When you configure **housekeeping** mode, the first pinned CPU and its thread siblings handle interrupts for the system.\n\nFor more information, see [Configuring interrupt processing for individual pods](#).\n\n### 1.3.19. Storage\n\n#### Volume Attributes Classes is generally available\n\nVolume Attributes Classes provide a way for administrators to describe \"classes\" of storage they offer. Different classes might correspond to different quality-of-service levels. Volume Attributes Classes was introduced in OpenShift Container Platform 4.19, and is now generally available in 4.21. Volume Attributes Classes is available only with AWS Elastic Block Storage (EBS) and Google Cloud Platform (GCP) persistent disk (PD) Container Storage Interface (CSI).\n\nYou can apply a Volume Attributes Classes to a persistent volume claim (PVC). If a new Volume Attributes Class becomes available in the cluster, you can update the PVC with the new Volume Attributes Classes if needed.\n\nVolume Attributes Classes have parameters that describe volumes belonging to them. If a parameter is omitted, the default is used at volume provisioning. If a user applies the PVC with a different Volume Attributes Class with omitted parameters, the default value of the parameters might be used depending on the CSI driver implementation. For more information, see the related CSI driver documentation.\n\nFor more information, see [Volume Attributes Classes](#).\n\n#### Azure File CSI supporting snapshots feature is generally available\n\nA snapshot represents the state of the storage volume in a cluster at a particular point in time. Volume snapshots can be used to provision a new volume.\n\nOpenShift Container Platform 4.17 introduced volume snapshot support for the Microsoft Azure File Container Storage Interface (CSI) Driver Operator as a Technology Preview feature. In 4.21, this feature is generally available. Also, Azure File snapshots now supports Network File System (NFS) in addition to Server Message Block (SMB).\n\nFor more information, see [CSI drivers supported by OpenShift Container Platform](#) and [CSI volume snapshots](#).\n\n#### Azure File CSI supporting volume cloning feature is generally available\n\nVolume cloning duplicates an existing persistent volume (PV) to help protect against data loss in OpenShift Container Platform. You can also use a volume clone just as you would use any standard volume.\n\nOpenShift Container Platform 4.16 introduced volume cloning for the Microsoft Azure File Container Storage Interface (CSI) Driver Operator as a Technology Preview feature. In 4.21, this feature is generally available. Also, Azure File cloning now supports Network File System (NFS) in addition to Server Message Block (SMB).\n\nFor more information, see [Azure File CSI Driver Operator](#) and [CSI volume cloning](#).\n\n#### oVirt CSI Driver Operator is removed from OpenShift Container Platform 4.21Red Hat Virtualization (RHV) as a host platform for OpenShift Container Platform was deprecated in version 4.14 and is no longer supported. In OpenShift Container Platform 4.21, the oVirt CSI Driver Operator is removed.\n\n### CIFS/SMB CSI Driver Operator supports IBM Power\n\nIn OpenShift Container Platform 4.21, the CIFS/SMB CSI Driver Operator supports IBM Power (ppc64le).\n\nFor more information, see [CIFS/SMB CSI Driver Operator](#).\n\n### Introduction of new field to track the status of volume resize attempts\n\nOpenShift Container Platform 4.19 introduced resizing recovery that stops the expansion controller from indefinitely attempting to expand a volume to an unsupported size request. This feature allows you to recover and provide another smaller resize value for the persistent volume claim (PVC). The new value must be larger than the original volume size.\n\nOpenShift Container Platform 4.21 introduces the **pvc.Status.AllocatedResourceStatus** field, which shows the status of volume resize attempts. If a user changes the size of their PVCs, this new field allows resource quota to be tracked accurately.\n\nFor more information about resizing volumes, see [Expanding persistent volumes](#).\n\nFor more information about recovering when resizing volumes, see [Recovering from failure when expanding volumes](#).\n\n### Mutable CSI node allocatable property (Technical Preview)\n\nThis feature allows for dynamically updating the maximum number of storage volumes a node can handle. Without this feature, volume limits are essentially immutable when a node first joins the cluster. If the environment changes—for example, if you attach a new network interface (ENI) that shares a hardware \"slot\" with your storage—OpenShift Container Platform does not recognize it has fewer slots available for disks, leading to pods becoming stuck.\n\nThis feature is only supported on AWS Elastic Block Storage (EBS).\n\nMutable CSI node allocatable property is supported in OpenShift Container Platform 4.21 as a Technical Preview feature. To enable this feature, you need to enable Feature Gates.\n\nFor more information about enabling Technical Preview features, see [Feature Gates](#).\n\n### Reducing permissions while using the GCP PD CSI Driver Operator is generally available\n\nThe default installation allows the Google Cloud Platform (GCP) persistent disk (PD) Container Storage Interface (CSI) Driver to impersonate any service account in the Google Cloud project. You can reduce the scope of permissions granted to the GCP PD CSI Driver service account in your Google Cloud project to only the required node service accounts.\n\nFor more information about this feature, see [Reducing permissions while using the GCP PD CSI Driver Operator](#).\n\n### Volume group snapshots API updated (Technical Preview)\n\nThe API for the Container Storage Interface (CSI) volume group snapshot feature is updated from **v1beta1** to **v1beta2**.\n\nThis feature is supported at the Technical Preview level.\n\nFor more information, see [CSI volume group snapshots](#).\n\n### Updated release of the Secrets Store CSI Driver OperatorThe Secrets Store CSI Driver Operator version v4.21 is now based on the upstream version v1.5.4 release of secrets-store-csi-driver.\n\n### 1.3.20. Web console\n\n#### OLM v1 software catalog in the web console (Technology Preview)\n\nWith this update, you can preview the Operator Lifecycle Manager (OLM) v1 software catalog in the web console. Select **Ecosystem** → **Software Catalog** → **Operators** to preview this feature. To see the OLM (Classic) software catalog, click the **Enable OLM v1 (Tech Preview)** toggle.\n\n## 1.4. NOTABLE TECHNICAL CHANGES\n\nThis section includes several technical changes for OpenShift Container Platform 4.21.\n\n#### VMware vSphere 7 and VMware Cloud Foundation 4 end of general support\n\nBroadcom has ended general support for VMware vSphere 7 and VMware Cloud Foundation (VCF) 4. If your existing OpenShift Container Platform cluster is running on either of these platforms, you must plan to migrate or upgrade your VMware infrastructure to a supported version. OpenShift Container Platform supports installation on vSphere 8 Update 1 or later, or VCF 5 or later.\n\n#### Bare Metal Operator has read-only root filesystem by default\n\nAs of this update, the Bare Metal Operator has the **readOnlyRootFilesystem** security context setting enabled to meet common hardening recommendations.\n\n#### MachineSets advertise node architecture for autoscaling\n\nWith this update, MachineSets advertise the architecture of their nodes, which allows the autoscaler to intelligently scale MachineSets in multi-architecture environments.\n\n#### Dynamic Resource Allocation plugin is disabled in the NUMA-aware scheduler\n\nWith this update, the Dynamic Resource Allocation (DRA) is disabled so that the secondary scheduler, managed by **numaresources** operator, does not need to handle DRA resources. The Kubernetes project has recently enabled DRA by default, setting specific expectations on the scheduler-plugins project to support watching DRA resources. As a result, the OpenShift topology-aware scheduler (TAS) disables DRA plugin in its profile, and therefore ignores DRA-related custom resources (CRs) when making scheduling decisions.\n\n## 1.5. DEPRECATED AND REMOVED FEATURES\n\n### 1.5.1. Images deprecated and removed features\n\nTable 1.1. Images deprecated and removed tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Cluster Samples Operator</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n### 1.5.2. Installation deprecated and removed features\n\nTable 1.2. Installation deprecated and removed tracker<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>--cloud</b> parameter for <b>oc adm release extract</b></td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>CoreDNS wildcard queries for the <b>cluster.local</b> domain</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td><b>compute.platform.openstack.rootVolume.type</b> for RHOSP</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td><b>controlPlane.platform.openstack.rootVolume.type</b> for RHOSP</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td><b>ingressVIP</b> and <b>apiVIP</b> settings in the <b>install-config.yaml</b> file for installer-provisioned infrastructure clusters</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Package-based RHEL compute machines</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td><b>platform.aws.preserveBootstrapIgnition</b> parameter for Amazon Web Services (AWS)</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Installing a cluster on AWS with compute nodes in AWS Outposts</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Deploying managed clusters using <b>SiteConfig</b> and the GitOps ZTP workflow</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td>Installing a cluster using Fujitsu iRMC drivers on bare-metal machines</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n### 1.5.3. Machine Management deprecated and removed features\n\nTable 1.3. Machine management deprecated and removed tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Confidential Computing with AMD Secure Encrypted Virtualization for Google Cloud</td>\n<td>General Availability</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Managing bare-metal machines using Fujitsu iRMC drivers</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n### 1.5.4. Networking deprecated and removed features\n\nTable 1.4. Networking deprecated and removed tracker<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>iptables</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n### 1.5.5. Node deprecated and removed features\n\nTable 1.5. Node deprecated and removed tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>ImageContentSourcePolicy</b> (ICSP) objects</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Kubernetes topology label <b>failure-domain.beta.kubernetes.io/zone</b></td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Kubernetes topology label <b>failure-domain.beta.kubernetes.io/region</b></td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>cgroup v1</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n</tbody>\n</table>\n\n### 1.5.6. OpenShift CLI (oc) deprecated and removed features\n\nTable 1.6. OpenShift CLI (oc) deprecated and removed tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>oc-mirror plugin v1</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Docker v2 registries</td>\n<td>General Availability</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n### 1.5.7. Operator lifecycle and development deprecated and removed features\n\nTable 1.7. Operator lifecycle and development deprecated and removed tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Operator SDK</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td>Scaffolding tools for Ansible-based Operator projects</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td>Scaffolding tools for Helm-based Operator projects</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td>Scaffolding tools for Go-based Operator projects</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td>Scaffolding tools for Hybrid Helm-based Operator projects</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Scaffolding tools for Java-based Operator projects</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td>SQLite database format for Operator catalogs</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n### 1.5.8. Storage deprecated and removed features\n\nTable 1.8. Storage deprecated and removed tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Shared Resources CSI Driver Operator</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n</tbody>\n</table>\n\n### 1.5.9. Web console deprecated and removed features\n\nTable 1.9. Web console deprecated and removed tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>useModal</b> hook for dynamic plugin SDK</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Patternfly 4</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n</tbody>\n</table>\n\n### 1.5.10. Workloads deprecated and removed features\n\nTable 1.10. Workloads deprecated and removed tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>DeploymentConfig</b> objects</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n## 1.6. DEPRECATED FEATURES\n\n### Deprecation of Fujitsu Integrated Remote Management Controller (iRMC) driver for bare-metal machines\n\nAs of OpenShift Container Platform 4.21, support for the Fujitsu iRMC baseboard management controller (BMC) driver has been deprecated and will be removed in a future release. If a **BareMetalHost** resource contains a BMC address with **irmc://** as its URI scheme, the resource must be updated to use another BMC scheme, such as **redfish://** or **ipmi://**. Once support for this driver is removed, hosts that use **irmc://** URI schemes will become unmanageable.\n\nFor information about updating the **BareMetalHost** resource, see [Editing a BareMetalHost resource](#).\n\n## 1.7. REMOVED FEATURESThis section includes removed features for OpenShift Container Platform 4.21.\n\n### Swap memory support has been removed\n\nThe ability to configure swap memory is no longer available in OpenShift Container Platform because using swap memory can prevent a node from properly safeguarding itself from failures.\n\n## 1.8. FIXED ISSUES\n\nThe following issues are fixed for this release:\n\n### 1.8.1. Installer\n\n- • Before this update, the vSphere platform configuration lacked a validation check to prevent the simultaneous definition of both a custom virtual machine template and a **clusterOSImage** parameter. As a consequence, users could provide both parameters in the installation configuration, leading to ambiguity and potential deployment failures. With this release, the vSphere validation logic has been updated to ensure that template and **clusterOSImage** parameters are treated as mutually exclusive, returning a specific error message if both fields are populated. ([OCPBUGS-63584](#))\n- • Before this update, a race condition occurred when multiple reconciliation loops or concurrent processes attempted to add a virtual machine (VM) to a vSphere Host Group simultaneously due to the provider lacking a check to see if the VM was already a member. Consequently, the vSphere API could return errors during the cluster reconfiguration task, leading to reconciliation failures and preventing the VM from being correctly associated with its designated zone or host group. With this release, the zonal logic has been updated to verify the VM's membership within the target host group before initiating a reconfiguration task, ensuring the operation is only performed if the VM is not already present. ([OCPBUGS-60765](#))\n\n### 1.8.2. Kube Controller Manager\n\n- • Before this update, **relatedObjects** in the **ClusterOperator** Custom Resource object omitted the **ClusterRoleBinding** object, resulting in incomplete debugging information. With this release, the related objects for **ClusterOperator** are expanded to include **ClusterRoleBinding**. As a result, the **kube-controller-manager ClusterRoleBinding** is included in the **ClusterOperator** output. ([OCPBUGS-65502](#))\n\n### 1.8.3. Kube Scheduler\n\n- • Before this update, the **ClusterOperator** object failed to reference **ClusterRoleBinding** in the **relatedObjects** array, and caused the **Kube-scheduler ClusterRoleBinding** to be omitted in the **ClusterOperator** output. As a consequence, debugging difficulties occurred. With this release, the **ClusterRoleBinding** for the **kube-scheduler** Operator is added to the **ClusterOperator relatedObjects**. ([OCPBUGS-65503](#))\n\n### 1.8.4. Networking\n\n- • Before this update, an incorrect private key containing certificate data caused HAProxy reload failure in OpenShift Container Platform 4.14. As a consequence, incorrect certificate configuration caused HAProxy router pods to fail reloads, which led to a partial outage. With this release, **haproxy** now validates certificates. As a result, router reload failures with invalid certificates are prevented. ([OCPBUGS-49769](#))- • To maintain compatibility with Kubernetes 1.34, CoreDNS has been updated to version 1.13.1. This update resolves intermittent DNS resolution issues reported in previous versions and includes upstream performance fixes and security patches.\n\n### 1.8.5. Clock state metrics degrade correctly after upstream clock loss\n\n- • Previously, when the upstream clock connection was lost and the clock entered the **unlocked** state, the **ptp4l** and **ts2phc** clock state metrics did not degrade as expected. This behavior caused inconsistent time synchronization state reporting. This issue has been fixed. When the upstream clock connection is lost, the **ptp4l** and **ts2phc** clock state metrics now degrade correctly, providing consistent time synchronization state reporting.\n\n### 1.8.6. Node Tuning Operator\n\n- • Before this update, the Performance Profile Creator tool failed to analyze a **must-gather** archive if the archive contained a custom namespace directory ending with the suffix **nodes**. With this release, the PPC now correctly excludes the **namespaces** directory when processing the must-gather data to create a suggested **PerformanceProfile**. ([OCPBUGS-60218](#))\n\n### 1.8.7. OpenShift API Server\n\n- • Before this update, there was an incorrect error field path for **hostUsers** when validating a security context constraint. It was shown as **.spec.securityContext.hostUsers**, but **hostUsers** is not in the security context. With this release, the error field path is now **.spec.hostUsers**. ([OCPBUGS-65727](#))\n\n## 1.9. TECHNOLOGY PREVIEW FEATURES STATUS\n\nSome features in this release are currently in Technology Preview. These experimental features are not intended for production use. Note the following scope of support on the Red Hat Customer Portal for these features:\n\n### Technology Preview Features Support Scope\n\nIn the following tables, features are marked with the following statuses:\n\n- • *Not Available*\n- • *Technology Preview*\n- • *General Availability*\n- • *Deprecated*\n- • *Removed*\n\n### 1.9.1. Authentication and authorization Technology Preview features\n\nTable 1.11. Authentication and authorization Technology Preview tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Pod security admission restricted enforcement</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Direct authentication with an external OIDC identity provider</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>KMS Plugin</td>\n<td>Not Available</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n### 1.9.2. Edge computing Technology Preview features\n\nTable 1.12. Edge computing Technology Preview tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Accelerated provisioning of GitOps ZTP</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Enabling disk encryption with TPM and PCR protection</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Configuring a local arbiter node</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Configuring a two-node OpenShift Container Platform cluster with fencing</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n### 1.9.3. Extensions Technology Preview features\n\nTable 1.13. Extensions Technology Preview tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Operator Lifecycle Manager (OLM) v1</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>OLM v1 runtime validation of container images using sigstore signatures</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>OLM v1 permissions preflight check for cluster extensions</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>OLM v1 deploying a cluster extension in a specified namespace</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>OLM v1 deploying a cluster extension that uses webhooks</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>OLM v1 software catalog</td>\n<td>Not Available</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n### 1.9.4. Installation Technology Preview features\n\nTable 1.14. Installation Technology Preview tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Adding kernel modules to nodes with kvc</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Enabling NIC partitioning for SR-IOV devices</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>User-defined labels and tags for Google Cloud</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Installing a cluster on Alibaba Cloud by using Assisted Installer</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Installing a cluster on Microsoft Azure with confidential VMs</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Dedicated disk for etcd on Microsoft Azure</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Mount shared entitlements in BuildConfigs in RHEL</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>OpenShift zones support for vSphere host groups</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Selectable Cluster Inventory</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Installing a cluster on Google Cloud using the Cluster API implementation</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Enabling a user-provisioned DNS on Google Cloud</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Enabling a user-provisioned DNS on Microsoft Azure</td>\n<td>Not Available</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Enabling a user-provisioned DNS on Amazon Web Services (AWS)</td>\n<td>Not Available</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Installing a cluster using Google Cloud private and restricted API endpoints</td>\n<td>Not Available</td>\n<td>Not Available</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Installing a cluster on VMware vSphere with multiple network interface controllers</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Using bare metal as a service</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Running firmware upgrades for hosts in deployed bare metal clusters</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Changing the CVO log level</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n### 1.9.5. Machine Config Operator Technology Preview features\n\nTable 1.15. Machine Config Operator Technology Preview tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Boot image management for Azure and vSphere</td>\n<td>Not available</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Boot image management for control plane nodes</td>\n<td>Not available</td>\n<td>Not available</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>image mode for OpenShift status reporting improvements</td>\n<td>Not available</td>\n<td>Not available</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Overriding storage or partition setup</td>\n<td>Not available</td>\n<td>Not available</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n### 1.9.6. Machine management Technology Preview features\n\nTable 1.16. Machine management Technology Preview tracker<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Managing machines with the Cluster API for Amazon Web Services</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Managing machines with the Cluster API for Google Cloud</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Managing machines with the Cluster API for IBM Power® Virtual Server</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Managing machines with the Cluster API for Microsoft Azure</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Managing machines with the Cluster API for RHOSP</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Managing machines with the Cluster API for VMware vSphere</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Managing machines with the Cluster API for bare metal</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Cloud controller manager for IBM Power® Virtual Server</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Adding multiple subnets to an existing VMware vSphere cluster by using compute machine sets</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Configuring Trusted Launch for Microsoft Azure virtual machines by using machine sets</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Configuring Azure confidential virtual machines by using machine sets</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Bare-metal nodes on VMware vSphere clusters</td>\n<td>Not Available</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n### 1.9.7. Multi-Architecture Technology Preview features\n\nTable 1.17. Multi-Architecture Technology Preview tracker\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>kdump</b> on <b>arm64</b> architecture</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td><b>kdump</b> on <b>s390x</b> architecture</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n</tbody>\n</table>"},"html":{"kind":"string","value":"<h1>OpenShift Container Platform 4.21</h1><h2>Release notes</h2><p>Highlights of what is new and what has changed with this OpenShift Container Platform release</p><h1>OpenShift Container Platform 4.21 Release notes</h1><hr/><p>Highlights of what is new and what has changed with this OpenShift Container Platform release</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.</p><p>Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.</p><p>Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.</p><p>Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.</p><p>XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.</p><p>The OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.</p><p>All other trademarks are the property of their respective owners.</p><h2>Abstract</h2><p>The release notes for OpenShift Container Platform summarize all new features and enhancements, notable technical changes, major corrections from the previous version, and any known bugs upon general availability.</p>\n<h1>Table of Contents</h1>\n\n<table>\n<tr>\n<td><b>CHAPTER 1. OPENSHIFT CONTAINER PLATFORM 4.21 RELEASE NOTES .....</b></td>\n<td><b>4</b></td>\n</tr>\n<tr>\n<td>1.1. ABOUT THIS RELEASE</td>\n<td>4</td>\n</tr>\n<tr>\n<td>1.2. OPENSHIFT CONTAINER PLATFORM LAYERED AND DEPENDENT COMPONENT SUPPORT AND COMPATIBILITY</td>\n<td>4</td>\n</tr>\n<tr>\n<td>1.3. NEW FEATURES AND ENHANCEMENTS</td>\n<td>4</td>\n</tr>\n<tr>\n<td> 1.3.1. API server</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.3.2. Authentication and authorization</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.3.3. Autoscaling</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.3.4. Edge computing</td>\n<td>6</td>\n</tr>\n<tr>\n<td> 1.3.5. etcd</td>\n<td>6</td>\n</tr>\n<tr>\n<td> 1.3.6. Extensions (OLM v1)</td>\n<td>6</td>\n</tr>\n<tr>\n<td> 1.3.7. IBM Power</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 1.3.8. IBM Z and IBM LinuxONE</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 1.3.9. Installation and update</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 1.3.10. Machine Config Operator</td>\n<td>10</td>\n</tr>\n<tr>\n<td> 1.3.11. Machine management</td>\n<td>11</td>\n</tr>\n<tr>\n<td> 1.3.12. Monitoring</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 1.3.13. Networking</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 1.3.14. Nodes</td>\n<td>13</td>\n</tr>\n<tr>\n<td> 1.3.15. OpenShift CLI (oc)</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.3.16. Operator development</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.3.17. Postinstallation configuration</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.3.18. Scalability and performance</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.3.19. Storage</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 1.3.20. Web console</td>\n<td>17</td>\n</tr>\n<tr>\n<td>1.4. NOTABLE TECHNICAL CHANGES</td>\n<td>17</td>\n</tr>\n<tr>\n<td>1.5. DEPRECATED AND REMOVED FEATURES</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 1.5.1. Images deprecated and removed features</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 1.5.2. Installation deprecated and removed features</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 1.5.3. Machine Management deprecated and removed features</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 1.5.4. Networking deprecated and removed features</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 1.5.5. Node deprecated and removed features</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 1.5.6. OpenShift CLI (oc) deprecated and removed features</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 1.5.7. Operator lifecycle and development deprecated and removed features</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 1.5.8. Storage deprecated and removed features</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 1.5.9. Web console deprecated and removed features</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 1.5.10. Workloads deprecated and removed features</td>\n<td>20</td>\n</tr>\n<tr>\n<td>1.6. DEPRECATED FEATURES</td>\n<td>20</td>\n</tr>\n<tr>\n<td>1.7. REMOVED FEATURES</td>\n<td>20</td>\n</tr>\n<tr>\n<td>1.8. FIXED ISSUES</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.8.1. Installer</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.8.2. Kube Controller Manager</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.8.3. Kube Scheduler</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.8.4. Networking</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.8.5. Clock state metrics degrade correctly after upstream clock loss</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 1.8.6. Node Tuning Operator</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 1.8.7. OpenShift API Server</td>\n<td>22</td>\n</tr>\n<tr>\n<td>1.9. TECHNOLOGY PREVIEW FEATURES STATUS</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 1.9.1. Authentication and authorization Technology Preview features</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 1.9.2. Edge computing Technology Preview features</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 1.9.3. Extensions Technology Preview features</td>\n<td>23</td>\n</tr>\n</table>\n\n<table>\n<tr><td>1.9.4. Installation Technology Preview features</td><td>24</td></tr>\n<tr><td>1.9.5. Machine Config Operator Technology Preview features</td><td>25</td></tr>\n<tr><td>1.9.6. Machine management Technology Preview features</td><td>25</td></tr>\n<tr><td>1.9.7. Multi-Architecture Technology Preview features</td><td>26</td></tr>\n<tr><td>1.9.8. Networking Technology Preview features</td><td>27</td></tr>\n<tr><td>1.9.9. Node Technology Preview features</td><td>29</td></tr>\n<tr><td>1.9.10. OpenShift CLI (oc) Technology Preview features</td><td>29</td></tr>\n<tr><td>1.9.11. Operator lifecycle and development Technology Preview features</td><td>29</td></tr>\n<tr><td>1.9.12. Red Hat OpenStack Platform (RHOSP) Technology Preview features</td><td>30</td></tr>\n<tr><td>1.9.13. Scalability and performance Technology Preview features</td><td>30</td></tr>\n<tr><td>1.9.14. Storage Technology Preview features</td><td>30</td></tr>\n<tr><td>1.9.15. Web console Technology Preview features</td><td>32</td></tr>\n<tr><td>1.10. KNOWN ISSUES</td><td>32</td></tr>\n<tr><td>1.11. ASYNCHRONOUS ERRATA UPDATES</td><td>34</td></tr>\n<tr><td>1.11.1. RHBA-2026:6561 - OpenShift Container Platform 4.21.9 fixed issues advisory</td><td>34</td></tr>\n<tr><td>1.11.1.1. Fixed issues</td><td>34</td></tr>\n<tr><td>1.11.1.2. Updating</td><td>36</td></tr>\n<tr><td>1.11.2. RHBA-2026:5926 - OpenShift Container Platform 4.21.8 fixed issues advisory</td><td>37</td></tr>\n<tr><td>1.11.2.1. Enhancements</td><td>37</td></tr>\n<tr><td>1.11.2.2. Known issues</td><td>37</td></tr>\n<tr><td>1.11.2.3. Fixed issues</td><td>37</td></tr>\n<tr><td>1.11.2.4. Updating</td><td>38</td></tr>\n<tr><td>1.11.3. RHSA-2026:5174 - OpenShift Container Platform 4.21.7 fixed issues advisory</td><td>38</td></tr>\n<tr><td>1.11.3.1. Fixed issues</td><td>38</td></tr>\n<tr><td>1.11.3.2. Updating</td><td>39</td></tr>\n<tr><td>1.11.4. RHBA-2026:4420 - OpenShift Container Platform 4.21.6 fixed issues</td><td>39</td></tr>\n<tr><td>1.11.4.1. New features</td><td>40</td></tr>\n<tr><td>1.11.4.2. Known issues</td><td>40</td></tr>\n<tr><td>1.11.4.3. Fixed issues</td><td>40</td></tr>\n<tr><td>1.11.4.4. Updating</td><td>41</td></tr>\n<tr><td>1.11.5. RHBA-2026:3881 - OpenShift Container Platform 4.21.5 fixed issues</td><td>41</td></tr>\n<tr><td>1.11.5.1. Fixed issues</td><td>42</td></tr>\n<tr><td>1.11.5.2. Updating</td><td>42</td></tr>\n<tr><td>1.11.6. RHSA-2026:3402 - OpenShift Container Platform 4.21.4 image release, fixed issues, and security update</td><td>43</td></tr>\n<tr><td>1.11.6.1. Fixed issues</td><td>43</td></tr>\n<tr><td>1.11.6.2. Updating</td><td>44</td></tr>\n<tr><td>1.11.7. RHSA-2026:2984 - OpenShift Container Platform 4.21.3 fixed issues and security update</td><td>44</td></tr>\n<tr><td>1.11.7.1. Known issues</td><td>44</td></tr>\n<tr><td>1.11.7.2. Fixed issues</td><td>44</td></tr>\n<tr><td>1.11.7.3. Updating</td><td>45</td></tr>\n<tr><td>1.11.8. RHBA-2026:2637 - OpenShift Container Platform 4.21.2 fixed issues</td><td>45</td></tr>\n<tr><td>1.11.8.1. Enhancements</td><td>45</td></tr>\n<tr><td>1.11.8.2. Fixed issues</td><td>45</td></tr>\n<tr><td>1.11.8.3. Updating</td><td>46</td></tr>\n<tr><td>1.11.9. RHSA-2026:2129 - OpenShift Container Platform 4.21.1 fixed issues and security update</td><td>46</td></tr>\n<tr><td>1.11.9.1. Enhancements</td><td>47</td></tr>\n<tr><td>1.11.9.2. Known issues</td><td>47</td></tr>\n<tr><td>1.11.9.3. Fixed issues</td><td>48</td></tr>\n<tr><td>1.11.9.4. Updating</td><td>58</td></tr>\n<tr><td><b>CHAPTER 2. ADDITIONAL RELEASE NOTES</b> .....</td><td><b>59</b></td></tr>\n</table>\n<h1>CHAPTER 1. OPENSHIFT CONTAINER PLATFORM 4.21<br/>RELEASE NOTES</h1><p>Red Hat OpenShift Container Platform provides developers and IT organizations with a hybrid cloud application platform for deploying both new and existing applications on secure, scalable resources with minimal configuration and management. OpenShift Container Platform supports a wide selection of programming languages and frameworks, such as Java, JavaScript, Python, Ruby, and PHP.</p><p>Built on Red Hat Enterprise Linux (RHEL) and Kubernetes, OpenShift Container Platform provides a more secure and scalable multitenant operating system for today's enterprise-class applications, while delivering integrated application runtimes and libraries. OpenShift Container Platform enables organizations to meet security, privacy, compliance, and governance requirements.</p><h2>1.1. ABOUT THIS RELEASE</h2><p>OpenShift Container Platform (<a href=\"#\">RHBA-2026:1481</a>) is now available. This release uses <a href=\"#\">Kubernetes 1.34</a> with CRI-O runtime. New features, changes, and known issues that pertain to OpenShift Container Platform 4.21 are included in this topic.</p><p>OpenShift Container Platform 4.21 clusters are available at <a href=\"https://console.redhat.com/openshift\">https://console.redhat.com/openshift</a>. From the Red Hat Hybrid Cloud Console, you can deploy OpenShift Container Platform clusters to either on-premises or cloud environments.</p><p>You must use RHCOS machines for the control plane and for the compute machines.</p><p>Starting from OpenShift Container Platform 4.14, the Extended Update Support (EUS) phase for even-numbered releases increases the total available lifecycle to 24 months on all supported architectures, including <b>x86_64</b>, 64-bit ARM (<b>aarch64</b>), IBM Power® (<b>ppc64le</b>), and IBM Z® (<b>s390x</b>) architectures. Beyond this, Red Hat also offers a 12-month additional EUS add-on, denoted as <i>Additional EUS Term 2</i>, that extends the total available lifecycle from 24 months to 36 months. The Additional EUS Term 2 is available on all architecture variants of OpenShift Container Platform. For more information about support for all versions, see the <a href=\"#\">Red Hat OpenShift Container Platform Life Cycle Policy</a>.</p><p>OpenShift Container Platform is designed for FIPS. When running Red Hat Enterprise Linux (RHEL) or Red Hat Enterprise Linux CoreOS (RHCOS) booted in FIPS mode, OpenShift Container Platform core components use the RHEL cryptographic libraries that have been submitted to NIST for FIPS 140-2/140-3 Validation on only the <b>x86_64</b>, <b>ppc64le</b>, and <b>s390x</b> architectures.</p><p>For more information about the NIST validation program, see <a href=\"#\">Cryptographic Module Validation Program</a>. For the latest NIST status for the individual versions of RHEL cryptographic libraries that have been submitted for validation, see <a href=\"#\">Compliance Activities and Government Standards</a>.</p><h2>1.2. OPENSHIFT CONTAINER PLATFORM LAYERED AND DEPENDENT COMPONENT SUPPORT AND COMPATIBILITY</h2><p>The scope of support for layered and dependent components of OpenShift Container Platform changes independently of the OpenShift Container Platform version. To determine the current support status and compatibility for an add-on, refer to its release notes. For more information, see the <a href=\"#\">Red Hat OpenShift Container Platform Life Cycle Policy</a>.</p><h2>1.3. NEW FEATURES AND ENHANCEMENTS</h2><p>This release adds improvements related to the following components and concepts:</p><h3>1.3.1. API server</h3><h4>Dynamic updates to storage performance parameters by using VolumeAttributesClass</h4><p>Before this release, updating storage performance parameters such as IOPS or throughput often required manual volume reprovisioning, complex snapshot migrations, or application downtime. With this release, OpenShift Container Platform supports the <b>VolumeAttributesClass</b> (VAC) API, enabling you to modify and dynamically scale storage parameters by updating the VAC assigned to a <b>PersistentVolumeClaim</b> (PVC). This support allows on-demand performance tuning without service interruption.</p><h3>1.3.2. Authentication and authorization</h3><h4>Using the Azurekubelogin plugin for direct authentication with Microsoft Entra ID</h4><p>Red Hat tested authenticating to OpenShift Container Platform by using the Azure <b>kubelogin</b> plugin. This validation covers environments where Microsoft Entra ID is configured as the external OIDC provider for direct authentication. The following login modes for <b>kubelogin</b> were tested:</p><ul><li>• Device code grant</li><li>• Service principal authentication</li><li>• Interactive web browser flow</li></ul><p>For more information, see <a href=\"#\">Enabling direct authentication with an external OIDC identity provider</a> .</p><h4>ConsoleLink support for email links</h4><p>The <b>ConsoleLink</b> Custom Resource Definition supports <b>mailto:</b> links. You can create email links in the OpenShift web console that open the default email client.</p><h4>Impersonating a user with multiple group memberships in the console</h4><p>Cluster administrators can impersonate a user with multiple group memberships at the same time in the OpenShift web console. This supports reproducing effective permissions for RBAC troubleshooting.</p><h4>Customizing the Code Editor theme and font size in the console</h4><p>With this update, users can customize the Code Editor theme and adjust the font size. By default, the Code Editor theme follows the active OpenShift Console theme, but users can now set it independently. These options improve productivity and reduce the need for frequent changes.</p><h4>Quick starts for Trusted Profile Analyzer and Trusted Artifact Signer</h4><p>With this update, the OpenShift Console adds two quick starts for Trusted Profile Analyzer and Trusted Artifact Signer to the Overview page, making them easier to find and use. This change simplifies the user journey, improves the user experience, and strengthens product integration by highlighting Red Hat's security ecosystem within the platform.</p><h4>Grouping Helm charts under the Ecosystem header</h4><p>Before this update, the OpenShift Console introduced the unified view in 4.19, and the <b>Helm</b> UI displayed in the <b>Admin</b> view but outside the <b>Ecosystem</b> menu. With this update, the OpenShift Console displays <b>Helm</b> under <b>Ecosystem</b>, centralizing software management navigation in one location within the unified view.</p><h3>1.3.3. Autoscaling</h3><h4>Network policy support for Autoscaling Operators</h4><p>The following Operators now have multiple network policies that control network traffic to and from the Operator and operand pods. These policies restrict traffic to only traffic that is explicitly allowed or required.</p><ul><li>• Cluster Resource Override Operator</li><li>• Cluster Autoscaler</li><li>• Vertical Pod Autoscaler</li><li>• Horizontal Pod Autoscaler</li></ul><h3>Applying VPA recommendations without pod re-creation</h3><p>You can now configure a Vertical Pod Autoscaler Operator (VPA) in the <b>InPlaceOrRecreate</b> mode. In this mode, the VPA attempts to apply the recommended updates without re-creating pods. If the VPA is unable to update the pods in place, the VPA falls back to re-creating the pods. For more information, see <a href=\"#\">About the Vertical Pod Autoscaler Operator modes</a>.</p><h3>Cluster Autoscaler Operator can now cordon nodes before removing the node</h3><p>By default, when the Cluster Autoscaler Operator removes a node, it does not cordon the node when draining the pods from the node. You can configure the Operator to cordon the node before draining and moving the pods. For more information, see <a href=\"#\">About the cluster autoscaler</a>.</p><h2>1.3.4. Edge computing</h2><h3>ClusterInstance CR replaces SiteConfig CR for GitOps ZTP deployments</h3><p>In earlier releases, the <b>SiteConfig</b> custom resource (CR) was deprecated. This release removes support for the <b>SiteConfig</b> CR. You must now use the <b>ClusterInstance</b> CR to deploy managed clusters with GitOps ZTP. For more information, see <a href=\"#\">Deploying a managed cluster with ClusterInstance and GitOps ZTP</a>.</p><h3>Support for removing devices and device classes from a volume group</h3><p>You can remove the device paths in the <b>deviceSelector.paths</b> field and the <b>deviceClass</b> object from the <b>LVMCluster</b> resource. For more information, see <a href=\"#\">About removing devices and device classes from a volume group</a></p><h2>1.3.5. etcd</h2><h3>Manage etcd size by limiting the time-to-live (TTL) duration for Kubernetes events (Technology Preview)</h3><p>With this release, you can manage etcd size by setting the <b>eventTTLMinutes</b> property. Having too many stale Kubernetes events in an etcd database can degrade performance. By setting the <b>eventTTLMinutes</b> property, you can specify how long an event can stay in the database before it is purged. For more information, see <a href=\"#\">Managing etcd size by limiting the duration of Kubernetes events</a>.</p><h2>1.3.6. Extensions (OLM v1)</h2><h3>Cluster extension support for webhooks in bundles</h3><p>With this update, OLM v1 supports Operators that use webhooks for validation, mutation, or conversion. For more information, see <a href=\"#\">Webhook support</a>.</p><h3>Support for <b>SingleNamespace</b> and <b>OwnNamespace</b> install modes by using the configuration API (Technology Preview)</h3>\n<p>If an Operator supports the <b>SingleNamespace</b> or <b>OwnNamespace</b> install modes, you can configure the Operator to watch a specified namespace. For more information, see <a href=\"#\">Extension configuration</a>.</p>\n\n<h3>OLM v1 software catalog in the web console (Technology Preview)</h3>\n\n<p>With this update, you can preview the OLM v1 software catalog in the web console. Select <b>Ecosystem → Software Catalog → Operators</b> to preview this feature. To see the OLM (Classic) software catalog, click the <b>Enable OLM v1 (Tech Preview)</b> toggle.</p>\n\n<h2>1.3.7. IBM Power</h2>\n\n<h3>The IBM Power® release on OpenShift Container Platform 4.21 adds improvements and new capabilities to OpenShift Container Platform components</h3>\n\n<p>This release introduces support for the following features on IBM Power:</p>\n\n<ul>\n<li>• Enable Installer-Provisioned Infrastructure (IPI) support for PowerVC [Technology Preview]</li>\n<li>• Enable Spyre Accelerator on IBM Power®</li>\n</ul>\n\n<h3>The IBM Power® release for OpenShift Container Platform 4.21 adds support for the following operator</h3>\n\n<ul>\n<li>• CIFS/SMB CSI Driver Operator</li>\n<li>• Kernel Module Management Operator (KMMO)</li>\n<li>• Red Hat build of Kueue</li>\n</ul>\n\n<h3>IMPORTANT</h3>\n\n<p>When using <b>kdump</b> on IBM Power®, the following limitations apply:</p>\n\n<ul>\n<li>• Firmware-assisted dump (<b>fadump</b>) is not supported.</li>\n<li>• Persistent memory dump is not supported.</li>\n</ul>\n\n<h2>1.3.8. IBM Z and IBM LinuxONE</h2>\n\n<h3>The IBM Z® and IBM® LinuxONE release on OpenShift Container Platform 4.21 adds improvements and new capabilities to OpenShift Container Platform components</h3>\n\n<p>This release introduces support for the following features on IBM Z® and IBM® LinuxONE:</p>\n\n<ul>\n<li>• Enable Spyre Accelerator on IBM Z®</li>\n</ul>\n\n<h3>The IBM Z® release for OpenShift Container Platform 4.21 adds support for the following operator</h3>\n\n<ul>\n<li>• Kernel Module Management Operator (KMMO)</li>\n<li>• Red Hat build of Kueue</li>\n</ul>\n\n<h2>1.3.9. Installation and update</h2>\n\n<h3>Restricting service account impersonation to the compute nodes service account</h3>\n\n<p>When you install a Google Cloud and configure it to use Google Cloud Workload Identity, you can</p>\n<p>now restrict the Google Cloud <b>iam.serviceAccounts.actAs</b> permission that the Cloud Credential Operator utility grants the Machine API controller service account at the project level to only the compute nodes service account.</p><p>For more information, see <a href=\"#\">Restricting service account impersonation to the compute nodes service account</a>.</p><h3>Configuring image mode for OpenShift during installation is now supported</h3><p>You can now apply a custom layered image to your nodes during OpenShift Container Platform installation. For more information, see <a href=\"#\">Applying a custom layered image during OpenShift Container Platform installation</a>.</p><h3>Installing a cluster on Google Cloud with a user-provisioned DNS is generally available</h3><p>You can enable a user-provisioned domain name server (DNS) instead of the default cluster-provisioned DNS solution. For example, your organization's security policies might not allow the use of public DNS services such as Google Cloud DNS. You can manage your DNS only for the IP addresses of the API and Ingress servers. If you use this feature, you must provide your own DNS solution that includes records for <b>api.<cluster_name>.<base_domain>.</b> and <b>*.apps.<cluster_name>.<base_domain>..</b></p><p>Installing a cluster on Google Cloud with a user-provisioned DNS was introduced in OpenShift Container Platform 4.19 with Technology Preview status. In OpenShift Container Platform 4.21, it is now generally available.</p><p>For more information, see <a href=\"#\">Enabling a user-managed DNS</a> and <a href=\"#\">Provisioning your own DNS records</a>.</p><h3>Installing a cluster on Microsoft Azure uses Marketplace images by default</h3><p>As of this update, the OpenShift Container Platform installation program uses Marketplace images by default when installing a cluster on Azure. This speeds up the installation by removing the need to upload a virtual hard disk to Azure and create an image during installation. This feature is not supported on Azure Stack Hub, or for Azure installations that use Confidential VMs.</p><h3>The <b>ccocntl</b> utility supports preserving custom Microsoft Azure role assignments</h3><p>The Cloud Credential Operator utility (<b>ccocntl</b>) can now preserve custom role assignments by using the <b>--preserve-existing-roles</b> flag. Previously, the tool removed role assignments that were not defined in the <code>CredentialsRequest</code>, including those manually added by administrators.</p><h3>Managing your own firewall rules when installing a cluster on Google Cloud into an existing VPC</h3><p>As of this update, you can manage your own firewall rules when installing a cluster on Google Cloud into an existing VPC by enabling the <b>firewallRulesManagement</b> parameter in the <b>install-config.yaml</b> file. You can limit the permissions that you grant to the installation program by managing your own firewall rules.</p><p>For more information, see <a href=\"#\">Managing your own firewall rules</a>.</p><h3>The <b>ccocntl</b> utility supports Amazon Web Services permissions boundaries</h3><p>The Cloud Credential Operator utility (<b>ccocntl</b>) now supports attaching an AWS permissions boundary to the IAM roles that it creates. You can use this feature to meet organizational security requirements that restrict the maximum permissions of created roles.</p><h3>Throughput customization for Amazon Web Services gp3 drives</h3><p>With this update, you can now customize the maximum throughput for gp3 <b>rootVolume</b> drives when installing a cluster on Amazon Web Services. This customization is set by modifying the <b>compute.platform.aws.rootVolume.throughput</b> or <b>controlPlane.platform.aws.rootVolume.throughput</b> parameters in the <b>install-config.yaml</b> file.</p><p>For more information, see <a href=\"#\">Optional AWS configuration parameters</a>.</p>\n<h2>Support for VMware vSphere Foundation 9 and VMware Cloud Foundation 9</h2>\n\n<p>You can now install OpenShift Container Platform on VMware vSphere Foundation (VVF) 9 and VMware Cloud Foundation (VCF) 9.</p>\n\n<h3>NOTE</h3>\n\n<p>The following additional VCF and VVF components are outside the scope of Red Hat support:</p>\n\n<ul>\n<li>• Management: VCF Operations, VCF Automation, VCF Fleet Management, and VCF Identity Broker.</li>\n<li>• Networking: VMware NSX Container Plugin (NCP).</li>\n<li>• Migration: VMware HCX.</li>\n</ul>\n\n<h2>Support for installing OpenShift Container Platform on Oracle Database Appliance (ODA)</h2>\n\n<p>With this update, you can install a cluster on Oracle Database Appliance using the Assisted Installer. For more information, see <a href=\"#\">Installing a cluster on Oracle Database Appliance by using the Assisted Installer</a>.</p>\n\n<h2>Installing a dual-stack cluster on Red Hat OpenStack Platform (RHOSP) when the machine network is IPv6-only</h2>\n\n<p>From RHOSP 17.1, you can deploy a dual-stack OpenShift Container Platform cluster when your RHOSP machine network is IPv6-only; the cluster still uses IPv4 for internal cluster and service networks.</p>\n\n<p>For more information, see <a href=\"#\">Configuring a cluster with dual-stack networking</a>.</p>\n\n<h2>Installing a cluster on AWS with a user-provisioned DNS (Technology Preview)</h2>\n\n<p>You can enable a user-provisioned domain name server (DNS) instead of the default cluster-provisioned DNS solution. For example, your organization's security policies might not allow the use of public DNS services such as Amazon Web Services (AWS) DNS. As a result, you can manage the API and Ingress DNS records in your own system rather than adding the records to the DNS of the cloud. If you use this feature, you must provide your own DNS solution that includes records for <b>api.<cluster_name>.<base_domain></b>. and <b>*.apps.<cluster_name>.<base_domain></b>. Enabling a user-provisioned DNS is available as a Technology Preview feature.</p>\n\n<p>For more information, see <a href=\"#\">Enabling a user-managed DNS</a> and <a href=\"#\">Provisioning your own DNS records</a>.</p>\n\n<h2>Installing a cluster on Microsoft Azure using NAT Gateways</h2>\n\n<p>With this update, you can install a cluster on Azure using NAT Gateways as your outbound routing strategy. NAT Gateways can minimize the risk of SNAT port exhaustion that can occur with other outbound routing strategies. You can configure NAT Gateways using the <b>platform.azure.outboundType</b> parameter in the <b>install-config.yaml</b> file.</p>\n\n<p>For more information, see <a href=\"#\">Additional Azure configuration parameters</a>.</p>\n\n<h2>Installing a cluster using Google Cloud private and restricted API endpoints</h2>\n\n<p>With this release, you can use Google Cloud Private Service Connect (PSC) endpoints when installing your OpenShift Container Platform cluster so that your installation meets your organization's strict regulatory policies.</p>\n\n<p>For more information, see <a href=\"#\">Optional configuration parameters</a>.</p>\n<h3>Dell iDRAC10 supported for bare metal installation using Redfish virtual media</h3><p>Dell iDRAC10 versions 1.20.25.00, 1.20.60.50, and 1.20.70.50 have been tested and verified to work for installer-provisioned OpenShift Container Platform clusters deployed by using Redfish virtual media. iDRAC10 has not been tested with installations that use a provisioning network. For more information, see <a href=\"#\">Firmware requirements for installing with virtual media</a>.</p><h3>Providing a local or self-signed CA certificate for Baseboard Management Controllers (BMCs) when installing a cluster on bare metal</h3><p>With this update, you can provide your own local or self-signed CA certificate to secure communication with BMCs when installing a cluster on bare metal. You can configure this certificate using the <b>platform.baremetal.bmcCACert</b> parameter in the <code>install-config.yaml</code> file. If you do not use a trusted CA certificate, you can secure BMC communication by providing your own CA certificate. You can also configure a local or self-signed CA certificate after installation, whether the cluster was installed with a different BMC CA certificate or with no BMC CA certificate.</p><p>For more information, see <a href=\"#\">Additional installation configuration parameters</a> and <a href=\"#\">Configuring a local or self-signed Baseboard Management Controller CA certificate</a>.</p><h3>Running firmware upgrades for hosts in deployed bare metal clusters (Generally Available)</h3><p>For hosts in deployed bare metal clusters, you can update firmware attributes and the firmware image. As a result, you can run firmware upgrades and update BIOS settings for hosts that are already provisioned without fully deprovisioning them. Performing a live update to the <b>HostFirmwareComponents</b>, <b>HostFirmwareSettings</b>, or <b>HostUpdatePolicy</b> resource can be a destructive and destabilizing action. Perform these updates only after careful consideration. This feature was introduced in OpenShift Container Platform 4.18 with Technology Preview status. This feature is now supported as generally available in OpenShift Container Platform 4.21.</p><p>For more information, see <a href=\"#\">Performing a live update to the HostFirmwareSettings resource</a>, <a href=\"#\">Performing a live update to the HostFirmwareComponents resource</a>, and <a href=\"#\">Setting the HostUpdatePolicy resource</a>.</p><h3>Testing for Amazon Web Services m7 instance type</h3><p>As of OpenShift Container Platform 4.21, m7 instance types have been tested for installations on Amazon Web Services. For more information about tested instance types, see <a href=\"#\">Tested instance types for AWS</a>.</p><h3>Installing a cluster on Microsoft Azure with a user-provisioned DNS (Technology Preview)</h3><p>You can enable a user-provisioned domain name server (DNS) instead of the default cluster-provisioned DNS solution. For example, your organization's security policies might not allow the use of public DNS services such as Microsoft Azure DNS. You can manage your DNS only for the IP addresses of the API and Ingress servers. If you use this feature, you must provide your own DNS solution that includes records for <b>api.<cluster_name>.<base_domain></b> and <b>*.apps.<cluster_name>.<base_domain></b>. Enabling a user-provisioned DNS is available as a Technology Preview feature.</p><p>For more information, see <a href=\"#\">Enabling a user-managed DNS</a> and <a href=\"#\">Provisioning your own DNS records</a>.</p><h2>1.3.10. Machine Config Operator</h2><h3>Boot image management for Azure and vSphere clusters promoted to GA</h3><p>Updating boot images has been promoted to GA for Microsoft Azure and VMware vSphere clusters. For more information, see <a href=\"#\">Boot image management</a>.</p><h3>Configuring image mode for OpenShift during installation is now supported</h3>\n<p>You can now apply a custom layered image to your nodes during OpenShift Container Platform installation. For more information, see <a href=\"#\">Applying a custom layered image during OpenShift Container Platform installation</a>.</p>\n\n<h3>Image mode for OpenShift status reporting improvements</h3>\n\n<p>The output of the <b>oc describe machineconfignodes <mcp_name></b> now contains an <b>ImageBuildDegraded</b> error that indicates if an image mode for OpenShift failed. For more information, see <a href=\"#\">About node status during updates</a>.</p>\n\n<h3>Image mode for OpenShift status reporting improvements (Technology preview)</h3>\n\n<p>The <b>oc describe machineconfigpool <mcp_name></b> output, as a Technology Preview feature, now includes the following fields that report the status of machine config updates when image mode for OpenShift is enabled:</p>\n\n<ul>\n<li>• <b>Spec.ConfigImage.DesiredImage</b>. This is the desired image for that node.</li>\n<li>• <b>Status.ConfigImage.CurrentImage</b>. This is the current image on that node.</li>\n<li>• <b>Status.Conditions.ImagePulledFromRegistry</b>. This reports whether an image is able to pull correctly in an image mode update.</li>\n</ul>\n\n<p>For more information, see <a href=\"#\">About node status during updates</a>.</p>\n\n<h3>Boot image management for control plane nodes is now supported (Technology Preview)</h3>\n\n<p>Updating boot images is now supported as a Technology Preview feature for VMware vSphere clusters. This feature allows you to configure your cluster to update the node boot image whenever you update your cluster. Previously, updating boot images was supported for worker nodes. For more information, see <a href=\"#\">Boot image management</a>.</p>\n\n<h3>Overriding storage or partition setup (Technology preview)</h3>\n\n<p>You can now use a <b>MachineConfig</b> object to change the installed disk partition schema, file systems, and RAID configurations for new nodes. Previously, for security reasons, you were blocked from changing these configurations from what was established during the cluster installation. For more information, see \"Overriding storage and partition setup\".</p>\n\n<h2>1.3.11. Machine management</h2>\n\n<h3>Creating Google Cloud Spot VMs by using compute machine sets</h3>\n\n<p>With this release, OpenShift Container Platform supports deploying Machine API compute machines on Spot VMs in Google Cloud clusters. Google Cloud recommends using Spot VMs over their predecessor, preemptible VMs, because they include new features that preemptible VMs do not support.</p>\n\n<p>For more information, see <a href=\"#\">Machine sets that deploy machines as Spot VMs</a>.</p>\n\n<h3>Additional control plane machine set failure domain options for Azure</h3>\n\n<p>This release includes additional configuration options for control plane machine set failure domains on Microsoft Azure.</p>\n\n<p>For more information, see <a href=\"#\">Sample Azure failure domain configuration</a>.</p>\n\n<h3>Configuration of throughput for Amazon Web Services gp3 volumes on EBS devices</h3>\n\n<p>This release includes support for configuring the maximum throughput for gp3 drives on EBS devices for clusters installed on Amazon Web Services (AWS).</p>\n\n<p>For more information, see <a href=\"#\">Configuring storage throughput for gp3 drives (Machine API)</a> and <a href=\"#\">Configuring storage throughput for gp3 drives (Cluster API)</a>.</p>\n<p>In OpenShift Container Platform version 4.21.1 and later, this feature also works with <a href=\"#\">control plane machine sets</a>.</p><h3>Bare-metal nodes on VMware vSphere clusters (Technology Preview)</h3><p>You can now add bare-metal compute machines to an existing OpenShift Container Platform cluster on vSphere. This capability enables you to migrate workloads to physical hardware without reinstalling the cluster. For instructions on adding these machines, see <a href=\"#\">Adding bare-metal compute machines to a vSphere cluster</a>.</p><h3>1.3.12. Monitoring</h3><h4>NOTE</h4><p>The monitoring stack documentation is now available as a separate documentation set. The 4.21 monitoring release notes are available at <a href=\"#\">Release notes for OpenShift monitoring</a>.</p><h3>1.3.13. Networking</h3><h4>MetalLB Operator status reporting</h4><p>You can now use enhanced MetalLB Operator reporting features to view real-time operational data for IP address allocation and Border Gateway Protocol (BGP) connectivity. Previously, viewing this information required manual log inspection across multiple controllers. With this release, you can monitor your network health and resolve connectivity issues directly through the following custom resources:</p><ul><li>● <b>IPAddressPool</b>: Monitor cluster-wide IP address allocation through the <b>status</b> field to track usage and prevent address exhaustion.</li><li>● <b>ServiceBGPSStatus</b>: Verify which service IP addresses are announced to specific BGP peers to ensure correct route advertisements.</li><li>● <b>BGPSessionStatus</b>: Check the real-time state of BGP and Bidirectional Forwarding Detection sessions to quickly identify connectivity drops.</li></ul><p>For more information, see <a href=\"#\">Monitoring MetalLB configuration status</a>.</p><h4>Applying unassisted holdover for boundary clocks and time synchronous clocks</h4><p>OpenShift Container Platform 4.20 introduced unassisted holdover for boundary clocks and time synchronous clocks as a Technology Preview feature. This feature is now Generally Available (GA). For more information, see <a href=\"#\">Applying unassisted holdover for boundary clocks and time slave clocks</a>.</p><h4>SR-IOV Operator supports ARM architecture</h4><p>The Single Root I/O Virtualization (SR-IOV) Operator can now communicate with ARM hardware. You can now complete tasks such as configure network cards that are already plugged into an ARM server and use these cards in your applications. For instructions on how to search for ARM hardware that the SR-IOV Operator supports, see <a href=\"#\">About Single Root I/O Virtualization (SR-IOV) hardware networks</a>.</p><h4>Support for Red Hat OpenShift Service Mesh version 3.2</h4><p>OpenShift Container Platform 4.21 updates Service Mesh to version 3.2. This version update incorporates essential CVE fixes and ensures that your OpenShift Container Platform instances receive the latest fixes, features, and enhancements. See the <a href=\"#\">Service Mesh 3.2 release notes</a> for more information.</p><h3>PTP Operator introduces GNSS-to-NTP failover for high-precision timing</h3>\n<p>With this release, the PTP Operator introduces an active GNSS-to-NTP failover configuration to ensure time synchronization continuity in environments requiring extremely high time accuracy. When the primary Global Navigation Satellite System (GNSS) signal is lost or compromised, for example because of satellite jamming, the system automatically fails over to Network Time Protocol (NTP) to maintain time accuracy. When the GNSS signal is restored, the system automatically recovers back to using GNSS as the primary time source.</p>\n\n<p>This feature is particularly important in telco environments that require high precision time synchronization with built-in redundancy. To enable GNSS to NTP failover, you configure the <b>PtpConfig</b> resource with the <b>ntpfailover</b> plugin enabled and configure both <b>chronyd</b> and <b>ts2phc</b> settings.</p>\n\n<p>For more information, see <a href=\"#\">Configuring GNSS failover to NTP for time synchronization continuity</a> .</p>\n<h3>Network policies for additional namespaces</h3>\n<p>With this release, OpenShift Container Platform continues to deploy Kubernetes network policies to additional system namespaces to control ingress and egress traffic. It is anticipated that future releases might include network policies for additional system namespaces and Red Hat Operators.</p>\n<h3>Ingress network flow analysis with the commatrix plugin</h3>\n<p>With this release, you can use the <b>commatrix</b> plugin to generate ingress network flow data from your cluster. You can also use the plugin to identify any differences between open ports on the host and expected ingress flows for your environment.</p>\n\n<p>For more information, see <a href=\"#\">Ingress network flow analysis with the commatrix plugin</a></p>\n<h3>Configure the dnsRecordsType parameter (Technology preview)</h3>\n<p>During cluster installation, you can specify the <b>dnsRecordsType</b> parameter in the <b>install-config.yaml</b> file to set if the internal DNS service or an external source provides the necessary records for <b>api</b>, <b>api-int</b>, and <b>ingress</b> DNS records. For more information about DNS requirements, see <a href=\"#\">User-provisioned DNS requirements</a>.</p>\n<h2>1.3.14. Nodes</h2><h3>Allocating specific GPUs to pods (DRA) is now generally available</h3>\n<p>Attribute-Based GPU Allocation, which allows pods to request GPUs based on specific device attributes by using a Dynamic Resource Allocation (DRA) driver, is now generally available. For more information, see <a href=\"#\">Allocating GPUs to Pods</a> .</p>\n<h3>The default openshift cluster image policy is now generally available</h3>\n<p>The default <b>openshift</b> cluster image policy is now generally available and active by default. For more information, see <a href=\"#\">Manage secure signatures with sigstore</a> .</p>\n\n<p>If your OpenShift Container Platform 4.20 or earlier cluster has a cluster image policy named <b>openshift</b>, the upgrade to OpenShift Container Platform marks the cluster as not updatable (<b>Upgradeable=False</b>) because of this default <b>openshift</b> cluster image policy. You must remove your <b>openshift</b> cluster image policy to clear the <b>Upgradeable=False</b> condition and proceed with the update. You can optionally create your own cluster image policy with a different name before removing your <b>openshift</b> cluster image policy.</p>\n<h3>Support for sigstore BYOPKI is now generally available</h3>\n<p>Support for using a certificate from your own public key infrastructure as a Sigstore root of trust is now generally available. For more information, see <a href=\"#\">Manage secure signatures with sigstore</a> .</p>\n<h2>Automatically calculate and apply CPU and memory resources for system components</h2><p>OpenShift Container Platform now automatically calculates and reserves a portion of the CPU and memory resources for use by the underlying node and system components. Previously, you needed to enable the feature by creating a <b>KubeletConfig</b> custom resource (CR) with the <b>autoSizingReserved: true</b> parameter. For clusters updated to OpenShift Container Platform 4.21, you can enable the feature by deleting the <b>50-worker-auto-sizing-disabled</b> machine config. After you delete the machine config, the nodes reboot with the new resource settings. If you manually configured system reserved CPU or memory resources, these settings remain upon update and do not change. For more information on this new feature, see <a href=\"#\">Automatically allocating resources for nodes</a>.</p><h2>Linux PSI monitoring can now be enabled</h2><p>You can now enable Linux Pressure Stall Information (PSI) monitoring, which makes PSI metrics for CPU, memory, and I/O available for your cluster, by using a <b>MachineConfig</b> object. For more information, see <a href=\"#\">Enabling Pressure Stall Information (PSI) monitoring</a>.</p><h3>1.3.15. OpenShift CLI (oc)</h3><h4>Signature mirroring enabled by default for oc-mirror v2</h4><p>With this update, the oc-mirror v2 plugin mirrors image signatures by default. This enhancement ensures that image integrity is automatically preserved during the mirroring process without requiring additional configuration. If your environment does not require signature validation, you can manually disable this feature by using the <b>--remove-signatures</b> command-line flag. For more information, see <a href=\"#\">Disabling signature mirroring for oc-mirror plugin v2</a>.</p><h3>1.3.16. Operator development</h3><h4>Supported Operator base images</h4><p>With this release, the following base images for Operator projects are updated for compatibility with OpenShift Container Platform 4.21. The runtime functionality and configuration APIs for these base images are supported for bug fixes and for addressing CVEs.</p><ul><li>• The base image for Ansible-based Operator projects</li><li>• The base image for Helm-based Operator projects</li></ul><p>For more information, see <a href=\"#\">Updating the base image for existing Ansible- or Helm-based Operator projects for OpenShift Container Platform 4.19 and later</a> (Red Hat Knowledgebase).</p><h3>1.3.17. Postinstallation configuration</h3><h4>Enabling hardware metrics monitoring on bare-metal clusters (Technology Preview)</h4><p>With this update, you can enable your cluster to collect hardware metrics from the Redfish-compatible baseboard management controllers of your bare-metal nodes. Metrics include temperature, power consumption, fan status, and drive health. You enable this Technology Preview feature by enabling the Ironic Prometheus Exporter in your cluster as a postinstallation task. For more information, see <a href=\"#\">Hardware metrics in the Monitoring stack</a>.</p><h3>1.3.18. Scalability and performance</h3><h4>Pod-level IRQ affinity introduces housekeeping mode</h4><p>For latency-sensitive workloads, you can now configure the <b>irq-load-balancing.crio.io</b> pod annotation to use <b>housekeeping</b> mode. This mode enables a subset of pinned CPUs to handle system interrupts while isolating the remaining pinned CPUs for latency-sensitive workloads. This reduces the overall CPU footprint by eliminating the need for dedicated housekeeping CPUs for IRQ handling. When you configure <b>housekeeping</b> mode, the first pinned CPU and its thread siblings handle interrupts for the system.</p><p>For more information, see <a href=\"#\">Configuring interrupt processing for individual pods</a>.</p><h3>1.3.19. Storage</h3><h4>Volume Attributes Classes is generally available</h4><p>Volume Attributes Classes provide a way for administrators to describe \"classes\" of storage they offer. Different classes might correspond to different quality-of-service levels. Volume Attributes Classes was introduced in OpenShift Container Platform 4.19, and is now generally available in 4.21. Volume Attributes Classes is available only with AWS Elastic Block Storage (EBS) and Google Cloud Platform (GCP) persistent disk (PD) Container Storage Interface (CSI).</p><p>You can apply a Volume Attributes Classes to a persistent volume claim (PVC). If a new Volume Attributes Class becomes available in the cluster, you can update the PVC with the new Volume Attributes Classes if needed.</p><p>Volume Attributes Classes have parameters that describe volumes belonging to them. If a parameter is omitted, the default is used at volume provisioning. If a user applies the PVC with a different Volume Attributes Class with omitted parameters, the default value of the parameters might be used depending on the CSI driver implementation. For more information, see the related CSI driver documentation.</p><p>For more information, see <a href=\"#\">Volume Attributes Classes</a>.</p><h4>Azure File CSI supporting snapshots feature is generally available</h4><p>A snapshot represents the state of the storage volume in a cluster at a particular point in time. Volume snapshots can be used to provision a new volume.</p><p>OpenShift Container Platform 4.17 introduced volume snapshot support for the Microsoft Azure File Container Storage Interface (CSI) Driver Operator as a Technology Preview feature. In 4.21, this feature is generally available. Also, Azure File snapshots now supports Network File System (NFS) in addition to Server Message Block (SMB).</p><p>For more information, see <a href=\"#\">CSI drivers supported by OpenShift Container Platform</a> and <a href=\"#\">CSI volume snapshots</a>.</p><h4>Azure File CSI supporting volume cloning feature is generally available</h4><p>Volume cloning duplicates an existing persistent volume (PV) to help protect against data loss in OpenShift Container Platform. You can also use a volume clone just as you would use any standard volume.</p><p>OpenShift Container Platform 4.16 introduced volume cloning for the Microsoft Azure File Container Storage Interface (CSI) Driver Operator as a Technology Preview feature. In 4.21, this feature is generally available. Also, Azure File cloning now supports Network File System (NFS) in addition to Server Message Block (SMB).</p><p>For more information, see <a href=\"#\">Azure File CSI Driver Operator</a> and <a href=\"#\">CSI volume cloning</a>.</p><h4>oVirt CSI Driver Operator is removed from OpenShift Container Platform 4.21</h4><p>Red Hat Virtualization (RHV) as a host platform for OpenShift Container Platform was deprecated in version 4.14 and is no longer supported. In OpenShift Container Platform 4.21, the oVirt CSI Driver Operator is removed.</p><h3>CIFS/SMB CSI Driver Operator supports IBM Power</h3><p>In OpenShift Container Platform 4.21, the CIFS/SMB CSI Driver Operator supports IBM Power (ppc64le).</p><p>For more information, see <a href=\"#\">CIFS/SMB CSI Driver Operator</a>.</p><h3>Introduction of new field to track the status of volume resize attempts</h3><p>OpenShift Container Platform 4.19 introduced resizing recovery that stops the expansion controller from indefinitely attempting to expand a volume to an unsupported size request. This feature allows you to recover and provide another smaller resize value for the persistent volume claim (PVC). The new value must be larger than the original volume size.</p><p>OpenShift Container Platform 4.21 introduces the <b>pvc.Status.AllocatedResourceStatus</b> field, which shows the status of volume resize attempts. If a user changes the size of their PVCs, this new field allows resource quota to be tracked accurately.</p><p>For more information about resizing volumes, see <a href=\"#\">Expanding persistent volumes</a>.</p><p>For more information about recovering when resizing volumes, see <a href=\"#\">Recovering from failure when expanding volumes</a>.</p><h3>Mutable CSI node allocatable property (Technical Preview)</h3><p>This feature allows for dynamically updating the maximum number of storage volumes a node can handle. Without this feature, volume limits are essentially immutable when a node first joins the cluster. If the environment changes—for example, if you attach a new network interface (ENI) that shares a hardware \"slot\" with your storage—OpenShift Container Platform does not recognize it has fewer slots available for disks, leading to pods becoming stuck.</p><p>This feature is only supported on AWS Elastic Block Storage (EBS).</p><p>Mutable CSI node allocatable property is supported in OpenShift Container Platform 4.21 as a Technical Preview feature. To enable this feature, you need to enable Feature Gates.</p><p>For more information about enabling Technical Preview features, see <a href=\"#\">Feature Gates</a>.</p><h3>Reducing permissions while using the GCP PD CSI Driver Operator is generally available</h3><p>The default installation allows the Google Cloud Platform (GCP) persistent disk (PD) Container Storage Interface (CSI) Driver to impersonate any service account in the Google Cloud project. You can reduce the scope of permissions granted to the GCP PD CSI Driver service account in your Google Cloud project to only the required node service accounts.</p><p>For more information about this feature, see <a href=\"#\">Reducing permissions while using the GCP PD CSI Driver Operator</a>.</p><h3>Volume group snapshots API updated (Technical Preview)</h3><p>The API for the Container Storage Interface (CSI) volume group snapshot feature is updated from <b>v1beta1</b> to <b>v1beta2</b>.</p><p>This feature is supported at the Technical Preview level.</p><p>For more information, see <a href=\"#\">CSI volume group snapshots</a>.</p><h3>Updated release of the Secrets Store CSI Driver Operator</h3>\n<p>The Secrets Store CSI Driver Operator version v4.21 is now based on the upstream version v1.5.4 release of secrets-store-csi-driver.</p>\n\n<h3>1.3.20. Web console</h3>\n\n<h4>OLM v1 software catalog in the web console (Technology Preview)</h4>\n\n<p>With this update, you can preview the Operator Lifecycle Manager (OLM) v1 software catalog in the web console. Select <b>Ecosystem</b> → <b>Software Catalog</b> → <b>Operators</b> to preview this feature. To see the OLM (Classic) software catalog, click the <b>Enable OLM v1 (Tech Preview)</b> toggle.</p>\n\n<h2>1.4. NOTABLE TECHNICAL CHANGES</h2>\n\n<p>This section includes several technical changes for OpenShift Container Platform 4.21.</p>\n\n<h4>VMware vSphere 7 and VMware Cloud Foundation 4 end of general support</h4>\n\n<p>Broadcom has ended general support for VMware vSphere 7 and VMware Cloud Foundation (VCF) 4. If your existing OpenShift Container Platform cluster is running on either of these platforms, you must plan to migrate or upgrade your VMware infrastructure to a supported version. OpenShift Container Platform supports installation on vSphere 8 Update 1 or later, or VCF 5 or later.</p>\n\n<h4>Bare Metal Operator has read-only root filesystem by default</h4>\n\n<p>As of this update, the Bare Metal Operator has the <b>readOnlyRootFilesystem</b> security context setting enabled to meet common hardening recommendations.</p>\n\n<h4>MachineSets advertise node architecture for autoscaling</h4>\n\n<p>With this update, MachineSets advertise the architecture of their nodes, which allows the autoscaler to intelligently scale MachineSets in multi-architecture environments.</p>\n\n<h4>Dynamic Resource Allocation plugin is disabled in the NUMA-aware scheduler</h4>\n\n<p>With this update, the Dynamic Resource Allocation (DRA) is disabled so that the secondary scheduler, managed by <b>numaresources</b> operator, does not need to handle DRA resources. The Kubernetes project has recently enabled DRA by default, setting specific expectations on the scheduler-plugins project to support watching DRA resources. As a result, the OpenShift topology-aware scheduler (TAS) disables DRA plugin in its profile, and therefore ignores DRA-related custom resources (CRs) when making scheduling decisions.</p>\n\n<h2>1.5. DEPRECATED AND REMOVED FEATURES</h2>\n\n<h3>1.5.1. Images deprecated and removed features</h3>\n\n<p>Table 1.1. Images deprecated and removed tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Cluster Samples Operator</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.5.2. Installation deprecated and removed features</h3>\n\n<p>Table 1.2. Installation deprecated and removed tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>--cloud</b> parameter for <b>oc adm release extract</b></td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>CoreDNS wildcard queries for the <b>cluster.local</b> domain</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td><b>compute.platform.openstack.rootVolume.type</b> for RHOSP</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td><b>controlPlane.platform.openstack.rootVolume.type</b> for RHOSP</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td><b>ingressVIP</b> and <b>apiVIP</b> settings in the <b>install-config.yaml</b> file for installer-provisioned infrastructure clusters</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Package-based RHEL compute machines</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td><b>platform.aws.preserveBootstrapIgnition</b> parameter for Amazon Web Services (AWS)</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Installing a cluster on AWS with compute nodes in AWS Outposts</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Deploying managed clusters using <b>SiteConfig</b> and the GitOps ZTP workflow</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td>Installing a cluster using Fujitsu iRMC drivers on bare-metal machines</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.5.3. Machine Management deprecated and removed features</h3>\n\n<p>Table 1.3. Machine management deprecated and removed tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Confidential Computing with AMD Secure Encrypted Virtualization for Google Cloud</td>\n<td>General Availability</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Managing bare-metal machines using Fujitsu iRMC drivers</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.5.4. Networking deprecated and removed features</h3>\n\n<p>Table 1.4. Networking deprecated and removed tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>iptables</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.5.5. Node deprecated and removed features</h3>\n\n<p>Table 1.5. Node deprecated and removed tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>ImageContentSourcePolicy</b> (ICSP) objects</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Kubernetes topology label <b>failure-domain.beta.kubernetes.io/zone</b></td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Kubernetes topology label <b>failure-domain.beta.kubernetes.io/region</b></td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>cgroup v1</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.5.6. OpenShift CLI (oc) deprecated and removed features</h3>\n\n<p>Table 1.6. OpenShift CLI (oc) deprecated and removed tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>oc-mirror plugin v1</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Docker v2 registries</td>\n<td>General Availability</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.5.7. Operator lifecycle and development deprecated and removed features</h3>\n\n<p>Table 1.7. Operator lifecycle and development deprecated and removed tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Operator SDK</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td>Scaffolding tools for Ansible-based Operator projects</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td>Scaffolding tools for Helm-based Operator projects</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td>Scaffolding tools for Go-based Operator projects</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td>Scaffolding tools for Hybrid Helm-based Operator projects</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Scaffolding tools for Java-based Operator projects</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n<tr>\n<td>SQLite database format for Operator catalogs</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.5.8. Storage deprecated and removed features</h3>\n\n<p>Table 1.8. Storage deprecated and removed tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Shared Resources CSI Driver Operator</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.5.9. Web console deprecated and removed features</h3>\n\n<p>Table 1.9. Web console deprecated and removed tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>useModal</b> hook for dynamic plugin SDK</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n<tr>\n<td>Patternfly 4</td>\n<td>Removed</td>\n<td>Removed</td>\n<td>Removed</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.5.10. Workloads deprecated and removed features</h3>\n\n<p>Table 1.10. Workloads deprecated and removed tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>DeploymentConfig</b> objects</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n<td>Deprecated</td>\n</tr>\n</tbody>\n</table>\n\n<h2>1.6. DEPRECATED FEATURES</h2>\n\n<h3>Deprecation of Fujitsu Integrated Remote Management Controller (iRMC) driver for bare-metal machines</h3>\n\n<p>As of OpenShift Container Platform 4.21, support for the Fujitsu iRMC baseboard management controller (BMC) driver has been deprecated and will be removed in a future release. If a <b>BareMetalHost</b> resource contains a BMC address with <b>irmc://</b> as its URI scheme, the resource must be updated to use another BMC scheme, such as <b>redfish://</b> or <b>ipmi://</b>. Once support for this driver is removed, hosts that use <b>irmc://</b> URI schemes will become unmanageable.</p>\n\n<p>For information about updating the <b>BareMetalHost</b> resource, see <a href=\"#\">Editing a BareMetalHost resource</a>.</p>\n\n<h2>1.7. REMOVED FEATURES</h2>\n<p>This section includes removed features for OpenShift Container Platform 4.21.</p><h3>Swap memory support has been removed</h3><p>The ability to configure swap memory is no longer available in OpenShift Container Platform because using swap memory can prevent a node from properly safeguarding itself from failures.</p><h2>1.8. FIXED ISSUES</h2><p>The following issues are fixed for this release:</p><h3>1.8.1. Installer</h3><ul><li>• Before this update, the vSphere platform configuration lacked a validation check to prevent the simultaneous definition of both a custom virtual machine template and a <b>clusterOSImage</b> parameter. As a consequence, users could provide both parameters in the installation configuration, leading to ambiguity and potential deployment failures. With this release, the vSphere validation logic has been updated to ensure that template and <b>clusterOSImage</b> parameters are treated as mutually exclusive, returning a specific error message if both fields are populated. (<a href=\"#\">OCPBUGS-63584</a>)</li><li>• Before this update, a race condition occurred when multiple reconciliation loops or concurrent processes attempted to add a virtual machine (VM) to a vSphere Host Group simultaneously due to the provider lacking a check to see if the VM was already a member. Consequently, the vSphere API could return errors during the cluster reconfiguration task, leading to reconciliation failures and preventing the VM from being correctly associated with its designated zone or host group. With this release, the zonal logic has been updated to verify the VM's membership within the target host group before initiating a reconfiguration task, ensuring the operation is only performed if the VM is not already present. (<a href=\"#\">OCPBUGS-60765</a>)</li></ul><h3>1.8.2. Kube Controller Manager</h3><ul><li>• Before this update, <b>relatedObjects</b> in the <b>ClusterOperator</b> Custom Resource object omitted the <b>ClusterRoleBinding</b> object, resulting in incomplete debugging information. With this release, the related objects for <b>ClusterOperator</b> are expanded to include <b>ClusterRoleBinding</b>. As a result, the <b>kube-controller-manager ClusterRoleBinding</b> is included in the <b>ClusterOperator</b> output. (<a href=\"#\">OCPBUGS-65502</a>)</li></ul><h3>1.8.3. Kube Scheduler</h3><ul><li>• Before this update, the <b>ClusterOperator</b> object failed to reference <b>ClusterRoleBinding</b> in the <b>relatedObjects</b> array, and caused the <b>Kube-scheduler ClusterRoleBinding</b> to be omitted in the <b>ClusterOperator</b> output. As a consequence, debugging difficulties occurred. With this release, the <b>ClusterRoleBinding</b> for the <b>kube-scheduler</b> Operator is added to the <b>ClusterOperator relatedObjects</b>. (<a href=\"#\">OCPBUGS-65503</a>)</li></ul><h3>1.8.4. Networking</h3><ul><li>• Before this update, an incorrect private key containing certificate data caused HAProxy reload failure in OpenShift Container Platform 4.14. As a consequence, incorrect certificate configuration caused HAProxy router pods to fail reloads, which led to a partial outage. With this release, <b>haproxy</b> now validates certificates. As a result, router reload failures with invalid certificates are prevented. (<a href=\"#\">OCPBUGS-49769</a>)</li></ul>\n<ul>\n<li>• To maintain compatibility with Kubernetes 1.34, CoreDNS has been updated to version 1.13.1. This update resolves intermittent DNS resolution issues reported in previous versions and includes upstream performance fixes and security patches.</li>\n</ul>\n\n<h3>1.8.5. Clock state metrics degrade correctly after upstream clock loss</h3>\n\n<ul>\n<li>• Previously, when the upstream clock connection was lost and the clock entered the <b>unlocked</b> state, the <b>ptp4l</b> and <b>ts2phc</b> clock state metrics did not degrade as expected. This behavior caused inconsistent time synchronization state reporting. This issue has been fixed. When the upstream clock connection is lost, the <b>ptp4l</b> and <b>ts2phc</b> clock state metrics now degrade correctly, providing consistent time synchronization state reporting.</li>\n</ul>\n\n<h3>1.8.6. Node Tuning Operator</h3>\n\n<ul>\n<li>• Before this update, the Performance Profile Creator tool failed to analyze a <b>must-gather</b> archive if the archive contained a custom namespace directory ending with the suffix <b>nodes</b>. With this release, the PPC now correctly excludes the <b>namespaces</b> directory when processing the must-gather data to create a suggested <b>PerformanceProfile</b>. (<a href=\"#\">OCPBUGS-60218</a>)</li>\n</ul>\n\n<h3>1.8.7. OpenShift API Server</h3>\n\n<ul>\n<li>• Before this update, there was an incorrect error field path for <b>hostUsers</b> when validating a security context constraint. It was shown as <b>.spec.securityContext.hostUsers</b>, but <b>hostUsers</b> is not in the security context. With this release, the error field path is now <b>.spec.hostUsers</b>. (<a href=\"#\">OCPBUGS-65727</a>)</li>\n</ul>\n\n<h2>1.9. TECHNOLOGY PREVIEW FEATURES STATUS</h2>\n\n<p>Some features in this release are currently in Technology Preview. These experimental features are not intended for production use. Note the following scope of support on the Red Hat Customer Portal for these features:</p>\n\n<h3>Technology Preview Features Support Scope</h3>\n\n<p>In the following tables, features are marked with the following statuses:</p>\n\n<ul>\n<li>• <i>Not Available</i></li>\n<li>• <i>Technology Preview</i></li>\n<li>• <i>General Availability</i></li>\n<li>• <i>Deprecated</i></li>\n<li>• <i>Removed</i></li>\n</ul>\n\n<h3>1.9.1. Authentication and authorization Technology Preview features</h3>\n\n<p>Table 1.11. Authentication and authorization Technology Preview tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Pod security admission restricted enforcement</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Direct authentication with an external OIDC identity provider</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>KMS Plugin</td>\n<td>Not Available</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.9.2. Edge computing Technology Preview features</h3>\n\n<p>Table 1.12. Edge computing Technology Preview tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Accelerated provisioning of GitOps ZTP</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Enabling disk encryption with TPM and PCR protection</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Configuring a local arbiter node</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Configuring a two-node OpenShift Container Platform cluster with fencing</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.9.3. Extensions Technology Preview features</h3>\n\n<p>Table 1.13. Extensions Technology Preview tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Operator Lifecycle Manager (OLM) v1</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>OLM v1 runtime validation of container images using sigstore signatures</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>OLM v1 permissions preflight check for cluster extensions</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>OLM v1 deploying a cluster extension in a specified namespace</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>OLM v1 deploying a cluster extension that uses webhooks</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>OLM v1 software catalog</td>\n<td>Not Available</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.9.4. Installation Technology Preview features</h3>\n\n<p>Table 1.14. Installation Technology Preview tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Adding kernel modules to nodes with kvc</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Enabling NIC partitioning for SR-IOV devices</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>User-defined labels and tags for Google Cloud</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Installing a cluster on Alibaba Cloud by using Assisted Installer</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Installing a cluster on Microsoft Azure with confidential VMs</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Dedicated disk for etcd on Microsoft Azure</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Mount shared entitlements in BuildConfigs in RHEL</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>OpenShift zones support for vSphere host groups</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Selectable Cluster Inventory</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Installing a cluster on Google Cloud using the Cluster API implementation</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Enabling a user-provisioned DNS on Google Cloud</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Enabling a user-provisioned DNS on Microsoft Azure</td>\n<td>Not Available</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Enabling a user-provisioned DNS on Amazon Web Services (AWS)</td>\n<td>Not Available</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Installing a cluster using Google Cloud private and restricted API endpoints</td>\n<td>Not Available</td>\n<td>Not Available</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Installing a cluster on VMware vSphere with multiple network interface controllers</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Using bare metal as a service</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Running firmware upgrades for hosts in deployed bare metal clusters</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Changing the CVO log level</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.9.5. Machine Config Operator Technology Preview features</h3>\n\n<p>Table 1.15. Machine Config Operator Technology Preview tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Boot image management for Azure and vSphere</td>\n<td>Not available</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Boot image management for control plane nodes</td>\n<td>Not available</td>\n<td>Not available</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>image mode for OpenShift status reporting improvements</td>\n<td>Not available</td>\n<td>Not available</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Overriding storage or partition setup</td>\n<td>Not available</td>\n<td>Not available</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.9.6. Machine management Technology Preview features</h3>\n\n<p>Table 1.16. Machine management Technology Preview tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Managing machines with the Cluster API for Amazon Web Services</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Managing machines with the Cluster API for Google Cloud</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Managing machines with the Cluster API for IBM Power® Virtual Server</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Managing machines with the Cluster API for Microsoft Azure</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Managing machines with the Cluster API for RHOSP</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Managing machines with the Cluster API for VMware vSphere</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Managing machines with the Cluster API for bare metal</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Cloud controller manager for IBM Power® Virtual Server</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Adding multiple subnets to an existing VMware vSphere cluster by using compute machine sets</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n<td>Technology Preview</td>\n</tr>\n<tr>\n<td>Configuring Trusted Launch for Microsoft Azure virtual machines by using machine sets</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Configuring Azure confidential virtual machines by using machine sets</td>\n<td>General Availability</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td>Bare-metal nodes on VMware vSphere clusters</td>\n<td>Not Available</td>\n<td>Not Available</td>\n<td>Technology Preview</td>\n</tr>\n</tbody>\n</table>\n\n<h3>1.9.7. Multi-Architecture Technology Preview features</h3>\n\n<p>Table 1.17. Multi-Architecture Technology Preview tracker</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Feature</th>\n<th>4.19</th>\n<th>4.20</th>\n<th>4.21</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>kdump</b> on <b>arm64</b> architecture</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n<tr>\n<td><b>kdump</b> on <b>s390x</b> architecture</td>\n<td>Technology Preview</td>\n<td>General Availability</td>\n<td>General Availability</td>\n</tr>\n</tbody>\n</table>"},"page_stats":{"kind":"list like","value":[{"page_number":1,"error":false,"token_count":256,"num_chunks":5},{"page_number":2,"error":false,"token_count":48,"num_chunks":1},{"page_number":3,"error":false,"token_count":95,"num_chunks":2},{"page_number":4,"error":false,"token_count":605,"num_chunks":11},{"page_number":5,"error":false,"token_count":1789,"num_chunks":4},{"page_number":6,"error":false,"token_count":1757,"num_chunks":3},{"page_number":7,"error":false,"token_count":110,"num_chunks":2},{"page_number":8,"error":false,"token_count":1306,"num_chunks":16},{"page_number":9,"error":false,"token_count":1354,"num_chunks":22},{"page_number":10,"error":false,"token_count":1327,"num_chunks":20},{"page_number":11,"error":false,"token_count":1438,"num_chunks":24},{"page_number":12,"error":false,"token_count":1515,"num_chunks":22},{"page_number":13,"error":false,"token_count":1476,"num_chunks":22},{"page_number":14,"error":false,"token_count":1466,"num_chunks":19},{"page_number":15,"error":false,"token_count":1512,"num_chunks":23},{"page_number":16,"error":false,"token_count":1291,"num_chunks":20},{"page_number":17,"error":false,"token_count":1530,"num_chunks":21},{"page_number":18,"error":false,"token_count":1276,"num_chunks":19},{"page_number":19,"error":false,"token_count":1299,"num_chunks":19},{"page_number":20,"error":false,"token_count":1426,"num_chunks":24},{"page_number":21,"error":false,"token_count":1448,"num_chunks":22},{"page_number":22,"error":false,"token_count":1072,"num_chunks":8},{"page_number":23,"error":false,"token_count":1289,"num_chunks":12},{"page_number":24,"error":false,"token_count":1401,"num_chunks":17},{"page_number":25,"error":false,"token_count":1265,"num_chunks":15},{"page_number":26,"error":false,"token_count":1276,"num_chunks":17},{"page_number":27,"error":false,"token_count":1072,"num_chunks":9},{"page_number":28,"error":false,"token_count":1011,"num_chunks":6},{"page_number":29,"error":false,"token_count":934,"num_chunks":8},{"page_number":30,"error":false,"token_count":1049,"num_chunks":6}],"string":"[\n {\n \"page_number\": 1,\n \"error\": false,\n \"token_count\": 256,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 2,\n \"error\": false,\n \"token_count\": 48,\n \"num_chunks\": 1\n },\n {\n \"page_number\": 3,\n \"error\": false,\n \"token_count\": 95,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 4,\n \"error\": false,\n \"token_count\": 605,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 5,\n \"error\": false,\n \"token_count\": 1789,\n \"num_chunks\": 4\n },\n {\n \"page_number\": 6,\n \"error\": false,\n \"token_count\": 1757,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 7,\n \"error\": false,\n \"token_count\": 110,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 8,\n \"error\": false,\n \"token_count\": 1306,\n \"num_chunks\": 16\n },\n {\n \"page_number\": 9,\n \"error\": false,\n \"token_count\": 1354,\n \"num_chunks\": 22\n },\n {\n \"page_number\": 10,\n \"error\": false,\n \"token_count\": 1327,\n \"num_chunks\": 20\n },\n {\n \"page_number\": 11,\n \"error\": false,\n \"token_count\": 1438,\n \"num_chunks\": 24\n },\n {\n \"page_number\": 12,\n \"error\": false,\n \"token_count\": 1515,\n \"num_chunks\": 22\n },\n {\n \"page_number\": 13,\n \"error\": false,\n \"token_count\": 1476,\n \"num_chunks\": 22\n },\n {\n \"page_number\": 14,\n \"error\": false,\n \"token_count\": 1466,\n \"num_chunks\": 19\n },\n {\n \"page_number\": 15,\n \"error\": false,\n \"token_count\": 1512,\n \"num_chunks\": 23\n },\n {\n \"page_number\": 16,\n \"error\": false,\n \"token_count\": 1291,\n \"num_chunks\": 20\n },\n {\n \"page_number\": 17,\n \"error\": false,\n \"token_count\": 1530,\n \"num_chunks\": 21\n },\n {\n \"page_number\": 18,\n \"error\": false,\n \"token_count\": 1276,\n \"num_chunks\": 19\n },\n {\n \"page_number\": 19,\n \"error\": false,\n \"token_count\": 1299,\n \"num_chunks\": 19\n },\n {\n \"page_number\": 20,\n \"error\": false,\n \"token_count\": 1426,\n \"num_chunks\": 24\n },\n {\n \"page_number\": 21,\n \"error\": false,\n \"token_count\": 1448,\n \"num_chunks\": 22\n },\n {\n \"page_number\": 22,\n \"error\": false,\n \"token_count\": 1072,\n \"num_chunks\": 8\n },\n {\n \"page_number\": 23,\n \"error\": false,\n \"token_count\": 1289,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 24,\n \"error\": false,\n \"token_count\": 1401,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 25,\n \"error\": false,\n \"token_count\": 1265,\n \"num_chunks\": 15\n },\n {\n \"page_number\": 26,\n \"error\": false,\n \"token_count\": 1276,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 27,\n \"error\": false,\n \"token_count\": 1072,\n \"num_chunks\": 9\n },\n {\n \"page_number\": 28,\n \"error\": false,\n \"token_count\": 1011,\n \"num_chunks\": 6\n },\n {\n \"page_number\": 29,\n \"error\": false,\n \"token_count\": 934,\n \"num_chunks\": 8\n },\n {\n \"page_number\": 30,\n \"error\": false,\n \"token_count\": 1049,\n \"num_chunks\": 6\n }\n]","isConversational":false}}},{"rowIdx":91,"cells":{"source_id":{"kind":"string","value":"OpenShift_Container_Platform-4.21-Role_APIs-en-US"},"pdf_url":{"kind":"string","value":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/role_apis/OpenShift_Container_Platform-4.21-Role_APIs-en-US.pdf"},"status":{"kind":"string","value":"success"},"processed_at":{"kind":"string","value":"2026-04-15T18:32:40.991805+00:00"},"elapsed_seconds":{"kind":"number","value":59.43,"string":"59.43"},"num_pages":{"kind":"number","value":46,"string":"46"},"num_pages_processed":{"kind":"number","value":30,"string":"30"},"max_pages_per_paper":{"kind":"number","value":30,"string":"30"},"pdf_exceeds_page_limit":{"kind":"bool","value":true,"string":"true"},"failed_pages":{"kind":"list like","value":[],"string":"[]","isConversational":false},"prompt_type":{"kind":"string","value":"ocr_layout"},"model_id":{"kind":"string","value":"datalab-to/chandra-ocr-2"},"script_version":{"kind":"timestamp","value":"2026-04-15T00:00:00","string":"2026-04-15T00:00:00"},"markdown":{"kind":"string","value":"# OpenShift Container Platform 4.21\n\n## Role APIs\n\nReference guide for role APIs# OpenShift Container Platform 4.21 Role APIs\n\n---\n\nReference guide for role APIs## Legal Notice\n\nCopyright © Red Hat.\n\nExcept as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.\n\nRed Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.\n\nRed Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.\n\nLinux ® is the registered trademark of Linus Torvalds in the United States and other countries.\n\nXFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.\n\nThe OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.\n\nAll other trademarks are the property of their respective owners.\n\n## Abstract\n\nThis document describes the OpenShift Container Platform role API objects and their detailed specifications.# Table of Contents\n\n<table>\n<tr>\n<td><b>CHAPTER 1. ROLE APIS</b> .....</td>\n<td><b>3</b></td>\n</tr>\n<tr>\n<td> 1.1. CLUSTERROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]</td>\n<td>3</td>\n</tr>\n<tr>\n<td> 1.2. CLUSTERROLE [AUTHORIZATION.OPENSHIFT.IO/V1]</td>\n<td>3</td>\n</tr>\n<tr>\n<td> 1.3. ROLEBINDINGRESTRICTION [AUTHORIZATION.OPENSHIFT.IO/V1]</td>\n<td>3</td>\n</tr>\n<tr>\n<td> 1.4. ROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]</td>\n<td>3</td>\n</tr>\n<tr>\n<td> 1.5. ROLE [AUTHORIZATION.OPENSHIFT.IO/V1]</td>\n<td>4</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. CLUSTERROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>5</b></td>\n</tr>\n<tr>\n<td> 2.1. SPECIFICATION</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 2.2. API ENDPOINTS</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 2.2.1. /apis/authorization.openshift.io/v1/clusterrulebindings</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 2.2.2. /apis/authorization.openshift.io/v1/clusterrulebindings/{name}</td>\n<td>8</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. CLUSTERROLE [AUTHORIZATION.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>12</b></td>\n</tr>\n<tr>\n<td> 3.1. SPECIFICATION</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 3.1.1. .rules</td>\n<td>13</td>\n</tr>\n<tr>\n<td> 3.1.2. .rules[]</td>\n<td>13</td>\n</tr>\n<tr>\n<td> 3.2. API ENDPOINTS</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 3.2.1. /apis/authorization.openshift.io/v1/clusterrules</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 3.2.2. /apis/authorization.openshift.io/v1/clusterrules/{name}</td>\n<td>16</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. ROLEBINDINGRESTRICTION [AUTHORIZATION.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>20</b></td>\n</tr>\n<tr>\n<td> 4.1. SPECIFICATION</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 4.1.1. .spec</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 4.2. API ENDPOINTS</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 4.2.1. /apis/authorization.openshift.io/v1/rolebindingrestrictions</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 4.2.2. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindingrestrictions</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 4.2.3. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindingrestrictions/{name}</td>\n<td>23</td>\n</tr>\n<tr>\n<td><b>CHAPTER 5. ROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>27</b></td>\n</tr>\n<tr>\n<td> 5.1. SPECIFICATION</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 5.2. API ENDPOINTS</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 5.2.1. /apis/authorization.openshift.io/v1/rolebindings</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 5.2.2. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindings</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 5.2.3. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindings/{name}</td>\n<td>31</td>\n</tr>\n<tr>\n<td><b>CHAPTER 6. ROLE [AUTHORIZATION.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>35</b></td>\n</tr>\n<tr>\n<td> 6.1. SPECIFICATION</td>\n<td>35</td>\n</tr>\n<tr>\n<td> 6.1.1. .rules</td>\n<td>36</td>\n</tr>\n<tr>\n<td> 6.1.2. .rules[]</td>\n<td>36</td>\n</tr>\n<tr>\n<td> 6.2. API ENDPOINTS</td>\n<td>37</td>\n</tr>\n<tr>\n<td> 6.2.1. /apis/authorization.openshift.io/v1/roles</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 6.2.2. /apis/authorization.openshift.io/v1/namespaces/{namespace}/roles</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 6.2.3. /apis/authorization.openshift.io/v1/namespaces/{namespace}/roles/{name}</td>\n<td>39</td>\n</tr>\n</table>## CHAPTER 1. ROLE APIS\n\n### 1.1. CLUSTERROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]\n\n#### Description\n\nClusterRoleBinding references a ClusterRole, but not contain it. It can reference any ClusterRole in the same namespace or in the global namespace. It adds who information via (Users and Groups) OR Subjects and namespace information by which namespace it exists in. ClusterRoleBindings in a given namespace only have effect in that namespace (excepting the master namespace which has power in all namespaces).\n\nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n#### Type\n\n**object**\n\n### 1.2. CLUSTERROLE [AUTHORIZATION.OPENSHIFT.IO/V1]\n\n#### Description\n\nClusterRole is a logical grouping of PolicyRules that can be referenced as a unit by ClusterRoleBindings.\n\nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n#### Type\n\n**object**\n\n### 1.3. ROLEBINDINGRESTRICTION [AUTHORIZATION.OPENSHIFT.IO/V1]\n\n#### Description\n\nRoleBindingRestriction is an object that can be matched against a subject (user, group, or service account) to determine whether rolebindings on that subject are allowed in the namespace to which the RoleBindingRestriction belongs. If any one of those RoleBindingRestriction objects matches a subject, rolebindings on that subject in the namespace are allowed.\n\nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n#### Type\n\n**object**\n\n### 1.4. ROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]\n\n#### Description\n\nRoleBinding references a Role, but not contain it. It can reference any Role in the same namespace or in the global namespace. It adds who information via (Users and Groups) OR Subjects and namespace information by which namespace it exists in. RoleBindings in a given namespace only have effect in that namespace (excepting the master namespace which has power in all namespaces).Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n**Type**\n\n**object**\n\n## 1.5. ROLE [AUTHORIZATION.OPENSHIFT.IO/V1]\n\n**Description**\n\nRole is a logical grouping of PolicyRules that can be referenced as a unit by RoleBindings. \nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n**Type**\n\n**object**## CHAPTER 2. CLUSTERROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]\n\n### Description\n\nClusterRoleBinding references a ClusterRole, but not contain it. It can reference any ClusterRole in the same namespace or in the global namespace. It adds who information via (Users and Groups) OR Subjects and namespace information by which namespace it exists in. ClusterRoleBindings in a given namespace only have effect in that namespace (excepting the master namespace which has power in all namespaces).\n\nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n### Type\n\n**object**\n\n### Required\n\n- • **subjects**\n- • **roleRef**\n\n## 2.1. SPECIFICATION\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>groupNames</b></td>\n<td><b>array (string)</b></td>\n<td>GroupNames holds all the groups directly bound to the role. This field should only be specified when supporting legacy clients and servers. See Subjects for further details.</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info:<br/><a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta_v2</b></td>\n<td>metadata is the standard object's metadata. More info:<br/><a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</a></td>\n</tr>\n<tr>\n<td><b>roleRef</b></td>\n<td><b>ObjectReference</b></td>\n<td>RoleRef can only reference the current namespace and the global namespace. If the ClusterRoleRef cannot be resolved, the Authorizer must return an error. Since Policy is a singleton, this is sufficient knowledge to locate a role.</td>\n</tr>\n<tr>\n<td><b>subjects</b></td>\n<td><b>array (ObjectReference)</b></td>\n<td>Subjects hold object references to authorize with this rule. This field is ignored if UserNames or GroupNames are specified to support legacy clients and servers. Thus newer clients that do not need to support backwards compatibility should send only fully qualified Subjects and should omit the UserNames and GroupNames fields. Clients that need to support backwards compatibility can use this field to build the UserNames and GroupNames.</td>\n</tr>\n<tr>\n<td><b>userNames</b></td>\n<td><b>array (string)</b></td>\n<td>UserNames holds all the usernames directly bound to the role. This field should only be specified when supporting legacy clients and servers. See Subjects for further details.</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n</table>\n\n## 2.2. API ENDPOINTS\n\nThe following API endpoints are available:\n\n- • **/apis/authorization.openshift.io/v1/clusterrulebindings**\n - ◦ **GET**: list objects of kind ClusterRoleBinding\n - ◦ **POST**: create a ClusterRoleBinding\n- • **/apis/authorization.openshift.io/v1/clusterrulebindings/{name}**\n - ◦ **DELETE**: delete a ClusterRoleBinding\n - ◦ **GET**: read the specified ClusterRoleBinding\n - ◦ **PATCH**: partially update the specified ClusterRoleBinding\n - ◦ **PUT**: replace the specified ClusterRoleBinding\n\n### 2.2.1. /apis/authorization.openshift.io/v1/clusterrulebindings\n\nHTTP method\n\n**GET**\n\nDescription\n\nlist objects of kind ClusterRoleBinding\n\nTable 2.1. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRoleBindingList</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**POST**\n\nDescription\n\ncreate a ClusterRoleBinding\n\nTable 2.2. Query parameters<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 2.3. Body parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterRoleBinding</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nTable 2.4. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.2. /apis/authorization.openshift.io/v1/clusterrolebindings/{name}\n\nTable 2.5. Global path parameters<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the ClusterRoleBinding</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**DELETE**\n\nDescription\n\ndelete a ClusterRoleBinding\n\nTable 2.6. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n\nTable 2.7. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status_v3</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>Status_v3</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**GET**\n\nDescription\n\nread the specified ClusterRoleBinding\n\nTable 2.8. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**PATCH**\n\nDescriptionpartially update the specified ClusterRoleBinding\n\nTable 2.9. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 2.10. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n#### HTTP method\n\n##### PUT\n\n#### Description\n\nreplace the specified ClusterRoleBinding\n\nTable 2.11. Query parameters<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 2.12. Body parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterRoleBinding</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nTable 2.13. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>## CHAPTER 3. CLUSTERROLE [AUTHORIZATION.OPENSHIFT.IO/V1]\n\n### Description\n\nClusterRole is a logical grouping of PolicyRules that can be referenced as a unit by ClusterRoleBindings.\n\nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n### Type\n\n**object**\n\n### Required\n\n- • **rules**\n\n## 3.1. SPECIFICATION\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>aggregationRule</b></td>\n<td><b>AggregationRule_v2</b></td>\n<td>AggregationRule is an optional field that describes how to build the Rules for this ClusterRole. If AggregationRule is set, then the Rules are controller managed and direct changes to Rules will be stomped by the controller.</td>\n</tr>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta_v2</b></td>\n<td>metadata is the standard object's metadata. More info:<br/><a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</a></td>\n</tr>\n<tr>\n<td><b>rules</b></td>\n<td><b>array</b></td>\n<td>Rules holds all the PolicyRules for this ClusterRole</td>\n</tr>\n<tr>\n<td><b>rules[]</b></td>\n<td><b>object</b></td>\n<td>PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.</td>\n</tr>\n</tbody>\n</table>\n\n### 3.1.1. .rules\n\n#### Description\n\nRules holds all the PolicyRules for this ClusterRole\n\n#### Type\n\n**array**\n\n### 3.1.2. .rules[]\n\n#### Description\n\nPolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.\n\n#### Type\n\n**object**\n\n#### Required\n\n- • **verbs**\n- • **resources**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiGroups</b></td>\n<td><b>array (string)</b></td>\n<td>APIGroups is the name of the APIGroup that contains the resources. If this field is empty, then both Kubernetes and origin API groups are assumed. That means that if an action is requested against one of the enumerated resources in either the Kubernetes or the origin API group, the request will be allowed</td>\n</tr>\n<tr>\n<td><b>attributeRestrictions</b></td>\n<td><b>RawExtension</b></td>\n<td>AttributeRestrictions will vary depending on what the Authorizer/AuthorizationAttributeBuilder pair supports. If the Authorizer does not recognize how to handle the AttributeRestrictions, the Authorizer should report an error.</td>\n</tr>\n<tr>\n<td><b>nonResourceURLs</b></td>\n<td><b>array (string)</b></td>\n<td>NonResourceURLsSlice is a set of partial URLs that a user should have access to. *s are allowed, but only as the full, final step in the path. This name is intentionally different than the internal type so that the DefaultConvert works nicely and because the ordering may be different.</td>\n</tr>\n<tr>\n<td><b>resourceNames</b></td>\n<td><b>array (string)</b></td>\n<td>ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed.</td>\n</tr>\n<tr>\n<td><b>resources</b></td>\n<td><b>array (string)</b></td>\n<td>Resources is a list of resources this rule applies to. ResourceAll represents all resources.</td>\n</tr>\n<tr>\n<td><b>verbs</b></td>\n<td><b>array (string)</b></td>\n<td>Verbs is a list of Verbs that apply to ALL the ResourceKinds and AttributeRestrictions contained in this rule. VerbAll represents all kinds.</td>\n</tr>\n</tbody>\n</table>\n\n## 3.2. API ENDPOINTS\n\nThe following API endpoints are available:- • **/apis/authorization.openshift.io/v1/cluserroles**\n - ◦ **GET**: list objects of kind ClusterRole\n - ◦ **POST**: create a ClusterRole\n- • **/apis/authorization.openshift.io/v1/cluserroles/{name}**\n - ◦ **DELETE**: delete a ClusterRole\n - ◦ **GET**: read the specified ClusterRole\n - ◦ **PATCH**: partially update the specified ClusterRole\n - ◦ **PUT**: replace the specified ClusterRole\n\n### 3.2.1. /apis/authorization.openshift.io/v1/cluserroles\n\nHTTP method\n\n**GET**\n\nDescription\n\nlist objects of kind ClusterRole\n\nTable 3.1. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRoleList</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**POST**\n\nDescription\n\ncreate a ClusterRole\n\nTable 3.2. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are:\n<ul>\n<li>- Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23.</li>\n<li>- Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+.</li>\n<li>- Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>\n\nTable 3.3. Body parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterRole</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nTable 3.4. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### 3.2.2. /apis/authorization.openshift.io/v1/cluserroles/{name}\n\nTable 3.5. Global path parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the ClusterRole</td>\n</tr>\n</tbody>\n</table>**HTTP method****DELETE****Description**\n\ndelete a ClusterRole\n\n**Table 3.6. Query parameters**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n\n**Table 3.7. HTTP responses**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status_v3</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>Status_v3</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n**HTTP method****GET****Description**\n\nread the specified ClusterRole\n\n**Table 3.8. HTTP responses**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n**HTTP method****PATCH****Description**\n\npartially update the specified ClusterRole\n\n**Table 3.9. Query parameters**<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 3.10. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n**HTTP method****PUT****Description**\n\nreplace the specified ClusterRole\n\nTable 3.11. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 3.12. Body parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterRole</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nTable 3.13. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>## CHAPTER 4. ROLEBINDINGRESTRICTION [AUTHORIZATION.OPENSHIFT.IO/V1]\n\n### Description\n\nRoleBindingRestriction is an object that can be matched against a subject (user, group, or service account) to determine whether rolebindings on that subject are allowed in the namespace to which the RoleBindingRestriction belongs. If any one of those RoleBindingRestriction objects matches a subject, rolebindings on that subject in the namespace are allowed.\n\nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n### Type\n\n**object**\n\n### 4.1. SPECIFICATION\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta</b></td>\n<td>Standard object's metadata. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</a></td>\n</tr>\n<tr>\n<td><b>spec</b></td>\n<td><b>object</b></td>\n<td>spec defines the matcher.</td>\n</tr>\n</tbody>\n</table>### 4.1.1. .spec\n\n#### Description\n\nspec defines the matcher.\n\n#### Type\n\n**object**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>grouprestriction</b></td>\n<td>```</td>\n<td>grouprestriction matches against group subjects.</td>\n</tr>\n<tr>\n<td><b>serviceaccountrestriction</b></td>\n<td>```</td>\n<td>serviceaccountrestriction matches against service-account subjects.</td>\n</tr>\n<tr>\n<td><b>userrestriction</b></td>\n<td>```</td>\n<td>userrestriction matches against user subjects.</td>\n</tr>\n</tbody>\n</table>\n\n## 4.2. API ENDPOINTS\n\nThe following API endpoints are available:\n\n- • **/apis/authorization.openshift.io/v1/rolebindingrestrictions**\n - ◦ **GET**: list objects of kind RoleBindingRestriction\n- • **/apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindingrestrictions**\n - ◦ **DELETE**: delete collection of RoleBindingRestriction\n - ◦ **GET**: list objects of kind RoleBindingRestriction\n - ◦ **POST**: create a RoleBindingRestriction\n- • **/apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindingrestrictions/{name}**\n - ◦ **DELETE**: delete a RoleBindingRestriction\n - ◦ **GET**: read the specified RoleBindingRestriction\n - ◦ **PATCH**: partially update the specified RoleBindingRestriction\n - ◦ **PUT**: replace the specified RoleBindingRestriction\n\n### 4.2.1. /apis/authorization.openshift.io/v1/rolebindingrestrictions\n\n#### HTTP method\n\n**GET**\n\n#### Descriptionlist objects of kind RoleBindingRestriction\n\nTable 4.1. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>RoleBindingRestrictionList</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n## 4.2.2. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindingrestr\n\nHTTP method\n\n**DELETE**\n\nDescription\n\ndelete collection of RoleBindingRestriction\n\nTable 4.2. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**GET**\n\nDescription\n\nlist objects of kind RoleBindingRestriction\n\nTable 4.3. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>RoleBindingRestrictionList</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**POST**\n\nDescription\n\ncreate a RoleBindingRestriction\n\nTable 4.4. Query parameters<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 4.5. Body parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>RoleBindingRestriction</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nTable 4.6. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### 4.2.3. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindingrestrTable 4.7. Global path parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the RoleBindingRestriction</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**DELETE**\n\nDescription\n\ndelete a RoleBindingRestriction\n\nTable 4.8. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n\nTable 4.9. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**GET**\n\nDescription\n\nread the specified RoleBindingRestriction\n\nTable 4.10. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**PATCH****Description**\n\npartially update the specified RoleBindingRestriction\n\n**Table 4.11. Query parameters**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\n**Table 4.12. HTTP responses**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n**HTTP method**\n\n**PUT**\n\n**Description**\n\nreplace the specified RoleBindingRestriction\n\n**Table 4.13. Query parameters**<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 4.14. Body parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>RoleBindingRestriction</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nTable 4.15. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>"},"html":{"kind":"string","value":"<h1>OpenShift Container Platform 4.21</h1><h2>Role APIs</h2><p>Reference guide for role APIs</p><h1>OpenShift Container Platform 4.21 Role APIs</h1><hr/><p>Reference guide for role APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.</p><p>Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.</p><p>Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.</p><p>Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.</p><p>XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.</p><p>The OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.</p><p>All other trademarks are the property of their respective owners.</p><h2>Abstract</h2><p>This document describes the OpenShift Container Platform role API objects and their detailed specifications.</p>\n<h1>Table of Contents</h1>\n\n<table>\n<tr>\n<td><b>CHAPTER 1. ROLE APIS</b> .....</td>\n<td><b>3</b></td>\n</tr>\n<tr>\n<td> 1.1. CLUSTERROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]</td>\n<td>3</td>\n</tr>\n<tr>\n<td> 1.2. CLUSTERROLE [AUTHORIZATION.OPENSHIFT.IO/V1]</td>\n<td>3</td>\n</tr>\n<tr>\n<td> 1.3. ROLEBINDINGRESTRICTION [AUTHORIZATION.OPENSHIFT.IO/V1]</td>\n<td>3</td>\n</tr>\n<tr>\n<td> 1.4. ROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]</td>\n<td>3</td>\n</tr>\n<tr>\n<td> 1.5. ROLE [AUTHORIZATION.OPENSHIFT.IO/V1]</td>\n<td>4</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. CLUSTERROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>5</b></td>\n</tr>\n<tr>\n<td> 2.1. SPECIFICATION</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 2.2. API ENDPOINTS</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 2.2.1. /apis/authorization.openshift.io/v1/clusterrulebindings</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 2.2.2. /apis/authorization.openshift.io/v1/clusterrulebindings/{name}</td>\n<td>8</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. CLUSTERROLE [AUTHORIZATION.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>12</b></td>\n</tr>\n<tr>\n<td> 3.1. SPECIFICATION</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 3.1.1. .rules</td>\n<td>13</td>\n</tr>\n<tr>\n<td> 3.1.2. .rules[]</td>\n<td>13</td>\n</tr>\n<tr>\n<td> 3.2. API ENDPOINTS</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 3.2.1. /apis/authorization.openshift.io/v1/clusterrules</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 3.2.2. /apis/authorization.openshift.io/v1/clusterrules/{name}</td>\n<td>16</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. ROLEBINDINGRESTRICTION [AUTHORIZATION.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>20</b></td>\n</tr>\n<tr>\n<td> 4.1. SPECIFICATION</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 4.1.1. .spec</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 4.2. API ENDPOINTS</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 4.2.1. /apis/authorization.openshift.io/v1/rolebindingrestrictions</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 4.2.2. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindingrestrictions</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 4.2.3. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindingrestrictions/{name}</td>\n<td>23</td>\n</tr>\n<tr>\n<td><b>CHAPTER 5. ROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>27</b></td>\n</tr>\n<tr>\n<td> 5.1. SPECIFICATION</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 5.2. API ENDPOINTS</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 5.2.1. /apis/authorization.openshift.io/v1/rolebindings</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 5.2.2. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindings</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 5.2.3. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindings/{name}</td>\n<td>31</td>\n</tr>\n<tr>\n<td><b>CHAPTER 6. ROLE [AUTHORIZATION.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>35</b></td>\n</tr>\n<tr>\n<td> 6.1. SPECIFICATION</td>\n<td>35</td>\n</tr>\n<tr>\n<td> 6.1.1. .rules</td>\n<td>36</td>\n</tr>\n<tr>\n<td> 6.1.2. .rules[]</td>\n<td>36</td>\n</tr>\n<tr>\n<td> 6.2. API ENDPOINTS</td>\n<td>37</td>\n</tr>\n<tr>\n<td> 6.2.1. /apis/authorization.openshift.io/v1/roles</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 6.2.2. /apis/authorization.openshift.io/v1/namespaces/{namespace}/roles</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 6.2.3. /apis/authorization.openshift.io/v1/namespaces/{namespace}/roles/{name}</td>\n<td>39</td>\n</tr>\n</table>\n<h2>CHAPTER 1. ROLE APIS</h2><h3>1.1. CLUSTERROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]</h3><h4>Description</h4><p>ClusterRoleBinding references a ClusterRole, but not contain it. It can reference any ClusterRole in the same namespace or in the global namespace. It adds who information via (Users and Groups) OR Subjects and namespace information by which namespace it exists in. ClusterRoleBindings in a given namespace only have effect in that namespace (excepting the master namespace which has power in all namespaces).</p><p>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p><h4>Type</h4><p><b>object</b></p><h3>1.2. CLUSTERROLE [AUTHORIZATION.OPENSHIFT.IO/V1]</h3><h4>Description</h4><p>ClusterRole is a logical grouping of PolicyRules that can be referenced as a unit by ClusterRoleBindings.</p><p>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p><h4>Type</h4><p><b>object</b></p><h3>1.3. ROLEBINDINGRESTRICTION [AUTHORIZATION.OPENSHIFT.IO/V1]</h3><h4>Description</h4><p>RoleBindingRestriction is an object that can be matched against a subject (user, group, or service account) to determine whether rolebindings on that subject are allowed in the namespace to which the RoleBindingRestriction belongs. If any one of those RoleBindingRestriction objects matches a subject, rolebindings on that subject in the namespace are allowed.</p><p>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p><h4>Type</h4><p><b>object</b></p><h3>1.4. ROLEBINDING [AUTHORIZATION.OPENSHIFT.IO/V1]</h3><h4>Description</h4><p>RoleBinding references a Role, but not contain it. It can reference any Role in the same namespace or in the global namespace. It adds who information via (Users and Groups) OR Subjects and namespace information by which namespace it exists in. RoleBindings in a given namespace only have effect in that namespace (excepting the master namespace which has power in all namespaces).</p><p>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p><p><b>Type</b></p><p><b>object</b></p><h2>1.5. ROLE [AUTHORIZATION.OPENSHIFT.IO/V1]</h2><p><b>Description</b></p><p>Role is a logical grouping of PolicyRules that can be referenced as a unit by RoleBindings.<br/>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p><p><b>Type</b></p><p><b>object</b></p>\n<h2>CHAPTER 2. CLUSTERROLEBINDING<br/>[AUTHORIZATION.OPENSHIFT.IO/V1]</h2>\n\n<h3>Description</h3>\n\n<p>ClusterRoleBinding references a ClusterRole, but not contain it. It can reference any ClusterRole in the same namespace or in the global namespace. It adds who information via (Users and Groups) OR Subjects and namespace information by which namespace it exists in. ClusterRoleBindings in a given namespace only have effect in that namespace (excepting the master namespace which has power in all namespaces).</p>\n\n<p>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p>\n\n<h3>Type</h3>\n\n<p><b>object</b></p>\n\n<h3>Required</h3>\n\n<ul>\n<li>• <b>subjects</b></li>\n<li>• <b>roleRef</b></li>\n</ul>\n\n<h2>2.1. SPECIFICATION</h2>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>groupNames</b></td>\n<td><b>array (string)</b></td>\n<td>GroupNames holds all the groups directly bound to the role. This field should only be specified when supporting legacy clients and servers. See Subjects for further details.</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info:<br/><a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta_v2</b></td>\n<td>metadata is the standard object's metadata. More info:<br/><a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</a></td>\n</tr>\n<tr>\n<td><b>roleRef</b></td>\n<td><b>ObjectReference</b></td>\n<td>RoleRef can only reference the current namespace and the global namespace. If the ClusterRoleRef cannot be resolved, the Authorizer must return an error. Since Policy is a singleton, this is sufficient knowledge to locate a role.</td>\n</tr>\n<tr>\n<td><b>subjects</b></td>\n<td><b>array (ObjectReference)</b></td>\n<td>Subjects hold object references to authorize with this rule. This field is ignored if UserNames or GroupNames are specified to support legacy clients and servers. Thus newer clients that do not need to support backwards compatibility should send only fully qualified Subjects and should omit the UserNames and GroupNames fields. Clients that need to support backwards compatibility can use this field to build the UserNames and GroupNames.</td>\n</tr>\n<tr>\n<td><b>userNames</b></td>\n<td><b>array (string)</b></td>\n<td>UserNames holds all the usernames directly bound to the role. This field should only be specified when supporting legacy clients and servers. See Subjects for further details.</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n</table>\n\n<h2>2.2. API ENDPOINTS</h2>\n\n<p>The following API endpoints are available:</p>\n\n<ul style=\"list-style-type: none;\">\n<li>• <b>/apis/authorization.openshift.io/v1/clusterrulebindings</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>GET</b>: list objects of kind ClusterRoleBinding</li>\n<li>◦ <b>POST</b>: create a ClusterRoleBinding</li>\n</ul>\n</li>\n<li>• <b>/apis/authorization.openshift.io/v1/clusterrulebindings/{name}</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>DELETE</b>: delete a ClusterRoleBinding</li>\n<li>◦ <b>GET</b>: read the specified ClusterRoleBinding</li>\n<li>◦ <b>PATCH</b>: partially update the specified ClusterRoleBinding</li>\n<li>◦ <b>PUT</b>: replace the specified ClusterRoleBinding</li>\n</ul>\n</li>\n</ul>\n\n<h3>2.2.1. /apis/authorization.openshift.io/v1/clusterrulebindings</h3>\n\n<p>HTTP method</p>\n\n<p><b>GET</b></p>\n\n<p>Description</p>\n\n<p>list objects of kind ClusterRoleBinding</p>\n\n<p>Table 2.1. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRoleBindingList</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>POST</b></p>\n\n<p>Description</p>\n\n<p>create a ClusterRoleBinding</p>\n\n<p>Table 2.2. Query parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\nTable 2.3. Body parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterRoleBinding</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\nTable 2.4. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.2. /apis/authorization.openshift.io/v1/clusterrolebindings/{name}</h3>\nTable 2.5. Global path parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the ClusterRoleBinding</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>DELETE</b></p>\n\n<p>Description</p>\n\n<p>delete a ClusterRoleBinding</p>\n\n<p>Table 2.6. Query parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n\n<p>Table 2.7. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status_v3</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>Status_v3</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>GET</b></p>\n\n<p>Description</p>\n\n<p>read the specified ClusterRoleBinding</p>\n\n<p>Table 2.8. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>PATCH</b></p>\n\n<p>Description</p>\n\n<p>partially update the specified ClusterRoleBinding</p>\n\n<p>Table 2.9. Query parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\n<p>Table 2.10. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h4>HTTP method</h4>\n\n<h5>PUT</h5>\n\n<h4>Description</h4>\n\n<p>replace the specified ClusterRoleBinding</p>\n\n<p>Table 2.11. Query parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\nTable 2.12. Body parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterRoleBinding</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\nTable 2.13. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterRoleBinding</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h2>CHAPTER 3. CLUSTERROLE<br/>[AUTHORIZATION.OPENSHIFT.IO/V1]</h2>\n\n<h3>Description</h3>\n\n<p>ClusterRole is a logical grouping of PolicyRules that can be referenced as a unit by ClusterRoleBindings.</p>\n\n<p>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p>\n\n<h3>Type</h3>\n\n<p><b>object</b></p>\n\n<h3>Required</h3>\n\n<ul>\n<li>• <b>rules</b></li>\n</ul>\n\n<h2>3.1. SPECIFICATION</h2>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>aggregationRule</b></td>\n<td><b>AggregationRule_v2</b></td>\n<td>AggregationRule is an optional field that describes how to build the Rules for this ClusterRole. If AggregationRule is set, then the Rules are controller managed and direct changes to Rules will be stomped by the controller.</td>\n</tr>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta_v2</b></td>\n<td>metadata is the standard object's metadata. More info:<br/><a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</a></td>\n</tr>\n<tr>\n<td><b>rules</b></td>\n<td><b>array</b></td>\n<td>Rules holds all the PolicyRules for this ClusterRole</td>\n</tr>\n<tr>\n<td><b>rules[]</b></td>\n<td><b>object</b></td>\n<td>PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.</td>\n</tr>\n</tbody>\n</table>\n\n<h3>3.1.1. .rules</h3>\n\n<h4>Description</h4>\n\n<p>Rules holds all the PolicyRules for this ClusterRole</p>\n\n<h4>Type</h4>\n\n<p><b>array</b></p>\n\n<h3>3.1.2. .rules[]</h3>\n\n<h4>Description</h4>\n\n<p>PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.</p>\n\n<h4>Type</h4>\n\n<p><b>object</b></p>\n\n<h4>Required</h4>\n\n<ul>\n<li>• <b>verbs</b></li>\n<li>• <b>resources</b></li>\n</ul>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiGroups</b></td>\n<td><b>array (string)</b></td>\n<td>APIGroups is the name of the APIGroup that contains the resources. If this field is empty, then both Kubernetes and origin API groups are assumed. That means that if an action is requested against one of the enumerated resources in either the Kubernetes or the origin API group, the request will be allowed</td>\n</tr>\n<tr>\n<td><b>attributeRestrictions</b></td>\n<td><b>RawExtension</b></td>\n<td>AttributeRestrictions will vary depending on what the Authorizer/AuthorizationAttributeBuilder pair supports. If the Authorizer does not recognize how to handle the AttributeRestrictions, the Authorizer should report an error.</td>\n</tr>\n<tr>\n<td><b>nonResourceURLs</b></td>\n<td><b>array (string)</b></td>\n<td>NonResourceURLsSlice is a set of partial URLs that a user should have access to. *s are allowed, but only as the full, final step in the path. This name is intentionally different than the internal type so that the DefaultConvert works nicely and because the ordering may be different.</td>\n</tr>\n<tr>\n<td><b>resourceNames</b></td>\n<td><b>array (string)</b></td>\n<td>ResourceNames is an optional white list of names that the rule applies to. An empty set means that everything is allowed.</td>\n</tr>\n<tr>\n<td><b>resources</b></td>\n<td><b>array (string)</b></td>\n<td>Resources is a list of resources this rule applies to. ResourceAll represents all resources.</td>\n</tr>\n<tr>\n<td><b>verbs</b></td>\n<td><b>array (string)</b></td>\n<td>Verbs is a list of Verbs that apply to ALL the ResourceKinds and AttributeRestrictions contained in this rule. VerbAll represents all kinds.</td>\n</tr>\n</tbody>\n</table>\n\n<h2>3.2. API ENDPOINTS</h2>\n\n<p>The following API endpoints are available:</p>\n\n<ul>\n<li>• <b>/apis/authorization.openshift.io/v1/cluserroles</b>\n<ul>\n<li>◦ <b>GET</b>: list objects of kind ClusterRole</li>\n<li>◦ <b>POST</b>: create a ClusterRole</li>\n</ul>\n</li>\n<li>• <b>/apis/authorization.openshift.io/v1/cluserroles/{name}</b>\n<ul>\n<li>◦ <b>DELETE</b>: delete a ClusterRole</li>\n<li>◦ <b>GET</b>: read the specified ClusterRole</li>\n<li>◦ <b>PATCH</b>: partially update the specified ClusterRole</li>\n<li>◦ <b>PUT</b>: replace the specified ClusterRole</li>\n</ul>\n</li>\n</ul>\n\n<h3>3.2.1. /apis/authorization.openshift.io/v1/cluserroles</h3>\n\n<p>HTTP method</p>\n\n<p><b>GET</b></p>\n\n<p>Description</p>\n\n<p>list objects of kind ClusterRole</p>\n\n<p>Table 3.1. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRoleList</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>POST</b></p>\n\n<p>Description</p>\n\n<p>create a ClusterRole</p>\n\n<p>Table 3.2. Query parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are:\n<ul>\n<li>- Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23.</li>\n<li>- Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+.</li>\n<li>- Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>\nTable 3.3. Body parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterRole</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\nTable 3.4. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>3.2.2. /apis/authorization.openshift.io/v1/cluserroles/{name}</h3>\nTable 3.5. Global path parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the ClusterRole</td>\n</tr>\n</tbody>\n</table>\n<b>HTTP method</b><b>DELETE</b><b>Description</b>\n<p>delete a ClusterRole</p>\n<b>Table 3.6. Query parameters</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n<b>Table 3.7. HTTP responses</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status_v3</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>Status_v3</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n<b>HTTP method</b><b>GET</b><b>Description</b>\n<p>read the specified ClusterRole</p>\n<b>Table 3.8. HTTP responses</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n<b>HTTP method</b><b>PATCH</b><b>Description</b>\n<p>partially update the specified ClusterRole</p>\n<b>Table 3.9. Query parameters</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\nTable 3.10. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n<b>HTTP method</b><b>PUT</b><b>Description</b><p>replace the specified ClusterRole</p>Table 3.11. Query parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\nTable 3.12. Body parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterRole</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\nTable 3.13. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterRole</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h2>CHAPTER 4. ROLEBINDINGRESTRICTION<br/>[AUTHORIZATION.OPENSHIFT.IO/V1]</h2>\n\n<h3>Description</h3>\n\n<p>RoleBindingRestriction is an object that can be matched against a subject (user, group, or service account) to determine whether rolebindings on that subject are allowed in the namespace to which the RoleBindingRestriction belongs. If any one of those RoleBindingRestriction objects matches a subject, rolebindings on that subject in the namespace are allowed.</p>\n\n<p>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p>\n\n<h3>Type</h3>\n\n<p><b>object</b></p>\n\n<h3>4.1. SPECIFICATION</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta</b></td>\n<td>Standard object's metadata. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</a></td>\n</tr>\n<tr>\n<td><b>spec</b></td>\n<td><b>object</b></td>\n<td>spec defines the matcher.</td>\n</tr>\n</tbody>\n</table>\n\n<h3>4.1.1. .spec</h3>\n\n<h4>Description</h4>\n\n<p>spec defines the matcher.</p>\n\n<h4>Type</h4>\n\n<p><b>object</b></p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>grouprestriction</b></td>\n<td>```</td>\n<td>grouprestriction matches against group subjects.</td>\n</tr>\n<tr>\n<td><b>serviceaccountrestriction</b></td>\n<td>```</td>\n<td>serviceaccountrestriction matches against service-account subjects.</td>\n</tr>\n<tr>\n<td><b>userrestriction</b></td>\n<td>```</td>\n<td>userrestriction matches against user subjects.</td>\n</tr>\n</tbody>\n</table>\n\n<h2>4.2. API ENDPOINTS</h2>\n\n<p>The following API endpoints are available:</p>\n\n<ul style=\"list-style-type: none;\">\n<li>• <b>/apis/authorization.openshift.io/v1/rolebindingrestrictions</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>GET</b>: list objects of kind RoleBindingRestriction</li>\n</ul>\n</li>\n<li>• <b>/apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindingrestrictions</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>DELETE</b>: delete collection of RoleBindingRestriction</li>\n<li>◦ <b>GET</b>: list objects of kind RoleBindingRestriction</li>\n<li>◦ <b>POST</b>: create a RoleBindingRestriction</li>\n</ul>\n</li>\n<li>• <b>/apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindingrestrictions/{name}</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>DELETE</b>: delete a RoleBindingRestriction</li>\n<li>◦ <b>GET</b>: read the specified RoleBindingRestriction</li>\n<li>◦ <b>PATCH</b>: partially update the specified RoleBindingRestriction</li>\n<li>◦ <b>PUT</b>: replace the specified RoleBindingRestriction</li>\n</ul>\n</li>\n</ul>\n\n<h3>4.2.1. /apis/authorization.openshift.io/v1/rolebindingrestrictions</h3>\n\n<h4>HTTP method</h4>\n\n<p><b>GET</b></p>\n\n<h4>Description</h4>\n\n<p>list objects of kind RoleBindingRestriction</p>\nTable 4.1. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>RoleBindingRestrictionList</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h2>4.2.2. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindingrestr</h2>\n\n<p>HTTP method</p>\n\n<p><b>DELETE</b></p>\n\n<p>Description</p>\n\n<p>delete collection of RoleBindingRestriction</p>\nTable 4.2. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>GET</b></p>\n\n<p>Description</p>\n\n<p>list objects of kind RoleBindingRestriction</p>\nTable 4.3. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>RoleBindingRestrictionList</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>POST</b></p>\n\n<p>Description</p>\n\n<p>create a RoleBindingRestriction</p>\nTable 4.4. Query parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\nTable 4.5. Body parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>RoleBindingRestriction</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\nTable 4.6. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>4.2.3. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindingrestr</h3>\nTable 4.7. Global path parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the RoleBindingRestriction</td>\n</tr>\n</tbody>\n</table>\n<p>HTTP method</p><b>DELETE</b><p>Description</p><p>delete a RoleBindingRestriction</p>Table 4.8. Query parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\nTable 4.9. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n<p>HTTP method</p><b>GET</b><p>Description</p><p>read the specified RoleBindingRestriction</p>Table 4.10. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n<p>HTTP method</p><b>PATCH</b><b>Description</b>\n<p>partially update the specified RoleBindingRestriction</p>\n<b>Table 4.11. Query parameters</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n<b>Table 4.12. HTTP responses</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n<b>HTTP method</b>\n<p><b>PUT</b></p>\n<b>Description</b>\n<p>replace the specified RoleBindingRestriction</p>\n<b>Table 4.13. Query parameters</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\nTable 4.14. Body parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>RoleBindingRestriction</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\nTable 4.15. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>RoleBindingRestriction</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>"},"page_stats":{"kind":"list like","value":[{"page_number":1,"error":false,"token_count":245,"num_chunks":5},{"page_number":2,"error":false,"token_count":48,"num_chunks":1},{"page_number":3,"error":false,"token_count":84,"num_chunks":2},{"page_number":4,"error":false,"token_count":587,"num_chunks":11},{"page_number":5,"error":false,"token_count":1644,"num_chunks":4},{"page_number":6,"error":false,"token_count":81,"num_chunks":2},{"page_number":7,"error":false,"token_count":1240,"num_chunks":24},{"page_number":8,"error":false,"token_count":460,"num_chunks":10},{"page_number":9,"error":false,"token_count":866,"num_chunks":12},{"page_number":10,"error":false,"token_count":644,"num_chunks":3},{"page_number":11,"error":false,"token_count":1098,"num_chunks":18},{"page_number":12,"error":false,"token_count":947,"num_chunks":9},{"page_number":13,"error":false,"token_count":1228,"num_chunks":20},{"page_number":14,"error":false,"token_count":967,"num_chunks":12},{"page_number":15,"error":false,"token_count":829,"num_chunks":7},{"page_number":16,"error":false,"token_count":928,"num_chunks":12},{"page_number":17,"error":false,"token_count":1003,"num_chunks":16},{"page_number":18,"error":false,"token_count":693,"num_chunks":5},{"page_number":19,"error":false,"token_count":1063,"num_chunks":16},{"page_number":20,"error":false,"token_count":1003,"num_chunks":10},{"page_number":21,"error":false,"token_count":1154,"num_chunks":21},{"page_number":22,"error":false,"token_count":915,"num_chunks":11},{"page_number":23,"error":false,"token_count":824,"num_chunks":7},{"page_number":24,"error":false,"token_count":938,"num_chunks":10},{"page_number":25,"error":false,"token_count":1117,"num_chunks":15},{"page_number":26,"error":false,"token_count":1212,"num_chunks":23},{"page_number":27,"error":false,"token_count":929,"num_chunks":8},{"page_number":28,"error":false,"token_count":1132,"num_chunks":20},{"page_number":29,"error":false,"token_count":965,"num_chunks":13},{"page_number":30,"error":false,"token_count":822,"num_chunks":7}],"string":"[\n {\n \"page_number\": 1,\n \"error\": false,\n \"token_count\": 245,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 2,\n \"error\": false,\n \"token_count\": 48,\n \"num_chunks\": 1\n },\n {\n \"page_number\": 3,\n \"error\": false,\n \"token_count\": 84,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 4,\n \"error\": false,\n \"token_count\": 587,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 5,\n \"error\": false,\n \"token_count\": 1644,\n \"num_chunks\": 4\n },\n {\n \"page_number\": 6,\n \"error\": false,\n \"token_count\": 81,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 7,\n \"error\": false,\n \"token_count\": 1240,\n \"num_chunks\": 24\n },\n {\n \"page_number\": 8,\n \"error\": false,\n \"token_count\": 460,\n \"num_chunks\": 10\n },\n {\n \"page_number\": 9,\n \"error\": false,\n \"token_count\": 866,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 10,\n \"error\": false,\n \"token_count\": 644,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 11,\n \"error\": false,\n \"token_count\": 1098,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 12,\n \"error\": false,\n \"token_count\": 947,\n \"num_chunks\": 9\n },\n {\n \"page_number\": 13,\n \"error\": false,\n \"token_count\": 1228,\n \"num_chunks\": 20\n },\n {\n \"page_number\": 14,\n \"error\": false,\n \"token_count\": 967,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 15,\n \"error\": false,\n \"token_count\": 829,\n \"num_chunks\": 7\n },\n {\n \"page_number\": 16,\n \"error\": false,\n \"token_count\": 928,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 17,\n \"error\": false,\n \"token_count\": 1003,\n \"num_chunks\": 16\n },\n {\n \"page_number\": 18,\n \"error\": false,\n \"token_count\": 693,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 19,\n \"error\": false,\n \"token_count\": 1063,\n \"num_chunks\": 16\n },\n {\n \"page_number\": 20,\n \"error\": false,\n \"token_count\": 1003,\n \"num_chunks\": 10\n },\n {\n \"page_number\": 21,\n \"error\": false,\n \"token_count\": 1154,\n \"num_chunks\": 21\n },\n {\n \"page_number\": 22,\n \"error\": false,\n \"token_count\": 915,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 23,\n \"error\": false,\n \"token_count\": 824,\n \"num_chunks\": 7\n },\n {\n \"page_number\": 24,\n \"error\": false,\n \"token_count\": 938,\n \"num_chunks\": 10\n },\n {\n \"page_number\": 25,\n \"error\": false,\n \"token_count\": 1117,\n \"num_chunks\": 15\n },\n {\n \"page_number\": 26,\n \"error\": false,\n \"token_count\": 1212,\n \"num_chunks\": 23\n },\n {\n \"page_number\": 27,\n \"error\": false,\n \"token_count\": 929,\n \"num_chunks\": 8\n },\n {\n \"page_number\": 28,\n \"error\": false,\n \"token_count\": 1132,\n \"num_chunks\": 20\n },\n {\n \"page_number\": 29,\n \"error\": false,\n \"token_count\": 965,\n \"num_chunks\": 13\n },\n {\n \"page_number\": 30,\n \"error\": false,\n \"token_count\": 822,\n \"num_chunks\": 7\n }\n]","isConversational":false}}},{"rowIdx":92,"cells":{"source_id":{"kind":"string","value":"OpenShift_Container_Platform-4.21-Scalability_and_performance-en-US"},"pdf_url":{"kind":"string","value":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/scalability_and_performance/OpenShift_Container_Platform-4.21-Scalability_and_performance-en-US.pdf"},"status":{"kind":"string","value":"success"},"processed_at":{"kind":"string","value":"2026-04-15T18:33:51.253367+00:00"},"elapsed_seconds":{"kind":"number","value":70.25,"string":"70.25"},"num_pages":{"kind":"number","value":434,"string":"434"},"num_pages_processed":{"kind":"number","value":30,"string":"30"},"max_pages_per_paper":{"kind":"number","value":30,"string":"30"},"pdf_exceeds_page_limit":{"kind":"bool","value":true,"string":"true"},"failed_pages":{"kind":"list like","value":[],"string":"[]","isConversational":false},"prompt_type":{"kind":"string","value":"ocr_layout"},"model_id":{"kind":"string","value":"datalab-to/chandra-ocr-2"},"script_version":{"kind":"timestamp","value":"2026-04-15T00:00:00","string":"2026-04-15T00:00:00"},"markdown":{"kind":"string","value":"# OpenShift Container Platform 4.21\n\n## Scalability and performance\n\nScaling your OpenShift Container Platform cluster and tuning performance in production environments## OpenShift Container Platform 4.21 Scalability and performance\n\n---\n\nScaling your OpenShift Container Platform cluster and tuning performance in production environments## Legal Notice\n\nCopyright © Red Hat.\n\nExcept as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.\n\nRed Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.\n\nRed Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.\n\nLinux ® is the registered trademark of Linus Torvalds in the United States and other countries.\n\nXFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.\n\nThe OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.\n\nAll other trademarks are the property of their respective owners.\n\n## Abstract\n\nThis document provides instructions for scaling your cluster and optimizing the performance of your OpenShift Container Platform environment.# Table of Contents\n\n<table>\n<tr>\n<td><b>CHAPTER 1. OPENSHIFT CONTAINER PLATFORM SCALABILITY AND PERFORMANCE OVERVIEW</b> .....</td>\n<td><b>11</b></td>\n</tr>\n<tr>\n<td> 1.1. RECOMMENDED PERFORMANCE AND SCALABILITY PRACTICES</td>\n<td>11</td>\n</tr>\n<tr>\n<td> 1.2. TELCO REFERENCE DESIGN SPECIFICATIONS</td>\n<td>11</td>\n</tr>\n<tr>\n<td> 1.3. PLANNING, OPTIMIZATION, AND MEASUREMENT</td>\n<td>11</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. RECOMMENDED PERFORMANCE AND SCALABILITY PRACTICES</b> .....</td>\n<td><b>12</b></td>\n</tr>\n<tr>\n<td> 2.1. RECOMMENDED CONTROL PLANE PRACTICES</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 2.1.1. Recommended practices for scaling the cluster</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 2.1.2. Control plane node sizing</td>\n<td>13</td>\n</tr>\n<tr>\n<td> 2.2. SELECTING A LARGER AWS INSTANCE TYPE FOR CONTROL PLANE MACHINES</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2.1. Additional resources</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2.2. Changing the Amazon Web Services instance type by using a control plane machine set</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2.3. Changing the Amazon Web Services instance type by using the AWS console</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.3. RECOMMENDED INFRASTRUCTURE PRACTICES</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.3.1. Infrastructure node sizing</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.3.2. Scaling the Cluster Monitoring Operator</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.3.3. Prometheus database storage requirements</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.3.4. Configuring cluster monitoring</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 2.3.5. Additional resources</td>\n<td>20</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. TELCO CORE REFERENCE DESIGN SPECIFICATIONS</b> .....</td>\n<td><b>21</b></td>\n</tr>\n<tr>\n<td> 3.1. TELCO CORE RDS USE MODEL OVERVIEW</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.2. ABOUT THE TELCO CORE CLUSTER USE MODEL</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.3. REFERENCE DESIGN SCOPE</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 3.4. DEVIATIONS FROM THE REFERENCE DESIGN</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 3.5. TELCO CORE COMMON BASELINE MODEL</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.6. DEPLOYMENT PLANNING</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.6.1. Worker Nodes and MachineConfigPools</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.6.2. Zones</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.7. TELCO CORE CLUSTER COMMON USE MODEL ENGINEERING CONSIDERATIONS</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.7.1. Application workloads</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.7.2. Signaling workloads</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 3.8. TELCO CORE RDS COMPONENTS</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 3.8.1. CPU partitioning and performance tuning</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 3.8.2. Workloads on schedulable control planes</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.8.3. Service Mesh</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.8.4. Networking</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.8.4.1. Cluster Network Operator</td>\n<td>34</td>\n</tr>\n<tr>\n<td> 3.8.4.2. Load balancer</td>\n<td>36</td>\n</tr>\n<tr>\n<td> 3.8.4.3. SR-IOV</td>\n<td>37</td>\n</tr>\n<tr>\n<td> 3.8.4.4. NMState Operator</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 3.8.5. Logging</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 3.8.6. Power Management</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 3.8.7. Storage</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 3.8.7.1. OpenShift Data Foundation</td>\n<td>40</td>\n</tr>\n<tr>\n<td> 3.8.7.2. Additional storage solutions</td>\n<td>41</td>\n</tr>\n<tr>\n<td> 3.9. TELCO CORE DEPLOYMENT COMPONENTS</td>\n<td>41</td>\n</tr>\n<tr>\n<td> 3.9.1. Red Hat Advanced Cluster Management</td>\n<td>41</td>\n</tr>\n<tr>\n<td> 3.9.2. Topology Aware Lifecycle Manager</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 3.9.3. GitOps Operator and GitOps ZTP plugins</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 3.9.4. Agent-based Installer</td>\n<td>44</td>\n</tr>\n</table><table>\n<tr><td>3.10. MONITORING</td><td>44</td></tr>\n<tr><td>3.11. SCHEDULING</td><td>45</td></tr>\n<tr><td>3.12. NODE CONFIGURATION</td><td>46</td></tr>\n<tr><td> 3.12.1. Host firmware and boot loader configuration</td><td>47</td></tr>\n<tr><td> 3.12.2. Kubelet Settings</td><td>48</td></tr>\n<tr><td>3.13. DISCONNECTED ENVIRONMENT</td><td>48</td></tr>\n<tr><td>3.14. SECURITY</td><td>49</td></tr>\n<tr><td>3.15. CERT-MANAGER OPERATOR</td><td>51</td></tr>\n<tr><td>3.16. SCALABILITY</td><td>51</td></tr>\n<tr><td>3.17. TELCO CORE REFERENCE CONFIGURATION CRS</td><td>51</td></tr>\n<tr><td> 3.17.1. Extracting the telco core reference design configuration CRs</td><td>51</td></tr>\n<tr><td> 3.17.2. Comparing a cluster with the telco core reference configuration</td><td>53</td></tr>\n<tr><td> 3.17.3. Node configuration reference CRs</td><td>57</td></tr>\n<tr><td> 3.17.4. Cluster infrastructure reference CRs</td><td>57</td></tr>\n<tr><td> 3.17.5. Resource tuning reference CRs</td><td>59</td></tr>\n<tr><td> 3.17.6. Networking reference CRs</td><td>59</td></tr>\n<tr><td> 3.17.7. Scheduling reference CRs</td><td>63</td></tr>\n<tr><td> 3.17.8. Storage reference CRs</td><td>64</td></tr>\n<tr><td> 3.17.9. Security reference CRs</td><td>65</td></tr>\n<tr><td>3.18. TELCO CORE REFERENCE CONFIGURATION SOFTWARE SPECIFICATIONS</td><td>65</td></tr>\n<tr><td><b>CHAPTER 4. TELCO RAN DU REFERENCE DESIGN SPECIFICATION .....</b></td><td><b>67</b></td></tr>\n<tr><td> 4.1. REFERENCE DESIGN SPECIFICATIONS FOR TELCO RAN DU 5G DEPLOYMENTS</td><td>67</td></tr>\n<tr><td> 4.1.1. Supported CPU architectures for RAN DU</td><td>68</td></tr>\n<tr><td> 4.2. REFERENCE DESIGN SCOPE</td><td>68</td></tr>\n<tr><td> 4.3. DEVIATIONS FROM THE REFERENCE DESIGN</td><td>69</td></tr>\n<tr><td> 4.4. ENGINEERING CONSIDERATIONS FOR THE RAN DU USE MODEL</td><td>69</td></tr>\n<tr><td> 4.5. TELCO RAN DU APPLICATION WORKLOADS</td><td>73</td></tr>\n<tr><td> 4.6. TELCO RAN DU REFERENCE DESIGN COMPONENTS</td><td>74</td></tr>\n<tr><td> 4.6.1. Host firmware tuning</td><td>74</td></tr>\n<tr><td> 4.6.2. Kubelet Settings</td><td>75</td></tr>\n<tr><td> 4.6.3. CPU partitioning and performance tuning</td><td>76</td></tr>\n<tr><td> 4.6.4. PTP Operator</td><td>79</td></tr>\n<tr><td> 4.6.5. SR-IOV Operator</td><td>80</td></tr>\n<tr><td> 4.6.6. Logging</td><td>82</td></tr>\n<tr><td> 4.6.7. SRIOV-FEC Operator</td><td>82</td></tr>\n<tr><td> 4.6.8. Lifecycle Agent</td><td>83</td></tr>\n<tr><td> 4.6.9. Local Storage Operator</td><td>83</td></tr>\n<tr><td> 4.6.10. Logical Volume Manager Storage</td><td>83</td></tr>\n<tr><td> 4.6.11. Workload partitioning</td><td>84</td></tr>\n<tr><td> 4.6.12. Cluster tuning</td><td>85</td></tr>\n<tr><td> 4.6.13. Machine configuration</td><td>87</td></tr>\n<tr><td> 4.7. TELCO RAN DU DEPLOYMENT COMPONENTS</td><td>88</td></tr>\n<tr><td> 4.7.1. Red Hat Advanced Cluster Management</td><td>88</td></tr>\n<tr><td> 4.7.2. SiteConfig Operator</td><td>89</td></tr>\n<tr><td> 4.7.3. Topology Aware Lifecycle Manager</td><td>90</td></tr>\n<tr><td> 4.7.4. GitOps Operator and GitOps ZTP</td><td>91</td></tr>\n<tr><td> 4.7.5. Agent-based installer</td><td>92</td></tr>\n<tr><td> 4.8. TELCO RAN DU REFERENCE CONFIGURATION CRS</td><td>92</td></tr>\n<tr><td> 4.8.1. Cluster tuning reference CRs</td><td>93</td></tr>\n<tr><td> 4.8.2. Day 2 Operators reference CRs</td><td>94</td></tr>\n<tr><td> 4.8.3. Machine configuration reference CRs</td><td>102</td></tr>\n<tr><td> 4.9. COMPARING A CLUSTER WITH THE TELCO RAN DU REFERENCE CONFIGURATION</td><td>103</td></tr>\n</table>---\n\n<table>\n<tr>\n<td>4.10. TELCO RAN DU 4.21 VALIDATED SOFTWARE COMPONENTS</td>\n<td>105</td>\n</tr>\n<tr>\n<td><b>CHAPTER 5. TELCO HUB REFERENCE DESIGN SPECIFICATION</b> .....</td>\n<td><b>107</b></td>\n</tr>\n<tr>\n<td>5.1. REFERENCE DESIGN SCOPE</td>\n<td>107</td>\n</tr>\n<tr>\n<td>5.2. DEVIATIONS FROM THE REFERENCE DESIGN</td>\n<td>107</td>\n</tr>\n<tr>\n<td>5.3. HUB CLUSTER ARCHITECTURE OVERVIEW</td>\n<td>108</td>\n</tr>\n<tr>\n<td>5.4. TELCO MANAGEMENT HUB CLUSTER USE MODEL</td>\n<td>109</td>\n</tr>\n<tr>\n<td>5.5. HUB CLUSTER SCALING TARGET</td>\n<td>110</td>\n</tr>\n<tr>\n<td>5.6. HUB CLUSTER RESOURCE UTILIZATION</td>\n<td>111</td>\n</tr>\n<tr>\n<td>5.7. HUB CLUSTER TOPOLOGY</td>\n<td>111</td>\n</tr>\n<tr>\n<td>5.8. HUB CLUSTER NETWORKING</td>\n<td>112</td>\n</tr>\n<tr>\n<td>5.9. HUB CLUSTER MEMORY AND CPU REQUIREMENTS</td>\n<td>113</td>\n</tr>\n<tr>\n<td>5.10. HUB CLUSTER STORAGE REQUIREMENTS</td>\n<td>114</td>\n</tr>\n<tr>\n<td> 5.10.1. Assisted Service</td>\n<td>114</td>\n</tr>\n<tr>\n<td> 5.10.2. RHACM Observability</td>\n<td>114</td>\n</tr>\n<tr>\n<td> 5.10.3. Storage considerations</td>\n<td>116</td>\n</tr>\n<tr>\n<td>5.11. GIT REPOSITORY</td>\n<td>117</td>\n</tr>\n<tr>\n<td>5.12. OPENSHIFT CONTAINER PLATFORM INSTALLATION ON THE HUB CLUSTER</td>\n<td>117</td>\n</tr>\n<tr>\n<td>5.13. DAY 2 OPERATORS IN THE HUB CLUSTER</td>\n<td>118</td>\n</tr>\n<tr>\n<td>5.14. OBSERVABILITY</td>\n<td>119</td>\n</tr>\n<tr>\n<td>5.15. MANAGED CLUSTER LIFECYCLE MANAGEMENT</td>\n<td>121</td>\n</tr>\n<tr>\n<td> 5.15.1. Managed cluster deployment</td>\n<td>121</td>\n</tr>\n<tr>\n<td> 5.15.2. Managed cluster updates</td>\n<td>122</td>\n</tr>\n<tr>\n<td> 5.15.3. Hub cluster disaster recovery</td>\n<td>124</td>\n</tr>\n<tr>\n<td>5.16. HUB CLUSTER COMPONENTS</td>\n<td>124</td>\n</tr>\n<tr>\n<td> 5.16.1. Red Hat Advanced Cluster Management (RHACM)</td>\n<td>124</td>\n</tr>\n<tr>\n<td> 5.16.2. Topology Aware Lifecycle Manager</td>\n<td>126</td>\n</tr>\n<tr>\n<td> 5.16.3. GitOps Operator and GitOps ZTP</td>\n<td>127</td>\n</tr>\n<tr>\n<td> 5.16.4. Local Storage Operator</td>\n<td>127</td>\n</tr>\n<tr>\n<td> 5.16.5. Red Hat OpenShift Data Foundation</td>\n<td>128</td>\n</tr>\n<tr>\n<td> 5.16.6. Logging</td>\n<td>128</td>\n</tr>\n<tr>\n<td> 5.16.7. OpenShift API for Data Protection</td>\n<td>129</td>\n</tr>\n<tr>\n<td> 5.16.8. cert-manager Operator</td>\n<td>129</td>\n</tr>\n<tr>\n<td>5.17. EXTRACTING THE TELCO HUB REFERENCE DESIGN CONFIGURATION CRS</td>\n<td>130</td>\n</tr>\n<tr>\n<td>5.18. COMPARING A CLUSTER WITH THE TELCO HUB REFERENCE CONFIGURATION</td>\n<td>132</td>\n</tr>\n<tr>\n<td>5.19. HUB CLUSTER REFERENCE CONFIGURATION CRS</td>\n<td>134</td>\n</tr>\n<tr>\n<td>5.20. ADVANCED CLUSTER MANAGEMENT REFERENCE CRS</td>\n<td>135</td>\n</tr>\n<tr>\n<td>5.21. STORAGE REFERENCE CRS</td>\n<td>137</td>\n</tr>\n<tr>\n<td>5.22. GITOPS ZERO TOUCH PROVISIONING (ZTP) REFERENCE CRS</td>\n<td>139</td>\n</tr>\n<tr>\n<td>5.23. LOGGING REFERENCE CRS</td>\n<td>142</td>\n</tr>\n<tr>\n<td>5.24. CONTAINER REGISTRY REFERENCE CRS</td>\n<td>142</td>\n</tr>\n<tr>\n<td>5.25. IMAGE MIRRORING REFERENCE CRS</td>\n<td>143</td>\n</tr>\n<tr>\n<td>5.26. INSTALLATION REFERENCE CRS</td>\n<td>144</td>\n</tr>\n<tr>\n<td>5.27. SECURITY REFERENCE CRS</td>\n<td>144</td>\n</tr>\n<tr>\n<td>5.28. BACKUP RECOVERY REFERENCE CRS</td>\n<td>145</td>\n</tr>\n<tr>\n<td>5.29. TELCO HUB REFERENCE CONFIGURATION SOFTWARE SPECIFICATIONS</td>\n<td>146</td>\n</tr>\n<tr>\n<td><b>CHAPTER 6. COMPARING CLUSTER CONFIGURATIONS</b> .....</td>\n<td><b>148</b></td>\n</tr>\n<tr>\n<td>6.1. UNDERSTANDING THE CLUSTER-COMPARE PLUGIN</td>\n<td>148</td>\n</tr>\n<tr>\n<td> 6.1.1. Overview of the cluster-compare plugin</td>\n<td>148</td>\n</tr>\n<tr>\n<td> 6.1.2. Understanding a reference configuration</td>\n<td>149</td>\n</tr>\n<tr>\n<td> 6.1.3. Additional resources</td>\n<td>150</td>\n</tr>\n<tr>\n<td>6.2. INSTALLING THE CLUSTER-COMPARE PLUGIN</td>\n<td>150</td>\n</tr>\n</table><table>\n<tbody>\n<tr>\n<td>6.2.1. Installing the cluster-compare plugin</td>\n<td>150</td>\n</tr>\n<tr>\n<td>6.2.2. Additional resources</td>\n<td>151</td>\n</tr>\n<tr>\n<td>6.3. USING THE CLUSTER-COMPARE PLUGIN</td>\n<td>151</td>\n</tr>\n<tr>\n<td>6.3.1. Using the cluster-compare plugin with a live cluster</td>\n<td>151</td>\n</tr>\n<tr>\n<td>6.3.2. Using the cluster-compare plugin with must-gather data</td>\n<td>153</td>\n</tr>\n<tr>\n<td>6.3.3. Reference cluster-compare plugin options</td>\n<td>156</td>\n</tr>\n<tr>\n<td>6.3.4. Example: Comparing a cluster with the telco core reference configuration</td>\n<td>157</td>\n</tr>\n<tr>\n<td>6.3.5. Additional resources</td>\n<td>161</td>\n</tr>\n<tr>\n<td>6.4. CREATING A REFERENCE CONFIGURATION</td>\n<td>161</td>\n</tr>\n<tr>\n<td>6.4.1. Structure of the metadata.yaml file</td>\n<td>161</td>\n</tr>\n<tr>\n<td>6.4.2. Configuring template relationships</td>\n<td>162</td>\n</tr>\n<tr>\n<td>6.4.3. Configuring expected variation in a template</td>\n<td>163</td>\n</tr>\n<tr>\n<td>6.4.3.1. Reference template functions</td>\n<td>164</td>\n</tr>\n<tr>\n<td>6.4.4. Configuring the metadata.yaml file to exclude template fields</td>\n<td>166</td>\n</tr>\n<tr>\n<td>6.4.4.1. Excluding all fields not specified in a template</td>\n<td>167</td>\n</tr>\n<tr>\n<td>6.4.4.2. Excluding specific fields by setting default exclusion fields</td>\n<td>167</td>\n</tr>\n<tr>\n<td>6.4.4.3. Excluding specific fields</td>\n<td>168</td>\n</tr>\n<tr>\n<td>6.4.4.4. Excluding specific fields by setting default exclusion groups</td>\n<td>168</td>\n</tr>\n<tr>\n<td>6.4.5. Configuring inline validation for template fields</td>\n<td>169</td>\n</tr>\n<tr>\n<td>6.4.5.1. Configuring inline validation with the regex function</td>\n<td>169</td>\n</tr>\n<tr>\n<td>6.4.5.2. Configuring inline validation with the capturegroups function</td>\n<td>170</td>\n</tr>\n<tr>\n<td>6.4.6. Configuring descriptions for the output</td>\n<td>171</td>\n</tr>\n<tr>\n<td>6.5. PERFORMING ADVANCED REFERENCE CONFIGURATION CUSTOMIZATION</td>\n<td>172</td>\n</tr>\n<tr>\n<td>6.5.1. Configuring manual matching between CRs and templates</td>\n<td>172</td>\n</tr>\n<tr>\n<td>6.5.2. Patching a reference configuration</td>\n<td>173</td>\n</tr>\n<tr>\n<td>6.5.2.1. Using the cluster-compare plugin to generate a patch</td>\n<td>174</td>\n</tr>\n<tr>\n<td>6.5.2.2. Creating a patch file manually</td>\n<td>175</td>\n</tr>\n<tr>\n<td>6.6. TROUBLESHOOTING CLUSTER COMPARISONS</td>\n<td>178</td>\n</tr>\n<tr>\n<td>6.6.1. Troubleshooting false positives for missing resources</td>\n<td>178</td>\n</tr>\n<tr>\n<td>6.6.2. Troubleshooting multiple template matches for the same CR</td>\n<td>178</td>\n</tr>\n<tr>\n<td>6.6.3. Additional resources</td>\n<td>178</td>\n</tr>\n<tr>\n<td><b>CHAPTER 7. PLANNING YOUR ENVIRONMENT ACCORDING TO OBJECT MAXIMUMS</b> .....</td>\n<td><b>179</b></td>\n</tr>\n<tr>\n<td>7.1. OPENSHIFT CONTAINER PLATFORM TESTED CLUSTER MAXIMUMS FOR MAJOR RELEASES</td>\n<td>179</td>\n</tr>\n<tr>\n<td>7.2. OPENSHIFT CONTAINER PLATFORM ENVIRONMENT AND CONFIGURATION ON WHICH THE CLUSTER MAXIMUMS ARE TESTED</td>\n<td>183</td>\n</tr>\n<tr>\n<td>7.2.1. AWS cloud platform cluster maximums</td>\n<td>183</td>\n</tr>\n<tr>\n<td>7.2.2. IBM Power platform cluster maximums</td>\n<td>184</td>\n</tr>\n<tr>\n<td>7.2.3. IBM Z platform cluster maximums</td>\n<td>185</td>\n</tr>\n<tr>\n<td>7.3. HOW TO PLAN YOUR ENVIRONMENT ACCORDING TO TESTED CLUSTER MAXIMUMS</td>\n<td>185</td>\n</tr>\n<tr>\n<td>7.4. HOW TO PLAN YOUR ENVIRONMENT ACCORDING TO APPLICATION REQUIREMENTS</td>\n<td>186</td>\n</tr>\n<tr>\n<td><b>CHAPTER 8. USING QUOTAS AND LIMIT RANGES</b> .....</td>\n<td><b>190</b></td>\n</tr>\n<tr>\n<td>8.1. RESOURCES MANAGED BY QUOTA</td>\n<td>190</td>\n</tr>\n<tr>\n<td>8.2. SETTING RESOURCE QUOTA FOR EXTENDED RESOURCES</td>\n<td>192</td>\n</tr>\n<tr>\n<td>8.3. QUOTA SCOPES</td>\n<td>195</td>\n</tr>\n<tr>\n<td>8.4. ADDITIONAL RESOURCES</td>\n<td>196</td>\n</tr>\n<tr>\n<td>8.5. ADMIN QUOTA USAGE</td>\n<td>196</td>\n</tr>\n<tr>\n<td>8.5.1. Sample resource quota definitions</td>\n<td>196</td>\n</tr>\n<tr>\n<td>8.5.2. Creating a quota</td>\n<td>201</td>\n</tr>\n<tr>\n<td>8.5.3. Creating object count quotas</td>\n<td>201</td>\n</tr>\n<tr>\n<td>8.5.4. Viewing a quota</td>\n<td>202</td>\n</tr>\n<tr>\n<td>8.5.5. Configuring quota synchronization period</td>\n<td>202</td>\n</tr>\n</tbody>\n</table>---\n\n<table>\n<tr>\n<td>8.5.6. Setting a quota to consume a resource</td>\n<td>203</td>\n</tr>\n<tr>\n<td>8.6. ADDITIONAL RESOURCES</td>\n<td>204</td>\n</tr>\n<tr>\n<td>8.7. LIMIT RANGES IN A LIMITRANGE OBJECT</td>\n<td>204</td>\n</tr>\n<tr>\n<td>8.7.1. Container limits</td>\n<td>207</td>\n</tr>\n<tr>\n<td>8.7.2. Pod limits</td>\n<td>208</td>\n</tr>\n<tr>\n<td>8.7.3. Image limits</td>\n<td>209</td>\n</tr>\n<tr>\n<td>8.7.4. Image stream limits</td>\n<td>209</td>\n</tr>\n<tr>\n<td>8.7.5. PersistentVolumeClaim limits</td>\n<td>210</td>\n</tr>\n<tr>\n<td>8.8. ADDITIONAL RESOURCES</td>\n<td>211</td>\n</tr>\n<tr>\n<td>8.9. LIMIT RANGE OPERATIONS</td>\n<td>211</td>\n</tr>\n<tr>\n<td>8.10. ADDITIONAL RESOURCES</td>\n<td>212</td>\n</tr>\n<tr>\n<td><b>CHAPTER 9. HOST PRACTICES FOR IBM Z AND IBM LINUXONE ENVIRONMENTS</b> .....</td>\n<td><b>213</b></td>\n</tr>\n<tr>\n<td>9.1. MANAGING CPU OVERCOMMITMENT</td>\n<td>213</td>\n</tr>\n<tr>\n<td>9.2. DISABLE TRANSPARENT HUGE PAGES</td>\n<td>213</td>\n</tr>\n<tr>\n<td>9.3. BOOSTING NETWORKING PERFORMANCE WITH RFS</td>\n<td>214</td>\n</tr>\n<tr>\n<td>9.4. CHOOSE YOUR NETWORKING SETUP</td>\n<td>215</td>\n</tr>\n<tr>\n<td>9.5. ENSURE HIGH DISK PERFORMANCE WITH HYPERPAV ON Z/VM</td>\n<td>216</td>\n</tr>\n<tr>\n<td>9.6. RHEL KVM ON IBM Z HOST RECOMMENDATIONS</td>\n<td>217</td>\n</tr>\n<tr>\n<td>9.6.1. Use I/O threads for your virtual block devices</td>\n<td>217</td>\n</tr>\n<tr>\n<td>9.6.2. Avoid virtual SCSI devices</td>\n<td>218</td>\n</tr>\n<tr>\n<td>9.6.3. Configure guest caching for disk</td>\n<td>218</td>\n</tr>\n<tr>\n<td>9.6.4. Excluding the memory balloon device</td>\n<td>218</td>\n</tr>\n<tr>\n<td>9.6.5. Tuning the CPU migration algorithm of the host scheduler</td>\n<td>219</td>\n</tr>\n<tr>\n<td>9.6.6. Disabling the cgroup controller</td>\n<td>219</td>\n</tr>\n<tr>\n<td>9.6.7. Tuning the polling period for idle virtual CPUs</td>\n<td>220</td>\n</tr>\n<tr>\n<td><b>CHAPTER 10. USING THE NODE TUNING OPERATOR</b> .....</td>\n<td><b>221</b></td>\n</tr>\n<tr>\n<td>10.1. ABOUT THE NODE TUNING OPERATOR</td>\n<td>221</td>\n</tr>\n<tr>\n<td>10.2. ACCESSING AN EXAMPLE NODE TUNING OPERATOR SPECIFICATION</td>\n<td>221</td>\n</tr>\n<tr>\n<td>10.3. DEFAULT PROFILES SET ON A CLUSTER</td>\n<td>222</td>\n</tr>\n<tr>\n<td>10.4. VERIFYING THAT THE TUNED PROFILES ARE APPLIED</td>\n<td>222</td>\n</tr>\n<tr>\n<td>10.5. CUSTOM TUNING SPECIFICATION</td>\n<td>223</td>\n</tr>\n<tr>\n<td>10.6. CUSTOM TUNING EXAMPLES</td>\n<td>228</td>\n</tr>\n<tr>\n<td>10.7. DEFERRING APPLICATION OF TUNING CHANGES</td>\n<td>230</td>\n</tr>\n<tr>\n<td>10.7.1. Deferring application of tuning changes: An example</td>\n<td>232</td>\n</tr>\n<tr>\n<td>10.8. SUPPORTED TUNED DAEMON PLUGINS</td>\n<td>235</td>\n</tr>\n<tr>\n<td>10.9. CONFIGURING NODE TUNING IN A HOSTED CLUSTER</td>\n<td>236</td>\n</tr>\n<tr>\n<td>10.10. ADVANCED NODE TUNING FOR HOSTED CLUSTERS BY SETTING KERNEL BOOT PARAMETERS</td>\n<td>239</td>\n</tr>\n<tr>\n<td><b>CHAPTER 11. USING CPU MANAGER AND TOPOLOGY MANAGER</b> .....</td>\n<td><b>243</b></td>\n</tr>\n<tr>\n<td>11.1. SETTING UP CPU MANAGER</td>\n<td>243</td>\n</tr>\n<tr>\n<td>11.2. TOPOLOGY MANAGER POLICIES</td>\n<td>248</td>\n</tr>\n<tr>\n<td>11.3. SETTING UP TOPOLOGY MANAGER</td>\n<td>249</td>\n</tr>\n<tr>\n<td>11.4. POD INTERACTIONS WITH TOPOLOGY MANAGER POLICIES</td>\n<td>249</td>\n</tr>\n<tr>\n<td><b>CHAPTER 12. SCHEDULING NUMA-AWARE WORKLOADS</b> .....</td>\n<td><b>251</b></td>\n</tr>\n<tr>\n<td>12.1. ABOUT NUMA</td>\n<td>251</td>\n</tr>\n<tr>\n<td>12.2. ABOUT NUMA-AWARE SCHEDULING</td>\n<td>251</td>\n</tr>\n<tr>\n<td>12.3. NUMA RESOURCE SCHEDULING STRATEGIES</td>\n<td>253</td>\n</tr>\n<tr>\n<td>12.4. INSTALLING THE NUMA RESOURCES OPERATOR</td>\n<td>254</td>\n</tr>\n<tr>\n<td>12.4.1. Installing the NUMA Resources Operator using the CLI</td>\n<td>254</td>\n</tr>\n<tr>\n<td>12.4.2. Installing the NUMA Resources Operator using the web console</td>\n<td>255</td>\n</tr>\n<tr>\n<td>12.5. CONFIGURING A SINGLE NUMA NODE POLICY</td>\n<td>256</td>\n</tr>\n</table><table>\n<tbody>\n<tr>\n<td>12.5.1. Managing high availability (HA) for the NUMA-aware scheduler</td>\n<td>256</td>\n</tr>\n<tr>\n<td> 12.5.1.1. Customizing scheduler replicas</td>\n<td>257</td>\n</tr>\n<tr>\n<td> 12.5.1.2. Disabling NUMA-aware scheduling</td>\n<td>258</td>\n</tr>\n<tr>\n<td> 12.5.1.3. Verifying scheduler high availability (HA) status</td>\n<td>258</td>\n</tr>\n<tr>\n<td>12.5.2. Sample performance profile</td>\n<td>259</td>\n</tr>\n<tr>\n<td>12.5.3. Creating a KubeletConfig CR</td>\n<td>260</td>\n</tr>\n<tr>\n<td>12.6. SCHEDULING NUMA-AWARE WORKLOADS</td>\n<td>261</td>\n</tr>\n<tr>\n<td> 12.6.1. Creating the NUMAResourcesOperator custom resource</td>\n<td>262</td>\n</tr>\n<tr>\n<td> 12.6.2. Creating the NUMAResourcesOperator custom resource for hosted control planes</td>\n<td>263</td>\n</tr>\n<tr>\n<td> 12.6.3. Deploying the NUMA-aware secondary pod scheduler</td>\n<td>266</td>\n</tr>\n<tr>\n<td> 12.6.4. Scheduling workloads with the NUMA-aware scheduler</td>\n<td>267</td>\n</tr>\n<tr>\n<td>12.7. NUMA RESOURCES OPERATOR SUPPORT FOR SCHEDULABLE CONTROL-PLANE NODES</td>\n<td>271</td>\n</tr>\n<tr>\n<td> 12.7.1. Configuring NUMA Resources Operator on schedulable control plane nodes</td>\n<td>272</td>\n</tr>\n<tr>\n<td>12.8. CONFIGURING POLLING OPERATIONS FOR NUMA RESOURCES UPDATES</td>\n<td>276</td>\n</tr>\n<tr>\n<td>12.9. TROUBLESHOOTING NUMA-AWARE SCHEDULING</td>\n<td>278</td>\n</tr>\n<tr>\n<td> 12.9.1. Reporting more exact resource availability</td>\n<td>281</td>\n</tr>\n<tr>\n<td> 12.9.2. Changing where high-performance workloads run</td>\n<td>284</td>\n</tr>\n<tr>\n<td> 12.9.3. Checking the NUMA-aware scheduler logs</td>\n<td>285</td>\n</tr>\n<tr>\n<td> 12.9.4. Troubleshooting the resource topology exporter</td>\n<td>288</td>\n</tr>\n<tr>\n<td> 12.9.5. Correcting a missing resource topology exporter config map</td>\n<td>289</td>\n</tr>\n<tr>\n<td> 12.9.6. Collecting NUMA Resources Operator data</td>\n<td>291</td>\n</tr>\n<tr>\n<td><b>CHAPTER 13. SCALABILITY AND PERFORMANCE OPTIMIZATION</b> .....</td>\n<td><b>292</b></td>\n</tr>\n<tr>\n<td>13.1. OPTIMIZING STORAGE</td>\n<td>292</td>\n</tr>\n<tr>\n<td> 13.1.1. Available persistent storage options</td>\n<td>292</td>\n</tr>\n<tr>\n<td> 13.1.2. Recommended configurable storage technology</td>\n<td>293</td>\n</tr>\n<tr>\n<td> 13.1.2.1. Specific application storage recommendations</td>\n<td>294</td>\n</tr>\n<tr>\n<td> 13.1.3. Additional resources</td>\n<td>296</td>\n</tr>\n<tr>\n<td> 13.1.4. Data storage management</td>\n<td>296</td>\n</tr>\n<tr>\n<td> 13.1.5. Optimizing storage performance for Microsoft Azure</td>\n<td>297</td>\n</tr>\n<tr>\n<td>13.2. OPTIMIZING ROUTING</td>\n<td>297</td>\n</tr>\n<tr>\n<td> 13.2.1. Baseline Ingress Controller (router) performance</td>\n<td>297</td>\n</tr>\n<tr>\n<td> 13.2.2. Additional resources</td>\n<td>299</td>\n</tr>\n<tr>\n<td> 13.2.3. Configuring Ingress Controller liveness, readiness, and startup probes</td>\n<td>299</td>\n</tr>\n<tr>\n<td> 13.2.4. Configuring HAProxy reload interval</td>\n<td>300</td>\n</tr>\n<tr>\n<td>13.3. OPTIMIZING NETWORKING</td>\n<td>301</td>\n</tr>\n<tr>\n<td> 13.3.1. Additional resources</td>\n<td>301</td>\n</tr>\n<tr>\n<td> 13.3.2. Optimizing the MTU for your network</td>\n<td>301</td>\n</tr>\n<tr>\n<td> 13.3.3. Recommended practices for installing large-scale clusters</td>\n<td>302</td>\n</tr>\n<tr>\n<td> 13.3.4. Impact of IPsec</td>\n<td>302</td>\n</tr>\n<tr>\n<td> 13.3.5. Additional resources</td>\n<td>302</td>\n</tr>\n<tr>\n<td>13.4. OPTIMIZING CPU USAGE WITH MOUNT NAMESPACE ENCAPSULATION</td>\n<td>303</td>\n</tr>\n<tr>\n<td> 13.4.1. Encapsulating mount namespaces</td>\n<td>303</td>\n</tr>\n<tr>\n<td> 13.4.2. Configuring mount namespace encapsulation</td>\n<td>305</td>\n</tr>\n<tr>\n<td> 13.4.3. Inspecting encapsulated namespaces</td>\n<td>308</td>\n</tr>\n<tr>\n<td> 13.4.4. Running additional services in the encapsulated namespace</td>\n<td>309</td>\n</tr>\n<tr>\n<td> 13.4.5. Additional resources</td>\n<td>309</td>\n</tr>\n<tr>\n<td><b>CHAPTER 14. MANAGING BARE-METAL HOSTS</b> .....</td>\n<td><b>311</b></td>\n</tr>\n<tr>\n<td>14.1. ABOUT BARE METAL HOSTS AND NODES</td>\n<td>311</td>\n</tr>\n<tr>\n<td>14.2. MAINTAINING BARE METAL HOSTS</td>\n<td>311</td>\n</tr>\n<tr>\n<td> 14.2.1. Adding a bare metal host to the cluster using the web console</td>\n<td>312</td>\n</tr>\n<tr>\n<td> 14.2.2. Adding a bare-metal host to the cluster using YAML in the web console</td>\n<td>312</td>\n</tr>\n</tbody>\n</table>---\n\n<table>\n<tr>\n<td>14.2.3. Automatically scaling machines to the number of available bare-metal hosts</td>\n<td>313</td>\n</tr>\n<tr>\n<td>14.2.4. Removing bare-metal hosts from the provisioner node</td>\n<td>314</td>\n</tr>\n<tr>\n<td>14.2.5. Powering off bare-metal hosts by using the web console</td>\n<td>315</td>\n</tr>\n<tr>\n<td>14.2.6. Powering off bare-metal hosts by using the CLI</td>\n<td>316</td>\n</tr>\n<tr>\n<td><b>CHAPTER 15. OPTIMIZING MEMORY MANAGEMENT FOR WORKLOADS BY USING HUGE PAGES</b> .....</td>\n<td><b>318</b></td>\n</tr>\n<tr>\n<td>15.1. WHAT HUGE PAGES DO</td>\n<td>318</td>\n</tr>\n<tr>\n<td>15.2. HOW HUGE PAGES ARE CONSUMED BY APPS</td>\n<td>318</td>\n</tr>\n<tr>\n<td> 15.2.1. Allocating huge pages of a specific size</td>\n<td>319</td>\n</tr>\n<tr>\n<td> 15.2.2. Huge page requirements</td>\n<td>319</td>\n</tr>\n<tr>\n<td>15.3. CONSUMING HUGE PAGES RESOURCES USING THE DOWNWARD API</td>\n<td>319</td>\n</tr>\n<tr>\n<td>15.4. CONFIGURING HUGE PAGES AT BOOT TIME</td>\n<td>321</td>\n</tr>\n<tr>\n<td>15.5. DISABLING TRANSPARENT HUGE PAGES</td>\n<td>323</td>\n</tr>\n<tr>\n<td><b>CHAPTER 16. UNDERSTANDING LOW LATENCY TUNING FOR CLUSTER NODES</b> .....</td>\n<td><b>325</b></td>\n</tr>\n<tr>\n<td>16.1. ABOUT LOW LATENCY</td>\n<td>325</td>\n</tr>\n<tr>\n<td>16.2. ABOUT HYPER-THREADING FOR LOW LATENCY AND REAL-TIME APPLICATIONS</td>\n<td>326</td>\n</tr>\n<tr>\n<td><b>CHAPTER 17. TUNING NODES FOR LOW LATENCY WITH THE PERFORMANCE PROFILE</b> .....</td>\n<td><b>327</b></td>\n</tr>\n<tr>\n<td>17.1. CREATING A PERFORMANCE PROFILE</td>\n<td>327</td>\n</tr>\n<tr>\n<td> 17.1.1. About the Performance Profile Creator</td>\n<td>327</td>\n</tr>\n<tr>\n<td> 17.1.2. Creating a machine config pool to target nodes for performance tuning</td>\n<td>328</td>\n</tr>\n<tr>\n<td> 17.1.3. Gathering data about your cluster for the PPC</td>\n<td>329</td>\n</tr>\n<tr>\n<td> 17.1.4. Running the Performance Profile Creator using Podman</td>\n<td>330</td>\n</tr>\n<tr>\n<td> 17.1.5. Running the Performance Profile Creator wrapper script</td>\n<td>334</td>\n</tr>\n<tr>\n<td> 17.1.6. Performance Profile Creator arguments</td>\n<td>339</td>\n</tr>\n<tr>\n<td>17.2. REFERENCE PERFORMANCE PROFILES</td>\n<td>342</td>\n</tr>\n<tr>\n<td> 17.2.1. Performance profile template for clusters that use OVS-DPDK on OpenStack</td>\n<td>342</td>\n</tr>\n<tr>\n<td> 17.2.2. Telco RAN DU reference design performance profile</td>\n<td>343</td>\n</tr>\n<tr>\n<td> 17.2.3. Telco core reference design performance profile</td>\n<td>344</td>\n</tr>\n<tr>\n<td>17.3. SUPPORTED PERFORMANCE PROFILE API VERSIONS</td>\n<td>345</td>\n</tr>\n<tr>\n<td>17.4. NODE POWER CONSUMPTION AND REALTIME PROCESSING WITH WORKLOAD HINTS</td>\n<td>345</td>\n</tr>\n<tr>\n<td>17.5. CONFIGURING POWER SAVING FOR NODES THAT RUN COLOCATED HIGH AND LOW PRIORITY WORKLOADS</td>\n<td>347</td>\n</tr>\n<tr>\n<td>17.6. CPUS FOR INFRA AND APPLICATION CONTAINERS</td>\n<td>348</td>\n</tr>\n<tr>\n<td>17.7. RESTRICTING CPUS FOR INFRA AND APPLICATION CONTAINERS</td>\n<td>350</td>\n</tr>\n<tr>\n<td>17.8. CONFIGURING HYPER-THREADING FOR A CLUSTER</td>\n<td>351</td>\n</tr>\n<tr>\n<td>17.9. DISABLING HYPER-THREADING FOR LOW LATENCY APPLICATIONS</td>\n<td>352</td>\n</tr>\n<tr>\n<td>17.10. MANAGING DEVICE INTERRUPT PROCESSING FOR GUARANTEED POD ISOLATED CPUS</td>\n<td>353</td>\n</tr>\n<tr>\n<td> 17.10.1. Finding the effective IRQ affinity setting for a node</td>\n<td>353</td>\n</tr>\n<tr>\n<td> 17.10.2. Configuring node interrupt affinity</td>\n<td>355</td>\n</tr>\n<tr>\n<td>17.11. CONFIGURING MEMORY PAGE SIZES</td>\n<td>356</td>\n</tr>\n<tr>\n<td> 17.11.1. Configuring kernel page sizes</td>\n<td>356</td>\n</tr>\n<tr>\n<td> 17.11.2. Configuring huge pages</td>\n<td>357</td>\n</tr>\n<tr>\n<td> 17.11.3. Allocating multiple huge page sizes</td>\n<td>358</td>\n</tr>\n<tr>\n<td>17.12. REDUCING NIC QUEUES USING THE NODE TUNING OPERATOR</td>\n<td>359</td>\n</tr>\n<tr>\n<td> 17.12.1. Adjusting the NIC queues with the performance profile</td>\n<td>359</td>\n</tr>\n<tr>\n<td> 17.12.2. Verifying the queue status</td>\n<td>362</td>\n</tr>\n<tr>\n<td> 17.12.3. Logging associated with adjusting NIC queues</td>\n<td>366</td>\n</tr>\n<tr>\n<td><b>CHAPTER 18. TUNING HOSTED CONTROL PLANES FOR LOW LATENCY WITH THE PERFORMANCE PROFILE</b> .....</td>\n<td><b>367</b></td>\n</tr>\n<tr>\n<td>18.1. CREATING A PERFORMANCE PROFILE FOR HOSTED CONTROL PLANES</td>\n<td>367</td>\n</tr>\n<tr>\n<td> 18.1.1. Gathering data about your hosted control planes cluster for the PPC</td>\n<td>367</td>\n</tr>\n</table>\n\n---<table>\n<tr>\n<td>18.1.2. Running the Performance Profile Creator on a hosted cluster using Podman</td>\n<td>369</td>\n</tr>\n<tr>\n<td>18.1.3. Configuring low-latency tuning in a hosted cluster</td>\n<td>371</td>\n</tr>\n<tr>\n<td><b>CHAPTER 19. PROVISIONING REAL-TIME AND LOW LATENCY WORKLOADS</b> .....</td>\n<td><b>375</b></td>\n</tr>\n<tr>\n<td>19.1. SCHEDULING A LOW LATENCY WORKLOAD ONTO A COMPUTE NODE</td>\n<td>375</td>\n</tr>\n<tr>\n<td>19.2. CREATING A POD WITH A GUARANTEED QOS CLASS</td>\n<td>378</td>\n</tr>\n<tr>\n<td>19.3. DISABLING CPU LOAD BALANCING IN A POD</td>\n<td>380</td>\n</tr>\n<tr>\n<td>19.4. DISABLING POWER SAVING MODE FOR HIGH PRIORITY PODS</td>\n<td>381</td>\n</tr>\n<tr>\n<td>19.5. DISABLING CPU CFS QUOTA</td>\n<td>382</td>\n</tr>\n<tr>\n<td>19.6. CONFIGURING INTERRUPT PROCESSING FOR INDIVIDUAL PODS</td>\n<td>383</td>\n</tr>\n<tr>\n<td><b>CHAPTER 20. DEBUGGING LOW LATENCY NODE TUNING STATUS</b> .....</td>\n<td><b>386</b></td>\n</tr>\n<tr>\n<td>20.1. DEBUGGING LOW LATENCY CNF TUNING STATUS</td>\n<td>386</td>\n</tr>\n<tr>\n<td>20.2. MACHINE CONFIG POOLS</td>\n<td>387</td>\n</tr>\n<tr>\n<td>20.3. ABOUT THE MUST-GATHER TOOL</td>\n<td>388</td>\n</tr>\n<tr>\n<td>20.4. COLLECTING LOW LATENCY TUNING DEBUGGING DATA FOR RED HAT SUPPORT</td>\n<td>388</td>\n</tr>\n<tr>\n<td><b>CHAPTER 21. PERFORMING LATENCY TESTS FOR PLATFORM VERIFICATION</b> .....</td>\n<td><b>391</b></td>\n</tr>\n<tr>\n<td>21.1. PREREQUISITES FOR RUNNING LATENCY TESTS</td>\n<td>391</td>\n</tr>\n<tr>\n<td>21.2. MEASURING LATENCY</td>\n<td>391</td>\n</tr>\n<tr>\n<td>21.3. RUNNING THE LATENCY TESTS</td>\n<td>393</td>\n</tr>\n<tr>\n<td>21.3.1. Running hwlatdetect</td>\n<td>394</td>\n</tr>\n<tr>\n<td>21.3.2. Example hwlatdetect test results</td>\n<td>396</td>\n</tr>\n<tr>\n<td>21.3.3. Running cyclictest</td>\n<td>397</td>\n</tr>\n<tr>\n<td>21.3.4. Example cyclictest results</td>\n<td>399</td>\n</tr>\n<tr>\n<td>21.3.5. Running oslat</td>\n<td>400</td>\n</tr>\n<tr>\n<td>21.4. GENERATING A LATENCY TEST FAILURE REPORT</td>\n<td>402</td>\n</tr>\n<tr>\n<td>21.5. GENERATING A JUNIT LATENCY TEST REPORT</td>\n<td>402</td>\n</tr>\n<tr>\n<td>21.6. RUNNING LATENCY TESTS ON A SINGLE-NODE OPENSHIFT CLUSTER</td>\n<td>403</td>\n</tr>\n<tr>\n<td>21.7. RUNNING LATENCY TESTS IN A DISCONNECTED CLUSTER</td>\n<td>404</td>\n</tr>\n<tr>\n<td>21.7.1. Mirroring the images to a custom registry accessible from the cluster</td>\n<td>404</td>\n</tr>\n<tr>\n<td>21.7.2. Configuring the tests to consume images from a custom registry</td>\n<td>405</td>\n</tr>\n<tr>\n<td>21.7.3. Mirroring images to the cluster OpenShift image registry</td>\n<td>405</td>\n</tr>\n<tr>\n<td>21.7.4. Mirroring a different set of test images</td>\n<td>406</td>\n</tr>\n<tr>\n<td>21.8. TROUBLESHOOTING ERRORS WITH THE CNF-TESTS CONTAINER</td>\n<td>407</td>\n</tr>\n<tr>\n<td><b>CHAPTER 22. IMPROVING CLUSTER STABILITY IN HIGH LATENCY ENVIRONMENTS USING WORKER LATENCY PROFILES</b> .....</td>\n<td><b>408</b></td>\n</tr>\n<tr>\n<td>22.1. UNDERSTANDING WORKER LATENCY PROFILES</td>\n<td>408</td>\n</tr>\n<tr>\n<td>22.2. IMPLEMENTING WORKER LATENCY PROFILES AT CLUSTER CREATION</td>\n<td>411</td>\n</tr>\n<tr>\n<td>22.3. USING AND CHANGING WORKER LATENCY PROFILES</td>\n<td>412</td>\n</tr>\n<tr>\n<td>22.4. DISPLAYING RESULTING VALUES OF WORKER LATENCY PROFILE</td>\n<td>415</td>\n</tr>\n<tr>\n<td><b>CHAPTER 23. WORKLOAD PARTITIONING</b> .....</td>\n<td><b>417</b></td>\n</tr>\n<tr>\n<td>23.1. ENABLING WORKLOAD PARTITIONING</td>\n<td>417</td>\n</tr>\n<tr>\n<td>23.2. PERFORMANCE PROFILES AND WORKLOAD PARTITIONING</td>\n<td>418</td>\n</tr>\n<tr>\n<td><b>CHAPTER 24. USING THE NODE OBSERVABILITY OPERATOR</b> .....</td>\n<td><b>421</b></td>\n</tr>\n<tr>\n<td>24.1. WORKFLOW OF THE NODE OBSERVABILITY OPERATOR</td>\n<td>421</td>\n</tr>\n<tr>\n<td>24.2. INSTALLING THE NODE OBSERVABILITY OPERATOR</td>\n<td>421</td>\n</tr>\n<tr>\n<td>24.2.1. Installing the Node Observability Operator using the CLI</td>\n<td>421</td>\n</tr>\n<tr>\n<td>24.2.2. Installing the Node Observability Operator using the web console</td>\n<td>423</td>\n</tr>\n<tr>\n<td>24.3. REQUESTING CRI-O AND KUBELET PROFILING DATA USING THE NODE OBSERVABILITY OPERATOR</td>\n<td>424</td>\n</tr>\n<tr>\n<td>24.3.1. Creating the Node Observability custom resource</td>\n<td>424</td>\n</tr>\n</table><table><tr><td>24.3.2. Running the profiling query</td><td>425</td></tr><tr><td>24.4. NODE OBSERVABILITY OPERATOR SCRIPTING</td><td>427</td></tr><tr><td>24.4.1. Creating the Node Observability custom resource for scripting</td><td>427</td></tr><tr><td>24.4.2. Configuring Node Observability Operator scripting</td><td>428</td></tr><tr><td>24.5. ADDITIONAL RESOURCES</td><td>430</td></tr></table># CHAPTER 1. OPENSHIFT CONTAINER PLATFORM SCALABILITY AND PERFORMANCE OVERVIEW\n\nOpenShift Container Platform provides best practices and tools to help you optimize the performance and scale of your clusters. The following documentation provides information on recommended performance and scalability practices, reference design specifications, optimization, and low latency tuning.\n\nTo contact Red Hat support, see [Getting support](#).\n\n## NOTE\n\nSome performance and scalability Operators have release cycles that are independent from OpenShift Container Platform release cycles. For more information, see [OpenShift Operators](#).\n\n## 1.1. RECOMMENDED PERFORMANCE AND SCALABILITY PRACTICES\n\n[Recommended control plane practices](#)\n\n[Recommended infrastructure practices](#)\n\n## 1.2. TELCO REFERENCE DESIGN SPECIFICATIONS\n\n[Telco RAN DU reference design specification for OpenShift Container Platform 4.21](#)\n\n[Telco core reference design specification](#)\n\n## 1.3. PLANNING, OPTIMIZATION, AND MEASUREMENT\n\n[Planning your environment according to object maximums](#)\n\n[Recommended practices for IBM Z and IBM LinuxONE](#)\n\n[Using the Node Tuning Operator](#)\n\n[Using CPU Manager and Topology Manager](#)\n\n[Scheduling NUMA-aware workloads](#)\n\n[Optimizing storage, routing, networking and CPU usage](#)\n\n[Managing bare metal hosts and events](#)\n\n[What are huge pages and how are they used by apps](#)\n\n[Low latency tuning for improving cluster stability and partitioning workload](#)\n\n[Improving cluster stability in high latency environments using worker latency profiles](#)\n\n[Workload partitioning](#)\n\n[Using the Node Observability Operator](#)## CHAPTER 2. RECOMMENDED PERFORMANCE AND SCALABILITY PRACTICES\n\n### 2.1. RECOMMENDED CONTROL PLANE PRACTICES\n\nTo ensure optimal performance and scalability, apply the recommended practices for OpenShift Container Platform control planes. By understanding these recommended practices, you can configure your environment to handle increasing workloads while maintaining stability.\n\n#### 2.1.1. Recommended practices for scaling the cluster\n\nTo scale your cluster effectively, apply the recommended practices for installations with cloud provider integration. By understanding this guidance, you can optimize performance and ensure stability as you increase the size of your environment.\n\nApply the following best practices to scale the number of compute machines in your OpenShift Container Platform cluster. You scale the worker machines by increasing or decreasing the number of replicas that are defined in the compute machine set.\n\nWhen scaling up the cluster to higher node counts:\n\n- • Spread nodes across all of the available zones for higher availability.\n- • Scale up by no more than 25 to 50 machines at once.\n- • Consider creating new compute machine sets in each available zone with alternative instance types of similar size to help mitigate any periodic provider capacity constraints. For example, on AWS, use **m5.large** and **m5d.large**.\n\n#### NOTE\n\nCloud providers might implement a quota for API services. Therefore, gradually scale the cluster.\n\nThe controller might not be able to create the machines if the replicas in the compute machine sets are set to higher numbers all at one time. The number of requests the cloud platform, which OpenShift Container Platform is deployed on top of, is able to handle impacts the process. The controller starts to query more while trying to create, check, and update the machines with the status. The cloud platform on which OpenShift Container Platform is deployed has API request limits; excessive queries might lead to machine creation failures due to cloud platform limitations.\n\nEnable machine health checks when scaling to large node counts. In case of failures, the health checks monitor the condition and automatically repair unhealthy machines.\n\n#### NOTE\n\nWhen scaling large and dense clusters to lower node counts, it might take large amounts of time because the process involves draining or evicting the objects running on the nodes being terminated in parallel. Also, the client might start to throttle the requests if there are too many objects to evict. The default client queries per second (QPS) and burst rates are currently set to **50** and **100** respectively. These values cannot be modified in OpenShift Container Platform.### 2.1.2. Control plane node sizing\n\nTo ensure optimal performance and stability, determine the resource requirements for control plane nodes. These sizing guidelines depend on the number and type of nodes and objects in your cluster.\n\nThe following control plane node size recommendations are based on the results of a control plane density focused testing, or *Cluster-density*. This test creates the following objects across a given number of namespaces:\n\n- • 1 image stream\n- • 1 build\n- • 5 deployments, with 2 pod replicas in a **sleep** state, mounting 4 secrets, 4 config maps, and 1 downward API volume each\n- • 5 services, each one pointing to the TCP/8080 and TCP/8443 ports of one of the previous deployments\n- • 1 route pointing to the first of the previous services\n- • 10 secrets containing 2048 random string characters\n- • 10 config maps containing 2048 random string characters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Number of compute nodes</th>\n<th>Cluster-density (namespaces)</th>\n<th>CPU cores</th>\n<th>Memory (GB)</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>24</td>\n<td>500</td>\n<td>4</td>\n<td>16</td>\n</tr>\n<tr>\n<td>120</td>\n<td>1000</td>\n<td>8</td>\n<td>32</td>\n</tr>\n<tr>\n<td>252</td>\n<td>4000</td>\n<td>16, but 24 if using the OVN-Kubernetes network plug-in</td>\n<td>64, but 128 if using the OVN-Kubernetes network plug-in</td>\n</tr>\n<tr>\n<td>501, but untested with the OVN-Kubernetes network plug-in</td>\n<td>4000</td>\n<td>16</td>\n<td>96</td>\n</tr>\n</tbody>\n</table>\n\nThe data from the table above is based on an OpenShift Container Platform running on top of AWS, using r5.4xlarge instances as control-plane nodes and m5.2xlarge instances as compute nodes.\n\nOn a large and dense cluster with three control plane nodes, the CPU and memory usage will spike up when one of the nodes is stopped, rebooted, or fails. The failures can be due to unexpected issues with power, network, underlying infrastructure, or intentional cases where the cluster is restarted after shutting it down to save costs. The remaining two control plane nodes must handle the load in order to be highly available, which leads to increase in the resource usage. This is also expected during upgrades because the control plane nodes are cordoned, drained, and rebooted serially to apply the operating system updates, as well as the control plane Operators update. To avoid cascading failures, keep the overall CPU and memory resource usage on the control plane nodes to at most 60% of all available capacity to handle the resource usage spikes. Increase the CPU and memory on the control plane nodes accordingly to avoid potential downtime due to lack of resources.## IMPORTANT\n\nThe node sizing varies depending on the number of nodes and object counts in the cluster. It also depends on whether the objects are actively being created on the cluster. During object creation, the control plane is more active in terms of resource usage compared to when the objects are in the **Running** phase.\n\nOperator Lifecycle Manager (OLM) runs on the control plane nodes and its memory footprint depends on the number of namespaces and user installed operators that OLM needs to manage on the cluster. Control plane nodes need to be sized accordingly to avoid OOM kills. Following data points are based on the results from cluster maximums testing.\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Number of namespaces</th>\n<th>OLM memory at idle state (GB)</th>\n<th>OLM memory with 5 user operators installed (GB)</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>500</td>\n<td>0.823</td>\n<td>1.7</td>\n</tr>\n<tr>\n<td>1000</td>\n<td>1.2</td>\n<td>2.5</td>\n</tr>\n<tr>\n<td>1500</td>\n<td>1.7</td>\n<td>3.2</td>\n</tr>\n<tr>\n<td>2000</td>\n<td>2</td>\n<td>4.4</td>\n</tr>\n<tr>\n<td>3000</td>\n<td>2.7</td>\n<td>5.6</td>\n</tr>\n<tr>\n<td>4000</td>\n<td>3.8</td>\n<td>7.6</td>\n</tr>\n<tr>\n<td>5000</td>\n<td>4.2</td>\n<td>9.02</td>\n</tr>\n<tr>\n<td>6000</td>\n<td>5.8</td>\n<td>11.3</td>\n</tr>\n<tr>\n<td>7000</td>\n<td>6.6</td>\n<td>12.9</td>\n</tr>\n<tr>\n<td>8000</td>\n<td>6.9</td>\n<td>14.8</td>\n</tr>\n<tr>\n<td>9000</td>\n<td>8</td>\n<td>17.7</td>\n</tr>\n<tr>\n<td>10,000</td>\n<td>9.9</td>\n<td>21.6</td>\n</tr>\n</tbody>\n</table>## IMPORTANT\n\nYou can modify the control plane node size in a running OpenShift Container Platform 4.21 cluster for the following configurations only:\n\n- • Clusters installed with a user-provisioned installation method.\n- • AWS clusters installed with an installer-provisioned infrastructure installation method.\n- • Clusters that use a control plane machine set to manage control plane machines.\n\nFor all other configurations, you must estimate your total node count and use the suggested control plane node size during installation.\n\n## NOTE\n\nIn OpenShift Container Platform 4.21, half of a CPU core (500 millicore) is now reserved by the system by default compared to OpenShift Container Platform 3.11 and previous versions. The sizes are determined taking that into consideration.\n\n## 2.2. SELECTING A LARGER AWS INSTANCE TYPE FOR CONTROL PLANE MACHINES\n\nIf the control plane machines in an Amazon Web Services (AWS) cluster require more resources, you can select a larger AWS instance type for the control plane machines to use.\n\n## NOTE\n\nThe procedure for clusters that use a control plane machine set is different from the procedure for clusters that do not use a control plane machine set.\n\nIf you are uncertain about the state of the **ControlPlaneMachineSet** CR in your cluster, you can verify the CR status.\n\n### 2.2.1. Additional resources\n\n- • [Verify the CR status](#)\n\n### 2.2.2. Changing the Amazon Web Services instance type by using a control plane machine set\n\nYou can change the Amazon Web Services (AWS) instance type that your control plane machines use by updating the specification in the control plane machine set custom resource (CR).\n\n#### Prerequisites\n\n- • Your AWS cluster uses a control plane machine set.\n\n#### Procedure\n\n1. 1. Edit the following line under the **providerSpec** field:\n\n```\nproviderSpec:\n``````\nvalue: \n... \ninstanceType: <compatible_aws_instance_type>\n```\n\n- • **<compatible\\_aws\\_instance\\_type>**: Specifies a larger AWS instance type with the same base as the previous selection. For example, you can change **m6i.xlarge** to **m6i.2xlarge** or **m6i.4xlarge**.\n\n2. Save your changes.\n\n#### Additional resources\n\n- • [Managing control plane machines with control plane machine sets](#)\n\n### 2.2.3. Changing the Amazon Web Services instance type by using the AWS console\n\nYou can change the Amazon Web Services (AWS) instance type that your control plane machines use by updating the instance type in the AWS console.\n\n#### Prerequisites\n\n- • You have access to the AWS console with the permissions required to modify the EC2 Instance for your cluster.\n- • You have access to the OpenShift Container Platform cluster as a user with the **cluster-admin** role.\n\n#### Procedure\n\n1. 1. Open the AWS console and fetch the instances for the control plane machines.\n2. 2. Choose one control plane machine instance.\n 1. a. For the selected control plane machine, back up the etcd data by creating an etcd snapshot. For more information, see \"Backing up etcd\".\n 2. b. In the AWS console, stop the control plane machine instance.\n 3. c. Select the stopped instance, and click **Actions → Instance Settings → Change instance type**.\n 4. d. Change the instance to a larger type, ensuring that the type is the same base as the previous selection, and apply changes. For example, you can change **m6i.xlarge** to **m6i.2xlarge** or **m6i.4xlarge**.\n 5. e. Start the instance.\n 6. f. If your OpenShift Container Platform cluster has a corresponding **Machine** object for the instance, update the instance type of the object to match the instance type set in the AWS console.\n3. 3. Repeat this process for each control plane machine.\n\n#### Additional resources- • [Backing up etcd](#)\n- • [AWS documentation about changing the instance type](#)\n\n## 2.3. RECOMMENDED INFRASTRUCTURE PRACTICES\n\nThis topic provides recommended performance and scalability practices for infrastructure in OpenShift Container Platform.\n\n### 2.3.1. Infrastructure node sizing\n\n*Infrastructure nodes* are nodes that are labeled to run pieces of the OpenShift Container Platform environment. The infrastructure node resource requirements depend on the cluster age, nodes, and objects in the cluster, as these factors can lead to an increase in the number of metrics or time series in Prometheus. The following infrastructure node size recommendations are based on the results observed in cluster-density testing detailed in the **Control plane node sizing** section, where the monitoring stack and the default ingress-controller were moved to these nodes.\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Number of worker nodes</th>\n<th>Cluster density, or number of namespaces</th>\n<th>CPU cores</th>\n<th>Memory (GB)</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>27</td>\n<td>500</td>\n<td>4</td>\n<td>24</td>\n</tr>\n<tr>\n<td>120</td>\n<td>1000</td>\n<td>8</td>\n<td>48</td>\n</tr>\n<tr>\n<td>252</td>\n<td>4000</td>\n<td>16</td>\n<td>128</td>\n</tr>\n<tr>\n<td>501</td>\n<td>4000</td>\n<td>32</td>\n<td>128</td>\n</tr>\n</tbody>\n</table>\n\nIn general, three infrastructure nodes are recommended per cluster.\n\n#### IMPORTANT\n\nThese sizing recommendations should be used as a guideline. Prometheus is a highly memory intensive application; the resource usage depends on various factors including the number of nodes, objects, the Prometheus metrics scraping interval, metrics or time series, and the age of the cluster. In addition, the router resource usage can also be affected by the number of routes and the amount/type of inbound requests.\n\nThese recommendations apply only to infrastructure nodes hosting Monitoring, Ingress and Registry infrastructure components installed during cluster creation.\n\n#### NOTE\n\nIn OpenShift Container Platform 4.21, half of a CPU core (500 millicore) is now reserved by the system by default compared to OpenShift Container Platform 3.11 and previous versions. This influences the stated sizing recommendations.\n\n### 2.3.2. Scaling the Cluster Monitoring Operator\n\nOpenShift Container Platform exposes metrics that the Cluster Monitoring Operator (CMO) collectsand stores in the Prometheus-based monitoring stack. As an administrator, you can view dashboards for system resources, containers, and components metrics in the OpenShift Container Platform web console by navigating to **Observe → Dashboards**.\n\n### 2.3.3. Prometheus database storage requirements\n\nRed Hat performed various tests for different scale sizes.\n\n#### NOTE\n\n- • The following Prometheus storage requirements are not prescriptive and should be used as a reference. Higher resource consumption might be observed in your cluster depending on workload activity and resource density, including the number of pods, containers, routes, or other resources exposing metrics collected by Prometheus.\n- • You can configure the size-based data retention policy to suit your storage requirements.\n\n**Table 2.1. Prometheus Database storage requirements based on number of nodes/pods in the cluster**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Number of nodes</th>\n<th>Number of pods<br/>(2 containers per pod)</th>\n<th>Prometheus storage growth per day</th>\n<th>Prometheus storage growth per 15 days</th>\n<th>Network (per tsdb chunk)</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>50</td>\n<td>1800</td>\n<td>6.3 GB</td>\n<td>94 GB</td>\n<td>16 MB</td>\n</tr>\n<tr>\n<td>100</td>\n<td>3600</td>\n<td>13 GB</td>\n<td>195 GB</td>\n<td>26 MB</td>\n</tr>\n<tr>\n<td>150</td>\n<td>5400</td>\n<td>19 GB</td>\n<td>283 GB</td>\n<td>36 MB</td>\n</tr>\n<tr>\n<td>200</td>\n<td>7200</td>\n<td>25 GB</td>\n<td>375 GB</td>\n<td>46 MB</td>\n</tr>\n</tbody>\n</table>\n\nApproximately 20 percent of the expected size was added as overhead to ensure that the storage requirements do not exceed the calculated value.\n\nThe above calculation is for the default OpenShift Container Platform Cluster Monitoring Operator.\n\n#### NOTE\n\nCPU utilization has minor impact. The ratio is approximately 1 core out of 40 per 50 nodes and 1800 pods.\n\n#### Recommendations for OpenShift Container Platform\n\n- • Use at least two infrastructure (infra) nodes.\n- • Use at least three **openshift-container-storage** nodes with non-volatile memory express (SSD or NVMe) drives.### 2.3.4. Configuring cluster monitoring\n\nYou can increase the storage capacity for the Prometheus component in the cluster monitoring stack.\n\n#### Procedure\n\nTo increase the storage capacity for Prometheus:\n\n1. 1. Create a YAML configuration file, **cluster-monitoring-config.yaml**. For example:\n\n```\napiVersion: v1\nkind: ConfigMap\ndata:\n config.yaml: |\n prometheusK8s:\n retention: {{PROMETHEUS_RETENTION_PERIOD}} 1\n nodeSelector:\n node-role.kubernetes.io/infra: \"\"\n volumeClaimTemplate:\n spec:\n storageClassName: {{STORAGE_CLASS}} 2\n resources:\n requests:\n storage: {{PROMETHEUS_STORAGE_SIZE}} 3\n alertmanagerMain:\n nodeSelector:\n node-role.kubernetes.io/infra: \"\"\n volumeClaimTemplate:\n spec:\n storageClassName: {{STORAGE_CLASS}} 4\n resources:\n requests:\n storage: {{ALERTMANAGER_STORAGE_SIZE}} 5\n metadata:\n name: cluster-monitoring-config\n namespace: openshift-monitoring\n```\n\n1. 1 The default value of Prometheus retention is **PROMETHEUS\\_RETENTION\\_PERIOD=15d**. Units are measured in time using one of these suffixes: s, m, h, d.\n2. 2 4 The storage class for your cluster.\n3. 3 A typical value is **PROMETHEUS\\_STORAGE\\_SIZE=200Gi**. Storage values can be a plain integer or a fixed-point integer using one of these suffixes: E, P, T, G, M, K. You can also use the power-of-two equivalents: Ei, Pi, Ti, Gi, Mi, Ki.\n4. 5 A typical value is **ALERTMANAGER\\_STORAGE\\_SIZE=20Gi**. Storage values can be a plain integer or a fixed-point integer using one of these suffixes: E, P, T, G, M, K. You can also use the power-of-two equivalents: Ei, Pi, Ti, Gi, Mi, Ki.\n\n1. 2. Add values for the retention period, storage class, and storage sizes.\n2. 3. Save the file.1. 4. Apply the changes by running:\n\n```\n$ oc create -f cluster-monitoring-config.yaml\n```\n\n### 2.3.5. Additional resources\n\n- • [Infrastructure Nodes in OpenShift 4](#)\n- • [OpenShift Container Platform cluster maximums](#)\n- • [Creating infrastructure machine sets](#)# CHAPTER 3. TELCO CORE REFERENCE DESIGN SPECIFICATIONS\n\nThe telco core reference design specifications (RDS) configures an OpenShift Container Platform cluster running on commodity hardware to host telco core workloads.\n\n## 3.1. TELCO CORE RDS USE MODEL OVERVIEW\n\nThe Telco core reference design specification (RDS) describes a platform that supports large-scale telco applications including control plane functions such as signaling and aggregation. It also includes some centralized data plane functions, for example, user plane functions (UPF). These functions generally require scalability, complex networking support, resilient software-defined storage, and support performance requirements that are less stringent and constrained than far-edge deployments such as RAN.\n\n## 3.2. ABOUT THE TELCO CORE CLUSTER USE MODEL\n\nThe telco core cluster use model is designed for clusters running on commodity hardware. Telco core clusters support large scale telco applications including control plane functions like signaling, aggregation, session border controller (SBC), and centralized data plane functions such as 5G user plane functions (UPF). Telco core cluster functions require scalability, complex networking support, resilient software-defined storage, and support performance requirements that are less stringent and constrained than far-edge RAN deployments.\n\nNetworking requirements for telco core functions vary widely across a range of networking features and performance points. IPv6 is a requirement and dual-stack is common. Some functions need maximum throughput and transaction rate and require support for user-plane DPDK networking. Other functions use typical cloud-native patterns and can rely on OVN-Kubernetes, kernel networking, and load balancing.\n\nTelco core clusters are configured as standard with three control plane and one or more worker nodes configured with the stock (non-RT) kernel. In support of workloads with varying networking and performance requirements, you can segment worker nodes by using **MachineConfigPool** custom resources (CR), for example, for non-user data plane or high-throughput use cases. In support of required telco operational features, core clusters have a standard set of Day 2 OLM-managed Operators installed.Figure 3.1. Telco core RDS cluster service-based architecture and networking topology\n\n**5G core cluster**\n\n5G core network functions\n\nNWDAF, NSFF, AUSF, UDM, NRF, NEF, AF\n\nAMF, SMF, PCF, CHF\n\nUE, RAN, UPF, DN\n\nInternet\n\nLegend:\n\n- Kubernetes networking (REST) \n OVN-K, metalLB\n- Control plane networking \n OVN-K, MAC-VLAN, kernel SR-IOV\n- Data plane networking \n SR-IOV with DPDK\n\n### 3.3. REFERENCE DESIGN SCOPE\n\nThe telco core, telco RAN and telco hub reference design specifications (RDS) capture the recommended, tested, and supported configurations to get reliable and repeatable performance for clusters running the telco core and telco RAN profiles.\n\nEach RDS includes the released features and supported configurations that are engineered and validated for clusters to run the individual profiles. The configurations provide a baseline OpenShift Container Platform installation that meets feature and KPI targets. Each RDS also describes expected variations for each individual configuration. Validation of each RDS includes many long duration and at-scale tests.\n\n#### NOTE\n\nThe validated reference configurations are updated for each major Y-stream release of OpenShift Container Platform. Z-stream patch releases are periodically re-tested against the reference configurations.\n\n### 3.4. DEVIATIONS FROM THE REFERENCE DESIGN\n\nDeviating from the validated telco core, telco RAN DU, and telco hub reference design specifications (RDS) can have significant impact beyond the specific component or feature that you change. Deviations require analysis and engineering in the context of the complete solution.## IMPORTANT\n\nAll deviations from the RDS should be analyzed and documented with clear action tracking information. Due diligence is expected from partners to understand how to bring deviations into line with the reference design. This might require partners to provide additional resources to engage with Red Hat to work towards enabling their use case to achieve a best in class outcome with the platform. This is critical for the supportability of the solution and ensuring alignment across Red Hat and with partners.\n\nDeviation from the RDS can have some or all of the following consequences:\n\n- • It can take longer to resolve issues.\n- • There is a risk of missing project service-level agreements (SLAs), project deadlines, end provider performance requirements, and so on.\n- • Unapproved deviations may require escalation at executive levels.\n\n## NOTE\n\nRed Hat prioritizes the servicing of requests for deviations based on partner engagement priorities.\n\n## 3.5. TELCO CORE COMMON BASELINE MODEL\n\nThe following configurations and use models are applicable to all telco core use cases. The telco core use cases build on this common baseline of features.\n\n### Cluster topology\n\nThe telco core reference design supports two distinct cluster configuration variants:\n\n- • A non-schedulable control plane variant, where user workloads are strictly prohibited from running on master nodes.\n- • A schedulable control plane variant, which allows for user workloads to run on master nodes to optimize resource utilization. This variant is only applicable to bare-metal control plane nodes and must be configured at installation time.\n\nAll clusters, regardless of the variant, must conform to the following requirements:\n\n- • A highly available control plane consisting of three or more nodes.\n- • The use of multiple machine config pools.\n\n### Storage\n\nTelco core use cases require highly available persistent storage as provided by an external storage solution. OpenShift Data Foundation might be used to manage access to the external storage.\n\n### Networking\n\nTelco core cluster networking conforms to the following requirements:\n\n- • Dual stack IPv4/IPv6 (IPv4 primary).\n- • Fully disconnected - clusters do not have access to public networking at any point in their lifecycle.- • Supports multiple networks. Segmented networking provides isolation between operations, administration and maintenance (OAM), signaling, and storage traffic.\n- • Cluster network type is OVN-Kubernetes as required for IPv6 support.\n- • Telco core clusters have multiple layers of networking supported by underlying RHCOS, SR-IOV Network Operator, Load Balancer and other components. These layers include the following:\n - ◦ Cluster networking layer. The cluster network configuration is defined and applied through the installation configuration. Update the configuration during Day 2 operations with the NMSState Operator. Use the initial configuration to establish the following:\n - ■ Host interface configuration.\n - ■ Active/active bonding (LACP).\n - ◦ Secondary/additional network layer. Configure the OpenShift Container Platform CNI through network **additionalNetwork** or **NetworkAttachmentDefinition** CRs. Use the initial configuration to configure MACVLAN virtual network interfaces.\n - ◦ Application workload layer. User plane networking runs in cloud-native network functions (CNFs).\n\n### Service Mesh\n\nTelco CNFs can use Service Mesh. Telco core clusters typically include a Service Mesh implementation. The choice of implementation and configuration is outside the scope of this specification.\n\n## 3.6. DEPLOYMENT PLANNING\n\nProper deployment planning is essential for telco core clusters to ensure high availability, minimize service disruption during upgrades, and optimize cluster performance.\n\n### 3.6.1. Worker Nodes and MachineConfigPools\n\n**MachineConfigPools** (MCPs) custom resources (CR) enable the subdivision of worker nodes in telco core clusters into different node groups based on customer planning parameters. Careful deployment planning using MCPs is crucial to minimize deployment and upgrade time and, more importantly, to minimize interruption of telco-grade services during cluster upgrades.\n\n#### Description\n\nTelco core clusters can use **MachineConfigPools** (MCPs) to split worker nodes into additional separate roles, for example, due to different hardware profiles. This allows custom tuning for each role and also plays a critical function in speeding up a telco core cluster deployment or upgrade. Multiple MCPs can be used to properly plan cluster upgrades across one or multiple maintenance windows. This is crucial because telco-grade services might otherwise be affected if careful planning is not considered.\n\nDuring cluster upgrades, you can pause MCPs while you upgrade the control plane. See \"Performing a canary rollout update\" for more information. This ensures that worker nodes are not rebooted and running workloads remain unaffected until the MCP is unpaused.Using careful MCP planning, you can control the timing and order of which set of nodes are upgraded at any time. For more information on how to use MCPs to plan telco upgrades, see \"Applying MachineConfigPool labels to nodes before the update\".\n\nBefore beginning the initial deployment, review the following engineering considerations:\n\n### PerformanceProfile and Tuned profile association:\n\nWhen using PerformanceProfiles, remember that each Machine Config Pool (MCP) must be linked to exactly one PerformanceProfile or Tuned profile definition. Consequently, even if the desired configuration is identical for multiple MCPs, each MCP still requires its own dedicated PerformanceProfile definition.\n\n### Planning your MCP labeling strategy:\n\nPlan your MCP labeling with an appropriate strategy to split your worker nodes depending on parameters such as:\n\n- ● The worker node type: identifying a group of nodes with equivalent hardware profile, for example workers for control plane Network Functions (NFs) and workers for user data plane NFs.\n- ● The number of worker nodes per worker node type.\n- ● The minimum number of MCPs required for an equivalent hardware profile is 1, but could be larger for larger clusters. For example, you may design for more MCPs per hardware profile to support a more granular upgrade where a smaller percentage of the cluster capacity is affected with each step.\n- ● The update strategy for nodes within an MCP is by upgrade requirements and the chosen **maxUnavailable** value:\n - ○ Number of maintenance windows allowed\n - ○ Duration of a maintenance window\n - ○ Total number of worker nodes\n - ○ Desired **maxUnavailable** (number of nodes updated concurrently) for the MCP.\n- ● CNF requirements for worker nodes, in terms of:\n - ○ Minimum availability per Pod required during an upgrade, configured with a pod disruption budget (PDB). PDBs are crucial to maintain telco service level Agreements (SLAs) during upgrades. For more information about PDB, see \"Understanding how to use pod disruption budgets to specify the number of pods that must be up\".\n - ○ Minimum true high availability required per Pod, such that each replica runs on separate hardware.\n - ○ Pod affinity and anti-affinity link: For more information about how to use pod affinity and anti-affinity, see \"Placing pods relative to other pods using affinity and anti-affinity rules\".\n- ● Duration and number of upgrade maintenance windows during which telco-grade services might be affected.\n\n## 3.6.2. ZonesDesigning the cluster to support disruption of multiple nodes simultaneously is critical for high availability (HA) and reduced upgrade times. OpenShift Container Platform and Kubernetes use the label **topology.kubernetes.io/zone** to create pools of nodes which are subject to a common failure domain. Annotating nodes for topology (availability) zones allows high-availability workloads to spread such that each zone holds only one replica from a set of HA replicated pods. With this spread the loss of a single zone will not violate HA constraints and minimum service availability will be maintained. OpenShift Container Platform and Kubernetes apply a default TopologySpreadConstraint to all replica constructs, such as **Service**, **ReplicaSet**, **StatefulSet** or **ReplicationController** resources, which spreads the replicas based on the **topology.kubernetes.io/zone** label. This default allows zone based spread to apply without any change to your workload pod specs.\n\nCluster upgrades typically result in node disruption as the underlying OS is updated. In large clusters it is necessary to update multiple nodes concurrently in order to complete upgrades quickly and in as few maintenance windows as possible. By using zones to ensure pod spread, an upgrade can be applied to all nodes in a zone simultaneously (assuming sufficient spare capacity) while maintaining high availability and service availability. The recommended cluster design is to partition nodes into multiple MCPs based on the considerations above and label all nodes in a single MCP as a single zone which is distinct from zones attached to other MCPs. Using this strategy all nodes in an MCP can be updated simultaneously.\n\nLifecycle hooks (readiness, liveness, startup and pre-stop) play an important role in ensuring application availability. For upgrades in particular the pre-stop hook allows applications to take necessary steps to prepare for disruption prior to being evicted from the node.\n\n### Limits and requirements\n\n- • The default TopologySpreadConstraints (TSC) only apply when an explicit TSC is not given. If your pods have explicit TSC ensure that spread based on zones is included.\n- • The cluster must have sufficient spare capacity to tolerate simultaneous update of an MCP. Otherwise the **maxUnavailable** of the MCP must be set to less than 100%.\n- • The ability to update all nodes in an MCP simultaneously further depends on workload design and ability to maintain required service levels with that level of disruption.\n\n### Engineering Considerations\n\n- • Pod drain times can significantly impact node update times. Ensure the workload design allows pods to be drained quickly.\n- • PodDisruptionBudgets (PDB) are used to enforce high availability requirements.\n - ◦ With sufficient zones in the cluster design, a zone can be disrupted or lost without violating the PDB. If there are insufficient zones, or other scheduling constraints restrict the set of available nodes, the scheduling of pods might violate the PDB when the zone is disrupted or lost. During upgrades with simultaneous node updates this might lead to partial serialization of updates.\n - ◦ PDB with 0 disruptable pods will block node drain and require administrator intervention. This pattern should be avoided for fast and automated upgrades.\n\n### Additional resources\n\n- • [Performing a canary rollout update](#)\n- • [Applying MachineConfigPool labels to nodes before the update](#)"},"html":{"kind":"string","value":"<h1>OpenShift Container Platform 4.21</h1><h2>Scalability and performance</h2><p>Scaling your OpenShift Container Platform cluster and tuning performance in production environments</p><h2>OpenShift Container Platform 4.21 Scalability and performance</h2><hr/><p>Scaling your OpenShift Container Platform cluster and tuning performance in production environments</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.</p><p>Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.</p><p>Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.</p><p>Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.</p><p>XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.</p><p>The OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.</p><p>All other trademarks are the property of their respective owners.</p><h2>Abstract</h2><p>This document provides instructions for scaling your cluster and optimizing the performance of your OpenShift Container Platform environment.</p>\n<h1>Table of Contents</h1>\n\n<table>\n<tr>\n<td><b>CHAPTER 1. OPENSHIFT CONTAINER PLATFORM SCALABILITY AND PERFORMANCE OVERVIEW</b> .....</td>\n<td><b>11</b></td>\n</tr>\n<tr>\n<td> 1.1. RECOMMENDED PERFORMANCE AND SCALABILITY PRACTICES</td>\n<td>11</td>\n</tr>\n<tr>\n<td> 1.2. TELCO REFERENCE DESIGN SPECIFICATIONS</td>\n<td>11</td>\n</tr>\n<tr>\n<td> 1.3. PLANNING, OPTIMIZATION, AND MEASUREMENT</td>\n<td>11</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. RECOMMENDED PERFORMANCE AND SCALABILITY PRACTICES</b> .....</td>\n<td><b>12</b></td>\n</tr>\n<tr>\n<td> 2.1. RECOMMENDED CONTROL PLANE PRACTICES</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 2.1.1. Recommended practices for scaling the cluster</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 2.1.2. Control plane node sizing</td>\n<td>13</td>\n</tr>\n<tr>\n<td> 2.2. SELECTING A LARGER AWS INSTANCE TYPE FOR CONTROL PLANE MACHINES</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2.1. Additional resources</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2.2. Changing the Amazon Web Services instance type by using a control plane machine set</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2.3. Changing the Amazon Web Services instance type by using the AWS console</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.3. RECOMMENDED INFRASTRUCTURE PRACTICES</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.3.1. Infrastructure node sizing</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.3.2. Scaling the Cluster Monitoring Operator</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.3.3. Prometheus database storage requirements</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.3.4. Configuring cluster monitoring</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 2.3.5. Additional resources</td>\n<td>20</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. TELCO CORE REFERENCE DESIGN SPECIFICATIONS</b> .....</td>\n<td><b>21</b></td>\n</tr>\n<tr>\n<td> 3.1. TELCO CORE RDS USE MODEL OVERVIEW</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.2. ABOUT THE TELCO CORE CLUSTER USE MODEL</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.3. REFERENCE DESIGN SCOPE</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 3.4. DEVIATIONS FROM THE REFERENCE DESIGN</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 3.5. TELCO CORE COMMON BASELINE MODEL</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.6. DEPLOYMENT PLANNING</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.6.1. Worker Nodes and MachineConfigPools</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.6.2. Zones</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.7. TELCO CORE CLUSTER COMMON USE MODEL ENGINEERING CONSIDERATIONS</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.7.1. Application workloads</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.7.2. Signaling workloads</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 3.8. TELCO CORE RDS COMPONENTS</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 3.8.1. CPU partitioning and performance tuning</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 3.8.2. Workloads on schedulable control planes</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.8.3. Service Mesh</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.8.4. Networking</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.8.4.1. Cluster Network Operator</td>\n<td>34</td>\n</tr>\n<tr>\n<td> 3.8.4.2. Load balancer</td>\n<td>36</td>\n</tr>\n<tr>\n<td> 3.8.4.3. SR-IOV</td>\n<td>37</td>\n</tr>\n<tr>\n<td> 3.8.4.4. NMState Operator</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 3.8.5. Logging</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 3.8.6. Power Management</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 3.8.7. Storage</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 3.8.7.1. OpenShift Data Foundation</td>\n<td>40</td>\n</tr>\n<tr>\n<td> 3.8.7.2. Additional storage solutions</td>\n<td>41</td>\n</tr>\n<tr>\n<td> 3.9. TELCO CORE DEPLOYMENT COMPONENTS</td>\n<td>41</td>\n</tr>\n<tr>\n<td> 3.9.1. Red Hat Advanced Cluster Management</td>\n<td>41</td>\n</tr>\n<tr>\n<td> 3.9.2. Topology Aware Lifecycle Manager</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 3.9.3. GitOps Operator and GitOps ZTP plugins</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 3.9.4. Agent-based Installer</td>\n<td>44</td>\n</tr>\n</table>\n\n<table>\n<tr><td>3.10. MONITORING</td><td>44</td></tr>\n<tr><td>3.11. SCHEDULING</td><td>45</td></tr>\n<tr><td>3.12. NODE CONFIGURATION</td><td>46</td></tr>\n<tr><td> 3.12.1. Host firmware and boot loader configuration</td><td>47</td></tr>\n<tr><td> 3.12.2. Kubelet Settings</td><td>48</td></tr>\n<tr><td>3.13. DISCONNECTED ENVIRONMENT</td><td>48</td></tr>\n<tr><td>3.14. SECURITY</td><td>49</td></tr>\n<tr><td>3.15. CERT-MANAGER OPERATOR</td><td>51</td></tr>\n<tr><td>3.16. SCALABILITY</td><td>51</td></tr>\n<tr><td>3.17. TELCO CORE REFERENCE CONFIGURATION CRS</td><td>51</td></tr>\n<tr><td> 3.17.1. Extracting the telco core reference design configuration CRs</td><td>51</td></tr>\n<tr><td> 3.17.2. Comparing a cluster with the telco core reference configuration</td><td>53</td></tr>\n<tr><td> 3.17.3. Node configuration reference CRs</td><td>57</td></tr>\n<tr><td> 3.17.4. Cluster infrastructure reference CRs</td><td>57</td></tr>\n<tr><td> 3.17.5. Resource tuning reference CRs</td><td>59</td></tr>\n<tr><td> 3.17.6. Networking reference CRs</td><td>59</td></tr>\n<tr><td> 3.17.7. Scheduling reference CRs</td><td>63</td></tr>\n<tr><td> 3.17.8. Storage reference CRs</td><td>64</td></tr>\n<tr><td> 3.17.9. Security reference CRs</td><td>65</td></tr>\n<tr><td>3.18. TELCO CORE REFERENCE CONFIGURATION SOFTWARE SPECIFICATIONS</td><td>65</td></tr>\n<tr><td><b>CHAPTER 4. TELCO RAN DU REFERENCE DESIGN SPECIFICATION .....</b></td><td><b>67</b></td></tr>\n<tr><td> 4.1. REFERENCE DESIGN SPECIFICATIONS FOR TELCO RAN DU 5G DEPLOYMENTS</td><td>67</td></tr>\n<tr><td> 4.1.1. Supported CPU architectures for RAN DU</td><td>68</td></tr>\n<tr><td> 4.2. REFERENCE DESIGN SCOPE</td><td>68</td></tr>\n<tr><td> 4.3. DEVIATIONS FROM THE REFERENCE DESIGN</td><td>69</td></tr>\n<tr><td> 4.4. ENGINEERING CONSIDERATIONS FOR THE RAN DU USE MODEL</td><td>69</td></tr>\n<tr><td> 4.5. TELCO RAN DU APPLICATION WORKLOADS</td><td>73</td></tr>\n<tr><td> 4.6. TELCO RAN DU REFERENCE DESIGN COMPONENTS</td><td>74</td></tr>\n<tr><td> 4.6.1. Host firmware tuning</td><td>74</td></tr>\n<tr><td> 4.6.2. Kubelet Settings</td><td>75</td></tr>\n<tr><td> 4.6.3. CPU partitioning and performance tuning</td><td>76</td></tr>\n<tr><td> 4.6.4. PTP Operator</td><td>79</td></tr>\n<tr><td> 4.6.5. SR-IOV Operator</td><td>80</td></tr>\n<tr><td> 4.6.6. Logging</td><td>82</td></tr>\n<tr><td> 4.6.7. SRIOV-FEC Operator</td><td>82</td></tr>\n<tr><td> 4.6.8. Lifecycle Agent</td><td>83</td></tr>\n<tr><td> 4.6.9. Local Storage Operator</td><td>83</td></tr>\n<tr><td> 4.6.10. Logical Volume Manager Storage</td><td>83</td></tr>\n<tr><td> 4.6.11. Workload partitioning</td><td>84</td></tr>\n<tr><td> 4.6.12. Cluster tuning</td><td>85</td></tr>\n<tr><td> 4.6.13. Machine configuration</td><td>87</td></tr>\n<tr><td> 4.7. TELCO RAN DU DEPLOYMENT COMPONENTS</td><td>88</td></tr>\n<tr><td> 4.7.1. Red Hat Advanced Cluster Management</td><td>88</td></tr>\n<tr><td> 4.7.2. SiteConfig Operator</td><td>89</td></tr>\n<tr><td> 4.7.3. Topology Aware Lifecycle Manager</td><td>90</td></tr>\n<tr><td> 4.7.4. GitOps Operator and GitOps ZTP</td><td>91</td></tr>\n<tr><td> 4.7.5. Agent-based installer</td><td>92</td></tr>\n<tr><td> 4.8. TELCO RAN DU REFERENCE CONFIGURATION CRS</td><td>92</td></tr>\n<tr><td> 4.8.1. Cluster tuning reference CRs</td><td>93</td></tr>\n<tr><td> 4.8.2. Day 2 Operators reference CRs</td><td>94</td></tr>\n<tr><td> 4.8.3. Machine configuration reference CRs</td><td>102</td></tr>\n<tr><td> 4.9. COMPARING A CLUSTER WITH THE TELCO RAN DU REFERENCE CONFIGURATION</td><td>103</td></tr>\n</table>\n\n<hr/>\n<table>\n<tr>\n<td>4.10. TELCO RAN DU 4.21 VALIDATED SOFTWARE COMPONENTS</td>\n<td>105</td>\n</tr>\n<tr>\n<td><b>CHAPTER 5. TELCO HUB REFERENCE DESIGN SPECIFICATION</b> .....</td>\n<td><b>107</b></td>\n</tr>\n<tr>\n<td>5.1. REFERENCE DESIGN SCOPE</td>\n<td>107</td>\n</tr>\n<tr>\n<td>5.2. DEVIATIONS FROM THE REFERENCE DESIGN</td>\n<td>107</td>\n</tr>\n<tr>\n<td>5.3. HUB CLUSTER ARCHITECTURE OVERVIEW</td>\n<td>108</td>\n</tr>\n<tr>\n<td>5.4. TELCO MANAGEMENT HUB CLUSTER USE MODEL</td>\n<td>109</td>\n</tr>\n<tr>\n<td>5.5. HUB CLUSTER SCALING TARGET</td>\n<td>110</td>\n</tr>\n<tr>\n<td>5.6. HUB CLUSTER RESOURCE UTILIZATION</td>\n<td>111</td>\n</tr>\n<tr>\n<td>5.7. HUB CLUSTER TOPOLOGY</td>\n<td>111</td>\n</tr>\n<tr>\n<td>5.8. HUB CLUSTER NETWORKING</td>\n<td>112</td>\n</tr>\n<tr>\n<td>5.9. HUB CLUSTER MEMORY AND CPU REQUIREMENTS</td>\n<td>113</td>\n</tr>\n<tr>\n<td>5.10. HUB CLUSTER STORAGE REQUIREMENTS</td>\n<td>114</td>\n</tr>\n<tr>\n<td> 5.10.1. Assisted Service</td>\n<td>114</td>\n</tr>\n<tr>\n<td> 5.10.2. RHACM Observability</td>\n<td>114</td>\n</tr>\n<tr>\n<td> 5.10.3. Storage considerations</td>\n<td>116</td>\n</tr>\n<tr>\n<td>5.11. GIT REPOSITORY</td>\n<td>117</td>\n</tr>\n<tr>\n<td>5.12. OPENSHIFT CONTAINER PLATFORM INSTALLATION ON THE HUB CLUSTER</td>\n<td>117</td>\n</tr>\n<tr>\n<td>5.13. DAY 2 OPERATORS IN THE HUB CLUSTER</td>\n<td>118</td>\n</tr>\n<tr>\n<td>5.14. OBSERVABILITY</td>\n<td>119</td>\n</tr>\n<tr>\n<td>5.15. MANAGED CLUSTER LIFECYCLE MANAGEMENT</td>\n<td>121</td>\n</tr>\n<tr>\n<td> 5.15.1. Managed cluster deployment</td>\n<td>121</td>\n</tr>\n<tr>\n<td> 5.15.2. Managed cluster updates</td>\n<td>122</td>\n</tr>\n<tr>\n<td> 5.15.3. Hub cluster disaster recovery</td>\n<td>124</td>\n</tr>\n<tr>\n<td>5.16. HUB CLUSTER COMPONENTS</td>\n<td>124</td>\n</tr>\n<tr>\n<td> 5.16.1. Red Hat Advanced Cluster Management (RHACM)</td>\n<td>124</td>\n</tr>\n<tr>\n<td> 5.16.2. Topology Aware Lifecycle Manager</td>\n<td>126</td>\n</tr>\n<tr>\n<td> 5.16.3. GitOps Operator and GitOps ZTP</td>\n<td>127</td>\n</tr>\n<tr>\n<td> 5.16.4. Local Storage Operator</td>\n<td>127</td>\n</tr>\n<tr>\n<td> 5.16.5. Red Hat OpenShift Data Foundation</td>\n<td>128</td>\n</tr>\n<tr>\n<td> 5.16.6. Logging</td>\n<td>128</td>\n</tr>\n<tr>\n<td> 5.16.7. OpenShift API for Data Protection</td>\n<td>129</td>\n</tr>\n<tr>\n<td> 5.16.8. cert-manager Operator</td>\n<td>129</td>\n</tr>\n<tr>\n<td>5.17. EXTRACTING THE TELCO HUB REFERENCE DESIGN CONFIGURATION CRS</td>\n<td>130</td>\n</tr>\n<tr>\n<td>5.18. COMPARING A CLUSTER WITH THE TELCO HUB REFERENCE CONFIGURATION</td>\n<td>132</td>\n</tr>\n<tr>\n<td>5.19. HUB CLUSTER REFERENCE CONFIGURATION CRS</td>\n<td>134</td>\n</tr>\n<tr>\n<td>5.20. ADVANCED CLUSTER MANAGEMENT REFERENCE CRS</td>\n<td>135</td>\n</tr>\n<tr>\n<td>5.21. STORAGE REFERENCE CRS</td>\n<td>137</td>\n</tr>\n<tr>\n<td>5.22. GITOPS ZERO TOUCH PROVISIONING (ZTP) REFERENCE CRS</td>\n<td>139</td>\n</tr>\n<tr>\n<td>5.23. LOGGING REFERENCE CRS</td>\n<td>142</td>\n</tr>\n<tr>\n<td>5.24. CONTAINER REGISTRY REFERENCE CRS</td>\n<td>142</td>\n</tr>\n<tr>\n<td>5.25. IMAGE MIRRORING REFERENCE CRS</td>\n<td>143</td>\n</tr>\n<tr>\n<td>5.26. INSTALLATION REFERENCE CRS</td>\n<td>144</td>\n</tr>\n<tr>\n<td>5.27. SECURITY REFERENCE CRS</td>\n<td>144</td>\n</tr>\n<tr>\n<td>5.28. BACKUP RECOVERY REFERENCE CRS</td>\n<td>145</td>\n</tr>\n<tr>\n<td>5.29. TELCO HUB REFERENCE CONFIGURATION SOFTWARE SPECIFICATIONS</td>\n<td>146</td>\n</tr>\n<tr>\n<td><b>CHAPTER 6. COMPARING CLUSTER CONFIGURATIONS</b> .....</td>\n<td><b>148</b></td>\n</tr>\n<tr>\n<td>6.1. UNDERSTANDING THE CLUSTER-COMPARE PLUGIN</td>\n<td>148</td>\n</tr>\n<tr>\n<td> 6.1.1. Overview of the cluster-compare plugin</td>\n<td>148</td>\n</tr>\n<tr>\n<td> 6.1.2. Understanding a reference configuration</td>\n<td>149</td>\n</tr>\n<tr>\n<td> 6.1.3. Additional resources</td>\n<td>150</td>\n</tr>\n<tr>\n<td>6.2. INSTALLING THE CLUSTER-COMPARE PLUGIN</td>\n<td>150</td>\n</tr>\n</table>\n\n<table>\n<tbody>\n<tr>\n<td>6.2.1. Installing the cluster-compare plugin</td>\n<td>150</td>\n</tr>\n<tr>\n<td>6.2.2. Additional resources</td>\n<td>151</td>\n</tr>\n<tr>\n<td>6.3. USING THE CLUSTER-COMPARE PLUGIN</td>\n<td>151</td>\n</tr>\n<tr>\n<td>6.3.1. Using the cluster-compare plugin with a live cluster</td>\n<td>151</td>\n</tr>\n<tr>\n<td>6.3.2. Using the cluster-compare plugin with must-gather data</td>\n<td>153</td>\n</tr>\n<tr>\n<td>6.3.3. Reference cluster-compare plugin options</td>\n<td>156</td>\n</tr>\n<tr>\n<td>6.3.4. Example: Comparing a cluster with the telco core reference configuration</td>\n<td>157</td>\n</tr>\n<tr>\n<td>6.3.5. Additional resources</td>\n<td>161</td>\n</tr>\n<tr>\n<td>6.4. CREATING A REFERENCE CONFIGURATION</td>\n<td>161</td>\n</tr>\n<tr>\n<td>6.4.1. Structure of the metadata.yaml file</td>\n<td>161</td>\n</tr>\n<tr>\n<td>6.4.2. Configuring template relationships</td>\n<td>162</td>\n</tr>\n<tr>\n<td>6.4.3. Configuring expected variation in a template</td>\n<td>163</td>\n</tr>\n<tr>\n<td>6.4.3.1. Reference template functions</td>\n<td>164</td>\n</tr>\n<tr>\n<td>6.4.4. Configuring the metadata.yaml file to exclude template fields</td>\n<td>166</td>\n</tr>\n<tr>\n<td>6.4.4.1. Excluding all fields not specified in a template</td>\n<td>167</td>\n</tr>\n<tr>\n<td>6.4.4.2. Excluding specific fields by setting default exclusion fields</td>\n<td>167</td>\n</tr>\n<tr>\n<td>6.4.4.3. Excluding specific fields</td>\n<td>168</td>\n</tr>\n<tr>\n<td>6.4.4.4. Excluding specific fields by setting default exclusion groups</td>\n<td>168</td>\n</tr>\n<tr>\n<td>6.4.5. Configuring inline validation for template fields</td>\n<td>169</td>\n</tr>\n<tr>\n<td>6.4.5.1. Configuring inline validation with the regex function</td>\n<td>169</td>\n</tr>\n<tr>\n<td>6.4.5.2. Configuring inline validation with the capturegroups function</td>\n<td>170</td>\n</tr>\n<tr>\n<td>6.4.6. Configuring descriptions for the output</td>\n<td>171</td>\n</tr>\n<tr>\n<td>6.5. PERFORMING ADVANCED REFERENCE CONFIGURATION CUSTOMIZATION</td>\n<td>172</td>\n</tr>\n<tr>\n<td>6.5.1. Configuring manual matching between CRs and templates</td>\n<td>172</td>\n</tr>\n<tr>\n<td>6.5.2. Patching a reference configuration</td>\n<td>173</td>\n</tr>\n<tr>\n<td>6.5.2.1. Using the cluster-compare plugin to generate a patch</td>\n<td>174</td>\n</tr>\n<tr>\n<td>6.5.2.2. Creating a patch file manually</td>\n<td>175</td>\n</tr>\n<tr>\n<td>6.6. TROUBLESHOOTING CLUSTER COMPARISONS</td>\n<td>178</td>\n</tr>\n<tr>\n<td>6.6.1. Troubleshooting false positives for missing resources</td>\n<td>178</td>\n</tr>\n<tr>\n<td>6.6.2. Troubleshooting multiple template matches for the same CR</td>\n<td>178</td>\n</tr>\n<tr>\n<td>6.6.3. Additional resources</td>\n<td>178</td>\n</tr>\n<tr>\n<td><b>CHAPTER 7. PLANNING YOUR ENVIRONMENT ACCORDING TO OBJECT MAXIMUMS</b> .....</td>\n<td><b>179</b></td>\n</tr>\n<tr>\n<td>7.1. OPENSHIFT CONTAINER PLATFORM TESTED CLUSTER MAXIMUMS FOR MAJOR RELEASES</td>\n<td>179</td>\n</tr>\n<tr>\n<td>7.2. OPENSHIFT CONTAINER PLATFORM ENVIRONMENT AND CONFIGURATION ON WHICH THE CLUSTER MAXIMUMS ARE TESTED</td>\n<td>183</td>\n</tr>\n<tr>\n<td>7.2.1. AWS cloud platform cluster maximums</td>\n<td>183</td>\n</tr>\n<tr>\n<td>7.2.2. IBM Power platform cluster maximums</td>\n<td>184</td>\n</tr>\n<tr>\n<td>7.2.3. IBM Z platform cluster maximums</td>\n<td>185</td>\n</tr>\n<tr>\n<td>7.3. HOW TO PLAN YOUR ENVIRONMENT ACCORDING TO TESTED CLUSTER MAXIMUMS</td>\n<td>185</td>\n</tr>\n<tr>\n<td>7.4. HOW TO PLAN YOUR ENVIRONMENT ACCORDING TO APPLICATION REQUIREMENTS</td>\n<td>186</td>\n</tr>\n<tr>\n<td><b>CHAPTER 8. USING QUOTAS AND LIMIT RANGES</b> .....</td>\n<td><b>190</b></td>\n</tr>\n<tr>\n<td>8.1. RESOURCES MANAGED BY QUOTA</td>\n<td>190</td>\n</tr>\n<tr>\n<td>8.2. SETTING RESOURCE QUOTA FOR EXTENDED RESOURCES</td>\n<td>192</td>\n</tr>\n<tr>\n<td>8.3. QUOTA SCOPES</td>\n<td>195</td>\n</tr>\n<tr>\n<td>8.4. ADDITIONAL RESOURCES</td>\n<td>196</td>\n</tr>\n<tr>\n<td>8.5. ADMIN QUOTA USAGE</td>\n<td>196</td>\n</tr>\n<tr>\n<td>8.5.1. Sample resource quota definitions</td>\n<td>196</td>\n</tr>\n<tr>\n<td>8.5.2. Creating a quota</td>\n<td>201</td>\n</tr>\n<tr>\n<td>8.5.3. Creating object count quotas</td>\n<td>201</td>\n</tr>\n<tr>\n<td>8.5.4. Viewing a quota</td>\n<td>202</td>\n</tr>\n<tr>\n<td>8.5.5. Configuring quota synchronization period</td>\n<td>202</td>\n</tr>\n</tbody>\n</table>\n\n<hr/>\n<table>\n<tr>\n<td>8.5.6. Setting a quota to consume a resource</td>\n<td>203</td>\n</tr>\n<tr>\n<td>8.6. ADDITIONAL RESOURCES</td>\n<td>204</td>\n</tr>\n<tr>\n<td>8.7. LIMIT RANGES IN A LIMITRANGE OBJECT</td>\n<td>204</td>\n</tr>\n<tr>\n<td>8.7.1. Container limits</td>\n<td>207</td>\n</tr>\n<tr>\n<td>8.7.2. Pod limits</td>\n<td>208</td>\n</tr>\n<tr>\n<td>8.7.3. Image limits</td>\n<td>209</td>\n</tr>\n<tr>\n<td>8.7.4. Image stream limits</td>\n<td>209</td>\n</tr>\n<tr>\n<td>8.7.5. PersistentVolumeClaim limits</td>\n<td>210</td>\n</tr>\n<tr>\n<td>8.8. ADDITIONAL RESOURCES</td>\n<td>211</td>\n</tr>\n<tr>\n<td>8.9. LIMIT RANGE OPERATIONS</td>\n<td>211</td>\n</tr>\n<tr>\n<td>8.10. ADDITIONAL RESOURCES</td>\n<td>212</td>\n</tr>\n<tr>\n<td><b>CHAPTER 9. HOST PRACTICES FOR IBM Z AND IBM LINUXONE ENVIRONMENTS</b> .....</td>\n<td><b>213</b></td>\n</tr>\n<tr>\n<td>9.1. MANAGING CPU OVERCOMMITMENT</td>\n<td>213</td>\n</tr>\n<tr>\n<td>9.2. DISABLE TRANSPARENT HUGE PAGES</td>\n<td>213</td>\n</tr>\n<tr>\n<td>9.3. BOOSTING NETWORKING PERFORMANCE WITH RFS</td>\n<td>214</td>\n</tr>\n<tr>\n<td>9.4. CHOOSE YOUR NETWORKING SETUP</td>\n<td>215</td>\n</tr>\n<tr>\n<td>9.5. ENSURE HIGH DISK PERFORMANCE WITH HYPERPAV ON Z/VM</td>\n<td>216</td>\n</tr>\n<tr>\n<td>9.6. RHEL KVM ON IBM Z HOST RECOMMENDATIONS</td>\n<td>217</td>\n</tr>\n<tr>\n<td>9.6.1. Use I/O threads for your virtual block devices</td>\n<td>217</td>\n</tr>\n<tr>\n<td>9.6.2. Avoid virtual SCSI devices</td>\n<td>218</td>\n</tr>\n<tr>\n<td>9.6.3. Configure guest caching for disk</td>\n<td>218</td>\n</tr>\n<tr>\n<td>9.6.4. Excluding the memory balloon device</td>\n<td>218</td>\n</tr>\n<tr>\n<td>9.6.5. Tuning the CPU migration algorithm of the host scheduler</td>\n<td>219</td>\n</tr>\n<tr>\n<td>9.6.6. Disabling the cgroup controller</td>\n<td>219</td>\n</tr>\n<tr>\n<td>9.6.7. Tuning the polling period for idle virtual CPUs</td>\n<td>220</td>\n</tr>\n<tr>\n<td><b>CHAPTER 10. USING THE NODE TUNING OPERATOR</b> .....</td>\n<td><b>221</b></td>\n</tr>\n<tr>\n<td>10.1. ABOUT THE NODE TUNING OPERATOR</td>\n<td>221</td>\n</tr>\n<tr>\n<td>10.2. ACCESSING AN EXAMPLE NODE TUNING OPERATOR SPECIFICATION</td>\n<td>221</td>\n</tr>\n<tr>\n<td>10.3. DEFAULT PROFILES SET ON A CLUSTER</td>\n<td>222</td>\n</tr>\n<tr>\n<td>10.4. VERIFYING THAT THE TUNED PROFILES ARE APPLIED</td>\n<td>222</td>\n</tr>\n<tr>\n<td>10.5. CUSTOM TUNING SPECIFICATION</td>\n<td>223</td>\n</tr>\n<tr>\n<td>10.6. CUSTOM TUNING EXAMPLES</td>\n<td>228</td>\n</tr>\n<tr>\n<td>10.7. DEFERRING APPLICATION OF TUNING CHANGES</td>\n<td>230</td>\n</tr>\n<tr>\n<td>10.7.1. Deferring application of tuning changes: An example</td>\n<td>232</td>\n</tr>\n<tr>\n<td>10.8. SUPPORTED TUNED DAEMON PLUGINS</td>\n<td>235</td>\n</tr>\n<tr>\n<td>10.9. CONFIGURING NODE TUNING IN A HOSTED CLUSTER</td>\n<td>236</td>\n</tr>\n<tr>\n<td>10.10. ADVANCED NODE TUNING FOR HOSTED CLUSTERS BY SETTING KERNEL BOOT PARAMETERS</td>\n<td>239</td>\n</tr>\n<tr>\n<td><b>CHAPTER 11. USING CPU MANAGER AND TOPOLOGY MANAGER</b> .....</td>\n<td><b>243</b></td>\n</tr>\n<tr>\n<td>11.1. SETTING UP CPU MANAGER</td>\n<td>243</td>\n</tr>\n<tr>\n<td>11.2. TOPOLOGY MANAGER POLICIES</td>\n<td>248</td>\n</tr>\n<tr>\n<td>11.3. SETTING UP TOPOLOGY MANAGER</td>\n<td>249</td>\n</tr>\n<tr>\n<td>11.4. POD INTERACTIONS WITH TOPOLOGY MANAGER POLICIES</td>\n<td>249</td>\n</tr>\n<tr>\n<td><b>CHAPTER 12. SCHEDULING NUMA-AWARE WORKLOADS</b> .....</td>\n<td><b>251</b></td>\n</tr>\n<tr>\n<td>12.1. ABOUT NUMA</td>\n<td>251</td>\n</tr>\n<tr>\n<td>12.2. ABOUT NUMA-AWARE SCHEDULING</td>\n<td>251</td>\n</tr>\n<tr>\n<td>12.3. NUMA RESOURCE SCHEDULING STRATEGIES</td>\n<td>253</td>\n</tr>\n<tr>\n<td>12.4. INSTALLING THE NUMA RESOURCES OPERATOR</td>\n<td>254</td>\n</tr>\n<tr>\n<td>12.4.1. Installing the NUMA Resources Operator using the CLI</td>\n<td>254</td>\n</tr>\n<tr>\n<td>12.4.2. Installing the NUMA Resources Operator using the web console</td>\n<td>255</td>\n</tr>\n<tr>\n<td>12.5. CONFIGURING A SINGLE NUMA NODE POLICY</td>\n<td>256</td>\n</tr>\n</table>\n\n<table>\n<tbody>\n<tr>\n<td>12.5.1. Managing high availability (HA) for the NUMA-aware scheduler</td>\n<td>256</td>\n</tr>\n<tr>\n<td> 12.5.1.1. Customizing scheduler replicas</td>\n<td>257</td>\n</tr>\n<tr>\n<td> 12.5.1.2. Disabling NUMA-aware scheduling</td>\n<td>258</td>\n</tr>\n<tr>\n<td> 12.5.1.3. Verifying scheduler high availability (HA) status</td>\n<td>258</td>\n</tr>\n<tr>\n<td>12.5.2. Sample performance profile</td>\n<td>259</td>\n</tr>\n<tr>\n<td>12.5.3. Creating a KubeletConfig CR</td>\n<td>260</td>\n</tr>\n<tr>\n<td>12.6. SCHEDULING NUMA-AWARE WORKLOADS</td>\n<td>261</td>\n</tr>\n<tr>\n<td> 12.6.1. Creating the NUMAResourcesOperator custom resource</td>\n<td>262</td>\n</tr>\n<tr>\n<td> 12.6.2. Creating the NUMAResourcesOperator custom resource for hosted control planes</td>\n<td>263</td>\n</tr>\n<tr>\n<td> 12.6.3. Deploying the NUMA-aware secondary pod scheduler</td>\n<td>266</td>\n</tr>\n<tr>\n<td> 12.6.4. Scheduling workloads with the NUMA-aware scheduler</td>\n<td>267</td>\n</tr>\n<tr>\n<td>12.7. NUMA RESOURCES OPERATOR SUPPORT FOR SCHEDULABLE CONTROL-PLANE NODES</td>\n<td>271</td>\n</tr>\n<tr>\n<td> 12.7.1. Configuring NUMA Resources Operator on schedulable control plane nodes</td>\n<td>272</td>\n</tr>\n<tr>\n<td>12.8. CONFIGURING POLLING OPERATIONS FOR NUMA RESOURCES UPDATES</td>\n<td>276</td>\n</tr>\n<tr>\n<td>12.9. TROUBLESHOOTING NUMA-AWARE SCHEDULING</td>\n<td>278</td>\n</tr>\n<tr>\n<td> 12.9.1. Reporting more exact resource availability</td>\n<td>281</td>\n</tr>\n<tr>\n<td> 12.9.2. Changing where high-performance workloads run</td>\n<td>284</td>\n</tr>\n<tr>\n<td> 12.9.3. Checking the NUMA-aware scheduler logs</td>\n<td>285</td>\n</tr>\n<tr>\n<td> 12.9.4. Troubleshooting the resource topology exporter</td>\n<td>288</td>\n</tr>\n<tr>\n<td> 12.9.5. Correcting a missing resource topology exporter config map</td>\n<td>289</td>\n</tr>\n<tr>\n<td> 12.9.6. Collecting NUMA Resources Operator data</td>\n<td>291</td>\n</tr>\n<tr>\n<td><b>CHAPTER 13. SCALABILITY AND PERFORMANCE OPTIMIZATION</b> .....</td>\n<td><b>292</b></td>\n</tr>\n<tr>\n<td>13.1. OPTIMIZING STORAGE</td>\n<td>292</td>\n</tr>\n<tr>\n<td> 13.1.1. Available persistent storage options</td>\n<td>292</td>\n</tr>\n<tr>\n<td> 13.1.2. Recommended configurable storage technology</td>\n<td>293</td>\n</tr>\n<tr>\n<td> 13.1.2.1. Specific application storage recommendations</td>\n<td>294</td>\n</tr>\n<tr>\n<td> 13.1.3. Additional resources</td>\n<td>296</td>\n</tr>\n<tr>\n<td> 13.1.4. Data storage management</td>\n<td>296</td>\n</tr>\n<tr>\n<td> 13.1.5. Optimizing storage performance for Microsoft Azure</td>\n<td>297</td>\n</tr>\n<tr>\n<td>13.2. OPTIMIZING ROUTING</td>\n<td>297</td>\n</tr>\n<tr>\n<td> 13.2.1. Baseline Ingress Controller (router) performance</td>\n<td>297</td>\n</tr>\n<tr>\n<td> 13.2.2. Additional resources</td>\n<td>299</td>\n</tr>\n<tr>\n<td> 13.2.3. Configuring Ingress Controller liveness, readiness, and startup probes</td>\n<td>299</td>\n</tr>\n<tr>\n<td> 13.2.4. Configuring HAProxy reload interval</td>\n<td>300</td>\n</tr>\n<tr>\n<td>13.3. OPTIMIZING NETWORKING</td>\n<td>301</td>\n</tr>\n<tr>\n<td> 13.3.1. Additional resources</td>\n<td>301</td>\n</tr>\n<tr>\n<td> 13.3.2. Optimizing the MTU for your network</td>\n<td>301</td>\n</tr>\n<tr>\n<td> 13.3.3. Recommended practices for installing large-scale clusters</td>\n<td>302</td>\n</tr>\n<tr>\n<td> 13.3.4. Impact of IPsec</td>\n<td>302</td>\n</tr>\n<tr>\n<td> 13.3.5. Additional resources</td>\n<td>302</td>\n</tr>\n<tr>\n<td>13.4. OPTIMIZING CPU USAGE WITH MOUNT NAMESPACE ENCAPSULATION</td>\n<td>303</td>\n</tr>\n<tr>\n<td> 13.4.1. Encapsulating mount namespaces</td>\n<td>303</td>\n</tr>\n<tr>\n<td> 13.4.2. Configuring mount namespace encapsulation</td>\n<td>305</td>\n</tr>\n<tr>\n<td> 13.4.3. Inspecting encapsulated namespaces</td>\n<td>308</td>\n</tr>\n<tr>\n<td> 13.4.4. Running additional services in the encapsulated namespace</td>\n<td>309</td>\n</tr>\n<tr>\n<td> 13.4.5. Additional resources</td>\n<td>309</td>\n</tr>\n<tr>\n<td><b>CHAPTER 14. MANAGING BARE-METAL HOSTS</b> .....</td>\n<td><b>311</b></td>\n</tr>\n<tr>\n<td>14.1. ABOUT BARE METAL HOSTS AND NODES</td>\n<td>311</td>\n</tr>\n<tr>\n<td>14.2. MAINTAINING BARE METAL HOSTS</td>\n<td>311</td>\n</tr>\n<tr>\n<td> 14.2.1. Adding a bare metal host to the cluster using the web console</td>\n<td>312</td>\n</tr>\n<tr>\n<td> 14.2.2. Adding a bare-metal host to the cluster using YAML in the web console</td>\n<td>312</td>\n</tr>\n</tbody>\n</table>\n\n<hr/>\n<table>\n<tr>\n<td>14.2.3. Automatically scaling machines to the number of available bare-metal hosts</td>\n<td>313</td>\n</tr>\n<tr>\n<td>14.2.4. Removing bare-metal hosts from the provisioner node</td>\n<td>314</td>\n</tr>\n<tr>\n<td>14.2.5. Powering off bare-metal hosts by using the web console</td>\n<td>315</td>\n</tr>\n<tr>\n<td>14.2.6. Powering off bare-metal hosts by using the CLI</td>\n<td>316</td>\n</tr>\n<tr>\n<td><b>CHAPTER 15. OPTIMIZING MEMORY MANAGEMENT FOR WORKLOADS BY USING HUGE PAGES</b> .....</td>\n<td><b>318</b></td>\n</tr>\n<tr>\n<td>15.1. WHAT HUGE PAGES DO</td>\n<td>318</td>\n</tr>\n<tr>\n<td>15.2. HOW HUGE PAGES ARE CONSUMED BY APPS</td>\n<td>318</td>\n</tr>\n<tr>\n<td> 15.2.1. Allocating huge pages of a specific size</td>\n<td>319</td>\n</tr>\n<tr>\n<td> 15.2.2. Huge page requirements</td>\n<td>319</td>\n</tr>\n<tr>\n<td>15.3. CONSUMING HUGE PAGES RESOURCES USING THE DOWNWARD API</td>\n<td>319</td>\n</tr>\n<tr>\n<td>15.4. CONFIGURING HUGE PAGES AT BOOT TIME</td>\n<td>321</td>\n</tr>\n<tr>\n<td>15.5. DISABLING TRANSPARENT HUGE PAGES</td>\n<td>323</td>\n</tr>\n<tr>\n<td><b>CHAPTER 16. UNDERSTANDING LOW LATENCY TUNING FOR CLUSTER NODES</b> .....</td>\n<td><b>325</b></td>\n</tr>\n<tr>\n<td>16.1. ABOUT LOW LATENCY</td>\n<td>325</td>\n</tr>\n<tr>\n<td>16.2. ABOUT HYPER-THREADING FOR LOW LATENCY AND REAL-TIME APPLICATIONS</td>\n<td>326</td>\n</tr>\n<tr>\n<td><b>CHAPTER 17. TUNING NODES FOR LOW LATENCY WITH THE PERFORMANCE PROFILE</b> .....</td>\n<td><b>327</b></td>\n</tr>\n<tr>\n<td>17.1. CREATING A PERFORMANCE PROFILE</td>\n<td>327</td>\n</tr>\n<tr>\n<td> 17.1.1. About the Performance Profile Creator</td>\n<td>327</td>\n</tr>\n<tr>\n<td> 17.1.2. Creating a machine config pool to target nodes for performance tuning</td>\n<td>328</td>\n</tr>\n<tr>\n<td> 17.1.3. Gathering data about your cluster for the PPC</td>\n<td>329</td>\n</tr>\n<tr>\n<td> 17.1.4. Running the Performance Profile Creator using Podman</td>\n<td>330</td>\n</tr>\n<tr>\n<td> 17.1.5. Running the Performance Profile Creator wrapper script</td>\n<td>334</td>\n</tr>\n<tr>\n<td> 17.1.6. Performance Profile Creator arguments</td>\n<td>339</td>\n</tr>\n<tr>\n<td>17.2. REFERENCE PERFORMANCE PROFILES</td>\n<td>342</td>\n</tr>\n<tr>\n<td> 17.2.1. Performance profile template for clusters that use OVS-DPDK on OpenStack</td>\n<td>342</td>\n</tr>\n<tr>\n<td> 17.2.2. Telco RAN DU reference design performance profile</td>\n<td>343</td>\n</tr>\n<tr>\n<td> 17.2.3. Telco core reference design performance profile</td>\n<td>344</td>\n</tr>\n<tr>\n<td>17.3. SUPPORTED PERFORMANCE PROFILE API VERSIONS</td>\n<td>345</td>\n</tr>\n<tr>\n<td>17.4. NODE POWER CONSUMPTION AND REALTIME PROCESSING WITH WORKLOAD HINTS</td>\n<td>345</td>\n</tr>\n<tr>\n<td>17.5. CONFIGURING POWER SAVING FOR NODES THAT RUN COLOCATED HIGH AND LOW PRIORITY WORKLOADS</td>\n<td>347</td>\n</tr>\n<tr>\n<td>17.6. CPUS FOR INFRA AND APPLICATION CONTAINERS</td>\n<td>348</td>\n</tr>\n<tr>\n<td>17.7. RESTRICTING CPUS FOR INFRA AND APPLICATION CONTAINERS</td>\n<td>350</td>\n</tr>\n<tr>\n<td>17.8. CONFIGURING HYPER-THREADING FOR A CLUSTER</td>\n<td>351</td>\n</tr>\n<tr>\n<td>17.9. DISABLING HYPER-THREADING FOR LOW LATENCY APPLICATIONS</td>\n<td>352</td>\n</tr>\n<tr>\n<td>17.10. MANAGING DEVICE INTERRUPT PROCESSING FOR GUARANTEED POD ISOLATED CPUS</td>\n<td>353</td>\n</tr>\n<tr>\n<td> 17.10.1. Finding the effective IRQ affinity setting for a node</td>\n<td>353</td>\n</tr>\n<tr>\n<td> 17.10.2. Configuring node interrupt affinity</td>\n<td>355</td>\n</tr>\n<tr>\n<td>17.11. CONFIGURING MEMORY PAGE SIZES</td>\n<td>356</td>\n</tr>\n<tr>\n<td> 17.11.1. Configuring kernel page sizes</td>\n<td>356</td>\n</tr>\n<tr>\n<td> 17.11.2. Configuring huge pages</td>\n<td>357</td>\n</tr>\n<tr>\n<td> 17.11.3. Allocating multiple huge page sizes</td>\n<td>358</td>\n</tr>\n<tr>\n<td>17.12. REDUCING NIC QUEUES USING THE NODE TUNING OPERATOR</td>\n<td>359</td>\n</tr>\n<tr>\n<td> 17.12.1. Adjusting the NIC queues with the performance profile</td>\n<td>359</td>\n</tr>\n<tr>\n<td> 17.12.2. Verifying the queue status</td>\n<td>362</td>\n</tr>\n<tr>\n<td> 17.12.3. Logging associated with adjusting NIC queues</td>\n<td>366</td>\n</tr>\n<tr>\n<td><b>CHAPTER 18. TUNING HOSTED CONTROL PLANES FOR LOW LATENCY WITH THE PERFORMANCE PROFILE</b> .....</td>\n<td><b>367</b></td>\n</tr>\n<tr>\n<td>18.1. CREATING A PERFORMANCE PROFILE FOR HOSTED CONTROL PLANES</td>\n<td>367</td>\n</tr>\n<tr>\n<td> 18.1.1. Gathering data about your hosted control planes cluster for the PPC</td>\n<td>367</td>\n</tr>\n</table>\n<hr/>\n\n<table>\n<tr>\n<td>18.1.2. Running the Performance Profile Creator on a hosted cluster using Podman</td>\n<td>369</td>\n</tr>\n<tr>\n<td>18.1.3. Configuring low-latency tuning in a hosted cluster</td>\n<td>371</td>\n</tr>\n<tr>\n<td><b>CHAPTER 19. PROVISIONING REAL-TIME AND LOW LATENCY WORKLOADS</b> .....</td>\n<td><b>375</b></td>\n</tr>\n<tr>\n<td>19.1. SCHEDULING A LOW LATENCY WORKLOAD ONTO A COMPUTE NODE</td>\n<td>375</td>\n</tr>\n<tr>\n<td>19.2. CREATING A POD WITH A GUARANTEED QOS CLASS</td>\n<td>378</td>\n</tr>\n<tr>\n<td>19.3. DISABLING CPU LOAD BALANCING IN A POD</td>\n<td>380</td>\n</tr>\n<tr>\n<td>19.4. DISABLING POWER SAVING MODE FOR HIGH PRIORITY PODS</td>\n<td>381</td>\n</tr>\n<tr>\n<td>19.5. DISABLING CPU CFS QUOTA</td>\n<td>382</td>\n</tr>\n<tr>\n<td>19.6. CONFIGURING INTERRUPT PROCESSING FOR INDIVIDUAL PODS</td>\n<td>383</td>\n</tr>\n<tr>\n<td><b>CHAPTER 20. DEBUGGING LOW LATENCY NODE TUNING STATUS</b> .....</td>\n<td><b>386</b></td>\n</tr>\n<tr>\n<td>20.1. DEBUGGING LOW LATENCY CNF TUNING STATUS</td>\n<td>386</td>\n</tr>\n<tr>\n<td>20.2. MACHINE CONFIG POOLS</td>\n<td>387</td>\n</tr>\n<tr>\n<td>20.3. ABOUT THE MUST-GATHER TOOL</td>\n<td>388</td>\n</tr>\n<tr>\n<td>20.4. COLLECTING LOW LATENCY TUNING DEBUGGING DATA FOR RED HAT SUPPORT</td>\n<td>388</td>\n</tr>\n<tr>\n<td><b>CHAPTER 21. PERFORMING LATENCY TESTS FOR PLATFORM VERIFICATION</b> .....</td>\n<td><b>391</b></td>\n</tr>\n<tr>\n<td>21.1. PREREQUISITES FOR RUNNING LATENCY TESTS</td>\n<td>391</td>\n</tr>\n<tr>\n<td>21.2. MEASURING LATENCY</td>\n<td>391</td>\n</tr>\n<tr>\n<td>21.3. RUNNING THE LATENCY TESTS</td>\n<td>393</td>\n</tr>\n<tr>\n<td>21.3.1. Running hwlatdetect</td>\n<td>394</td>\n</tr>\n<tr>\n<td>21.3.2. Example hwlatdetect test results</td>\n<td>396</td>\n</tr>\n<tr>\n<td>21.3.3. Running cyclictest</td>\n<td>397</td>\n</tr>\n<tr>\n<td>21.3.4. Example cyclictest results</td>\n<td>399</td>\n</tr>\n<tr>\n<td>21.3.5. Running oslat</td>\n<td>400</td>\n</tr>\n<tr>\n<td>21.4. GENERATING A LATENCY TEST FAILURE REPORT</td>\n<td>402</td>\n</tr>\n<tr>\n<td>21.5. GENERATING A JUNIT LATENCY TEST REPORT</td>\n<td>402</td>\n</tr>\n<tr>\n<td>21.6. RUNNING LATENCY TESTS ON A SINGLE-NODE OPENSHIFT CLUSTER</td>\n<td>403</td>\n</tr>\n<tr>\n<td>21.7. RUNNING LATENCY TESTS IN A DISCONNECTED CLUSTER</td>\n<td>404</td>\n</tr>\n<tr>\n<td>21.7.1. Mirroring the images to a custom registry accessible from the cluster</td>\n<td>404</td>\n</tr>\n<tr>\n<td>21.7.2. Configuring the tests to consume images from a custom registry</td>\n<td>405</td>\n</tr>\n<tr>\n<td>21.7.3. Mirroring images to the cluster OpenShift image registry</td>\n<td>405</td>\n</tr>\n<tr>\n<td>21.7.4. Mirroring a different set of test images</td>\n<td>406</td>\n</tr>\n<tr>\n<td>21.8. TROUBLESHOOTING ERRORS WITH THE CNF-TESTS CONTAINER</td>\n<td>407</td>\n</tr>\n<tr>\n<td><b>CHAPTER 22. IMPROVING CLUSTER STABILITY IN HIGH LATENCY ENVIRONMENTS USING WORKER LATENCY PROFILES</b> .....</td>\n<td><b>408</b></td>\n</tr>\n<tr>\n<td>22.1. UNDERSTANDING WORKER LATENCY PROFILES</td>\n<td>408</td>\n</tr>\n<tr>\n<td>22.2. IMPLEMENTING WORKER LATENCY PROFILES AT CLUSTER CREATION</td>\n<td>411</td>\n</tr>\n<tr>\n<td>22.3. USING AND CHANGING WORKER LATENCY PROFILES</td>\n<td>412</td>\n</tr>\n<tr>\n<td>22.4. DISPLAYING RESULTING VALUES OF WORKER LATENCY PROFILE</td>\n<td>415</td>\n</tr>\n<tr>\n<td><b>CHAPTER 23. WORKLOAD PARTITIONING</b> .....</td>\n<td><b>417</b></td>\n</tr>\n<tr>\n<td>23.1. ENABLING WORKLOAD PARTITIONING</td>\n<td>417</td>\n</tr>\n<tr>\n<td>23.2. PERFORMANCE PROFILES AND WORKLOAD PARTITIONING</td>\n<td>418</td>\n</tr>\n<tr>\n<td><b>CHAPTER 24. USING THE NODE OBSERVABILITY OPERATOR</b> .....</td>\n<td><b>421</b></td>\n</tr>\n<tr>\n<td>24.1. WORKFLOW OF THE NODE OBSERVABILITY OPERATOR</td>\n<td>421</td>\n</tr>\n<tr>\n<td>24.2. INSTALLING THE NODE OBSERVABILITY OPERATOR</td>\n<td>421</td>\n</tr>\n<tr>\n<td>24.2.1. Installing the Node Observability Operator using the CLI</td>\n<td>421</td>\n</tr>\n<tr>\n<td>24.2.2. Installing the Node Observability Operator using the web console</td>\n<td>423</td>\n</tr>\n<tr>\n<td>24.3. REQUESTING CRI-O AND KUBELET PROFILING DATA USING THE NODE OBSERVABILITY OPERATOR</td>\n<td>424</td>\n</tr>\n<tr>\n<td>24.3.1. Creating the Node Observability custom resource</td>\n<td>424</td>\n</tr>\n</table>\n<table><tr><td>24.3.2. Running the profiling query</td><td>425</td></tr><tr><td>24.4. NODE OBSERVABILITY OPERATOR SCRIPTING</td><td>427</td></tr><tr><td>24.4.1. Creating the Node Observability custom resource for scripting</td><td>427</td></tr><tr><td>24.4.2. Configuring Node Observability Operator scripting</td><td>428</td></tr><tr><td>24.5. ADDITIONAL RESOURCES</td><td>430</td></tr></table><h1>CHAPTER 1. OPENSHIFT CONTAINER PLATFORM SCALABILITY AND PERFORMANCE OVERVIEW</h1><p>OpenShift Container Platform provides best practices and tools to help you optimize the performance and scale of your clusters. The following documentation provides information on recommended performance and scalability practices, reference design specifications, optimization, and low latency tuning.</p><p>To contact Red Hat support, see <a href=\"#\">Getting support</a>.</p><h2>NOTE</h2><p>Some performance and scalability Operators have release cycles that are independent from OpenShift Container Platform release cycles. For more information, see <a href=\"#\">OpenShift Operators</a>.</p><h2>1.1. RECOMMENDED PERFORMANCE AND SCALABILITY PRACTICES</h2><p><a href=\"#\">Recommended control plane practices</a></p><p><a href=\"#\">Recommended infrastructure practices</a></p><h2>1.2. TELCO REFERENCE DESIGN SPECIFICATIONS</h2><p><a href=\"#\">Telco RAN DU reference design specification for OpenShift Container Platform 4.21</a></p><p><a href=\"#\">Telco core reference design specification</a></p><h2>1.3. PLANNING, OPTIMIZATION, AND MEASUREMENT</h2><p><a href=\"#\">Planning your environment according to object maximums</a></p><p><a href=\"#\">Recommended practices for IBM Z and IBM LinuxONE</a></p><p><a href=\"#\">Using the Node Tuning Operator</a></p><p><a href=\"#\">Using CPU Manager and Topology Manager</a></p><p><a href=\"#\">Scheduling NUMA-aware workloads</a></p><p><a href=\"#\">Optimizing storage, routing, networking and CPU usage</a></p><p><a href=\"#\">Managing bare metal hosts and events</a></p><p><a href=\"#\">What are huge pages and how are they used by apps</a></p><p><a href=\"#\">Low latency tuning for improving cluster stability and partitioning workload</a></p><p><a href=\"#\">Improving cluster stability in high latency environments using worker latency profiles</a></p><p><a href=\"#\">Workload partitioning</a></p><p><a href=\"#\">Using the Node Observability Operator</a></p><h2>CHAPTER 2. RECOMMENDED PERFORMANCE AND SCALABILITY PRACTICES</h2><h3>2.1. RECOMMENDED CONTROL PLANE PRACTICES</h3><p>To ensure optimal performance and scalability, apply the recommended practices for OpenShift Container Platform control planes. By understanding these recommended practices, you can configure your environment to handle increasing workloads while maintaining stability.</p><h4>2.1.1. Recommended practices for scaling the cluster</h4><p>To scale your cluster effectively, apply the recommended practices for installations with cloud provider integration. By understanding this guidance, you can optimize performance and ensure stability as you increase the size of your environment.</p><p>Apply the following best practices to scale the number of compute machines in your OpenShift Container Platform cluster. You scale the worker machines by increasing or decreasing the number of replicas that are defined in the compute machine set.</p><p>When scaling up the cluster to higher node counts:</p><ul><li>• Spread nodes across all of the available zones for higher availability.</li><li>• Scale up by no more than 25 to 50 machines at once.</li><li>• Consider creating new compute machine sets in each available zone with alternative instance types of similar size to help mitigate any periodic provider capacity constraints. For example, on AWS, use <b>m5.large</b> and <b>m5d.large</b>.</li></ul><h4>NOTE</h4><p>Cloud providers might implement a quota for API services. Therefore, gradually scale the cluster.</p><p>The controller might not be able to create the machines if the replicas in the compute machine sets are set to higher numbers all at one time. The number of requests the cloud platform, which OpenShift Container Platform is deployed on top of, is able to handle impacts the process. The controller starts to query more while trying to create, check, and update the machines with the status. The cloud platform on which OpenShift Container Platform is deployed has API request limits; excessive queries might lead to machine creation failures due to cloud platform limitations.</p><p>Enable machine health checks when scaling to large node counts. In case of failures, the health checks monitor the condition and automatically repair unhealthy machines.</p><h4>NOTE</h4><p>When scaling large and dense clusters to lower node counts, it might take large amounts of time because the process involves draining or evicting the objects running on the nodes being terminated in parallel. Also, the client might start to throttle the requests if there are too many objects to evict. The default client queries per second (QPS) and burst rates are currently set to <b>50</b> and <b>100</b> respectively. These values cannot be modified in OpenShift Container Platform.</p>\n<h3>2.1.2. Control plane node sizing</h3>\n\n<p>To ensure optimal performance and stability, determine the resource requirements for control plane nodes. These sizing guidelines depend on the number and type of nodes and objects in your cluster.</p>\n\n<p>The following control plane node size recommendations are based on the results of a control plane density focused testing, or <i>Cluster-density</i>. This test creates the following objects across a given number of namespaces:</p>\n\n<ul>\n<li>• 1 image stream</li>\n<li>• 1 build</li>\n<li>• 5 deployments, with 2 pod replicas in a <b>sleep</b> state, mounting 4 secrets, 4 config maps, and 1 downward API volume each</li>\n<li>• 5 services, each one pointing to the TCP/8080 and TCP/8443 ports of one of the previous deployments</li>\n<li>• 1 route pointing to the first of the previous services</li>\n<li>• 10 secrets containing 2048 random string characters</li>\n<li>• 10 config maps containing 2048 random string characters</li>\n</ul>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Number of compute nodes</th>\n<th>Cluster-density (namespaces)</th>\n<th>CPU cores</th>\n<th>Memory (GB)</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>24</td>\n<td>500</td>\n<td>4</td>\n<td>16</td>\n</tr>\n<tr>\n<td>120</td>\n<td>1000</td>\n<td>8</td>\n<td>32</td>\n</tr>\n<tr>\n<td>252</td>\n<td>4000</td>\n<td>16, but 24 if using the OVN-Kubernetes network plug-in</td>\n<td>64, but 128 if using the OVN-Kubernetes network plug-in</td>\n</tr>\n<tr>\n<td>501, but untested with the OVN-Kubernetes network plug-in</td>\n<td>4000</td>\n<td>16</td>\n<td>96</td>\n</tr>\n</tbody>\n</table>\n\n<p>The data from the table above is based on an OpenShift Container Platform running on top of AWS, using r5.4xlarge instances as control-plane nodes and m5.2xlarge instances as compute nodes.</p>\n\n<p>On a large and dense cluster with three control plane nodes, the CPU and memory usage will spike up when one of the nodes is stopped, rebooted, or fails. The failures can be due to unexpected issues with power, network, underlying infrastructure, or intentional cases where the cluster is restarted after shutting it down to save costs. The remaining two control plane nodes must handle the load in order to be highly available, which leads to increase in the resource usage. This is also expected during upgrades because the control plane nodes are cordoned, drained, and rebooted serially to apply the operating system updates, as well as the control plane Operators update. To avoid cascading failures, keep the overall CPU and memory resource usage on the control plane nodes to at most 60% of all available capacity to handle the resource usage spikes. Increase the CPU and memory on the control plane nodes accordingly to avoid potential downtime due to lack of resources.</p>\n\n<h2>IMPORTANT</h2>\n\n<p>The node sizing varies depending on the number of nodes and object counts in the cluster. It also depends on whether the objects are actively being created on the cluster. During object creation, the control plane is more active in terms of resource usage compared to when the objects are in the <b>Running</b> phase.</p>\n\n<p>Operator Lifecycle Manager (OLM) runs on the control plane nodes and its memory footprint depends on the number of namespaces and user installed operators that OLM needs to manage on the cluster. Control plane nodes need to be sized accordingly to avoid OOM kills. Following data points are based on the results from cluster maximums testing.</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Number of namespaces</th>\n<th>OLM memory at idle state (GB)</th>\n<th>OLM memory with 5 user operators installed (GB)</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>500</td>\n<td>0.823</td>\n<td>1.7</td>\n</tr>\n<tr>\n<td>1000</td>\n<td>1.2</td>\n<td>2.5</td>\n</tr>\n<tr>\n<td>1500</td>\n<td>1.7</td>\n<td>3.2</td>\n</tr>\n<tr>\n<td>2000</td>\n<td>2</td>\n<td>4.4</td>\n</tr>\n<tr>\n<td>3000</td>\n<td>2.7</td>\n<td>5.6</td>\n</tr>\n<tr>\n<td>4000</td>\n<td>3.8</td>\n<td>7.6</td>\n</tr>\n<tr>\n<td>5000</td>\n<td>4.2</td>\n<td>9.02</td>\n</tr>\n<tr>\n<td>6000</td>\n<td>5.8</td>\n<td>11.3</td>\n</tr>\n<tr>\n<td>7000</td>\n<td>6.6</td>\n<td>12.9</td>\n</tr>\n<tr>\n<td>8000</td>\n<td>6.9</td>\n<td>14.8</td>\n</tr>\n<tr>\n<td>9000</td>\n<td>8</td>\n<td>17.7</td>\n</tr>\n<tr>\n<td>10,000</td>\n<td>9.9</td>\n<td>21.6</td>\n</tr>\n</tbody>\n</table>\n<h2>IMPORTANT</h2><p>You can modify the control plane node size in a running OpenShift Container Platform 4.21 cluster for the following configurations only:</p><ul><li>• Clusters installed with a user-provisioned installation method.</li><li>• AWS clusters installed with an installer-provisioned infrastructure installation method.</li><li>• Clusters that use a control plane machine set to manage control plane machines.</li></ul><p>For all other configurations, you must estimate your total node count and use the suggested control plane node size during installation.</p><h2>NOTE</h2><p>In OpenShift Container Platform 4.21, half of a CPU core (500 millicore) is now reserved by the system by default compared to OpenShift Container Platform 3.11 and previous versions. The sizes are determined taking that into consideration.</p><h2>2.2. SELECTING A LARGER AWS INSTANCE TYPE FOR CONTROL PLANE MACHINES</h2><p>If the control plane machines in an Amazon Web Services (AWS) cluster require more resources, you can select a larger AWS instance type for the control plane machines to use.</p><h2>NOTE</h2><p>The procedure for clusters that use a control plane machine set is different from the procedure for clusters that do not use a control plane machine set.</p><p>If you are uncertain about the state of the <b>ControlPlaneMachineSet</b> CR in your cluster, you can verify the CR status.</p><h3>2.2.1. Additional resources</h3><ul><li>• <a href=\"#\">Verify the CR status</a></li></ul><h3>2.2.2. Changing the Amazon Web Services instance type by using a control plane machine set</h3><p>You can change the Amazon Web Services (AWS) instance type that your control plane machines use by updating the specification in the control plane machine set custom resource (CR).</p><h4>Prerequisites</h4><ul><li>• Your AWS cluster uses a control plane machine set.</li></ul><h4>Procedure</h4><ol><li>1. Edit the following line under the <b>providerSpec</b> field:</li></ol><pre>providerSpec:</pre><pre>value:<br/>...<br/>instanceType: <compatible_aws_instance_type></pre><ul><li>• <b><compatible_aws_instance_type></b>: Specifies a larger AWS instance type with the same base as the previous selection. For example, you can change <b>m6i.xlarge</b> to <b>m6i.2xlarge</b> or <b>m6i.4xlarge</b>.</li></ul><p>2. Save your changes.</p><h4>Additional resources</h4><ul><li>• <a href=\"#\">Managing control plane machines with control plane machine sets</a></li></ul><h3>2.2.3. Changing the Amazon Web Services instance type by using the AWS console</h3><p>You can change the Amazon Web Services (AWS) instance type that your control plane machines use by updating the instance type in the AWS console.</p><h4>Prerequisites</h4><ul><li>• You have access to the AWS console with the permissions required to modify the EC2 Instance for your cluster.</li><li>• You have access to the OpenShift Container Platform cluster as a user with the <b>cluster-admin</b> role.</li></ul><h4>Procedure</h4><ol><li>1. Open the AWS console and fetch the instances for the control plane machines.</li><li>2. Choose one control plane machine instance.<ol type=\"a\"><li>a. For the selected control plane machine, back up the etcd data by creating an etcd snapshot. For more information, see \"Backing up etcd\".</li><li>b. In the AWS console, stop the control plane machine instance.</li><li>c. Select the stopped instance, and click <b>Actions → Instance Settings → Change instance type</b>.</li><li>d. Change the instance to a larger type, ensuring that the type is the same base as the previous selection, and apply changes. For example, you can change <b>m6i.xlarge</b> to <b>m6i.2xlarge</b> or <b>m6i.4xlarge</b>.</li><li>e. Start the instance.</li><li>f. If your OpenShift Container Platform cluster has a corresponding <b>Machine</b> object for the instance, update the instance type of the object to match the instance type set in the AWS console.</li></ol></li><li>3. Repeat this process for each control plane machine.</li></ol><h4>Additional resources</h4>\n<ul>\n<li>• <a href=\"#\">Backing up etcd</a></li>\n<li>• <a href=\"#\">AWS documentation about changing the instance type</a></li>\n</ul>\n\n<h2>2.3. RECOMMENDED INFRASTRUCTURE PRACTICES</h2>\n\n<p>This topic provides recommended performance and scalability practices for infrastructure in OpenShift Container Platform.</p>\n\n<h3>2.3.1. Infrastructure node sizing</h3>\n\n<p><i>Infrastructure nodes</i> are nodes that are labeled to run pieces of the OpenShift Container Platform environment. The infrastructure node resource requirements depend on the cluster age, nodes, and objects in the cluster, as these factors can lead to an increase in the number of metrics or time series in Prometheus. The following infrastructure node size recommendations are based on the results observed in cluster-density testing detailed in the <b>Control plane node sizing</b> section, where the monitoring stack and the default ingress-controller were moved to these nodes.</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Number of worker nodes</th>\n<th>Cluster density, or number of namespaces</th>\n<th>CPU cores</th>\n<th>Memory (GB)</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>27</td>\n<td>500</td>\n<td>4</td>\n<td>24</td>\n</tr>\n<tr>\n<td>120</td>\n<td>1000</td>\n<td>8</td>\n<td>48</td>\n</tr>\n<tr>\n<td>252</td>\n<td>4000</td>\n<td>16</td>\n<td>128</td>\n</tr>\n<tr>\n<td>501</td>\n<td>4000</td>\n<td>32</td>\n<td>128</td>\n</tr>\n</tbody>\n</table>\n\n<p>In general, three infrastructure nodes are recommended per cluster.</p>\n\n<h4>IMPORTANT</h4>\n\n<p>These sizing recommendations should be used as a guideline. Prometheus is a highly memory intensive application; the resource usage depends on various factors including the number of nodes, objects, the Prometheus metrics scraping interval, metrics or time series, and the age of the cluster. In addition, the router resource usage can also be affected by the number of routes and the amount/type of inbound requests.</p>\n\n<p>These recommendations apply only to infrastructure nodes hosting Monitoring, Ingress and Registry infrastructure components installed during cluster creation.</p>\n\n<h4>NOTE</h4>\n\n<p>In OpenShift Container Platform 4.21, half of a CPU core (500 millicore) is now reserved by the system by default compared to OpenShift Container Platform 3.11 and previous versions. This influences the stated sizing recommendations.</p>\n\n<h3>2.3.2. Scaling the Cluster Monitoring Operator</h3>\n\n<p>OpenShift Container Platform exposes metrics that the Cluster Monitoring Operator (CMO) collects</p>\n\n<p>and stores in the Prometheus-based monitoring stack. As an administrator, you can view dashboards for system resources, containers, and components metrics in the OpenShift Container Platform web console by navigating to <b>Observe → Dashboards</b>.</p>\n\n<h3>2.3.3. Prometheus database storage requirements</h3>\n\n<p>Red Hat performed various tests for different scale sizes.</p>\n\n<h4>NOTE</h4>\n\n<ul>\n<li>• The following Prometheus storage requirements are not prescriptive and should be used as a reference. Higher resource consumption might be observed in your cluster depending on workload activity and resource density, including the number of pods, containers, routes, or other resources exposing metrics collected by Prometheus.</li>\n<li>• You can configure the size-based data retention policy to suit your storage requirements.</li>\n</ul>\n\n<p><b>Table 2.1. Prometheus Database storage requirements based on number of nodes/pods in the cluster</b></p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Number of nodes</th>\n<th>Number of pods<br/>(2 containers per pod)</th>\n<th>Prometheus storage growth per day</th>\n<th>Prometheus storage growth per 15 days</th>\n<th>Network (per tsdb chunk)</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>50</td>\n<td>1800</td>\n<td>6.3 GB</td>\n<td>94 GB</td>\n<td>16 MB</td>\n</tr>\n<tr>\n<td>100</td>\n<td>3600</td>\n<td>13 GB</td>\n<td>195 GB</td>\n<td>26 MB</td>\n</tr>\n<tr>\n<td>150</td>\n<td>5400</td>\n<td>19 GB</td>\n<td>283 GB</td>\n<td>36 MB</td>\n</tr>\n<tr>\n<td>200</td>\n<td>7200</td>\n<td>25 GB</td>\n<td>375 GB</td>\n<td>46 MB</td>\n</tr>\n</tbody>\n</table>\n\n<p>Approximately 20 percent of the expected size was added as overhead to ensure that the storage requirements do not exceed the calculated value.</p>\n\n<p>The above calculation is for the default OpenShift Container Platform Cluster Monitoring Operator.</p>\n\n<h4>NOTE</h4>\n\n<p>CPU utilization has minor impact. The ratio is approximately 1 core out of 40 per 50 nodes and 1800 pods.</p>\n\n<h4>Recommendations for OpenShift Container Platform</h4>\n\n<ul>\n<li>• Use at least two infrastructure (infra) nodes.</li>\n<li>• Use at least three <b>openshift-container-storage</b> nodes with non-volatile memory express (SSD or NVMe) drives.</li>\n</ul>\n\n<h3>2.3.4. Configuring cluster monitoring</h3>\n\n<p>You can increase the storage capacity for the Prometheus component in the cluster monitoring stack.</p>\n\n<h4>Procedure</h4>\n\n<p>To increase the storage capacity for Prometheus:</p>\n\n<ol>\n<li>1. Create a YAML configuration file, <b>cluster-monitoring-config.yaml</b>. For example:</li>\n</ol>\n\n<pre>apiVersion: v1\nkind: ConfigMap\ndata:\n config.yaml: |\n prometheusK8s:\n retention: {{PROMETHEUS_RETENTION_PERIOD}} 1\n nodeSelector:\n node-role.kubernetes.io/infra: \"\"\n volumeClaimTemplate:\n spec:\n storageClassName: {{STORAGE_CLASS}} 2\n resources:\n requests:\n storage: {{PROMETHEUS_STORAGE_SIZE}} 3\n alertmanagerMain:\n nodeSelector:\n node-role.kubernetes.io/infra: \"\"\n volumeClaimTemplate:\n spec:\n storageClassName: {{STORAGE_CLASS}} 4\n resources:\n requests:\n storage: {{ALERTMANAGER_STORAGE_SIZE}} 5\n metadata:\n name: cluster-monitoring-config\n namespace: openshift-monitoring</pre>\n\n<ol>\n<li>1 The default value of Prometheus retention is <b>PROMETHEUS_RETENTION_PERIOD=15d</b>. Units are measured in time using one of these suffixes: s, m, h, d.</li>\n<li>2 4 The storage class for your cluster.</li>\n<li>3 A typical value is <b>PROMETHEUS_STORAGE_SIZE=200Gi</b>. Storage values can be a plain integer or a fixed-point integer using one of these suffixes: E, P, T, G, M, K. You can also use the power-of-two equivalents: Ei, Pi, Ti, Gi, Mi, Ki.</li>\n<li>5 A typical value is <b>ALERTMANAGER_STORAGE_SIZE=20Gi</b>. Storage values can be a plain integer or a fixed-point integer using one of these suffixes: E, P, T, G, M, K. You can also use the power-of-two equivalents: Ei, Pi, Ti, Gi, Mi, Ki.</li>\n</ol>\n\n<ol>\n<li>2. Add values for the retention period, storage class, and storage sizes.</li>\n<li>3. Save the file.</li>\n</ol>\n<ol><li>4. Apply the changes by running:</li></ol><pre>$ oc create -f cluster-monitoring-config.yaml</pre><h3>2.3.5. Additional resources</h3><ul><li>• <a href=\"#\">Infrastructure Nodes in OpenShift 4</a></li><li>• <a href=\"#\">OpenShift Container Platform cluster maximums</a></li><li>• <a href=\"#\">Creating infrastructure machine sets</a></li></ul><h1>CHAPTER 3. TELCO CORE REFERENCE DESIGN SPECIFICATIONS</h1><p>The telco core reference design specifications (RDS) configures an OpenShift Container Platform cluster running on commodity hardware to host telco core workloads.</p><h2>3.1. TELCO CORE RDS USE MODEL OVERVIEW</h2><p>The Telco core reference design specification (RDS) describes a platform that supports large-scale telco applications including control plane functions such as signaling and aggregation. It also includes some centralized data plane functions, for example, user plane functions (UPF). These functions generally require scalability, complex networking support, resilient software-defined storage, and support performance requirements that are less stringent and constrained than far-edge deployments such as RAN.</p><h2>3.2. ABOUT THE TELCO CORE CLUSTER USE MODEL</h2><p>The telco core cluster use model is designed for clusters running on commodity hardware. Telco core clusters support large scale telco applications including control plane functions like signaling, aggregation, session border controller (SBC), and centralized data plane functions such as 5G user plane functions (UPF). Telco core cluster functions require scalability, complex networking support, resilient software-defined storage, and support performance requirements that are less stringent and constrained than far-edge RAN deployments.</p><p>Networking requirements for telco core functions vary widely across a range of networking features and performance points. IPv6 is a requirement and dual-stack is common. Some functions need maximum throughput and transaction rate and require support for user-plane DPDK networking. Other functions use typical cloud-native patterns and can rely on OVN-Kubernetes, kernel networking, and load balancing.</p><p>Telco core clusters are configured as standard with three control plane and one or more worker nodes configured with the stock (non-RT) kernel. In support of workloads with varying networking and performance requirements, you can segment worker nodes by using <b>MachineConfigPool</b> custom resources (CR), for example, for non-user data plane or high-throughput use cases. In support of required telco operational features, core clusters have a standard set of Day 2 OLM-managed Operators installed.</p>Figure 3.1. Telco core RDS cluster service-based architecture and networking topology\n\n<p><b>5G core cluster</b></p>\n<p>5G core network functions</p>\n<p>NWDAF, NSFF, AUSF, UDM, NRF, NEF, AF</p>\n<p>AMF, SMF, PCF, CHF</p>\n<p>UE, RAN, UPF, DN</p>\n<p>Internet</p>\n<p>Legend:</p>\n<ul>\n<li>Kubernetes networking (REST)<br/>OVN-K, metalLB</li>\n<li>Control plane networking<br/>OVN-K, MAC-VLAN, kernel SR-IOV</li>\n<li>Data plane networking<br/>SR-IOV with DPDK</li>\n</ul>\n\n<h3>3.3. REFERENCE DESIGN SCOPE</h3>\n\n<p>The telco core, telco RAN and telco hub reference design specifications (RDS) capture the recommended, tested, and supported configurations to get reliable and repeatable performance for clusters running the telco core and telco RAN profiles.</p>\n\n<p>Each RDS includes the released features and supported configurations that are engineered and validated for clusters to run the individual profiles. The configurations provide a baseline OpenShift Container Platform installation that meets feature and KPI targets. Each RDS also describes expected variations for each individual configuration. Validation of each RDS includes many long duration and at-scale tests.</p>\n\n<h4>NOTE</h4>\n\n<p>The validated reference configurations are updated for each major Y-stream release of OpenShift Container Platform. Z-stream patch releases are periodically re-tested against the reference configurations.</p>\n\n<h3>3.4. DEVIATIONS FROM THE REFERENCE DESIGN</h3>\n\n<p>Deviating from the validated telco core, telco RAN DU, and telco hub reference design specifications (RDS) can have significant impact beyond the specific component or feature that you change. Deviations require analysis and engineering in the context of the complete solution.</p>\n\n<h2>IMPORTANT</h2>\n\n<p>All deviations from the RDS should be analyzed and documented with clear action tracking information. Due diligence is expected from partners to understand how to bring deviations into line with the reference design. This might require partners to provide additional resources to engage with Red Hat to work towards enabling their use case to achieve a best in class outcome with the platform. This is critical for the supportability of the solution and ensuring alignment across Red Hat and with partners.</p>\n\n<p>Deviation from the RDS can have some or all of the following consequences:</p>\n\n<ul>\n<li>• It can take longer to resolve issues.</li>\n<li>• There is a risk of missing project service-level agreements (SLAs), project deadlines, end provider performance requirements, and so on.</li>\n<li>• Unapproved deviations may require escalation at executive levels.</li>\n</ul>\n\n<h2>NOTE</h2>\n\n<p>Red Hat prioritizes the servicing of requests for deviations based on partner engagement priorities.</p>\n\n<h2>3.5. TELCO CORE COMMON BASELINE MODEL</h2>\n\n<p>The following configurations and use models are applicable to all telco core use cases. The telco core use cases build on this common baseline of features.</p>\n\n<h3>Cluster topology</h3>\n\n<p>The telco core reference design supports two distinct cluster configuration variants:</p>\n\n<ul>\n<li>• A non-schedulable control plane variant, where user workloads are strictly prohibited from running on master nodes.</li>\n<li>• A schedulable control plane variant, which allows for user workloads to run on master nodes to optimize resource utilization. This variant is only applicable to bare-metal control plane nodes and must be configured at installation time.</li>\n</ul>\n\n<p>All clusters, regardless of the variant, must conform to the following requirements:</p>\n\n<ul>\n<li>• A highly available control plane consisting of three or more nodes.</li>\n<li>• The use of multiple machine config pools.</li>\n</ul>\n\n<h3>Storage</h3>\n\n<p>Telco core use cases require highly available persistent storage as provided by an external storage solution. OpenShift Data Foundation might be used to manage access to the external storage.</p>\n\n<h3>Networking</h3>\n\n<p>Telco core cluster networking conforms to the following requirements:</p>\n\n<ul>\n<li>• Dual stack IPv4/IPv6 (IPv4 primary).</li>\n<li>• Fully disconnected - clusters do not have access to public networking at any point in their lifecycle.</li>\n</ul>\n<ul><li>• Supports multiple networks. Segmented networking provides isolation between operations, administration and maintenance (OAM), signaling, and storage traffic.</li><li>• Cluster network type is OVN-Kubernetes as required for IPv6 support.</li><li>• Telco core clusters have multiple layers of networking supported by underlying RHCOS, SR-IOV Network Operator, Load Balancer and other components. These layers include the following:<ul><li>◦ Cluster networking layer. The cluster network configuration is defined and applied through the installation configuration. Update the configuration during Day 2 operations with the NMSState Operator. Use the initial configuration to establish the following:<ul><li>■ Host interface configuration.</li><li>■ Active/active bonding (LACP).</li></ul></li><li>◦ Secondary/additional network layer. Configure the OpenShift Container Platform CNI through network <b>additionalNetwork</b> or <b>NetworkAttachmentDefinition</b> CRs. Use the initial configuration to configure MACVLAN virtual network interfaces.</li><li>◦ Application workload layer. User plane networking runs in cloud-native network functions (CNFs).</li></ul></li></ul><h3>Service Mesh</h3><p>Telco CNFs can use Service Mesh. Telco core clusters typically include a Service Mesh implementation. The choice of implementation and configuration is outside the scope of this specification.</p><h2>3.6. DEPLOYMENT PLANNING</h2><p>Proper deployment planning is essential for telco core clusters to ensure high availability, minimize service disruption during upgrades, and optimize cluster performance.</p><h3>3.6.1. Worker Nodes and MachineConfigPools</h3><p><b>MachineConfigPools</b> (MCPs) custom resources (CR) enable the subdivision of worker nodes in telco core clusters into different node groups based on customer planning parameters. Careful deployment planning using MCPs is crucial to minimize deployment and upgrade time and, more importantly, to minimize interruption of telco-grade services during cluster upgrades.</p><h4>Description</h4><p>Telco core clusters can use <b>MachineConfigPools</b> (MCPs) to split worker nodes into additional separate roles, for example, due to different hardware profiles. This allows custom tuning for each role and also plays a critical function in speeding up a telco core cluster deployment or upgrade. Multiple MCPs can be used to properly plan cluster upgrades across one or multiple maintenance windows. This is crucial because telco-grade services might otherwise be affected if careful planning is not considered.</p><p>During cluster upgrades, you can pause MCPs while you upgrade the control plane. See \"Performing a canary rollout update\" for more information. This ensures that worker nodes are not rebooted and running workloads remain unaffected until the MCP is unpaused.</p>\n<p>Using careful MCP planning, you can control the timing and order of which set of nodes are upgraded at any time. For more information on how to use MCPs to plan telco upgrades, see \"Applying MachineConfigPool labels to nodes before the update\".</p>\n\n<p>Before beginning the initial deployment, review the following engineering considerations:</p>\n\n<h3>PerformanceProfile and Tuned profile association:</h3>\n\n<p>When using PerformanceProfiles, remember that each Machine Config Pool (MCP) must be linked to exactly one PerformanceProfile or Tuned profile definition. Consequently, even if the desired configuration is identical for multiple MCPs, each MCP still requires its own dedicated PerformanceProfile definition.</p>\n\n<h3>Planning your MCP labeling strategy:</h3>\n\n<p>Plan your MCP labeling with an appropriate strategy to split your worker nodes depending on parameters such as:</p>\n\n<ul style=\"list-style-type: none;\">\n<li>● The worker node type: identifying a group of nodes with equivalent hardware profile, for example workers for control plane Network Functions (NFs) and workers for user data plane NFs.</li>\n<li>● The number of worker nodes per worker node type.</li>\n<li>● The minimum number of MCPs required for an equivalent hardware profile is 1, but could be larger for larger clusters. For example, you may design for more MCPs per hardware profile to support a more granular upgrade where a smaller percentage of the cluster capacity is affected with each step.</li>\n<li>● The update strategy for nodes within an MCP is by upgrade requirements and the chosen <b>maxUnavailable</b> value:\n <ul style=\"list-style-type: none;\">\n<li>○ Number of maintenance windows allowed</li>\n<li>○ Duration of a maintenance window</li>\n<li>○ Total number of worker nodes</li>\n<li>○ Desired <b>maxUnavailable</b> (number of nodes updated concurrently) for the MCP.</li>\n</ul>\n</li>\n<li>● CNF requirements for worker nodes, in terms of:\n <ul style=\"list-style-type: none;\">\n<li>○ Minimum availability per Pod required during an upgrade, configured with a pod disruption budget (PDB). PDBs are crucial to maintain telco service level Agreements (SLAs) during upgrades. For more information about PDB, see \"Understanding how to use pod disruption budgets to specify the number of pods that must be up\".</li>\n<li>○ Minimum true high availability required per Pod, such that each replica runs on separate hardware.</li>\n<li>○ Pod affinity and anti-affinity link: For more information about how to use pod affinity and anti-affinity, see \"Placing pods relative to other pods using affinity and anti-affinity rules\".</li>\n</ul>\n</li>\n<li>● Duration and number of upgrade maintenance windows during which telco-grade services might be affected.</li>\n</ul>\n\n<h2>3.6.2. Zones</h2>\n<p>Designing the cluster to support disruption of multiple nodes simultaneously is critical for high availability (HA) and reduced upgrade times. OpenShift Container Platform and Kubernetes use the label <b>topology.kubernetes.io/zone</b> to create pools of nodes which are subject to a common failure domain. Annotating nodes for topology (availability) zones allows high-availability workloads to spread such that each zone holds only one replica from a set of HA replicated pods. With this spread the loss of a single zone will not violate HA constraints and minimum service availability will be maintained. OpenShift Container Platform and Kubernetes apply a default TopologySpreadConstraint to all replica constructs, such as <b>Service</b>, <b>ReplicaSet</b>, <b>StatefulSet</b> or <b>ReplicationController</b> resources, which spreads the replicas based on the <b>topology.kubernetes.io/zone</b> label. This default allows zone based spread to apply without any change to your workload pod specs.</p><p>Cluster upgrades typically result in node disruption as the underlying OS is updated. In large clusters it is necessary to update multiple nodes concurrently in order to complete upgrades quickly and in as few maintenance windows as possible. By using zones to ensure pod spread, an upgrade can be applied to all nodes in a zone simultaneously (assuming sufficient spare capacity) while maintaining high availability and service availability. The recommended cluster design is to partition nodes into multiple MCPs based on the considerations above and label all nodes in a single MCP as a single zone which is distinct from zones attached to other MCPs. Using this strategy all nodes in an MCP can be updated simultaneously.</p><p>Lifecycle hooks (readiness, liveness, startup and pre-stop) play an important role in ensuring application availability. For upgrades in particular the pre-stop hook allows applications to take necessary steps to prepare for disruption prior to being evicted from the node.</p><h3>Limits and requirements</h3><ul><li>• The default TopologySpreadConstraints (TSC) only apply when an explicit TSC is not given. If your pods have explicit TSC ensure that spread based on zones is included.</li><li>• The cluster must have sufficient spare capacity to tolerate simultaneous update of an MCP. Otherwise the <b>maxUnavailable</b> of the MCP must be set to less than 100%.</li><li>• The ability to update all nodes in an MCP simultaneously further depends on workload design and ability to maintain required service levels with that level of disruption.</li></ul><h3>Engineering Considerations</h3><ul><li>• Pod drain times can significantly impact node update times. Ensure the workload design allows pods to be drained quickly.</li><li>• PodDisruptionBudgets (PDB) are used to enforce high availability requirements.<ul><li>◦ With sufficient zones in the cluster design, a zone can be disrupted or lost without violating the PDB. If there are insufficient zones, or other scheduling constraints restrict the set of available nodes, the scheduling of pods might violate the PDB when the zone is disrupted or lost. During upgrades with simultaneous node updates this might lead to partial serialization of updates.</li><li>◦ PDB with 0 disruptable pods will block node drain and require administrator intervention. This pattern should be avoided for fast and automated upgrades.</li></ul></li></ul><h3>Additional resources</h3><ul><li>• <a href=\"#\">Performing a canary rollout update</a></li><li>• <a href=\"#\">Applying MachineConfigPool labels to nodes before the update</a></li></ul>"},"page_stats":{"kind":"list like","value":[{"page_number":1,"error":false,"token_count":256,"num_chunks":5},{"page_number":2,"error":false,"token_count":48,"num_chunks":1},{"page_number":3,"error":false,"token_count":94,"num_chunks":2},{"page_number":4,"error":false,"token_count":591,"num_chunks":11},{"page_number":5,"error":false,"token_count":1876,"num_chunks":4},{"page_number":6,"error":false,"token_count":1698,"num_chunks":3},{"page_number":7,"error":false,"token_count":1915,"num_chunks":3},{"page_number":8,"error":false,"token_count":1913,"num_chunks":3},{"page_number":9,"error":false,"token_count":1902,"num_chunks":3},{"page_number":10,"error":false,"token_count":2063,"num_chunks":3},{"page_number":11,"error":false,"token_count":2008,"num_chunks":3},{"page_number":12,"error":false,"token_count":1943,"num_chunks":3},{"page_number":13,"error":false,"token_count":249,"num_chunks":3},{"page_number":14,"error":false,"token_count":85,"num_chunks":2},{"page_number":15,"error":false,"token_count":1276,"num_chunks":27},{"page_number":16,"error":false,"token_count":1137,"num_chunks":18},{"page_number":17,"error":false,"token_count":1076,"num_chunks":9},{"page_number":18,"error":false,"token_count":892,"num_chunks":7},{"page_number":19,"error":false,"token_count":1276,"num_chunks":25},{"page_number":20,"error":false,"token_count":974,"num_chunks":14},{"page_number":21,"error":false,"token_count":1300,"num_chunks":18},{"page_number":22,"error":false,"token_count":1251,"num_chunks":17},{"page_number":23,"error":false,"token_count":890,"num_chunks":10},{"page_number":24,"error":false,"token_count":302,"num_chunks":6},{"page_number":25,"error":false,"token_count":756,"num_chunks":10},{"page_number":26,"error":false,"token_count":943,"num_chunks":12},{"page_number":27,"error":false,"token_count":1307,"num_chunks":22},{"page_number":28,"error":false,"token_count":963,"num_chunks":12},{"page_number":29,"error":false,"token_count":970,"num_chunks":10},{"page_number":30,"error":false,"token_count":1096,"num_chunks":11}],"string":"[\n {\n \"page_number\": 1,\n \"error\": false,\n \"token_count\": 256,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 2,\n \"error\": false,\n \"token_count\": 48,\n \"num_chunks\": 1\n },\n {\n \"page_number\": 3,\n \"error\": false,\n \"token_count\": 94,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 4,\n \"error\": false,\n \"token_count\": 591,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 5,\n \"error\": false,\n \"token_count\": 1876,\n \"num_chunks\": 4\n },\n {\n \"page_number\": 6,\n \"error\": false,\n \"token_count\": 1698,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 7,\n \"error\": false,\n \"token_count\": 1915,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 8,\n \"error\": false,\n \"token_count\": 1913,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 9,\n \"error\": false,\n \"token_count\": 1902,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 10,\n \"error\": false,\n \"token_count\": 2063,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 11,\n \"error\": false,\n \"token_count\": 2008,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 12,\n \"error\": false,\n \"token_count\": 1943,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 13,\n \"error\": false,\n \"token_count\": 249,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 14,\n \"error\": false,\n \"token_count\": 85,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 15,\n \"error\": false,\n \"token_count\": 1276,\n \"num_chunks\": 27\n },\n {\n \"page_number\": 16,\n \"error\": false,\n \"token_count\": 1137,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 17,\n \"error\": false,\n \"token_count\": 1076,\n \"num_chunks\": 9\n },\n {\n \"page_number\": 18,\n \"error\": false,\n \"token_count\": 892,\n \"num_chunks\": 7\n },\n {\n \"page_number\": 19,\n \"error\": false,\n \"token_count\": 1276,\n \"num_chunks\": 25\n },\n {\n \"page_number\": 20,\n \"error\": false,\n \"token_count\": 974,\n \"num_chunks\": 14\n },\n {\n \"page_number\": 21,\n \"error\": false,\n \"token_count\": 1300,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 22,\n \"error\": false,\n \"token_count\": 1251,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 23,\n \"error\": false,\n \"token_count\": 890,\n \"num_chunks\": 10\n },\n {\n \"page_number\": 24,\n \"error\": false,\n \"token_count\": 302,\n \"num_chunks\": 6\n },\n {\n \"page_number\": 25,\n \"error\": false,\n \"token_count\": 756,\n \"num_chunks\": 10\n },\n {\n \"page_number\": 26,\n \"error\": false,\n \"token_count\": 943,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 27,\n \"error\": false,\n \"token_count\": 1307,\n \"num_chunks\": 22\n },\n {\n \"page_number\": 28,\n \"error\": false,\n \"token_count\": 963,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 29,\n \"error\": false,\n \"token_count\": 970,\n \"num_chunks\": 10\n },\n {\n \"page_number\": 30,\n \"error\": false,\n \"token_count\": 1096,\n \"num_chunks\": 11\n }\n]","isConversational":false}}},{"rowIdx":93,"cells":{"source_id":{"kind":"string","value":"OpenShift_Container_Platform-4.21-Schedule_and_quota_APIs-en-US"},"pdf_url":{"kind":"string","value":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/schedule_and_quota_apis/OpenShift_Container_Platform-4.21-Schedule_and_quota_APIs-en-US.pdf"},"status":{"kind":"string","value":"success"},"processed_at":{"kind":"string","value":"2026-04-15T18:34:55.030140+00:00"},"elapsed_seconds":{"kind":"number","value":63.76,"string":"63.76"},"num_pages":{"kind":"number","value":102,"string":"102"},"num_pages_processed":{"kind":"number","value":30,"string":"30"},"max_pages_per_paper":{"kind":"number","value":30,"string":"30"},"pdf_exceeds_page_limit":{"kind":"bool","value":true,"string":"true"},"failed_pages":{"kind":"list like","value":[],"string":"[]","isConversational":false},"prompt_type":{"kind":"string","value":"ocr_layout"},"model_id":{"kind":"string","value":"datalab-to/chandra-ocr-2"},"script_version":{"kind":"timestamp","value":"2026-04-15T00:00:00","string":"2026-04-15T00:00:00"},"markdown":{"kind":"string","value":"# OpenShift Container Platform 4.21\n\n## Schedule and quota APIs\n\nReference guide for schedule and quota APIs# OpenShift Container Platform 4.21 Schedule and quota APIs\n\n---\n\nReference guide for schedule and quota APIs## Legal Notice\n\nCopyright © Red Hat.\n\nExcept as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.\n\nRed Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.\n\nRed Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.\n\nLinux ® is the registered trademark of Linus Torvalds in the United States and other countries.\n\nXFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.\n\nThe OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.\n\nAll other trademarks are the property of their respective owners.\n\n## Abstract\n\nThis document describes the OpenShift Container Platform schedule and quota API objects and their detailed specifications.# Table of Contents\n\n<table>\n<tr>\n<td><b>CHAPTER 1. SCHEDULE AND QUOTA APIS</b> .....</td>\n<td><b>5</b></td>\n</tr>\n<tr>\n<td> 1.1. APPLIEDCLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.2. CLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.3. FLOWSHEMA [FLOWCONTROL.APISERVER.K8S.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.4. LIMITRANGE [V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.5. PRIORITYCLASS [SCHEDULING.K8S.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.6. PRIORITYLEVELCONFIGURATION [FLOWCONTROL.APISERVER.K8S.IO/V1]</td>\n<td>6</td>\n</tr>\n<tr>\n<td> 1.7. RESOURCEQUOTA [V1]</td>\n<td>6</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. APPLIEDCLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>7</b></td>\n</tr>\n<tr>\n<td> 2.1. SPECIFICATION</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 2.1.1. .spec</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.1.2. .spec.selector</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.1.3. .status</td>\n<td>9</td>\n</tr>\n<tr>\n<td> 2.1.4. .status.namespaces</td>\n<td>9</td>\n</tr>\n<tr>\n<td> 2.1.5. .status.namespaces[]</td>\n<td>10</td>\n</tr>\n<tr>\n<td> 2.2. API ENDPOINTS</td>\n<td>10</td>\n</tr>\n<tr>\n<td> 2.2.1. /apis/quota.openshift.io/v1/appliedclusterresourcequotas</td>\n<td>10</td>\n</tr>\n<tr>\n<td> 2.2.2. /apis/quota.openshift.io/v1/namespaces/{namespace}/appliedclusterresourcequotas</td>\n<td>11</td>\n</tr>\n<tr>\n<td> 2.2.3. /apis/quota.openshift.io/v1/namespaces/{namespace}/appliedclusterresourcequotas/{name}</td>\n<td>11</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. CLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>12</b></td>\n</tr>\n<tr>\n<td> 3.1. SPECIFICATION</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 3.1.1. .spec</td>\n<td>13</td>\n</tr>\n<tr>\n<td> 3.1.2. .spec.quota</td>\n<td>13</td>\n</tr>\n<tr>\n<td> 3.1.3. .spec.quota.scopeSelector</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 3.1.4. .spec.quota.scopeSelector.matchExpressions</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 3.1.5. .spec.quota.scopeSelector.matchExpressions[]</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 3.1.6. .spec.selector</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 3.1.7. .status</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 3.1.8. .status.total</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 3.2. API ENDPOINTS</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 3.2.1. /apis/quota.openshift.io/v1/clusterresourcequotas</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 3.2.2. /apis/quota.openshift.io/v1/watch/clusterresourcequotas</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.3. /apis/quota.openshift.io/v1/clusterresourcequotas/{name}</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.4. /apis/quota.openshift.io/v1/watch/clusterresourcequotas/{name}</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 3.2.5. /apis/quota.openshift.io/v1/clusterresourcequotas/{name}/status</td>\n<td>23</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. FLOWSHEMA [FLOWCONTROL.APISERVER.K8S.IO/V1]</b> .....</td>\n<td><b>26</b></td>\n</tr>\n<tr>\n<td> 4.1. SPECIFICATION</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 4.1.1. .spec</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 4.1.2. .spec.distinguisherMethod</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 4.1.3. .spec.priorityLevelConfiguration</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 4.1.4. .spec.rules</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 4.1.5. .spec.rules[]</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 4.1.6. .spec.rules[].nonResourceRules</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 4.1.7. .spec.rules[].nonResourceRules[]</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 4.1.8. .spec.rules[].resourceRules</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 4.1.9. .spec.rules[].resourceRules[]</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 4.1.10. .spec.rules[].subjects</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 4.1.11. .spec.rules[].subjects[]</td>\n<td>34</td>\n</tr>\n<tr>\n<td> 4.1.12. .spec.rules[].subjects[].group</td>\n<td>34</td>\n</tr>\n</table><table>\n<tbody>\n<tr>\n<td>4.1.13. .spec.rules[].subjects[].serviceAccount</td>\n<td>35</td>\n</tr>\n<tr>\n<td>4.1.14. .spec.rules[].subjects[].user</td>\n<td>35</td>\n</tr>\n<tr>\n<td>4.1.15. .status</td>\n<td>36</td>\n</tr>\n<tr>\n<td>4.1.16. .status.conditions</td>\n<td>36</td>\n</tr>\n<tr>\n<td>4.1.17. .status.conditions[]</td>\n<td>36</td>\n</tr>\n<tr>\n<td><b>4.2. API ENDPOINTS</b></td>\n<td><b>37</b></td>\n</tr>\n<tr>\n<td>4.2.1. /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas</td>\n<td>38</td>\n</tr>\n<tr>\n<td>4.2.2. /apis/flowcontrol.apiserver.k8s.io/v1/watch/flowschemas</td>\n<td>39</td>\n</tr>\n<tr>\n<td>4.2.3. /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas/{name}</td>\n<td>40</td>\n</tr>\n<tr>\n<td>4.2.4. /apis/flowcontrol.apiserver.k8s.io/v1/watch/flowschemas/{name}</td>\n<td>43</td>\n</tr>\n<tr>\n<td>4.2.5. /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas/{name}/status</td>\n<td>43</td>\n</tr>\n<tr>\n<td><b>CHAPTER 5. LIMITRANGE [V1]</b></td>\n<td><b>47</b></td>\n</tr>\n<tr>\n<td>5.1. SPECIFICATION</td>\n<td>47</td>\n</tr>\n<tr>\n<td>5.1.1. .spec</td>\n<td>47</td>\n</tr>\n<tr>\n<td>5.1.2. .spec.limits</td>\n<td>48</td>\n</tr>\n<tr>\n<td>5.1.3. .spec.limits[]</td>\n<td>48</td>\n</tr>\n<tr>\n<td>5.2. API ENDPOINTS</td>\n<td>49</td>\n</tr>\n<tr>\n<td>5.2.1. /api/v1/limitranges</td>\n<td>50</td>\n</tr>\n<tr>\n<td>5.2.2. /api/v1/watch/limitranges</td>\n<td>50</td>\n</tr>\n<tr>\n<td>5.2.3. /api/v1/namespaces/{namespace}/limitranges</td>\n<td>50</td>\n</tr>\n<tr>\n<td>5.2.4. /api/v1/watch/namespaces/{namespace}/limitranges</td>\n<td>52</td>\n</tr>\n<tr>\n<td>5.2.5. /api/v1/namespaces/{namespace}/limitranges/{name}</td>\n<td>53</td>\n</tr>\n<tr>\n<td>5.2.6. /api/v1/watch/namespaces/{namespace}/limitranges/{name}</td>\n<td>56</td>\n</tr>\n<tr>\n<td><b>CHAPTER 6. PRIORITYCLASS [SCHEDULING.K8S.IO/V1]</b></td>\n<td><b>57</b></td>\n</tr>\n<tr>\n<td>6.1. SPECIFICATION</td>\n<td>57</td>\n</tr>\n<tr>\n<td>6.2. API ENDPOINTS</td>\n<td>58</td>\n</tr>\n<tr>\n<td>6.2.1. /apis/scheduling.k8s.io/v1/priorityclasses</td>\n<td>59</td>\n</tr>\n<tr>\n<td>6.2.2. /apis/scheduling.k8s.io/v1/watch/priorityclasses</td>\n<td>61</td>\n</tr>\n<tr>\n<td>6.2.3. /apis/scheduling.k8s.io/v1/priorityclasses/{name}</td>\n<td>61</td>\n</tr>\n<tr>\n<td>6.2.4. /apis/scheduling.k8s.io/v1/watch/priorityclasses/{name}</td>\n<td>64</td>\n</tr>\n<tr>\n<td><b>CHAPTER 7. PRIORITYLEVELCONFIGURATION [FLOWCONTROL.APISERVER.K8S.IO/V1]</b></td>\n<td><b>66</b></td>\n</tr>\n<tr>\n<td>7.1. SPECIFICATION</td>\n<td>66</td>\n</tr>\n<tr>\n<td>7.1.1. .spec</td>\n<td>67</td>\n</tr>\n<tr>\n<td>7.1.2. .spec.exempt</td>\n<td>67</td>\n</tr>\n<tr>\n<td>7.1.3. .spec.limited</td>\n<td>68</td>\n</tr>\n<tr>\n<td>7.1.4. .spec.limited.limitResponse</td>\n<td>71</td>\n</tr>\n<tr>\n<td>7.1.5. .spec.limited.limitResponse.queuing</td>\n<td>72</td>\n</tr>\n<tr>\n<td>7.1.6. .status</td>\n<td>73</td>\n</tr>\n<tr>\n<td>7.1.7. .status.conditions</td>\n<td>73</td>\n</tr>\n<tr>\n<td>7.1.8. .status.conditions[]</td>\n<td>73</td>\n</tr>\n<tr>\n<td>7.2. API ENDPOINTS</td>\n<td>74</td>\n</tr>\n<tr>\n<td>7.2.1. /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations</td>\n<td>75</td>\n</tr>\n<tr>\n<td>7.2.2. /apis/flowcontrol.apiserver.k8s.io/v1/watch/prioritylevelconfigurations</td>\n<td>77</td>\n</tr>\n<tr>\n<td>7.2.3. /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations/{name}</td>\n<td>77</td>\n</tr>\n<tr>\n<td>7.2.4. /apis/flowcontrol.apiserver.k8s.io/v1/watch/prioritylevelconfigurations/{name}</td>\n<td>80</td>\n</tr>\n<tr>\n<td>7.2.5. /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations/{name}/status</td>\n<td>81</td>\n</tr>\n<tr>\n<td><b>CHAPTER 8. RESOURCEQUOTA [V1]</b></td>\n<td><b>84</b></td>\n</tr>\n<tr>\n<td>8.1. SPECIFICATION</td>\n<td>84</td>\n</tr>\n<tr>\n<td>8.1.1. .spec</td>\n<td>84</td>\n</tr>\n<tr>\n<td>8.1.2. .spec.scopeSelector</td>\n<td>85</td>\n</tr>\n</tbody>\n</table>---\n\n<table><tr><td>8.1.3. .spec.scopeSelector.matchExpressions</td><td>85</td></tr><tr><td>8.1.4. .spec.scopeSelector.matchExpressions[]</td><td>86</td></tr><tr><td>8.1.5. .status</td><td>87</td></tr><tr><td>8.2. API ENDPOINTS</td><td>88</td></tr><tr><td>8.2.1. /api/v1/resourcequotas</td><td>89</td></tr><tr><td>8.2.2. /api/v1/watch/resourcequotas</td><td>89</td></tr><tr><td>8.2.3. /api/v1/namespaces/{namespace}/resourcequotas</td><td>89</td></tr><tr><td>8.2.4. /api/v1/watch/namespaces/{namespace}/resourcequotas</td><td>91</td></tr><tr><td>8.2.5. /api/v1/namespaces/{namespace}/resourcequotas/{name}</td><td>92</td></tr><tr><td>8.2.6. /api/v1/watch/namespaces/{namespace}/resourcequotas/{name}</td><td>95</td></tr><tr><td>8.2.7. /api/v1/namespaces/{namespace}/resourcequotas/{name}/status</td><td>95</td></tr></table>## CHAPTER 1. SCHEDULE AND QUOTA APIS\n\n### 1.1. APPLIEDCLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]\n\n#### Description\n\nAppliedClusterResourceQuota mirrors ClusterResourceQuota at a project scope, for projection into a project. It allows a project-admin to know which ClusterResourceQuotas are applied to his project and their associated usage.\n\nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n#### Type\n\n**object**\n\n### 1.2. CLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]\n\n#### Description\n\nClusterResourceQuota mirrors ResourceQuota at a cluster scope. This object is easily convertible to synthetic ResourceQuota object to allow quota evaluation re-use.\n\nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n#### Type\n\n**object**\n\n### 1.3. FLOWSCHEMA [FLOWCONTROL.APISERVER.K8S.IO/V1]\n\n#### Description\n\nFlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a \"flow distinguisher\".\n\n#### Type\n\n**object**\n\n### 1.4. LIMITRANGE [V1]\n\n#### Description\n\nLimitRange sets resource usage limits for each kind of resource in a Namespace.\n\n#### Type\n\n**object**\n\n### 1.5. PRIORITYCLASS [SCHEDULING.K8S.IO/V1]\n\n#### Description\n\nPriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.\n\n#### Type**object**\n\n## 1.6. PRIORITYLEVELCONFIGURATION [FLOWCONTROL.APISERVER.K8S.IO/V1]\n\n### Description\n\nPriorityLevelConfiguration represents the configuration of a priority level.\n\n### Type\n\n**object**\n\n## 1.7. RESOURCEQUOTA [V1]\n\n### Description\n\nResourceQuota sets aggregate quota restrictions enforced per namespace\n\n### Type\n\n**object**# CHAPTER 2. APPLIEDCLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]\n\n## Description\n\nAppliedClusterResourceQuota mirrors ClusterResourceQuota at a project scope, for projection into a project. It allows a project-admin to know which ClusterResourceQuotas are applied to his project and their associated usage.\n\nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n## Type\n\n**object**\n\n## Required\n\n- • **metadata**\n- • **spec**\n\n## 2.1. SPECIFICATION\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta_v2</b></td>\n<td>metadata is the standard object's metadata. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</a></td>\n</tr>\n<tr>\n<td><b>spec</b></td>\n<td><b>object</b></td>\n<td>ClusterResourceQuotaSpec defines the desired quota restrictions</td>\n</tr>\n<tr>\n<td><b>status</b></td>\n<td><b>object</b></td>\n<td>ClusterResourceQuotaStatus defines the actual enforced quota and its current usage</td>\n</tr>\n</tbody>\n</table>\n\n### 2.1.1. .spec\n\n#### Description\n\nClusterResourceQuotaSpec defines the desired quota restrictions\n\n#### Type\n\n**object**\n\n#### Required\n\n- • **selector**\n- • **quota**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>quota</b></td>\n<td><b>ResourceQuotaSpec_v2</b></td>\n<td>Quota defines the desired quota</td>\n</tr>\n<tr>\n<td><b>selector</b></td>\n<td><b>object</b></td>\n<td>ClusterResourceQuotaSelector is used to select projects. At least one of LabelSelector or AnnotationSelector must present. If only one is present, it is the only selection criteria. If both are specified, the project must match both restrictions.</td>\n</tr>\n</tbody>\n</table>\n\n### 2.1.2. .spec.selector\n\n#### Description\n\nClusterResourceQuotaSelector is used to select projects. At least one of LabelSelector or AnnotationSelector must present. If only one is present, it is the only selection criteria. If both are specified, the project must match both restrictions.Type\n\n**object**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>annotations</b></td>\n<td><b>object (string)</b></td>\n<td>AnnotationSelector is used to select projects by annotation.</td>\n</tr>\n<tr>\n<td><b>labels</b></td>\n<td><b>LabelSelector_v4</b></td>\n<td>LabelSelector is used to select projects by label.</td>\n</tr>\n</tbody>\n</table>\n\n### 2.1.3. .status\n\nDescription\n\nClusterResourceQuotaStatus defines the actual enforced quota and its current usage\n\nType\n\n**object**\n\nRequired\n\n- • **total**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>namespaces</b></td>\n<td><b>array</b></td>\n<td>Namespaces slices the usage by project. This division allows for quick resolution of deletion reconciliation inside of a single project without requiring a recalculation across all projects. This can be used to pull the deltas for a given project.</td>\n</tr>\n<tr>\n<td><b>namespaces[]</b></td>\n<td><b>object</b></td>\n<td>ResourceQuotaStatusByNamespace gives status for a particular project</td>\n</tr>\n<tr>\n<td><b>total</b></td>\n<td><b>ResourceQuotaStatus</b></td>\n<td>Total defines the actual enforced quota and its current usage across all projects</td>\n</tr>\n</tbody>\n</table>\n\n### 2.1.4. .status.namespaces\n\nDescription\n\nNamespaces slices the usage by project. This division allows for quick resolution of deletion reconciliation inside of a single project without requiring a recalculation across all projects. This can be used to pull the deltas for a given project.\n\nType**array**\n\n### 2.1.5. .status.namespaces[]\n\n**Description**\n\nResourceQuotaStatusByNamespace gives status for a particular project\n\n**Type****object****Required**\n\n- • **namespace**\n- • **status**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>namespace</b></td>\n<td><b>string</b></td>\n<td>Namespace the project this status applies to</td>\n</tr>\n<tr>\n<td><b>status</b></td>\n<td><b>ResourceQuotaStatus</b></td>\n<td>Status indicates how many resources have been consumed by this project</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2. API ENDPOINTS\n\nThe following API endpoints are available:\n\n- • **/apis/quota.openshift.io/v1/appliedclusterresourcequotas**\n - ◦ **GET**: list objects of kind AppliedClusterResourceQuota\n- • **/apis/quota.openshift.io/v1/namespaces/{namespace}/appliedclusterresourcequotas**\n - ◦ **GET**: list objects of kind AppliedClusterResourceQuota\n- • **/apis/quota.openshift.io/v1/namespaces/{namespace}/appliedclusterresourcequotas/{name}**\n - ◦ **GET**: read the specified AppliedClusterResourceQuota\n\n### 2.2.1. /apis/quota.openshift.io/v1/appliedclusterresourcequotas\n\n**HTTP method****GET****Description**\n\nlist objects of kind AppliedClusterResourceQuota\n\nTable 2.1. HTTP responses<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">AppliedClusterResourceQuotaList</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.2. /apis/quota.openshift.io/v1/namespaces/{namespace}/appliedclusterresourcequota\n\nHTTP method\n\n**GET**\n\nDescription\n\nlist objects of kind AppliedClusterResourceQuota\n\nTable 2.2. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">AppliedClusterResourceQuotaList</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.3. /apis/quota.openshift.io/v1/namespaces/{namespace}/appliedclusterresourcequota\n\nTable 2.3. Global path parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the AppliedClusterResourceQuota</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**GET**\n\nDescription\n\nread the specified AppliedClusterResourceQuota\n\nTable 2.4. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">AppliedClusterResourceQuota</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>## CHAPTER 3. CLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]\n\n### Description\n\nClusterResourceQuota mirrors ResourceQuota at a cluster scope. This object is easily convertible to synthetic ResourceQuota object to allow quota evaluation re-use.\n\nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n### Type\n\n**object**\n\n### Required\n\n- • **metadata**\n- • **spec**\n\n### 3.1. SPECIFICATION\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta</b></td>\n<td>Standard object's metadata. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</a></td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>spec</b></td>\n<td><b>object</b></td>\n<td>spec defines the desired quota</td>\n</tr>\n<tr>\n<td><b>status</b></td>\n<td><b>object</b></td>\n<td>status defines the actual enforced quota and its current usage</td>\n</tr>\n</tbody>\n</table>\n\n### 3.1.1. .spec\n\n#### Description\n\nspec defines the desired quota\n\n#### Type\n\n**object**\n\n#### Required\n\n- • **quota**\n- • **selector**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>quota</b></td>\n<td><b>object</b></td>\n<td>quota defines the desired quota</td>\n</tr>\n<tr>\n<td><b>selector</b></td>\n<td><b>object</b></td>\n<td>selector is the selector used to match projects. It should only select active projects on the scale of dozens (though it can select many more less active projects). These projects will contend on object creation through this resource.</td>\n</tr>\n</tbody>\n</table>\n\n### 3.1.2. .spec.quota\n\n#### Description\n\nquota defines the desired quota\n\n#### Type\n\n**object**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>hard</b></td>\n<td><b>integer-or-string</b></td>\n<td>hard is the set of desired hard limits for each named resource.<br/>More info:<br/><a href=\"https://kubernetes.io/docs/concepts/policy/resource-quotas/\">https://kubernetes.io/docs/concepts/policy/resource-quotas/</a></td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>scopeSelector</b></td>\n<td><b>object</b></td>\n<td>scopeSelector is also a collection of filters like scopes that must match each object tracked by a quota but expressed using ScopeSelectorOperator in combination with possible values. For a resource to match, both scopes AND scopeSelector (if specified in spec), must be matched.</td>\n</tr>\n<tr>\n<td><b>scopes</b></td>\n<td><b>array (string)</b></td>\n<td>A collection of filters that must match each object tracked by a quota. If not specified, the quota matches all objects.</td>\n</tr>\n</tbody>\n</table>\n\n### 3.1.3. .spec.quota.scopeSelector\n\n#### Description\n\nscopeSelector is also a collection of filters like scopes that must match each object tracked by a quota but expressed using ScopeSelectorOperator in combination with possible values. For a resource to match, both scopes AND scopeSelector (if specified in spec), must be matched.\n\n#### Type\n\n**object**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>matchExpressions</b></td>\n<td><b>array</b></td>\n<td>A list of scope selector requirements by scope of the resources.</td>\n</tr>\n<tr>\n<td><b>matchExpressions[]</b></td>\n<td><b>object</b></td>\n<td>A scoped-resource selector requirement is a selector that contains values, a scope name, and an operator that relates the scope name and values.</td>\n</tr>\n</tbody>\n</table>\n\n### 3.1.4. .spec.quota.scopeSelector.matchExpressions\n\n#### Description\n\nA list of scope selector requirements by scope of the resources.\n\n#### Type\n\n**array**\n\n### 3.1.5. .spec.quota.scopeSelector.matchExpressions[]\n\n#### DescriptionA scoped-resource selector requirement is a selector that contains values, a scope name, and an operator that relates the scope name and values.\n\n#### Type\n\n**object**\n\n#### Required\n\n- • **operator**\n- • **scopeName**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>operator</b></td>\n<td><b>string</b></td>\n<td>Represents a scope's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist.</td>\n</tr>\n<tr>\n<td><b>scopeName</b></td>\n<td><b>string</b></td>\n<td>The name of the scope that the selector applies to.</td>\n</tr>\n<tr>\n<td><b>values</b></td>\n<td><b>array (string)</b></td>\n<td>An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.</td>\n</tr>\n</tbody>\n</table>\n\n### 3.1.6. .spec.selector\n\n#### Description\n\nselector is the selector used to match projects. It should only select active projects on the scale of dozens (though it can select many more less active projects). These projects will contend on object creation through this resource.\n\n#### Type\n\n**object**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>annotations</b></td>\n<td><b>undefined (string)</b></td>\n<td>AnnotationSelector is used to select projects by annotation.</td>\n</tr>\n<tr>\n<td><b>labels</b></td>\n<td><b>..</b></td>\n<td>LabelSelector is used to select projects by label.</td>\n</tr>\n</tbody>\n</table>\n\n### 3.1.7. .status**Description**\n\nstatus defines the actual enforced quota and its current usage\n\n**Type**\n\n**object**\n\n**Required**\n\n- • **total**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>namespaces</b></td>\n<td><b>string</b></td>\n<td>namespaces slices the usage by project. This division allows for quick resolution of deletion reconciliation inside of a single project without requiring a recalculation across all projects. This can be used to pull the deltas for a given project.</td>\n</tr>\n<tr>\n<td><b>total</b></td>\n<td><b>object</b></td>\n<td>total defines the actual enforced quota and its current usage across all projects</td>\n</tr>\n</tbody>\n</table>\n\n**3.1.8. .status.total****Description**\n\ntotal defines the actual enforced quota and its current usage across all projects\n\n**Type**\n\n**object**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>hard</b></td>\n<td><b>integer-or-string</b></td>\n<td>Hard is the set of enforced hard limits for each named resource. More info: <a href=\"https://kubernetes.io/docs/concepts/policy/resource-quotas/\">https://kubernetes.io/docs/concepts/policy/resource-quotas/</a></td>\n</tr>\n<tr>\n<td><b>used</b></td>\n<td><b>integer-or-string</b></td>\n<td>Used is the current observed total usage of the resource in the namespace.</td>\n</tr>\n</tbody>\n</table>\n\n**3.2. API ENDPOINTS**\n\nThe following API endpoints are available:\n\n- • **/apis/quota.openshift.io/v1/clustresourcequotas**\n\n• **DELETE /apis/quota.openshift.io/v1/clustresourcequotas**- ◦ **DELETE**: delete collection of ClusterResourceQuota\n- ◦ **GET**: list objects of kind ClusterResourceQuota\n- ◦ **POST**: create a ClusterResourceQuota\n- • **/apis/quota.openshift.io/v1/watch/clusterresourcequotas**\n - ◦ **GET**: watch individual changes to a list of ClusterResourceQuota. deprecated: use the 'watch' parameter with a list operation instead.\n- • **/apis/quota.openshift.io/v1/clusterresourcequotas/{name}**\n - ◦ **DELETE**: delete a ClusterResourceQuota\n - ◦ **GET**: read the specified ClusterResourceQuota\n - ◦ **PATCH**: partially update the specified ClusterResourceQuota\n - ◦ **PUT**: replace the specified ClusterResourceQuota\n- • **/apis/quota.openshift.io/v1/watch/clusterresourcequotas/{name}**\n - ◦ **GET**: watch changes to an object of kind ClusterResourceQuota. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.\n- • **/apis/quota.openshift.io/v1/clusterresourcequotas/{name}/status**\n - ◦ **GET**: read status of the specified ClusterResourceQuota\n - ◦ **PATCH**: partially update status of the specified ClusterResourceQuota\n - ◦ **PUT**: replace status of the specified ClusterResourceQuota\n\n### 3.2.1. /apis/quota.openshift.io/v1/clusterresourcequotas\n\nHTTP method\n\n**DELETE**\n\nDescription\n\ndelete collection of ClusterResourceQuota\n\nTable 3.1. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**GET**\n\nDescriptionlist objects of kind ClusterResourceQuota\n\nTable 3.2. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">ClusterResourceQuotaList</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**POST**\n\nDescription\n\ncreate a ClusterResourceQuota\n\nTable 3.3. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 3.4. Body parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterResourceQuota</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nTable 3.5. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### 3.2.2. /apis/quota.openshift.io/v1/watch/clustresourcequotas\n\nHTTP method\n\n**GET**\n\nDescription\n\nwatch individual changes to a list of ClusterResourceQuota. deprecated: use the 'watch' parameter with a list operation instead.\n\nTable 3.6. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>WatchEvent</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### 3.2.3. /apis/quota.openshift.io/v1/clustresourcequotas/{name}\n\nTable 3.7. Global path parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the ClusterResourceQuota</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**DELETE**\n\nDescription\n\ndelete a ClusterResourceQuotaTable 3.8. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n\nTable 3.9. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method**GET**Description\n\nread the specified ClusterResourceQuota\n\nTable 3.10. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method**PATCH**Description\n\npartially update the specified ClusterResourceQuota\n\nTable 3.11. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are:\n<ul>\n<li>- Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23.</li>\n<li>- Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+.</li>\n<li>- Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>\n\nTable 3.12. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method**PUT**Description\n\nreplace the specified ClusterResourceQuota\n\nTable 3.13. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are:\n<ul>\n<li>- All: all dry run stages will be processed</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are:\n<ul>\n<li>- Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23.</li>\n<li>- Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+.</li>\n<li>- Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>\n\nTable 3.14. Body parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterResourceQuota</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nTable 3.15. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### 3.2.4. /apis/quota.openshift.io/v1/watch/clusterresourcequotas/{name}\n\nTable 3.16. Global path parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the ClusterResourceQuota</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method**GET****Description**\n\nwatch changes to an object of kind ClusterResourceQuota. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.\n\n**Table 3.17. HTTP responses**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>WatchEvent</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n**3.2.5. /apis/quota.openshift.io/v1/clusterresourcequotas/{name}/status****Table 3.18. Global path parameters**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the ClusterResourceQuota</td>\n</tr>\n</tbody>\n</table>\n\n**HTTP method****GET****Description**\n\nread status of the specified ClusterResourceQuota\n\n**Table 3.19. HTTP responses**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n**HTTP method****PATCH****Description**\n\npartially update status of the specified ClusterResourceQuota\n\n**Table 3.20. Query parameters**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 3.21. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n**HTTP method****PUT****Description**\n\nreplace status of the specified ClusterResourceQuota\n\nTable 3.22. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 3.23. Body parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterResourceQuota</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nTable 3.24. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>## CHAPTER 4. FLOWSCHEMA [FLOWCONTROL.APISERVER.K8S.IO/V1]\n\n### Description\n\nFlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a \"flow distinguisher\".\n\n### Type\n\n**object**\n\n## 4.1. SPECIFICATION\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta</b></td>\n<td><b>metadata</b> is the standard object's metadata. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</a></td>\n</tr>\n<tr>\n<td><b>spec</b></td>\n<td><b>object</b></td>\n<td>FlowSchemaSpec describes how the FlowSchema's specification looks like.</td>\n</tr>\n</tbody>\n</table>"},"html":{"kind":"string","value":"<h1>OpenShift Container Platform 4.21</h1><h2>Schedule and quota APIs</h2><p>Reference guide for schedule and quota APIs</p><h1>OpenShift Container Platform 4.21 Schedule and quota APIs</h1><hr/><p>Reference guide for schedule and quota APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.</p><p>Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.</p><p>Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.</p><p>Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.</p><p>XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.</p><p>The OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.</p><p>All other trademarks are the property of their respective owners.</p><h2>Abstract</h2><p>This document describes the OpenShift Container Platform schedule and quota API objects and their detailed specifications.</p>\n<h1>Table of Contents</h1>\n\n<table>\n<tr>\n<td><b>CHAPTER 1. SCHEDULE AND QUOTA APIS</b> .....</td>\n<td><b>5</b></td>\n</tr>\n<tr>\n<td> 1.1. APPLIEDCLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.2. CLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.3. FLOWSHEMA [FLOWCONTROL.APISERVER.K8S.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.4. LIMITRANGE [V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.5. PRIORITYCLASS [SCHEDULING.K8S.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.6. PRIORITYLEVELCONFIGURATION [FLOWCONTROL.APISERVER.K8S.IO/V1]</td>\n<td>6</td>\n</tr>\n<tr>\n<td> 1.7. RESOURCEQUOTA [V1]</td>\n<td>6</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. APPLIEDCLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>7</b></td>\n</tr>\n<tr>\n<td> 2.1. SPECIFICATION</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 2.1.1. .spec</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.1.2. .spec.selector</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.1.3. .status</td>\n<td>9</td>\n</tr>\n<tr>\n<td> 2.1.4. .status.namespaces</td>\n<td>9</td>\n</tr>\n<tr>\n<td> 2.1.5. .status.namespaces[]</td>\n<td>10</td>\n</tr>\n<tr>\n<td> 2.2. API ENDPOINTS</td>\n<td>10</td>\n</tr>\n<tr>\n<td> 2.2.1. /apis/quota.openshift.io/v1/appliedclusterresourcequotas</td>\n<td>10</td>\n</tr>\n<tr>\n<td> 2.2.2. /apis/quota.openshift.io/v1/namespaces/{namespace}/appliedclusterresourcequotas</td>\n<td>11</td>\n</tr>\n<tr>\n<td> 2.2.3. /apis/quota.openshift.io/v1/namespaces/{namespace}/appliedclusterresourcequotas/{name}</td>\n<td>11</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. CLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>12</b></td>\n</tr>\n<tr>\n<td> 3.1. SPECIFICATION</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 3.1.1. .spec</td>\n<td>13</td>\n</tr>\n<tr>\n<td> 3.1.2. .spec.quota</td>\n<td>13</td>\n</tr>\n<tr>\n<td> 3.1.3. .spec.quota.scopeSelector</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 3.1.4. .spec.quota.scopeSelector.matchExpressions</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 3.1.5. .spec.quota.scopeSelector.matchExpressions[]</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 3.1.6. .spec.selector</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 3.1.7. .status</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 3.1.8. .status.total</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 3.2. API ENDPOINTS</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 3.2.1. /apis/quota.openshift.io/v1/clusterresourcequotas</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 3.2.2. /apis/quota.openshift.io/v1/watch/clusterresourcequotas</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.3. /apis/quota.openshift.io/v1/clusterresourcequotas/{name}</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.4. /apis/quota.openshift.io/v1/watch/clusterresourcequotas/{name}</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 3.2.5. /apis/quota.openshift.io/v1/clusterresourcequotas/{name}/status</td>\n<td>23</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. FLOWSHEMA [FLOWCONTROL.APISERVER.K8S.IO/V1]</b> .....</td>\n<td><b>26</b></td>\n</tr>\n<tr>\n<td> 4.1. SPECIFICATION</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 4.1.1. .spec</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 4.1.2. .spec.distinguisherMethod</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 4.1.3. .spec.priorityLevelConfiguration</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 4.1.4. .spec.rules</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 4.1.5. .spec.rules[]</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 4.1.6. .spec.rules[].nonResourceRules</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 4.1.7. .spec.rules[].nonResourceRules[]</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 4.1.8. .spec.rules[].resourceRules</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 4.1.9. .spec.rules[].resourceRules[]</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 4.1.10. .spec.rules[].subjects</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 4.1.11. .spec.rules[].subjects[]</td>\n<td>34</td>\n</tr>\n<tr>\n<td> 4.1.12. .spec.rules[].subjects[].group</td>\n<td>34</td>\n</tr>\n</table>\n\n<table>\n<tbody>\n<tr>\n<td>4.1.13. .spec.rules[].subjects[].serviceAccount</td>\n<td>35</td>\n</tr>\n<tr>\n<td>4.1.14. .spec.rules[].subjects[].user</td>\n<td>35</td>\n</tr>\n<tr>\n<td>4.1.15. .status</td>\n<td>36</td>\n</tr>\n<tr>\n<td>4.1.16. .status.conditions</td>\n<td>36</td>\n</tr>\n<tr>\n<td>4.1.17. .status.conditions[]</td>\n<td>36</td>\n</tr>\n<tr>\n<td><b>4.2. API ENDPOINTS</b></td>\n<td><b>37</b></td>\n</tr>\n<tr>\n<td>4.2.1. /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas</td>\n<td>38</td>\n</tr>\n<tr>\n<td>4.2.2. /apis/flowcontrol.apiserver.k8s.io/v1/watch/flowschemas</td>\n<td>39</td>\n</tr>\n<tr>\n<td>4.2.3. /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas/{name}</td>\n<td>40</td>\n</tr>\n<tr>\n<td>4.2.4. /apis/flowcontrol.apiserver.k8s.io/v1/watch/flowschemas/{name}</td>\n<td>43</td>\n</tr>\n<tr>\n<td>4.2.5. /apis/flowcontrol.apiserver.k8s.io/v1/flowschemas/{name}/status</td>\n<td>43</td>\n</tr>\n<tr>\n<td><b>CHAPTER 5. LIMITRANGE [V1]</b></td>\n<td><b>47</b></td>\n</tr>\n<tr>\n<td>5.1. SPECIFICATION</td>\n<td>47</td>\n</tr>\n<tr>\n<td>5.1.1. .spec</td>\n<td>47</td>\n</tr>\n<tr>\n<td>5.1.2. .spec.limits</td>\n<td>48</td>\n</tr>\n<tr>\n<td>5.1.3. .spec.limits[]</td>\n<td>48</td>\n</tr>\n<tr>\n<td>5.2. API ENDPOINTS</td>\n<td>49</td>\n</tr>\n<tr>\n<td>5.2.1. /api/v1/limitranges</td>\n<td>50</td>\n</tr>\n<tr>\n<td>5.2.2. /api/v1/watch/limitranges</td>\n<td>50</td>\n</tr>\n<tr>\n<td>5.2.3. /api/v1/namespaces/{namespace}/limitranges</td>\n<td>50</td>\n</tr>\n<tr>\n<td>5.2.4. /api/v1/watch/namespaces/{namespace}/limitranges</td>\n<td>52</td>\n</tr>\n<tr>\n<td>5.2.5. /api/v1/namespaces/{namespace}/limitranges/{name}</td>\n<td>53</td>\n</tr>\n<tr>\n<td>5.2.6. /api/v1/watch/namespaces/{namespace}/limitranges/{name}</td>\n<td>56</td>\n</tr>\n<tr>\n<td><b>CHAPTER 6. PRIORITYCLASS [SCHEDULING.K8S.IO/V1]</b></td>\n<td><b>57</b></td>\n</tr>\n<tr>\n<td>6.1. SPECIFICATION</td>\n<td>57</td>\n</tr>\n<tr>\n<td>6.2. API ENDPOINTS</td>\n<td>58</td>\n</tr>\n<tr>\n<td>6.2.1. /apis/scheduling.k8s.io/v1/priorityclasses</td>\n<td>59</td>\n</tr>\n<tr>\n<td>6.2.2. /apis/scheduling.k8s.io/v1/watch/priorityclasses</td>\n<td>61</td>\n</tr>\n<tr>\n<td>6.2.3. /apis/scheduling.k8s.io/v1/priorityclasses/{name}</td>\n<td>61</td>\n</tr>\n<tr>\n<td>6.2.4. /apis/scheduling.k8s.io/v1/watch/priorityclasses/{name}</td>\n<td>64</td>\n</tr>\n<tr>\n<td><b>CHAPTER 7. PRIORITYLEVELCONFIGURATION [FLOWCONTROL.APISERVER.K8S.IO/V1]</b></td>\n<td><b>66</b></td>\n</tr>\n<tr>\n<td>7.1. SPECIFICATION</td>\n<td>66</td>\n</tr>\n<tr>\n<td>7.1.1. .spec</td>\n<td>67</td>\n</tr>\n<tr>\n<td>7.1.2. .spec.exempt</td>\n<td>67</td>\n</tr>\n<tr>\n<td>7.1.3. .spec.limited</td>\n<td>68</td>\n</tr>\n<tr>\n<td>7.1.4. .spec.limited.limitResponse</td>\n<td>71</td>\n</tr>\n<tr>\n<td>7.1.5. .spec.limited.limitResponse.queuing</td>\n<td>72</td>\n</tr>\n<tr>\n<td>7.1.6. .status</td>\n<td>73</td>\n</tr>\n<tr>\n<td>7.1.7. .status.conditions</td>\n<td>73</td>\n</tr>\n<tr>\n<td>7.1.8. .status.conditions[]</td>\n<td>73</td>\n</tr>\n<tr>\n<td>7.2. API ENDPOINTS</td>\n<td>74</td>\n</tr>\n<tr>\n<td>7.2.1. /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations</td>\n<td>75</td>\n</tr>\n<tr>\n<td>7.2.2. /apis/flowcontrol.apiserver.k8s.io/v1/watch/prioritylevelconfigurations</td>\n<td>77</td>\n</tr>\n<tr>\n<td>7.2.3. /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations/{name}</td>\n<td>77</td>\n</tr>\n<tr>\n<td>7.2.4. /apis/flowcontrol.apiserver.k8s.io/v1/watch/prioritylevelconfigurations/{name}</td>\n<td>80</td>\n</tr>\n<tr>\n<td>7.2.5. /apis/flowcontrol.apiserver.k8s.io/v1/prioritylevelconfigurations/{name}/status</td>\n<td>81</td>\n</tr>\n<tr>\n<td><b>CHAPTER 8. RESOURCEQUOTA [V1]</b></td>\n<td><b>84</b></td>\n</tr>\n<tr>\n<td>8.1. SPECIFICATION</td>\n<td>84</td>\n</tr>\n<tr>\n<td>8.1.1. .spec</td>\n<td>84</td>\n</tr>\n<tr>\n<td>8.1.2. .spec.scopeSelector</td>\n<td>85</td>\n</tr>\n</tbody>\n</table>\n<hr/><table><tr><td>8.1.3. .spec.scopeSelector.matchExpressions</td><td>85</td></tr><tr><td>8.1.4. .spec.scopeSelector.matchExpressions[]</td><td>86</td></tr><tr><td>8.1.5. .status</td><td>87</td></tr><tr><td>8.2. API ENDPOINTS</td><td>88</td></tr><tr><td>8.2.1. /api/v1/resourcequotas</td><td>89</td></tr><tr><td>8.2.2. /api/v1/watch/resourcequotas</td><td>89</td></tr><tr><td>8.2.3. /api/v1/namespaces/{namespace}/resourcequotas</td><td>89</td></tr><tr><td>8.2.4. /api/v1/watch/namespaces/{namespace}/resourcequotas</td><td>91</td></tr><tr><td>8.2.5. /api/v1/namespaces/{namespace}/resourcequotas/{name}</td><td>92</td></tr><tr><td>8.2.6. /api/v1/watch/namespaces/{namespace}/resourcequotas/{name}</td><td>95</td></tr><tr><td>8.2.7. /api/v1/namespaces/{namespace}/resourcequotas/{name}/status</td><td>95</td></tr></table><h2>CHAPTER 1. SCHEDULE AND QUOTA APIS</h2><h3>1.1. APPLIEDCLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]</h3><h4>Description</h4><p>AppliedClusterResourceQuota mirrors ClusterResourceQuota at a project scope, for projection into a project. It allows a project-admin to know which ClusterResourceQuotas are applied to his project and their associated usage.</p><p>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p><h4>Type</h4><p><b>object</b></p><h3>1.2. CLUSTERRESOURCEQUOTA [QUOTA.OPENSHIFT.IO/V1]</h3><h4>Description</h4><p>ClusterResourceQuota mirrors ResourceQuota at a cluster scope. This object is easily convertible to synthetic ResourceQuota object to allow quota evaluation re-use.</p><p>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p><h4>Type</h4><p><b>object</b></p><h3>1.3. FLOWSCHEMA [FLOWCONTROL.APISERVER.K8S.IO/V1]</h3><h4>Description</h4><p>FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a \"flow distinguisher\".</p><h4>Type</h4><p><b>object</b></p><h3>1.4. LIMITRANGE [V1]</h3><h4>Description</h4><p>LimitRange sets resource usage limits for each kind of resource in a Namespace.</p><h4>Type</h4><p><b>object</b></p><h3>1.5. PRIORITYCLASS [SCHEDULING.K8S.IO/V1]</h3><h4>Description</h4><p>PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.</p><h4>Type</h4><p><b>object</b></p><h2>1.6. PRIORITYLEVELCONFIGURATION<br/>[FLOWCONTROL.APISERVER.K8S.IO/V1]</h2><h3>Description</h3><p>PriorityLevelConfiguration represents the configuration of a priority level.</p><h3>Type</h3><p><b>object</b></p><h2>1.7. RESOURCEQUOTA [V1]</h2><h3>Description</h3><p>ResourceQuota sets aggregate quota restrictions enforced per namespace</p><h3>Type</h3><p><b>object</b></p>\n<h1>CHAPTER 2. APPLIEDCLUSTERRESOURCEQUOTA<br/>[QUOTA.OPENSHIFT.IO/V1]</h1>\n\n<h2>Description</h2>\n\n<p>AppliedClusterResourceQuota mirrors ClusterResourceQuota at a project scope, for projection into a project. It allows a project-admin to know which ClusterResourceQuotas are applied to his project and their associated usage.</p>\n\n<p>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p>\n\n<h2>Type</h2>\n\n<p><b>object</b></p>\n\n<h2>Required</h2>\n\n<ul>\n<li>• <b>metadata</b></li>\n<li>• <b>spec</b></li>\n</ul>\n\n<h2>2.1. SPECIFICATION</h2>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta_v2</b></td>\n<td>metadata is the standard object's metadata. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</a></td>\n</tr>\n<tr>\n<td><b>spec</b></td>\n<td><b>object</b></td>\n<td>ClusterResourceQuotaSpec defines the desired quota restrictions</td>\n</tr>\n<tr>\n<td><b>status</b></td>\n<td><b>object</b></td>\n<td>ClusterResourceQuotaStatus defines the actual enforced quota and its current usage</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.1.1. .spec</h3>\n\n<h4>Description</h4>\n\n<p>ClusterResourceQuotaSpec defines the desired quota restrictions</p>\n\n<h4>Type</h4>\n\n<p><b>object</b></p>\n\n<h4>Required</h4>\n\n<ul>\n<li>• <b>selector</b></li>\n<li>• <b>quota</b></li>\n</ul>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>quota</b></td>\n<td><b>ResourceQuotaSpec_v2</b></td>\n<td>Quota defines the desired quota</td>\n</tr>\n<tr>\n<td><b>selector</b></td>\n<td><b>object</b></td>\n<td>ClusterResourceQuotaSelector is used to select projects. At least one of LabelSelector or AnnotationSelector must present. If only one is present, it is the only selection criteria. If both are specified, the project must match both restrictions.</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.1.2. .spec.selector</h3>\n\n<h4>Description</h4>\n\n<p>ClusterResourceQuotaSelector is used to select projects. At least one of LabelSelector or AnnotationSelector must present. If only one is present, it is the only selection criteria. If both are specified, the project must match both restrictions.</p>\n\n<p>Type</p>\n\n<p><b>object</b></p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>annotations</b></td>\n<td><b>object (string)</b></td>\n<td>AnnotationSelector is used to select projects by annotation.</td>\n</tr>\n<tr>\n<td><b>labels</b></td>\n<td><b>LabelSelector_v4</b></td>\n<td>LabelSelector is used to select projects by label.</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.1.3. .status</h3>\n\n<p>Description</p>\n\n<p>ClusterResourceQuotaStatus defines the actual enforced quota and its current usage</p>\n\n<p>Type</p>\n\n<p><b>object</b></p>\n\n<p>Required</p>\n\n<ul>\n<li>• <b>total</b></li>\n</ul>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>namespaces</b></td>\n<td><b>array</b></td>\n<td>Namespaces slices the usage by project. This division allows for quick resolution of deletion reconciliation inside of a single project without requiring a recalculation across all projects. This can be used to pull the deltas for a given project.</td>\n</tr>\n<tr>\n<td><b>namespaces[]</b></td>\n<td><b>object</b></td>\n<td>ResourceQuotaStatusByNamespace gives status for a particular project</td>\n</tr>\n<tr>\n<td><b>total</b></td>\n<td><b>ResourceQuotaStatus</b></td>\n<td>Total defines the actual enforced quota and its current usage across all projects</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.1.4. .status.namespaces</h3>\n\n<p>Description</p>\n\n<p>Namespaces slices the usage by project. This division allows for quick resolution of deletion reconciliation inside of a single project without requiring a recalculation across all projects. This can be used to pull the deltas for a given project.</p>\n\n<p>Type</p>\n<b>array</b><h3>2.1.5. .status.namespaces[]</h3><b>Description</b>\n<p>ResourceQuotaStatusByNamespace gives status for a particular project</p>\n<b>Type</b><b>object</b><b>Required</b>\n<ul>\n<li>• <b>namespace</b></li>\n<li>• <b>status</b></li>\n</ul>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>namespace</b></td>\n<td><b>string</b></td>\n<td>Namespace the project this status applies to</td>\n</tr>\n<tr>\n<td><b>status</b></td>\n<td><b>ResourceQuotaStatus</b></td>\n<td>Status indicates how many resources have been consumed by this project</td>\n</tr>\n</tbody>\n</table>\n<h2>2.2. API ENDPOINTS</h2>\n<p>The following API endpoints are available:</p>\n\n<ul>\n<li>• <b>/apis/quota.openshift.io/v1/appliedclusterresourcequotas</b>\n<ul>\n<li>◦ <b>GET</b>: list objects of kind AppliedClusterResourceQuota</li>\n</ul>\n</li>\n<li>• <b>/apis/quota.openshift.io/v1/namespaces/{namespace}/appliedclusterresourcequotas</b>\n<ul>\n<li>◦ <b>GET</b>: list objects of kind AppliedClusterResourceQuota</li>\n</ul>\n</li>\n<li>• <b>/apis/quota.openshift.io/v1/namespaces/{namespace}/appliedclusterresourcequotas/{name}</b>\n<ul>\n<li>◦ <b>GET</b>: read the specified AppliedClusterResourceQuota</li>\n</ul>\n</li>\n</ul>\n<h3>2.2.1. /apis/quota.openshift.io/v1/appliedclusterresourcequotas</h3><b>HTTP method</b><b>GET</b><b>Description</b>\n<p>list objects of kind AppliedClusterResourceQuota</p>\n\n<p>Table 2.1. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">AppliedClusterResourceQuotaList</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.2. /apis/quota.openshift.io/v1/namespaces/{namespace}/appliedclusterresourcequota</h3>\n\n<p>HTTP method</p>\n\n<p><b>GET</b></p>\n\n<p>Description</p>\n\n<p>list objects of kind AppliedClusterResourceQuota</p>\n\n<p>Table 2.2. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">AppliedClusterResourceQuotaList</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.3. /apis/quota.openshift.io/v1/namespaces/{namespace}/appliedclusterresourcequota</h3>\n\n<p>Table 2.3. Global path parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the AppliedClusterResourceQuota</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>GET</b></p>\n\n<p>Description</p>\n\n<p>read the specified AppliedClusterResourceQuota</p>\n\n<p>Table 2.4. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">AppliedClusterResourceQuota</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h2>CHAPTER 3. CLUSTERRESOURCEQUOTA<br/>[QUOTA.OPENSHIFT.IO/V1]</h2>\n\n<h3>Description</h3>\n\n<p>ClusterResourceQuota mirrors ResourceQuota at a cluster scope. This object is easily convertible to synthetic ResourceQuota object to allow quota evaluation re-use.</p>\n\n<p>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p>\n\n<h3>Type</h3>\n\n<p><b>object</b></p>\n\n<h3>Required</h3>\n\n<ul>\n<li>• <b>metadata</b></li>\n<li>• <b>spec</b></li>\n</ul>\n\n<h3>3.1. SPECIFICATION</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta</b></td>\n<td>Standard object's metadata. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</a></td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>spec</b></td>\n<td><b>object</b></td>\n<td>spec defines the desired quota</td>\n</tr>\n<tr>\n<td><b>status</b></td>\n<td><b>object</b></td>\n<td>status defines the actual enforced quota and its current usage</td>\n</tr>\n</tbody>\n</table>\n\n<h3>3.1.1. .spec</h3>\n\n<h4>Description</h4>\n\n<p>spec defines the desired quota</p>\n\n<h4>Type</h4>\n\n<p><b>object</b></p>\n\n<h4>Required</h4>\n\n<ul>\n<li>• <b>quota</b></li>\n<li>• <b>selector</b></li>\n</ul>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>quota</b></td>\n<td><b>object</b></td>\n<td>quota defines the desired quota</td>\n</tr>\n<tr>\n<td><b>selector</b></td>\n<td><b>object</b></td>\n<td>selector is the selector used to match projects. It should only select active projects on the scale of dozens (though it can select many more less active projects). These projects will contend on object creation through this resource.</td>\n</tr>\n</tbody>\n</table>\n\n<h3>3.1.2. .spec.quota</h3>\n\n<h4>Description</h4>\n\n<p>quota defines the desired quota</p>\n\n<h4>Type</h4>\n\n<p><b>object</b></p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>hard</b></td>\n<td><b>integer-or-string</b></td>\n<td>hard is the set of desired hard limits for each named resource.<br/>More info:<br/><a href=\"https://kubernetes.io/docs/concepts/policy/resource-quotas/\">https://kubernetes.io/docs/concepts/policy/resource-quotas/</a></td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>scopeSelector</b></td>\n<td><b>object</b></td>\n<td>scopeSelector is also a collection of filters like scopes that must match each object tracked by a quota but expressed using ScopeSelectorOperator in combination with possible values. For a resource to match, both scopes AND scopeSelector (if specified in spec), must be matched.</td>\n</tr>\n<tr>\n<td><b>scopes</b></td>\n<td><b>array (string)</b></td>\n<td>A collection of filters that must match each object tracked by a quota. If not specified, the quota matches all objects.</td>\n</tr>\n</tbody>\n</table>\n\n<h3>3.1.3. .spec.quota.scopeSelector</h3>\n\n<h4>Description</h4>\n\n<p>scopeSelector is also a collection of filters like scopes that must match each object tracked by a quota but expressed using ScopeSelectorOperator in combination with possible values. For a resource to match, both scopes AND scopeSelector (if specified in spec), must be matched.</p>\n\n<h4>Type</h4>\n\n<p><b>object</b></p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>matchExpressions</b></td>\n<td><b>array</b></td>\n<td>A list of scope selector requirements by scope of the resources.</td>\n</tr>\n<tr>\n<td><b>matchExpressions[]</b></td>\n<td><b>object</b></td>\n<td>A scoped-resource selector requirement is a selector that contains values, a scope name, and an operator that relates the scope name and values.</td>\n</tr>\n</tbody>\n</table>\n\n<h3>3.1.4. .spec.quota.scopeSelector.matchExpressions</h3>\n\n<h4>Description</h4>\n\n<p>A list of scope selector requirements by scope of the resources.</p>\n\n<h4>Type</h4>\n\n<p><b>array</b></p>\n\n<h3>3.1.5. .spec.quota.scopeSelector.matchExpressions[]</h3>\n\n<h4>Description</h4>\n\n<p>A scoped-resource selector requirement is a selector that contains values, a scope name, and an operator that relates the scope name and values.</p>\n\n<h4>Type</h4>\n\n<p><b>object</b></p>\n\n<h4>Required</h4>\n\n<ul>\n<li>• <b>operator</b></li>\n<li>• <b>scopeName</b></li>\n</ul>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>operator</b></td>\n<td><b>string</b></td>\n<td>Represents a scope's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist.</td>\n</tr>\n<tr>\n<td><b>scopeName</b></td>\n<td><b>string</b></td>\n<td>The name of the scope that the selector applies to.</td>\n</tr>\n<tr>\n<td><b>values</b></td>\n<td><b>array (string)</b></td>\n<td>An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.</td>\n</tr>\n</tbody>\n</table>\n\n<h3>3.1.6. .spec.selector</h3>\n\n<h4>Description</h4>\n\n<p>selector is the selector used to match projects. It should only select active projects on the scale of dozens (though it can select many more less active projects). These projects will contend on object creation through this resource.</p>\n\n<h4>Type</h4>\n\n<p><b>object</b></p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>annotations</b></td>\n<td><b>undefined (string)</b></td>\n<td>AnnotationSelector is used to select projects by annotation.</td>\n</tr>\n<tr>\n<td><b>labels</b></td>\n<td><b>..</b></td>\n<td>LabelSelector is used to select projects by label.</td>\n</tr>\n</tbody>\n</table>\n\n<h3>3.1.7. .status</h3>\n<b>Description</b>\n<p>status defines the actual enforced quota and its current usage</p>\n<b>Type</b>\n<p><b>object</b></p>\n<b>Required</b>\n<ul>\n<li>• <b>total</b></li>\n</ul>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>namespaces</b></td>\n<td><b>string</b></td>\n<td>namespaces slices the usage by project. This division allows for quick resolution of deletion reconciliation inside of a single project without requiring a recalculation across all projects. This can be used to pull the deltas for a given project.</td>\n</tr>\n<tr>\n<td><b>total</b></td>\n<td><b>object</b></td>\n<td>total defines the actual enforced quota and its current usage across all projects</td>\n</tr>\n</tbody>\n</table>\n<b>3.1.8. .status.total</b><b>Description</b>\n<p>total defines the actual enforced quota and its current usage across all projects</p>\n<b>Type</b>\n<p><b>object</b></p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>hard</b></td>\n<td><b>integer-or-string</b></td>\n<td>Hard is the set of enforced hard limits for each named resource. More info: <a href=\"https://kubernetes.io/docs/concepts/policy/resource-quotas/\">https://kubernetes.io/docs/concepts/policy/resource-quotas/</a></td>\n</tr>\n<tr>\n<td><b>used</b></td>\n<td><b>integer-or-string</b></td>\n<td>Used is the current observed total usage of the resource in the namespace.</td>\n</tr>\n</tbody>\n</table>\n<b>3.2. API ENDPOINTS</b>\n<p>The following API endpoints are available:</p>\n\n<ul>\n<li>• <b>/apis/quota.openshift.io/v1/clustresourcequotas</b></li>\n</ul>\n\n<p>• <b>DELETE /apis/quota.openshift.io/v1/clustresourcequotas</b></p>\n\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>DELETE</b>: delete collection of ClusterResourceQuota</li>\n<li>◦ <b>GET</b>: list objects of kind ClusterResourceQuota</li>\n<li>◦ <b>POST</b>: create a ClusterResourceQuota</li>\n<li>• <b>/apis/quota.openshift.io/v1/watch/clusterresourcequotas</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>GET</b>: watch individual changes to a list of ClusterResourceQuota. deprecated: use the 'watch' parameter with a list operation instead.</li>\n</ul>\n</li>\n<li>• <b>/apis/quota.openshift.io/v1/clusterresourcequotas/{name}</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>DELETE</b>: delete a ClusterResourceQuota</li>\n<li>◦ <b>GET</b>: read the specified ClusterResourceQuota</li>\n<li>◦ <b>PATCH</b>: partially update the specified ClusterResourceQuota</li>\n<li>◦ <b>PUT</b>: replace the specified ClusterResourceQuota</li>\n</ul>\n</li>\n<li>• <b>/apis/quota.openshift.io/v1/watch/clusterresourcequotas/{name}</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>GET</b>: watch changes to an object of kind ClusterResourceQuota. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</li>\n</ul>\n</li>\n<li>• <b>/apis/quota.openshift.io/v1/clusterresourcequotas/{name}/status</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>GET</b>: read status of the specified ClusterResourceQuota</li>\n<li>◦ <b>PATCH</b>: partially update status of the specified ClusterResourceQuota</li>\n<li>◦ <b>PUT</b>: replace status of the specified ClusterResourceQuota</li>\n</ul>\n</li>\n</ul>\n\n<h3>3.2.1. /apis/quota.openshift.io/v1/clusterresourcequotas</h3>\n\n<p>HTTP method</p>\n\n<p><b>DELETE</b></p>\n\n<p>Description</p>\n\n<p>delete collection of ClusterResourceQuota</p>\n\n<p>Table 3.1. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>GET</b></p>\n\n<p>Description</p>\n\n<p>list objects of kind ClusterResourceQuota</p>\n\n<p>Table 3.2. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">ClusterResourceQuotaList</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>POST</b></p>\n\n<p>Description</p>\n\n<p>create a ClusterResourceQuota</p>\n\n<p>Table 3.3. Query parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\n<p>Table 3.4. Body parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterResourceQuota</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\nTable 3.5. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>3.2.2. /apis/quota.openshift.io/v1/watch/clustresourcequotas</h3>\n\n<p>HTTP method</p>\n\n<p><b>GET</b></p>\n\n<p>Description</p>\n\n<p>watch individual changes to a list of ClusterResourceQuota. deprecated: use the 'watch' parameter with a list operation instead.</p>\nTable 3.6. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>WatchEvent</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>3.2.3. /apis/quota.openshift.io/v1/clustresourcequotas/{name}</h3>\nTable 3.7. Global path parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the ClusterResourceQuota</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>DELETE</b></p>\n\n<p>Description</p>\n\n<p>delete a ClusterResourceQuota</p>\nTable 3.8. Query parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\nTable 3.9. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\nHTTP method<b>GET</b>Description\n<p>read the specified ClusterResourceQuota</p>\nTable 3.10. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\nHTTP method<b>PATCH</b>Description\n<p>partially update the specified ClusterResourceQuota</p>\nTable 3.11. Query parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are:\n<ul>\n<li>- Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23.</li>\n<li>- Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+.</li>\n<li>- Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>\nTable 3.12. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\nHTTP method<b>PUT</b>Description<p>replace the specified ClusterResourceQuota</p>Table 3.13. Query parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are:\n<ul>\n<li>- All: all dry run stages will be processed</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are:\n<ul>\n<li>- Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23.</li>\n<li>- Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+.</li>\n<li>- Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>\nTable 3.14. Body parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterResourceQuota</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\nTable 3.15. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>3.2.4. /apis/quota.openshift.io/v1/watch/clusterresourcequotas/{name}</h3>\nTable 3.16. Global path parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the ClusterResourceQuota</td>\n</tr>\n</tbody>\n</table>\n<p>HTTP method</p><b>GET</b><b>Description</b>\n<p>watch changes to an object of kind ClusterResourceQuota. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</p>\n<b>Table 3.17. HTTP responses</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>WatchEvent</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n<b>3.2.5. /apis/quota.openshift.io/v1/clusterresourcequotas/{name}/status</b><b>Table 3.18. Global path parameters</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the ClusterResourceQuota</td>\n</tr>\n</tbody>\n</table>\n<b>HTTP method</b><b>GET</b><b>Description</b>\n<p>read status of the specified ClusterResourceQuota</p>\n<b>Table 3.19. HTTP responses</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n<b>HTTP method</b><b>PATCH</b><b>Description</b>\n<p>partially update status of the specified ClusterResourceQuota</p>\n<b>Table 3.20. Query parameters</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\nTable 3.21. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n<b>HTTP method</b><b>PUT</b><b>Description</b><p>replace status of the specified ClusterResourceQuota</p>Table 3.22. Query parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\nTable 3.23. Body parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>ClusterResourceQuota</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\nTable 3.24. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>ClusterResourceQuota</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h2>CHAPTER 4. FLOWSCHEMA<br/>[FLOWCONTROL.APISERVER.K8S.IO/V1]</h2>\n\n<h3>Description</h3>\n\n<p>FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a \"flow distinguisher\".</p>\n\n<h3>Type</h3>\n\n<p><b>object</b></p>\n\n<h2>4.1. SPECIFICATION</h2>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta</b></td>\n<td><b>metadata</b> is the standard object's metadata. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</a></td>\n</tr>\n<tr>\n<td><b>spec</b></td>\n<td><b>object</b></td>\n<td>FlowSchemaSpec describes how the FlowSchema's specification looks like.</td>\n</tr>\n</tbody>\n</table>"},"page_stats":{"kind":"list like","value":[{"page_number":1,"error":false,"token_count":246,"num_chunks":5},{"page_number":2,"error":false,"token_count":48,"num_chunks":1},{"page_number":3,"error":false,"token_count":88,"num_chunks":2},{"page_number":4,"error":false,"token_count":589,"num_chunks":11},{"page_number":5,"error":false,"token_count":1969,"num_chunks":4},{"page_number":6,"error":false,"token_count":1955,"num_chunks":3},{"page_number":7,"error":false,"token_count":450,"num_chunks":3},{"page_number":8,"error":false,"token_count":83,"num_chunks":2},{"page_number":9,"error":false,"token_count":1343,"num_chunks":29},{"page_number":10,"error":false,"token_count":529,"num_chunks":13},{"page_number":11,"error":false,"token_count":896,"num_chunks":12},{"page_number":12,"error":false,"token_count":1052,"num_chunks":14},{"page_number":13,"error":false,"token_count":1094,"num_chunks":17},{"page_number":14,"error":false,"token_count":1149,"num_chunks":20},{"page_number":15,"error":false,"token_count":1209,"num_chunks":19},{"page_number":16,"error":false,"token_count":967,"num_chunks":12},{"page_number":17,"error":false,"token_count":1147,"num_chunks":17},{"page_number":18,"error":false,"token_count":1066,"num_chunks":16},{"page_number":19,"error":false,"token_count":1066,"num_chunks":15},{"page_number":20,"error":false,"token_count":1155,"num_chunks":19},{"page_number":21,"error":false,"token_count":1133,"num_chunks":13},{"page_number":22,"error":false,"token_count":1002,"num_chunks":13},{"page_number":23,"error":false,"token_count":1231,"num_chunks":19},{"page_number":24,"error":false,"token_count":1137,"num_chunks":18},{"page_number":25,"error":false,"token_count":933,"num_chunks":11},{"page_number":26,"error":false,"token_count":1019,"num_chunks":11},{"page_number":27,"error":false,"token_count":1235,"num_chunks":22},{"page_number":28,"error":false,"token_count":892,"num_chunks":11},{"page_number":29,"error":false,"token_count":831,"num_chunks":7},{"page_number":30,"error":false,"token_count":875,"num_chunks":9}],"string":"[\n {\n \"page_number\": 1,\n \"error\": false,\n \"token_count\": 246,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 2,\n \"error\": false,\n \"token_count\": 48,\n \"num_chunks\": 1\n },\n {\n \"page_number\": 3,\n \"error\": false,\n \"token_count\": 88,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 4,\n \"error\": false,\n \"token_count\": 589,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 5,\n \"error\": false,\n \"token_count\": 1969,\n \"num_chunks\": 4\n },\n {\n \"page_number\": 6,\n \"error\": false,\n \"token_count\": 1955,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 7,\n \"error\": false,\n \"token_count\": 450,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 8,\n \"error\": false,\n \"token_count\": 83,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 9,\n \"error\": false,\n \"token_count\": 1343,\n \"num_chunks\": 29\n },\n {\n \"page_number\": 10,\n \"error\": false,\n \"token_count\": 529,\n \"num_chunks\": 13\n },\n {\n \"page_number\": 11,\n \"error\": false,\n \"token_count\": 896,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 12,\n \"error\": false,\n \"token_count\": 1052,\n \"num_chunks\": 14\n },\n {\n \"page_number\": 13,\n \"error\": false,\n \"token_count\": 1094,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 14,\n \"error\": false,\n \"token_count\": 1149,\n \"num_chunks\": 20\n },\n {\n \"page_number\": 15,\n \"error\": false,\n \"token_count\": 1209,\n \"num_chunks\": 19\n },\n {\n \"page_number\": 16,\n \"error\": false,\n \"token_count\": 967,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 17,\n \"error\": false,\n \"token_count\": 1147,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 18,\n \"error\": false,\n \"token_count\": 1066,\n \"num_chunks\": 16\n },\n {\n \"page_number\": 19,\n \"error\": false,\n \"token_count\": 1066,\n \"num_chunks\": 15\n },\n {\n \"page_number\": 20,\n \"error\": false,\n \"token_count\": 1155,\n \"num_chunks\": 19\n },\n {\n \"page_number\": 21,\n \"error\": false,\n \"token_count\": 1133,\n \"num_chunks\": 13\n },\n {\n \"page_number\": 22,\n \"error\": false,\n \"token_count\": 1002,\n \"num_chunks\": 13\n },\n {\n \"page_number\": 23,\n \"error\": false,\n \"token_count\": 1231,\n \"num_chunks\": 19\n },\n {\n \"page_number\": 24,\n \"error\": false,\n \"token_count\": 1137,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 25,\n \"error\": false,\n \"token_count\": 933,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 26,\n \"error\": false,\n \"token_count\": 1019,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 27,\n \"error\": false,\n \"token_count\": 1235,\n \"num_chunks\": 22\n },\n {\n \"page_number\": 28,\n \"error\": false,\n \"token_count\": 892,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 29,\n \"error\": false,\n \"token_count\": 831,\n \"num_chunks\": 7\n },\n {\n \"page_number\": 30,\n \"error\": false,\n \"token_count\": 875,\n \"num_chunks\": 9\n }\n]","isConversational":false}}},{"rowIdx":94,"cells":{"source_id":{"kind":"string","value":"OpenShift_Container_Platform-4.21-Security_and_compliance-en-US"},"pdf_url":{"kind":"string","value":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/security_and_compliance/OpenShift_Container_Platform-4.21-Security_and_compliance-en-US.pdf"},"status":{"kind":"string","value":"success"},"processed_at":{"kind":"string","value":"2026-04-15T18:36:11.168334+00:00"},"elapsed_seconds":{"kind":"number","value":76.13,"string":"76.13"},"num_pages":{"kind":"number","value":583,"string":"583"},"num_pages_processed":{"kind":"number","value":30,"string":"30"},"max_pages_per_paper":{"kind":"number","value":30,"string":"30"},"pdf_exceeds_page_limit":{"kind":"bool","value":true,"string":"true"},"failed_pages":{"kind":"list like","value":[],"string":"[]","isConversational":false},"prompt_type":{"kind":"string","value":"ocr_layout"},"model_id":{"kind":"string","value":"datalab-to/chandra-ocr-2"},"script_version":{"kind":"timestamp","value":"2026-04-15T00:00:00","string":"2026-04-15T00:00:00"},"markdown":{"kind":"string","value":"# OpenShift Container Platform 4.21\n\n## Security and compliance\n\nLearning about and managing security for OpenShift Container Platform# OpenShift Container Platform 4.21 Security and compliance\n\n---\n\nLearning about and managing security for OpenShift Container Platform## Legal Notice\n\nCopyright © Red Hat.\n\nExcept as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.\n\nRed Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.\n\nRed Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.\n\nLinux ® is the registered trademark of Linus Torvalds in the United States and other countries.\n\nXFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.\n\nThe OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.\n\nAll other trademarks are the property of their respective owners.\n\n## Abstract\n\nThis document discusses container security, configuring certificates, and enabling encryption to help secure the cluster.# Table of Contents\n\n<table>\n<tr>\n<td><b>CHAPTER 1. OPENSHIFT CONTAINER PLATFORM SECURITY AND COMPLIANCE</b> .....</td>\n<td><b>20</b></td>\n</tr>\n<tr>\n<td> 1.1. SECURITY OVERVIEW</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 1.1.1. Container security</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 1.1.2. Auditing</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 1.1.3. Certificates</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 1.1.4. Encrypting data</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.1.5. Vulnerability scanning</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.2. COMPLIANCE OVERVIEW</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.2.1. Compliance checking</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.2.2. File integrity checking</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.3. ADDITIONAL RESOURCES</td>\n<td>21</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. CONTAINER SECURITY</b> .....</td>\n<td><b>23</b></td>\n</tr>\n<tr>\n<td> 2.1. UNDERSTANDING CONTAINER SECURITY</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 2.1.1. What are containers?</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.1.2. What is OpenShift Container Platform?</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.2. UNDERSTANDING HOST AND VM SECURITY</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 2.2.1. Securing containers on Red Hat Enterprise Linux CoreOS (RHCOS)</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 2.2.2. Comparing virtualization and containers</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 2.2.3. Securing OpenShift Container Platform</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 2.3. HARDENING RHCOS</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 2.3.1. Choosing what to harden in RHCOS</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 2.3.2. Choosing how to harden RHCOS</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 2.3.2.1. Hardening before installation</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 2.3.2.2. Hardening during installation</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 2.3.2.3. Hardening after the cluster is running</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 2.4. CONTAINER IMAGE SIGNATURES</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 2.4.1. Enabling signature verification for Red Hat Container Registries</td>\n<td>30</td>\n</tr>\n<tr>\n<td> 2.4.2. Verifying the signature verification configuration</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 2.4.3. Understanding the verification of container images lacking verifiable signatures</td>\n<td>37</td>\n</tr>\n<tr>\n<td> 2.4.3.1. Automated verification during updates</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 2.4.3.2. Using skopeo to verify signatures of Red Hat container images</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 2.4.4. Additional resources</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 2.5. UNDERSTANDING COMPLIANCE</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 2.5.1. Understanding compliance and risk management</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 2.6. SECURING CONTAINER CONTENT</td>\n<td>40</td>\n</tr>\n<tr>\n<td> 2.6.1. Securing inside the container</td>\n<td>40</td>\n</tr>\n<tr>\n<td> 2.6.2. Creating redistributable images with UBI</td>\n<td>40</td>\n</tr>\n<tr>\n<td> 2.6.3. Security scanning in RHEL</td>\n<td>41</td>\n</tr>\n<tr>\n<td> 2.6.3.1. Scanning OpenShift images</td>\n<td>41</td>\n</tr>\n<tr>\n<td> 2.6.4. Integrating external scanning</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 2.6.4.1. Image metadata</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 2.6.4.1.1. Example annotation keys</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 2.6.4.1.2. Example annotation values</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 2.6.4.2. Annotating image objects</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 2.6.4.2.1. Example annotate CLI command</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 2.6.4.3. Controlling pod execution</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 2.6.4.3.1. Example annotation</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 2.6.4.4. Integration reference</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 2.6.4.4.1. Example REST API call</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 2.7. USING CONTAINER REGISTRIES SECURELY</td>\n<td>45</td>\n</tr>\n</table><table>\n<tr>\n<td>2.7.1. Knowing where containers come from?</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.7.2. Immutable and certified containers</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.7.3. Getting containers from Red Hat Registry and Ecosystem Catalog</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.7.4. OpenShift Container Registry</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.7.5. Storing containers using Red Hat Quay</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.8. SECURING THE BUILD PROCESS</td>\n<td>48</td>\n</tr>\n<tr>\n<td>2.8.1. Building once, deploying everywhere</td>\n<td>48</td>\n</tr>\n<tr>\n<td>2.8.2. Managing builds</td>\n<td>49</td>\n</tr>\n<tr>\n<td>2.8.3. Securing inputs during builds</td>\n<td>49</td>\n</tr>\n<tr>\n<td>2.8.4. Designing your build process</td>\n<td>50</td>\n</tr>\n<tr>\n<td>2.8.5. Building Knative serverless applications</td>\n<td>51</td>\n</tr>\n<tr>\n<td>2.8.6. Additional resources</td>\n<td>51</td>\n</tr>\n<tr>\n<td>2.9. DEPLOYING CONTAINERS</td>\n<td>52</td>\n</tr>\n<tr>\n<td>2.9.1. Controlling container deployments with triggers</td>\n<td>52</td>\n</tr>\n<tr>\n<td>2.9.2. Controlling what image sources can be deployed</td>\n<td>53</td>\n</tr>\n<tr>\n<td>2.9.3. Using signature transports</td>\n<td>54</td>\n</tr>\n<tr>\n<td>2.9.4. Creating secrets and config maps</td>\n<td>55</td>\n</tr>\n<tr>\n<td>2.9.5. Automating continuous deployment</td>\n<td>55</td>\n</tr>\n<tr>\n<td>2.10. SECURING THE CONTAINER PLATFORM</td>\n<td>55</td>\n</tr>\n<tr>\n<td>2.10.1. Isolating containers with multitenancy</td>\n<td>56</td>\n</tr>\n<tr>\n<td>2.10.2. Protecting control plane with admission plugins</td>\n<td>56</td>\n</tr>\n<tr>\n<td>2.10.2.1. Security context constraints (SCCs)</td>\n<td>56</td>\n</tr>\n<tr>\n<td>2.10.2.2. Granting roles to service accounts</td>\n<td>57</td>\n</tr>\n<tr>\n<td>2.10.3. Authentication and authorization</td>\n<td>57</td>\n</tr>\n<tr>\n<td>2.10.3.1. Controlling access using OAuth</td>\n<td>57</td>\n</tr>\n<tr>\n<td>2.10.3.2. API access control and management</td>\n<td>57</td>\n</tr>\n<tr>\n<td>2.10.3.3. Red Hat Single Sign-On</td>\n<td>58</td>\n</tr>\n<tr>\n<td>2.10.3.4. Secure self-service web console</td>\n<td>58</td>\n</tr>\n<tr>\n<td>2.10.4. Managing certificates for the platform</td>\n<td>58</td>\n</tr>\n<tr>\n<td>2.10.4.1. Configuring custom certificates</td>\n<td>58</td>\n</tr>\n<tr>\n<td>2.11. SECURING NETWORKS</td>\n<td>59</td>\n</tr>\n<tr>\n<td>2.11.1. Using network namespaces</td>\n<td>59</td>\n</tr>\n<tr>\n<td>2.11.2. Isolating pods with network policies</td>\n<td>59</td>\n</tr>\n<tr>\n<td>2.11.3. Using multiple pod networks</td>\n<td>59</td>\n</tr>\n<tr>\n<td>2.11.4. Isolating applications</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.11.5. Securing ingress traffic</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.11.6. Securing egress traffic</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.12. SECURING ATTACHED STORAGE</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.12.1. Persistent volume plugins</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.12.2. Shared storage</td>\n<td>61</td>\n</tr>\n<tr>\n<td>2.12.3. Block storage</td>\n<td>61</td>\n</tr>\n<tr>\n<td>2.13. MONITORING CLUSTER EVENTS AND LOGS</td>\n<td>62</td>\n</tr>\n<tr>\n<td>2.13.1. Watching cluster events</td>\n<td>62</td>\n</tr>\n<tr>\n<td>2.13.2. Logging</td>\n<td>63</td>\n</tr>\n<tr>\n<td>2.13.3. Audit logs</td>\n<td>63</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. CONFIGURING CERTIFICATES</b></td>\n<td><b>64</b></td>\n</tr>\n<tr>\n<td>3.1. REPLACING THE DEFAULT INGRESS CERTIFICATE</td>\n<td>64</td>\n</tr>\n<tr>\n<td>3.1.1. Understanding the default ingress certificate</td>\n<td>64</td>\n</tr>\n<tr>\n<td>3.1.2. Replacing the default ingress certificate</td>\n<td>64</td>\n</tr>\n<tr>\n<td>3.1.3. Additional resources</td>\n<td>66</td>\n</tr>\n<tr>\n<td>3.2. ADDING API SERVER CERTIFICATES</td>\n<td>66</td>\n</tr>\n<tr>\n<td>3.2.1. Add an API server named certificate</td>\n<td>66</td>\n</tr>\n</table>---\n\n<table>\n<tr>\n<td>3.3. SECURING SERVICE TRAFFIC USING SERVICE SERVING CERTIFICATE SECRETS</td>\n<td>68</td>\n</tr>\n<tr>\n<td> 3.3.1. Understanding service serving certificates</td>\n<td>68</td>\n</tr>\n<tr>\n<td> 3.3.2. Add a service certificate</td>\n<td>69</td>\n</tr>\n<tr>\n<td> 3.3.3. Add the service CA bundle to a config map</td>\n<td>70</td>\n</tr>\n<tr>\n<td> 3.3.4. Add the service CA bundle to an API service</td>\n<td>72</td>\n</tr>\n<tr>\n<td> 3.3.5. Add the service CA bundle to a custom resource definition</td>\n<td>73</td>\n</tr>\n<tr>\n<td> 3.3.6. Add the service CA bundle to a mutating webhook configuration</td>\n<td>74</td>\n</tr>\n<tr>\n<td> 3.3.7. Add the service CA bundle to a validating webhook configuration</td>\n<td>74</td>\n</tr>\n<tr>\n<td> 3.3.8. Manually rotate the generated service certificate</td>\n<td>75</td>\n</tr>\n<tr>\n<td> 3.3.9. Manually rotate the service CA certificate</td>\n<td>76</td>\n</tr>\n<tr>\n<td>3.4. UPDATING THE CA BUNDLE</td>\n<td>77</td>\n</tr>\n<tr>\n<td> 3.4.1. Understanding the CA Bundle certificate</td>\n<td>77</td>\n</tr>\n<tr>\n<td> 3.4.2. Replacing the CA Bundle certificate</td>\n<td>78</td>\n</tr>\n<tr>\n<td> 3.4.3. Additional resources</td>\n<td>78</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. CERTIFICATE TYPES AND DESCRIPTIONS</b> .....</td>\n<td><b>80</b></td>\n</tr>\n<tr>\n<td>4.1. USER-PROVIDED CERTIFICATES FOR THE API SERVER</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.1.1. Purpose</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.1.2. Location</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.1.3. Management</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.1.4. Expiration</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.1.5. Customization</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.1.6. Additional resources</td>\n<td>80</td>\n</tr>\n<tr>\n<td>4.2. PROXY CERTIFICATES</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.2.1. Purpose</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.2.1.1. Additional resources</td>\n<td>81</td>\n</tr>\n<tr>\n<td> 4.2.2. Managing proxy certificates during installation</td>\n<td>81</td>\n</tr>\n<tr>\n<td> 4.2.3. Location</td>\n<td>81</td>\n</tr>\n<tr>\n<td> 4.2.4. Expiration</td>\n<td>82</td>\n</tr>\n<tr>\n<td> 4.2.5. Services</td>\n<td>82</td>\n</tr>\n<tr>\n<td> 4.2.6. Management</td>\n<td>82</td>\n</tr>\n<tr>\n<td> 4.2.7. Customization</td>\n<td>82</td>\n</tr>\n<tr>\n<td> 4.2.8. Renewal</td>\n<td>83</td>\n</tr>\n<tr>\n<td>4.3. SERVICE CA CERTIFICATES</td>\n<td>83</td>\n</tr>\n<tr>\n<td> 4.3.1. Purpose</td>\n<td>83</td>\n</tr>\n<tr>\n<td> 4.3.2. Expiration</td>\n<td>83</td>\n</tr>\n<tr>\n<td> 4.3.3. Management</td>\n<td>84</td>\n</tr>\n<tr>\n<td> 4.3.4. Services</td>\n<td>84</td>\n</tr>\n<tr>\n<td> 4.3.5. Additional resources</td>\n<td>85</td>\n</tr>\n<tr>\n<td>4.4. NODE CERTIFICATES</td>\n<td>85</td>\n</tr>\n<tr>\n<td> 4.4.1. Purpose</td>\n<td>85</td>\n</tr>\n<tr>\n<td> 4.4.2. Location</td>\n<td>85</td>\n</tr>\n<tr>\n<td> 4.4.3. Management</td>\n<td>85</td>\n</tr>\n<tr>\n<td> 4.4.4. Expiration</td>\n<td>85</td>\n</tr>\n<tr>\n<td> 4.4.5. Renewal</td>\n<td>85</td>\n</tr>\n<tr>\n<td> 4.4.6. Additional resources</td>\n<td>86</td>\n</tr>\n<tr>\n<td>4.5. BOOTSTRAP CERTIFICATES</td>\n<td>86</td>\n</tr>\n<tr>\n<td> 4.5.1. Purpose</td>\n<td>86</td>\n</tr>\n<tr>\n<td> 4.5.2. Management</td>\n<td>86</td>\n</tr>\n<tr>\n<td> 4.5.3. Expiration</td>\n<td>86</td>\n</tr>\n<tr>\n<td> 4.5.4. Customization</td>\n<td>86</td>\n</tr>\n<tr>\n<td>4.6. ETCD CERTIFICATES</td>\n<td>86</td>\n</tr>\n<tr>\n<td> 4.6.1. Purpose</td>\n<td>86</td>\n</tr>\n</table><table>\n<tr><td>4.6.2. Expiration</td><td>87</td></tr>\n<tr><td>4.6.3. Rotating the etcd certificate</td><td>87</td></tr>\n<tr><td>4.6.4. Removing an unused certificate authority from the bundle</td><td>87</td></tr>\n<tr><td>4.6.5. etcd certificate rotation alerts and metrics signer certificates</td><td>87</td></tr>\n<tr><td>4.6.6. Management</td><td>88</td></tr>\n<tr><td>4.6.7. Services</td><td>88</td></tr>\n<tr><td>4.6.8. Additional resources</td><td>88</td></tr>\n<tr><td>4.7. OLM CERTIFICATES</td><td>88</td></tr>\n<tr><td>4.7.1. Management</td><td>88</td></tr>\n<tr><td>4.7.2. Additional resources</td><td>89</td></tr>\n<tr><td>4.8. AGGREGATED API CLIENT CERTIFICATES</td><td>89</td></tr>\n<tr><td>4.8.1. Purpose</td><td>89</td></tr>\n<tr><td>4.8.2. Management</td><td>89</td></tr>\n<tr><td>4.8.3. Expiration</td><td>89</td></tr>\n<tr><td>4.8.4. Customization</td><td>89</td></tr>\n<tr><td>4.9. MACHINE CONFIG OPERATOR CERTIFICATES</td><td>89</td></tr>\n<tr><td>4.9.1. Purpose</td><td>89</td></tr>\n<tr><td>4.9.1.1. Provisioning details</td><td>90</td></tr>\n<tr><td>4.9.1.2. Provisioning chain of trust</td><td>90</td></tr>\n<tr><td>4.9.1.3. Key material inside a cluster</td><td>90</td></tr>\n<tr><td>4.9.2. Management</td><td>91</td></tr>\n<tr><td>4.9.3. Expiration</td><td>91</td></tr>\n<tr><td>4.9.4. Customization</td><td>91</td></tr>\n<tr><td>4.10. USER-PROVIDED CERTIFICATES FOR DEFAULT INGRESS</td><td>91</td></tr>\n<tr><td>4.10.1. Purpose</td><td>91</td></tr>\n<tr><td>4.10.2. Location</td><td>92</td></tr>\n<tr><td>4.10.3. Management</td><td>92</td></tr>\n<tr><td>4.10.4. Expiration</td><td>92</td></tr>\n<tr><td>4.10.5. Services</td><td>92</td></tr>\n<tr><td>4.10.6. Customization</td><td>92</td></tr>\n<tr><td>4.10.7. Additional resources</td><td>92</td></tr>\n<tr><td>4.11. INGRESS CERTIFICATES</td><td>92</td></tr>\n<tr><td>4.11.1. Purpose</td><td>92</td></tr>\n<tr><td>4.11.2. Location</td><td>92</td></tr>\n<tr><td>4.11.3. Workflow</td><td>93</td></tr>\n<tr><td>4.11.4. Expiration</td><td>94</td></tr>\n<tr><td>4.11.5. Services</td><td>95</td></tr>\n<tr><td>4.11.6. Management</td><td>95</td></tr>\n<tr><td>4.11.7. Renewal</td><td>95</td></tr>\n<tr><td>4.12. MONITORING AND OPENSHIFT LOGGING OPERATOR COMPONENT CERTIFICATES</td><td>95</td></tr>\n<tr><td>4.12.1. Expiration</td><td>95</td></tr>\n<tr><td>4.12.2. Management</td><td>95</td></tr>\n<tr><td>4.13. CONTROL PLANE CERTIFICATES</td><td>95</td></tr>\n<tr><td>4.13.1. Location</td><td>95</td></tr>\n<tr><td>4.13.2. Management</td><td>96</td></tr>\n<tr><td><b>CHAPTER 5. COMPLIANCE OPERATOR</b> .....</td><td><b>97</b></td></tr>\n<tr><td>5.1. COMPLIANCE OPERATOR OVERVIEW</td><td>97</td></tr>\n<tr><td>5.1.1. Compliance Operator concepts</td><td>97</td></tr>\n<tr><td>5.1.2. Compliance Operator management</td><td>97</td></tr>\n<tr><td>5.1.3. Compliance Operator scan management</td><td>97</td></tr>\n<tr><td>5.2. COMPLIANCE OPERATOR RELEASE NOTES</td><td>97</td></tr>\n<tr><td>5.2.1. OpenShift Compliance Operator 1.8.2</td><td>98</td></tr>\n</table>---\n\n<table><tr><td>5.2.1.1. Bug Fixes</td><td>98</td></tr><tr><td>5.2.2. OpenShift Compliance Operator 1.8.1</td><td>98</td></tr><tr><td>5.2.2.1. Bug Fixes</td><td>98</td></tr><tr><td>5.2.3. OpenShift Compliance Operator 1.8.0</td><td>98</td></tr><tr><td>5.2.3.1. New features and enhancements</td><td>98</td></tr><tr><td>5.2.3.2. Bug fixes</td><td>99</td></tr><tr><td>5.2.4. OpenShift Compliance Operator 1.7.1</td><td>101</td></tr><tr><td>5.2.4.1. Bug fixes</td><td>101</td></tr><tr><td>5.2.5. OpenShift Compliance Operator 1.7.0</td><td>101</td></tr><tr><td>5.2.5.1. New features and enhancements</td><td>101</td></tr><tr><td>5.2.5.2. Bug fixes</td><td>102</td></tr><tr><td>5.2.6. OpenShift Compliance Operator 1.6.2</td><td>102</td></tr><tr><td>5.2.7. OpenShift Compliance Operator 1.6.1</td><td>103</td></tr><tr><td>5.2.8. OpenShift Compliance Operator 1.6.0</td><td>103</td></tr><tr><td>5.2.8.1. New features and enhancements</td><td>103</td></tr><tr><td>5.2.8.2. Bug fixes</td><td>103</td></tr><tr><td>5.2.9. OpenShift Compliance Operator 1.5.1</td><td>104</td></tr><tr><td>5.2.10. OpenShift Compliance Operator 1.5.0</td><td>104</td></tr><tr><td>5.2.10.1. New features and enhancements</td><td>104</td></tr><tr><td>5.2.10.2. Bug fixes</td><td>104</td></tr><tr><td>5.2.11. OpenShift Compliance Operator 1.4.1</td><td>104</td></tr><tr><td>5.2.11.1. New features and enhancements</td><td>105</td></tr><tr><td>5.2.11.2. Bug fixes</td><td>105</td></tr><tr><td>5.2.12. OpenShift Compliance Operator 1.4.0</td><td>106</td></tr><tr><td>5.2.12.1. New features and enhancements</td><td>106</td></tr><tr><td>5.2.12.2. Bug fixes</td><td>106</td></tr><tr><td>5.2.13. OpenShift Compliance Operator 1.3.1</td><td>106</td></tr><tr><td>5.2.13.1. New features and enhancements</td><td>107</td></tr><tr><td>5.2.13.2. Known issue</td><td>107</td></tr><tr><td>5.2.14. OpenShift Compliance Operator 1.3.0</td><td>107</td></tr><tr><td>5.2.14.1. New features and enhancements</td><td>107</td></tr><tr><td>5.2.15. OpenShift Compliance Operator 1.2.0</td><td>107</td></tr><tr><td>5.2.15.1. New features and enhancements</td><td>107</td></tr><tr><td>5.2.16. OpenShift Compliance Operator 1.1.0</td><td>108</td></tr><tr><td>5.2.16.1. New features and enhancements</td><td>108</td></tr><tr><td>5.2.16.2. Bug fixes</td><td>108</td></tr><tr><td>5.2.17. OpenShift Compliance Operator 1.0.0</td><td>109</td></tr><tr><td>5.2.17.1. New features and enhancements</td><td>109</td></tr><tr><td>5.2.17.2. Bug fixes</td><td>109</td></tr><tr><td>5.2.18. OpenShift Compliance Operator 0.1.61</td><td>110</td></tr><tr><td>5.2.18.1. New features and enhancements</td><td>110</td></tr><tr><td>5.2.18.2. Bug fixes</td><td>110</td></tr><tr><td>5.2.19. OpenShift Compliance Operator 0.1.59</td><td>111</td></tr><tr><td>5.2.19.1. New features and enhancements</td><td>111</td></tr><tr><td>5.2.19.2. Bug fixes</td><td>111</td></tr><tr><td>5.2.20. OpenShift Compliance Operator 0.1.57</td><td>111</td></tr><tr><td>5.2.20.1. New features and enhancements</td><td>111</td></tr><tr><td>5.2.20.2. Bug fixes</td><td>112</td></tr><tr><td>5.2.20.3. Deprecations</td><td>112</td></tr><tr><td>5.2.21. OpenShift Compliance Operator 0.1.53</td><td>113</td></tr><tr><td>5.2.21.1. Bug fixes</td><td>113</td></tr><tr><td>5.2.21.2. Known issue</td><td>114</td></tr><tr><td>5.2.22. OpenShift Compliance Operator 0.1.52</td><td>114</td></tr></table>\n\n---<table><tr><td>5.2.22.1. New features and enhancements</td><td>114</td></tr><tr><td>5.2.22.2. Bug fixes</td><td>114</td></tr><tr><td>5.2.22.3. Known issue</td><td>114</td></tr><tr><td>5.2.23. OpenShift Compliance Operator 0.1.49</td><td>115</td></tr><tr><td>5.2.23.1. New features and enhancements</td><td>115</td></tr><tr><td>5.2.23.2. Bug fixes</td><td>115</td></tr><tr><td>5.2.24. OpenShift Compliance Operator 0.1.48</td><td>116</td></tr><tr><td>5.2.24.1. Bug fixes</td><td>116</td></tr><tr><td>5.2.25. OpenShift Compliance Operator 0.1.47</td><td>116</td></tr><tr><td>5.2.25.1. New features and enhancements</td><td>116</td></tr><tr><td>5.2.25.2. Bug fixes</td><td>116</td></tr><tr><td>5.2.26. OpenShift Compliance Operator 0.1.44</td><td>117</td></tr><tr><td>5.2.26.1. New features and enhancements</td><td>117</td></tr><tr><td>5.2.26.2. Templating and variable use</td><td>118</td></tr><tr><td>5.2.26.3. Bug fixes</td><td>118</td></tr><tr><td>5.2.27. Release Notes for Compliance Operator 0.1.39</td><td>119</td></tr><tr><td>5.2.27.1. New features and enhancements</td><td>119</td></tr><tr><td>5.2.28. Additional resources</td><td>119</td></tr><tr><td>5.3. COMPLIANCE OPERATOR SUPPORT</td><td>119</td></tr><tr><td>5.3.1. Compliance Operator lifecycle</td><td>119</td></tr><tr><td>5.3.2. Getting support</td><td>119</td></tr><tr><td>5.3.3. Using the must-gather tool for the Compliance Operator</td><td>119</td></tr><tr><td>5.3.4. Additional resources</td><td>120</td></tr><tr><td>5.4. COMPLIANCE OPERATOR CONCEPTS</td><td>120</td></tr><tr><td>5.4.1. Understanding the Compliance Operator</td><td>120</td></tr><tr><td>5.4.1.1. Compliance Operator profiles</td><td>120</td></tr><tr><td>5.4.1.1.1. Compliance Operator profile types</td><td>124</td></tr><tr><td>5.4.2. Understanding the Custom Resource Definitions</td><td>125</td></tr><tr><td>5.4.2.1. CRDs workflow</td><td>125</td></tr><tr><td>5.4.2.2. Defining the compliance scan requirements</td><td>125</td></tr><tr><td>5.4.2.2.1. ProfileBundle object</td><td>125</td></tr><tr><td>5.4.2.2.2. Profile object</td><td>126</td></tr><tr><td>5.4.2.2.3. Rule object</td><td>127</td></tr><tr><td>5.4.2.2.4. TailoredProfile object</td><td>127</td></tr><tr><td>5.4.2.3. Configuring the compliance scan settings</td><td>129</td></tr><tr><td>5.4.2.3.1. ScanSetting object</td><td>129</td></tr><tr><td>5.4.2.4. Processing the compliance scan requirements with compliance scans settings</td><td>130</td></tr><tr><td>5.4.2.4.1. ScanSettingBinding object</td><td>130</td></tr><tr><td>5.4.2.5. Tracking the compliance scans</td><td>131</td></tr><tr><td>5.4.2.5.1. ComplianceSuite object</td><td>131</td></tr><tr><td>5.4.2.5.2. Advanced ComplianceScan Object</td><td>132</td></tr><tr><td>5.4.2.6. Viewing the compliance results</td><td>134</td></tr><tr><td>5.4.2.6.1. ComplianceCheckResult object</td><td>134</td></tr><tr><td>5.4.2.6.2. ComplianceRemediation object</td><td>135</td></tr><tr><td>5.5. COMPLIANCE OPERATOR MANAGEMENT</td><td>136</td></tr><tr><td>5.5.1. Installing the Compliance Operator</td><td>136</td></tr><tr><td>5.5.1.1. Installing the Compliance Operator through the web console</td><td>136</td></tr><tr><td>5.5.1.2. Installing the Compliance Operator using the CLI</td><td>137</td></tr><tr><td>5.5.1.3. Installing the Compliance Operator on ROSA hosted control planes (HCP)</td><td>139</td></tr><tr><td>5.5.1.4. Installing the Compliance Operator on Hypershift hosted control planes</td><td>141</td></tr><tr><td>5.5.1.5. Additional resources</td><td>142</td></tr><tr><td>5.5.2. Updating the Compliance Operator</td><td>143</td></tr><tr><td>5.5.2.1. Preparing for an Operator update</td><td>143</td></tr></table>---\n\n<table>\n<tr>\n<td>5.5.2.2. Changing the update channel for an Operator</td>\n<td>143</td>\n</tr>\n<tr>\n<td>5.5.2.3. Manually approving a pending Operator update</td>\n<td>144</td>\n</tr>\n<tr>\n<td>5.5.3. Managing the Compliance Operator</td>\n<td>144</td>\n</tr>\n<tr>\n<td>5.5.3.1. ProfileBundle CR example</td>\n<td>144</td>\n</tr>\n<tr>\n<td>5.5.3.2. Updating security content</td>\n<td>145</td>\n</tr>\n<tr>\n<td>5.5.3.3. Additional resources</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.5.4. Uninstalling the Compliance Operator</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.5.4.1. Uninstalling the OpenShift Compliance Operator from OpenShift Container Platform using the web console</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.5.4.2. Uninstalling the OpenShift Compliance Operator from OpenShift Container Platform using the CLI</td>\n<td>147</td>\n</tr>\n<tr>\n<td>5.6. COMPLIANCE OPERATOR SCAN MANAGEMENT</td>\n<td>148</td>\n</tr>\n<tr>\n<td>5.6.1. Supported compliance profiles</td>\n<td>148</td>\n</tr>\n<tr>\n<td>5.6.1.1. Compliance profiles</td>\n<td>149</td>\n</tr>\n<tr>\n<td>5.6.1.1.1. CIS compliance profiles</td>\n<td>149</td>\n</tr>\n<tr>\n<td>5.6.1.1.2. BSI Profile Support</td>\n<td>150</td>\n</tr>\n<tr>\n<td>5.6.1.1.3. Essential Eight compliance profiles</td>\n<td>151</td>\n</tr>\n<tr>\n<td>5.6.1.1.4. FedRAMP High compliance profiles</td>\n<td>152</td>\n</tr>\n<tr>\n<td>5.6.1.1.5. FedRAMP Moderate compliance profiles</td>\n<td>153</td>\n</tr>\n<tr>\n<td>5.6.1.1.6. NERC-CIP compliance profiles</td>\n<td>155</td>\n</tr>\n<tr>\n<td>5.6.1.1.7. PCI-DSS compliance profiles</td>\n<td>156</td>\n</tr>\n<tr>\n<td>5.6.1.1.8. STIG compliance profiles</td>\n<td>158</td>\n</tr>\n<tr>\n<td>5.6.1.1.9. About extended compliance profiles</td>\n<td>159</td>\n</tr>\n<tr>\n<td>5.6.1.1.10. Compliance Operator profile types</td>\n<td>160</td>\n</tr>\n<tr>\n<td>5.6.2. Compliance Operator scans</td>\n<td>161</td>\n</tr>\n<tr>\n<td>5.6.2.1. Running compliance scans</td>\n<td>161</td>\n</tr>\n<tr>\n<td>5.6.2.2. Setting custom storage size for results</td>\n<td>165</td>\n</tr>\n<tr>\n<td>5.6.2.2.1. Using custom result storage values</td>\n<td>165</td>\n</tr>\n<tr>\n<td>5.6.2.3. Scheduling the result server pod on a worker node</td>\n<td>166</td>\n</tr>\n<tr>\n<td>5.6.2.4. ScanSetting Custom Resource</td>\n<td>167</td>\n</tr>\n<tr>\n<td>5.6.2.5. Configuring the hosted control planes management cluster</td>\n<td>167</td>\n</tr>\n<tr>\n<td>5.6.2.6. Applying resource requests and limits</td>\n<td>169</td>\n</tr>\n<tr>\n<td>5.6.2.7. Scheduling Pods with container resource requests</td>\n<td>169</td>\n</tr>\n<tr>\n<td>5.6.3. Tailoring the Compliance Operator</td>\n<td>171</td>\n</tr>\n<tr>\n<td>5.6.3.1. Creating a new tailored profile</td>\n<td>171</td>\n</tr>\n<tr>\n<td>5.6.3.2. Using tailored profiles to extend existing ProfileBundles</td>\n<td>172</td>\n</tr>\n<tr>\n<td>5.6.4. Retrieving Compliance Operator raw results</td>\n<td>174</td>\n</tr>\n<tr>\n<td>5.6.4.1. Obtaining Compliance Operator raw results from a persistent volume</td>\n<td>174</td>\n</tr>\n<tr>\n<td>5.6.5. Managing Compliance Operator result and remediation</td>\n<td>176</td>\n</tr>\n<tr>\n<td>5.6.5.1. Filters for compliance check results</td>\n<td>176</td>\n</tr>\n<tr>\n<td>5.6.5.2. Reviewing a remediation</td>\n<td>178</td>\n</tr>\n<tr>\n<td>5.6.5.3. Applying remediation when using customized machine config pools</td>\n<td>179</td>\n</tr>\n<tr>\n<td>5.6.5.4. Evaluating KubeletConfig rules against default configuration values</td>\n<td>180</td>\n</tr>\n<tr>\n<td>5.6.5.5. Scanning custom node pools</td>\n<td>181</td>\n</tr>\n<tr>\n<td>5.6.5.6. Remediating KubeletConfig sub pools</td>\n<td>182</td>\n</tr>\n<tr>\n<td>5.6.5.7. Applying a remediation</td>\n<td>182</td>\n</tr>\n<tr>\n<td>5.6.5.8. Remediating a platform check manually</td>\n<td>183</td>\n</tr>\n<tr>\n<td>5.6.5.9. Updating remediations</td>\n<td>184</td>\n</tr>\n<tr>\n<td>5.6.5.10. Unapplying a remediation</td>\n<td>185</td>\n</tr>\n<tr>\n<td>5.6.5.11. Removing a KubeletConfig remediation</td>\n<td>185</td>\n</tr>\n<tr>\n<td>5.6.5.12. Inconsistent ComplianceScan</td>\n<td>187</td>\n</tr>\n<tr>\n<td>5.6.5.13. Additional resources</td>\n<td>188</td>\n</tr>\n<tr>\n<td>5.6.6. Performing advanced Compliance Operator tasks</td>\n<td>188</td>\n</tr>\n</table><table>\n<tr><td>5.6.6.1. Using the ComplianceSuite and ComplianceScan objects directly</td><td>188</td></tr>\n<tr><td>5.6.6.2. Setting PriorityClass for ScanSetting scans</td><td>189</td></tr>\n<tr><td>5.6.6.3. Using raw tailored profiles</td><td>190</td></tr>\n<tr><td>5.6.6.4. Performing a rescan</td><td>191</td></tr>\n<tr><td>5.6.6.5. Setting custom storage size for results</td><td>191</td></tr>\n<tr><td> 5.6.6.5.1. Using custom result storage values</td><td>192</td></tr>\n<tr><td>5.6.6.6. Applying remediations generated by suite scans</td><td>192</td></tr>\n<tr><td>5.6.6.7. Automatically update remediations</td><td>192</td></tr>\n<tr><td>5.6.6.8. Creating a custom SCC for the Compliance Operator</td><td>193</td></tr>\n<tr><td>5.6.6.9. Additional resources</td><td>194</td></tr>\n<tr><td>5.6.7. Troubleshooting Compliance Operator scans</td><td>194</td></tr>\n<tr><td> 5.6.7.1. Anatomy of a scan</td><td>195</td></tr>\n<tr><td> 5.6.7.1.1. Compliance sources</td><td>195</td></tr>\n<tr><td> 5.6.7.1.2. The ScanSetting and ScanSettingBinding objects lifecycle and debugging</td><td>196</td></tr>\n<tr><td> 5.6.7.1.3. ComplianceSuite custom resource lifecycle and debugging</td><td>196</td></tr>\n<tr><td> 5.6.7.1.4. ComplianceScan custom resource lifecycle and debugging</td><td>197</td></tr>\n<tr><td> 5.6.7.1.4.1. Pending phase</td><td>197</td></tr>\n<tr><td> 5.6.7.1.4.2. Launching phase</td><td>197</td></tr>\n<tr><td> 5.6.7.1.4.3. Running phase</td><td>198</td></tr>\n<tr><td> 5.6.7.1.4.4. Aggregating phase</td><td>199</td></tr>\n<tr><td> 5.6.7.1.4.5. Done phase</td><td>199</td></tr>\n<tr><td> 5.6.7.1.5. ComplianceRemediation controller lifecycle and debugging</td><td>200</td></tr>\n<tr><td> 5.6.7.1.6. Useful labels</td><td>201</td></tr>\n<tr><td> 5.6.7.2. Increasing Compliance Operator resource limits</td><td>201</td></tr>\n<tr><td> 5.6.7.3. Configuring Operator resource constraints</td><td>202</td></tr>\n<tr><td> 5.6.7.4. Configuring ScanSetting resources</td><td>202</td></tr>\n<tr><td> 5.6.7.5. Configuring ScanSetting timeout</td><td>204</td></tr>\n<tr><td> 5.6.7.6. Getting support</td><td>204</td></tr>\n<tr><td>5.6.8. Using the oc-compliance plugin</td><td>205</td></tr>\n<tr><td> 5.6.8.1. Installing the oc-compliance plugin</td><td>205</td></tr>\n<tr><td> 5.6.8.2. Fetching raw results</td><td>205</td></tr>\n<tr><td> 5.6.8.3. Re-running scans</td><td>206</td></tr>\n<tr><td> 5.6.8.4. Using ScanSettingBinding custom resources</td><td>207</td></tr>\n<tr><td> 5.6.8.5. Printing controls</td><td>208</td></tr>\n<tr><td> 5.6.8.6. Fetching compliance remediation details</td><td>209</td></tr>\n<tr><td> 5.6.8.7. Viewing ComplianceCheckResult object details</td><td>211</td></tr>\n<tr><td><b>CHAPTER 6. FILE INTEGRITY OPERATOR</b></td><td><b>212</b></td></tr>\n<tr><td>6.1. FILE INTEGRITY OPERATOR OVERVIEW</td><td>212</td></tr>\n<tr><td>6.2. FILE INTEGRITY OPERATOR RELEASE NOTES</td><td>212</td></tr>\n<tr><td> 6.2.1. OpenShift File Integrity Operator 1.3.8</td><td>212</td></tr>\n<tr><td> 6.2.1.1. Bug fixes</td><td>212</td></tr>\n<tr><td> 6.2.2. OpenShift File Integrity Operator 1.3.7</td><td>213</td></tr>\n<tr><td> 6.2.3. OpenShift File Integrity Operator 1.3.6</td><td>213</td></tr>\n<tr><td> 6.2.3.1. Bug fixes</td><td>213</td></tr>\n<tr><td> 6.2.4. OpenShift File Integrity Operator 1.3.5</td><td>213</td></tr>\n<tr><td> 6.2.5. OpenShift File Integrity Operator 1.3.4</td><td>213</td></tr>\n<tr><td> 6.2.5.1. Bug fixes</td><td>214</td></tr>\n<tr><td> 6.2.6. OpenShift File Integrity Operator 1.3.3</td><td>214</td></tr>\n<tr><td> 6.2.6.1. New features and enhancements</td><td>214</td></tr>\n<tr><td> 6.2.6.2. Bug fixes</td><td>214</td></tr>\n<tr><td> 6.2.7. OpenShift File Integrity Operator 1.3.2</td><td>214</td></tr>\n<tr><td> 6.2.8. OpenShift File Integrity Operator 1.3.1</td><td>214</td></tr>\n</table>---\n\n<table><tr><td>6.2.8.1. New features and enhancements</td><td>215</td></tr><tr><td>6.2.8.2. Bug fixes</td><td>215</td></tr><tr><td>6.2.8.3. Known Issues</td><td>215</td></tr><tr><td>6.2.9. OpenShift File Integrity Operator 1.2.1</td><td>215</td></tr><tr><td>6.2.10. OpenShift File Integrity Operator 1.2.0</td><td>215</td></tr><tr><td>6.2.10.1. New features and enhancements</td><td>215</td></tr><tr><td>6.2.11. OpenShift File Integrity Operator 1.0.0</td><td>216</td></tr><tr><td>6.2.12. OpenShift File Integrity Operator 0.1.32</td><td>216</td></tr><tr><td>6.2.12.1. Bug fixes</td><td>216</td></tr><tr><td>6.2.13. OpenShift File Integrity Operator 0.1.30</td><td>216</td></tr><tr><td>6.2.13.1. New features and enhancements</td><td>216</td></tr><tr><td>6.2.13.2. Bug fixes</td><td>216</td></tr><tr><td>6.2.14. OpenShift File Integrity Operator 0.1.24</td><td>216</td></tr><tr><td>6.2.14.1. New features and enhancements</td><td>216</td></tr><tr><td>6.2.14.2. Bug fixes</td><td>217</td></tr><tr><td>6.2.15. OpenShift File Integrity Operator 0.1.22</td><td>217</td></tr><tr><td>6.2.15.1. Bug fixes</td><td>217</td></tr><tr><td>6.2.16. OpenShift File Integrity Operator 0.1.21</td><td>217</td></tr><tr><td>6.2.16.1. New features and enhancements</td><td>217</td></tr><tr><td>6.2.16.2. Bug fixes</td><td>218</td></tr><tr><td>6.2.17. Additional resources</td><td>218</td></tr><tr><td>6.3. FILE INTEGRITY OPERATOR SUPPORT</td><td>218</td></tr><tr><td>6.3.1. File Integrity Operator lifecycle</td><td>218</td></tr><tr><td>6.3.2. Getting support</td><td>218</td></tr><tr><td>6.4. INSTALLING THE FILE INTEGRITY OPERATOR</td><td>218</td></tr><tr><td>6.4.1. Installing the File Integrity Operator using the web console</td><td>218</td></tr><tr><td>6.4.2. Installing the File Integrity Operator using the CLI</td><td>219</td></tr><tr><td>6.4.3. Additional resources</td><td>220</td></tr><tr><td>6.5. UPDATING THE FILE INTEGRITY OPERATOR</td><td>220</td></tr><tr><td>6.5.1. Preparing for an Operator update</td><td>221</td></tr><tr><td>6.5.2. Changing the update channel for an Operator</td><td>221</td></tr><tr><td>6.5.3. Manually approving a pending Operator update</td><td>222</td></tr><tr><td>6.6. UNDERSTANDING THE FILE INTEGRITY OPERATOR</td><td>222</td></tr><tr><td>6.6.1. Creating the FileIntegrity custom resource</td><td>222</td></tr><tr><td>6.6.2. Checking the FileIntegrity custom resource status</td><td>224</td></tr><tr><td>6.6.3. FileIntegrity custom resource phases</td><td>224</td></tr><tr><td>6.6.4. Understanding the FileIntegrityNodeStatuses object</td><td>224</td></tr><tr><td>6.6.5. FileIntegrityNodeStatus CR status types</td><td>225</td></tr><tr><td>6.6.5.1. FileIntegrityNodeStatus CR success example</td><td>226</td></tr><tr><td>6.6.5.2. FileIntegrityNodeStatus CR failure status example</td><td>226</td></tr><tr><td>6.6.6. Understanding events</td><td>228</td></tr><tr><td>6.7. CONFIGURING THE CUSTOM FILE INTEGRITY OPERATOR</td><td>229</td></tr><tr><td>6.7.1. Viewing FileIntegrity object attributes</td><td>229</td></tr><tr><td>6.7.2. Important attributes</td><td>230</td></tr><tr><td>6.7.3. Examine the default configuration</td><td>231</td></tr><tr><td>6.7.4. Understanding the default File Integrity Operator configuration</td><td>231</td></tr><tr><td>6.7.5. Supplying a custom AIDE configuration</td><td>231</td></tr><tr><td>6.7.6. Defining a custom File Integrity Operator configuration</td><td>232</td></tr><tr><td>6.7.7. Changing the custom File Integrity configuration</td><td>233</td></tr><tr><td>6.8. PERFORMING ADVANCED CUSTOM FILE INTEGRITY OPERATOR TASKS</td><td>233</td></tr><tr><td>6.8.1. Reinitializing the database</td><td>233</td></tr><tr><td>6.8.2. Machine config integration</td><td>234</td></tr><tr><td>6.8.3. Exploring the daemon sets</td><td>234</td></tr></table>\n\n---<table>\n<tr>\n<td>6.9. TROUBLESHOOTING THE FILE INTEGRITY OPERATOR</td>\n<td>235</td>\n</tr>\n<tr>\n<td> 6.9.1. General troubleshooting</td>\n<td>235</td>\n</tr>\n<tr>\n<td> 6.9.2. Checking the AIDE configuration</td>\n<td>235</td>\n</tr>\n<tr>\n<td> 6.9.3. Determining the FileIntegrity object's phase</td>\n<td>235</td>\n</tr>\n<tr>\n<td> 6.9.4. Determining that the daemon set's pods are running on the expected nodes</td>\n<td>235</td>\n</tr>\n<tr>\n<td>6.10. UNINSTALLING THE FILE INTEGRITY OPERATOR</td>\n<td>236</td>\n</tr>\n<tr>\n<td> 6.10.1. Uninstall the File Integrity Operator using the web console</td>\n<td>236</td>\n</tr>\n<tr>\n<td><b>CHAPTER 7. SECURITY PROFILES OPERATOR</b></td>\n<td><b>237</b></td>\n</tr>\n<tr>\n<td> 7.1. SECURITY PROFILES OPERATOR OVERVIEW</td>\n<td>237</td>\n</tr>\n<tr>\n<td> 7.2. SECURITY PROFILES OPERATOR RELEASE NOTES</td>\n<td>237</td>\n</tr>\n<tr>\n<td> 7.2.1. Security Profiles Operator 0.10.0</td>\n<td>237</td>\n</tr>\n<tr>\n<td> 7.2.1.1. Bug fixes</td>\n<td>237</td>\n</tr>\n<tr>\n<td> 7.2.1.2. New features and enhancements</td>\n<td>238</td>\n</tr>\n<tr>\n<td> 7.2.2. Security Profiles Operator 0.9.0</td>\n<td>238</td>\n</tr>\n<tr>\n<td> 7.2.2.1. Bug fixes</td>\n<td>238</td>\n</tr>\n<tr>\n<td> 7.2.3. Security Profiles Operator 0.8.6</td>\n<td>238</td>\n</tr>\n<tr>\n<td> 7.2.4. Security Profiles Operator 0.8.5</td>\n<td>238</td>\n</tr>\n<tr>\n<td> 7.2.4.1. Bug fixes</td>\n<td>239</td>\n</tr>\n<tr>\n<td> 7.2.5. Security Profiles Operator 0.8.4</td>\n<td>239</td>\n</tr>\n<tr>\n<td> 7.2.5.1. New features and enhancements</td>\n<td>239</td>\n</tr>\n<tr>\n<td> 7.2.6. Security Profiles Operator 0.8.2</td>\n<td>239</td>\n</tr>\n<tr>\n<td> 7.2.6.1. Bug fixes</td>\n<td>239</td>\n</tr>\n<tr>\n<td> 7.2.7. Security Profiles Operator 0.8.0</td>\n<td>240</td>\n</tr>\n<tr>\n<td> 7.2.7.1. Bug fixes</td>\n<td>240</td>\n</tr>\n<tr>\n<td> 7.2.8. Security Profiles Operator 0.7.1</td>\n<td>240</td>\n</tr>\n<tr>\n<td> 7.2.8.1. New features and enhancements</td>\n<td>240</td>\n</tr>\n<tr>\n<td> 7.2.8.2. Deprecated and removed features</td>\n<td>240</td>\n</tr>\n<tr>\n<td> 7.2.8.3. Bug fixes</td>\n<td>240</td>\n</tr>\n<tr>\n<td> 7.2.8.4. Known issue</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.2.9. Security Profiles Operator 0.5.2</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.2.9.1. Known issue</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.2.10. Security Profiles Operator 0.5.0</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.2.10.1. Known issue</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.3. SECURITY PROFILES OPERATOR SUPPORT</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.3.1. Security Profiles Operator lifecycle</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.3.2. Getting support</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.4. UNDERSTANDING THE SECURITY PROFILES OPERATOR</td>\n<td>242</td>\n</tr>\n<tr>\n<td> 7.4.1. About Security Profiles</td>\n<td>242</td>\n</tr>\n<tr>\n<td> 7.5. ENABLING THE SECURITY PROFILES OPERATOR</td>\n<td>242</td>\n</tr>\n<tr>\n<td> 7.5.1. Installing the Security Profiles Operator</td>\n<td>243</td>\n</tr>\n<tr>\n<td> 7.5.2. Installing the Security Profiles Operator using the CLI</td>\n<td>243</td>\n</tr>\n<tr>\n<td> 7.5.3. Configuring logging verbosity</td>\n<td>245</td>\n</tr>\n<tr>\n<td> 7.6. MANAGING SECCOMP PROFILES</td>\n<td>245</td>\n</tr>\n<tr>\n<td> 7.6.1. Creating seccomp profiles</td>\n<td>245</td>\n</tr>\n<tr>\n<td> 7.6.2. Applying seccomp profiles to a pod</td>\n<td>246</td>\n</tr>\n<tr>\n<td> 7.6.2.1. Binding workloads to profiles with ProfileBindings</td>\n<td>247</td>\n</tr>\n<tr>\n<td> 7.6.3. Recording profiles from workloads</td>\n<td>249</td>\n</tr>\n<tr>\n<td> 7.6.3.1. Merging per-container profile instances</td>\n<td>251</td>\n</tr>\n<tr>\n<td> 7.6.4. Additional resources</td>\n<td>252</td>\n</tr>\n<tr>\n<td> 7.7. MANAGING SELINUX PROFILES</td>\n<td>252</td>\n</tr>\n<tr>\n<td> 7.7.1. Creating SELinux profiles</td>\n<td>252</td>\n</tr>\n<tr>\n<td> 7.7.2. Applying SELinux profiles to a pod</td>\n<td>254</td>\n</tr>\n</table><table>\n<tr><td>7.7.2.1. Applying SELinux log policies</td><td>255</td></tr>\n<tr><td>7.7.2.2. Binding workloads to profiles with ProfileBindings</td><td>255</td></tr>\n<tr><td>7.7.2.3. Replicating controllers and SecurityContextConstraints</td><td>257</td></tr>\n<tr><td>7.7.3. Recording profiles from workloads</td><td>258</td></tr>\n<tr><td>7.7.3.1. Merging per-container profile instances</td><td>261</td></tr>\n<tr><td>7.7.3.2. About seLinuxContext: RunAsAny</td><td>262</td></tr>\n<tr><td>7.7.4. Additional resources</td><td>262</td></tr>\n<tr><td>7.8. ADVANCED SECURITY PROFILES OPERATOR TASKS</td><td>262</td></tr>\n<tr><td>7.8.1. Restrict the allowed syscalls in seccomp profiles</td><td>262</td></tr>\n<tr><td>7.8.2. Base syscalls for a container runtime</td><td>263</td></tr>\n<tr><td>7.8.3. Enabling memory optimization in the spod daemon</td><td>263</td></tr>\n<tr><td>7.8.4. Customizing daemon resource requirements</td><td>264</td></tr>\n<tr><td>7.8.5. Setting a custom priority class name for the spod daemon pod</td><td>264</td></tr>\n<tr><td>7.8.6. Using metrics</td><td>264</td></tr>\n<tr><td>7.8.6.1. controller-runtime metrics</td><td>265</td></tr>\n<tr><td>7.8.7. Using the log enricher</td><td>267</td></tr>\n<tr><td>7.8.7.1. Using the log enricher to trace an application</td><td>268</td></tr>\n<tr><td>7.8.8. Configuring webhooks</td><td>269</td></tr>\n<tr><td>7.9. ADVANCED AUDIT LOGGING FRAMEWORK</td><td>270</td></tr>\n<tr><td>7.9.1. Benefits of Advanced Audit Logging Framework</td><td>270</td></tr>\n<tr><td>7.9.2. Performance considerations</td><td>271</td></tr>\n<tr><td>7.9.3. Prerequisites for use of the Advanced Audit Logging Framework</td><td>271</td></tr>\n<tr><td>7.9.4. The Audit JSON log enricher</td><td>272</td></tr>\n<tr><td>7.9.5. Kubernetes API log compared to Advanced Audit Logging output</td><td>272</td></tr>\n<tr><td>7.9.6. Enabling Advanced Audit Logging</td><td>273</td></tr>\n<tr><td>7.9.7. Audit JSON Log Enricher configuration</td><td>274</td></tr>\n<tr><td>7.9.8. Audit log file fine-tuning and rotation</td><td>275</td></tr>\n<tr><td>7.9.9. Advanced Audit Logs for a specific pod</td><td>276</td></tr>\n<tr><td>7.9.10. Monitoring the audit logs</td><td>279</td></tr>\n<tr><td>7.9.11. Auditing node debugging sessions</td><td>280</td></tr>\n<tr><td>7.9.12. Correlate with Kubernetes audit logs</td><td>282</td></tr>\n<tr><td>7.9.13. Audit JSON Log Enricher Output</td><td>283</td></tr>\n<tr><td>7.9.14. Kubernetes API audit log output</td><td>283</td></tr>\n<tr><td>7.9.15. Correlation key</td><td>284</td></tr>\n<tr><td>7.9.16. Correlating with API Server Audit Log</td><td>284</td></tr>\n<tr><td>7.9.17. Using the mutating webhook</td><td>285</td></tr>\n<tr><td>7.9.17.1. The Debug Pod</td><td>285</td></tr>\n<tr><td>7.9.18. Disabling Advanced Audit Logging</td><td>286</td></tr>\n<tr><td>7.9.19. Additional resources</td><td>286</td></tr>\n<tr><td>7.10. TROUBLESHOOTING THE SECURITY PROFILES OPERATOR</td><td>287</td></tr>\n<tr><td>7.10.1. Inspecting seccomp profiles</td><td>287</td></tr>\n<tr><td>7.11. UNINSTALLING THE SECURITY PROFILES OPERATOR</td><td>288</td></tr>\n<tr><td>7.11.1. Uninstall the Security Profiles Operator using the web console</td><td>288</td></tr>\n<tr><td><b>CHAPTER 8. NBDE TANG SERVER OPERATOR</b></td><td><b>289</b></td></tr>\n<tr><td>8.1. NBDE TANG SERVER OPERATOR OVERVIEW</td><td>289</td></tr>\n<tr><td>8.2. NBDE TANG SERVER OPERATOR RELEASE NOTES</td><td>289</td></tr>\n<tr><td>8.3. UNDERSTANDING THE NBDE TANG SERVER OPERATOR</td><td>289</td></tr>\n<tr><td>8.3.1. Additional resources</td><td>290</td></tr>\n<tr><td>8.4. INSTALLING THE NBDE TANG SERVER OPERATOR</td><td>290</td></tr>\n<tr><td>8.4.1. Installing the NBDE Tang Server Operator using the web console</td><td>290</td></tr>\n<tr><td>8.4.2. Installing the NBDE Tang Server Operator using CLI</td><td>291</td></tr>\n<tr><td>8.5. CONFIGURING AND MANAGING TANG SERVERS USING THE NBDE TANG SERVER OPERATOR</td><td>292</td></tr>\n</table><table>\n<tr>\n<td>8.5.1. Deploying a Tang server using the NBDE Tang Server Operator</td>\n<td>292</td>\n</tr>\n<tr>\n<td>8.5.2. Rotating keys using the NBDE Tang Server Operator</td>\n<td>298</td>\n</tr>\n<tr>\n<td>8.5.3. Deleting hidden keys with the NBDE Tang Server Operator</td>\n<td>299</td>\n</tr>\n<tr>\n<td>8.6. IDENTIFYING URL OF A TANG SERVER DEPLOYED WITH THE NBDE TANG SERVER OPERATOR</td>\n<td>301</td>\n</tr>\n<tr>\n<td>8.6.1. Identifying URL of the NBDE Tang Server Operator using the web console</td>\n<td>301</td>\n</tr>\n<tr>\n<td>8.6.2. Identifying URL of the NBDE Tang Server Operator using CLI</td>\n<td>303</td>\n</tr>\n<tr>\n<td>8.6.3. Additional resources</td>\n<td>304</td>\n</tr>\n<tr>\n<td><b>CHAPTER 9. UNDERSTANDING SECRETS MANAGEMENT IN OPENSHIFT CONTAINER PLATFORM ..</b></td>\n<td><b>305</b></td>\n</tr>\n<tr>\n<td>9.1. SECRETS MANAGEMENT OPERATORS IN OPENSHIFT CONTAINER PLATFORM</td>\n<td>305</td>\n</tr>\n<tr>\n<td><b>CHAPTER 10. CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT .....</b></td>\n<td><b>306</b></td>\n</tr>\n<tr>\n<td>10.1. CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT OVERVIEW</td>\n<td>306</td>\n</tr>\n<tr>\n<td>10.1.1. About the cert-manager Operator for Red Hat OpenShift</td>\n<td>306</td>\n</tr>\n<tr>\n<td>10.1.2. cert-manager Operator for Red Hat OpenShift issuer providers</td>\n<td>306</td>\n</tr>\n<tr>\n<td>10.1.3. Certificate request methods</td>\n<td>307</td>\n</tr>\n<tr>\n<td>10.1.4. Supported cert-manager Operator for Red Hat OpenShift versions</td>\n<td>307</td>\n</tr>\n<tr>\n<td>10.1.5. About FIPS compliance for cert-manager Operator for Red Hat OpenShift</td>\n<td>307</td>\n</tr>\n<tr>\n<td>10.1.6. Additional resources</td>\n<td>307</td>\n</tr>\n<tr>\n<td>10.2. CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT RELEASE NOTES</td>\n<td>308</td>\n</tr>\n<tr>\n<td>10.2.1. cert-manager Operator for Red Hat OpenShift 1.18.1</td>\n<td>308</td>\n</tr>\n<tr>\n<td>10.2.1.1. New features and enhancements</td>\n<td>308</td>\n</tr>\n<tr>\n<td>10.2.1.2. CVEs</td>\n<td>308</td>\n</tr>\n<tr>\n<td>10.2.2. cert-manager Operator for Red Hat OpenShift 1.18.0</td>\n<td>309</td>\n</tr>\n<tr>\n<td>10.2.2.1. New features and enhancements</td>\n<td>309</td>\n</tr>\n<tr>\n<td>10.2.2.2. Known issues</td>\n<td>309</td>\n</tr>\n<tr>\n<td>10.3. INSTALLING THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>310</td>\n</tr>\n<tr>\n<td>10.3.1. Installing the cert-manager Operator for Red Hat OpenShift</td>\n<td>310</td>\n</tr>\n<tr>\n<td>10.3.1.1. Installing the cert-manager Operator for Red Hat OpenShift by using the web console</td>\n<td>310</td>\n</tr>\n<tr>\n<td>10.3.1.2. Installing the cert-manager Operator for Red Hat OpenShift by using the CLI</td>\n<td>311</td>\n</tr>\n<tr>\n<td>10.3.2. Understanding update channels of the cert-manager Operator for Red Hat OpenShift</td>\n<td>314</td>\n</tr>\n<tr>\n<td>10.3.2.1. stable-v1 channel</td>\n<td>314</td>\n</tr>\n<tr>\n<td>10.3.2.2. stable-v1.y channel</td>\n<td>314</td>\n</tr>\n<tr>\n<td>10.3.3. Additional resources</td>\n<td>315</td>\n</tr>\n<tr>\n<td>10.4. CONFIGURING THE EGRESS PROXY FOR THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>315</td>\n</tr>\n<tr>\n<td>10.4.1. Injecting a custom CA certificate for the cert-manager Operator for Red Hat OpenShift</td>\n<td>315</td>\n</tr>\n<tr>\n<td>10.4.2. Additional resources</td>\n<td>316</td>\n</tr>\n<tr>\n<td>10.5. CUSTOMIZING THE CERT-MANAGER OPERATOR BY USING THE CERTMANAGER CUSTOM RESOURCE</td>\n<td>316</td>\n</tr>\n<tr>\n<td>10.5.1. Explanation of fields in the CertManager custom resource</td>\n<td>318</td>\n</tr>\n<tr>\n<td>10.5.1.1. Common configurable fields in the CertManager CR for the cert-manager components</td>\n<td>318</td>\n</tr>\n<tr>\n<td>10.5.1.2. Overridable arguments for the cert-manager components</td>\n<td>319</td>\n</tr>\n<tr>\n<td>10.5.1.3. Overridable environment variables for the cert-manager controller</td>\n<td>321</td>\n</tr>\n<tr>\n<td>10.5.1.4. Overridable resource parameters for the cert-manager components</td>\n<td>321</td>\n</tr>\n<tr>\n<td>10.5.1.5. Overridable scheduling parameters for the cert-manager components</td>\n<td>321</td>\n</tr>\n<tr>\n<td>10.5.2. Customizing cert-manager by overriding environment variables from the cert-manager Operator API</td>\n<td>322</td>\n</tr>\n<tr>\n<td>10.5.3. Customizing cert-manager by overriding arguments from the cert-manager Operator API</td>\n<td>324</td>\n</tr>\n<tr>\n<td>10.5.4. Deleting a TLS secret automatically upon Certificate removal</td>\n<td>325</td>\n</tr>\n<tr>\n<td>10.5.5. Overriding CPU and memory limits for the cert-manager components</td>\n<td>327</td>\n</tr>\n<tr>\n<td>10.5.6. Configuring scheduling overrides for cert-manager components</td>\n<td>330</td>\n</tr>\n<tr>\n<td>10.6. AUTHENTICATING THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>332</td>\n</tr>\n<tr>\n<td>10.6.1. Authenticating on AWS</td>\n<td>332</td>\n</tr>\n</table>---\n\n<table>\n<tr>\n<td>10.6.2. Authenticating with AWS Security Token Service</td>\n<td>334</td>\n</tr>\n<tr>\n<td>10.6.3. Authenticating on Google Cloud</td>\n<td>336</td>\n</tr>\n<tr>\n<td>10.6.4. Authenticating with Google Cloud Workload Identity</td>\n<td>338</td>\n</tr>\n<tr>\n<td>10.7. CONFIGURING AN ACME ISSUER</td>\n<td>340</td>\n</tr>\n<tr>\n<td>10.7.1. About ACME issuers</td>\n<td>341</td>\n</tr>\n<tr>\n<td> 10.7.1.1. Supported ACME challenges types</td>\n<td>341</td>\n</tr>\n<tr>\n<td> 10.7.1.2. Supported DNS-01 providers</td>\n<td>342</td>\n</tr>\n<tr>\n<td>10.7.2. Configuring an ACME issuer to solve HTTP-01 challenges</td>\n<td>342</td>\n</tr>\n<tr>\n<td>10.7.3. Configuring an ACME issuer by using explicit credentials for AWS Route53</td>\n<td>345</td>\n</tr>\n<tr>\n<td>10.7.4. Configuring an ACME issuer by using ambient credentials on AWS</td>\n<td>347</td>\n</tr>\n<tr>\n<td>10.7.5. Configuring an ACME issuer by using explicit credentials for Google Cloud DNS</td>\n<td>349</td>\n</tr>\n<tr>\n<td>10.7.6. Configuring an ACME issuer by using ambient credentials on Google Cloud</td>\n<td>351</td>\n</tr>\n<tr>\n<td>10.7.7. Configuring an ACME issuer by using explicit credentials for Microsoft Azure DNS</td>\n<td>353</td>\n</tr>\n<tr>\n<td>10.7.8. Additional resources</td>\n<td>356</td>\n</tr>\n<tr>\n<td>10.8. CONFIGURING CERTIFICATES WITH AN ISSUER</td>\n<td>356</td>\n</tr>\n<tr>\n<td>10.8.1. Creating certificates for user workloads</td>\n<td>356</td>\n</tr>\n<tr>\n<td>10.8.2. Creating certificates for the API server</td>\n<td>357</td>\n</tr>\n<tr>\n<td>10.8.3. Creating certificates for the Ingress Controller</td>\n<td>359</td>\n</tr>\n<tr>\n<td>10.8.4. Additional resources</td>\n<td>360</td>\n</tr>\n<tr>\n<td>10.9. SECURING ROUTES WITH THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>361</td>\n</tr>\n<tr>\n<td>10.9.1. Configuring certificates to secure routes in your cluster</td>\n<td>361</td>\n</tr>\n<tr>\n<td>10.9.2. Additional resources</td>\n<td>364</td>\n</tr>\n<tr>\n<td>10.10. INTEGRATING THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT WITH ISTIO-CSR</td>\n<td>364</td>\n</tr>\n<tr>\n<td>10.10.1. Installing the Istio-CSR agent through cert-manager Operator for Red Hat OpenShift</td>\n<td>364</td>\n</tr>\n<tr>\n<td> 10.10.1.1. Creating a root CA issuer for the Istio-CSR agent</td>\n<td>364</td>\n</tr>\n<tr>\n<td> 10.10.1.2. Creating the IstioCSR custom resource</td>\n<td>366</td>\n</tr>\n<tr>\n<td> 10.10.1.3. Setting the log level for the istio-csr component</td>\n<td>368</td>\n</tr>\n<tr>\n<td> 10.10.1.4. Configuring the namespace selector for CA bundle distribution</td>\n<td>369</td>\n</tr>\n<tr>\n<td> 10.10.1.5. Configuring the CA certificate for the Istio server</td>\n<td>370</td>\n</tr>\n<tr>\n<td>10.10.2. Uninstalling the Istio-CSR agent managed by cert-manager Operator for Red Hat OpenShift</td>\n<td>371</td>\n</tr>\n<tr>\n<td>10.11. NETWORK POLICY CONFIGURATION FOR CERT-MANAGER OPERATOR</td>\n<td>372</td>\n</tr>\n<tr>\n<td>10.11.1. Default ingress and egress rules</td>\n<td>373</td>\n</tr>\n<tr>\n<td>10.11.2. Network policy configuration parameters</td>\n<td>373</td>\n</tr>\n<tr>\n<td>10.11.3. Network policy configuration examples</td>\n<td>374</td>\n</tr>\n<tr>\n<td>10.11.4. Verifying the network policy creation</td>\n<td>375</td>\n</tr>\n<tr>\n<td>10.12. MONITORING CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>376</td>\n</tr>\n<tr>\n<td>10.12.1. Enabling user workload monitoring</td>\n<td>376</td>\n</tr>\n<tr>\n<td>10.12.2. Configuring metrics collection for cert-manager Operator for Red Hat OpenShift operands by using a ServiceMonitor</td>\n<td>377</td>\n</tr>\n<tr>\n<td>10.12.3. Querying metrics for the cert-manager Operator for Red Hat OpenShift operands</td>\n<td>379</td>\n</tr>\n<tr>\n<td>10.12.4. Configuring metrics collection for the istio-csr operand</td>\n<td>379</td>\n</tr>\n<tr>\n<td>10.12.5. Querying metrics for the istio-csr operand</td>\n<td>380</td>\n</tr>\n<tr>\n<td>10.13. CONFIGURING LOG LEVELS FOR CERT-MANAGER AND THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>381</td>\n</tr>\n<tr>\n<td>10.13.1. Setting a log level for cert-manager</td>\n<td>381</td>\n</tr>\n<tr>\n<td>10.13.2. Setting a log level for the cert-manager Operator for Red Hat OpenShift</td>\n<td>382</td>\n</tr>\n<tr>\n<td>10.13.3. Additional resources</td>\n<td>383</td>\n</tr>\n<tr>\n<td>10.14. UNINSTALLING THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>383</td>\n</tr>\n<tr>\n<td>10.14.1. Uninstalling the cert-manager Operator for Red Hat OpenShift</td>\n<td>383</td>\n</tr>\n<tr>\n<td>10.14.2. Removing cert-manager Operator for Red Hat OpenShift resources</td>\n<td>383</td>\n</tr>\n<tr>\n<td><b>CHAPTER 11. ZERO TRUST WORKLOAD IDENTITY MANAGER</b> .....</td>\n<td><b>386</b></td>\n</tr>\n<tr>\n<td>11.1. ZERO TRUST WORKLOAD IDENTITY MANAGER OVERVIEW</td>\n<td>386</td>\n</tr>\n</table>\n\n---<table><tr><td>11.1.1. SPIFFE</td><td>386</td></tr><tr><td>11.1.2. SPIRE Server</td><td>386</td></tr><tr><td>11.1.3. SPIRE Agent</td><td>386</td></tr><tr><td>11.1.4. Attestation</td><td>386</td></tr><tr><td>11.2. ZERO TRUST WORKLOAD IDENTITY MANAGER COMPONENTS</td><td>387</td></tr><tr><td>11.2.1. SPIFFE CSI Driver</td><td>387</td></tr><tr><td>11.2.2. SPIRE OpenID Connect Discovery Provider</td><td>387</td></tr><tr><td>11.2.3. SPIRE Controller Manager</td><td>387</td></tr><tr><td>11.2.4. SPIRE Server and Agent telemetry</td><td>387</td></tr><tr><td>11.2.5. About the Zero Trust Workload Identity Manager workflow</td><td>388</td></tr><tr><td>11.3. ZERO TRUST WORKLOAD IDENTITY MANAGER RELEASE NOTES</td><td>389</td></tr><tr><td>11.3.1. Zero Trust Workload Identity Manager 1.0.0 (General Availability)</td><td>389</td></tr><tr><td>11.3.1.1. New features and enhancements</td><td>389</td></tr><tr><td>11.3.1.2. Status and observability improvements</td><td>392</td></tr><tr><td>11.3.1.3. Fixed issues</td><td>392</td></tr><tr><td>11.3.2. Zero Trust Workload Identity Manager 0.2.0 (Technology Preview)</td><td>393</td></tr><tr><td>11.3.2.1. New features and enhancements</td><td>394</td></tr><tr><td>11.3.2.2. Fixed issues</td><td>394</td></tr><tr><td>11.3.3. Zero Trust Workload Identity Manager 0.1.0 (Technology Preview)</td><td>395</td></tr><tr><td>11.4. INSTALLING THE ZERO TRUST WORKLOAD IDENTITY MANAGER</td><td>396</td></tr><tr><td>11.4.1. Installing the Zero Trust Workload Identity Manager by using the web console</td><td>396</td></tr><tr><td>11.4.2. Installing the Zero Trust Workload Identity Manager by using the CLI</td><td>397</td></tr><tr><td>11.5. DEPLOYING ZERO TRUST WORKLOAD IDENTITY MANAGER OPERANDS</td><td>399</td></tr><tr><td>11.5.1. About the ZeroTrustWorkloadIdentityManager custom resource</td><td>399</td></tr><tr><td>11.5.2. Deploying the SPIRE Server</td><td>400</td></tr><tr><td>11.5.3. Deploying the SPIRE Agent</td><td>403</td></tr><tr><td>11.5.4. Deploying the SPIFFE Container Storage Interface driver</td><td>405</td></tr><tr><td>11.5.5. Deploying the SPIRE OpenID Connect Discovery Provider</td><td>407</td></tr><tr><td>11.5.6. Verify the health of the operands</td><td>409</td></tr><tr><td>11.6. CONFIGURING THE EGRESS PROXY FOR THE ZERO TRUST WORKLOAD IDENTITY MANAGER</td><td>409</td></tr><tr><td>11.6.1. Injecting a custom CA certificate for the Zero Trust Workload Identity Manager</td><td>410</td></tr><tr><td>11.6.2. Additional resources</td><td>412</td></tr><tr><td>11.7. ZERO TRUST WORKLOAD IDENTITY MANAGER OIDC FEDERATION</td><td>412</td></tr><tr><td>11.7.1. About the Entra ID OpenID Connect</td><td>412</td></tr><tr><td>11.7.1.1. Configuring the external certificate for the managed OIDC discovery provider route</td><td>412</td></tr><tr><td>11.7.1.2. Disabling a managed route</td><td>414</td></tr><tr><td>11.7.1.3. Using Entra ID with Microsoft Azure</td><td>414</td></tr><tr><td>11.7.1.4. Configuring Azure blob storage</td><td>415</td></tr><tr><td>11.7.1.5. Configuring an Azure user managed identity</td><td>416</td></tr><tr><td>11.7.1.6. Creating the demonstration application</td><td>416</td></tr><tr><td>11.7.1.7. Deploying the workload application</td><td>417</td></tr><tr><td>11.7.1.8. Configuring Azure with the SPIFFE identity federation</td><td>419</td></tr><tr><td>11.7.1.9. Verifying that the application workload can access the content in the Azure Blob Storage</td><td>419</td></tr><tr><td>11.7.2. About Vault OpenID Connect</td><td>420</td></tr><tr><td>11.7.2.1. Installing Vault</td><td>421</td></tr><tr><td>11.7.2.2. Initializing and unsealing Vault</td><td>422</td></tr><tr><td>11.7.2.3. Enabling the key-value secrets engine and store a test secret</td><td>423</td></tr><tr><td>11.7.2.4. Configuring JSON Web Token authentication with SPIRE</td><td>424</td></tr><tr><td>11.7.2.5. Deploying a demonstration application</td><td>426</td></tr><tr><td>11.7.2.6. Authenticating and retrieving the secret</td><td>427</td></tr><tr><td>11.8. ZERO TRUST WORKLOAD IDENTITY MANAGER SPIRE FEDERATION</td><td>427</td></tr><tr><td>11.8.1. Understanding bundle endpoint profiles</td><td>428</td></tr><tr><td>11.8.2. Federation configuration examples</td><td>429</td></tr></table>---\n\n<table>\n<tr>\n<td>11.8.3. Configuring SPIRE federation with the https_spiffe profile</td>\n<td>431</td>\n</tr>\n<tr>\n<td>11.8.4. Using SPIRE federation with Automatic Certificate Management Environment protocol</td>\n<td>435</td>\n</tr>\n<tr>\n<td>11.8.5. Using SPIRE federation with manual certificate management</td>\n<td>440</td>\n</tr>\n<tr>\n<td>11.8.6. Federation configuration field reference</td>\n<td>448</td>\n</tr>\n<tr>\n<td>11.9. ENABLING CREATE-ONLY MODE FOR THE ZERO TRUST WORKLOAD IDENTITY MANAGER</td>\n<td>452</td>\n</tr>\n<tr>\n<td>11.9.1. Pausing Operator reconciliation</td>\n<td>452</td>\n</tr>\n<tr>\n<td>11.9.2. Resuming Operator reconciliation</td>\n<td>453</td>\n</tr>\n<tr>\n<td>11.10. MONITORING ZERO TRUST WORKLOAD IDENTITY MANAGER</td>\n<td>453</td>\n</tr>\n<tr>\n<td>11.10.1. Enabling user workload monitoring</td>\n<td>454</td>\n</tr>\n<tr>\n<td>11.10.2. Configuring metrics collection for SPIRE Server by using a ServiceMonitor</td>\n<td>455</td>\n</tr>\n<tr>\n<td>11.10.3. Configuring metrics collection for SPIRE Agent by using a Service Monitor</td>\n<td>456</td>\n</tr>\n<tr>\n<td>11.10.4. Configuring metrics collection for the Operator by using a ServiceMonitor</td>\n<td>457</td>\n</tr>\n<tr>\n<td>11.10.5. Querying metrics for the Zero Trust Workload Identity Manager</td>\n<td>460</td>\n</tr>\n<tr>\n<td>11.10.6. Zero Trust Workload Identity Manager monitoring available metrics</td>\n<td>461</td>\n</tr>\n<tr>\n<td>11.11. UNINSTALLING THE ZERO TRUST WORKLOAD IDENTITY MANAGER</td>\n<td>462</td>\n</tr>\n<tr>\n<td>11.11.1. Uninstalling the Zero Trust Workload Identity Manager</td>\n<td>462</td>\n</tr>\n<tr>\n<td>11.11.2. Uninstalling Zero Trust Workload Identity Manager resources by using the CLI</td>\n<td>463</td>\n</tr>\n<tr>\n<td><b>CHAPTER 12. EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</b> .....</td>\n<td><b>465</b></td>\n</tr>\n<tr>\n<td>12.1. EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT OVERVIEW</td>\n<td>465</td>\n</tr>\n<tr>\n<td>12.1.1. About the External Secrets Operator for Red Hat OpenShift</td>\n<td>465</td>\n</tr>\n<tr>\n<td>12.1.2. External secrets providers for the External Secrets Operator for Red Hat OpenShift</td>\n<td>465</td>\n</tr>\n<tr>\n<td>12.1.3. About FIPS compliance for External Secrets Operator for Red Hat OpenShift</td>\n<td>466</td>\n</tr>\n<tr>\n<td>12.1.4. Security considerations</td>\n<td>466</td>\n</tr>\n<tr>\n<td>12.1.5. Additional resources</td>\n<td>466</td>\n</tr>\n<tr>\n<td>12.2. EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT RELEASE NOTES</td>\n<td>467</td>\n</tr>\n<tr>\n<td>12.2.1. Release notes for External Secrets Operator for Red Hat OpenShift 1.1.0 (General Availability)</td>\n<td>467</td>\n</tr>\n<tr>\n<td>12.2.1.1. New features and enhancements</td>\n<td>467</td>\n</tr>\n<tr>\n<td>12.2.2. Release notes for External Secrets Operator for Red Hat OpenShift 1.0.0 (General Availability)</td>\n<td>467</td>\n</tr>\n<tr>\n<td>12.2.2.1. Fixed issues</td>\n<td>468</td>\n</tr>\n<tr>\n<td>12.2.2.2. New features and enhancements</td>\n<td>468</td>\n</tr>\n<tr>\n<td>12.2.3. Release notes for External Secrets Operator for Red Hat OpenShift 0.1.0 (Technology Preview)</td>\n<td>469</td>\n</tr>\n<tr>\n<td>12.2.3.1. New features and enhancements</td>\n<td>469</td>\n</tr>\n<tr>\n<td>12.3. INSTALLING THE EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>469</td>\n</tr>\n<tr>\n<td>12.3.1. Limitations of External Secrets Operator for Red Hat OpenShift</td>\n<td>469</td>\n</tr>\n<tr>\n<td>12.3.2. Installing the External Secrets Operator for Red Hat OpenShift by using the web console</td>\n<td>469</td>\n</tr>\n<tr>\n<td>12.3.3. Installing the External Secrets Operator for Red Hat OpenShift by using the CLI</td>\n<td>471</td>\n</tr>\n<tr>\n<td>12.3.4. Additional resources</td>\n<td>472</td>\n</tr>\n<tr>\n<td>12.3.5. Installing the External Secrets operand by using the CLI</td>\n<td>472</td>\n</tr>\n<tr>\n<td>12.3.6. Understanding update channels of the External Secrets Operator for Red Hat OpenShift</td>\n<td>474</td>\n</tr>\n<tr>\n<td>12.3.6.1. About the External Secrets Operator for Red Hat OpenShift stable-v1 channel</td>\n<td>474</td>\n</tr>\n<tr>\n<td>12.3.6.2. About the External Secrets Operator for Red Hat OpenShift stable-v1.y channel</td>\n<td>474</td>\n</tr>\n<tr>\n<td>12.3.7. Additional resources</td>\n<td>475</td>\n</tr>\n<tr>\n<td>12.4. CONFIGURING NETWORK POLICY FOR THE OPERAND</td>\n<td>475</td>\n</tr>\n<tr>\n<td>12.4.1. Adding a custom network policy to allow egress to all external providers</td>\n<td>475</td>\n</tr>\n<tr>\n<td>12.4.2. Adding a custom network policy to allow egress to a specific provider</td>\n<td>476</td>\n</tr>\n<tr>\n<td>12.4.3. Default ingress and egress rules</td>\n<td>477</td>\n</tr>\n<tr>\n<td>12.5. ABOUT THE EGRESS PROXY FOR THE EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>477</td>\n</tr>\n<tr>\n<td>12.5.1. Configuring the egress proxy for the External Secrets Operator for Red Hat OpenShift</td>\n<td>477</td>\n</tr>\n<tr>\n<td>12.5.2. Additional resources</td>\n<td>479</td>\n</tr>\n<tr>\n<td>12.6. MONITORING THE EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>479</td>\n</tr>\n<tr>\n<td>12.6.1. Enabling user workload monitoring</td>\n<td>479</td>\n</tr>\n</table><table><tr><td>12.6.2. Configuring metrics collection for External Secrets Operator for Red Hat OpenShift by using a ServiceMonitor</td><td>480</td></tr><tr><td>12.6.3. Querying metrics for the External Secrets Operator for Red Hat OpenShift</td><td>483</td></tr><tr><td>12.6.4. Configuring metrics collection for External Secrets Operator for Red Hat OpenShift operands by using a ServiceMonitor</td><td>484</td></tr><tr><td>12.6.5. Querying metrics for the external-secrets operand</td><td>486</td></tr><tr><td>12.7. CUSTOMIZING THE EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</td><td>486</td></tr><tr><td>12.7.1. Setting a log level for the External Secrets Operator for Red Hat OpenShift</td><td>487</td></tr><tr><td>12.7.2. Setting a log level for the External Secrets Operator for Red Hat OpenShift operand</td><td>488</td></tr><tr><td>12.7.3. Configuring cert-manager for the external-secrets certificate requirements</td><td>489</td></tr><tr><td>12.7.4. Configuring the bitwardenSecretManagerProvider plugin</td><td>490</td></tr><tr><td>12.7.5. Adding custom annotations to external-secrets resources</td><td>491</td></tr><tr><td>12.7.6. Configuring the revisionHistoryLimit for external-secrets components</td><td>493</td></tr><tr><td>12.7.7. Setting custom environment variables for external-secrets components</td><td>494</td></tr><tr><td>12.8. UNINSTALLING THE EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</td><td>495</td></tr><tr><td>12.8.1. Uninstalling the External Secrets Operator for Red Hat OpenShift using the web console</td><td>495</td></tr><tr><td>12.8.2. Removing External Secrets Operator for Red Hat OpenShift resources by using the web console</td><td>496</td></tr><tr><td>12.8.3. Removing External Secrets Operator for Red Hat OpenShift resources by using the CLI</td><td>497</td></tr><tr><td>12.9. EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT APIS</td><td>498</td></tr><tr><td>12.9.1. externalSecretsManagerList</td><td>498</td></tr><tr><td>12.9.2. externalSecretsManager</td><td>499</td></tr><tr><td>12.9.3. externalSecretsConfigList</td><td>500</td></tr><tr><td>12.9.4. externalSecretsConfig</td><td>500</td></tr><tr><td>12.9.5. Listing fields in External Secrets Operator for Red Hat OpenShift APIs</td><td>501</td></tr><tr><td>12.9.6. externalSecretsManagerSpec</td><td>501</td></tr><tr><td>12.9.7. externalSecretsManagerStatus</td><td>502</td></tr><tr><td>12.9.8. externalSecretsConfigSpec</td><td>502</td></tr><tr><td>12.9.9. externalSecretsConfigStatus</td><td>503</td></tr><tr><td>12.9.10. globalConfig</td><td>503</td></tr><tr><td>12.9.11. controllerConfig</td><td>505</td></tr><tr><td>12.9.12. controllerStatus</td><td>506</td></tr><tr><td>12.9.13. applicationConfig</td><td>507</td></tr><tr><td>12.9.14. bitwardenSecretManagerProvider</td><td>509</td></tr><tr><td>12.9.15. webhookConfig</td><td>510</td></tr><tr><td>12.9.16. certManagerConfig</td><td>511</td></tr><tr><td>12.9.17. certProvidersConfig</td><td>513</td></tr><tr><td>12.9.18. objectReference</td><td>513</td></tr><tr><td>12.9.19. secretReference</td><td>514</td></tr><tr><td>12.9.20. condition</td><td>514</td></tr><tr><td>12.9.21. conditionalStatus</td><td>514</td></tr><tr><td>12.9.22. mode</td><td>515</td></tr><tr><td>12.9.23. pluginsConfig</td><td>515</td></tr><tr><td>12.9.24. proxyConfig</td><td>515</td></tr><tr><td>12.9.25. componentConfig</td><td>516</td></tr><tr><td>12.9.26. deploymentConfig</td><td>517</td></tr><tr><td>12.10. MIGRATING FROM THE COMMUNITY EXTERNAL SECRETS OPERATOR TO THE EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</td><td>518</td></tr><tr><td>12.10.1. Deleting the community External Secrets Operator</td><td>518</td></tr><tr><td>12.10.2. Uninstalling the community External Secrets Operator</td><td>519</td></tr><tr><td>12.10.2.1. Uninstalling a helm installed community External Secrets Operator</td><td>519</td></tr><tr><td>12.10.2.2. Uninstalling an Operator Lifecycle Manager installed community External Secrets Operator</td><td>520</td></tr><tr><td>12.10.2.3. Uninstalling a raw manifest installed community External Secrets Operator</td><td>520</td></tr><tr><td>12.10.3. Installing the External Secrets Operator for Red Hat OpenShift</td><td>521</td></tr></table>---\n\n<table>\n<tr>\n<td>12.10.4. Creating the ExternalSecretsConfig Operator</td>\n<td>521</td>\n</tr>\n<tr>\n<td><b>CHAPTER 13. VIEWING AUDIT LOGS</b> .....</td>\n<td><b>524</b></td>\n</tr>\n<tr>\n<td>13.1. ABOUT THE API AUDIT LOG</td>\n<td>524</td>\n</tr>\n<tr>\n<td>13.2. VIEWING THE AUDIT LOGS</td>\n<td>525</td>\n</tr>\n<tr>\n<td>13.3. FILTERING AUDIT LOGS</td>\n<td>529</td>\n</tr>\n<tr>\n<td>13.4. GATHERING AUDIT LOGS</td>\n<td>530</td>\n</tr>\n<tr>\n<td>13.5. ADDITIONAL RESOURCES</td>\n<td>530</td>\n</tr>\n<tr>\n<td><b>CHAPTER 14. CONFIGURING THE AUDIT LOG POLICY</b> .....</td>\n<td><b>531</b></td>\n</tr>\n<tr>\n<td>14.1. ABOUT AUDIT LOG POLICY PROFILES</td>\n<td>531</td>\n</tr>\n<tr>\n<td>14.2. CONFIGURING THE AUDIT LOG POLICY</td>\n<td>532</td>\n</tr>\n<tr>\n<td>14.3. CONFIGURING THE AUDIT LOG POLICY WITH CUSTOM RULES</td>\n<td>533</td>\n</tr>\n<tr>\n<td>14.4. DISABLING AUDIT LOGGING</td>\n<td>534</td>\n</tr>\n<tr>\n<td><b>CHAPTER 15. CONFIGURING TLS SECURITY PROFILES</b> .....</td>\n<td><b>537</b></td>\n</tr>\n<tr>\n<td>15.1. UNDERSTANDING TLS SECURITY PROFILES</td>\n<td>537</td>\n</tr>\n<tr>\n<td>15.2. VIEWING TLS SECURITY PROFILE DETAILS</td>\n<td>538</td>\n</tr>\n<tr>\n<td>15.3. CONFIGURING THE TLS SECURITY PROFILE FOR THE INGRESS CONTROLLER</td>\n<td>540</td>\n</tr>\n<tr>\n<td>15.4. CONFIGURING THE TLS SECURITY PROFILE FOR THE CONTROL PLANE</td>\n<td>542</td>\n</tr>\n<tr>\n<td>15.5. CONFIGURING THE TLS SECURITY PROFILE FOR THE KUBELET</td>\n<td>545</td>\n</tr>\n<tr>\n<td><b>CHAPTER 16. CONFIGURING SECCOMP PROFILES</b> .....</td>\n<td><b>548</b></td>\n</tr>\n<tr>\n<td>16.1. VERIFYING THE DEFAULT SECCOMP PROFILE APPLIED TO A POD</td>\n<td>548</td>\n</tr>\n<tr>\n<td>16.1.1. Upgraded cluster</td>\n<td>549</td>\n</tr>\n<tr>\n<td>16.1.2. Newly installed cluster</td>\n<td>549</td>\n</tr>\n<tr>\n<td>16.2. CONFIGURING A CUSTOM SECCOMP PROFILE</td>\n<td>550</td>\n</tr>\n<tr>\n<td>16.2.1. Creating seccomp profiles</td>\n<td>550</td>\n</tr>\n<tr>\n<td>16.2.2. Setting up the custom seccomp profile</td>\n<td>551</td>\n</tr>\n<tr>\n<td>16.2.3. Applying the custom seccomp profile to the workload</td>\n<td>551</td>\n</tr>\n<tr>\n<td>16.3. ADDITIONAL RESOURCES</td>\n<td>552</td>\n</tr>\n<tr>\n<td><b>CHAPTER 17. ALLOWING JAVASCRIPT-BASED ACCESS TO THE API SERVER FROM ADDITIONAL HOSTS</b> .</td>\n<td><b>553</b></td>\n</tr>\n<tr>\n<td>17.1. ALLOWING JAVASCRIPT-BASED ACCESS TO THE API SERVER FROM ADDITIONAL HOSTS</td>\n<td>553</td>\n</tr>\n<tr>\n<td><b>CHAPTER 18. SCANNING PODS FOR VULNERABILITIES</b> .....</td>\n<td><b>555</b></td>\n</tr>\n<tr>\n<td>18.1. INSTALLING THE RED HAT QUAY CONTAINER SECURITY OPERATOR</td>\n<td>555</td>\n</tr>\n<tr>\n<td>18.2. USING THE RED HAT QUAY CONTAINER SECURITY OPERATOR</td>\n<td>557</td>\n</tr>\n<tr>\n<td>18.3. QUERYING IMAGE VULNERABILITIES FROM THE CLI</td>\n<td>557</td>\n</tr>\n<tr>\n<td>18.4. UNINSTALLING THE RED HAT QUAY CONTAINER SECURITY OPERATOR</td>\n<td>558</td>\n</tr>\n<tr>\n<td><b>CHAPTER 19. NETWORK-BOUND DISK ENCRYPTION (NBDE)</b> .....</td>\n<td><b>560</b></td>\n</tr>\n<tr>\n<td>19.1. ABOUT DISK ENCRYPTION TECHNOLOGY</td>\n<td>560</td>\n</tr>\n<tr>\n<td>19.1.1. Disk encryption technology comparison</td>\n<td>560</td>\n</tr>\n<tr>\n<td>19.1.1.1. Key escrow</td>\n<td>560</td>\n</tr>\n<tr>\n<td>19.1.1.2. TPM encryption</td>\n<td>560</td>\n</tr>\n<tr>\n<td>19.1.1.3. Network-Bound Disk Encryption (NBDE)</td>\n<td>561</td>\n</tr>\n<tr>\n<td>19.1.1.4. Secret sharing encryption</td>\n<td>562</td>\n</tr>\n<tr>\n<td>19.1.2. Tang server disk encryption</td>\n<td>562</td>\n</tr>\n<tr>\n<td>19.1.3. Tang server location planning</td>\n<td>563</td>\n</tr>\n<tr>\n<td>19.1.4. Tang server sizing requirements</td>\n<td>564</td>\n</tr>\n<tr>\n<td>19.1.5. Logging considerations</td>\n<td>565</td>\n</tr>\n<tr>\n<td>19.2. TANG SERVER INSTALLATION CONSIDERATIONS</td>\n<td>565</td>\n</tr>\n<tr>\n<td>19.2.1. Installation scenarios</td>\n<td>565</td>\n</tr>\n</table><table><tr><td>19.2.2. Installing a Tang server</td><td>566</td></tr><tr><td> 19.2.2.1. Compute requirements</td><td>566</td></tr><tr><td> 19.2.2.2. Automatic start at boot</td><td>566</td></tr><tr><td> 19.2.2.3. HTTP versus HTTPS</td><td>566</td></tr><tr><td>19.3. TANG SERVER ENCRYPTION KEY MANAGEMENT</td><td>567</td></tr><tr><td> 19.3.1. Backing up keys for a Tang server</td><td>567</td></tr><tr><td> 19.3.2. Recovering keys for a Tang server</td><td>567</td></tr><tr><td> 19.3.3. Rekeying Tang servers</td><td>567</td></tr><tr><td> 19.3.3.1. Generating a new Tang server key</td><td>568</td></tr><tr><td> 19.3.3.2. Rekeying all NBDE nodes</td><td>570</td></tr><tr><td> 19.3.3.3. Troubleshooting temporary rekeying errors for Tang servers</td><td>573</td></tr><tr><td> 19.3.3.4. Troubleshooting permanent rekeying errors for Tang servers</td><td>573</td></tr><tr><td> 19.3.4. Deleting old Tang server keys</td><td>575</td></tr><tr><td>19.4. DISASTER RECOVERY CONSIDERATIONS</td><td>576</td></tr><tr><td> 19.4.1. Loss of a client machine</td><td>576</td></tr><tr><td> 19.4.2. Planning for a loss of client network connectivity</td><td>576</td></tr><tr><td> 19.4.3. Unexpected loss of network connectivity</td><td>577</td></tr><tr><td> 19.4.4. Recovering network connectivity manually</td><td>577</td></tr><tr><td> 19.4.5. Emergency recovery of network connectivity</td><td>578</td></tr><tr><td> 19.4.6. Loss of a network segment</td><td>578</td></tr><tr><td> 19.4.7. Loss of a Tang server</td><td>578</td></tr><tr><td> 19.4.8. Rekeying compromised key material</td><td>579</td></tr></table># CHAPTER 1. OPENSHIFT CONTAINER PLATFORM SECURITY AND COMPLIANCE\n\n## 1.1. SECURITY OVERVIEW\n\nIt is important to understand how to properly secure various aspects of your OpenShift Container Platform cluster.\n\n### 1.1.1. Container security\n\nA good starting point to understanding OpenShift Container Platform security is to review the concepts in [Understanding container security](#). This and subsequent sections provide a high-level walkthrough of the container security measures available in OpenShift Container Platform, including solutions for the host layer, the container and orchestration layer, and the build and application layer. These sections also include information on the following topics:\n\n- • Why container security is important and how it compares with existing security standards.\n- • Which container security measures are provided by the host (RHCOS and RHEL) layer and which are provided by OpenShift Container Platform.\n- • How to evaluate your container content and sources for vulnerabilities.\n- • How to design your build and deployment process to proactively check container content.\n- • How to control access to containers through authentication and authorization.\n- • How networking and attached storage are secured in OpenShift Container Platform.\n- • Containerized solutions for API management and SSO.\n\n### 1.1.2. Auditing\n\nOpenShift Container Platform auditing provides a security-relevant chronological set of records documenting the sequence of activities that have affected the system by individual users, administrators, or other components of the system. Administrators can [configure the audit log policy](#) and [view audit logs](#).\n\n### 1.1.3. Certificates\n\nCertificates are used by various components to validate access to the cluster. Administrators can [replace the default ingress certificate](#), [add API server certificates](#), or [add a service certificate](#).\n\nYou can also review more details about the types of certificates used by the cluster:\n\n- • [User-provided certificates for the API server](#)\n- • [Proxy certificates](#)\n- • [Service CA certificates](#)\n- • [Node certificates](#)\n- • [Bootstrap certificates](#)- • [etcd certificates](#)\n- • [OLM certificates](#)\n- • [Aggregated API client certificates](#)\n- • [Machine Config Operator certificates](#)\n- • [User-provided certificates for default ingress](#)\n- • [Ingress certificates](#)\n- • [Monitoring and cluster logging Operator component certificates](#)\n- • [Control plane certificates](#)\n\n### 1.1.4. Encrypting data\n\nYou can [enable etcd encryption](#) for your cluster to provide an additional layer of data security. For example, it can help protect the loss of sensitive data if an etcd backup is exposed to the incorrect parties.\n\n### 1.1.5. Vulnerability scanning\n\nAdministrators can use the Red Hat Quay Container Security Operator to run [vulnerability scans](#) and review information about detected vulnerabilities.\n\n## 1.2. COMPLIANCE OVERVIEW\n\nFor many OpenShift Container Platform customers, regulatory readiness, or compliance, on some level is required before any systems can be put into production. That regulatory readiness can be imposed by national standards, industry standards, or the organization's corporate governance framework.\n\n### 1.2.1. Compliance checking\n\nAdministrators can use the [Compliance Operator](#) to run compliance scans and recommend remediations for any issues found. The [oc-compliance plugin](#) is an OpenShift CLI (**oc**) plugin that provides a set of utilities to easily interact with the Compliance Operator.\n\n### 1.2.2. File integrity checking\n\nAdministrators can use the [File Integrity Operator](#) to continually run file integrity checks on cluster nodes and provide a log of files that have been modified.\n\n## 1.3. ADDITIONAL RESOURCES\n\n- • [Understanding authentication](#)\n- • [Configuring the internal OAuth server](#)\n- • [Understanding identity provider configuration](#)\n- • [Using RBAC to define and apply permissions](#)- ● [Managing security context constraints](#)## CHAPTER 2. CONTAINER SECURITY\n\n### 2.1. UNDERSTANDING CONTAINER SECURITY\n\nSecuring a containerized application relies on multiple levels of security:\n\n- • Container security begins with a trusted base container image and continues through the container build process as it moves through your CI/CD pipeline.\n\n#### IMPORTANT\n\nImage streams by default do not automatically update. This default behavior might create a security issue because security updates to images referenced by an image stream do not automatically occur. For information about how to override this default behavior, see [Configuring periodic importing of imagestreamtags](#).\n\n- • When a container is deployed, its security depends on it running on secure operating systems and networks, and establishing firm boundaries between the container itself and the users and hosts that interact with it.\n- • Continued security relies on being able to scan container images for vulnerabilities and having an efficient way to correct and replace vulnerable images.\n\nBeyond what a platform such as OpenShift Container Platform offers out of the box, your organization will likely have its own security demands. Some level of compliance verification might be needed before you can even bring OpenShift Container Platform into your data center.\n\nLikewise, you may need to add your own agents, specialized hardware drivers, or encryption features to OpenShift Container Platform, before it can meet your organization's security standards.\n\nThis guide provides a high-level walkthrough of the container security measures available in OpenShift Container Platform, including solutions for the host layer, the container and orchestration layer, and the build and application layer. It then points you to specific OpenShift Container Platform documentation to help you achieve those security measures.\n\nThis guide contains the following information:\n\n- • Why container security is important and how it compares with existing security standards.\n- • Which container security measures are provided by the host (RHCOS and RHEL) layer and which are provided by OpenShift Container Platform.\n- • How to evaluate your container content and sources for vulnerabilities.\n- • How to design your build and deployment process to proactively check container content.\n- • How to control access to containers through authentication and authorization.\n- • How networking and attached storage are secured in OpenShift Container Platform.\n- • Containerized solutions for API management and SSO.\n\nThe goal of this guide is to understand the incredible security benefits of using OpenShift Container Platform for your containerized workloads and how the entire Red Hat ecosystem plays a part in makingand keeping containers secure. It will also help you understand how you can engage with the OpenShift Container Platform to achieve your organization's security goals.\n\n### 2.1.1. What are containers?\n\nContainers package an application and all its dependencies into a single image that can be promoted from development, to test, to production, without change. A container might be part of a larger application that works closely with other containers.\n\nContainers provide consistency across environments and multiple deployment targets: physical servers, virtual machines (VMs), and private or public cloud.\n\nSome of the benefits of using containers include:\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Infrastructure</th>\n<th>Applications</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Sandboxed application processes on a shared Linux operating system kernel</td>\n<td>Package my application and all of its dependencies</td>\n</tr>\n<tr>\n<td>Simpler, lighter, and denser than virtual machines</td>\n<td>Deploy to any environment in seconds and enable CI/CD</td>\n</tr>\n<tr>\n<td>Portable across different environments</td>\n<td>Easily access and share containerized components</td>\n</tr>\n</tbody>\n</table>\n\nSee [Understanding Linux containers](#) from the Red Hat Customer Portal to find out more about Linux containers. To learn about RHEL container tools, see [Building, running, and managing containers](#) in the RHEL product documentation.\n\n### 2.1.2. What is OpenShift Container Platform?\n\nAutomating how containerized applications are deployed, run, and managed is the job of a platform such as OpenShift Container Platform. At its core, OpenShift Container Platform relies on the Kubernetes project to provide the engine for orchestrating containers across many nodes in scalable data centers.\n\nKubernetes is a project, which can run using different operating systems and add-on components that offer no guarantees of supportability from the project. As a result, the security of different Kubernetes platforms can vary.\n\nOpenShift Container Platform is designed to lock down Kubernetes security and integrate the platform with a variety of extended components. To do this, OpenShift Container Platform draws on the extensive Red Hat ecosystem of open source technologies that include the operating systems, authentication, storage, networking, development tools, base container images, and many other components.\n\nOpenShift Container Platform can leverage Red Hat's experience in uncovering and rapidly deploying fixes for vulnerabilities in the platform itself as well as the containerized applications running on the platform. Red Hat's experience also extends to efficiently integrating new components with OpenShift Container Platform as they become available and adapting technologies to individual customer needs.\n\n#### Additional resources\n\n- • [OpenShift Container Platform architecture](#)- • [OpenShift Security Guide](#)\n\n## 2.2. UNDERSTANDING HOST AND VM SECURITY\n\nBoth containers and virtual machines provide ways of separating applications running on a host from the operating system itself. Understanding RHCOS, which is the operating system used by OpenShift Container Platform, will help you see how the host systems protect containers and hosts from each other.\n\n### 2.2.1. Securing containers on Red Hat Enterprise Linux CoreOS (RHCOS)\n\nContainers simplify the act of deploying many applications to run on the same host, using the same kernel and container runtime to spin up each container. The applications can be owned by many users and, because they are kept separate, can run different, and even incompatible, versions of those applications at the same time without issue.\n\nIn Linux, containers are just a special type of process, so securing containers is similar in many ways to securing any other running process. An environment for running containers starts with an operating system that can secure the host kernel from containers and other processes running on the host, as well as secure containers from each other.\n\nBecause OpenShift Container Platform 4.21 runs on RHCOS hosts, with the option of using Red Hat Enterprise Linux (RHEL) as worker nodes, the following concepts apply by default to any deployed OpenShift Container Platform cluster. These RHEL security features are at the core of what makes running containers in OpenShift Container Platform more secure:\n\n- • *Linux namespaces* enable creating an abstraction of a particular global system resource to make it appear as a separate instance to processes within a namespace. Consequently, several containers can use the same computing resource simultaneously without creating a conflict. Container namespaces that are separate from the host by default include mount table, process table, network interface, user, control group, UTS, and IPC namespaces. Those containers that need direct access to host namespaces need to have elevated permissions to request that access. See [Building, running, and managing containers](#) from the RHEL 9 container documentation for details on the types of namespaces.\n- • *SELinux* provides an additional layer of security to keep containers isolated from each other and from the host. SELinux allows administrators to enforce mandatory access controls (MAC) for every user, application, process, and file.\n\n#### WARNING\n\nDisabling SELinux on RHCOS is not supported.\n\n- • *CGroups* (control groups) limit, account for, and isolate the resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. CGroups are used to ensure that containers on the same host are not impacted by each other.\n- • *Secure computing mode (seccomp)* profiles can be associated with a container to restrict available system calls. See page 94 of the [Red Hat OpenShift security guide](#) for details about seccomp.- • Deploying containers using *RHCOS* reduces the attack surface by minimizing the host environment and tuning it for containers. The [CRI-O container engine](#) further reduces that attack surface by implementing only those features required by Kubernetes and OpenShift Container Platform to run and manage containers, as opposed to other container engines that implement desktop-oriented standalone features.\n\nRHCOS is a version of Red Hat Enterprise Linux (RHEL) that is specially configured to work as control plane (master) and worker nodes on OpenShift Container Platform clusters. So RHCOS is tuned to efficiently run container workloads, along with Kubernetes and OpenShift Container Platform services.\n\n## NOTE\n\nTo further protect RHCOS systems in OpenShift Container Platform clusters, most containers, except those managing or monitoring the host system itself, should run as a non-root user. Dropping the privilege level or creating containers with the least amount of privileges possible is recommended best practice for protecting your own OpenShift Container Platform clusters.\n\n### Additional resources\n\n- • [How nodes enforce resource constraints](#)\n- • [Managing security context constraints](#)\n- • [Supported platforms for OpenShift clusters](#)\n- • [Choosing how to configure RHCOS](#)\n- • [Ignition](#)\n- • [Kernel arguments](#)\n- • [Kernel modules](#)\n- • [Disk encryption](#)\n- • [Chrony time service](#)\n- • [About the OpenShift Update Service](#)\n- • [FIPS cryptography](#)\n\n### 2.2.2. Comparing virtualization and containers\n\nTraditional virtualization provides another way to keep application environments separate on the same physical host. However, virtual machines work in a different way than containers. Virtualization relies on a hypervisor spinning up guest virtual machines (VMs), each of which has its own operating system (OS), represented by a running kernel, as well as the running application and its dependencies.\n\nWith VMs, the hypervisor isolates the guests from each other and from the host kernel. Fewer individuals and processes have access to the hypervisor, reducing the attack surface on the physical server. That said, security must still be monitored: one guest VM might be able to use hypervisor bugs to gain access to another VM or the host kernel. And, when the OS needs to be patched, it must be patched on all guest VMs using that OS."},"html":{"kind":"string","value":"<h1>OpenShift Container Platform 4.21</h1><h2>Security and compliance</h2><p>Learning about and managing security for OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Security and compliance</h1><hr/><p>Learning about and managing security for OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.</p><p>Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.</p><p>Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.</p><p>Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.</p><p>XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.</p><p>The OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.</p><p>All other trademarks are the property of their respective owners.</p><h2>Abstract</h2><p>This document discusses container security, configuring certificates, and enabling encryption to help secure the cluster.</p>\n<h1>Table of Contents</h1>\n\n<table>\n<tr>\n<td><b>CHAPTER 1. OPENSHIFT CONTAINER PLATFORM SECURITY AND COMPLIANCE</b> .....</td>\n<td><b>20</b></td>\n</tr>\n<tr>\n<td> 1.1. SECURITY OVERVIEW</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 1.1.1. Container security</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 1.1.2. Auditing</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 1.1.3. Certificates</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 1.1.4. Encrypting data</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.1.5. Vulnerability scanning</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.2. COMPLIANCE OVERVIEW</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.2.1. Compliance checking</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.2.2. File integrity checking</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 1.3. ADDITIONAL RESOURCES</td>\n<td>21</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. CONTAINER SECURITY</b> .....</td>\n<td><b>23</b></td>\n</tr>\n<tr>\n<td> 2.1. UNDERSTANDING CONTAINER SECURITY</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 2.1.1. What are containers?</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.1.2. What is OpenShift Container Platform?</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.2. UNDERSTANDING HOST AND VM SECURITY</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 2.2.1. Securing containers on Red Hat Enterprise Linux CoreOS (RHCOS)</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 2.2.2. Comparing virtualization and containers</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 2.2.3. Securing OpenShift Container Platform</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 2.3. HARDENING RHCOS</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 2.3.1. Choosing what to harden in RHCOS</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 2.3.2. Choosing how to harden RHCOS</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 2.3.2.1. Hardening before installation</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 2.3.2.2. Hardening during installation</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 2.3.2.3. Hardening after the cluster is running</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 2.4. CONTAINER IMAGE SIGNATURES</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 2.4.1. Enabling signature verification for Red Hat Container Registries</td>\n<td>30</td>\n</tr>\n<tr>\n<td> 2.4.2. Verifying the signature verification configuration</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 2.4.3. Understanding the verification of container images lacking verifiable signatures</td>\n<td>37</td>\n</tr>\n<tr>\n<td> 2.4.3.1. Automated verification during updates</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 2.4.3.2. Using skopeo to verify signatures of Red Hat container images</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 2.4.4. Additional resources</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 2.5. UNDERSTANDING COMPLIANCE</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 2.5.1. Understanding compliance and risk management</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 2.6. SECURING CONTAINER CONTENT</td>\n<td>40</td>\n</tr>\n<tr>\n<td> 2.6.1. Securing inside the container</td>\n<td>40</td>\n</tr>\n<tr>\n<td> 2.6.2. Creating redistributable images with UBI</td>\n<td>40</td>\n</tr>\n<tr>\n<td> 2.6.3. Security scanning in RHEL</td>\n<td>41</td>\n</tr>\n<tr>\n<td> 2.6.3.1. Scanning OpenShift images</td>\n<td>41</td>\n</tr>\n<tr>\n<td> 2.6.4. Integrating external scanning</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 2.6.4.1. Image metadata</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 2.6.4.1.1. Example annotation keys</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 2.6.4.1.2. Example annotation values</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 2.6.4.2. Annotating image objects</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 2.6.4.2.1. Example annotate CLI command</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 2.6.4.3. Controlling pod execution</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 2.6.4.3.1. Example annotation</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 2.6.4.4. Integration reference</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 2.6.4.4.1. Example REST API call</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 2.7. USING CONTAINER REGISTRIES SECURELY</td>\n<td>45</td>\n</tr>\n</table>\n\n<table>\n<tr>\n<td>2.7.1. Knowing where containers come from?</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.7.2. Immutable and certified containers</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.7.3. Getting containers from Red Hat Registry and Ecosystem Catalog</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.7.4. OpenShift Container Registry</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.7.5. Storing containers using Red Hat Quay</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.8. SECURING THE BUILD PROCESS</td>\n<td>48</td>\n</tr>\n<tr>\n<td>2.8.1. Building once, deploying everywhere</td>\n<td>48</td>\n</tr>\n<tr>\n<td>2.8.2. Managing builds</td>\n<td>49</td>\n</tr>\n<tr>\n<td>2.8.3. Securing inputs during builds</td>\n<td>49</td>\n</tr>\n<tr>\n<td>2.8.4. Designing your build process</td>\n<td>50</td>\n</tr>\n<tr>\n<td>2.8.5. Building Knative serverless applications</td>\n<td>51</td>\n</tr>\n<tr>\n<td>2.8.6. Additional resources</td>\n<td>51</td>\n</tr>\n<tr>\n<td>2.9. DEPLOYING CONTAINERS</td>\n<td>52</td>\n</tr>\n<tr>\n<td>2.9.1. Controlling container deployments with triggers</td>\n<td>52</td>\n</tr>\n<tr>\n<td>2.9.2. Controlling what image sources can be deployed</td>\n<td>53</td>\n</tr>\n<tr>\n<td>2.9.3. Using signature transports</td>\n<td>54</td>\n</tr>\n<tr>\n<td>2.9.4. Creating secrets and config maps</td>\n<td>55</td>\n</tr>\n<tr>\n<td>2.9.5. Automating continuous deployment</td>\n<td>55</td>\n</tr>\n<tr>\n<td>2.10. SECURING THE CONTAINER PLATFORM</td>\n<td>55</td>\n</tr>\n<tr>\n<td>2.10.1. Isolating containers with multitenancy</td>\n<td>56</td>\n</tr>\n<tr>\n<td>2.10.2. Protecting control plane with admission plugins</td>\n<td>56</td>\n</tr>\n<tr>\n<td>2.10.2.1. Security context constraints (SCCs)</td>\n<td>56</td>\n</tr>\n<tr>\n<td>2.10.2.2. Granting roles to service accounts</td>\n<td>57</td>\n</tr>\n<tr>\n<td>2.10.3. Authentication and authorization</td>\n<td>57</td>\n</tr>\n<tr>\n<td>2.10.3.1. Controlling access using OAuth</td>\n<td>57</td>\n</tr>\n<tr>\n<td>2.10.3.2. API access control and management</td>\n<td>57</td>\n</tr>\n<tr>\n<td>2.10.3.3. Red Hat Single Sign-On</td>\n<td>58</td>\n</tr>\n<tr>\n<td>2.10.3.4. Secure self-service web console</td>\n<td>58</td>\n</tr>\n<tr>\n<td>2.10.4. Managing certificates for the platform</td>\n<td>58</td>\n</tr>\n<tr>\n<td>2.10.4.1. Configuring custom certificates</td>\n<td>58</td>\n</tr>\n<tr>\n<td>2.11. SECURING NETWORKS</td>\n<td>59</td>\n</tr>\n<tr>\n<td>2.11.1. Using network namespaces</td>\n<td>59</td>\n</tr>\n<tr>\n<td>2.11.2. Isolating pods with network policies</td>\n<td>59</td>\n</tr>\n<tr>\n<td>2.11.3. Using multiple pod networks</td>\n<td>59</td>\n</tr>\n<tr>\n<td>2.11.4. Isolating applications</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.11.5. Securing ingress traffic</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.11.6. Securing egress traffic</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.12. SECURING ATTACHED STORAGE</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.12.1. Persistent volume plugins</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.12.2. Shared storage</td>\n<td>61</td>\n</tr>\n<tr>\n<td>2.12.3. Block storage</td>\n<td>61</td>\n</tr>\n<tr>\n<td>2.13. MONITORING CLUSTER EVENTS AND LOGS</td>\n<td>62</td>\n</tr>\n<tr>\n<td>2.13.1. Watching cluster events</td>\n<td>62</td>\n</tr>\n<tr>\n<td>2.13.2. Logging</td>\n<td>63</td>\n</tr>\n<tr>\n<td>2.13.3. Audit logs</td>\n<td>63</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. CONFIGURING CERTIFICATES</b></td>\n<td><b>64</b></td>\n</tr>\n<tr>\n<td>3.1. REPLACING THE DEFAULT INGRESS CERTIFICATE</td>\n<td>64</td>\n</tr>\n<tr>\n<td>3.1.1. Understanding the default ingress certificate</td>\n<td>64</td>\n</tr>\n<tr>\n<td>3.1.2. Replacing the default ingress certificate</td>\n<td>64</td>\n</tr>\n<tr>\n<td>3.1.3. Additional resources</td>\n<td>66</td>\n</tr>\n<tr>\n<td>3.2. ADDING API SERVER CERTIFICATES</td>\n<td>66</td>\n</tr>\n<tr>\n<td>3.2.1. Add an API server named certificate</td>\n<td>66</td>\n</tr>\n</table>\n\n<hr/>\n<table>\n<tr>\n<td>3.3. SECURING SERVICE TRAFFIC USING SERVICE SERVING CERTIFICATE SECRETS</td>\n<td>68</td>\n</tr>\n<tr>\n<td> 3.3.1. Understanding service serving certificates</td>\n<td>68</td>\n</tr>\n<tr>\n<td> 3.3.2. Add a service certificate</td>\n<td>69</td>\n</tr>\n<tr>\n<td> 3.3.3. Add the service CA bundle to a config map</td>\n<td>70</td>\n</tr>\n<tr>\n<td> 3.3.4. Add the service CA bundle to an API service</td>\n<td>72</td>\n</tr>\n<tr>\n<td> 3.3.5. Add the service CA bundle to a custom resource definition</td>\n<td>73</td>\n</tr>\n<tr>\n<td> 3.3.6. Add the service CA bundle to a mutating webhook configuration</td>\n<td>74</td>\n</tr>\n<tr>\n<td> 3.3.7. Add the service CA bundle to a validating webhook configuration</td>\n<td>74</td>\n</tr>\n<tr>\n<td> 3.3.8. Manually rotate the generated service certificate</td>\n<td>75</td>\n</tr>\n<tr>\n<td> 3.3.9. Manually rotate the service CA certificate</td>\n<td>76</td>\n</tr>\n<tr>\n<td>3.4. UPDATING THE CA BUNDLE</td>\n<td>77</td>\n</tr>\n<tr>\n<td> 3.4.1. Understanding the CA Bundle certificate</td>\n<td>77</td>\n</tr>\n<tr>\n<td> 3.4.2. Replacing the CA Bundle certificate</td>\n<td>78</td>\n</tr>\n<tr>\n<td> 3.4.3. Additional resources</td>\n<td>78</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. CERTIFICATE TYPES AND DESCRIPTIONS</b> .....</td>\n<td><b>80</b></td>\n</tr>\n<tr>\n<td>4.1. USER-PROVIDED CERTIFICATES FOR THE API SERVER</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.1.1. Purpose</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.1.2. Location</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.1.3. Management</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.1.4. Expiration</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.1.5. Customization</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.1.6. Additional resources</td>\n<td>80</td>\n</tr>\n<tr>\n<td>4.2. PROXY CERTIFICATES</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.2.1. Purpose</td>\n<td>80</td>\n</tr>\n<tr>\n<td> 4.2.1.1. Additional resources</td>\n<td>81</td>\n</tr>\n<tr>\n<td> 4.2.2. Managing proxy certificates during installation</td>\n<td>81</td>\n</tr>\n<tr>\n<td> 4.2.3. Location</td>\n<td>81</td>\n</tr>\n<tr>\n<td> 4.2.4. Expiration</td>\n<td>82</td>\n</tr>\n<tr>\n<td> 4.2.5. Services</td>\n<td>82</td>\n</tr>\n<tr>\n<td> 4.2.6. Management</td>\n<td>82</td>\n</tr>\n<tr>\n<td> 4.2.7. Customization</td>\n<td>82</td>\n</tr>\n<tr>\n<td> 4.2.8. Renewal</td>\n<td>83</td>\n</tr>\n<tr>\n<td>4.3. SERVICE CA CERTIFICATES</td>\n<td>83</td>\n</tr>\n<tr>\n<td> 4.3.1. Purpose</td>\n<td>83</td>\n</tr>\n<tr>\n<td> 4.3.2. Expiration</td>\n<td>83</td>\n</tr>\n<tr>\n<td> 4.3.3. Management</td>\n<td>84</td>\n</tr>\n<tr>\n<td> 4.3.4. Services</td>\n<td>84</td>\n</tr>\n<tr>\n<td> 4.3.5. Additional resources</td>\n<td>85</td>\n</tr>\n<tr>\n<td>4.4. NODE CERTIFICATES</td>\n<td>85</td>\n</tr>\n<tr>\n<td> 4.4.1. Purpose</td>\n<td>85</td>\n</tr>\n<tr>\n<td> 4.4.2. Location</td>\n<td>85</td>\n</tr>\n<tr>\n<td> 4.4.3. Management</td>\n<td>85</td>\n</tr>\n<tr>\n<td> 4.4.4. Expiration</td>\n<td>85</td>\n</tr>\n<tr>\n<td> 4.4.5. Renewal</td>\n<td>85</td>\n</tr>\n<tr>\n<td> 4.4.6. Additional resources</td>\n<td>86</td>\n</tr>\n<tr>\n<td>4.5. BOOTSTRAP CERTIFICATES</td>\n<td>86</td>\n</tr>\n<tr>\n<td> 4.5.1. Purpose</td>\n<td>86</td>\n</tr>\n<tr>\n<td> 4.5.2. Management</td>\n<td>86</td>\n</tr>\n<tr>\n<td> 4.5.3. Expiration</td>\n<td>86</td>\n</tr>\n<tr>\n<td> 4.5.4. Customization</td>\n<td>86</td>\n</tr>\n<tr>\n<td>4.6. ETCD CERTIFICATES</td>\n<td>86</td>\n</tr>\n<tr>\n<td> 4.6.1. Purpose</td>\n<td>86</td>\n</tr>\n</table>\n\n<table>\n<tr><td>4.6.2. Expiration</td><td>87</td></tr>\n<tr><td>4.6.3. Rotating the etcd certificate</td><td>87</td></tr>\n<tr><td>4.6.4. Removing an unused certificate authority from the bundle</td><td>87</td></tr>\n<tr><td>4.6.5. etcd certificate rotation alerts and metrics signer certificates</td><td>87</td></tr>\n<tr><td>4.6.6. Management</td><td>88</td></tr>\n<tr><td>4.6.7. Services</td><td>88</td></tr>\n<tr><td>4.6.8. Additional resources</td><td>88</td></tr>\n<tr><td>4.7. OLM CERTIFICATES</td><td>88</td></tr>\n<tr><td>4.7.1. Management</td><td>88</td></tr>\n<tr><td>4.7.2. Additional resources</td><td>89</td></tr>\n<tr><td>4.8. AGGREGATED API CLIENT CERTIFICATES</td><td>89</td></tr>\n<tr><td>4.8.1. Purpose</td><td>89</td></tr>\n<tr><td>4.8.2. Management</td><td>89</td></tr>\n<tr><td>4.8.3. Expiration</td><td>89</td></tr>\n<tr><td>4.8.4. Customization</td><td>89</td></tr>\n<tr><td>4.9. MACHINE CONFIG OPERATOR CERTIFICATES</td><td>89</td></tr>\n<tr><td>4.9.1. Purpose</td><td>89</td></tr>\n<tr><td>4.9.1.1. Provisioning details</td><td>90</td></tr>\n<tr><td>4.9.1.2. Provisioning chain of trust</td><td>90</td></tr>\n<tr><td>4.9.1.3. Key material inside a cluster</td><td>90</td></tr>\n<tr><td>4.9.2. Management</td><td>91</td></tr>\n<tr><td>4.9.3. Expiration</td><td>91</td></tr>\n<tr><td>4.9.4. Customization</td><td>91</td></tr>\n<tr><td>4.10. USER-PROVIDED CERTIFICATES FOR DEFAULT INGRESS</td><td>91</td></tr>\n<tr><td>4.10.1. Purpose</td><td>91</td></tr>\n<tr><td>4.10.2. Location</td><td>92</td></tr>\n<tr><td>4.10.3. Management</td><td>92</td></tr>\n<tr><td>4.10.4. Expiration</td><td>92</td></tr>\n<tr><td>4.10.5. Services</td><td>92</td></tr>\n<tr><td>4.10.6. Customization</td><td>92</td></tr>\n<tr><td>4.10.7. Additional resources</td><td>92</td></tr>\n<tr><td>4.11. INGRESS CERTIFICATES</td><td>92</td></tr>\n<tr><td>4.11.1. Purpose</td><td>92</td></tr>\n<tr><td>4.11.2. Location</td><td>92</td></tr>\n<tr><td>4.11.3. Workflow</td><td>93</td></tr>\n<tr><td>4.11.4. Expiration</td><td>94</td></tr>\n<tr><td>4.11.5. Services</td><td>95</td></tr>\n<tr><td>4.11.6. Management</td><td>95</td></tr>\n<tr><td>4.11.7. Renewal</td><td>95</td></tr>\n<tr><td>4.12. MONITORING AND OPENSHIFT LOGGING OPERATOR COMPONENT CERTIFICATES</td><td>95</td></tr>\n<tr><td>4.12.1. Expiration</td><td>95</td></tr>\n<tr><td>4.12.2. Management</td><td>95</td></tr>\n<tr><td>4.13. CONTROL PLANE CERTIFICATES</td><td>95</td></tr>\n<tr><td>4.13.1. Location</td><td>95</td></tr>\n<tr><td>4.13.2. Management</td><td>96</td></tr>\n<tr><td><b>CHAPTER 5. COMPLIANCE OPERATOR</b> .....</td><td><b>97</b></td></tr>\n<tr><td>5.1. COMPLIANCE OPERATOR OVERVIEW</td><td>97</td></tr>\n<tr><td>5.1.1. Compliance Operator concepts</td><td>97</td></tr>\n<tr><td>5.1.2. Compliance Operator management</td><td>97</td></tr>\n<tr><td>5.1.3. Compliance Operator scan management</td><td>97</td></tr>\n<tr><td>5.2. COMPLIANCE OPERATOR RELEASE NOTES</td><td>97</td></tr>\n<tr><td>5.2.1. OpenShift Compliance Operator 1.8.2</td><td>98</td></tr>\n</table>\n<hr/><table><tr><td>5.2.1.1. Bug Fixes</td><td>98</td></tr><tr><td>5.2.2. OpenShift Compliance Operator 1.8.1</td><td>98</td></tr><tr><td>5.2.2.1. Bug Fixes</td><td>98</td></tr><tr><td>5.2.3. OpenShift Compliance Operator 1.8.0</td><td>98</td></tr><tr><td>5.2.3.1. New features and enhancements</td><td>98</td></tr><tr><td>5.2.3.2. Bug fixes</td><td>99</td></tr><tr><td>5.2.4. OpenShift Compliance Operator 1.7.1</td><td>101</td></tr><tr><td>5.2.4.1. Bug fixes</td><td>101</td></tr><tr><td>5.2.5. OpenShift Compliance Operator 1.7.0</td><td>101</td></tr><tr><td>5.2.5.1. New features and enhancements</td><td>101</td></tr><tr><td>5.2.5.2. Bug fixes</td><td>102</td></tr><tr><td>5.2.6. OpenShift Compliance Operator 1.6.2</td><td>102</td></tr><tr><td>5.2.7. OpenShift Compliance Operator 1.6.1</td><td>103</td></tr><tr><td>5.2.8. OpenShift Compliance Operator 1.6.0</td><td>103</td></tr><tr><td>5.2.8.1. New features and enhancements</td><td>103</td></tr><tr><td>5.2.8.2. Bug fixes</td><td>103</td></tr><tr><td>5.2.9. OpenShift Compliance Operator 1.5.1</td><td>104</td></tr><tr><td>5.2.10. OpenShift Compliance Operator 1.5.0</td><td>104</td></tr><tr><td>5.2.10.1. New features and enhancements</td><td>104</td></tr><tr><td>5.2.10.2. Bug fixes</td><td>104</td></tr><tr><td>5.2.11. OpenShift Compliance Operator 1.4.1</td><td>104</td></tr><tr><td>5.2.11.1. New features and enhancements</td><td>105</td></tr><tr><td>5.2.11.2. Bug fixes</td><td>105</td></tr><tr><td>5.2.12. OpenShift Compliance Operator 1.4.0</td><td>106</td></tr><tr><td>5.2.12.1. New features and enhancements</td><td>106</td></tr><tr><td>5.2.12.2. Bug fixes</td><td>106</td></tr><tr><td>5.2.13. OpenShift Compliance Operator 1.3.1</td><td>106</td></tr><tr><td>5.2.13.1. New features and enhancements</td><td>107</td></tr><tr><td>5.2.13.2. Known issue</td><td>107</td></tr><tr><td>5.2.14. OpenShift Compliance Operator 1.3.0</td><td>107</td></tr><tr><td>5.2.14.1. New features and enhancements</td><td>107</td></tr><tr><td>5.2.15. OpenShift Compliance Operator 1.2.0</td><td>107</td></tr><tr><td>5.2.15.1. New features and enhancements</td><td>107</td></tr><tr><td>5.2.16. OpenShift Compliance Operator 1.1.0</td><td>108</td></tr><tr><td>5.2.16.1. New features and enhancements</td><td>108</td></tr><tr><td>5.2.16.2. Bug fixes</td><td>108</td></tr><tr><td>5.2.17. OpenShift Compliance Operator 1.0.0</td><td>109</td></tr><tr><td>5.2.17.1. New features and enhancements</td><td>109</td></tr><tr><td>5.2.17.2. Bug fixes</td><td>109</td></tr><tr><td>5.2.18. OpenShift Compliance Operator 0.1.61</td><td>110</td></tr><tr><td>5.2.18.1. New features and enhancements</td><td>110</td></tr><tr><td>5.2.18.2. Bug fixes</td><td>110</td></tr><tr><td>5.2.19. OpenShift Compliance Operator 0.1.59</td><td>111</td></tr><tr><td>5.2.19.1. New features and enhancements</td><td>111</td></tr><tr><td>5.2.19.2. Bug fixes</td><td>111</td></tr><tr><td>5.2.20. OpenShift Compliance Operator 0.1.57</td><td>111</td></tr><tr><td>5.2.20.1. New features and enhancements</td><td>111</td></tr><tr><td>5.2.20.2. Bug fixes</td><td>112</td></tr><tr><td>5.2.20.3. Deprecations</td><td>112</td></tr><tr><td>5.2.21. OpenShift Compliance Operator 0.1.53</td><td>113</td></tr><tr><td>5.2.21.1. Bug fixes</td><td>113</td></tr><tr><td>5.2.21.2. Known issue</td><td>114</td></tr><tr><td>5.2.22. OpenShift Compliance Operator 0.1.52</td><td>114</td></tr></table><hr/><table><tr><td>5.2.22.1. New features and enhancements</td><td>114</td></tr><tr><td>5.2.22.2. Bug fixes</td><td>114</td></tr><tr><td>5.2.22.3. Known issue</td><td>114</td></tr><tr><td>5.2.23. OpenShift Compliance Operator 0.1.49</td><td>115</td></tr><tr><td>5.2.23.1. New features and enhancements</td><td>115</td></tr><tr><td>5.2.23.2. Bug fixes</td><td>115</td></tr><tr><td>5.2.24. OpenShift Compliance Operator 0.1.48</td><td>116</td></tr><tr><td>5.2.24.1. Bug fixes</td><td>116</td></tr><tr><td>5.2.25. OpenShift Compliance Operator 0.1.47</td><td>116</td></tr><tr><td>5.2.25.1. New features and enhancements</td><td>116</td></tr><tr><td>5.2.25.2. Bug fixes</td><td>116</td></tr><tr><td>5.2.26. OpenShift Compliance Operator 0.1.44</td><td>117</td></tr><tr><td>5.2.26.1. New features and enhancements</td><td>117</td></tr><tr><td>5.2.26.2. Templating and variable use</td><td>118</td></tr><tr><td>5.2.26.3. Bug fixes</td><td>118</td></tr><tr><td>5.2.27. Release Notes for Compliance Operator 0.1.39</td><td>119</td></tr><tr><td>5.2.27.1. New features and enhancements</td><td>119</td></tr><tr><td>5.2.28. Additional resources</td><td>119</td></tr><tr><td>5.3. COMPLIANCE OPERATOR SUPPORT</td><td>119</td></tr><tr><td>5.3.1. Compliance Operator lifecycle</td><td>119</td></tr><tr><td>5.3.2. Getting support</td><td>119</td></tr><tr><td>5.3.3. Using the must-gather tool for the Compliance Operator</td><td>119</td></tr><tr><td>5.3.4. Additional resources</td><td>120</td></tr><tr><td>5.4. COMPLIANCE OPERATOR CONCEPTS</td><td>120</td></tr><tr><td>5.4.1. Understanding the Compliance Operator</td><td>120</td></tr><tr><td>5.4.1.1. Compliance Operator profiles</td><td>120</td></tr><tr><td>5.4.1.1.1. Compliance Operator profile types</td><td>124</td></tr><tr><td>5.4.2. Understanding the Custom Resource Definitions</td><td>125</td></tr><tr><td>5.4.2.1. CRDs workflow</td><td>125</td></tr><tr><td>5.4.2.2. Defining the compliance scan requirements</td><td>125</td></tr><tr><td>5.4.2.2.1. ProfileBundle object</td><td>125</td></tr><tr><td>5.4.2.2.2. Profile object</td><td>126</td></tr><tr><td>5.4.2.2.3. Rule object</td><td>127</td></tr><tr><td>5.4.2.2.4. TailoredProfile object</td><td>127</td></tr><tr><td>5.4.2.3. Configuring the compliance scan settings</td><td>129</td></tr><tr><td>5.4.2.3.1. ScanSetting object</td><td>129</td></tr><tr><td>5.4.2.4. Processing the compliance scan requirements with compliance scans settings</td><td>130</td></tr><tr><td>5.4.2.4.1. ScanSettingBinding object</td><td>130</td></tr><tr><td>5.4.2.5. Tracking the compliance scans</td><td>131</td></tr><tr><td>5.4.2.5.1. ComplianceSuite object</td><td>131</td></tr><tr><td>5.4.2.5.2. Advanced ComplianceScan Object</td><td>132</td></tr><tr><td>5.4.2.6. Viewing the compliance results</td><td>134</td></tr><tr><td>5.4.2.6.1. ComplianceCheckResult object</td><td>134</td></tr><tr><td>5.4.2.6.2. ComplianceRemediation object</td><td>135</td></tr><tr><td>5.5. COMPLIANCE OPERATOR MANAGEMENT</td><td>136</td></tr><tr><td>5.5.1. Installing the Compliance Operator</td><td>136</td></tr><tr><td>5.5.1.1. Installing the Compliance Operator through the web console</td><td>136</td></tr><tr><td>5.5.1.2. Installing the Compliance Operator using the CLI</td><td>137</td></tr><tr><td>5.5.1.3. Installing the Compliance Operator on ROSA hosted control planes (HCP)</td><td>139</td></tr><tr><td>5.5.1.4. Installing the Compliance Operator on Hypershift hosted control planes</td><td>141</td></tr><tr><td>5.5.1.5. Additional resources</td><td>142</td></tr><tr><td>5.5.2. Updating the Compliance Operator</td><td>143</td></tr><tr><td>5.5.2.1. Preparing for an Operator update</td><td>143</td></tr></table>\n<hr/>\n<table>\n<tr>\n<td>5.5.2.2. Changing the update channel for an Operator</td>\n<td>143</td>\n</tr>\n<tr>\n<td>5.5.2.3. Manually approving a pending Operator update</td>\n<td>144</td>\n</tr>\n<tr>\n<td>5.5.3. Managing the Compliance Operator</td>\n<td>144</td>\n</tr>\n<tr>\n<td>5.5.3.1. ProfileBundle CR example</td>\n<td>144</td>\n</tr>\n<tr>\n<td>5.5.3.2. Updating security content</td>\n<td>145</td>\n</tr>\n<tr>\n<td>5.5.3.3. Additional resources</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.5.4. Uninstalling the Compliance Operator</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.5.4.1. Uninstalling the OpenShift Compliance Operator from OpenShift Container Platform using the web console</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.5.4.2. Uninstalling the OpenShift Compliance Operator from OpenShift Container Platform using the CLI</td>\n<td>147</td>\n</tr>\n<tr>\n<td>5.6. COMPLIANCE OPERATOR SCAN MANAGEMENT</td>\n<td>148</td>\n</tr>\n<tr>\n<td>5.6.1. Supported compliance profiles</td>\n<td>148</td>\n</tr>\n<tr>\n<td>5.6.1.1. Compliance profiles</td>\n<td>149</td>\n</tr>\n<tr>\n<td>5.6.1.1.1. CIS compliance profiles</td>\n<td>149</td>\n</tr>\n<tr>\n<td>5.6.1.1.2. BSI Profile Support</td>\n<td>150</td>\n</tr>\n<tr>\n<td>5.6.1.1.3. Essential Eight compliance profiles</td>\n<td>151</td>\n</tr>\n<tr>\n<td>5.6.1.1.4. FedRAMP High compliance profiles</td>\n<td>152</td>\n</tr>\n<tr>\n<td>5.6.1.1.5. FedRAMP Moderate compliance profiles</td>\n<td>153</td>\n</tr>\n<tr>\n<td>5.6.1.1.6. NERC-CIP compliance profiles</td>\n<td>155</td>\n</tr>\n<tr>\n<td>5.6.1.1.7. PCI-DSS compliance profiles</td>\n<td>156</td>\n</tr>\n<tr>\n<td>5.6.1.1.8. STIG compliance profiles</td>\n<td>158</td>\n</tr>\n<tr>\n<td>5.6.1.1.9. About extended compliance profiles</td>\n<td>159</td>\n</tr>\n<tr>\n<td>5.6.1.1.10. Compliance Operator profile types</td>\n<td>160</td>\n</tr>\n<tr>\n<td>5.6.2. Compliance Operator scans</td>\n<td>161</td>\n</tr>\n<tr>\n<td>5.6.2.1. Running compliance scans</td>\n<td>161</td>\n</tr>\n<tr>\n<td>5.6.2.2. Setting custom storage size for results</td>\n<td>165</td>\n</tr>\n<tr>\n<td>5.6.2.2.1. Using custom result storage values</td>\n<td>165</td>\n</tr>\n<tr>\n<td>5.6.2.3. Scheduling the result server pod on a worker node</td>\n<td>166</td>\n</tr>\n<tr>\n<td>5.6.2.4. ScanSetting Custom Resource</td>\n<td>167</td>\n</tr>\n<tr>\n<td>5.6.2.5. Configuring the hosted control planes management cluster</td>\n<td>167</td>\n</tr>\n<tr>\n<td>5.6.2.6. Applying resource requests and limits</td>\n<td>169</td>\n</tr>\n<tr>\n<td>5.6.2.7. Scheduling Pods with container resource requests</td>\n<td>169</td>\n</tr>\n<tr>\n<td>5.6.3. Tailoring the Compliance Operator</td>\n<td>171</td>\n</tr>\n<tr>\n<td>5.6.3.1. Creating a new tailored profile</td>\n<td>171</td>\n</tr>\n<tr>\n<td>5.6.3.2. Using tailored profiles to extend existing ProfileBundles</td>\n<td>172</td>\n</tr>\n<tr>\n<td>5.6.4. Retrieving Compliance Operator raw results</td>\n<td>174</td>\n</tr>\n<tr>\n<td>5.6.4.1. Obtaining Compliance Operator raw results from a persistent volume</td>\n<td>174</td>\n</tr>\n<tr>\n<td>5.6.5. Managing Compliance Operator result and remediation</td>\n<td>176</td>\n</tr>\n<tr>\n<td>5.6.5.1. Filters for compliance check results</td>\n<td>176</td>\n</tr>\n<tr>\n<td>5.6.5.2. Reviewing a remediation</td>\n<td>178</td>\n</tr>\n<tr>\n<td>5.6.5.3. Applying remediation when using customized machine config pools</td>\n<td>179</td>\n</tr>\n<tr>\n<td>5.6.5.4. Evaluating KubeletConfig rules against default configuration values</td>\n<td>180</td>\n</tr>\n<tr>\n<td>5.6.5.5. Scanning custom node pools</td>\n<td>181</td>\n</tr>\n<tr>\n<td>5.6.5.6. Remediating KubeletConfig sub pools</td>\n<td>182</td>\n</tr>\n<tr>\n<td>5.6.5.7. Applying a remediation</td>\n<td>182</td>\n</tr>\n<tr>\n<td>5.6.5.8. Remediating a platform check manually</td>\n<td>183</td>\n</tr>\n<tr>\n<td>5.6.5.9. Updating remediations</td>\n<td>184</td>\n</tr>\n<tr>\n<td>5.6.5.10. Unapplying a remediation</td>\n<td>185</td>\n</tr>\n<tr>\n<td>5.6.5.11. Removing a KubeletConfig remediation</td>\n<td>185</td>\n</tr>\n<tr>\n<td>5.6.5.12. Inconsistent ComplianceScan</td>\n<td>187</td>\n</tr>\n<tr>\n<td>5.6.5.13. Additional resources</td>\n<td>188</td>\n</tr>\n<tr>\n<td>5.6.6. Performing advanced Compliance Operator tasks</td>\n<td>188</td>\n</tr>\n</table>\n\n<table>\n<tr><td>5.6.6.1. Using the ComplianceSuite and ComplianceScan objects directly</td><td>188</td></tr>\n<tr><td>5.6.6.2. Setting PriorityClass for ScanSetting scans</td><td>189</td></tr>\n<tr><td>5.6.6.3. Using raw tailored profiles</td><td>190</td></tr>\n<tr><td>5.6.6.4. Performing a rescan</td><td>191</td></tr>\n<tr><td>5.6.6.5. Setting custom storage size for results</td><td>191</td></tr>\n<tr><td> 5.6.6.5.1. Using custom result storage values</td><td>192</td></tr>\n<tr><td>5.6.6.6. Applying remediations generated by suite scans</td><td>192</td></tr>\n<tr><td>5.6.6.7. Automatically update remediations</td><td>192</td></tr>\n<tr><td>5.6.6.8. Creating a custom SCC for the Compliance Operator</td><td>193</td></tr>\n<tr><td>5.6.6.9. Additional resources</td><td>194</td></tr>\n<tr><td>5.6.7. Troubleshooting Compliance Operator scans</td><td>194</td></tr>\n<tr><td> 5.6.7.1. Anatomy of a scan</td><td>195</td></tr>\n<tr><td> 5.6.7.1.1. Compliance sources</td><td>195</td></tr>\n<tr><td> 5.6.7.1.2. The ScanSetting and ScanSettingBinding objects lifecycle and debugging</td><td>196</td></tr>\n<tr><td> 5.6.7.1.3. ComplianceSuite custom resource lifecycle and debugging</td><td>196</td></tr>\n<tr><td> 5.6.7.1.4. ComplianceScan custom resource lifecycle and debugging</td><td>197</td></tr>\n<tr><td> 5.6.7.1.4.1. Pending phase</td><td>197</td></tr>\n<tr><td> 5.6.7.1.4.2. Launching phase</td><td>197</td></tr>\n<tr><td> 5.6.7.1.4.3. Running phase</td><td>198</td></tr>\n<tr><td> 5.6.7.1.4.4. Aggregating phase</td><td>199</td></tr>\n<tr><td> 5.6.7.1.4.5. Done phase</td><td>199</td></tr>\n<tr><td> 5.6.7.1.5. ComplianceRemediation controller lifecycle and debugging</td><td>200</td></tr>\n<tr><td> 5.6.7.1.6. Useful labels</td><td>201</td></tr>\n<tr><td> 5.6.7.2. Increasing Compliance Operator resource limits</td><td>201</td></tr>\n<tr><td> 5.6.7.3. Configuring Operator resource constraints</td><td>202</td></tr>\n<tr><td> 5.6.7.4. Configuring ScanSetting resources</td><td>202</td></tr>\n<tr><td> 5.6.7.5. Configuring ScanSetting timeout</td><td>204</td></tr>\n<tr><td> 5.6.7.6. Getting support</td><td>204</td></tr>\n<tr><td>5.6.8. Using the oc-compliance plugin</td><td>205</td></tr>\n<tr><td> 5.6.8.1. Installing the oc-compliance plugin</td><td>205</td></tr>\n<tr><td> 5.6.8.2. Fetching raw results</td><td>205</td></tr>\n<tr><td> 5.6.8.3. Re-running scans</td><td>206</td></tr>\n<tr><td> 5.6.8.4. Using ScanSettingBinding custom resources</td><td>207</td></tr>\n<tr><td> 5.6.8.5. Printing controls</td><td>208</td></tr>\n<tr><td> 5.6.8.6. Fetching compliance remediation details</td><td>209</td></tr>\n<tr><td> 5.6.8.7. Viewing ComplianceCheckResult object details</td><td>211</td></tr>\n<tr><td><b>CHAPTER 6. FILE INTEGRITY OPERATOR</b></td><td><b>212</b></td></tr>\n<tr><td>6.1. FILE INTEGRITY OPERATOR OVERVIEW</td><td>212</td></tr>\n<tr><td>6.2. FILE INTEGRITY OPERATOR RELEASE NOTES</td><td>212</td></tr>\n<tr><td> 6.2.1. OpenShift File Integrity Operator 1.3.8</td><td>212</td></tr>\n<tr><td> 6.2.1.1. Bug fixes</td><td>212</td></tr>\n<tr><td> 6.2.2. OpenShift File Integrity Operator 1.3.7</td><td>213</td></tr>\n<tr><td> 6.2.3. OpenShift File Integrity Operator 1.3.6</td><td>213</td></tr>\n<tr><td> 6.2.3.1. Bug fixes</td><td>213</td></tr>\n<tr><td> 6.2.4. OpenShift File Integrity Operator 1.3.5</td><td>213</td></tr>\n<tr><td> 6.2.5. OpenShift File Integrity Operator 1.3.4</td><td>213</td></tr>\n<tr><td> 6.2.5.1. Bug fixes</td><td>214</td></tr>\n<tr><td> 6.2.6. OpenShift File Integrity Operator 1.3.3</td><td>214</td></tr>\n<tr><td> 6.2.6.1. New features and enhancements</td><td>214</td></tr>\n<tr><td> 6.2.6.2. Bug fixes</td><td>214</td></tr>\n<tr><td> 6.2.7. OpenShift File Integrity Operator 1.3.2</td><td>214</td></tr>\n<tr><td> 6.2.8. OpenShift File Integrity Operator 1.3.1</td><td>214</td></tr>\n</table>\n<hr/><table><tr><td>6.2.8.1. New features and enhancements</td><td>215</td></tr><tr><td>6.2.8.2. Bug fixes</td><td>215</td></tr><tr><td>6.2.8.3. Known Issues</td><td>215</td></tr><tr><td>6.2.9. OpenShift File Integrity Operator 1.2.1</td><td>215</td></tr><tr><td>6.2.10. OpenShift File Integrity Operator 1.2.0</td><td>215</td></tr><tr><td>6.2.10.1. New features and enhancements</td><td>215</td></tr><tr><td>6.2.11. OpenShift File Integrity Operator 1.0.0</td><td>216</td></tr><tr><td>6.2.12. OpenShift File Integrity Operator 0.1.32</td><td>216</td></tr><tr><td>6.2.12.1. Bug fixes</td><td>216</td></tr><tr><td>6.2.13. OpenShift File Integrity Operator 0.1.30</td><td>216</td></tr><tr><td>6.2.13.1. New features and enhancements</td><td>216</td></tr><tr><td>6.2.13.2. Bug fixes</td><td>216</td></tr><tr><td>6.2.14. OpenShift File Integrity Operator 0.1.24</td><td>216</td></tr><tr><td>6.2.14.1. New features and enhancements</td><td>216</td></tr><tr><td>6.2.14.2. Bug fixes</td><td>217</td></tr><tr><td>6.2.15. OpenShift File Integrity Operator 0.1.22</td><td>217</td></tr><tr><td>6.2.15.1. Bug fixes</td><td>217</td></tr><tr><td>6.2.16. OpenShift File Integrity Operator 0.1.21</td><td>217</td></tr><tr><td>6.2.16.1. New features and enhancements</td><td>217</td></tr><tr><td>6.2.16.2. Bug fixes</td><td>218</td></tr><tr><td>6.2.17. Additional resources</td><td>218</td></tr><tr><td>6.3. FILE INTEGRITY OPERATOR SUPPORT</td><td>218</td></tr><tr><td>6.3.1. File Integrity Operator lifecycle</td><td>218</td></tr><tr><td>6.3.2. Getting support</td><td>218</td></tr><tr><td>6.4. INSTALLING THE FILE INTEGRITY OPERATOR</td><td>218</td></tr><tr><td>6.4.1. Installing the File Integrity Operator using the web console</td><td>218</td></tr><tr><td>6.4.2. Installing the File Integrity Operator using the CLI</td><td>219</td></tr><tr><td>6.4.3. Additional resources</td><td>220</td></tr><tr><td>6.5. UPDATING THE FILE INTEGRITY OPERATOR</td><td>220</td></tr><tr><td>6.5.1. Preparing for an Operator update</td><td>221</td></tr><tr><td>6.5.2. Changing the update channel for an Operator</td><td>221</td></tr><tr><td>6.5.3. Manually approving a pending Operator update</td><td>222</td></tr><tr><td>6.6. UNDERSTANDING THE FILE INTEGRITY OPERATOR</td><td>222</td></tr><tr><td>6.6.1. Creating the FileIntegrity custom resource</td><td>222</td></tr><tr><td>6.6.2. Checking the FileIntegrity custom resource status</td><td>224</td></tr><tr><td>6.6.3. FileIntegrity custom resource phases</td><td>224</td></tr><tr><td>6.6.4. Understanding the FileIntegrityNodeStatuses object</td><td>224</td></tr><tr><td>6.6.5. FileIntegrityNodeStatus CR status types</td><td>225</td></tr><tr><td>6.6.5.1. FileIntegrityNodeStatus CR success example</td><td>226</td></tr><tr><td>6.6.5.2. FileIntegrityNodeStatus CR failure status example</td><td>226</td></tr><tr><td>6.6.6. Understanding events</td><td>228</td></tr><tr><td>6.7. CONFIGURING THE CUSTOM FILE INTEGRITY OPERATOR</td><td>229</td></tr><tr><td>6.7.1. Viewing FileIntegrity object attributes</td><td>229</td></tr><tr><td>6.7.2. Important attributes</td><td>230</td></tr><tr><td>6.7.3. Examine the default configuration</td><td>231</td></tr><tr><td>6.7.4. Understanding the default File Integrity Operator configuration</td><td>231</td></tr><tr><td>6.7.5. Supplying a custom AIDE configuration</td><td>231</td></tr><tr><td>6.7.6. Defining a custom File Integrity Operator configuration</td><td>232</td></tr><tr><td>6.7.7. Changing the custom File Integrity configuration</td><td>233</td></tr><tr><td>6.8. PERFORMING ADVANCED CUSTOM FILE INTEGRITY OPERATOR TASKS</td><td>233</td></tr><tr><td>6.8.1. Reinitializing the database</td><td>233</td></tr><tr><td>6.8.2. Machine config integration</td><td>234</td></tr><tr><td>6.8.3. Exploring the daemon sets</td><td>234</td></tr></table><hr/>\n<table>\n<tr>\n<td>6.9. TROUBLESHOOTING THE FILE INTEGRITY OPERATOR</td>\n<td>235</td>\n</tr>\n<tr>\n<td> 6.9.1. General troubleshooting</td>\n<td>235</td>\n</tr>\n<tr>\n<td> 6.9.2. Checking the AIDE configuration</td>\n<td>235</td>\n</tr>\n<tr>\n<td> 6.9.3. Determining the FileIntegrity object's phase</td>\n<td>235</td>\n</tr>\n<tr>\n<td> 6.9.4. Determining that the daemon set's pods are running on the expected nodes</td>\n<td>235</td>\n</tr>\n<tr>\n<td>6.10. UNINSTALLING THE FILE INTEGRITY OPERATOR</td>\n<td>236</td>\n</tr>\n<tr>\n<td> 6.10.1. Uninstall the File Integrity Operator using the web console</td>\n<td>236</td>\n</tr>\n<tr>\n<td><b>CHAPTER 7. SECURITY PROFILES OPERATOR</b></td>\n<td><b>237</b></td>\n</tr>\n<tr>\n<td> 7.1. SECURITY PROFILES OPERATOR OVERVIEW</td>\n<td>237</td>\n</tr>\n<tr>\n<td> 7.2. SECURITY PROFILES OPERATOR RELEASE NOTES</td>\n<td>237</td>\n</tr>\n<tr>\n<td> 7.2.1. Security Profiles Operator 0.10.0</td>\n<td>237</td>\n</tr>\n<tr>\n<td> 7.2.1.1. Bug fixes</td>\n<td>237</td>\n</tr>\n<tr>\n<td> 7.2.1.2. New features and enhancements</td>\n<td>238</td>\n</tr>\n<tr>\n<td> 7.2.2. Security Profiles Operator 0.9.0</td>\n<td>238</td>\n</tr>\n<tr>\n<td> 7.2.2.1. Bug fixes</td>\n<td>238</td>\n</tr>\n<tr>\n<td> 7.2.3. Security Profiles Operator 0.8.6</td>\n<td>238</td>\n</tr>\n<tr>\n<td> 7.2.4. Security Profiles Operator 0.8.5</td>\n<td>238</td>\n</tr>\n<tr>\n<td> 7.2.4.1. Bug fixes</td>\n<td>239</td>\n</tr>\n<tr>\n<td> 7.2.5. Security Profiles Operator 0.8.4</td>\n<td>239</td>\n</tr>\n<tr>\n<td> 7.2.5.1. New features and enhancements</td>\n<td>239</td>\n</tr>\n<tr>\n<td> 7.2.6. Security Profiles Operator 0.8.2</td>\n<td>239</td>\n</tr>\n<tr>\n<td> 7.2.6.1. Bug fixes</td>\n<td>239</td>\n</tr>\n<tr>\n<td> 7.2.7. Security Profiles Operator 0.8.0</td>\n<td>240</td>\n</tr>\n<tr>\n<td> 7.2.7.1. Bug fixes</td>\n<td>240</td>\n</tr>\n<tr>\n<td> 7.2.8. Security Profiles Operator 0.7.1</td>\n<td>240</td>\n</tr>\n<tr>\n<td> 7.2.8.1. New features and enhancements</td>\n<td>240</td>\n</tr>\n<tr>\n<td> 7.2.8.2. Deprecated and removed features</td>\n<td>240</td>\n</tr>\n<tr>\n<td> 7.2.8.3. Bug fixes</td>\n<td>240</td>\n</tr>\n<tr>\n<td> 7.2.8.4. Known issue</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.2.9. Security Profiles Operator 0.5.2</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.2.9.1. Known issue</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.2.10. Security Profiles Operator 0.5.0</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.2.10.1. Known issue</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.3. SECURITY PROFILES OPERATOR SUPPORT</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.3.1. Security Profiles Operator lifecycle</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.3.2. Getting support</td>\n<td>241</td>\n</tr>\n<tr>\n<td> 7.4. UNDERSTANDING THE SECURITY PROFILES OPERATOR</td>\n<td>242</td>\n</tr>\n<tr>\n<td> 7.4.1. About Security Profiles</td>\n<td>242</td>\n</tr>\n<tr>\n<td> 7.5. ENABLING THE SECURITY PROFILES OPERATOR</td>\n<td>242</td>\n</tr>\n<tr>\n<td> 7.5.1. Installing the Security Profiles Operator</td>\n<td>243</td>\n</tr>\n<tr>\n<td> 7.5.2. Installing the Security Profiles Operator using the CLI</td>\n<td>243</td>\n</tr>\n<tr>\n<td> 7.5.3. Configuring logging verbosity</td>\n<td>245</td>\n</tr>\n<tr>\n<td> 7.6. MANAGING SECCOMP PROFILES</td>\n<td>245</td>\n</tr>\n<tr>\n<td> 7.6.1. Creating seccomp profiles</td>\n<td>245</td>\n</tr>\n<tr>\n<td> 7.6.2. Applying seccomp profiles to a pod</td>\n<td>246</td>\n</tr>\n<tr>\n<td> 7.6.2.1. Binding workloads to profiles with ProfileBindings</td>\n<td>247</td>\n</tr>\n<tr>\n<td> 7.6.3. Recording profiles from workloads</td>\n<td>249</td>\n</tr>\n<tr>\n<td> 7.6.3.1. Merging per-container profile instances</td>\n<td>251</td>\n</tr>\n<tr>\n<td> 7.6.4. Additional resources</td>\n<td>252</td>\n</tr>\n<tr>\n<td> 7.7. MANAGING SELINUX PROFILES</td>\n<td>252</td>\n</tr>\n<tr>\n<td> 7.7.1. Creating SELinux profiles</td>\n<td>252</td>\n</tr>\n<tr>\n<td> 7.7.2. Applying SELinux profiles to a pod</td>\n<td>254</td>\n</tr>\n</table>\n\n<table>\n<tr><td>7.7.2.1. Applying SELinux log policies</td><td>255</td></tr>\n<tr><td>7.7.2.2. Binding workloads to profiles with ProfileBindings</td><td>255</td></tr>\n<tr><td>7.7.2.3. Replicating controllers and SecurityContextConstraints</td><td>257</td></tr>\n<tr><td>7.7.3. Recording profiles from workloads</td><td>258</td></tr>\n<tr><td>7.7.3.1. Merging per-container profile instances</td><td>261</td></tr>\n<tr><td>7.7.3.2. About seLinuxContext: RunAsAny</td><td>262</td></tr>\n<tr><td>7.7.4. Additional resources</td><td>262</td></tr>\n<tr><td>7.8. ADVANCED SECURITY PROFILES OPERATOR TASKS</td><td>262</td></tr>\n<tr><td>7.8.1. Restrict the allowed syscalls in seccomp profiles</td><td>262</td></tr>\n<tr><td>7.8.2. Base syscalls for a container runtime</td><td>263</td></tr>\n<tr><td>7.8.3. Enabling memory optimization in the spod daemon</td><td>263</td></tr>\n<tr><td>7.8.4. Customizing daemon resource requirements</td><td>264</td></tr>\n<tr><td>7.8.5. Setting a custom priority class name for the spod daemon pod</td><td>264</td></tr>\n<tr><td>7.8.6. Using metrics</td><td>264</td></tr>\n<tr><td>7.8.6.1. controller-runtime metrics</td><td>265</td></tr>\n<tr><td>7.8.7. Using the log enricher</td><td>267</td></tr>\n<tr><td>7.8.7.1. Using the log enricher to trace an application</td><td>268</td></tr>\n<tr><td>7.8.8. Configuring webhooks</td><td>269</td></tr>\n<tr><td>7.9. ADVANCED AUDIT LOGGING FRAMEWORK</td><td>270</td></tr>\n<tr><td>7.9.1. Benefits of Advanced Audit Logging Framework</td><td>270</td></tr>\n<tr><td>7.9.2. Performance considerations</td><td>271</td></tr>\n<tr><td>7.9.3. Prerequisites for use of the Advanced Audit Logging Framework</td><td>271</td></tr>\n<tr><td>7.9.4. The Audit JSON log enricher</td><td>272</td></tr>\n<tr><td>7.9.5. Kubernetes API log compared to Advanced Audit Logging output</td><td>272</td></tr>\n<tr><td>7.9.6. Enabling Advanced Audit Logging</td><td>273</td></tr>\n<tr><td>7.9.7. Audit JSON Log Enricher configuration</td><td>274</td></tr>\n<tr><td>7.9.8. Audit log file fine-tuning and rotation</td><td>275</td></tr>\n<tr><td>7.9.9. Advanced Audit Logs for a specific pod</td><td>276</td></tr>\n<tr><td>7.9.10. Monitoring the audit logs</td><td>279</td></tr>\n<tr><td>7.9.11. Auditing node debugging sessions</td><td>280</td></tr>\n<tr><td>7.9.12. Correlate with Kubernetes audit logs</td><td>282</td></tr>\n<tr><td>7.9.13. Audit JSON Log Enricher Output</td><td>283</td></tr>\n<tr><td>7.9.14. Kubernetes API audit log output</td><td>283</td></tr>\n<tr><td>7.9.15. Correlation key</td><td>284</td></tr>\n<tr><td>7.9.16. Correlating with API Server Audit Log</td><td>284</td></tr>\n<tr><td>7.9.17. Using the mutating webhook</td><td>285</td></tr>\n<tr><td>7.9.17.1. The Debug Pod</td><td>285</td></tr>\n<tr><td>7.9.18. Disabling Advanced Audit Logging</td><td>286</td></tr>\n<tr><td>7.9.19. Additional resources</td><td>286</td></tr>\n<tr><td>7.10. TROUBLESHOOTING THE SECURITY PROFILES OPERATOR</td><td>287</td></tr>\n<tr><td>7.10.1. Inspecting seccomp profiles</td><td>287</td></tr>\n<tr><td>7.11. UNINSTALLING THE SECURITY PROFILES OPERATOR</td><td>288</td></tr>\n<tr><td>7.11.1. Uninstall the Security Profiles Operator using the web console</td><td>288</td></tr>\n<tr><td><b>CHAPTER 8. NBDE TANG SERVER OPERATOR</b></td><td><b>289</b></td></tr>\n<tr><td>8.1. NBDE TANG SERVER OPERATOR OVERVIEW</td><td>289</td></tr>\n<tr><td>8.2. NBDE TANG SERVER OPERATOR RELEASE NOTES</td><td>289</td></tr>\n<tr><td>8.3. UNDERSTANDING THE NBDE TANG SERVER OPERATOR</td><td>289</td></tr>\n<tr><td>8.3.1. Additional resources</td><td>290</td></tr>\n<tr><td>8.4. INSTALLING THE NBDE TANG SERVER OPERATOR</td><td>290</td></tr>\n<tr><td>8.4.1. Installing the NBDE Tang Server Operator using the web console</td><td>290</td></tr>\n<tr><td>8.4.2. Installing the NBDE Tang Server Operator using CLI</td><td>291</td></tr>\n<tr><td>8.5. CONFIGURING AND MANAGING TANG SERVERS USING THE NBDE TANG SERVER OPERATOR</td><td>292</td></tr>\n</table>\n\n<table>\n<tr>\n<td>8.5.1. Deploying a Tang server using the NBDE Tang Server Operator</td>\n<td>292</td>\n</tr>\n<tr>\n<td>8.5.2. Rotating keys using the NBDE Tang Server Operator</td>\n<td>298</td>\n</tr>\n<tr>\n<td>8.5.3. Deleting hidden keys with the NBDE Tang Server Operator</td>\n<td>299</td>\n</tr>\n<tr>\n<td>8.6. IDENTIFYING URL OF A TANG SERVER DEPLOYED WITH THE NBDE TANG SERVER OPERATOR</td>\n<td>301</td>\n</tr>\n<tr>\n<td>8.6.1. Identifying URL of the NBDE Tang Server Operator using the web console</td>\n<td>301</td>\n</tr>\n<tr>\n<td>8.6.2. Identifying URL of the NBDE Tang Server Operator using CLI</td>\n<td>303</td>\n</tr>\n<tr>\n<td>8.6.3. Additional resources</td>\n<td>304</td>\n</tr>\n<tr>\n<td><b>CHAPTER 9. UNDERSTANDING SECRETS MANAGEMENT IN OPENSHIFT CONTAINER PLATFORM ..</b></td>\n<td><b>305</b></td>\n</tr>\n<tr>\n<td>9.1. SECRETS MANAGEMENT OPERATORS IN OPENSHIFT CONTAINER PLATFORM</td>\n<td>305</td>\n</tr>\n<tr>\n<td><b>CHAPTER 10. CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT .....</b></td>\n<td><b>306</b></td>\n</tr>\n<tr>\n<td>10.1. CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT OVERVIEW</td>\n<td>306</td>\n</tr>\n<tr>\n<td>10.1.1. About the cert-manager Operator for Red Hat OpenShift</td>\n<td>306</td>\n</tr>\n<tr>\n<td>10.1.2. cert-manager Operator for Red Hat OpenShift issuer providers</td>\n<td>306</td>\n</tr>\n<tr>\n<td>10.1.3. Certificate request methods</td>\n<td>307</td>\n</tr>\n<tr>\n<td>10.1.4. Supported cert-manager Operator for Red Hat OpenShift versions</td>\n<td>307</td>\n</tr>\n<tr>\n<td>10.1.5. About FIPS compliance for cert-manager Operator for Red Hat OpenShift</td>\n<td>307</td>\n</tr>\n<tr>\n<td>10.1.6. Additional resources</td>\n<td>307</td>\n</tr>\n<tr>\n<td>10.2. CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT RELEASE NOTES</td>\n<td>308</td>\n</tr>\n<tr>\n<td>10.2.1. cert-manager Operator for Red Hat OpenShift 1.18.1</td>\n<td>308</td>\n</tr>\n<tr>\n<td>10.2.1.1. New features and enhancements</td>\n<td>308</td>\n</tr>\n<tr>\n<td>10.2.1.2. CVEs</td>\n<td>308</td>\n</tr>\n<tr>\n<td>10.2.2. cert-manager Operator for Red Hat OpenShift 1.18.0</td>\n<td>309</td>\n</tr>\n<tr>\n<td>10.2.2.1. New features and enhancements</td>\n<td>309</td>\n</tr>\n<tr>\n<td>10.2.2.2. Known issues</td>\n<td>309</td>\n</tr>\n<tr>\n<td>10.3. INSTALLING THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>310</td>\n</tr>\n<tr>\n<td>10.3.1. Installing the cert-manager Operator for Red Hat OpenShift</td>\n<td>310</td>\n</tr>\n<tr>\n<td>10.3.1.1. Installing the cert-manager Operator for Red Hat OpenShift by using the web console</td>\n<td>310</td>\n</tr>\n<tr>\n<td>10.3.1.2. Installing the cert-manager Operator for Red Hat OpenShift by using the CLI</td>\n<td>311</td>\n</tr>\n<tr>\n<td>10.3.2. Understanding update channels of the cert-manager Operator for Red Hat OpenShift</td>\n<td>314</td>\n</tr>\n<tr>\n<td>10.3.2.1. stable-v1 channel</td>\n<td>314</td>\n</tr>\n<tr>\n<td>10.3.2.2. stable-v1.y channel</td>\n<td>314</td>\n</tr>\n<tr>\n<td>10.3.3. Additional resources</td>\n<td>315</td>\n</tr>\n<tr>\n<td>10.4. CONFIGURING THE EGRESS PROXY FOR THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>315</td>\n</tr>\n<tr>\n<td>10.4.1. Injecting a custom CA certificate for the cert-manager Operator for Red Hat OpenShift</td>\n<td>315</td>\n</tr>\n<tr>\n<td>10.4.2. Additional resources</td>\n<td>316</td>\n</tr>\n<tr>\n<td>10.5. CUSTOMIZING THE CERT-MANAGER OPERATOR BY USING THE CERTMANAGER CUSTOM RESOURCE</td>\n<td>316</td>\n</tr>\n<tr>\n<td>10.5.1. Explanation of fields in the CertManager custom resource</td>\n<td>318</td>\n</tr>\n<tr>\n<td>10.5.1.1. Common configurable fields in the CertManager CR for the cert-manager components</td>\n<td>318</td>\n</tr>\n<tr>\n<td>10.5.1.2. Overridable arguments for the cert-manager components</td>\n<td>319</td>\n</tr>\n<tr>\n<td>10.5.1.3. Overridable environment variables for the cert-manager controller</td>\n<td>321</td>\n</tr>\n<tr>\n<td>10.5.1.4. Overridable resource parameters for the cert-manager components</td>\n<td>321</td>\n</tr>\n<tr>\n<td>10.5.1.5. Overridable scheduling parameters for the cert-manager components</td>\n<td>321</td>\n</tr>\n<tr>\n<td>10.5.2. Customizing cert-manager by overriding environment variables from the cert-manager Operator API</td>\n<td>322</td>\n</tr>\n<tr>\n<td>10.5.3. Customizing cert-manager by overriding arguments from the cert-manager Operator API</td>\n<td>324</td>\n</tr>\n<tr>\n<td>10.5.4. Deleting a TLS secret automatically upon Certificate removal</td>\n<td>325</td>\n</tr>\n<tr>\n<td>10.5.5. Overriding CPU and memory limits for the cert-manager components</td>\n<td>327</td>\n</tr>\n<tr>\n<td>10.5.6. Configuring scheduling overrides for cert-manager components</td>\n<td>330</td>\n</tr>\n<tr>\n<td>10.6. AUTHENTICATING THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>332</td>\n</tr>\n<tr>\n<td>10.6.1. Authenticating on AWS</td>\n<td>332</td>\n</tr>\n</table>\n\n<hr/>\n<table>\n<tr>\n<td>10.6.2. Authenticating with AWS Security Token Service</td>\n<td>334</td>\n</tr>\n<tr>\n<td>10.6.3. Authenticating on Google Cloud</td>\n<td>336</td>\n</tr>\n<tr>\n<td>10.6.4. Authenticating with Google Cloud Workload Identity</td>\n<td>338</td>\n</tr>\n<tr>\n<td>10.7. CONFIGURING AN ACME ISSUER</td>\n<td>340</td>\n</tr>\n<tr>\n<td>10.7.1. About ACME issuers</td>\n<td>341</td>\n</tr>\n<tr>\n<td> 10.7.1.1. Supported ACME challenges types</td>\n<td>341</td>\n</tr>\n<tr>\n<td> 10.7.1.2. Supported DNS-01 providers</td>\n<td>342</td>\n</tr>\n<tr>\n<td>10.7.2. Configuring an ACME issuer to solve HTTP-01 challenges</td>\n<td>342</td>\n</tr>\n<tr>\n<td>10.7.3. Configuring an ACME issuer by using explicit credentials for AWS Route53</td>\n<td>345</td>\n</tr>\n<tr>\n<td>10.7.4. Configuring an ACME issuer by using ambient credentials on AWS</td>\n<td>347</td>\n</tr>\n<tr>\n<td>10.7.5. Configuring an ACME issuer by using explicit credentials for Google Cloud DNS</td>\n<td>349</td>\n</tr>\n<tr>\n<td>10.7.6. Configuring an ACME issuer by using ambient credentials on Google Cloud</td>\n<td>351</td>\n</tr>\n<tr>\n<td>10.7.7. Configuring an ACME issuer by using explicit credentials for Microsoft Azure DNS</td>\n<td>353</td>\n</tr>\n<tr>\n<td>10.7.8. Additional resources</td>\n<td>356</td>\n</tr>\n<tr>\n<td>10.8. CONFIGURING CERTIFICATES WITH AN ISSUER</td>\n<td>356</td>\n</tr>\n<tr>\n<td>10.8.1. Creating certificates for user workloads</td>\n<td>356</td>\n</tr>\n<tr>\n<td>10.8.2. Creating certificates for the API server</td>\n<td>357</td>\n</tr>\n<tr>\n<td>10.8.3. Creating certificates for the Ingress Controller</td>\n<td>359</td>\n</tr>\n<tr>\n<td>10.8.4. Additional resources</td>\n<td>360</td>\n</tr>\n<tr>\n<td>10.9. SECURING ROUTES WITH THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>361</td>\n</tr>\n<tr>\n<td>10.9.1. Configuring certificates to secure routes in your cluster</td>\n<td>361</td>\n</tr>\n<tr>\n<td>10.9.2. Additional resources</td>\n<td>364</td>\n</tr>\n<tr>\n<td>10.10. INTEGRATING THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT WITH ISTIO-CSR</td>\n<td>364</td>\n</tr>\n<tr>\n<td>10.10.1. Installing the Istio-CSR agent through cert-manager Operator for Red Hat OpenShift</td>\n<td>364</td>\n</tr>\n<tr>\n<td> 10.10.1.1. Creating a root CA issuer for the Istio-CSR agent</td>\n<td>364</td>\n</tr>\n<tr>\n<td> 10.10.1.2. Creating the IstioCSR custom resource</td>\n<td>366</td>\n</tr>\n<tr>\n<td> 10.10.1.3. Setting the log level for the istio-csr component</td>\n<td>368</td>\n</tr>\n<tr>\n<td> 10.10.1.4. Configuring the namespace selector for CA bundle distribution</td>\n<td>369</td>\n</tr>\n<tr>\n<td> 10.10.1.5. Configuring the CA certificate for the Istio server</td>\n<td>370</td>\n</tr>\n<tr>\n<td>10.10.2. Uninstalling the Istio-CSR agent managed by cert-manager Operator for Red Hat OpenShift</td>\n<td>371</td>\n</tr>\n<tr>\n<td>10.11. NETWORK POLICY CONFIGURATION FOR CERT-MANAGER OPERATOR</td>\n<td>372</td>\n</tr>\n<tr>\n<td>10.11.1. Default ingress and egress rules</td>\n<td>373</td>\n</tr>\n<tr>\n<td>10.11.2. Network policy configuration parameters</td>\n<td>373</td>\n</tr>\n<tr>\n<td>10.11.3. Network policy configuration examples</td>\n<td>374</td>\n</tr>\n<tr>\n<td>10.11.4. Verifying the network policy creation</td>\n<td>375</td>\n</tr>\n<tr>\n<td>10.12. MONITORING CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>376</td>\n</tr>\n<tr>\n<td>10.12.1. Enabling user workload monitoring</td>\n<td>376</td>\n</tr>\n<tr>\n<td>10.12.2. Configuring metrics collection for cert-manager Operator for Red Hat OpenShift operands by using a ServiceMonitor</td>\n<td>377</td>\n</tr>\n<tr>\n<td>10.12.3. Querying metrics for the cert-manager Operator for Red Hat OpenShift operands</td>\n<td>379</td>\n</tr>\n<tr>\n<td>10.12.4. Configuring metrics collection for the istio-csr operand</td>\n<td>379</td>\n</tr>\n<tr>\n<td>10.12.5. Querying metrics for the istio-csr operand</td>\n<td>380</td>\n</tr>\n<tr>\n<td>10.13. CONFIGURING LOG LEVELS FOR CERT-MANAGER AND THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>381</td>\n</tr>\n<tr>\n<td>10.13.1. Setting a log level for cert-manager</td>\n<td>381</td>\n</tr>\n<tr>\n<td>10.13.2. Setting a log level for the cert-manager Operator for Red Hat OpenShift</td>\n<td>382</td>\n</tr>\n<tr>\n<td>10.13.3. Additional resources</td>\n<td>383</td>\n</tr>\n<tr>\n<td>10.14. UNINSTALLING THE CERT-MANAGER OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>383</td>\n</tr>\n<tr>\n<td>10.14.1. Uninstalling the cert-manager Operator for Red Hat OpenShift</td>\n<td>383</td>\n</tr>\n<tr>\n<td>10.14.2. Removing cert-manager Operator for Red Hat OpenShift resources</td>\n<td>383</td>\n</tr>\n<tr>\n<td><b>CHAPTER 11. ZERO TRUST WORKLOAD IDENTITY MANAGER</b> .....</td>\n<td><b>386</b></td>\n</tr>\n<tr>\n<td>11.1. ZERO TRUST WORKLOAD IDENTITY MANAGER OVERVIEW</td>\n<td>386</td>\n</tr>\n</table>\n<hr/>\n<table><tr><td>11.1.1. SPIFFE</td><td>386</td></tr><tr><td>11.1.2. SPIRE Server</td><td>386</td></tr><tr><td>11.1.3. SPIRE Agent</td><td>386</td></tr><tr><td>11.1.4. Attestation</td><td>386</td></tr><tr><td>11.2. ZERO TRUST WORKLOAD IDENTITY MANAGER COMPONENTS</td><td>387</td></tr><tr><td>11.2.1. SPIFFE CSI Driver</td><td>387</td></tr><tr><td>11.2.2. SPIRE OpenID Connect Discovery Provider</td><td>387</td></tr><tr><td>11.2.3. SPIRE Controller Manager</td><td>387</td></tr><tr><td>11.2.4. SPIRE Server and Agent telemetry</td><td>387</td></tr><tr><td>11.2.5. About the Zero Trust Workload Identity Manager workflow</td><td>388</td></tr><tr><td>11.3. ZERO TRUST WORKLOAD IDENTITY MANAGER RELEASE NOTES</td><td>389</td></tr><tr><td>11.3.1. Zero Trust Workload Identity Manager 1.0.0 (General Availability)</td><td>389</td></tr><tr><td>11.3.1.1. New features and enhancements</td><td>389</td></tr><tr><td>11.3.1.2. Status and observability improvements</td><td>392</td></tr><tr><td>11.3.1.3. Fixed issues</td><td>392</td></tr><tr><td>11.3.2. Zero Trust Workload Identity Manager 0.2.0 (Technology Preview)</td><td>393</td></tr><tr><td>11.3.2.1. New features and enhancements</td><td>394</td></tr><tr><td>11.3.2.2. Fixed issues</td><td>394</td></tr><tr><td>11.3.3. Zero Trust Workload Identity Manager 0.1.0 (Technology Preview)</td><td>395</td></tr><tr><td>11.4. INSTALLING THE ZERO TRUST WORKLOAD IDENTITY MANAGER</td><td>396</td></tr><tr><td>11.4.1. Installing the Zero Trust Workload Identity Manager by using the web console</td><td>396</td></tr><tr><td>11.4.2. Installing the Zero Trust Workload Identity Manager by using the CLI</td><td>397</td></tr><tr><td>11.5. DEPLOYING ZERO TRUST WORKLOAD IDENTITY MANAGER OPERANDS</td><td>399</td></tr><tr><td>11.5.1. About the ZeroTrustWorkloadIdentityManager custom resource</td><td>399</td></tr><tr><td>11.5.2. Deploying the SPIRE Server</td><td>400</td></tr><tr><td>11.5.3. Deploying the SPIRE Agent</td><td>403</td></tr><tr><td>11.5.4. Deploying the SPIFFE Container Storage Interface driver</td><td>405</td></tr><tr><td>11.5.5. Deploying the SPIRE OpenID Connect Discovery Provider</td><td>407</td></tr><tr><td>11.5.6. Verify the health of the operands</td><td>409</td></tr><tr><td>11.6. CONFIGURING THE EGRESS PROXY FOR THE ZERO TRUST WORKLOAD IDENTITY MANAGER</td><td>409</td></tr><tr><td>11.6.1. Injecting a custom CA certificate for the Zero Trust Workload Identity Manager</td><td>410</td></tr><tr><td>11.6.2. Additional resources</td><td>412</td></tr><tr><td>11.7. ZERO TRUST WORKLOAD IDENTITY MANAGER OIDC FEDERATION</td><td>412</td></tr><tr><td>11.7.1. About the Entra ID OpenID Connect</td><td>412</td></tr><tr><td>11.7.1.1. Configuring the external certificate for the managed OIDC discovery provider route</td><td>412</td></tr><tr><td>11.7.1.2. Disabling a managed route</td><td>414</td></tr><tr><td>11.7.1.3. Using Entra ID with Microsoft Azure</td><td>414</td></tr><tr><td>11.7.1.4. Configuring Azure blob storage</td><td>415</td></tr><tr><td>11.7.1.5. Configuring an Azure user managed identity</td><td>416</td></tr><tr><td>11.7.1.6. Creating the demonstration application</td><td>416</td></tr><tr><td>11.7.1.7. Deploying the workload application</td><td>417</td></tr><tr><td>11.7.1.8. Configuring Azure with the SPIFFE identity federation</td><td>419</td></tr><tr><td>11.7.1.9. Verifying that the application workload can access the content in the Azure Blob Storage</td><td>419</td></tr><tr><td>11.7.2. About Vault OpenID Connect</td><td>420</td></tr><tr><td>11.7.2.1. Installing Vault</td><td>421</td></tr><tr><td>11.7.2.2. Initializing and unsealing Vault</td><td>422</td></tr><tr><td>11.7.2.3. Enabling the key-value secrets engine and store a test secret</td><td>423</td></tr><tr><td>11.7.2.4. Configuring JSON Web Token authentication with SPIRE</td><td>424</td></tr><tr><td>11.7.2.5. Deploying a demonstration application</td><td>426</td></tr><tr><td>11.7.2.6. Authenticating and retrieving the secret</td><td>427</td></tr><tr><td>11.8. ZERO TRUST WORKLOAD IDENTITY MANAGER SPIRE FEDERATION</td><td>427</td></tr><tr><td>11.8.1. Understanding bundle endpoint profiles</td><td>428</td></tr><tr><td>11.8.2. Federation configuration examples</td><td>429</td></tr></table>\n<hr/>\n<table>\n<tr>\n<td>11.8.3. Configuring SPIRE federation with the https_spiffe profile</td>\n<td>431</td>\n</tr>\n<tr>\n<td>11.8.4. Using SPIRE federation with Automatic Certificate Management Environment protocol</td>\n<td>435</td>\n</tr>\n<tr>\n<td>11.8.5. Using SPIRE federation with manual certificate management</td>\n<td>440</td>\n</tr>\n<tr>\n<td>11.8.6. Federation configuration field reference</td>\n<td>448</td>\n</tr>\n<tr>\n<td>11.9. ENABLING CREATE-ONLY MODE FOR THE ZERO TRUST WORKLOAD IDENTITY MANAGER</td>\n<td>452</td>\n</tr>\n<tr>\n<td>11.9.1. Pausing Operator reconciliation</td>\n<td>452</td>\n</tr>\n<tr>\n<td>11.9.2. Resuming Operator reconciliation</td>\n<td>453</td>\n</tr>\n<tr>\n<td>11.10. MONITORING ZERO TRUST WORKLOAD IDENTITY MANAGER</td>\n<td>453</td>\n</tr>\n<tr>\n<td>11.10.1. Enabling user workload monitoring</td>\n<td>454</td>\n</tr>\n<tr>\n<td>11.10.2. Configuring metrics collection for SPIRE Server by using a ServiceMonitor</td>\n<td>455</td>\n</tr>\n<tr>\n<td>11.10.3. Configuring metrics collection for SPIRE Agent by using a Service Monitor</td>\n<td>456</td>\n</tr>\n<tr>\n<td>11.10.4. Configuring metrics collection for the Operator by using a ServiceMonitor</td>\n<td>457</td>\n</tr>\n<tr>\n<td>11.10.5. Querying metrics for the Zero Trust Workload Identity Manager</td>\n<td>460</td>\n</tr>\n<tr>\n<td>11.10.6. Zero Trust Workload Identity Manager monitoring available metrics</td>\n<td>461</td>\n</tr>\n<tr>\n<td>11.11. UNINSTALLING THE ZERO TRUST WORKLOAD IDENTITY MANAGER</td>\n<td>462</td>\n</tr>\n<tr>\n<td>11.11.1. Uninstalling the Zero Trust Workload Identity Manager</td>\n<td>462</td>\n</tr>\n<tr>\n<td>11.11.2. Uninstalling Zero Trust Workload Identity Manager resources by using the CLI</td>\n<td>463</td>\n</tr>\n<tr>\n<td><b>CHAPTER 12. EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</b> .....</td>\n<td><b>465</b></td>\n</tr>\n<tr>\n<td>12.1. EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT OVERVIEW</td>\n<td>465</td>\n</tr>\n<tr>\n<td>12.1.1. About the External Secrets Operator for Red Hat OpenShift</td>\n<td>465</td>\n</tr>\n<tr>\n<td>12.1.2. External secrets providers for the External Secrets Operator for Red Hat OpenShift</td>\n<td>465</td>\n</tr>\n<tr>\n<td>12.1.3. About FIPS compliance for External Secrets Operator for Red Hat OpenShift</td>\n<td>466</td>\n</tr>\n<tr>\n<td>12.1.4. Security considerations</td>\n<td>466</td>\n</tr>\n<tr>\n<td>12.1.5. Additional resources</td>\n<td>466</td>\n</tr>\n<tr>\n<td>12.2. EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT RELEASE NOTES</td>\n<td>467</td>\n</tr>\n<tr>\n<td>12.2.1. Release notes for External Secrets Operator for Red Hat OpenShift 1.1.0 (General Availability)</td>\n<td>467</td>\n</tr>\n<tr>\n<td>12.2.1.1. New features and enhancements</td>\n<td>467</td>\n</tr>\n<tr>\n<td>12.2.2. Release notes for External Secrets Operator for Red Hat OpenShift 1.0.0 (General Availability)</td>\n<td>467</td>\n</tr>\n<tr>\n<td>12.2.2.1. Fixed issues</td>\n<td>468</td>\n</tr>\n<tr>\n<td>12.2.2.2. New features and enhancements</td>\n<td>468</td>\n</tr>\n<tr>\n<td>12.2.3. Release notes for External Secrets Operator for Red Hat OpenShift 0.1.0 (Technology Preview)</td>\n<td>469</td>\n</tr>\n<tr>\n<td>12.2.3.1. New features and enhancements</td>\n<td>469</td>\n</tr>\n<tr>\n<td>12.3. INSTALLING THE EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>469</td>\n</tr>\n<tr>\n<td>12.3.1. Limitations of External Secrets Operator for Red Hat OpenShift</td>\n<td>469</td>\n</tr>\n<tr>\n<td>12.3.2. Installing the External Secrets Operator for Red Hat OpenShift by using the web console</td>\n<td>469</td>\n</tr>\n<tr>\n<td>12.3.3. Installing the External Secrets Operator for Red Hat OpenShift by using the CLI</td>\n<td>471</td>\n</tr>\n<tr>\n<td>12.3.4. Additional resources</td>\n<td>472</td>\n</tr>\n<tr>\n<td>12.3.5. Installing the External Secrets operand by using the CLI</td>\n<td>472</td>\n</tr>\n<tr>\n<td>12.3.6. Understanding update channels of the External Secrets Operator for Red Hat OpenShift</td>\n<td>474</td>\n</tr>\n<tr>\n<td>12.3.6.1. About the External Secrets Operator for Red Hat OpenShift stable-v1 channel</td>\n<td>474</td>\n</tr>\n<tr>\n<td>12.3.6.2. About the External Secrets Operator for Red Hat OpenShift stable-v1.y channel</td>\n<td>474</td>\n</tr>\n<tr>\n<td>12.3.7. Additional resources</td>\n<td>475</td>\n</tr>\n<tr>\n<td>12.4. CONFIGURING NETWORK POLICY FOR THE OPERAND</td>\n<td>475</td>\n</tr>\n<tr>\n<td>12.4.1. Adding a custom network policy to allow egress to all external providers</td>\n<td>475</td>\n</tr>\n<tr>\n<td>12.4.2. Adding a custom network policy to allow egress to a specific provider</td>\n<td>476</td>\n</tr>\n<tr>\n<td>12.4.3. Default ingress and egress rules</td>\n<td>477</td>\n</tr>\n<tr>\n<td>12.5. ABOUT THE EGRESS PROXY FOR THE EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>477</td>\n</tr>\n<tr>\n<td>12.5.1. Configuring the egress proxy for the External Secrets Operator for Red Hat OpenShift</td>\n<td>477</td>\n</tr>\n<tr>\n<td>12.5.2. Additional resources</td>\n<td>479</td>\n</tr>\n<tr>\n<td>12.6. MONITORING THE EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</td>\n<td>479</td>\n</tr>\n<tr>\n<td>12.6.1. Enabling user workload monitoring</td>\n<td>479</td>\n</tr>\n</table>\n<table><tr><td>12.6.2. Configuring metrics collection for External Secrets Operator for Red Hat OpenShift by using a ServiceMonitor</td><td>480</td></tr><tr><td>12.6.3. Querying metrics for the External Secrets Operator for Red Hat OpenShift</td><td>483</td></tr><tr><td>12.6.4. Configuring metrics collection for External Secrets Operator for Red Hat OpenShift operands by using a ServiceMonitor</td><td>484</td></tr><tr><td>12.6.5. Querying metrics for the external-secrets operand</td><td>486</td></tr><tr><td>12.7. CUSTOMIZING THE EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</td><td>486</td></tr><tr><td>12.7.1. Setting a log level for the External Secrets Operator for Red Hat OpenShift</td><td>487</td></tr><tr><td>12.7.2. Setting a log level for the External Secrets Operator for Red Hat OpenShift operand</td><td>488</td></tr><tr><td>12.7.3. Configuring cert-manager for the external-secrets certificate requirements</td><td>489</td></tr><tr><td>12.7.4. Configuring the bitwardenSecretManagerProvider plugin</td><td>490</td></tr><tr><td>12.7.5. Adding custom annotations to external-secrets resources</td><td>491</td></tr><tr><td>12.7.6. Configuring the revisionHistoryLimit for external-secrets components</td><td>493</td></tr><tr><td>12.7.7. Setting custom environment variables for external-secrets components</td><td>494</td></tr><tr><td>12.8. UNINSTALLING THE EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</td><td>495</td></tr><tr><td>12.8.1. Uninstalling the External Secrets Operator for Red Hat OpenShift using the web console</td><td>495</td></tr><tr><td>12.8.2. Removing External Secrets Operator for Red Hat OpenShift resources by using the web console</td><td>496</td></tr><tr><td>12.8.3. Removing External Secrets Operator for Red Hat OpenShift resources by using the CLI</td><td>497</td></tr><tr><td>12.9. EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT APIS</td><td>498</td></tr><tr><td>12.9.1. externalSecretsManagerList</td><td>498</td></tr><tr><td>12.9.2. externalSecretsManager</td><td>499</td></tr><tr><td>12.9.3. externalSecretsConfigList</td><td>500</td></tr><tr><td>12.9.4. externalSecretsConfig</td><td>500</td></tr><tr><td>12.9.5. Listing fields in External Secrets Operator for Red Hat OpenShift APIs</td><td>501</td></tr><tr><td>12.9.6. externalSecretsManagerSpec</td><td>501</td></tr><tr><td>12.9.7. externalSecretsManagerStatus</td><td>502</td></tr><tr><td>12.9.8. externalSecretsConfigSpec</td><td>502</td></tr><tr><td>12.9.9. externalSecretsConfigStatus</td><td>503</td></tr><tr><td>12.9.10. globalConfig</td><td>503</td></tr><tr><td>12.9.11. controllerConfig</td><td>505</td></tr><tr><td>12.9.12. controllerStatus</td><td>506</td></tr><tr><td>12.9.13. applicationConfig</td><td>507</td></tr><tr><td>12.9.14. bitwardenSecretManagerProvider</td><td>509</td></tr><tr><td>12.9.15. webhookConfig</td><td>510</td></tr><tr><td>12.9.16. certManagerConfig</td><td>511</td></tr><tr><td>12.9.17. certProvidersConfig</td><td>513</td></tr><tr><td>12.9.18. objectReference</td><td>513</td></tr><tr><td>12.9.19. secretReference</td><td>514</td></tr><tr><td>12.9.20. condition</td><td>514</td></tr><tr><td>12.9.21. conditionalStatus</td><td>514</td></tr><tr><td>12.9.22. mode</td><td>515</td></tr><tr><td>12.9.23. pluginsConfig</td><td>515</td></tr><tr><td>12.9.24. proxyConfig</td><td>515</td></tr><tr><td>12.9.25. componentConfig</td><td>516</td></tr><tr><td>12.9.26. deploymentConfig</td><td>517</td></tr><tr><td>12.10. MIGRATING FROM THE COMMUNITY EXTERNAL SECRETS OPERATOR TO THE EXTERNAL SECRETS OPERATOR FOR RED HAT OPENSHIFT</td><td>518</td></tr><tr><td>12.10.1. Deleting the community External Secrets Operator</td><td>518</td></tr><tr><td>12.10.2. Uninstalling the community External Secrets Operator</td><td>519</td></tr><tr><td>12.10.2.1. Uninstalling a helm installed community External Secrets Operator</td><td>519</td></tr><tr><td>12.10.2.2. Uninstalling an Operator Lifecycle Manager installed community External Secrets Operator</td><td>520</td></tr><tr><td>12.10.2.3. Uninstalling a raw manifest installed community External Secrets Operator</td><td>520</td></tr><tr><td>12.10.3. Installing the External Secrets Operator for Red Hat OpenShift</td><td>521</td></tr></table>\n<hr/>\n<table>\n<tr>\n<td>12.10.4. Creating the ExternalSecretsConfig Operator</td>\n<td>521</td>\n</tr>\n<tr>\n<td><b>CHAPTER 13. VIEWING AUDIT LOGS</b> .....</td>\n<td><b>524</b></td>\n</tr>\n<tr>\n<td>13.1. ABOUT THE API AUDIT LOG</td>\n<td>524</td>\n</tr>\n<tr>\n<td>13.2. VIEWING THE AUDIT LOGS</td>\n<td>525</td>\n</tr>\n<tr>\n<td>13.3. FILTERING AUDIT LOGS</td>\n<td>529</td>\n</tr>\n<tr>\n<td>13.4. GATHERING AUDIT LOGS</td>\n<td>530</td>\n</tr>\n<tr>\n<td>13.5. ADDITIONAL RESOURCES</td>\n<td>530</td>\n</tr>\n<tr>\n<td><b>CHAPTER 14. CONFIGURING THE AUDIT LOG POLICY</b> .....</td>\n<td><b>531</b></td>\n</tr>\n<tr>\n<td>14.1. ABOUT AUDIT LOG POLICY PROFILES</td>\n<td>531</td>\n</tr>\n<tr>\n<td>14.2. CONFIGURING THE AUDIT LOG POLICY</td>\n<td>532</td>\n</tr>\n<tr>\n<td>14.3. CONFIGURING THE AUDIT LOG POLICY WITH CUSTOM RULES</td>\n<td>533</td>\n</tr>\n<tr>\n<td>14.4. DISABLING AUDIT LOGGING</td>\n<td>534</td>\n</tr>\n<tr>\n<td><b>CHAPTER 15. CONFIGURING TLS SECURITY PROFILES</b> .....</td>\n<td><b>537</b></td>\n</tr>\n<tr>\n<td>15.1. UNDERSTANDING TLS SECURITY PROFILES</td>\n<td>537</td>\n</tr>\n<tr>\n<td>15.2. VIEWING TLS SECURITY PROFILE DETAILS</td>\n<td>538</td>\n</tr>\n<tr>\n<td>15.3. CONFIGURING THE TLS SECURITY PROFILE FOR THE INGRESS CONTROLLER</td>\n<td>540</td>\n</tr>\n<tr>\n<td>15.4. CONFIGURING THE TLS SECURITY PROFILE FOR THE CONTROL PLANE</td>\n<td>542</td>\n</tr>\n<tr>\n<td>15.5. CONFIGURING THE TLS SECURITY PROFILE FOR THE KUBELET</td>\n<td>545</td>\n</tr>\n<tr>\n<td><b>CHAPTER 16. CONFIGURING SECCOMP PROFILES</b> .....</td>\n<td><b>548</b></td>\n</tr>\n<tr>\n<td>16.1. VERIFYING THE DEFAULT SECCOMP PROFILE APPLIED TO A POD</td>\n<td>548</td>\n</tr>\n<tr>\n<td>16.1.1. Upgraded cluster</td>\n<td>549</td>\n</tr>\n<tr>\n<td>16.1.2. Newly installed cluster</td>\n<td>549</td>\n</tr>\n<tr>\n<td>16.2. CONFIGURING A CUSTOM SECCOMP PROFILE</td>\n<td>550</td>\n</tr>\n<tr>\n<td>16.2.1. Creating seccomp profiles</td>\n<td>550</td>\n</tr>\n<tr>\n<td>16.2.2. Setting up the custom seccomp profile</td>\n<td>551</td>\n</tr>\n<tr>\n<td>16.2.3. Applying the custom seccomp profile to the workload</td>\n<td>551</td>\n</tr>\n<tr>\n<td>16.3. ADDITIONAL RESOURCES</td>\n<td>552</td>\n</tr>\n<tr>\n<td><b>CHAPTER 17. ALLOWING JAVASCRIPT-BASED ACCESS TO THE API SERVER FROM ADDITIONAL HOSTS</b> .</td>\n<td><b>553</b></td>\n</tr>\n<tr>\n<td>17.1. ALLOWING JAVASCRIPT-BASED ACCESS TO THE API SERVER FROM ADDITIONAL HOSTS</td>\n<td>553</td>\n</tr>\n<tr>\n<td><b>CHAPTER 18. SCANNING PODS FOR VULNERABILITIES</b> .....</td>\n<td><b>555</b></td>\n</tr>\n<tr>\n<td>18.1. INSTALLING THE RED HAT QUAY CONTAINER SECURITY OPERATOR</td>\n<td>555</td>\n</tr>\n<tr>\n<td>18.2. USING THE RED HAT QUAY CONTAINER SECURITY OPERATOR</td>\n<td>557</td>\n</tr>\n<tr>\n<td>18.3. QUERYING IMAGE VULNERABILITIES FROM THE CLI</td>\n<td>557</td>\n</tr>\n<tr>\n<td>18.4. UNINSTALLING THE RED HAT QUAY CONTAINER SECURITY OPERATOR</td>\n<td>558</td>\n</tr>\n<tr>\n<td><b>CHAPTER 19. NETWORK-BOUND DISK ENCRYPTION (NBDE)</b> .....</td>\n<td><b>560</b></td>\n</tr>\n<tr>\n<td>19.1. ABOUT DISK ENCRYPTION TECHNOLOGY</td>\n<td>560</td>\n</tr>\n<tr>\n<td>19.1.1. Disk encryption technology comparison</td>\n<td>560</td>\n</tr>\n<tr>\n<td>19.1.1.1. Key escrow</td>\n<td>560</td>\n</tr>\n<tr>\n<td>19.1.1.2. TPM encryption</td>\n<td>560</td>\n</tr>\n<tr>\n<td>19.1.1.3. Network-Bound Disk Encryption (NBDE)</td>\n<td>561</td>\n</tr>\n<tr>\n<td>19.1.1.4. Secret sharing encryption</td>\n<td>562</td>\n</tr>\n<tr>\n<td>19.1.2. Tang server disk encryption</td>\n<td>562</td>\n</tr>\n<tr>\n<td>19.1.3. Tang server location planning</td>\n<td>563</td>\n</tr>\n<tr>\n<td>19.1.4. Tang server sizing requirements</td>\n<td>564</td>\n</tr>\n<tr>\n<td>19.1.5. Logging considerations</td>\n<td>565</td>\n</tr>\n<tr>\n<td>19.2. TANG SERVER INSTALLATION CONSIDERATIONS</td>\n<td>565</td>\n</tr>\n<tr>\n<td>19.2.1. Installation scenarios</td>\n<td>565</td>\n</tr>\n</table>\n<table><tr><td>19.2.2. Installing a Tang server</td><td>566</td></tr><tr><td> 19.2.2.1. Compute requirements</td><td>566</td></tr><tr><td> 19.2.2.2. Automatic start at boot</td><td>566</td></tr><tr><td> 19.2.2.3. HTTP versus HTTPS</td><td>566</td></tr><tr><td>19.3. TANG SERVER ENCRYPTION KEY MANAGEMENT</td><td>567</td></tr><tr><td> 19.3.1. Backing up keys for a Tang server</td><td>567</td></tr><tr><td> 19.3.2. Recovering keys for a Tang server</td><td>567</td></tr><tr><td> 19.3.3. Rekeying Tang servers</td><td>567</td></tr><tr><td> 19.3.3.1. Generating a new Tang server key</td><td>568</td></tr><tr><td> 19.3.3.2. Rekeying all NBDE nodes</td><td>570</td></tr><tr><td> 19.3.3.3. Troubleshooting temporary rekeying errors for Tang servers</td><td>573</td></tr><tr><td> 19.3.3.4. Troubleshooting permanent rekeying errors for Tang servers</td><td>573</td></tr><tr><td> 19.3.4. Deleting old Tang server keys</td><td>575</td></tr><tr><td>19.4. DISASTER RECOVERY CONSIDERATIONS</td><td>576</td></tr><tr><td> 19.4.1. Loss of a client machine</td><td>576</td></tr><tr><td> 19.4.2. Planning for a loss of client network connectivity</td><td>576</td></tr><tr><td> 19.4.3. Unexpected loss of network connectivity</td><td>577</td></tr><tr><td> 19.4.4. Recovering network connectivity manually</td><td>577</td></tr><tr><td> 19.4.5. Emergency recovery of network connectivity</td><td>578</td></tr><tr><td> 19.4.6. Loss of a network segment</td><td>578</td></tr><tr><td> 19.4.7. Loss of a Tang server</td><td>578</td></tr><tr><td> 19.4.8. Rekeying compromised key material</td><td>579</td></tr></table><h1>CHAPTER 1. OPENSHIFT CONTAINER PLATFORM SECURITY AND COMPLIANCE</h1><h2>1.1. SECURITY OVERVIEW</h2><p>It is important to understand how to properly secure various aspects of your OpenShift Container Platform cluster.</p><h3>1.1.1. Container security</h3><p>A good starting point to understanding OpenShift Container Platform security is to review the concepts in <a href=\"#\">Understanding container security</a>. This and subsequent sections provide a high-level walkthrough of the container security measures available in OpenShift Container Platform, including solutions for the host layer, the container and orchestration layer, and the build and application layer. These sections also include information on the following topics:</p><ul><li>• Why container security is important and how it compares with existing security standards.</li><li>• Which container security measures are provided by the host (RHCOS and RHEL) layer and which are provided by OpenShift Container Platform.</li><li>• How to evaluate your container content and sources for vulnerabilities.</li><li>• How to design your build and deployment process to proactively check container content.</li><li>• How to control access to containers through authentication and authorization.</li><li>• How networking and attached storage are secured in OpenShift Container Platform.</li><li>• Containerized solutions for API management and SSO.</li></ul><h3>1.1.2. Auditing</h3><p>OpenShift Container Platform auditing provides a security-relevant chronological set of records documenting the sequence of activities that have affected the system by individual users, administrators, or other components of the system. Administrators can <a href=\"#\">configure the audit log policy</a> and <a href=\"#\">view audit logs</a>.</p><h3>1.1.3. Certificates</h3><p>Certificates are used by various components to validate access to the cluster. Administrators can <a href=\"#\">replace the default ingress certificate</a>, <a href=\"#\">add API server certificates</a>, or <a href=\"#\">add a service certificate</a>.</p><p>You can also review more details about the types of certificates used by the cluster:</p><ul><li>• <a href=\"#\">User-provided certificates for the API server</a></li><li>• <a href=\"#\">Proxy certificates</a></li><li>• <a href=\"#\">Service CA certificates</a></li><li>• <a href=\"#\">Node certificates</a></li><li>• <a href=\"#\">Bootstrap certificates</a></li></ul><ul><li>• <a href=\"#\">etcd certificates</a></li><li>• <a href=\"#\">OLM certificates</a></li><li>• <a href=\"#\">Aggregated API client certificates</a></li><li>• <a href=\"#\">Machine Config Operator certificates</a></li><li>• <a href=\"#\">User-provided certificates for default ingress</a></li><li>• <a href=\"#\">Ingress certificates</a></li><li>• <a href=\"#\">Monitoring and cluster logging Operator component certificates</a></li><li>• <a href=\"#\">Control plane certificates</a></li></ul><h3>1.1.4. Encrypting data</h3><p>You can <a href=\"#\">enable etcd encryption</a> for your cluster to provide an additional layer of data security. For example, it can help protect the loss of sensitive data if an etcd backup is exposed to the incorrect parties.</p><h3>1.1.5. Vulnerability scanning</h3><p>Administrators can use the Red Hat Quay Container Security Operator to run <a href=\"#\">vulnerability scans</a> and review information about detected vulnerabilities.</p><h2>1.2. COMPLIANCE OVERVIEW</h2><p>For many OpenShift Container Platform customers, regulatory readiness, or compliance, on some level is required before any systems can be put into production. That regulatory readiness can be imposed by national standards, industry standards, or the organization's corporate governance framework.</p><h3>1.2.1. Compliance checking</h3><p>Administrators can use the <a href=\"#\">Compliance Operator</a> to run compliance scans and recommend remediations for any issues found. The <a href=\"#\">oc-compliance plugin</a> is an OpenShift CLI (<b>oc</b>) plugin that provides a set of utilities to easily interact with the Compliance Operator.</p><h3>1.2.2. File integrity checking</h3><p>Administrators can use the <a href=\"#\">File Integrity Operator</a> to continually run file integrity checks on cluster nodes and provide a log of files that have been modified.</p><h2>1.3. ADDITIONAL RESOURCES</h2><ul><li>• <a href=\"#\">Understanding authentication</a></li><li>• <a href=\"#\">Configuring the internal OAuth server</a></li><li>• <a href=\"#\">Understanding identity provider configuration</a></li><li>• <a href=\"#\">Using RBAC to define and apply permissions</a></li></ul><ul><li>● <a href=\"#\">Managing security context constraints</a></li></ul><h2>CHAPTER 2. CONTAINER SECURITY</h2><h3>2.1. UNDERSTANDING CONTAINER SECURITY</h3><p>Securing a containerized application relies on multiple levels of security:</p><ul><li>• Container security begins with a trusted base container image and continues through the container build process as it moves through your CI/CD pipeline.</li></ul><h4>IMPORTANT</h4><p>Image streams by default do not automatically update. This default behavior might create a security issue because security updates to images referenced by an image stream do not automatically occur. For information about how to override this default behavior, see <a href=\"#\">Configuring periodic importing of imagestreamtags</a>.</p><ul><li>• When a container is deployed, its security depends on it running on secure operating systems and networks, and establishing firm boundaries between the container itself and the users and hosts that interact with it.</li><li>• Continued security relies on being able to scan container images for vulnerabilities and having an efficient way to correct and replace vulnerable images.</li></ul><p>Beyond what a platform such as OpenShift Container Platform offers out of the box, your organization will likely have its own security demands. Some level of compliance verification might be needed before you can even bring OpenShift Container Platform into your data center.</p><p>Likewise, you may need to add your own agents, specialized hardware drivers, or encryption features to OpenShift Container Platform, before it can meet your organization's security standards.</p><p>This guide provides a high-level walkthrough of the container security measures available in OpenShift Container Platform, including solutions for the host layer, the container and orchestration layer, and the build and application layer. It then points you to specific OpenShift Container Platform documentation to help you achieve those security measures.</p><p>This guide contains the following information:</p><ul><li>• Why container security is important and how it compares with existing security standards.</li><li>• Which container security measures are provided by the host (RHCOS and RHEL) layer and which are provided by OpenShift Container Platform.</li><li>• How to evaluate your container content and sources for vulnerabilities.</li><li>• How to design your build and deployment process to proactively check container content.</li><li>• How to control access to containers through authentication and authorization.</li><li>• How networking and attached storage are secured in OpenShift Container Platform.</li><li>• Containerized solutions for API management and SSO.</li></ul><p>The goal of this guide is to understand the incredible security benefits of using OpenShift Container Platform for your containerized workloads and how the entire Red Hat ecosystem plays a part in making</p>\n<p>and keeping containers secure. It will also help you understand how you can engage with the OpenShift Container Platform to achieve your organization's security goals.</p>\n\n<h3>2.1.1. What are containers?</h3>\n\n<p>Containers package an application and all its dependencies into a single image that can be promoted from development, to test, to production, without change. A container might be part of a larger application that works closely with other containers.</p>\n\n<p>Containers provide consistency across environments and multiple deployment targets: physical servers, virtual machines (VMs), and private or public cloud.</p>\n\n<p>Some of the benefits of using containers include:</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Infrastructure</th>\n<th>Applications</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Sandboxed application processes on a shared Linux operating system kernel</td>\n<td>Package my application and all of its dependencies</td>\n</tr>\n<tr>\n<td>Simpler, lighter, and denser than virtual machines</td>\n<td>Deploy to any environment in seconds and enable CI/CD</td>\n</tr>\n<tr>\n<td>Portable across different environments</td>\n<td>Easily access and share containerized components</td>\n</tr>\n</tbody>\n</table>\n\n<p>See <a href=\"#\">Understanding Linux containers</a> from the Red Hat Customer Portal to find out more about Linux containers. To learn about RHEL container tools, see <a href=\"#\">Building, running, and managing containers</a> in the RHEL product documentation.</p>\n\n<h3>2.1.2. What is OpenShift Container Platform?</h3>\n\n<p>Automating how containerized applications are deployed, run, and managed is the job of a platform such as OpenShift Container Platform. At its core, OpenShift Container Platform relies on the Kubernetes project to provide the engine for orchestrating containers across many nodes in scalable data centers.</p>\n\n<p>Kubernetes is a project, which can run using different operating systems and add-on components that offer no guarantees of supportability from the project. As a result, the security of different Kubernetes platforms can vary.</p>\n\n<p>OpenShift Container Platform is designed to lock down Kubernetes security and integrate the platform with a variety of extended components. To do this, OpenShift Container Platform draws on the extensive Red Hat ecosystem of open source technologies that include the operating systems, authentication, storage, networking, development tools, base container images, and many other components.</p>\n\n<p>OpenShift Container Platform can leverage Red Hat's experience in uncovering and rapidly deploying fixes for vulnerabilities in the platform itself as well as the containerized applications running on the platform. Red Hat's experience also extends to efficiently integrating new components with OpenShift Container Platform as they become available and adapting technologies to individual customer needs.</p>\n\n<h4>Additional resources</h4>\n\n<ul>\n<li>• <a href=\"#\">OpenShift Container Platform architecture</a></li>\n</ul>\n<ul><li>• <a href=\"#\">OpenShift Security Guide</a></li></ul><h2>2.2. UNDERSTANDING HOST AND VM SECURITY</h2><p>Both containers and virtual machines provide ways of separating applications running on a host from the operating system itself. Understanding RHCOS, which is the operating system used by OpenShift Container Platform, will help you see how the host systems protect containers and hosts from each other.</p><h3>2.2.1. Securing containers on Red Hat Enterprise Linux CoreOS (RHCOS)</h3><p>Containers simplify the act of deploying many applications to run on the same host, using the same kernel and container runtime to spin up each container. The applications can be owned by many users and, because they are kept separate, can run different, and even incompatible, versions of those applications at the same time without issue.</p><p>In Linux, containers are just a special type of process, so securing containers is similar in many ways to securing any other running process. An environment for running containers starts with an operating system that can secure the host kernel from containers and other processes running on the host, as well as secure containers from each other.</p><p>Because OpenShift Container Platform 4.21 runs on RHCOS hosts, with the option of using Red Hat Enterprise Linux (RHEL) as worker nodes, the following concepts apply by default to any deployed OpenShift Container Platform cluster. These RHEL security features are at the core of what makes running containers in OpenShift Container Platform more secure:</p><ul><li>• <i>Linux namespaces</i> enable creating an abstraction of a particular global system resource to make it appear as a separate instance to processes within a namespace. Consequently, several containers can use the same computing resource simultaneously without creating a conflict. Container namespaces that are separate from the host by default include mount table, process table, network interface, user, control group, UTS, and IPC namespaces. Those containers that need direct access to host namespaces need to have elevated permissions to request that access. See <a href=\"#\">Building, running, and managing containers</a> from the RHEL 9 container documentation for details on the types of namespaces.</li><li>• <i>SELinux</i> provides an additional layer of security to keep containers isolated from each other and from the host. SELinux allows administrators to enforce mandatory access controls (MAC) for every user, application, process, and file.</li></ul><h4>WARNING</h4><p>Disabling SELinux on RHCOS is not supported.</p><ul><li>• <i>CGroups</i> (control groups) limit, account for, and isolate the resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. CGroups are used to ensure that containers on the same host are not impacted by each other.</li><li>• <i>Secure computing mode (seccomp)</i> profiles can be associated with a container to restrict available system calls. See page 94 of the <a href=\"#\">Red Hat OpenShift security guide</a> for details about seccomp.</li></ul><ul><li>• Deploying containers using <i>RHCOS</i> reduces the attack surface by minimizing the host environment and tuning it for containers. The <a href=\"#\">CRI-O container engine</a> further reduces that attack surface by implementing only those features required by Kubernetes and OpenShift Container Platform to run and manage containers, as opposed to other container engines that implement desktop-oriented standalone features.</li></ul><p>RHCOS is a version of Red Hat Enterprise Linux (RHEL) that is specially configured to work as control plane (master) and worker nodes on OpenShift Container Platform clusters. So RHCOS is tuned to efficiently run container workloads, along with Kubernetes and OpenShift Container Platform services.</p><h2>NOTE</h2><p>To further protect RHCOS systems in OpenShift Container Platform clusters, most containers, except those managing or monitoring the host system itself, should run as a non-root user. Dropping the privilege level or creating containers with the least amount of privileges possible is recommended best practice for protecting your own OpenShift Container Platform clusters.</p><h3>Additional resources</h3><ul><li>• <a href=\"#\">How nodes enforce resource constraints</a></li><li>• <a href=\"#\">Managing security context constraints</a></li><li>• <a href=\"#\">Supported platforms for OpenShift clusters</a></li><li>• <a href=\"#\">Choosing how to configure RHCOS</a></li><li>• <a href=\"#\">Ignition</a></li><li>• <a href=\"#\">Kernel arguments</a></li><li>• <a href=\"#\">Kernel modules</a></li><li>• <a href=\"#\">Disk encryption</a></li><li>• <a href=\"#\">Chrony time service</a></li><li>• <a href=\"#\">About the OpenShift Update Service</a></li><li>• <a href=\"#\">FIPS cryptography</a></li></ul><h3>2.2.2. Comparing virtualization and containers</h3><p>Traditional virtualization provides another way to keep application environments separate on the same physical host. However, virtual machines work in a different way than containers. Virtualization relies on a hypervisor spinning up guest virtual machines (VMs), each of which has its own operating system (OS), represented by a running kernel, as well as the running application and its dependencies.</p><p>With VMs, the hypervisor isolates the guests from each other and from the host kernel. Fewer individuals and processes have access to the hypervisor, reducing the attack surface on the physical server. That said, security must still be monitored: one guest VM might be able to use hypervisor bugs to gain access to another VM or the host kernel. And, when the OS needs to be patched, it must be patched on all guest VMs using that OS.</p>"},"page_stats":{"kind":"list like","value":[{"page_number":1,"error":false,"token_count":251,"num_chunks":5},{"page_number":2,"error":false,"token_count":48,"num_chunks":1},{"page_number":3,"error":false,"token_count":90,"num_chunks":2},{"page_number":4,"error":false,"token_count":589,"num_chunks":11},{"page_number":5,"error":false,"token_count":1893,"num_chunks":4},{"page_number":6,"error":false,"token_count":1817,"num_chunks":3},{"page_number":7,"error":false,"token_count":1789,"num_chunks":3},{"page_number":8,"error":false,"token_count":1504,"num_chunks":3},{"page_number":9,"error":false,"token_count":1724,"num_chunks":3},{"page_number":10,"error":false,"token_count":1698,"num_chunks":3},{"page_number":11,"error":false,"token_count":1943,"num_chunks":3},{"page_number":12,"error":false,"token_count":1850,"num_chunks":3},{"page_number":13,"error":false,"token_count":1693,"num_chunks":3},{"page_number":14,"error":false,"token_count":2016,"num_chunks":3},{"page_number":15,"error":false,"token_count":1733,"num_chunks":3},{"page_number":16,"error":false,"token_count":2062,"num_chunks":3},{"page_number":17,"error":false,"token_count":2106,"num_chunks":3},{"page_number":18,"error":false,"token_count":1817,"num_chunks":3},{"page_number":19,"error":false,"token_count":2141,"num_chunks":3},{"page_number":20,"error":false,"token_count":1732,"num_chunks":3},{"page_number":21,"error":false,"token_count":1852,"num_chunks":3},{"page_number":22,"error":false,"token_count":817,"num_chunks":3},{"page_number":23,"error":false,"token_count":111,"num_chunks":2},{"page_number":24,"error":false,"token_count":961,"num_chunks":14},{"page_number":25,"error":false,"token_count":998,"num_chunks":15},{"page_number":26,"error":false,"token_count":132,"num_chunks":3},{"page_number":27,"error":false,"token_count":1060,"num_chunks":16},{"page_number":28,"error":false,"token_count":1156,"num_chunks":16},{"page_number":29,"error":false,"token_count":1093,"num_chunks":14},{"page_number":30,"error":false,"token_count":981,"num_chunks":12}],"string":"[\n {\n \"page_number\": 1,\n \"error\": false,\n \"token_count\": 251,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 2,\n \"error\": false,\n \"token_count\": 48,\n \"num_chunks\": 1\n },\n {\n \"page_number\": 3,\n \"error\": false,\n \"token_count\": 90,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 4,\n \"error\": false,\n \"token_count\": 589,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 5,\n \"error\": false,\n \"token_count\": 1893,\n \"num_chunks\": 4\n },\n {\n \"page_number\": 6,\n \"error\": false,\n \"token_count\": 1817,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 7,\n \"error\": false,\n \"token_count\": 1789,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 8,\n \"error\": false,\n \"token_count\": 1504,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 9,\n \"error\": false,\n \"token_count\": 1724,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 10,\n \"error\": false,\n \"token_count\": 1698,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 11,\n \"error\": false,\n \"token_count\": 1943,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 12,\n \"error\": false,\n \"token_count\": 1850,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 13,\n \"error\": false,\n \"token_count\": 1693,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 14,\n \"error\": false,\n \"token_count\": 2016,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 15,\n \"error\": false,\n \"token_count\": 1733,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 16,\n \"error\": false,\n \"token_count\": 2062,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 17,\n \"error\": false,\n \"token_count\": 2106,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 18,\n \"error\": false,\n \"token_count\": 1817,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 19,\n \"error\": false,\n \"token_count\": 2141,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 20,\n \"error\": false,\n \"token_count\": 1732,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 21,\n \"error\": false,\n \"token_count\": 1852,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 22,\n \"error\": false,\n \"token_count\": 817,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 23,\n \"error\": false,\n \"token_count\": 111,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 24,\n \"error\": false,\n \"token_count\": 961,\n \"num_chunks\": 14\n },\n {\n \"page_number\": 25,\n \"error\": false,\n \"token_count\": 998,\n \"num_chunks\": 15\n },\n {\n \"page_number\": 26,\n \"error\": false,\n \"token_count\": 132,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 27,\n \"error\": false,\n \"token_count\": 1060,\n \"num_chunks\": 16\n },\n {\n \"page_number\": 28,\n \"error\": false,\n \"token_count\": 1156,\n \"num_chunks\": 16\n },\n {\n \"page_number\": 29,\n \"error\": false,\n \"token_count\": 1093,\n \"num_chunks\": 14\n },\n {\n \"page_number\": 30,\n \"error\": false,\n \"token_count\": 981,\n \"num_chunks\": 12\n }\n]","isConversational":false}}},{"rowIdx":95,"cells":{"source_id":{"kind":"string","value":"OpenShift_Container_Platform-4.21-Security_APIs-en-US"},"pdf_url":{"kind":"string","value":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/security_apis/OpenShift_Container_Platform-4.21-Security_APIs-en-US.pdf"},"status":{"kind":"string","value":"success"},"processed_at":{"kind":"string","value":"2026-04-15T18:37:18.757573+00:00"},"elapsed_seconds":{"kind":"number","value":67.58,"string":"67.58"},"num_pages":{"kind":"number","value":101,"string":"101"},"num_pages_processed":{"kind":"number","value":30,"string":"30"},"max_pages_per_paper":{"kind":"number","value":30,"string":"30"},"pdf_exceeds_page_limit":{"kind":"bool","value":true,"string":"true"},"failed_pages":{"kind":"list like","value":[],"string":"[]","isConversational":false},"prompt_type":{"kind":"string","value":"ocr_layout"},"model_id":{"kind":"string","value":"datalab-to/chandra-ocr-2"},"script_version":{"kind":"timestamp","value":"2026-04-15T00:00:00","string":"2026-04-15T00:00:00"},"markdown":{"kind":"string","value":"# OpenShift Container Platform 4.21\n\n## Security APIs\n\nReference guide for security APIs# OpenShift Container Platform 4.21 Security APIs\n\n---\n\nReference guide for security APIs## Legal Notice\n\nCopyright © Red Hat.\n\nExcept as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.\n\nRed Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.\n\nRed Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.\n\nLinux ® is the registered trademark of Linus Torvalds in the United States and other countries.\n\nXFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.\n\nThe OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.\n\nAll other trademarks are the property of their respective owners.\n\n## Abstract\n\nThis document describes the OpenShift Container Platform security API objects and their detailed specifications.# Table of Contents\n\n<table>\n<tr>\n<td><b>CHAPTER 1. SECURITY APIS</b> .....</td>\n<td><b>4</b></td>\n</tr>\n<tr>\n<td> 1.1. CERTIFICATESIGNINGREQUEST [CERTIFICATES.K8S.IO/V1]</td>\n<td>4</td>\n</tr>\n<tr>\n<td> 1.2. CREDENTIALSREQUEST [CLOUDCREDENTIAL.OPENSHIFT.IO/V1]</td>\n<td>4</td>\n</tr>\n<tr>\n<td> 1.3. PODSECURITYPOLICYREVIEW [SECURITY.OPENSHIFT.IO/V1]</td>\n<td>4</td>\n</tr>\n<tr>\n<td> 1.4. PODSECURITYPOLICYSELFSUBJECTREVIEW [SECURITY.OPENSHIFT.IO/V1]</td>\n<td>4</td>\n</tr>\n<tr>\n<td> 1.5. PODSECURITYPOLICYSUBJECTREVIEW [SECURITY.OPENSHIFT.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.6. RANGEALLOCATION [SECURITY.OPENSHIFT.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.7. SECRET [V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.8. SECURITYCONTEXTCONSTRAINTS [SECURITY.OPENSHIFT.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.9. SERVICEACCOUNT [V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. CERTIFICATESIGNINGREQUEST [CERTIFICATES.K8S.IO/V1]</b> .....</td>\n<td><b>7</b></td>\n</tr>\n<tr>\n<td> 2.1. SPECIFICATION</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 2.1.1. .spec</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.1.2. .spec.extra</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 2.1.3. .status</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 2.1.4. .status.conditions</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 2.1.5. .status.conditions[]</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 2.2. API ENDPOINTS</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2.1. /apis/certificates.k8s.io/v1/certificatesigningrequests</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.2.2. /apis/certificates.k8s.io/v1/watch/certificatesigningrequests</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.2.3. /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 2.2.4. /apis/certificates.k8s.io/v1/watch/certificatesigningrequests/{name}</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.5. /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/status</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.6. /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/approval</td>\n<td>25</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. CREDENTIALSREQUEST [CLOUDCREDENTIAL.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>28</b></td>\n</tr>\n<tr>\n<td> 3.1. SPECIFICATION</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.1.1. .spec</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 3.1.2. .spec.secretRef</td>\n<td>30</td>\n</tr>\n<tr>\n<td> 3.1.3. .status</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.1.4. .status.conditions</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.1.5. .status.conditions[]</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.2. API ENDPOINTS</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.2.1. /apis/cloudcredential.openshift.io/v1/credentialsrequests</td>\n<td>34</td>\n</tr>\n<tr>\n<td> 3.2.2. /apis/cloudcredential.openshift.io/v1/namespaces/{namespace}/credentialsrequests</td>\n<td>34</td>\n</tr>\n<tr>\n<td> 3.2.3. /apis/cloudcredential.openshift.io/v1/namespaces/{namespace}/credentialsrequests/{name}</td>\n<td>36</td>\n</tr>\n<tr>\n<td> 3.2.4. /apis/cloudcredential.openshift.io/v1/namespaces/{namespace}/credentialsrequests/{name}/status</td>\n<td>39</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. PODSECURITYPOLICYREVIEW [SECURITY.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>43</b></td>\n</tr>\n<tr>\n<td> 4.1. SPECIFICATION</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.1.1. .spec</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 4.1.2. .status</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 4.1.3. .status.allowedServiceAccounts</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 4.1.4. .status.allowedServiceAccounts[]</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 4.2. API ENDPOINTS</td>\n<td>46</td>\n</tr>\n<tr>\n<td> 4.2.1. /apis/security.openshift.io/v1/namespaces/{namespace}/podsecuritypolicyreviews</td>\n<td>46</td>\n</tr>\n<tr>\n<td><b>CHAPTER 5. PODSECURITYPOLICYSELFSUBJECTREVIEW [SECURITY.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>48</b></td>\n</tr>\n<tr>\n<td> 5.1. SPECIFICATION</td>\n<td>48</td>\n</tr>\n<tr>\n<td> 5.1.1. .spec</td>\n<td>49</td>\n</tr>\n</table><table>\n<tr>\n<td>5.1.2. .status</td>\n<td>49</td>\n</tr>\n<tr>\n<td>5.2. API ENDPOINTS</td>\n<td>50</td>\n</tr>\n<tr>\n<td>5.2.1. /apis/security.openshift.io/v1/namespaces/{namespace}/podsecuritypolicyselfsubjectreviews</td>\n<td>50</td>\n</tr>\n<tr>\n<td><b>CHAPTER 6. PODSECURITYPOLICYSUBJECTREVIEW [SECURITY.OPENSHIFT.IO/V1]</b></td>\n<td><b>52</b></td>\n</tr>\n<tr>\n<td>6.1. SPECIFICATION</td>\n<td>52</td>\n</tr>\n<tr>\n<td>6.1.1. .spec</td>\n<td>53</td>\n</tr>\n<tr>\n<td>6.1.2. .status</td>\n<td>53</td>\n</tr>\n<tr>\n<td>6.2. API ENDPOINTS</td>\n<td>54</td>\n</tr>\n<tr>\n<td>6.2.1. /apis/security.openshift.io/v1/namespaces/{namespace}/podsecuritypolicyselfsubjectreviews</td>\n<td>54</td>\n</tr>\n<tr>\n<td><b>CHAPTER 7. RANGEALLOCATION [SECURITY.OPENSHIFT.IO/V1]</b></td>\n<td><b>56</b></td>\n</tr>\n<tr>\n<td>7.1. SPECIFICATION</td>\n<td>56</td>\n</tr>\n<tr>\n<td>7.2. API ENDPOINTS</td>\n<td>57</td>\n</tr>\n<tr>\n<td>7.2.1. /apis/security.openshift.io/v1/rangeallocations</td>\n<td>57</td>\n</tr>\n<tr>\n<td>7.2.2. /apis/security.openshift.io/v1/watch/rangeallocations</td>\n<td>59</td>\n</tr>\n<tr>\n<td>7.2.3. /apis/security.openshift.io/v1/rangeallocations/{name}</td>\n<td>60</td>\n</tr>\n<tr>\n<td>7.2.4. /apis/security.openshift.io/v1/watch/rangeallocations/{name}</td>\n<td>63</td>\n</tr>\n<tr>\n<td><b>CHAPTER 8. SECRET [V1]</b></td>\n<td><b>64</b></td>\n</tr>\n<tr>\n<td>8.1. SPECIFICATION</td>\n<td>64</td>\n</tr>\n<tr>\n<td>8.2. API ENDPOINTS</td>\n<td>65</td>\n</tr>\n<tr>\n<td>8.2.1. /api/v1/secrets</td>\n<td>66</td>\n</tr>\n<tr>\n<td>8.2.2. /api/v1/watch/secrets</td>\n<td>66</td>\n</tr>\n<tr>\n<td>8.2.3. /api/v1/namespaces/{namespace}/secrets</td>\n<td>67</td>\n</tr>\n<tr>\n<td>8.2.4. /api/v1/watch/namespaces/{namespace}/secrets</td>\n<td>69</td>\n</tr>\n<tr>\n<td>8.2.5. /api/v1/namespaces/{namespace}/secrets/{name}</td>\n<td>69</td>\n</tr>\n<tr>\n<td>8.2.6. /api/v1/watch/namespaces/{namespace}/secrets/{name}</td>\n<td>72</td>\n</tr>\n<tr>\n<td><b>CHAPTER 9. SECURITYCONTEXTCONSTRAINTS [SECURITY.OPENSHIFT.IO/V1]</b></td>\n<td><b>74</b></td>\n</tr>\n<tr>\n<td>9.1. SPECIFICATION</td>\n<td>74</td>\n</tr>\n<tr>\n<td>9.2. API ENDPOINTS</td>\n<td>79</td>\n</tr>\n<tr>\n<td>9.2.1. /apis/security.openshift.io/v1/securitycontextconstraints</td>\n<td>79</td>\n</tr>\n<tr>\n<td>9.2.2. /apis/security.openshift.io/v1/watch/securitycontextconstraints</td>\n<td>81</td>\n</tr>\n<tr>\n<td>9.2.3. /apis/security.openshift.io/v1/securitycontextconstraints/{name}</td>\n<td>82</td>\n</tr>\n<tr>\n<td>9.2.4. /apis/security.openshift.io/v1/watch/securitycontextconstraints/{name}</td>\n<td>85</td>\n</tr>\n<tr>\n<td><b>CHAPTER 10. SERVICEACCOUNT [V1]</b></td>\n<td><b>86</b></td>\n</tr>\n<tr>\n<td>10.1. SPECIFICATION</td>\n<td>86</td>\n</tr>\n<tr>\n<td>10.1.1. .imagePullSecrets</td>\n<td>88</td>\n</tr>\n<tr>\n<td>10.1.2. .imagePullSecrets[]</td>\n<td>88</td>\n</tr>\n<tr>\n<td>10.1.3. .secrets</td>\n<td>88</td>\n</tr>\n<tr>\n<td>10.1.4. .secrets[]</td>\n<td>88</td>\n</tr>\n<tr>\n<td>10.2. API ENDPOINTS</td>\n<td>90</td>\n</tr>\n<tr>\n<td>10.2.1. /api/v1/serviceaccounts</td>\n<td>90</td>\n</tr>\n<tr>\n<td>10.2.2. /api/v1/watch/serviceaccounts</td>\n<td>91</td>\n</tr>\n<tr>\n<td>10.2.3. /api/v1/namespaces/{namespace}/serviceaccounts</td>\n<td>91</td>\n</tr>\n<tr>\n<td>10.2.4. /api/v1/watch/namespaces/{namespace}/serviceaccounts</td>\n<td>93</td>\n</tr>\n<tr>\n<td>10.2.5. /api/v1/namespaces/{namespace}/serviceaccounts/{name}</td>\n<td>94</td>\n</tr>\n<tr>\n<td>10.2.6. /api/v1/watch/namespaces/{namespace}/serviceaccounts/{name}</td>\n<td>97</td>\n</tr>\n</table>## CHAPTER 1. SECURITY APIS\n\n### 1.1. CERTIFICATESIGNINGREQUEST [CERTIFICATES.K8S.IO/V1]\n\n#### Description\n\nCertificateSigningRequest objects provide a mechanism to obtain x509 certificates by submitting a certificate signing request, and having it asynchronously approved and issued.\n\nKubelets use this API to obtain: 1. client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client-kubelet\" signerName). 2. serving certificates for TLS endpoints kube-apiserver can connect to securely (with the \"kubernetes.io/kubelet-serving\" signerName).\n\nThis API can be used to request client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client\" signerName), or to obtain certificates from custom non-Kubernetes signers.\n\n#### Type\n\n**object**\n\n### 1.2. CREDENTIALSREQUEST [CLOUDCREDENTIAL.OPENSHIFT.IO/V1]\n\n#### Description\n\nCredentialsRequest is the Schema for the credentialsrequests API\n\n#### Type\n\n**object**\n\n### 1.3. PODSECURITYPOLICYREVIEW [SECURITY.OPENSHIFT.IO/V1]\n\n#### Description\n\nPodSecurityPolicyReview checks which service accounts (not users, since that would be cluster-wide) can create the **PodTemplateSpec** in question.\n\nCompatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer).\n\n#### Type\n\n**object**\n\n### 1.4. PODSECURITYPOLICYSELFSUBJECTREVIEW [SECURITY.OPENSHIFT.IO/V1]\n\n#### Description\n\nPodSecurityPolicySelfSubjectReview checks whether this user/SA tuple can create the PodTemplateSpec\n\nCompatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer).\n\n#### Type\n\n**object**## 1.5. PODSECURITYPOLICYSUBJECTREVIEW [SECURITY.OPENSHIFT.IO/V1]\n\n### Description\n\nPodSecurityPolicySubjectReview checks whether a particular user/SA tuple can create the PodTemplateSpec.\n\nCompatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer).\n\n### Type\n\n**object**\n\n## 1.6. RANGEALLOCATION [SECURITY.OPENSHIFT.IO/V1]\n\n### Description\n\nRangeAllocation is used so we can easily expose a RangeAllocation typed for security group\n\nCompatibility level 4: No compatibility is provided, the API can change at any point for any reason.\n\nThese capabilities should not be used by applications needing long term support.\n\n### Type\n\n**object**\n\n## 1.7. SECRET [V1]\n\n### Description\n\nSecret holds secret data of a certain type. The total bytes of the values in the Data field must be less than MaxSecretSize bytes.\n\n### Type\n\n**object**\n\n## 1.8. SECURITYCONTEXTCONSTRAINTS [SECURITY.OPENSHIFT.IO/V1]\n\n### Description\n\nSecurityContextConstraints governs the ability to make requests that affect the SecurityContext that will be applied to a container. For historical reasons SCC was exposed under the core Kubernetes API group. That exposure is deprecated and will be removed in a future release - users should instead use the security.openshift.io group to manage SecurityContextConstraints.\n\nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).\n\n### Type\n\n**object**\n\n## 1.9. SERVICEACCOUNT [V1]\n\n### Description\n\nServiceAccount binds together: \\* a name, understood by users, and perhaps by peripheral systems, for an identity \\* a principal that can be authenticated and authorized \\* a set of secretsType\n\n**object**# CHAPTER 2. CERTIFICATESIGNINGREQUEST [CERTIFICATES.K8S.IO/V1]\n\n## Description\n\nCertificateSigningRequest objects provide a mechanism to obtain x509 certificates by submitting a certificate signing request, and having it asynchronously approved and issued.\n\nKubelets use this API to obtain: 1. client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client-kubelet\" signerName). 2. serving certificates for TLS endpoints kube-apiserver can connect to securely (with the \"kubernetes.io/kubelet-serving\" signerName).\n\nThis API can be used to request client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client\" signerName), or to obtain certificates from custom non-Kubernetes signers.\n\n## Type\n\n**object**\n\n## Required\n\n- • **spec**\n\n## 2.1. SPECIFICATION\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta</b></td>\n<td></td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>spec</b></td>\n<td><b>object</b></td>\n<td>CertificateSigningRequestSpec contains the certificate request.</td>\n</tr>\n<tr>\n<td><b>status</b></td>\n<td><b>object</b></td>\n<td>CertificateSigningRequestStatus contains conditions used to indicate approved/denied/failed status of the request, and the issued certificate.</td>\n</tr>\n</tbody>\n</table>\n\n### 2.1.1. .spec\n\n#### Description\n\nCertificateSigningRequestSpec contains the certificate request.\n\n#### Type\n\n**object**\n\n#### Required\n\n- • **request**\n- • **signerName**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th data-bbox=\"88 46 363 83\">Property</th>\n<th data-bbox=\"363 46 636 83\">Type</th>\n<th data-bbox=\"636 46 908 83\">Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td data-bbox=\"88 83 363 708\"><b>expirationSeconds</b></td>\n<td data-bbox=\"363 83 636 708\"><b>integer</b></td>\n<td data-bbox=\"636 83 908 708\">\n<p>expirationSeconds is the requested duration of validity of the issued certificate. The certificate signer may issue a certificate with a different validity duration so a client must check the delta between the notBefore and and notAfter fields in the issued certificate to determine the actual duration.</p>\n<p>The v1.22+ in-tree implementations of the well-known Kubernetes signers will honor this field as long as the requested duration is not greater than the maximum duration they will honor per the --cluster-signing-duration CLI flag to the Kubernetes controller manager.</p>\n<p>Certificate signers may not honor this field for various reasons:</p>\n<ol>\n<li>1. Old signer that is unaware of the field (such as the in-tree implementations prior to v1.22)</li>\n<li>2. Signer whose configured maximum is shorter than the requested duration</li>\n<li>3. Signer whose configured minimum is longer than the requested duration</li>\n</ol>\n<p>The minimum valid value for expirationSeconds is 600, i.e. 10 minutes.</p>\n</td>\n</tr>\n<tr>\n<td data-bbox=\"88 708 363 811\"><b>extra</b></td>\n<td data-bbox=\"363 708 636 811\"><b>object</b></td>\n<td data-bbox=\"636 708 908 811\">\n<p>extra contains extra attributes of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</p>\n</td>\n</tr>\n<tr>\n<td data-bbox=\"88 811 363 847\"><b>extra{}</b></td>\n<td data-bbox=\"363 811 636 847\"><b>array (string)</b></td>\n<td data-bbox=\"636 811 908 847\"></td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th data-bbox=\"88 48 363 84\">Property</th>\n<th data-bbox=\"363 48 636 84\">Type</th>\n<th data-bbox=\"636 48 908 84\">Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td data-bbox=\"88 84 363 203\"><b>groups</b></td>\n<td data-bbox=\"363 84 636 203\"><b>array (string)</b></td>\n<td data-bbox=\"636 84 908 203\">groups contains group membership of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</td>\n</tr>\n<tr>\n<td data-bbox=\"88 203 363 336\"><b>request</b></td>\n<td data-bbox=\"363 203 636 336\"><b>string</b></td>\n<td data-bbox=\"636 203 908 336\">request contains an x509 certificate signing request encoded in a \"CERTIFICATE REQUEST\" PEM block. When serialized as JSON or YAML, the data is additionally base64-encoded.</td>\n</tr>\n<tr>\n<td data-bbox=\"88 336 363 946\"><b>signerName</b></td>\n<td data-bbox=\"363 336 636 946\"><b>string</b></td>\n<td data-bbox=\"636 336 908 946\">\n<p>signerName indicates the requested signer, and is a qualified name.</p>\n<p>List/watch requests for CertificateSigningRequests can filter on this field using a \"spec.signerName=NAME\" fieldSelector.</p>\n<p>Well-known Kubernetes signers are: 1. \"kubernetes.io/kube-apiserver-client\": issues client certificates that can be used to authenticate to kube-apiserver. Requests for this signer are never auto-approved by kube-controller-manager, can be issued by the \"csrsigning\" controller in kube-controller-manager. 2. \"kubernetes.io/kube-apiserver-client-kubelet\": issues client certificates that kubelets use to authenticate to kube-apiserver. Requests for this signer can be auto-approved by the \"csrapproving\" controller in kube-controller-manager, and can be issued by the \"csrsigning\" controller in kube-controller-manager. 3. \"kubernetes.io/kubelet-serving\" issues serving certificates that kubelets use to serve TLS endpoints, which kube-apiserver can connect to securely. Requests for this signer are never auto-approved by kube-controller-</p>\n</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th data-bbox=\"91 48 364 84\">Property</th>\n<th data-bbox=\"364 48 637 84\">Type</th>\n<th data-bbox=\"637 48 908 84\">Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td data-bbox=\"91 84 364 554\"></td>\n<td data-bbox=\"364 84 637 554\"></td>\n<td data-bbox=\"637 84 908 554\">\n<p>manager, and can be issued by the \"CertSigning\" controller in kube-controller-manager.</p>\n<p>More details are available at <a href=\"https://k8s.io/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers\">https://k8s.io/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers</a></p>\n<p>Custom signerNames can also be specified. The signer defines: 1. Trust distribution: how trust (CA bundles) are distributed. 2. Permitted subjects: and behavior when a disallowed subject is requested. 3. Required, permitted, or forbidden x509 extensions in the request (including whether subjectAltNames are allowed, which types, restrictions on allowed values) and behavior when a disallowed extension is requested. 4. Required, permitted, or forbidden key usages / extended key usages. 5. Expiration/certificate lifetime: whether it is fixed by the signer, configurable by the admin. 6. Whether or not requests for CA certificates are allowed.</p>\n</td>\n</tr>\n<tr>\n<td data-bbox=\"91 554 364 656\"><b>uid</b></td>\n<td data-bbox=\"364 554 637 656\"><b>string</b></td>\n<td data-bbox=\"637 554 908 656\">\n<p>uid contains the uid of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</p>\n</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>usages</b></td>\n<td><b>array (string)</b></td>\n<td>\n<p>usages specifies a set of key usages requested in the issued certificate.</p>\n<p>Requests for TLS client certificates typically request: \"digital signature\", \"key encipherment\", \"client auth\".</p>\n<p>Requests for TLS serving certificates typically request: \"key encipherment\", \"digital signature\", \"server auth\".</p>\n<p>Valid values are: \"signing\", \"digital signature\", \"content commitment\", \"key encipherment\", \"key agreement\", \"data encipherment\", \"cert sign\", \"crl sign\", \"encipher only\", \"decipher only\", \"any\", \"server auth\", \"client auth\", \"code signing\", \"email protection\", \"s/mime\", \"ipsec end system\", \"ipsec tunnel\", \"ipsec user\", \"timestamping\", \"ocsp signing\", \"microsoft sgc\", \"netscape sgc\"</p>\n</td>\n</tr>\n<tr>\n<td><b>username</b></td>\n<td><b>string</b></td>\n<td>\n<p>username contains the name of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</p>\n</td>\n</tr>\n</tbody>\n</table>\n\n### 2.1.2. .spec.extra\n\n#### Description\n\nextra contains extra attributes of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.\n\n#### Type\n\n**object**\n\n### 2.1.3. .status\n\n#### Description\n\nCertificateSigningRequestStatus contains conditions used to indicate approved/denied/failed status of the request, and the issued certificate.\n\n#### Type\n\n**object**<table border=\"1\">\n<thead>\n<tr>\n<th data-bbox=\"88 46 363 84\">Property</th>\n<th data-bbox=\"363 46 636 84\">Type</th>\n<th data-bbox=\"636 46 908 84\">Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td data-bbox=\"88 84 363 908\"><b>certificate</b></td>\n<td data-bbox=\"363 84 636 908\"><b>string</b></td>\n<td data-bbox=\"636 84 908 908\">\n<p>certificate is populated with an issued certificate by the signer after an Approved condition is present. This field is set via the /status subresource. Once populated, this field is immutable.</p>\n<p>If the certificate signing request is denied, a condition of type \"Denied\" is added and this field remains empty. If the signer cannot issue the certificate, a condition of type \"Failed\" is added and this field remains empty.</p>\n<p>Validation requirements: 1. certificate must contain one or more PEM blocks. 2. All PEM blocks must have the \"CERTIFICATE\" label, contain no headers, and the encoded data must be a BER-encoded ASN.1 Certificate structure as described in section 4 of RFC5280. 3. Non-PEM content may appear before or after the \"CERTIFICATE\" PEM blocks and is unvalidated, to allow for explanatory text as described in section 5.2 of RFC7468.</p>\n<p>If more than one PEM block is present, and the definition of the requested spec.signerName does not indicate otherwise, the first block is the issued certificate, and subsequent blocks should be treated as intermediate certificates and presented in TLS handshakes.</p>\n<p>The certificate is encoded in PEM format.</p>\n<p>When serialized as JSON or YAML, the data is additionally base64-encoded, so it consists of:</p>\n<pre>base64( -----BEGIN\nCERTIFICATE----- ... -----END\nCERTIFICATE----- )</pre>\n</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>conditions</b></td>\n<td><b>array</b></td>\n<td>conditions applied to the request. Known conditions are \"Approved\", \"Denied\", and \"Failed\".</td>\n</tr>\n<tr>\n<td><b>conditions[]</b></td>\n<td><b>object</b></td>\n<td>CertificateSigningRequestCondition describes a condition of a CertificateSigningRequest object</td>\n</tr>\n</tbody>\n</table>\n\n### 2.1.4. .status.conditions\n\n#### Description\n\nconditions applied to the request. Known conditions are \"Approved\", \"Denied\", and \"Failed\".\n\n#### Type\n\n**array**\n\n### 2.1.5. .status.conditions[]\n\n#### Description\n\nCertificateSigningRequestCondition describes a condition of a CertificateSigningRequest object\n\n#### Type\n\n**object**\n\n#### Required\n\n- • **type**\n- • **status**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>lastTransitionTime</b></td>\n<td><b>Time</b></td>\n<td>lastTransitionTime is the time the condition last transitioned from one status to another. If unset, when a new condition type is added or an existing condition's status is changed, the server defaults this to the current time.</td>\n</tr>\n<tr>\n<td><b>lastUpdateTime</b></td>\n<td><b>Time</b></td>\n<td>lastUpdateTime is the time of the last update to this condition</td>\n</tr>\n<tr>\n<td><b>message</b></td>\n<td><b>string</b></td>\n<td>message contains a human readable message with details about the request state</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>reason</b></td>\n<td><b>string</b></td>\n<td>reason indicates a brief reason for the request state</td>\n</tr>\n<tr>\n<td><b>status</b></td>\n<td><b>string</b></td>\n<td>status of the condition, one of True, False, Unknown. Approved, Denied, and Failed conditions may not be \"False\" or \"Unknown\".</td>\n</tr>\n<tr>\n<td><b>type</b></td>\n<td><b>string</b></td>\n<td>\n<p>type of the condition. Known conditions are \"Approved\", \"Denied\", and \"Failed\".</p>\n<p>An \"Approved\" condition is added via the /approval subresource, indicating the request was approved and should be issued by the signer.</p>\n<p>A \"Denied\" condition is added via the /approval subresource, indicating the request was denied and should not be issued by the signer.</p>\n<p>A \"Failed\" condition is added via the /status subresource, indicating the signer failed to issue the certificate.</p>\n<p>Approved and Denied conditions are mutually exclusive. Approved, Denied, and Failed conditions cannot be removed once added.</p>\n<p>Only one condition of a given type is allowed.</p>\n</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2. API ENDPOINTS\n\nThe following API endpoints are available:\n\n- • **/apis/certificates.k8s.io/v1/certificatesigningrequests**\n - ◦ **DELETE**: delete collection of CertificateSigningRequest\n - ◦ **GET**: list or watch objects of kind CertificateSigningRequest\n - ◦ **POST**: create a CertificateSigningRequest\n- • **/apis/certificates.k8s.io/v1/watch/certificatesigningrequests**\n - ◦ **GET**: watch individual changes to a list of CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation insteadwatch parameter with a list operation instead.\n\n- • **/apis/certificates.k8s.io/v1/certificatesigningrequests/{name}**\n - ◦ **DELETE**: delete a CertificateSigningRequest\n - ◦ **GET**: read the specified CertificateSigningRequest\n - ◦ **PATCH**: partially update the specified CertificateSigningRequest\n - ◦ **PUT**: replace the specified CertificateSigningRequest\n- • **/apis/certificates.k8s.io/v1/watch/certificatesigningrequests/{name}**\n - ◦ **GET**: watch changes to an object of kind CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.\n- • **/apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/status**\n - ◦ **GET**: read status of the specified CertificateSigningRequest\n - ◦ **PATCH**: partially update status of the specified CertificateSigningRequest\n - ◦ **PUT**: replace status of the specified CertificateSigningRequest\n- • **/apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/approval**\n - ◦ **GET**: read approval of the specified CertificateSigningRequest\n - ◦ **PATCH**: partially update approval of the specified CertificateSigningRequest\n - ◦ **PUT**: replace approval of the specified CertificateSigningRequest\n\n### 2.2.1. /apis/certificates.k8s.io/v1/certificatesigningrequests\n\nHTTP method\n\n**DELETE**\n\nDescription\n\ndelete collection of CertificateSigningRequest\n\nTable 2.1. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n\nTable 2.2. HTTP responses<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n**HTTP method****GET****Description**\n\nlist or watch objects of kind CertificateSigningRequest\n\n**Table 2.3. HTTP responses**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>CertificateSigningRequestList</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n**HTTP method****POST****Description**\n\ncreate a CertificateSigningRequest\n\n**Table 2.4. Query parameters**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are:\n<ul>\n<li>- Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23.</li>\n<li>- Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+.</li>\n<li>- Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>\n\nTable 2.5. Body parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>CertificateSigningRequest</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nTable 2.6. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>CertificateSigningRequest</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>CertificateSigningRequest</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>CertificateSigningRequest</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.2. /apis/certificates.k8s.io/v1/watch/certificatesigningrequests\n\n#### HTTP method\n\n**GET**\n\n#### Description\n\nwatch individual changes to a list of CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead.Table 2.7. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>WatchEvent</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.3. /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}\n\nTable 2.8. Global path parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the CertificateSigningRequest</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**DELETE**\n\nDescription\n\ndelete a CertificateSigningRequest\n\nTable 2.9. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n\nTable 2.10. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method\n\n**GET**\n\nDescription\n\nread the specified CertificateSigningRequestTable 2.11. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method**PATCH**Description\n\npartially update the specified CertificateSigningRequest\n\nTable 2.12. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 2.13. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### HTTP method\n\n#### PUT\n\n### Description\n\nreplace the specified CertificateSigningRequest\n\nTable 2.14. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 2.15. Body parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>CertificateSigningRequest</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nTable 2.16. HTTP responses<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.4. /apis/certificates.k8s.io/v1/watch/certificatesigningrequests/{name}\n\nTable 2.17. Global path parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the CertificateSigningRequest</td>\n</tr>\n</tbody>\n</table>\n\n### HTTP method\n\n**GET**\n\n### Description\n\nwatch changes to an object of kind CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.\n\nTable 2.18. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">WatchEvent</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.5. /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/status\n\nTable 2.19. Global path parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the CertificateSigningRequest</td>\n</tr>\n</tbody>\n</table>\n\n### HTTP method\n\n**GET**\n\n### Description\n\nread status of the specified CertificateSigningRequest\n\nTable 2.20. HTTP responses<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n## HTTP method\n\n### PATCH\n\n#### Description\n\npartially update status of the specified CertificateSigningRequest\n\nTable 2.21. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 2.22. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### HTTP method\n\n#### PUT\n\n### Description\n\nreplace status of the specified CertificateSigningRequest\n\nTable 2.23. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\nTable 2.24. Body parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>CertificateSigningRequest</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nTable 2.25. HTTP responses<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.6. /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/approval\n\nTable 2.26. Global path parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the CertificateSigningRequest</td>\n</tr>\n</tbody>\n</table>\n\n### HTTP method\n\n**GET**\n\n### Description\n\nread approval of the specified CertificateSigningRequest\n\nTable 2.27. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n### HTTP method\n\n**PATCH**\n\n### Description\n\npartially update approval of the specified CertificateSigningRequest\n\nTable 2.28. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are:\n<ul>\n<li>- Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23.</li>\n<li>- Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+.</li>\n<li>- Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>\n\nTable 2.29. HTTP responses\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\nHTTP method**PUT**Description\n\nreplace approval of the specified CertificateSigningRequest\n\nTable 2.30. Query parameters\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are:\n<ul>\n<li>- All: all dry run stages will be processed</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>"},"html":{"kind":"string","value":"<h1>OpenShift Container Platform 4.21</h1><h2>Security APIs</h2><p>Reference guide for security APIs</p><h1>OpenShift Container Platform 4.21 Security APIs</h1><hr/><p>Reference guide for security APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.</p><p>Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.</p><p>Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.</p><p>Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.</p><p>XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.</p><p>The OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.</p><p>All other trademarks are the property of their respective owners.</p><h2>Abstract</h2><p>This document describes the OpenShift Container Platform security API objects and their detailed specifications.</p>\n<h1>Table of Contents</h1>\n\n<table>\n<tr>\n<td><b>CHAPTER 1. SECURITY APIS</b> .....</td>\n<td><b>4</b></td>\n</tr>\n<tr>\n<td> 1.1. CERTIFICATESIGNINGREQUEST [CERTIFICATES.K8S.IO/V1]</td>\n<td>4</td>\n</tr>\n<tr>\n<td> 1.2. CREDENTIALSREQUEST [CLOUDCREDENTIAL.OPENSHIFT.IO/V1]</td>\n<td>4</td>\n</tr>\n<tr>\n<td> 1.3. PODSECURITYPOLICYREVIEW [SECURITY.OPENSHIFT.IO/V1]</td>\n<td>4</td>\n</tr>\n<tr>\n<td> 1.4. PODSECURITYPOLICYSELFSUBJECTREVIEW [SECURITY.OPENSHIFT.IO/V1]</td>\n<td>4</td>\n</tr>\n<tr>\n<td> 1.5. PODSECURITYPOLICYSUBJECTREVIEW [SECURITY.OPENSHIFT.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.6. RANGEALLOCATION [SECURITY.OPENSHIFT.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.7. SECRET [V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.8. SECURITYCONTEXTCONSTRAINTS [SECURITY.OPENSHIFT.IO/V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td> 1.9. SERVICEACCOUNT [V1]</td>\n<td>5</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. CERTIFICATESIGNINGREQUEST [CERTIFICATES.K8S.IO/V1]</b> .....</td>\n<td><b>7</b></td>\n</tr>\n<tr>\n<td> 2.1. SPECIFICATION</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 2.1.1. .spec</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.1.2. .spec.extra</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 2.1.3. .status</td>\n<td>12</td>\n</tr>\n<tr>\n<td> 2.1.4. .status.conditions</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 2.1.5. .status.conditions[]</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 2.2. API ENDPOINTS</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2.1. /apis/certificates.k8s.io/v1/certificatesigningrequests</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.2.2. /apis/certificates.k8s.io/v1/watch/certificatesigningrequests</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.2.3. /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 2.2.4. /apis/certificates.k8s.io/v1/watch/certificatesigningrequests/{name}</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.5. /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/status</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.6. /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/approval</td>\n<td>25</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. CREDENTIALSREQUEST [CLOUDCREDENTIAL.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>28</b></td>\n</tr>\n<tr>\n<td> 3.1. SPECIFICATION</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.1.1. .spec</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 3.1.2. .spec.secretRef</td>\n<td>30</td>\n</tr>\n<tr>\n<td> 3.1.3. .status</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.1.4. .status.conditions</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.1.5. .status.conditions[]</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.2. API ENDPOINTS</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.2.1. /apis/cloudcredential.openshift.io/v1/credentialsrequests</td>\n<td>34</td>\n</tr>\n<tr>\n<td> 3.2.2. /apis/cloudcredential.openshift.io/v1/namespaces/{namespace}/credentialsrequests</td>\n<td>34</td>\n</tr>\n<tr>\n<td> 3.2.3. /apis/cloudcredential.openshift.io/v1/namespaces/{namespace}/credentialsrequests/{name}</td>\n<td>36</td>\n</tr>\n<tr>\n<td> 3.2.4. /apis/cloudcredential.openshift.io/v1/namespaces/{namespace}/credentialsrequests/{name}/status</td>\n<td>39</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. PODSECURITYPOLICYREVIEW [SECURITY.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>43</b></td>\n</tr>\n<tr>\n<td> 4.1. SPECIFICATION</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.1.1. .spec</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 4.1.2. .status</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 4.1.3. .status.allowedServiceAccounts</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 4.1.4. .status.allowedServiceAccounts[]</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 4.2. API ENDPOINTS</td>\n<td>46</td>\n</tr>\n<tr>\n<td> 4.2.1. /apis/security.openshift.io/v1/namespaces/{namespace}/podsecuritypolicyreviews</td>\n<td>46</td>\n</tr>\n<tr>\n<td><b>CHAPTER 5. PODSECURITYPOLICYSELFSUBJECTREVIEW [SECURITY.OPENSHIFT.IO/V1]</b> .....</td>\n<td><b>48</b></td>\n</tr>\n<tr>\n<td> 5.1. SPECIFICATION</td>\n<td>48</td>\n</tr>\n<tr>\n<td> 5.1.1. .spec</td>\n<td>49</td>\n</tr>\n</table>\n\n<table>\n<tr>\n<td>5.1.2. .status</td>\n<td>49</td>\n</tr>\n<tr>\n<td>5.2. API ENDPOINTS</td>\n<td>50</td>\n</tr>\n<tr>\n<td>5.2.1. /apis/security.openshift.io/v1/namespaces/{namespace}/podsecuritypolicyselfsubjectreviews</td>\n<td>50</td>\n</tr>\n<tr>\n<td><b>CHAPTER 6. PODSECURITYPOLICYSUBJECTREVIEW [SECURITY.OPENSHIFT.IO/V1]</b></td>\n<td><b>52</b></td>\n</tr>\n<tr>\n<td>6.1. SPECIFICATION</td>\n<td>52</td>\n</tr>\n<tr>\n<td>6.1.1. .spec</td>\n<td>53</td>\n</tr>\n<tr>\n<td>6.1.2. .status</td>\n<td>53</td>\n</tr>\n<tr>\n<td>6.2. API ENDPOINTS</td>\n<td>54</td>\n</tr>\n<tr>\n<td>6.2.1. /apis/security.openshift.io/v1/namespaces/{namespace}/podsecuritypolicyselfsubjectreviews</td>\n<td>54</td>\n</tr>\n<tr>\n<td><b>CHAPTER 7. RANGEALLOCATION [SECURITY.OPENSHIFT.IO/V1]</b></td>\n<td><b>56</b></td>\n</tr>\n<tr>\n<td>7.1. SPECIFICATION</td>\n<td>56</td>\n</tr>\n<tr>\n<td>7.2. API ENDPOINTS</td>\n<td>57</td>\n</tr>\n<tr>\n<td>7.2.1. /apis/security.openshift.io/v1/rangeallocations</td>\n<td>57</td>\n</tr>\n<tr>\n<td>7.2.2. /apis/security.openshift.io/v1/watch/rangeallocations</td>\n<td>59</td>\n</tr>\n<tr>\n<td>7.2.3. /apis/security.openshift.io/v1/rangeallocations/{name}</td>\n<td>60</td>\n</tr>\n<tr>\n<td>7.2.4. /apis/security.openshift.io/v1/watch/rangeallocations/{name}</td>\n<td>63</td>\n</tr>\n<tr>\n<td><b>CHAPTER 8. SECRET [V1]</b></td>\n<td><b>64</b></td>\n</tr>\n<tr>\n<td>8.1. SPECIFICATION</td>\n<td>64</td>\n</tr>\n<tr>\n<td>8.2. API ENDPOINTS</td>\n<td>65</td>\n</tr>\n<tr>\n<td>8.2.1. /api/v1/secrets</td>\n<td>66</td>\n</tr>\n<tr>\n<td>8.2.2. /api/v1/watch/secrets</td>\n<td>66</td>\n</tr>\n<tr>\n<td>8.2.3. /api/v1/namespaces/{namespace}/secrets</td>\n<td>67</td>\n</tr>\n<tr>\n<td>8.2.4. /api/v1/watch/namespaces/{namespace}/secrets</td>\n<td>69</td>\n</tr>\n<tr>\n<td>8.2.5. /api/v1/namespaces/{namespace}/secrets/{name}</td>\n<td>69</td>\n</tr>\n<tr>\n<td>8.2.6. /api/v1/watch/namespaces/{namespace}/secrets/{name}</td>\n<td>72</td>\n</tr>\n<tr>\n<td><b>CHAPTER 9. SECURITYCONTEXTCONSTRAINTS [SECURITY.OPENSHIFT.IO/V1]</b></td>\n<td><b>74</b></td>\n</tr>\n<tr>\n<td>9.1. SPECIFICATION</td>\n<td>74</td>\n</tr>\n<tr>\n<td>9.2. API ENDPOINTS</td>\n<td>79</td>\n</tr>\n<tr>\n<td>9.2.1. /apis/security.openshift.io/v1/securitycontextconstraints</td>\n<td>79</td>\n</tr>\n<tr>\n<td>9.2.2. /apis/security.openshift.io/v1/watch/securitycontextconstraints</td>\n<td>81</td>\n</tr>\n<tr>\n<td>9.2.3. /apis/security.openshift.io/v1/securitycontextconstraints/{name}</td>\n<td>82</td>\n</tr>\n<tr>\n<td>9.2.4. /apis/security.openshift.io/v1/watch/securitycontextconstraints/{name}</td>\n<td>85</td>\n</tr>\n<tr>\n<td><b>CHAPTER 10. SERVICEACCOUNT [V1]</b></td>\n<td><b>86</b></td>\n</tr>\n<tr>\n<td>10.1. SPECIFICATION</td>\n<td>86</td>\n</tr>\n<tr>\n<td>10.1.1. .imagePullSecrets</td>\n<td>88</td>\n</tr>\n<tr>\n<td>10.1.2. .imagePullSecrets[]</td>\n<td>88</td>\n</tr>\n<tr>\n<td>10.1.3. .secrets</td>\n<td>88</td>\n</tr>\n<tr>\n<td>10.1.4. .secrets[]</td>\n<td>88</td>\n</tr>\n<tr>\n<td>10.2. API ENDPOINTS</td>\n<td>90</td>\n</tr>\n<tr>\n<td>10.2.1. /api/v1/serviceaccounts</td>\n<td>90</td>\n</tr>\n<tr>\n<td>10.2.2. /api/v1/watch/serviceaccounts</td>\n<td>91</td>\n</tr>\n<tr>\n<td>10.2.3. /api/v1/namespaces/{namespace}/serviceaccounts</td>\n<td>91</td>\n</tr>\n<tr>\n<td>10.2.4. /api/v1/watch/namespaces/{namespace}/serviceaccounts</td>\n<td>93</td>\n</tr>\n<tr>\n<td>10.2.5. /api/v1/namespaces/{namespace}/serviceaccounts/{name}</td>\n<td>94</td>\n</tr>\n<tr>\n<td>10.2.6. /api/v1/watch/namespaces/{namespace}/serviceaccounts/{name}</td>\n<td>97</td>\n</tr>\n</table>\n<h2>CHAPTER 1. SECURITY APIS</h2><h3>1.1. CERTIFICATESIGNINGREQUEST [CERTIFICATES.K8S.IO/V1]</h3><h4>Description</h4><p>CertificateSigningRequest objects provide a mechanism to obtain x509 certificates by submitting a certificate signing request, and having it asynchronously approved and issued.</p><p>Kubelets use this API to obtain: 1. client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client-kubelet\" signerName). 2. serving certificates for TLS endpoints kube-apiserver can connect to securely (with the \"kubernetes.io/kubelet-serving\" signerName).</p><p>This API can be used to request client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client\" signerName), or to obtain certificates from custom non-Kubernetes signers.</p><h4>Type</h4><p><b>object</b></p><h3>1.2. CREDENTIALSREQUEST [CLOUDCREDENTIAL.OPENSHIFT.IO/V1]</h3><h4>Description</h4><p>CredentialsRequest is the Schema for the credentialsrequests API</p><h4>Type</h4><p><b>object</b></p><h3>1.3. PODSECURITYPOLICYREVIEW [SECURITY.OPENSHIFT.IO/V1]</h3><h4>Description</h4><p>PodSecurityPolicyReview checks which service accounts (not users, since that would be cluster-wide) can create the <b>PodTemplateSpec</b> in question.</p><p>Compatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer).</p><h4>Type</h4><p><b>object</b></p><h3>1.4. PODSECURITYPOLICYSELFSUBJECTREVIEW [SECURITY.OPENSHIFT.IO/V1]</h3><h4>Description</h4><p>PodSecurityPolicySelfSubjectReview checks whether this user/SA tuple can create the PodTemplateSpec</p><p>Compatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer).</p><h4>Type</h4><p><b>object</b></p><h2>1.5. PODSECURITYPOLICYSUBJECTREVIEW<br/>[SECURITY.OPENSHIFT.IO/V1]</h2><h3>Description</h3><p>PodSecurityPolicySubjectReview checks whether a particular user/SA tuple can create the PodTemplateSpec.</p><p>Compatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer).</p><h3>Type</h3><p><b>object</b></p><h2>1.6. RANGEALLOCATION [SECURITY.OPENSHIFT.IO/V1]</h2><h3>Description</h3><p>RangeAllocation is used so we can easily expose a RangeAllocation typed for security group</p><p>Compatibility level 4: No compatibility is provided, the API can change at any point for any reason.</p><p>These capabilities should not be used by applications needing long term support.</p><h3>Type</h3><p><b>object</b></p><h2>1.7. SECRET [V1]</h2><h3>Description</h3><p>Secret holds secret data of a certain type. The total bytes of the values in the Data field must be less than MaxSecretSize bytes.</p><h3>Type</h3><p><b>object</b></p><h2>1.8. SECURITYCONTEXTCONSTRAINTS [SECURITY.OPENSHIFT.IO/V1]</h2><h3>Description</h3><p>SecurityContextConstraints governs the ability to make requests that affect the SecurityContext that will be applied to a container. For historical reasons SCC was exposed under the core Kubernetes API group. That exposure is deprecated and will be removed in a future release - users should instead use the security.openshift.io group to manage SecurityContextConstraints.</p><p>Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).</p><h3>Type</h3><p><b>object</b></p><h2>1.9. SERVICEACCOUNT [V1]</h2><h3>Description</h3><p>ServiceAccount binds together: * a name, understood by users, and perhaps by peripheral systems, for an identity * a principal that can be authenticated and authorized * a set of secrets</p><p>Type</p><p><b>object</b></p>\n<h1>CHAPTER 2. CERTIFICATESIGNINGREQUEST<br/>[CERTIFICATES.K8S.IO/V1]</h1>\n\n<h2>Description</h2>\n\n<p>CertificateSigningRequest objects provide a mechanism to obtain x509 certificates by submitting a certificate signing request, and having it asynchronously approved and issued.</p>\n\n<p>Kubelets use this API to obtain: 1. client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client-kubelet\" signerName). 2. serving certificates for TLS endpoints kube-apiserver can connect to securely (with the \"kubernetes.io/kubelet-serving\" signerName).</p>\n\n<p>This API can be used to request client certificates to authenticate to kube-apiserver (with the \"kubernetes.io/kube-apiserver-client\" signerName), or to obtain certificates from custom non-Kubernetes signers.</p>\n\n<h2>Type</h2>\n\n<p><b>object</b></p>\n\n<h2>Required</h2>\n\n<ul>\n<li>• <b>spec</b></li>\n</ul>\n\n<h2>2.1. SPECIFICATION</h2>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>apiVersion</b></td>\n<td><b>string</b></td>\n<td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</a></td>\n</tr>\n<tr>\n<td><b>kind</b></td>\n<td><b>string</b></td>\n<td>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: <a href=\"https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds\">https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</a></td>\n</tr>\n<tr>\n<td><b>metadata</b></td>\n<td><b>ObjectMeta</b></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>spec</b></td>\n<td><b>object</b></td>\n<td>CertificateSigningRequestSpec contains the certificate request.</td>\n</tr>\n<tr>\n<td><b>status</b></td>\n<td><b>object</b></td>\n<td>CertificateSigningRequestStatus contains conditions used to indicate approved/denied/failed status of the request, and the issued certificate.</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.1.1. .spec</h3>\n\n<h4>Description</h4>\n\n<p>CertificateSigningRequestSpec contains the certificate request.</p>\n\n<h4>Type</h4>\n\n<p><b>object</b></p>\n\n<h4>Required</h4>\n\n<ul>\n<li>• <b>request</b></li>\n<li>• <b>signerName</b></li>\n</ul>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th data-bbox=\"88 46 363 83\">Property</th>\n<th data-bbox=\"363 46 636 83\">Type</th>\n<th data-bbox=\"636 46 908 83\">Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td data-bbox=\"88 83 363 708\"><b>expirationSeconds</b></td>\n<td data-bbox=\"363 83 636 708\"><b>integer</b></td>\n<td data-bbox=\"636 83 908 708\">\n<p>expirationSeconds is the requested duration of validity of the issued certificate. The certificate signer may issue a certificate with a different validity duration so a client must check the delta between the notBefore and and notAfter fields in the issued certificate to determine the actual duration.</p>\n<p>The v1.22+ in-tree implementations of the well-known Kubernetes signers will honor this field as long as the requested duration is not greater than the maximum duration they will honor per the --cluster-signing-duration CLI flag to the Kubernetes controller manager.</p>\n<p>Certificate signers may not honor this field for various reasons:</p>\n<ol>\n<li>1. Old signer that is unaware of the field (such as the in-tree implementations prior to v1.22)</li>\n<li>2. Signer whose configured maximum is shorter than the requested duration</li>\n<li>3. Signer whose configured minimum is longer than the requested duration</li>\n</ol>\n<p>The minimum valid value for expirationSeconds is 600, i.e. 10 minutes.</p>\n</td>\n</tr>\n<tr>\n<td data-bbox=\"88 708 363 811\"><b>extra</b></td>\n<td data-bbox=\"363 708 636 811\"><b>object</b></td>\n<td data-bbox=\"636 708 908 811\">\n<p>extra contains extra attributes of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</p>\n</td>\n</tr>\n<tr>\n<td data-bbox=\"88 811 363 847\"><b>extra{}</b></td>\n<td data-bbox=\"363 811 636 847\"><b>array (string)</b></td>\n<td data-bbox=\"636 811 908 847\"></td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th data-bbox=\"88 48 363 84\">Property</th>\n<th data-bbox=\"363 48 636 84\">Type</th>\n<th data-bbox=\"636 48 908 84\">Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td data-bbox=\"88 84 363 203\"><b>groups</b></td>\n<td data-bbox=\"363 84 636 203\"><b>array (string)</b></td>\n<td data-bbox=\"636 84 908 203\">groups contains group membership of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</td>\n</tr>\n<tr>\n<td data-bbox=\"88 203 363 336\"><b>request</b></td>\n<td data-bbox=\"363 203 636 336\"><b>string</b></td>\n<td data-bbox=\"636 203 908 336\">request contains an x509 certificate signing request encoded in a \"CERTIFICATE REQUEST\" PEM block. When serialized as JSON or YAML, the data is additionally base64-encoded.</td>\n</tr>\n<tr>\n<td data-bbox=\"88 336 363 946\"><b>signerName</b></td>\n<td data-bbox=\"363 336 636 946\"><b>string</b></td>\n<td data-bbox=\"636 336 908 946\">\n<p>signerName indicates the requested signer, and is a qualified name.</p>\n<p>List/watch requests for CertificateSigningRequests can filter on this field using a \"spec.signerName=NAME\" fieldSelector.</p>\n<p>Well-known Kubernetes signers are: 1. \"kubernetes.io/kube-apiserver-client\": issues client certificates that can be used to authenticate to kube-apiserver. Requests for this signer are never auto-approved by kube-controller-manager, can be issued by the \"csrsigning\" controller in kube-controller-manager. 2. \"kubernetes.io/kube-apiserver-client-kubelet\": issues client certificates that kubelets use to authenticate to kube-apiserver. Requests for this signer can be auto-approved by the \"csrapproving\" controller in kube-controller-manager, and can be issued by the \"csrsigning\" controller in kube-controller-manager. 3. \"kubernetes.io/kubelet-serving\" issues serving certificates that kubelets use to serve TLS endpoints, which kube-apiserver can connect to securely. Requests for this signer are never auto-approved by kube-controller-</p>\n</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th data-bbox=\"91 48 364 84\">Property</th>\n<th data-bbox=\"364 48 637 84\">Type</th>\n<th data-bbox=\"637 48 908 84\">Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td data-bbox=\"91 84 364 554\"></td>\n<td data-bbox=\"364 84 637 554\"></td>\n<td data-bbox=\"637 84 908 554\">\n<p>manager, and can be issued by the \"CertSigning\" controller in kube-controller-manager.</p>\n<p>More details are available at <a href=\"https://k8s.io/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers\">https://k8s.io/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers</a></p>\n<p>Custom signerNames can also be specified. The signer defines: 1. Trust distribution: how trust (CA bundles) are distributed. 2. Permitted subjects: and behavior when a disallowed subject is requested. 3. Required, permitted, or forbidden x509 extensions in the request (including whether subjectAltNames are allowed, which types, restrictions on allowed values) and behavior when a disallowed extension is requested. 4. Required, permitted, or forbidden key usages / extended key usages. 5. Expiration/certificate lifetime: whether it is fixed by the signer, configurable by the admin. 6. Whether or not requests for CA certificates are allowed.</p>\n</td>\n</tr>\n<tr>\n<td data-bbox=\"91 554 364 656\"><b>uid</b></td>\n<td data-bbox=\"364 554 637 656\"><b>string</b></td>\n<td data-bbox=\"637 554 908 656\">\n<p>uid contains the uid of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</p>\n</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>usages</b></td>\n<td><b>array (string)</b></td>\n<td>\n<p>usages specifies a set of key usages requested in the issued certificate.</p>\n<p>Requests for TLS client certificates typically request: \"digital signature\", \"key encipherment\", \"client auth\".</p>\n<p>Requests for TLS serving certificates typically request: \"key encipherment\", \"digital signature\", \"server auth\".</p>\n<p>Valid values are: \"signing\", \"digital signature\", \"content commitment\", \"key encipherment\", \"key agreement\", \"data encipherment\", \"cert sign\", \"crl sign\", \"encipher only\", \"decipher only\", \"any\", \"server auth\", \"client auth\", \"code signing\", \"email protection\", \"s/mime\", \"ipsec end system\", \"ipsec tunnel\", \"ipsec user\", \"timestamping\", \"ocsp signing\", \"microsoft sgc\", \"netscape sgc\"</p>\n</td>\n</tr>\n<tr>\n<td><b>username</b></td>\n<td><b>string</b></td>\n<td>\n<p>username contains the name of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</p>\n</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.1.2. .spec.extra</h3>\n\n<h4>Description</h4>\n\n<p>extra contains extra attributes of the user that created the CertificateSigningRequest. Populated by the API server on creation and immutable.</p>\n\n<h4>Type</h4>\n\n<p><b>object</b></p>\n\n<h3>2.1.3. .status</h3>\n\n<h4>Description</h4>\n\n<p>CertificateSigningRequestStatus contains conditions used to indicate approved/denied/failed status of the request, and the issued certificate.</p>\n\n<h4>Type</h4>\n\n<p><b>object</b></p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th data-bbox=\"88 46 363 84\">Property</th>\n<th data-bbox=\"363 46 636 84\">Type</th>\n<th data-bbox=\"636 46 908 84\">Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td data-bbox=\"88 84 363 908\"><b>certificate</b></td>\n<td data-bbox=\"363 84 636 908\"><b>string</b></td>\n<td data-bbox=\"636 84 908 908\">\n<p>certificate is populated with an issued certificate by the signer after an Approved condition is present. This field is set via the /status subresource. Once populated, this field is immutable.</p>\n<p>If the certificate signing request is denied, a condition of type \"Denied\" is added and this field remains empty. If the signer cannot issue the certificate, a condition of type \"Failed\" is added and this field remains empty.</p>\n<p>Validation requirements: 1. certificate must contain one or more PEM blocks. 2. All PEM blocks must have the \"CERTIFICATE\" label, contain no headers, and the encoded data must be a BER-encoded ASN.1 Certificate structure as described in section 4 of RFC5280. 3. Non-PEM content may appear before or after the \"CERTIFICATE\" PEM blocks and is unvalidated, to allow for explanatory text as described in section 5.2 of RFC7468.</p>\n<p>If more than one PEM block is present, and the definition of the requested spec.signerName does not indicate otherwise, the first block is the issued certificate, and subsequent blocks should be treated as intermediate certificates and presented in TLS handshakes.</p>\n<p>The certificate is encoded in PEM format.</p>\n<p>When serialized as JSON or YAML, the data is additionally base64-encoded, so it consists of:</p>\n<pre>base64( -----BEGIN\nCERTIFICATE----- ... -----END\nCERTIFICATE----- )</pre>\n</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>conditions</b></td>\n<td><b>array</b></td>\n<td>conditions applied to the request. Known conditions are \"Approved\", \"Denied\", and \"Failed\".</td>\n</tr>\n<tr>\n<td><b>conditions[]</b></td>\n<td><b>object</b></td>\n<td>CertificateSigningRequestCondition describes a condition of a CertificateSigningRequest object</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.1.4. .status.conditions</h3>\n\n<h4>Description</h4>\n\n<p>conditions applied to the request. Known conditions are \"Approved\", \"Denied\", and \"Failed\".</p>\n\n<h4>Type</h4>\n\n<p><b>array</b></p>\n\n<h3>2.1.5. .status.conditions[]</h3>\n\n<h4>Description</h4>\n\n<p>CertificateSigningRequestCondition describes a condition of a CertificateSigningRequest object</p>\n\n<h4>Type</h4>\n\n<p><b>object</b></p>\n\n<h4>Required</h4>\n\n<ul>\n<li>• <b>type</b></li>\n<li>• <b>status</b></li>\n</ul>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>lastTransitionTime</b></td>\n<td><b>Time</b></td>\n<td>lastTransitionTime is the time the condition last transitioned from one status to another. If unset, when a new condition type is added or an existing condition's status is changed, the server defaults this to the current time.</td>\n</tr>\n<tr>\n<td><b>lastUpdateTime</b></td>\n<td><b>Time</b></td>\n<td>lastUpdateTime is the time of the last update to this condition</td>\n</tr>\n<tr>\n<td><b>message</b></td>\n<td><b>string</b></td>\n<td>message contains a human readable message with details about the request state</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Property</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>reason</b></td>\n<td><b>string</b></td>\n<td>reason indicates a brief reason for the request state</td>\n</tr>\n<tr>\n<td><b>status</b></td>\n<td><b>string</b></td>\n<td>status of the condition, one of True, False, Unknown. Approved, Denied, and Failed conditions may not be \"False\" or \"Unknown\".</td>\n</tr>\n<tr>\n<td><b>type</b></td>\n<td><b>string</b></td>\n<td>\n<p>type of the condition. Known conditions are \"Approved\", \"Denied\", and \"Failed\".</p>\n<p>An \"Approved\" condition is added via the /approval subresource, indicating the request was approved and should be issued by the signer.</p>\n<p>A \"Denied\" condition is added via the /approval subresource, indicating the request was denied and should not be issued by the signer.</p>\n<p>A \"Failed\" condition is added via the /status subresource, indicating the signer failed to issue the certificate.</p>\n<p>Approved and Denied conditions are mutually exclusive. Approved, Denied, and Failed conditions cannot be removed once added.</p>\n<p>Only one condition of a given type is allowed.</p>\n</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2. API ENDPOINTS</h2>\n\n<p>The following API endpoints are available:</p>\n\n<ul style=\"list-style-type: none;\">\n<li>• <b>/apis/certificates.k8s.io/v1/certificatesigningrequests</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>DELETE</b>: delete collection of CertificateSigningRequest</li>\n<li>◦ <b>GET</b>: list or watch objects of kind CertificateSigningRequest</li>\n<li>◦ <b>POST</b>: create a CertificateSigningRequest</li>\n</ul>\n</li>\n<li>• <b>/apis/certificates.k8s.io/v1/watch/certificatesigningrequests</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>GET</b>: watch individual changes to a list of CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead</li>\n</ul>\n</li>\n</ul>\n\n<p>watch parameter with a list operation instead.</p>\n\n<ul style=\"list-style-type: none;\">\n<li>• <b>/apis/certificates.k8s.io/v1/certificatesigningrequests/{name}</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>DELETE</b>: delete a CertificateSigningRequest</li>\n<li>◦ <b>GET</b>: read the specified CertificateSigningRequest</li>\n<li>◦ <b>PATCH</b>: partially update the specified CertificateSigningRequest</li>\n<li>◦ <b>PUT</b>: replace the specified CertificateSigningRequest</li>\n</ul>\n</li>\n<li>• <b>/apis/certificates.k8s.io/v1/watch/certificatesigningrequests/{name}</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>GET</b>: watch changes to an object of kind CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</li>\n</ul>\n</li>\n<li>• <b>/apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/status</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>GET</b>: read status of the specified CertificateSigningRequest</li>\n<li>◦ <b>PATCH</b>: partially update status of the specified CertificateSigningRequest</li>\n<li>◦ <b>PUT</b>: replace status of the specified CertificateSigningRequest</li>\n</ul>\n</li>\n<li>• <b>/apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/approval</b>\n<ul style=\"list-style-type: none;\">\n<li>◦ <b>GET</b>: read approval of the specified CertificateSigningRequest</li>\n<li>◦ <b>PATCH</b>: partially update approval of the specified CertificateSigningRequest</li>\n<li>◦ <b>PUT</b>: replace approval of the specified CertificateSigningRequest</li>\n</ul>\n</li>\n</ul>\n\n<h3>2.2.1. /apis/certificates.k8s.io/v1/certificatesigningrequests</h3>\n\n<p>HTTP method</p>\n\n<p><b>DELETE</b></p>\n\n<p>Description</p>\n\n<p>delete collection of CertificateSigningRequest</p>\n\n<p>Table 2.1. Query parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n\n<p>Table 2.2. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n<b>HTTP method</b><b>GET</b><b>Description</b>\n<p>list or watch objects of kind CertificateSigningRequest</p>\n<b>Table 2.3. HTTP responses</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>CertificateSigningRequestList</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n<b>HTTP method</b><b>POST</b><b>Description</b>\n<p>create a CertificateSigningRequest</p>\n<b>Table 2.4. Query parameters</b>\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are:\n<ul>\n<li>- Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23.</li>\n<li>- Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+.</li>\n<li>- Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>\nTable 2.5. Body parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>CertificateSigningRequest</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\nTable 2.6. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>CertificateSigningRequest</b> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><b>CertificateSigningRequest</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>CertificateSigningRequest</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.2. /apis/certificates.k8s.io/v1/watch/certificatesigningrequests</h3>\n\n<h4>HTTP method</h4>\n\n<p><b>GET</b></p>\n\n<h4>Description</h4>\n\n<p>watch individual changes to a list of CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead.</p>\nTable 2.7. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>WatchEvent</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.3. /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}</h3>\nTable 2.8. Global path parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the CertificateSigningRequest</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>DELETE</b></p>\n\n<p>Description</p>\n\n<p>delete a CertificateSigningRequest</p>\nTable 2.9. Query parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\nTable 2.10. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>202 - Accepted</td>\n<td><b>Status</b> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<p>HTTP method</p>\n\n<p><b>GET</b></p>\n\n<p>Description</p>\n\n<p>read the specified CertificateSigningRequest</p>\nTable 2.11. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\nHTTP method<b>PATCH</b>Description\n<p>partially update the specified CertificateSigningRequest</p>\nTable 2.12. Query parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\nTable 2.13. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>HTTP method</h3>\n\n<h4>PUT</h4>\n\n<h3>Description</h3>\n\n<p>replace the specified CertificateSigningRequest</p>\n\n<p>Table 2.14. Query parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\n<p>Table 2.15. Body parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>CertificateSigningRequest</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\n<p>Table 2.16. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.4. /apis/certificates.k8s.io/v1/watch/certificatesigningrequests/{name}</h2>\n\n<p>Table 2.17. Global path parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the CertificateSigningRequest</td>\n</tr>\n</tbody>\n</table>\n\n<h3>HTTP method</h3>\n\n<p><b>GET</b></p>\n\n<h3>Description</h3>\n\n<p>watch changes to an object of kind CertificateSigningRequest. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.</p>\n\n<p>Table 2.18. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">WatchEvent</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.5. /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/status</h2>\n\n<p>Table 2.19. Global path parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the CertificateSigningRequest</td>\n</tr>\n</tbody>\n</table>\n\n<h3>HTTP method</h3>\n\n<p><b>GET</b></p>\n\n<h3>Description</h3>\n\n<p>read status of the specified CertificateSigningRequest</p>\n\n<p>Table 2.20. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h2>HTTP method</h2>\n\n<h3>PATCH</h3>\n\n<h4>Description</h4>\n\n<p>partially update status of the specified CertificateSigningRequest</p>\n\n<p>Table 2.21. Query parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\n<p>Table 2.22. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>HTTP method</h3>\n\n<h4>PUT</h4>\n\n<h3>Description</h3>\n\n<p>replace status of the specified CertificateSigningRequest</p>\n\n<p>Table 2.23. Query parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</td>\n</tr>\n</tbody>\n</table>\n\n<p>Table 2.24. Body parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>body</b></td>\n<td><b>CertificateSigningRequest</b> schema</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\n<p>Table 2.25. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.6. /apis/certificates.k8s.io/v1/certificatesigningrequests/{name}/approval</h2>\n\n<p>Table 2.26. Global path parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>name</b></td>\n<td><b>string</b></td>\n<td>name of the CertificateSigningRequest</td>\n</tr>\n</tbody>\n</table>\n\n<h3>HTTP method</h3>\n\n<p><b>GET</b></p>\n\n<h3>Description</h3>\n\n<p>read approval of the specified CertificateSigningRequest</p>\n\n<p>Table 2.27. HTTP responses</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\n\n<h3>HTTP method</h3>\n\n<p><b>PATCH</b></p>\n\n<h3>Description</h3>\n\n<p>partially update approval of the specified CertificateSigningRequest</p>\n\n<p>Table 2.28. Query parameters</p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>fieldValidation</b></td>\n<td><b>string</b></td>\n<td>fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are:\n<ul>\n<li>- Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23.</li>\n<li>- Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+.</li>\n<li>- Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>\nTable 2.29. HTTP responses\n<table border=\"1\">\n<thead>\n<tr>\n<th>HTTP code</th>\n<th>Response body</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>200 - OK</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>201 - Created</td>\n<td><a href=\"#\">CertificateSigningRequest</a> schema</td>\n</tr>\n<tr>\n<td>401 - Unauthorized</td>\n<td>Empty</td>\n</tr>\n</tbody>\n</table>\nHTTP method<b>PUT</b>Description\n<p>replace approval of the specified CertificateSigningRequest</p>\nTable 2.30. Query parameters\n<table border=\"1\">\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Type</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><b>dryRun</b></td>\n<td><b>string</b></td>\n<td>When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are:\n<ul>\n<li>- All: all dry run stages will be processed</li>\n</ul>\n</td>\n</tr>\n</tbody>\n</table>"},"page_stats":{"kind":"list like","value":[{"page_number":1,"error":false,"token_count":241,"num_chunks":5},{"page_number":2,"error":false,"token_count":48,"num_chunks":1},{"page_number":3,"error":false,"token_count":84,"num_chunks":2},{"page_number":4,"error":false,"token_count":587,"num_chunks":11},{"page_number":5,"error":false,"token_count":1949,"num_chunks":4},{"page_number":6,"error":false,"token_count":1730,"num_chunks":3},{"page_number":7,"error":false,"token_count":110,"num_chunks":2},{"page_number":8,"error":false,"token_count":1303,"num_chunks":27},{"page_number":9,"error":false,"token_count":1341,"num_chunks":29},{"page_number":10,"error":false,"token_count":147,"num_chunks":4},{"page_number":11,"error":false,"token_count":1024,"num_chunks":13},{"page_number":12,"error":false,"token_count":648,"num_chunks":11},{"page_number":13,"error":false,"token_count":748,"num_chunks":3},{"page_number":14,"error":false,"token_count":773,"num_chunks":3},{"page_number":15,"error":false,"token_count":648,"num_chunks":3},{"page_number":16,"error":false,"token_count":910,"num_chunks":13},{"page_number":17,"error":false,"token_count":620,"num_chunks":3},{"page_number":18,"error":false,"token_count":1065,"num_chunks":16},{"page_number":19,"error":false,"token_count":790,"num_chunks":6},{"page_number":20,"error":false,"token_count":1096,"num_chunks":12},{"page_number":21,"error":false,"token_count":900,"num_chunks":15},{"page_number":22,"error":false,"token_count":1038,"num_chunks":12},{"page_number":23,"error":false,"token_count":1191,"num_chunks":19},{"page_number":24,"error":false,"token_count":997,"num_chunks":12},{"page_number":25,"error":false,"token_count":989,"num_chunks":12},{"page_number":26,"error":false,"token_count":1300,"num_chunks":20},{"page_number":27,"error":false,"token_count":1009,"num_chunks":11},{"page_number":28,"error":false,"token_count":981,"num_chunks":12},{"page_number":29,"error":false,"token_count":1214,"num_chunks":18},{"page_number":30,"error":false,"token_count":965,"num_chunks":11}],"string":"[\n {\n \"page_number\": 1,\n \"error\": false,\n \"token_count\": 241,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 2,\n \"error\": false,\n \"token_count\": 48,\n \"num_chunks\": 1\n },\n {\n \"page_number\": 3,\n \"error\": false,\n \"token_count\": 84,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 4,\n \"error\": false,\n \"token_count\": 587,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 5,\n \"error\": false,\n \"token_count\": 1949,\n \"num_chunks\": 4\n },\n {\n \"page_number\": 6,\n \"error\": false,\n \"token_count\": 1730,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 7,\n \"error\": false,\n \"token_count\": 110,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 8,\n \"error\": false,\n \"token_count\": 1303,\n \"num_chunks\": 27\n },\n {\n \"page_number\": 9,\n \"error\": false,\n \"token_count\": 1341,\n \"num_chunks\": 29\n },\n {\n \"page_number\": 10,\n \"error\": false,\n \"token_count\": 147,\n \"num_chunks\": 4\n },\n {\n \"page_number\": 11,\n \"error\": false,\n \"token_count\": 1024,\n \"num_chunks\": 13\n },\n {\n \"page_number\": 12,\n \"error\": false,\n \"token_count\": 648,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 13,\n \"error\": false,\n \"token_count\": 748,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 14,\n \"error\": false,\n \"token_count\": 773,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 15,\n \"error\": false,\n \"token_count\": 648,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 16,\n \"error\": false,\n \"token_count\": 910,\n \"num_chunks\": 13\n },\n {\n \"page_number\": 17,\n \"error\": false,\n \"token_count\": 620,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 18,\n \"error\": false,\n \"token_count\": 1065,\n \"num_chunks\": 16\n },\n {\n \"page_number\": 19,\n \"error\": false,\n \"token_count\": 790,\n \"num_chunks\": 6\n },\n {\n \"page_number\": 20,\n \"error\": false,\n \"token_count\": 1096,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 21,\n \"error\": false,\n \"token_count\": 900,\n \"num_chunks\": 15\n },\n {\n \"page_number\": 22,\n \"error\": false,\n \"token_count\": 1038,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 23,\n \"error\": false,\n \"token_count\": 1191,\n \"num_chunks\": 19\n },\n {\n \"page_number\": 24,\n \"error\": false,\n \"token_count\": 997,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 25,\n \"error\": false,\n \"token_count\": 989,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 26,\n \"error\": false,\n \"token_count\": 1300,\n \"num_chunks\": 20\n },\n {\n \"page_number\": 27,\n \"error\": false,\n \"token_count\": 1009,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 28,\n \"error\": false,\n \"token_count\": 981,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 29,\n \"error\": false,\n \"token_count\": 1214,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 30,\n \"error\": false,\n \"token_count\": 965,\n \"num_chunks\": 11\n }\n]","isConversational":false}}},{"rowIdx":96,"cells":{"source_id":{"kind":"string","value":"OpenShift_Container_Platform-4.21-Serverless-en-US"},"pdf_url":{"kind":"string","value":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/serverless/OpenShift_Container_Platform-4.21-Serverless-en-US.pdf"},"status":{"kind":"string","value":"success"},"processed_at":{"kind":"string","value":"2026-04-15T18:37:30.775362+00:00"},"elapsed_seconds":{"kind":"number","value":12,"string":"12"},"num_pages":{"kind":"number","value":7,"string":"7"},"num_pages_processed":{"kind":"number","value":7,"string":"7"},"max_pages_per_paper":{"kind":"number","value":30,"string":"30"},"pdf_exceeds_page_limit":{"kind":"bool","value":false,"string":"false"},"failed_pages":{"kind":"list like","value":[],"string":"[]","isConversational":false},"prompt_type":{"kind":"string","value":"ocr_layout"},"model_id":{"kind":"string","value":"datalab-to/chandra-ocr-2"},"script_version":{"kind":"timestamp","value":"2026-04-15T00:00:00","string":"2026-04-15T00:00:00"},"markdown":{"kind":"string","value":"# OpenShift Container Platform 4.21\n\n## Serverless\n\nOpenShift Serverless installation, usage, and release notes# OpenShift Container Platform 4.21 Serverless\n\n---\n\nOpenShift Serverless installation, usage, and release notes## Legal Notice\n\nCopyright © Red Hat.\n\nExcept as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.\n\nRed Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.\n\nRed Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.\n\nLinux ® is the registered trademark of Linus Torvalds in the United States and other countries.\n\nXFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.\n\nThe OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.\n\nAll other trademarks are the property of their respective owners.\n\n## Abstract\n\nThis document provides information on how to use OpenShift Serverless in OpenShift Container Platform.## Table of Contents\n\n<table><tr><td><b>CHAPTER 1. ABOUT SERVERLESS</b> .....</td><td><b>3</b></td></tr><tr><td> 1.1. OPENSHIFT SERVERLESS OVERVIEW</td><td>3</td></tr></table># CHAPTER 1. ABOUT SERVERLESS\n\n## 1.1. OPENSHIFT SERVERLESS OVERVIEW\n\nOpenShift Serverless provides Kubernetes native building blocks that enable developers to create and deploy serverless, event-driven applications on OpenShift Container Platform. OpenShift Serverless is based on the open source [Knative project](#), which provides portability and consistency for hybrid and multi-cloud environments by enabling an enterprise-grade serverless platform.\n\n### NOTE\n\nBecause OpenShift Serverless releases on a different cadence from OpenShift Container Platform, the OpenShift Serverless documentation is now available as a separate documentation set at [Red Hat OpenShift Serverless](#)."},"html":{"kind":"string","value":"<h1>OpenShift Container Platform 4.21</h1><h2>Serverless</h2><p>OpenShift Serverless installation, usage, and release notes</p><h1>OpenShift Container Platform 4.21 Serverless</h1><hr/><p>OpenShift Serverless installation, usage, and release notes</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.</p><p>Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.</p><p>Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.</p><p>Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.</p><p>XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.</p><p>The OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.</p><p>All other trademarks are the property of their respective owners.</p><h2>Abstract</h2><p>This document provides information on how to use OpenShift Serverless in OpenShift Container Platform.</p><h2>Table of Contents</h2><table><tr><td><b>CHAPTER 1. ABOUT SERVERLESS</b> .....</td><td><b>3</b></td></tr><tr><td> 1.1. OPENSHIFT SERVERLESS OVERVIEW</td><td>3</td></tr></table><h1>CHAPTER 1. ABOUT SERVERLESS</h1><h2>1.1. OPENSHIFT SERVERLESS OVERVIEW</h2><p>OpenShift Serverless provides Kubernetes native building blocks that enable developers to create and deploy serverless, event-driven applications on OpenShift Container Platform. OpenShift Serverless is based on the open source <a href=\"#\">Knative project</a>, which provides portability and consistency for hybrid and multi-cloud environments by enabling an enterprise-grade serverless platform.</p><h3>NOTE</h3><p>Because OpenShift Serverless releases on a different cadence from OpenShift Container Platform, the OpenShift Serverless documentation is now available as a separate documentation set at <a href=\"#\">Red Hat OpenShift Serverless</a>.</p>"},"page_stats":{"kind":"list like","value":[{"page_number":1,"error":false,"token_count":247,"num_chunks":5},{"page_number":2,"error":false,"token_count":48,"num_chunks":1},{"page_number":3,"error":false,"token_count":90,"num_chunks":2},{"page_number":4,"error":false,"token_count":589,"num_chunks":11},{"page_number":5,"error":false,"token_count":207,"num_chunks":4},{"page_number":6,"error":false,"token_count":81,"num_chunks":2},{"page_number":7,"error":false,"token_count":432,"num_chunks":8}],"string":"[\n {\n \"page_number\": 1,\n \"error\": false,\n \"token_count\": 247,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 2,\n \"error\": false,\n \"token_count\": 48,\n \"num_chunks\": 1\n },\n {\n \"page_number\": 3,\n \"error\": false,\n \"token_count\": 90,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 4,\n \"error\": false,\n \"token_count\": 589,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 5,\n \"error\": false,\n \"token_count\": 207,\n \"num_chunks\": 4\n },\n {\n \"page_number\": 6,\n \"error\": false,\n \"token_count\": 81,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 7,\n \"error\": false,\n \"token_count\": 432,\n \"num_chunks\": 8\n }\n]","isConversational":false}}},{"rowIdx":97,"cells":{"source_id":{"kind":"string","value":"OpenShift_Container_Platform-4.21-Service_Mesh-en-US"},"pdf_url":{"kind":"string","value":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/service_mesh/OpenShift_Container_Platform-4.21-Service_Mesh-en-US.pdf"},"status":{"kind":"string","value":"success"},"processed_at":{"kind":"string","value":"2026-04-15T18:38:52.437517+00:00"},"elapsed_seconds":{"kind":"number","value":81.66,"string":"81.66"},"num_pages":{"kind":"number","value":351,"string":"351"},"num_pages_processed":{"kind":"number","value":30,"string":"30"},"max_pages_per_paper":{"kind":"number","value":30,"string":"30"},"pdf_exceeds_page_limit":{"kind":"bool","value":true,"string":"true"},"failed_pages":{"kind":"list like","value":[],"string":"[]","isConversational":false},"prompt_type":{"kind":"string","value":"ocr_layout"},"model_id":{"kind":"string","value":"datalab-to/chandra-ocr-2"},"script_version":{"kind":"timestamp","value":"2026-04-15T00:00:00","string":"2026-04-15T00:00:00"},"markdown":{"kind":"string","value":"# OpenShift Container Platform 4.21\n\n## Service Mesh\n\nService Mesh installation, usage, and release notes# OpenShift Container Platform 4.21 Service Mesh\n\n---\n\nService Mesh installation, usage, and release notes## Legal Notice\n\nCopyright © Red Hat.\n\nExcept as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.\n\nRed Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.\n\nRed Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.\n\nLinux ® is the registered trademark of Linus Torvalds in the United States and other countries.\n\nXFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.\n\nThe OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.\n\nAll other trademarks are the property of their respective owners.\n\n## Abstract\n\nThis document provides information on how to use Service Mesh in OpenShift Container Platform.# Table of Contents\n\n<table>\n<tr>\n<td><b>CHAPTER 1. SERVICE MESH 3.X</b> .....</td>\n<td><b>15</b></td>\n</tr>\n<tr>\n<td> 1.1. SERVICE MESH OVERVIEW</td>\n<td>15</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. SERVICE MESH 2.X</b> .....</td>\n<td><b>16</b></td>\n</tr>\n<tr>\n<td> 2.1. ABOUT OPENSHIFT SERVICE MESH</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.1.1. Introduction to Red Hat OpenShift Service Mesh</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.1.2. Core features</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.2. SERVICE MESH RELEASE NOTES</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.2.1. Red Hat OpenShift Service Mesh version 2.6.11</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.2.1.1. Component updates</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.2.2. Red Hat OpenShift Service Mesh version 2.6.10</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.2.2.1. Component updates</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.2.3. Red Hat OpenShift Service Mesh version 2.6.9</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.2.3.1. Component updates</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.2.4. Red Hat OpenShift Service Mesh version 2.5.12</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.2.4.1. Component updates</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.2.5. Red Hat OpenShift Service Mesh version 2.6.8</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.2.5.1. Component updates</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 2.2.6. Red Hat OpenShift Service Mesh version 2.5.11</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 2.2.6.1. Component updates</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 2.2.7. Red Hat OpenShift Service Mesh version 2.6.7</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 2.2.7.1. Component updates</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 2.2.8. Red Hat OpenShift Service Mesh version 2.5.10</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 2.2.8.1. Component updates</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 2.2.9. Red Hat OpenShift Service Mesh version 2.6.6</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 2.2.9.1. Component updates</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 2.2.9.2. New features</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 2.2.10. Red Hat OpenShift Service Mesh version 2.5.9</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 2.2.10.1. Component updates</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 2.2.11. Red Hat OpenShift Service Mesh version 2.4.15</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 2.2.11.1. Component updates</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 2.2.12. Red Hat OpenShift Service Mesh version 2.6.5</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 2.2.12.1. Component updates</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.12.2. New features</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.12.3. Fixed issues</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.13. Red Hat OpenShift Service Mesh version 2.5.8</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.13.1. Component updates</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.13.2. Fixed issues</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.14. Red Hat OpenShift Service Mesh version 2.4.14</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 2.2.14.1. Component updates</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 2.2.14.2. Fixed issues</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 2.2.15. Red Hat OpenShift Service Mesh version 2.6.4</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 2.2.15.1. Component updates</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 2.2.16. Red Hat OpenShift Service Mesh version 2.5.7</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.2.16.1. Component updates</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.2.17. Red Hat OpenShift Service Mesh version 2.4.13</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.2.17.1. Component updates</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.2.18. Red Hat OpenShift Service Mesh version 2.6.3</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.2.18.1. Component updates</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 2.2.19. Red Hat OpenShift Service Mesh version 2.5.6</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 2.2.19.1. Component updates</td>\n<td>25</td>\n</tr>\n</table>---\n\n<table><tr><td>2.2.20. Red Hat OpenShift Service Mesh version 2.4.12</td><td>25</td></tr><tr><td> 2.2.20.1. Component updates</td><td>25</td></tr><tr><td>2.2.21. Red Hat OpenShift Service Mesh version 2.6.2</td><td>26</td></tr><tr><td> 2.2.21.1. Component updates</td><td>26</td></tr><tr><td> 2.2.21.2. New features</td><td>26</td></tr><tr><td> 2.2.21.3. Fixed issues</td><td>26</td></tr><tr><td>2.2.22. Red Hat OpenShift Service Mesh version 2.5.5</td><td>26</td></tr><tr><td> 2.2.22.1. Component updates</td><td>27</td></tr><tr><td> 2.2.22.2. Fixed issues</td><td>27</td></tr><tr><td>2.2.23. Red Hat OpenShift Service Mesh version 2.4.11</td><td>27</td></tr><tr><td> 2.2.23.1. Component updates</td><td>27</td></tr><tr><td> 2.2.23.2. Fixed issues</td><td>27</td></tr><tr><td>2.2.24. Red Hat OpenShift Service Mesh version 2.6.1</td><td>28</td></tr><tr><td> 2.2.24.1. Component updates</td><td>28</td></tr><tr><td> 2.2.24.2. Fixed issues</td><td>28</td></tr><tr><td>2.2.25. Red Hat OpenShift Service Mesh version 2.5.4</td><td>28</td></tr><tr><td> 2.2.25.1. Component updates</td><td>28</td></tr><tr><td>2.2.26. Red Hat OpenShift Service Mesh version 2.4.10</td><td>29</td></tr><tr><td> 2.2.26.1. Component updates</td><td>29</td></tr><tr><td>2.2.27. Red Hat OpenShift Service Mesh version 2.6.0</td><td>29</td></tr><tr><td> 2.2.27.1. Component updates</td><td>29</td></tr><tr><td> 2.2.27.2. Istio 1.20 support</td><td>29</td></tr><tr><td> 2.2.27.3. Istio and Kiali bundle image name changes</td><td>30</td></tr><tr><td> 2.2.27.4. Integration with Red Hat OpenShift Distributed Tracing Platform and Red Hat build of OpenTelemetry</td><td>30</td></tr><tr><td> 2.2.27.5. Red Hat OpenShift Distributed Tracing Platform (Jaeger) default setting change</td><td>30</td></tr><tr><td> 2.2.27.6. Gateway API use is generally available for Red Hat OpenShift Service Mesh cluster-wide deployments</td><td>31</td></tr><tr><td> 2.2.27.7. Fixed issues</td><td>32</td></tr><tr><td> 2.2.27.8. Kiali known issues</td><td>32</td></tr><tr><td>2.2.28. Red Hat OpenShift Service Mesh version 2.5.3</td><td>32</td></tr><tr><td> 2.2.28.1. Component updates</td><td>32</td></tr><tr><td>2.2.29. Red Hat OpenShift Service Mesh version 2.4.9</td><td>32</td></tr><tr><td> 2.2.29.1. Component updates</td><td>32</td></tr><tr><td>2.2.30. Red Hat OpenShift Service Mesh version 2.5.2</td><td>33</td></tr><tr><td> 2.2.30.1. Component updates</td><td>33</td></tr><tr><td> 2.2.30.2. Fixed issues</td><td>33</td></tr><tr><td>2.2.31. Red Hat OpenShift Service Mesh version 2.4.8</td><td>34</td></tr><tr><td> 2.2.31.1. Component updates</td><td>34</td></tr><tr><td>2.2.32. Red Hat OpenShift Service Mesh version 2.3.12</td><td>34</td></tr><tr><td> 2.2.32.1. Component updates</td><td>34</td></tr><tr><td>2.2.33. Previous releases</td><td>34</td></tr><tr><td> 2.2.33.1. New features Red Hat OpenShift Service Mesh version 2.5.1</td><td>34</td></tr><tr><td> 2.2.33.1.1. Component versions for Red Hat OpenShift Service Mesh version 2.5.1</td><td>35</td></tr><tr><td> 2.2.33.2. New features Red Hat OpenShift Service Mesh version 2.5</td><td>35</td></tr><tr><td> 2.2.33.2.1. Component versions for Red Hat OpenShift Service Mesh version 2.5</td><td>35</td></tr><tr><td> 2.2.33.2.2. Istio 1.18 support</td><td>35</td></tr><tr><td> 2.2.33.2.3. Cluster-Wide mesh migration</td><td>35</td></tr><tr><td> 2.2.33.2.4. Red Hat OpenShift Service Mesh Operator on ARM-based clusters</td><td>36</td></tr><tr><td> 2.2.33.2.5. Integration with Red Hat OpenShift Distributed Tracing Platform (Tempo) Stack</td><td>36</td></tr><tr><td> 2.2.33.2.6. OpenShift Service Mesh Console plugin</td><td>36</td></tr><tr><td> 2.2.33.2.7. Istio OpenShift Routing (IOR) default setting change</td><td>36</td></tr><tr><td> 2.2.33.2.8. Istio proxy concurrency configuration enhancement</td><td>37</td></tr></table>---\n\n<table>\n<tr>\n<td>2.2.33.2.9. Gateway API CRD versions</td>\n<td>37</td>\n</tr>\n<tr>\n<td>2.2.33.3. New features Red Hat OpenShift Service Mesh version 2.4.7</td>\n<td>37</td>\n</tr>\n<tr>\n<td>2.2.33.3.1. Component versions for Red Hat OpenShift Service Mesh version 2.4.7</td>\n<td>38</td>\n</tr>\n<tr>\n<td>2.2.33.4. New features Red Hat OpenShift Service Mesh version 2.4.6</td>\n<td>38</td>\n</tr>\n<tr>\n<td>2.2.33.4.1. Component versions for Red Hat OpenShift Service Mesh version 2.4.6</td>\n<td>38</td>\n</tr>\n<tr>\n<td>2.2.33.5. New features Red Hat OpenShift Service Mesh version 2.4.5</td>\n<td>38</td>\n</tr>\n<tr>\n<td>2.2.33.5.1. Component versions included in Red Hat OpenShift Service Mesh version 2.4.5</td>\n<td>38</td>\n</tr>\n<tr>\n<td>2.2.33.6. New features Red Hat OpenShift Service Mesh version 2.4.4</td>\n<td>39</td>\n</tr>\n<tr>\n<td>2.2.33.6.1. Component versions included in Red Hat OpenShift Service Mesh version 2.4.4</td>\n<td>39</td>\n</tr>\n<tr>\n<td>2.2.33.7. New features Red Hat OpenShift Service Mesh version 2.4.3</td>\n<td>39</td>\n</tr>\n<tr>\n<td>2.2.33.7.1. Component versions included in Red Hat OpenShift Service Mesh version 2.4.3</td>\n<td>39</td>\n</tr>\n<tr>\n<td>2.2.33.7.2. Red Hat OpenShift Service Mesh operator to ARM-based clusters</td>\n<td>39</td>\n</tr>\n<tr>\n<td>2.2.33.7.3. Remote Procedure Calls (gRPC) API support for external authorization configuration</td>\n<td>40</td>\n</tr>\n<tr>\n<td>2.2.33.8. New features Red Hat OpenShift Service Mesh version 2.4.2</td>\n<td>40</td>\n</tr>\n<tr>\n<td>2.2.33.8.1. Component versions included in Red Hat OpenShift Service Mesh version 2.4.2</td>\n<td>40</td>\n</tr>\n<tr>\n<td>2.2.33.9. New features Red Hat OpenShift Service Mesh version 2.4.1</td>\n<td>40</td>\n</tr>\n<tr>\n<td>2.2.33.9.1. Component versions included in Red Hat OpenShift Service Mesh version 2.4.1</td>\n<td>40</td>\n</tr>\n<tr>\n<td>2.2.33.10. New features Red Hat OpenShift Service Mesh version 2.4</td>\n<td>41</td>\n</tr>\n<tr>\n<td>2.2.33.10.1. Component versions included in Red Hat OpenShift Service Mesh version 2.4</td>\n<td>41</td>\n</tr>\n<tr>\n<td>2.2.33.10.2. Cluster-wide deployments</td>\n<td>41</td>\n</tr>\n<tr>\n<td>2.2.33.10.3. Support for discovery selectors</td>\n<td>41</td>\n</tr>\n<tr>\n<td>2.2.33.10.4. Integration with cert-manager istio-csr</td>\n<td>42</td>\n</tr>\n<tr>\n<td>2.2.33.10.5. Integration with external authorization systems</td>\n<td>42</td>\n</tr>\n<tr>\n<td>2.2.33.10.6. Integration with external Prometheus installation</td>\n<td>42</td>\n</tr>\n<tr>\n<td>2.2.33.10.7. Single stack IPv6 support</td>\n<td>42</td>\n</tr>\n<tr>\n<td>2.2.33.10.8. OpenShift Container Platform Gateway API support</td>\n<td>43</td>\n</tr>\n<tr>\n<td>2.2.33.10.9. Enabling OpenShift Container Platform Gateway API</td>\n<td>43</td>\n</tr>\n<tr>\n<td>2.2.33.10.10. Control plane deployment on infrastructure nodes</td>\n<td>43</td>\n</tr>\n<tr>\n<td>2.2.33.10.11. Istio 1.16 support</td>\n<td>43</td>\n</tr>\n<tr>\n<td>2.2.33.11. New features Red Hat OpenShift Service Mesh version 2.3.11</td>\n<td>44</td>\n</tr>\n<tr>\n<td>2.2.33.11.1. Component versions for Red Hat OpenShift Service Mesh version 2.3.11</td>\n<td>44</td>\n</tr>\n<tr>\n<td>2.2.33.12. New features Red Hat OpenShift Service Mesh version 2.3.10</td>\n<td>44</td>\n</tr>\n<tr>\n<td>2.2.33.12.1. Component versions for Red Hat OpenShift Service Mesh version 2.3.10</td>\n<td>44</td>\n</tr>\n<tr>\n<td>2.2.33.13. New features Red Hat OpenShift Service Mesh version 2.3.9</td>\n<td>44</td>\n</tr>\n<tr>\n<td>2.2.33.13.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.9</td>\n<td>44</td>\n</tr>\n<tr>\n<td>2.2.33.14. New features Red Hat OpenShift Service Mesh version 2.3.8</td>\n<td>45</td>\n</tr>\n<tr>\n<td>2.2.33.14.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.8</td>\n<td>45</td>\n</tr>\n<tr>\n<td>2.2.33.15. New features Red Hat OpenShift Service Mesh version 2.3.7</td>\n<td>45</td>\n</tr>\n<tr>\n<td>2.2.33.15.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.7</td>\n<td>45</td>\n</tr>\n<tr>\n<td>2.2.33.16. New features Red Hat OpenShift Service Mesh version 2.3.6</td>\n<td>45</td>\n</tr>\n<tr>\n<td>2.2.33.16.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.6</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.2.33.17. New features Red Hat OpenShift Service Mesh version 2.3.5</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.2.33.17.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.5</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.2.33.18. New features Red Hat OpenShift Service Mesh version 2.3.4</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.2.33.18.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.4</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.2.33.19. New features Red Hat OpenShift Service Mesh version 2.3.3</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.2.33.19.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.3</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.2.33.20. New features Red Hat OpenShift Service Mesh version 2.3.2</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.2.33.20.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.2</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.2.33.21. New features Red Hat OpenShift Service Mesh version 2.3.1</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.2.33.21.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.1</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.2.33.22. New features Red Hat OpenShift Service Mesh version 2.3</td>\n<td>48</td>\n</tr>\n<tr>\n<td>2.2.33.22.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3</td>\n<td>48</td>\n</tr>\n</table><table><tr><td>2.2.33.22.2. New Container Network Interface (CNI) DaemonSet container and ConfigMap</td><td>48</td></tr><tr><td>2.2.33.22.3. Gateway injection support</td><td>48</td></tr><tr><td>2.2.33.22.4. Istio 1.14 Support</td><td>48</td></tr><tr><td>2.2.33.22.5. OpenShift Service Mesh Console</td><td>49</td></tr><tr><td>2.2.33.22.6. Cluster-wide deployment</td><td>49</td></tr><tr><td> 2.2.33.22.6.1. Configuring cluster-wide deployment</td><td>49</td></tr><tr><td>2.2.33.23. New features Red Hat OpenShift Service Mesh version 2.2.12</td><td>50</td></tr><tr><td> 2.2.33.23.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.12</td><td>50</td></tr><tr><td>2.2.33.24. New features Red Hat OpenShift Service Mesh version 2.2.11</td><td>51</td></tr><tr><td> 2.2.33.24.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.11</td><td>51</td></tr><tr><td>2.2.33.25. New features Red Hat OpenShift Service Mesh version 2.2.10</td><td>51</td></tr><tr><td> 2.2.33.25.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.10</td><td>51</td></tr><tr><td>2.2.33.26. New features Red Hat OpenShift Service Mesh version 2.2.9</td><td>51</td></tr><tr><td> 2.2.33.26.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.9</td><td>51</td></tr><tr><td>2.2.33.27. New features Red Hat OpenShift Service Mesh version 2.2.8</td><td>52</td></tr><tr><td> 2.2.33.27.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.8</td><td>52</td></tr><tr><td>2.2.33.28. New features Red Hat OpenShift Service Mesh version 2.2.7</td><td>52</td></tr><tr><td> 2.2.33.28.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.7</td><td>52</td></tr><tr><td>2.2.33.29. New features Red Hat OpenShift Service Mesh version 2.2.6</td><td>52</td></tr><tr><td> 2.2.33.29.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.6</td><td>52</td></tr><tr><td>2.2.33.30. New features Red Hat OpenShift Service Mesh version 2.2.5</td><td>53</td></tr><tr><td> 2.2.33.30.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.5</td><td>53</td></tr><tr><td>2.2.33.31. New features Red Hat OpenShift Service Mesh version 2.2.4</td><td>53</td></tr><tr><td> 2.2.33.31.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.4</td><td>53</td></tr><tr><td>2.2.33.32. New features Red Hat OpenShift Service Mesh version 2.2.3</td><td>53</td></tr><tr><td> 2.2.33.32.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.3</td><td>54</td></tr><tr><td>2.2.33.33. New features Red Hat OpenShift Service Mesh version 2.2.2</td><td>54</td></tr><tr><td> 2.2.33.33.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.2</td><td>54</td></tr><tr><td> 2.2.33.33.2. Copy route labels</td><td>54</td></tr><tr><td>2.2.33.34. New features Red Hat OpenShift Service Mesh version 2.2.1</td><td>54</td></tr><tr><td> 2.2.33.34.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.1</td><td>54</td></tr><tr><td>2.2.33.35. New features Red Hat OpenShift Service Mesh 2.2</td><td>55</td></tr><tr><td> 2.2.33.35.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2</td><td>55</td></tr><tr><td> 2.2.33.35.2. WasmPlugin API</td><td>55</td></tr><tr><td> 2.2.33.35.3. Red Hat OpenShift Service on AWS support</td><td>55</td></tr><tr><td> 2.2.33.35.4. istio-node DaemonSet renamed</td><td>55</td></tr><tr><td> 2.2.33.35.5. Envoy sidecar networking changes</td><td>55</td></tr><tr><td> 2.2.33.35.6. Service Mesh Control Plane 1.1</td><td>55</td></tr><tr><td> 2.2.33.35.7. Istio 1.12 Support</td><td>56</td></tr><tr><td> 2.2.33.35.8. Kubernetes Gateway API</td><td>56</td></tr><tr><td> 2.2.33.35.8.1. Installing the Gateway API CRDs</td><td>56</td></tr><tr><td> 2.2.33.35.8.2. Enabling Kubernetes Gateway API</td><td>56</td></tr><tr><td> 2.2.33.35.8.3. Manually linking an existing gateway to a Gateway resource</td><td>57</td></tr><tr><td>2.2.33.36. New features Red Hat OpenShift Service Mesh 2.1.6</td><td>57</td></tr><tr><td> 2.2.33.36.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.6</td><td>57</td></tr><tr><td>2.2.33.37. New features Red Hat OpenShift Service Mesh 2.1.5.2</td><td>57</td></tr><tr><td> 2.2.33.37.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.5.2</td><td>57</td></tr><tr><td>2.2.33.38. New features Red Hat OpenShift Service Mesh 2.1.5.1</td><td>58</td></tr><tr><td> 2.2.33.38.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.5.1</td><td>58</td></tr><tr><td>2.2.33.39. New features Red Hat OpenShift Service Mesh 2.1.5</td><td>58</td></tr><tr><td> 2.2.33.39.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.5</td><td>58</td></tr><tr><td>2.2.33.40. New features Red Hat OpenShift Service Mesh 2.1.4</td><td>58</td></tr><tr><td> 2.2.33.40.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.4</td><td>59</td></tr></table>---\n\n<table>\n<tr>\n<td>2.2.33.41. New features Red Hat OpenShift Service Mesh 2.1.3</td>\n<td>59</td>\n</tr>\n<tr>\n<td> 2.2.33.41.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.3</td>\n<td>59</td>\n</tr>\n<tr>\n<td>2.2.33.42. New features Red Hat OpenShift Service Mesh 2.1.2.1</td>\n<td>59</td>\n</tr>\n<tr>\n<td> 2.2.33.42.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.2.1</td>\n<td>59</td>\n</tr>\n<tr>\n<td>2.2.33.43. New features Red Hat OpenShift Service Mesh 2.1.2</td>\n<td>60</td>\n</tr>\n<tr>\n<td> 2.2.33.43.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.2</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.2.33.44. New features Red Hat OpenShift Service Mesh 2.1.1</td>\n<td>60</td>\n</tr>\n<tr>\n<td> 2.2.33.44.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.1</td>\n<td>60</td>\n</tr>\n<tr>\n<td> 2.2.33.44.2. Disabling network policies</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.2.33.45. New features and enhancements Red Hat OpenShift Service Mesh 2.1</td>\n<td>61</td>\n</tr>\n<tr>\n<td> 2.2.33.45.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1</td>\n<td>61</td>\n</tr>\n<tr>\n<td> 2.2.33.45.2. Service Mesh Federation</td>\n<td>62</td>\n</tr>\n<tr>\n<td> 2.2.33.45.3. OVN-Kubernetes Container Network Interface (CNI) generally available</td>\n<td>62</td>\n</tr>\n<tr>\n<td> 2.2.33.45.4. Service Mesh WebAssembly (WASM) Extensions</td>\n<td>62</td>\n</tr>\n<tr>\n<td> 2.2.33.45.5. 3scale WebAssembly Adapter (WASM)</td>\n<td>62</td>\n</tr>\n<tr>\n<td> 2.2.33.45.6. Istio 1.9 Support</td>\n<td>62</td>\n</tr>\n<tr>\n<td> 2.2.33.45.7. Improved Service Mesh operator performance</td>\n<td>63</td>\n</tr>\n<tr>\n<td> 2.2.33.45.8. Kiali updates</td>\n<td>63</td>\n</tr>\n<tr>\n<td>2.2.33.46. New features Red Hat OpenShift Service Mesh 2.0.11.1</td>\n<td>63</td>\n</tr>\n<tr>\n<td> 2.2.33.46.1. Component versions included in Red Hat OpenShift Service Mesh version 2.0.11.1</td>\n<td>63</td>\n</tr>\n<tr>\n<td>2.2.33.47. New features Red Hat OpenShift Service Mesh 2.0.11</td>\n<td>64</td>\n</tr>\n<tr>\n<td> 2.2.33.47.1. Component versions included in Red Hat OpenShift Service Mesh version 2.0.11</td>\n<td>64</td>\n</tr>\n<tr>\n<td>2.2.33.48. New features Red Hat OpenShift Service Mesh 2.0.10</td>\n<td>64</td>\n</tr>\n<tr>\n<td> 2.2.33.48.1. Component versions included in Red Hat OpenShift Service Mesh version 2.0.10</td>\n<td>64</td>\n</tr>\n<tr>\n<td>2.2.33.49. New features Red Hat OpenShift Service Mesh 2.0.9</td>\n<td>64</td>\n</tr>\n<tr>\n<td> 2.2.33.49.1. Component versions included in Red Hat OpenShift Service Mesh version 2.0.9</td>\n<td>64</td>\n</tr>\n<tr>\n<td>2.2.33.50. New features Red Hat OpenShift Service Mesh 2.0.8</td>\n<td>65</td>\n</tr>\n<tr>\n<td>2.2.33.51. New features Red Hat OpenShift Service Mesh 2.0.7.1</td>\n<td>65</td>\n</tr>\n<tr>\n<td> 2.2.33.51.1. Change in how Red Hat OpenShift Service Mesh handles URI fragments</td>\n<td>65</td>\n</tr>\n<tr>\n<td> 2.2.33.51.2. Required update for authorization policies</td>\n<td>66</td>\n</tr>\n<tr>\n<td>2.2.33.52. New features Red Hat OpenShift Service Mesh 2.0.7</td>\n<td>67</td>\n</tr>\n<tr>\n<td>2.2.33.53. Red Hat OpenShift Service Mesh on Red Hat OpenShift Dedicated and Microsoft Azure Red Hat OpenShift</td>\n<td>67</td>\n</tr>\n<tr>\n<td>2.2.33.54. New features Red Hat OpenShift Service Mesh 2.0.6</td>\n<td>67</td>\n</tr>\n<tr>\n<td>2.2.33.55. New features Red Hat OpenShift Service Mesh 2.0.5</td>\n<td>67</td>\n</tr>\n<tr>\n<td>2.2.33.56. New features Red Hat OpenShift Service Mesh 2.0.4</td>\n<td>67</td>\n</tr>\n<tr>\n<td> 2.2.33.56.1. Manual updates required by CVE-2021-29492 and CVE-2021-31920</td>\n<td>67</td>\n</tr>\n<tr>\n<td> 2.2.33.56.2. Updating the path normalization configuration</td>\n<td>68</td>\n</tr>\n<tr>\n<td> 2.2.33.56.3. Path normalization configuration examples</td>\n<td>69</td>\n</tr>\n<tr>\n<td> 2.2.33.56.4. Configuring your SMCP for path normalization</td>\n<td>70</td>\n</tr>\n<tr>\n<td> 2.2.33.56.5. Configuring for case normalization</td>\n<td>70</td>\n</tr>\n<tr>\n<td>2.2.33.57. New features Red Hat OpenShift Service Mesh 2.0.3</td>\n<td>71</td>\n</tr>\n<tr>\n<td>2.2.33.58. New features Red Hat OpenShift Service Mesh 2.0.2</td>\n<td>71</td>\n</tr>\n<tr>\n<td>2.2.33.59. New features Red Hat OpenShift Service Mesh 2.0.1</td>\n<td>71</td>\n</tr>\n<tr>\n<td>2.2.33.60. New features Red Hat OpenShift Service Mesh 2.0</td>\n<td>71</td>\n</tr>\n<tr>\n<td>2.2.34. Technology Preview</td>\n<td>72</td>\n</tr>\n<tr>\n<td>2.2.35. Deprecated and removed features</td>\n<td>72</td>\n</tr>\n<tr>\n<td> 2.2.35.1. Deprecated and removed features in Red Hat OpenShift Service Mesh 2.5</td>\n<td>72</td>\n</tr>\n<tr>\n<td> 2.2.35.2. Deprecated and removed features in Red Hat OpenShift Service Mesh 2.4</td>\n<td>73</td>\n</tr>\n<tr>\n<td> 2.2.35.3. Deprecated and removed features in Red Hat OpenShift Service Mesh 2.3</td>\n<td>73</td>\n</tr>\n<tr>\n<td> 2.2.35.4. Deprecated features in Red Hat OpenShift Service Mesh 2.2</td>\n<td>73</td>\n</tr>\n<tr>\n<td> 2.2.35.5. Removed features in Red Hat OpenShift Service Mesh 2.2</td>\n<td>74</td>\n</tr>\n<tr>\n<td> 2.2.35.6. Removed features in Red Hat OpenShift Service Mesh 2.1</td>\n<td>74</td>\n</tr>\n</table>---\n\n<table><tr><td>2.2.35.7. Deprecated features in Red Hat OpenShift Service Mesh 2.0</td><td>74</td></tr><tr><td>2.2.36. Known issues</td><td>74</td></tr><tr><td>2.2.36.1. Service Mesh known issues</td><td>75</td></tr><tr><td>2.2.36.2. Kiali known issues</td><td>78</td></tr><tr><td>2.2.37. Fixed issues</td><td>79</td></tr><tr><td>2.2.37.1. Service Mesh fixed issues</td><td>79</td></tr><tr><td>2.3. UPGRADING SERVICE MESH</td><td>86</td></tr><tr><td>2.3.1. Understanding versioning</td><td>86</td></tr><tr><td>2.3.1.1. How versioning affects Service Mesh upgrades</td><td>86</td></tr><tr><td>2.3.1.2. Understanding Service Mesh versions</td><td>86</td></tr><tr><td>2.3.2. Upgrade considerations</td><td>87</td></tr><tr><td>2.3.2.1. Known issues that may affect upgrade</td><td>87</td></tr><tr><td>2.3.3. Upgrading the Operators</td><td>88</td></tr><tr><td>2.3.4. Upgrading the control plane</td><td>89</td></tr><tr><td>2.3.4.1. Upgrade changes from version 2.5 to version 2.6</td><td>90</td></tr><tr><td>2.3.4.1.1. Red Hat OpenShift Distributed Tracing Platform (Jaeger) default setting change</td><td>90</td></tr><tr><td>2.3.4.1.2. Envoy sidecar container default setting change</td><td>90</td></tr><tr><td>2.3.4.2. Upgrade changes from version 2.4 to version 2.5</td><td>90</td></tr><tr><td>2.3.4.2.1. Istio OpenShift Routing (IOR) default setting change</td><td>90</td></tr><tr><td>2.3.4.2.2. Istio proxy concurrency configuration enhancement</td><td>90</td></tr><tr><td>2.3.4.3. Upgrade changes from version 2.3 to version 2.4</td><td>90</td></tr><tr><td>2.3.4.4. Upgrade changes from version 2.2 to version 2.3</td><td>91</td></tr><tr><td>2.3.4.5. Upgrade changes from version 2.1 to version 2.2</td><td>91</td></tr><tr><td>2.3.4.6. Upgrade changes from version 2.0 to version 2.1</td><td>91</td></tr><tr><td>2.3.4.7. Upgrading the Service Mesh control plane</td><td>92</td></tr><tr><td>2.3.4.8. Migrating Red Hat OpenShift Service Mesh from version 1.1 to version 2.0</td><td>93</td></tr><tr><td>2.3.4.8.1. Upgrading Red Hat OpenShift Service Mesh</td><td>93</td></tr><tr><td>2.3.4.8.2. Configuring the 2.0 ServiceMeshControlPlane</td><td>95</td></tr><tr><td>2.3.4.8.2.1. Architecture changes</td><td>95</td></tr><tr><td>2.3.4.8.2.2. Annotation changes</td><td>96</td></tr><tr><td>2.3.4.8.2.3. Behavioral changes</td><td>96</td></tr><tr><td>2.3.4.8.2.4. Migration details for unsupported resources</td><td>96</td></tr><tr><td>2.3.4.8.2.5. Mixer plugins</td><td>98</td></tr><tr><td>2.3.4.8.2.6. Mutual TLS changes</td><td>98</td></tr><tr><td>2.3.4.8.2.6.1. Other mTLS Examples</td><td>98</td></tr><tr><td>2.3.4.8.3. Configuration recipes</td><td>101</td></tr><tr><td>2.3.4.8.3.1. Mutual TLS in a data plane</td><td>101</td></tr><tr><td>2.3.4.8.3.2. Custom signing key</td><td>101</td></tr><tr><td>2.3.4.8.3.3. Tracing</td><td>101</td></tr><tr><td>2.3.4.8.3.4. Visualization</td><td>102</td></tr><tr><td>2.3.4.8.3.5. Resource utilization and scheduling</td><td>102</td></tr><tr><td>2.3.4.8.4. Next steps for migrating your applications and workloads</td><td>104</td></tr><tr><td>2.3.5. Upgrading the data plane</td><td>104</td></tr><tr><td>2.3.5.1. Updating your applications and workloads</td><td>104</td></tr><tr><td>2.4. UNDERSTANDING SERVICE MESH</td><td>104</td></tr><tr><td>2.4.1. What is Red Hat OpenShift Service Mesh?</td><td>104</td></tr><tr><td>2.4.2. Service Mesh architecture</td><td>105</td></tr><tr><td>2.4.3. Understanding Kiali</td><td>107</td></tr><tr><td>2.4.3.1. Kiali overview</td><td>107</td></tr><tr><td>2.4.3.2. Kiali architecture</td><td>108</td></tr><tr><td>2.4.3.3. Kiali features</td><td>109</td></tr><tr><td>2.4.4. Understanding distributed tracing</td><td>109</td></tr><tr><td>2.4.4.1. Key concepts in distributed tracing</td><td>110</td></tr></table>\n\n------\n\n<table>\n<tr>\n<td>2.4.4.2. Red Hat OpenShift Distributed Tracing Platform architecture</td>\n<td>111</td>\n</tr>\n<tr>\n<td>2.4.4.3. Red Hat OpenShift Distributed Tracing Platform features</td>\n<td>111</td>\n</tr>\n<tr>\n<td>2.4.5. Next steps</td>\n<td>112</td>\n</tr>\n<tr>\n<td>2.5. SERVICE MESH DEPLOYMENT MODELS</td>\n<td>112</td>\n</tr>\n<tr>\n<td>2.5.1. Cluster-Wide (Single Tenant) mesh deployment model</td>\n<td>112</td>\n</tr>\n<tr>\n<td>2.5.2. Multitenant deployment model</td>\n<td>112</td>\n</tr>\n<tr>\n<td>2.5.2.1. About migrating to a cluster-wide mesh</td>\n<td>113</td>\n</tr>\n<tr>\n<td>2.5.2.1.1. Including and excluding namespaces from a cluster-wide mesh by using the web console</td>\n<td>113</td>\n</tr>\n<tr>\n<td>2.5.2.1.2. Including and excluding namespaces from a cluster-wide mesh by using the CLI</td>\n<td>114</td>\n</tr>\n<tr>\n<td>2.5.2.1.3. Defining which namespaces receive sidecar injection in a cluster-wide mesh by using the web console</td>\n<td>116</td>\n</tr>\n<tr>\n<td>2.5.2.1.4. Defining which namespaces receive sidecar injection in a cluster-wide mesh by using the CLI</td>\n<td>117</td>\n</tr>\n<tr>\n<td>2.5.2.1.5. Excluding individual pods from a cluster-wide mesh by using the web console</td>\n<td>118</td>\n</tr>\n<tr>\n<td>2.5.2.1.6. Excluding individual pods from a cluster-wide mesh by using the CLI</td>\n<td>119</td>\n</tr>\n<tr>\n<td>2.5.3. Multimesh or federated deployment model</td>\n<td>120</td>\n</tr>\n<tr>\n<td>2.6. SERVICE MESH AND ISTIO DIFFERENCES</td>\n<td>121</td>\n</tr>\n<tr>\n<td>2.6.1. Differences between Istio and Red Hat OpenShift Service Mesh</td>\n<td>121</td>\n</tr>\n<tr>\n<td>2.6.1.1. Command-line tool</td>\n<td>121</td>\n</tr>\n<tr>\n<td>2.6.1.2. Installation and upgrades</td>\n<td>121</td>\n</tr>\n<tr>\n<td>2.6.1.3. Automatic injection</td>\n<td>121</td>\n</tr>\n<tr>\n<td>2.6.1.4. Istio Role Based Access Control features</td>\n<td>121</td>\n</tr>\n<tr>\n<td>2.6.1.5. OpenSSL</td>\n<td>122</td>\n</tr>\n<tr>\n<td>2.6.1.6. External workloads</td>\n<td>122</td>\n</tr>\n<tr>\n<td>2.6.1.7. Virtual Machine Support</td>\n<td>122</td>\n</tr>\n<tr>\n<td>2.6.1.8. Component modifications</td>\n<td>122</td>\n</tr>\n<tr>\n<td>2.6.1.9. Envoy filters</td>\n<td>123</td>\n</tr>\n<tr>\n<td>2.6.1.10. Envoy services</td>\n<td>123</td>\n</tr>\n<tr>\n<td>2.6.1.11. Istio Container Network Interface (CNI) plugin</td>\n<td>123</td>\n</tr>\n<tr>\n<td>2.6.1.12. Global mTLS settings</td>\n<td>123</td>\n</tr>\n<tr>\n<td>2.6.1.13. Gateways</td>\n<td>123</td>\n</tr>\n<tr>\n<td>2.6.1.14. Multicluster configurations</td>\n<td>123</td>\n</tr>\n<tr>\n<td>2.6.1.15. Custom Certificate Signing Requests (CSR)</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.1.16. Routes for Istio Gateways</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.1.16.1. Catch-all domains</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.1.16.2. Subdomains</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.1.16.3. Transport layer security</td>\n<td>124</td>\n</tr>\n<tr>\n<td>Additional resources</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.2. Multitenant installations</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.2.1. Multitenancy versus cluster-wide installations</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.2.2. Cluster scoped resources</td>\n<td>125</td>\n</tr>\n<tr>\n<td>2.6.3. Kiali and service mesh</td>\n<td>125</td>\n</tr>\n<tr>\n<td>2.6.4. Distributed tracing and service mesh</td>\n<td>125</td>\n</tr>\n<tr>\n<td>2.7. PREPARING TO INSTALL SERVICE MESH</td>\n<td>126</td>\n</tr>\n<tr>\n<td>2.7.1. Prerequisites</td>\n<td>126</td>\n</tr>\n<tr>\n<td>2.7.2. Supported configurations</td>\n<td>127</td>\n</tr>\n<tr>\n<td>2.7.2.1. Supported platforms</td>\n<td>127</td>\n</tr>\n<tr>\n<td>2.7.2.2. Unsupported configurations</td>\n<td>127</td>\n</tr>\n<tr>\n<td>2.7.2.3. Supported network configurations</td>\n<td>127</td>\n</tr>\n<tr>\n<td>2.7.2.4. Supported configurations for Service Mesh</td>\n<td>127</td>\n</tr>\n<tr>\n<td>2.7.2.5. Supported configurations for Kiali</td>\n<td>128</td>\n</tr>\n<tr>\n<td>2.7.2.6. Supported configurations for Distributed Tracing</td>\n<td>128</td>\n</tr>\n<tr>\n<td>2.7.2.7. Supported WebAssembly module</td>\n<td>128</td>\n</tr>\n<tr>\n<td>2.7.3. Next steps</td>\n<td>128</td>\n</tr>\n</table><table><tr><td>2.8. INSTALLING THE OPERATORS</td><td>128</td></tr><tr><td> 2.8.1. Service Mesh Operators overview</td><td>129</td></tr><tr><td> 2.8.2. Installing the Operators</td><td>130</td></tr><tr><td> 2.8.3. Configuring the Service Mesh Operator to run on infrastructure nodes</td><td>131</td></tr><tr><td> 2.8.4. Verifying the Service Mesh Operator is running on infrastructure node</td><td>132</td></tr><tr><td> 2.8.5. Next steps</td><td>132</td></tr><tr><td>2.9. CREATING THE SERVICEMESHCONTROLPLANE</td><td>133</td></tr><tr><td> 2.9.1. About ServiceMeshControlPlane</td><td>133</td></tr><tr><td> 2.9.1.1. Deploying the Service Mesh control plane from the web console</td><td>133</td></tr><tr><td> 2.9.1.2. Deploying the Service Mesh control plane using the CLI</td><td>134</td></tr><tr><td> 2.9.1.3. Validating your SMCP installation with the CLI</td><td>135</td></tr><tr><td> 2.9.2. About control plane components and infrastructure nodes</td><td>136</td></tr><tr><td> 2.9.2.1. Configuring all control plane components to run on infrastructure nodes using the web console</td><td>136</td></tr><tr><td> 2.9.2.2. Configuring individual control plane components to run on infrastructure nodes using the web console</td><td>137</td></tr><tr><td> 2.9.2.3. Configuring all control plane components to run on infrastructure nodes using the CLI</td><td>138</td></tr><tr><td> 2.9.2.4. Configuring individual control plane components to run on infrastructure nodes using the CLI</td><td>139</td></tr><tr><td> 2.9.2.5. Verifying the Service Mesh control plane is running on infrastructure nodes</td><td>141</td></tr><tr><td> 2.9.3. About control plane and cluster-wide deployments</td><td>141</td></tr><tr><td> 2.9.3.1. Configuring the control plane for cluster-wide deployment with the web console</td><td>141</td></tr><tr><td> 2.9.3.2. Configuring the control plane for cluster-wide deployment with the CLI</td><td>142</td></tr><tr><td> 2.9.3.3. Customizing the member roll for a cluster-wide mesh</td><td>143</td></tr><tr><td> 2.9.4. Validating your SMCP installation with Kiali</td><td>144</td></tr><tr><td> 2.9.5. Additional resources</td><td>146</td></tr><tr><td> 2.9.6. Next steps</td><td>146</td></tr><tr><td>2.10. ADDING SERVICES TO A SERVICE MESH</td><td>146</td></tr><tr><td> 2.10.1. About adding projects to a service mesh</td><td>147</td></tr><tr><td> 2.10.2. Creating the Red Hat OpenShift Service Mesh member roll</td><td>147</td></tr><tr><td> 2.10.2.1. Creating the member roll from the web console</td><td>147</td></tr><tr><td> 2.10.2.2. Creating the member roll from the CLI</td><td>148</td></tr><tr><td> 2.10.3. About adding projects using the ServiceMeshMemberRoll resource</td><td>149</td></tr><tr><td> 2.10.3.1. Adding or removing projects from the mesh using the ServiceMeshMemberRoll resource with the web console</td><td>150</td></tr><tr><td> 2.10.3.2. Adding or removing projects from the mesh using ServiceMeshMemberRoll resource with the CLI</td><td>151</td></tr><tr><td> 2.10.4. About adding projects using the ServiceMeshMember resource</td><td>152</td></tr><tr><td> 2.10.4.1. Adding a project to the mesh using the ServiceMeshMember resource with the web console</td><td>152</td></tr><tr><td> 2.10.4.2. Adding a project to the mesh using the ServiceMeshMember resource with the CLI</td><td>153</td></tr><tr><td> 2.10.5. About adding projects using label selectors</td><td>155</td></tr><tr><td> 2.10.5.1. Adding a project to the mesh using label selectors with the web console</td><td>155</td></tr><tr><td> 2.10.5.2. Adding a project to the mesh using label selectors with the CLI</td><td>156</td></tr><tr><td> 2.10.6. Bookinfo example application</td><td>157</td></tr><tr><td> 2.10.6.1. Installing the Bookinfo application</td><td>158</td></tr><tr><td> 2.10.6.2. Adding default destination rules</td><td>160</td></tr><tr><td> 2.10.6.3. Verifying the Bookinfo installation</td><td>160</td></tr><tr><td> 2.10.6.4. Removing the Bookinfo application</td><td>162</td></tr><tr><td> 2.10.6.4.1. Delete the Bookinfo project</td><td>162</td></tr><tr><td> 2.10.6.4.2. Remove the Bookinfo project from the Service Mesh member roll</td><td>163</td></tr><tr><td> 2.10.7. Next steps</td><td>163</td></tr><tr><td>2.11. ENABLING SIDECAR INJECTION</td><td>163</td></tr><tr><td> 2.11.1. Prerequisites</td><td>164</td></tr><tr><td> 2.11.2. Enabling automatic sidecar injection</td><td>164</td></tr><tr><td> 2.11.3. Validating sidecar injection</td><td>165</td></tr></table>---\n\n<table>\n<tr>\n<td>2.11.4. Setting proxy environment variables through annotations</td>\n<td>166</td>\n</tr>\n<tr>\n<td>2.11.5. Updating sidecar proxies</td>\n<td>167</td>\n</tr>\n<tr>\n<td>2.11.6. Next steps</td>\n<td>167</td>\n</tr>\n<tr>\n<td>2.12. MANAGING USERS AND PROFILES</td>\n<td>167</td>\n</tr>\n<tr>\n<td>2.12.1. Creating the Red Hat OpenShift Service Mesh members</td>\n<td>167</td>\n</tr>\n<tr>\n<td>2.12.2. Creating Service Mesh control plane profiles</td>\n<td>168</td>\n</tr>\n<tr>\n<td>2.12.2.1. Creating the ConfigMap</td>\n<td>168</td>\n</tr>\n<tr>\n<td>2.12.2.2. Setting the correct network policy</td>\n<td>169</td>\n</tr>\n<tr>\n<td>2.13. SECURITY</td>\n<td>169</td>\n</tr>\n<tr>\n<td>2.13.1. About mutual Transport Layer Security (mTLS)</td>\n<td>170</td>\n</tr>\n<tr>\n<td>2.13.1.1. Enabling strict mTLS across the service mesh</td>\n<td>170</td>\n</tr>\n<tr>\n<td>2.13.1.1.1. Configuring sidecars for incoming connections for specific services</td>\n<td>171</td>\n</tr>\n<tr>\n<td>2.13.1.1.2. Configuring sidecars for outgoing connections</td>\n<td>171</td>\n</tr>\n<tr>\n<td>2.13.1.1.3. Setting the minimum and maximum protocol versions</td>\n<td>172</td>\n</tr>\n<tr>\n<td>2.13.1.2. Validating encryption with Kiali</td>\n<td>173</td>\n</tr>\n<tr>\n<td>2.13.2. Configuring Role Based Access Control (RBAC)</td>\n<td>174</td>\n</tr>\n<tr>\n<td>2.13.2.1. Configure intra-project communication</td>\n<td>175</td>\n</tr>\n<tr>\n<td>2.13.2.1.1. Restrict access to services outside a namespace</td>\n<td>175</td>\n</tr>\n<tr>\n<td>2.13.2.1.2. Creating allow-all and default deny-all authorization policies</td>\n<td>176</td>\n</tr>\n<tr>\n<td>2.13.2.2. Allow or deny access to the ingress gateway</td>\n<td>176</td>\n</tr>\n<tr>\n<td>2.13.2.3. Restrict access with JSON Web Token</td>\n<td>177</td>\n</tr>\n<tr>\n<td>2.13.3. Configuring cipher suites and ECDH curves</td>\n<td>177</td>\n</tr>\n<tr>\n<td>2.13.4. Configuring JSON Web Key Sets resolver certificate authority</td>\n<td>178</td>\n</tr>\n<tr>\n<td>2.13.5. Adding an external certificate authority key and certificate</td>\n<td>179</td>\n</tr>\n<tr>\n<td>2.13.5.1. Adding an existing certificate and key</td>\n<td>180</td>\n</tr>\n<tr>\n<td>2.13.5.2. Verifying your certificates</td>\n<td>181</td>\n</tr>\n<tr>\n<td>2.13.5.3. Removing the certificates</td>\n<td>182</td>\n</tr>\n<tr>\n<td>2.13.6. About integrating Service Mesh with cert-manager and istio-csr</td>\n<td>182</td>\n</tr>\n<tr>\n<td>2.13.6.1. Installing cert-manager</td>\n<td>183</td>\n</tr>\n<tr>\n<td>2.13.7. Additional resources</td>\n<td>187</td>\n</tr>\n<tr>\n<td>2.14. MANAGING TRAFFIC IN YOUR SERVICE MESH</td>\n<td>187</td>\n</tr>\n<tr>\n<td>2.14.1. Using gateways</td>\n<td>187</td>\n</tr>\n<tr>\n<td>2.14.1.1. Enabling gateway injection</td>\n<td>189</td>\n</tr>\n<tr>\n<td>2.14.1.2. Deploying automatic gateway injection</td>\n<td>189</td>\n</tr>\n<tr>\n<td>2.14.1.3. Managing ingress traffic</td>\n<td>192</td>\n</tr>\n<tr>\n<td>2.14.1.3.1. Determining the ingress IP and ports</td>\n<td>192</td>\n</tr>\n<tr>\n<td>2.14.1.3.1.1. Determining ingress ports with a load balancer</td>\n<td>192</td>\n</tr>\n<tr>\n<td>2.14.1.3.1.2. Determining ingress ports without a load balancer</td>\n<td>193</td>\n</tr>\n<tr>\n<td>2.14.1.4. Configuring an ingress gateway</td>\n<td>193</td>\n</tr>\n<tr>\n<td>2.14.2. Understanding automatic routes</td>\n<td>195</td>\n</tr>\n<tr>\n<td>2.14.2.1. Routes with subdomains</td>\n<td>195</td>\n</tr>\n<tr>\n<td>2.14.2.2. Creating subdomain routes</td>\n<td>196</td>\n</tr>\n<tr>\n<td>2.14.2.3. Route labels and annotations</td>\n<td>196</td>\n</tr>\n<tr>\n<td>2.14.2.4. Disabling automatic route creation</td>\n<td>197</td>\n</tr>\n<tr>\n<td>2.14.2.4.1. Disabling automatic route creation for specific cases</td>\n<td>197</td>\n</tr>\n<tr>\n<td>2.14.2.4.2. Disabling automatic route creation for all cases</td>\n<td>197</td>\n</tr>\n<tr>\n<td>2.14.3. Understanding service entries</td>\n<td>197</td>\n</tr>\n<tr>\n<td>2.14.4. Using VirtualServices</td>\n<td>198</td>\n</tr>\n<tr>\n<td>2.14.4.1. Configuring VirtualServices</td>\n<td>199</td>\n</tr>\n<tr>\n<td>2.14.4.2. VirtualService configuration reference</td>\n<td>199</td>\n</tr>\n<tr>\n<td>2.14.5. Understanding destination rules</td>\n<td>200</td>\n</tr>\n<tr>\n<td>2.14.6. Understanding network policies</td>\n<td>201</td>\n</tr>\n<tr>\n<td>2.14.6.1. Disabling automatic NetworkPolicy creation</td>\n<td>201</td>\n</tr>\n</table><table><tr><td>2.14.7. Configuring sidecars for traffic management</td><td>202</td></tr><tr><td>2.14.8. Routing Tutorial</td><td>203</td></tr><tr><td> 2.14.8.1. Bookinfo routing tutorial</td><td>203</td></tr><tr><td> 2.14.8.2. Applying a virtual service</td><td>203</td></tr><tr><td> 2.14.8.3. Testing the new route configuration</td><td>204</td></tr><tr><td> 2.14.8.4. Route based on user identity</td><td>204</td></tr><tr><td>2.15. GATEWAY MIGRATION</td><td>205</td></tr><tr><td> 2.15.1. About gateway migration</td><td>205</td></tr><tr><td> 2.15.2. Migrate from SMCP-Defined gateways to gateway injection</td><td>205</td></tr><tr><td> 2.15.3. Additional resources</td><td>208</td></tr><tr><td>2.16. ROUTE MIGRATION</td><td>208</td></tr><tr><td> 2.16.1. Migrating from Istio OpenShift Routing to explicitly-managed routes</td><td>208</td></tr><tr><td> 2.16.2. Additional resources</td><td>209</td></tr><tr><td>2.17. METRICS, LOGS, AND TRACES</td><td>209</td></tr><tr><td> 2.17.1. Discovering console addresses</td><td>209</td></tr><tr><td> 2.17.2. Accessing the Kiali console</td><td>211</td></tr><tr><td> 2.17.3. Viewing service mesh data in the Kiali console</td><td>212</td></tr><tr><td> 2.17.3.1. Changing graph layouts in Kiali</td><td>212</td></tr><tr><td> 2.17.3.2. Viewing logs in the Kiali console</td><td>213</td></tr><tr><td> 2.17.3.3. Viewing metrics in the Kiali console</td><td>214</td></tr><tr><td> 2.17.4. Distributed tracing</td><td>215</td></tr><tr><td> 2.17.4.1. Configuring the Red Hat OpenShift Distributed Tracing Platform and the Red Hat build of OpenTelemetry</td><td>215</td></tr><tr><td> 2.17.4.1.1. Configuring the OpenTelemetryCollector in a mTLS encrypted Service Mesh member namespace</td><td>218</td></tr><tr><td> 2.17.4.1.2. Configuring the Red Hat OpenShift Distributed Tracing Platform in a mTLS encrypted Service Mesh member namespace</td><td>219</td></tr><tr><td> 2.17.4.2. Connecting an existing distributed tracing Jaeger instance</td><td>219</td></tr><tr><td> 2.17.4.3. Adjusting the sampling rate</td><td>220</td></tr><tr><td> 2.17.5. Accessing the Jaeger console</td><td>221</td></tr><tr><td> 2.17.6. Accessing the Grafana console</td><td>223</td></tr><tr><td> 2.17.7. Accessing the Prometheus console</td><td>223</td></tr><tr><td> 2.17.8. Integrating with user-workload monitoring</td><td>223</td></tr><tr><td> 2.17.9. Additional resources</td><td>228</td></tr><tr><td>2.18. PERFORMANCE AND SCALABILITY</td><td>228</td></tr><tr><td> 2.18.1. Setting limits on compute resources</td><td>228</td></tr><tr><td> 2.18.2. Load test results</td><td>230</td></tr><tr><td> 2.18.2.1. Service Mesh Control plane performance</td><td>230</td></tr><tr><td> 2.18.2.2. Data plane performance</td><td>231</td></tr><tr><td> 2.18.2.2.1. CPU and memory consumption</td><td>231</td></tr><tr><td> 2.18.2.2.2. Additional latency</td><td>231</td></tr><tr><td>2.19. CONFIGURING SERVICE MESH FOR PRODUCTION</td><td>231</td></tr><tr><td> 2.19.1. Configuring your ServiceMeshControlPlane resource for production</td><td>232</td></tr><tr><td> 2.19.2. Additional resources</td><td>233</td></tr><tr><td>2.20. CONNECTING SERVICE MESHES</td><td>233</td></tr><tr><td> 2.20.1. Federation overview</td><td>233</td></tr><tr><td> 2.20.2. Federation features</td><td>233</td></tr><tr><td> 2.20.3. Federation security</td><td>234</td></tr><tr><td> 2.20.4. Federation limitations</td><td>234</td></tr><tr><td> 2.20.5. Federation prerequisites</td><td>234</td></tr><tr><td> 2.20.6. Planning your mesh federation</td><td>235</td></tr><tr><td> 2.20.7. Mesh federation across clusters</td><td>236</td></tr><tr><td> 2.20.7.1. Exposing the federation ingress on clusters running on bare metal</td><td>236</td></tr></table>---\n\n<table>\n<tr>\n<td>2.20.7.2. Exposing the federation ingress on clusters running on IBM Power and IBM Z</td>\n<td>236</td>\n</tr>\n<tr>\n<td>2.20.7.3. Exposing the federation ingress on Amazon Web Services (AWS)</td>\n<td>236</td>\n</tr>\n<tr>\n<td>2.20.7.4. Exposing the federation ingress on Azure</td>\n<td>236</td>\n</tr>\n<tr>\n<td>2.20.7.5. Exposing the federation ingress on Google Cloud</td>\n<td>237</td>\n</tr>\n<tr>\n<td>2.20.8. Federation implementation checklist</td>\n<td>237</td>\n</tr>\n<tr>\n<td>2.20.9. Configuring a Service Mesh control plane for federation</td>\n<td>237</td>\n</tr>\n<tr>\n<td>2.20.9.1. Understanding federation gateways</td>\n<td>239</td>\n</tr>\n<tr>\n<td>2.20.9.2. Understanding federation trust domain parameters</td>\n<td>243</td>\n</tr>\n<tr>\n<td>2.20.10. Joining a federated mesh</td>\n<td>244</td>\n</tr>\n<tr>\n<td>2.20.10.1. Creating a ServiceMeshPeer resource</td>\n<td>247</td>\n</tr>\n<tr>\n<td>2.20.11. Exporting a service from a federated mesh</td>\n<td>249</td>\n</tr>\n<tr>\n<td>2.20.11.1. Creating an ExportedServiceSet</td>\n<td>253</td>\n</tr>\n<tr>\n<td>2.20.12. Importing a service into a federated mesh</td>\n<td>255</td>\n</tr>\n<tr>\n<td>2.20.12.1. Creating an ImportedServiceSet</td>\n<td>258</td>\n</tr>\n<tr>\n<td>2.20.13. Configuring a federated mesh for failover</td>\n<td>259</td>\n</tr>\n<tr>\n<td>2.20.13.1. Configuring an ImportedServiceSet for failover</td>\n<td>260</td>\n</tr>\n<tr>\n<td>2.20.13.2. Configuring a DestinationRule for failover</td>\n<td>261</td>\n</tr>\n<tr>\n<td>2.20.14. Removing a service from the federated mesh</td>\n<td>263</td>\n</tr>\n<tr>\n<td>2.20.14.1. To remove a service from a single mesh</td>\n<td>263</td>\n</tr>\n<tr>\n<td>2.20.14.2. To remove a service from the entire federated mesh</td>\n<td>263</td>\n</tr>\n<tr>\n<td>2.20.15. Removing a mesh from the federated mesh</td>\n<td>263</td>\n</tr>\n<tr>\n<td>2.21. EXTENSIONS</td>\n<td>263</td>\n</tr>\n<tr>\n<td>2.21.1. WebAssembly modules overview</td>\n<td>263</td>\n</tr>\n<tr>\n<td>2.21.2. WasmPlugin container format</td>\n<td>264</td>\n</tr>\n<tr>\n<td>2.21.3. WasmPlugin API reference</td>\n<td>265</td>\n</tr>\n<tr>\n<td>2.21.3.1. Deploying WasmPlugin resources</td>\n<td>270</td>\n</tr>\n<tr>\n<td>2.21.4. ServiceMeshExtension container format</td>\n<td>270</td>\n</tr>\n<tr>\n<td>2.21.5. ServiceMeshExtension reference</td>\n<td>271</td>\n</tr>\n<tr>\n<td>2.21.5.1. Deploying ServiceMeshExtension resources</td>\n<td>273</td>\n</tr>\n<tr>\n<td>2.21.6. Migrating from ServiceMeshExtension to WasmPlugin resources</td>\n<td>274</td>\n</tr>\n<tr>\n<td>2.21.6.1. API changes</td>\n<td>274</td>\n</tr>\n<tr>\n<td>2.21.6.2. Container image format changes</td>\n<td>275</td>\n</tr>\n<tr>\n<td>2.21.6.3. Migrating to WasmPlugin resources</td>\n<td>275</td>\n</tr>\n<tr>\n<td>2.22. OPENSHIFT SERVICE MESH CONSOLE PLUGIN</td>\n<td>276</td>\n</tr>\n<tr>\n<td>2.22.1. About the OpenShift Service Mesh Console plugin</td>\n<td>276</td>\n</tr>\n<tr>\n<td>2.22.2. Installing OpenShift Service Mesh Console plugin using the OpenShift Container Platform web console</td>\n<td>277</td>\n</tr>\n<tr>\n<td>2.22.3. Installing OpenShift Service Mesh Console plugin using the CLI</td>\n<td>278</td>\n</tr>\n<tr>\n<td>2.22.4. Uninstalling OpenShift Service Mesh Console plugin using the OpenShift Container Platform web console</td>\n<td>279</td>\n</tr>\n<tr>\n<td>2.22.5. Uninstalling OpenShift Service Mesh Console plugin using the CLI</td>\n<td>279</td>\n</tr>\n<tr>\n<td>2.22.6. Additional resources</td>\n<td>279</td>\n</tr>\n<tr>\n<td>2.23. USING THE 3SCALE WEBASSEMBLY MODULE</td>\n<td>279</td>\n</tr>\n<tr>\n<td>2.23.1. Compatibility</td>\n<td>280</td>\n</tr>\n<tr>\n<td>2.23.2. Usage as a stand-alone module</td>\n<td>280</td>\n</tr>\n<tr>\n<td>2.23.3. Prerequisites</td>\n<td>280</td>\n</tr>\n<tr>\n<td>2.23.4. Configuring the threescale-wasm-auth module</td>\n<td>280</td>\n</tr>\n<tr>\n<td>2.23.4.1. The WasmPlugin API extension</td>\n<td>280</td>\n</tr>\n<tr>\n<td>2.23.5. Applying 3scale external ServiceEntry objects</td>\n<td>282</td>\n</tr>\n<tr>\n<td>2.23.6. The 3scale WebAssembly module configuration</td>\n<td>284</td>\n</tr>\n<tr>\n<td>2.23.6.1. Configuring the 3scale WebAssembly module</td>\n<td>284</td>\n</tr>\n<tr>\n<td>2.23.6.2. The 3scale WebAssembly module api object</td>\n<td>285</td>\n</tr>\n<tr>\n<td>2.23.6.3. The 3scale WebAssembly module system object</td>\n<td>285</td>\n</tr>\n</table><table>\n<tr><td>2.23.6.4. The 3scale WebAssembly module upstream object</td><td>286</td></tr>\n<tr><td>2.23.6.5. The 3scale WebAssembly module backend object</td><td>287</td></tr>\n<tr><td>2.23.6.6. The 3scale WebAssembly module services object</td><td>288</td></tr>\n<tr><td>2.23.6.7. The 3scale WebAssembly module credentials object</td><td>289</td></tr>\n<tr><td>2.23.6.8. The 3scale WebAssembly module lookup queries</td><td>290</td></tr>\n<tr><td>2.23.6.9. The 3scale WebAssembly module source object</td><td>291</td></tr>\n<tr><td>2.23.6.10. The 3scale WebAssembly module operations object</td><td>292</td></tr>\n<tr><td>2.23.6.11. The 3scale WebAssembly module mapping_rules object</td><td>292</td></tr>\n<tr><td>2.23.6.12. The 3scale WebAssembly module mapping_rule object</td><td>293</td></tr>\n<tr><td>2.23.7. The 3scale WebAssembly module examples for credentials use cases</td><td>295</td></tr>\n<tr><td>2.23.7.1. API key (user_key) in query string parameters</td><td>295</td></tr>\n<tr><td>2.23.7.2. Application ID and key</td><td>295</td></tr>\n<tr><td>2.23.7.3. Authorization header</td><td>296</td></tr>\n<tr><td>2.23.7.4. OpenID Connect (OIDC) use case</td><td>298</td></tr>\n<tr><td>2.23.7.5. Picking up the JWT token from a header</td><td>300</td></tr>\n<tr><td>2.23.8. 3scale WebAssembly module minimal working configuration</td><td>300</td></tr>\n<tr><td>2.24. USING THE 3SCALE ISTIO ADAPTER</td><td>301</td></tr>\n<tr><td>2.24.1. Integrate the 3scale adapter with Red Hat OpenShift Service Mesh</td><td>302</td></tr>\n<tr><td>2.24.1.1. Generating 3scale custom resources</td><td>303</td></tr>\n<tr><td>2.24.1.1.1. Generate templates from URL examples</td><td>304</td></tr>\n<tr><td>2.24.1.2. Generating manifests from a deployed adapter</td><td>305</td></tr>\n<tr><td>2.24.1.3. Routing service traffic through the adapter</td><td>306</td></tr>\n<tr><td>2.24.2. Configure the integration settings in 3scale</td><td>306</td></tr>\n<tr><td>2.24.3. Caching behavior</td><td>307</td></tr>\n<tr><td>2.24.4. Authenticating requests</td><td>307</td></tr>\n<tr><td>2.24.4.1. Applying authentication patterns</td><td>307</td></tr>\n<tr><td>2.24.4.1.1. API key authentication method</td><td>307</td></tr>\n<tr><td>2.24.4.1.2. Application ID and application key pair authentication method</td><td>308</td></tr>\n<tr><td>2.24.4.1.3. OpenID authentication method</td><td>308</td></tr>\n<tr><td>2.24.4.1.4. Hybrid authentication method</td><td>309</td></tr>\n<tr><td>2.24.5. 3scale Adapter metrics</td><td>310</td></tr>\n<tr><td>2.24.6. 3scale backend cache</td><td>310</td></tr>\n<tr><td>2.24.6.1. Advantages of enabling backend cache</td><td>311</td></tr>\n<tr><td>2.24.6.2. Trade-offs for having lower latencies</td><td>311</td></tr>\n<tr><td>2.24.6.3. Backend cache configuration settings</td><td>312</td></tr>\n<tr><td>2.24.7. 3scale Istio Adapter APIcast emulation</td><td>312</td></tr>\n<tr><td>2.24.8. 3scale Istio adapter verification</td><td>312</td></tr>\n<tr><td>2.24.9. 3scale Istio adapter troubleshooting checklist</td><td>313</td></tr>\n<tr><td>2.25. TROUBLESHOOTING YOUR SERVICE MESH</td><td>313</td></tr>\n<tr><td>2.25.1. Understanding Service Mesh versions</td><td>313</td></tr>\n<tr><td>2.25.2. Troubleshooting Operator installation</td><td>314</td></tr>\n<tr><td>2.25.2.1. Validating Operator installation</td><td>314</td></tr>\n<tr><td>2.25.2.2. Troubleshooting service mesh Operators</td><td>315</td></tr>\n<tr><td>2.25.2.2.1. Viewing Operator pod logs</td><td>316</td></tr>\n<tr><td>2.25.3. Troubleshooting the control plane</td><td>316</td></tr>\n<tr><td>2.25.3.1. Validating the Service Mesh control plane installation</td><td>316</td></tr>\n<tr><td>2.25.3.1.1. Accessing the Kiali console</td><td>319</td></tr>\n<tr><td>2.25.3.1.2. Accessing the Jaeger console</td><td>320</td></tr>\n<tr><td>2.25.3.2. Troubleshooting the Service Mesh control plane</td><td>321</td></tr>\n<tr><td>2.25.4. Troubleshooting the data plane</td><td>321</td></tr>\n<tr><td>2.25.4.1. Troubleshooting sidecar injection</td><td>322</td></tr>\n<tr><td>2.25.4.1.1. Troubleshooting Istio sidecar injection</td><td>322</td></tr>\n<tr><td>2.25.4.1.2. Troubleshooting Jaeger agent sidecar injection</td><td>322</td></tr>\n</table>---\n\n<table><tr><td>2.26. TROUBLESHOOTING ENVOY PROXY</td><td>322</td></tr><tr><td> 2.26.1. Enabling Envoy access logs</td><td>322</td></tr><tr><td> 2.26.2. Getting support</td><td>323</td></tr><tr><td> 2.26.2.1. About the Red Hat Knowledgebase</td><td>323</td></tr><tr><td> 2.26.2.2. Searching the Red Hat Knowledgebase</td><td>323</td></tr><tr><td> 2.26.2.3. About collecting service mesh data</td><td>324</td></tr><tr><td> 2.26.2.4. Submitting a support case</td><td>325</td></tr><tr><td>2.27. SERVICE MESH CONTROL PLANE CONFIGURATION REFERENCE</td><td>326</td></tr><tr><td> 2.27.1. Service Mesh Control plane parameters</td><td>326</td></tr><tr><td> 2.27.2. spec parameters</td><td>333</td></tr><tr><td> 2.27.2.1. general parameters</td><td>333</td></tr><tr><td> 2.27.2.2. profiles parameters</td><td>334</td></tr><tr><td> 2.27.2.3. techPreview parameters</td><td>334</td></tr><tr><td> 2.27.2.4. tracing parameters</td><td>335</td></tr><tr><td> 2.27.2.5. version parameter</td><td>336</td></tr><tr><td> 2.27.2.6. 3scale configuration</td><td>336</td></tr><tr><td> 2.27.3. status parameter</td><td>338</td></tr><tr><td> 2.27.4. Additional resources</td><td>340</td></tr><tr><td>2.28. KIALI CONFIGURATION REFERENCE</td><td>340</td></tr><tr><td> 2.28.1. Specifying Kiali configuration in the SMCP</td><td>340</td></tr><tr><td> 2.28.2. Specifying Kiali configuration in a Kiali custom resource</td><td>344</td></tr><tr><td>2.29. UNINSTALLING SERVICE MESH</td><td>345</td></tr><tr><td> 2.29.1. Removing the Red Hat OpenShift Service Mesh control plane</td><td>345</td></tr><tr><td> 2.29.1.1. Removing the Service Mesh control plane using the web console</td><td>345</td></tr><tr><td> 2.29.1.2. Removing the Service Mesh control plane using the CLI</td><td>345</td></tr><tr><td> 2.29.2. Removing the installed Operators</td><td>346</td></tr><tr><td> 2.29.2.1. Removing the Operators</td><td>346</td></tr><tr><td> 2.29.3. Clean up Operator resources</td><td>346</td></tr></table># CHAPTER 1. SERVICE MESH 3.X\n\n## 1.1. SERVICE MESH OVERVIEW\n\nRed Hat OpenShift Service Mesh manages and secures communication between microservices by providing traffic management, advanced routing, and load balancing. Red Hat OpenShift Service Mesh also enhances security through features like mutual TLS, and offers observability with metrics, logging, and tracing to monitor and troubleshoot applications.\n\n### NOTE\n\nBecause Red Hat OpenShift Service Mesh 3.0 releases on a different cadence from OpenShift Container Platform, the Service Mesh documentation is available as a separate documentation set at [Red Hat OpenShift Service Mesh](#).## CHAPTER 2. SERVICE MESH 2.X\n\n### 2.1. ABOUT OPENSHIFT SERVICE MESH\n\n#### NOTE\n\nBecause Red Hat OpenShift Service Mesh releases on a different cadence from OpenShift Container Platform and because the Red Hat OpenShift Service Mesh Operator supports deploying multiple versions of the **ServiceMeshControlPlane**, the Service Mesh documentation does not maintain separate documentation sets for minor versions of the product. The current documentation set applies to the most recent version of Service Mesh unless version-specific limitations are called out in a particular topic or for a particular feature.\n\nFor additional information about the Red Hat OpenShift Service Mesh life cycle and supported platforms, refer to the [Platform Life Cycle Policy](#).\n\n#### 2.1.1. Introduction to Red Hat OpenShift Service Mesh\n\nRed Hat OpenShift Service Mesh addresses a variety of problems in a microservice architecture by creating a centralized point of control in an application. It adds a transparent layer on existing distributed applications without requiring any changes to the application code.\n\nMicroservice architectures split the work of enterprise applications into modular services, which can make scaling and maintenance easier. However, as an enterprise application built on a microservice architecture grows in size and complexity, it becomes difficult to understand and manage. Service Mesh can address those architecture problems by capturing or intercepting traffic between services and can modify, redirect, or create new requests to other services.\n\nService Mesh, which is based on the open source [Istio project](#), provides an easy way to create a network of deployed services that provides discovery, load balancing, service-to-service authentication, failure recovery, metrics, and monitoring. A service mesh also provides more complex operational functionality, including A/B testing, canary releases, access control, and end-to-end authentication.\n\n#### NOTE\n\nRed Hat OpenShift Service Mesh 3 is generally available. For more information, see [Red Hat OpenShift Service Mesh 3.0](#).\n\n#### 2.1.2. Core features\n\nRed Hat OpenShift Service Mesh provides a number of key capabilities uniformly across a network of services:\n\n- ● **Traffic Management** – Control the flow of traffic and API calls between services, make calls more reliable, and make the network more robust in the face of adverse conditions.\n- ● **Service Identity and Security** – Provide services in the mesh with a verifiable identity and provide the ability to protect service traffic as it flows over networks of varying degrees of trustworthiness.\n- ● **Policy Enforcement** – Apply organizational policy to the interaction between services, ensure access policies are enforced and resources are fairly distributed among consumers. Policy changes are made by configuring the mesh, not by changing application code.- • **Telemetry** - Gain understanding of the dependencies between services and the nature and flow of traffic between them, providing the ability to quickly identify issues.\n\n## 2.2. SERVICE MESH RELEASE NOTES\n\n### 2.2.1. Red Hat OpenShift Service Mesh version 2.6.11\n\nThis release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.11, and includes the **ServiceMeshControlPlane** resource version updates for 2.6.11.\n\nThis release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.\n\nThe most current version of the Red Hat OpenShift Service Mesh Operator can be used with all supported versions of Service Mesh. The version of Service Mesh is specified using the **ServiceMeshControlPlane**.\n\nYou can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh automatically ensures a compatible version of Kiali.\n\n#### 2.2.1.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.2. Red Hat OpenShift Service Mesh version 2.6.10\n\nThis release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.10, and includes the **ServiceMeshControlPlane** resource version updates for 2.6.10.\n\nThis release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.\n\nYou can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh automatically ensures a compatible version of Kiali.\n\n#### 2.2.2.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.3. Red Hat OpenShift Service Mesh version 2.6.9\n\nThis release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.9, and includes the following **ServiceMeshControlPlane** resource version updates: 2.6.9 and 2.5.12.\n\nThis release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.\n\nYou can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh automatically ensures a compatible version of Kiali.\n\n#### 2.2.3.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.22</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.4. Red Hat OpenShift Service Mesh version 2.5.12\n\nThis release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.9 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).\n\n#### 2.2.4.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.22</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.5. Red Hat OpenShift Service Mesh version 2.6.8This release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.8, and includes the following **ServiceMeshControlPlane** resource version updates: 2.6.8 and 2.5.11.\n\nThis release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.\n\nYou can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh automatically ensures a compatible version of Kiali.\n\n### 2.2.5.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.21</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.6. Red Hat OpenShift Service Mesh version 2.5.11\n\nThis release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.8 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).\n\n### 2.2.6.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.21</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.7. Red Hat OpenShift Service Mesh version 2.6.7\n\nThis release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.7, and includes the following **ServiceMeshControlPlane** resource version updates: 2.6.7 and 2.5.10.\n\nThis release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.\n\nYou can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh is specified by using the **ServiceMeshControlPlane** resource. The version of Service Mesh automatically ensures a compatible version of Kiali.### 2.2.7.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.20</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.8. Red Hat OpenShift Service Mesh version 2.5.10\n\nThis release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.7 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).\n\n#### 2.2.8.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.20</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.9. Red Hat OpenShift Service Mesh version 2.6.6\n\nThis release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.6, and includes the following **ServiceMeshControlPlane** resource version updates: 2.6.6, 2.5.9, and 2.4.15.\n\nThis release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.\n\nYou can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh is specified by using the **ServiceMeshControlPlane** resource. The version of Service Mesh automatically ensures a compatible version of Kiali.\n\n#### 2.2.9.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.19</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.9.2. New features\n\n- • With this update, the Operator for Red Hat OpenShift Service Mesh 2.6 is renamed to Red Hat OpenShift Service Mesh 2 to align with the release of Red Hat OpenShift Service Mesh 3.0 and improve clarity.\n\n## 2.2.10. Red Hat OpenShift Service Mesh version 2.5.9\n\nThis release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.6 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).\n\n### 2.2.10.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.19</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.11. Red Hat OpenShift Service Mesh version 2.4.15\n\nThis release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.6 and is supported on OpenShift Container Platform 4.14 and later.\n\n### 2.2.11.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.16.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.24.12</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.65.20</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.12. Red Hat OpenShift Service Mesh version 2.6.5\n\nThis release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.5, and includes the following **ServiceMeshControlPlane** resource version updates: 2.6.5, 2.5.8, and 2.4.14.This release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.\n\nYou can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh is specified by using the **ServiceMeshControlPlane** resource. The version of Service Mesh automatically ensures a compatible version of Kiali.\n\n### 2.2.12.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.18</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.12.2. New features\n\n- • Red Hat OpenShift Distributed Tracing Platform Stack is now supported on IBM Z.\n\n### 2.2.12.3. Fixed issues\n\n- • [OSSM-8608](#) Previously, terminating a Container Network Interface (CNI) pod during the installation phase while copying binaries could leave Istio-CNI temporary files on the node file system. Repeated occurrences could eventually fill up the node disk space. Now, while terminating a CNI pod during the installation phase, existing temporary files are deleted before copying the CNI binary, ensuring that only one temporary file per Istio version exists on the node file system.\n\n## 2.2.13. Red Hat OpenShift Service Mesh version 2.5.8\n\nThis release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.5 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).\n\n### 2.2.13.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.18</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.13.2. Fixed issues- ● [OSSM-8608](#) Previously, terminating a Container Network Interface (CNI) pod during the installation phase while copying binaries could leave Istio-CNI temporary files on the node file system. Repeated occurrences could eventually fill up the node disk space. Now, while terminating a CNI pod during the installation phase, existing temporary files are deleted before copying the CNI binary, ensuring that only one temporary file per Istio version exists on the node file system.\n\n## 2.2.14. Red Hat OpenShift Service Mesh version 2.4.14\n\nThis release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.5 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).\n\n### 2.2.14.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.16.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.24.12</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.65.19</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.14.2. Fixed issues\n\n- ● [OSSM-8608](#) Previously, terminating a Container Network Interface (CNI) pod during the installation phase while copying binaries could leave Istio-CNI temporary files on the node file system. Repeated occurrences could eventually fill up the node disk space. Now, while terminating a CNI pod during the installation phase, existing temporary files are deleted before copying the CNI binary, ensuring that only one temporary file per Istio version exists on the node file system.\n\n## 2.2.15. Red Hat OpenShift Service Mesh version 2.6.4\n\nThis release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.4, and includes the following **ServiceMeshControlPlane** resource version updates: 2.6.4, 2.5.7, and 2.4.13.\n\nThis release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.\n\nThe most current version of the Kiali Operator provided by Red Hat can be used with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh is specified by using the **ServiceMeshControlPlane** resource. The version of Service Mesh automatically ensures a compatible version of Kiali.\n\n### 2.2.15.1. Component updates<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.17</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.16. Red Hat OpenShift Service Mesh version 2.5.7\n\nThis release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.4 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).\n\n### 2.2.16.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.17</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.17. Red Hat OpenShift Service Mesh version 2.4.13\n\nThis release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.4 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).\n\n### 2.2.17.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.16.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.24.12</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.65.18</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.18. Red Hat OpenShift Service Mesh version 2.6.3\n\nThis release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.3, and includes the following **ServiceMeshControlPlane** resource version updates: 2.6.3, 2.5.6, and 2.4.12.This release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.\n\nThe most current version of the Kiali Operator provided by Red Hat can be used with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh is specified by using the **ServiceMeshControlPlane** resource. The version of Service Mesh automatically ensures a compatible version of Kiali.\n\n### 2.2.18.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.16</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.19. Red Hat OpenShift Service Mesh version 2.5.6\n\nThis release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.3, addresses Common Vulnerabilities and Exposures (CVEs), and is supported on OpenShift Container Platform 4.14 and later.\n\n### 2.2.19.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.16</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.20. Red Hat OpenShift Service Mesh version 2.4.12\n\nThis release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.3, addresses Common Vulnerabilities and Exposures (CVEs), and is supported on OpenShift Container Platform 4.14 and later.\n\n### 2.2.20.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.16.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.24.12</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Kiali Server</td>\n<td>1.65.17</td>\n</tr>\n</tbody>\n</table>\n\n## 2.2.21. Red Hat OpenShift Service Mesh version 2.6.2\n\nThis release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.2, and includes the following **ServiceMeshControlPlane** resource version updates: 2.6.2, 2.5.5 and 2.4.11.\n\nThis release addresses Common Vulnerabilities and Exposures (CVEs), contains bug fixes, and is supported on OpenShift Container Platform 4.14 and later.\n\nThe most current version of the Kiali Operator provided by Red Hat can be used with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh is specified by using the **ServiceMeshControlPlane** resource. The version of Service Mesh automatically ensures a compatible version of Kiali.\n\n### 2.2.21.1. Component updates\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.15</td>\n</tr>\n</tbody>\n</table>\n\n### 2.2.21.2. New features\n\n- • The cert-manager Operator for Red Hat OpenShift is now supported on IBM Power, IBM Z, and IBM® LinuxONE.\n\n### 2.2.21.3. Fixed issues\n\n- • [OSSM-8099](#) Previously, there was an issue supporting persistent session labels when the endpoints were in the draining phase. Now, there is a method of handling draining endpoints for the stateful header sessions.\n- • [OSSM-8001](#) Previously, when **runAsUser** and **runAsGroup** were set to the same value in pods, the proxy GID was incorrectly set to match the container's GID, causing traffic interception issues with iptables rules applied by Istio CNI. Now, containers can have the same value for runAsUser and runAsGroup, and iptables rules apply correctly.\n- • [OSSM-8074](#) Previously, the Kiali Operator failed to install the Kiali server when a Service Mesh had a numeric-only namespace (e.g., **12345**). Now, namespaces with only numerals work correctly.\n\n## 2.2.22. Red Hat OpenShift Service Mesh version 2.5.5"},"html":{"kind":"string","value":"<h1>OpenShift Container Platform 4.21</h1><h2>Service Mesh</h2><p>Service Mesh installation, usage, and release notes</p><h1>OpenShift Container Platform 4.21 Service Mesh</h1><hr/><p>Service Mesh installation, usage, and release notes</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.</p><p>Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.</p><p>Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.</p><p>Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.</p><p>XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.</p><p>The OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.</p><p>All other trademarks are the property of their respective owners.</p><h2>Abstract</h2><p>This document provides information on how to use Service Mesh in OpenShift Container Platform.</p>\n<h1>Table of Contents</h1>\n\n<table>\n<tr>\n<td><b>CHAPTER 1. SERVICE MESH 3.X</b> .....</td>\n<td><b>15</b></td>\n</tr>\n<tr>\n<td> 1.1. SERVICE MESH OVERVIEW</td>\n<td>15</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. SERVICE MESH 2.X</b> .....</td>\n<td><b>16</b></td>\n</tr>\n<tr>\n<td> 2.1. ABOUT OPENSHIFT SERVICE MESH</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.1.1. Introduction to Red Hat OpenShift Service Mesh</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.1.2. Core features</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.2. SERVICE MESH RELEASE NOTES</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.2.1. Red Hat OpenShift Service Mesh version 2.6.11</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.2.1.1. Component updates</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.2.2. Red Hat OpenShift Service Mesh version 2.6.10</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.2.2.1. Component updates</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.2.3. Red Hat OpenShift Service Mesh version 2.6.9</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.2.3.1. Component updates</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.2.4. Red Hat OpenShift Service Mesh version 2.5.12</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.2.4.1. Component updates</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.2.5. Red Hat OpenShift Service Mesh version 2.6.8</td>\n<td>18</td>\n</tr>\n<tr>\n<td> 2.2.5.1. Component updates</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 2.2.6. Red Hat OpenShift Service Mesh version 2.5.11</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 2.2.6.1. Component updates</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 2.2.7. Red Hat OpenShift Service Mesh version 2.6.7</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 2.2.7.1. Component updates</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 2.2.8. Red Hat OpenShift Service Mesh version 2.5.10</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 2.2.8.1. Component updates</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 2.2.9. Red Hat OpenShift Service Mesh version 2.6.6</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 2.2.9.1. Component updates</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 2.2.9.2. New features</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 2.2.10. Red Hat OpenShift Service Mesh version 2.5.9</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 2.2.10.1. Component updates</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 2.2.11. Red Hat OpenShift Service Mesh version 2.4.15</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 2.2.11.1. Component updates</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 2.2.12. Red Hat OpenShift Service Mesh version 2.6.5</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 2.2.12.1. Component updates</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.12.2. New features</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.12.3. Fixed issues</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.13. Red Hat OpenShift Service Mesh version 2.5.8</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.13.1. Component updates</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.13.2. Fixed issues</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 2.2.14. Red Hat OpenShift Service Mesh version 2.4.14</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 2.2.14.1. Component updates</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 2.2.14.2. Fixed issues</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 2.2.15. Red Hat OpenShift Service Mesh version 2.6.4</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 2.2.15.1. Component updates</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 2.2.16. Red Hat OpenShift Service Mesh version 2.5.7</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.2.16.1. Component updates</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.2.17. Red Hat OpenShift Service Mesh version 2.4.13</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.2.17.1. Component updates</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.2.18. Red Hat OpenShift Service Mesh version 2.6.3</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 2.2.18.1. Component updates</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 2.2.19. Red Hat OpenShift Service Mesh version 2.5.6</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 2.2.19.1. Component updates</td>\n<td>25</td>\n</tr>\n</table>\n<hr/><table><tr><td>2.2.20. Red Hat OpenShift Service Mesh version 2.4.12</td><td>25</td></tr><tr><td> 2.2.20.1. Component updates</td><td>25</td></tr><tr><td>2.2.21. Red Hat OpenShift Service Mesh version 2.6.2</td><td>26</td></tr><tr><td> 2.2.21.1. Component updates</td><td>26</td></tr><tr><td> 2.2.21.2. New features</td><td>26</td></tr><tr><td> 2.2.21.3. Fixed issues</td><td>26</td></tr><tr><td>2.2.22. Red Hat OpenShift Service Mesh version 2.5.5</td><td>26</td></tr><tr><td> 2.2.22.1. Component updates</td><td>27</td></tr><tr><td> 2.2.22.2. Fixed issues</td><td>27</td></tr><tr><td>2.2.23. Red Hat OpenShift Service Mesh version 2.4.11</td><td>27</td></tr><tr><td> 2.2.23.1. Component updates</td><td>27</td></tr><tr><td> 2.2.23.2. Fixed issues</td><td>27</td></tr><tr><td>2.2.24. Red Hat OpenShift Service Mesh version 2.6.1</td><td>28</td></tr><tr><td> 2.2.24.1. Component updates</td><td>28</td></tr><tr><td> 2.2.24.2. Fixed issues</td><td>28</td></tr><tr><td>2.2.25. Red Hat OpenShift Service Mesh version 2.5.4</td><td>28</td></tr><tr><td> 2.2.25.1. Component updates</td><td>28</td></tr><tr><td>2.2.26. Red Hat OpenShift Service Mesh version 2.4.10</td><td>29</td></tr><tr><td> 2.2.26.1. Component updates</td><td>29</td></tr><tr><td>2.2.27. Red Hat OpenShift Service Mesh version 2.6.0</td><td>29</td></tr><tr><td> 2.2.27.1. Component updates</td><td>29</td></tr><tr><td> 2.2.27.2. Istio 1.20 support</td><td>29</td></tr><tr><td> 2.2.27.3. Istio and Kiali bundle image name changes</td><td>30</td></tr><tr><td> 2.2.27.4. Integration with Red Hat OpenShift Distributed Tracing Platform and Red Hat build of OpenTelemetry</td><td>30</td></tr><tr><td> 2.2.27.5. Red Hat OpenShift Distributed Tracing Platform (Jaeger) default setting change</td><td>30</td></tr><tr><td> 2.2.27.6. Gateway API use is generally available for Red Hat OpenShift Service Mesh cluster-wide deployments</td><td>31</td></tr><tr><td> 2.2.27.7. Fixed issues</td><td>32</td></tr><tr><td> 2.2.27.8. Kiali known issues</td><td>32</td></tr><tr><td>2.2.28. Red Hat OpenShift Service Mesh version 2.5.3</td><td>32</td></tr><tr><td> 2.2.28.1. Component updates</td><td>32</td></tr><tr><td>2.2.29. Red Hat OpenShift Service Mesh version 2.4.9</td><td>32</td></tr><tr><td> 2.2.29.1. Component updates</td><td>32</td></tr><tr><td>2.2.30. Red Hat OpenShift Service Mesh version 2.5.2</td><td>33</td></tr><tr><td> 2.2.30.1. Component updates</td><td>33</td></tr><tr><td> 2.2.30.2. Fixed issues</td><td>33</td></tr><tr><td>2.2.31. Red Hat OpenShift Service Mesh version 2.4.8</td><td>34</td></tr><tr><td> 2.2.31.1. Component updates</td><td>34</td></tr><tr><td>2.2.32. Red Hat OpenShift Service Mesh version 2.3.12</td><td>34</td></tr><tr><td> 2.2.32.1. Component updates</td><td>34</td></tr><tr><td>2.2.33. Previous releases</td><td>34</td></tr><tr><td> 2.2.33.1. New features Red Hat OpenShift Service Mesh version 2.5.1</td><td>34</td></tr><tr><td> 2.2.33.1.1. Component versions for Red Hat OpenShift Service Mesh version 2.5.1</td><td>35</td></tr><tr><td> 2.2.33.2. New features Red Hat OpenShift Service Mesh version 2.5</td><td>35</td></tr><tr><td> 2.2.33.2.1. Component versions for Red Hat OpenShift Service Mesh version 2.5</td><td>35</td></tr><tr><td> 2.2.33.2.2. Istio 1.18 support</td><td>35</td></tr><tr><td> 2.2.33.2.3. Cluster-Wide mesh migration</td><td>35</td></tr><tr><td> 2.2.33.2.4. Red Hat OpenShift Service Mesh Operator on ARM-based clusters</td><td>36</td></tr><tr><td> 2.2.33.2.5. Integration with Red Hat OpenShift Distributed Tracing Platform (Tempo) Stack</td><td>36</td></tr><tr><td> 2.2.33.2.6. OpenShift Service Mesh Console plugin</td><td>36</td></tr><tr><td> 2.2.33.2.7. Istio OpenShift Routing (IOR) default setting change</td><td>36</td></tr><tr><td> 2.2.33.2.8. Istio proxy concurrency configuration enhancement</td><td>37</td></tr></table>\n<hr/>\n<table>\n<tr>\n<td>2.2.33.2.9. Gateway API CRD versions</td>\n<td>37</td>\n</tr>\n<tr>\n<td>2.2.33.3. New features Red Hat OpenShift Service Mesh version 2.4.7</td>\n<td>37</td>\n</tr>\n<tr>\n<td>2.2.33.3.1. Component versions for Red Hat OpenShift Service Mesh version 2.4.7</td>\n<td>38</td>\n</tr>\n<tr>\n<td>2.2.33.4. New features Red Hat OpenShift Service Mesh version 2.4.6</td>\n<td>38</td>\n</tr>\n<tr>\n<td>2.2.33.4.1. Component versions for Red Hat OpenShift Service Mesh version 2.4.6</td>\n<td>38</td>\n</tr>\n<tr>\n<td>2.2.33.5. New features Red Hat OpenShift Service Mesh version 2.4.5</td>\n<td>38</td>\n</tr>\n<tr>\n<td>2.2.33.5.1. Component versions included in Red Hat OpenShift Service Mesh version 2.4.5</td>\n<td>38</td>\n</tr>\n<tr>\n<td>2.2.33.6. New features Red Hat OpenShift Service Mesh version 2.4.4</td>\n<td>39</td>\n</tr>\n<tr>\n<td>2.2.33.6.1. Component versions included in Red Hat OpenShift Service Mesh version 2.4.4</td>\n<td>39</td>\n</tr>\n<tr>\n<td>2.2.33.7. New features Red Hat OpenShift Service Mesh version 2.4.3</td>\n<td>39</td>\n</tr>\n<tr>\n<td>2.2.33.7.1. Component versions included in Red Hat OpenShift Service Mesh version 2.4.3</td>\n<td>39</td>\n</tr>\n<tr>\n<td>2.2.33.7.2. Red Hat OpenShift Service Mesh operator to ARM-based clusters</td>\n<td>39</td>\n</tr>\n<tr>\n<td>2.2.33.7.3. Remote Procedure Calls (gRPC) API support for external authorization configuration</td>\n<td>40</td>\n</tr>\n<tr>\n<td>2.2.33.8. New features Red Hat OpenShift Service Mesh version 2.4.2</td>\n<td>40</td>\n</tr>\n<tr>\n<td>2.2.33.8.1. Component versions included in Red Hat OpenShift Service Mesh version 2.4.2</td>\n<td>40</td>\n</tr>\n<tr>\n<td>2.2.33.9. New features Red Hat OpenShift Service Mesh version 2.4.1</td>\n<td>40</td>\n</tr>\n<tr>\n<td>2.2.33.9.1. Component versions included in Red Hat OpenShift Service Mesh version 2.4.1</td>\n<td>40</td>\n</tr>\n<tr>\n<td>2.2.33.10. New features Red Hat OpenShift Service Mesh version 2.4</td>\n<td>41</td>\n</tr>\n<tr>\n<td>2.2.33.10.1. Component versions included in Red Hat OpenShift Service Mesh version 2.4</td>\n<td>41</td>\n</tr>\n<tr>\n<td>2.2.33.10.2. Cluster-wide deployments</td>\n<td>41</td>\n</tr>\n<tr>\n<td>2.2.33.10.3. Support for discovery selectors</td>\n<td>41</td>\n</tr>\n<tr>\n<td>2.2.33.10.4. Integration with cert-manager istio-csr</td>\n<td>42</td>\n</tr>\n<tr>\n<td>2.2.33.10.5. Integration with external authorization systems</td>\n<td>42</td>\n</tr>\n<tr>\n<td>2.2.33.10.6. Integration with external Prometheus installation</td>\n<td>42</td>\n</tr>\n<tr>\n<td>2.2.33.10.7. Single stack IPv6 support</td>\n<td>42</td>\n</tr>\n<tr>\n<td>2.2.33.10.8. OpenShift Container Platform Gateway API support</td>\n<td>43</td>\n</tr>\n<tr>\n<td>2.2.33.10.9. Enabling OpenShift Container Platform Gateway API</td>\n<td>43</td>\n</tr>\n<tr>\n<td>2.2.33.10.10. Control plane deployment on infrastructure nodes</td>\n<td>43</td>\n</tr>\n<tr>\n<td>2.2.33.10.11. Istio 1.16 support</td>\n<td>43</td>\n</tr>\n<tr>\n<td>2.2.33.11. New features Red Hat OpenShift Service Mesh version 2.3.11</td>\n<td>44</td>\n</tr>\n<tr>\n<td>2.2.33.11.1. Component versions for Red Hat OpenShift Service Mesh version 2.3.11</td>\n<td>44</td>\n</tr>\n<tr>\n<td>2.2.33.12. New features Red Hat OpenShift Service Mesh version 2.3.10</td>\n<td>44</td>\n</tr>\n<tr>\n<td>2.2.33.12.1. Component versions for Red Hat OpenShift Service Mesh version 2.3.10</td>\n<td>44</td>\n</tr>\n<tr>\n<td>2.2.33.13. New features Red Hat OpenShift Service Mesh version 2.3.9</td>\n<td>44</td>\n</tr>\n<tr>\n<td>2.2.33.13.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.9</td>\n<td>44</td>\n</tr>\n<tr>\n<td>2.2.33.14. New features Red Hat OpenShift Service Mesh version 2.3.8</td>\n<td>45</td>\n</tr>\n<tr>\n<td>2.2.33.14.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.8</td>\n<td>45</td>\n</tr>\n<tr>\n<td>2.2.33.15. New features Red Hat OpenShift Service Mesh version 2.3.7</td>\n<td>45</td>\n</tr>\n<tr>\n<td>2.2.33.15.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.7</td>\n<td>45</td>\n</tr>\n<tr>\n<td>2.2.33.16. New features Red Hat OpenShift Service Mesh version 2.3.6</td>\n<td>45</td>\n</tr>\n<tr>\n<td>2.2.33.16.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.6</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.2.33.17. New features Red Hat OpenShift Service Mesh version 2.3.5</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.2.33.17.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.5</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.2.33.18. New features Red Hat OpenShift Service Mesh version 2.3.4</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.2.33.18.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.4</td>\n<td>46</td>\n</tr>\n<tr>\n<td>2.2.33.19. New features Red Hat OpenShift Service Mesh version 2.3.3</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.2.33.19.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.3</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.2.33.20. New features Red Hat OpenShift Service Mesh version 2.3.2</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.2.33.20.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.2</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.2.33.21. New features Red Hat OpenShift Service Mesh version 2.3.1</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.2.33.21.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3.1</td>\n<td>47</td>\n</tr>\n<tr>\n<td>2.2.33.22. New features Red Hat OpenShift Service Mesh version 2.3</td>\n<td>48</td>\n</tr>\n<tr>\n<td>2.2.33.22.1. Component versions included in Red Hat OpenShift Service Mesh version 2.3</td>\n<td>48</td>\n</tr>\n</table>\n<table><tr><td>2.2.33.22.2. New Container Network Interface (CNI) DaemonSet container and ConfigMap</td><td>48</td></tr><tr><td>2.2.33.22.3. Gateway injection support</td><td>48</td></tr><tr><td>2.2.33.22.4. Istio 1.14 Support</td><td>48</td></tr><tr><td>2.2.33.22.5. OpenShift Service Mesh Console</td><td>49</td></tr><tr><td>2.2.33.22.6. Cluster-wide deployment</td><td>49</td></tr><tr><td> 2.2.33.22.6.1. Configuring cluster-wide deployment</td><td>49</td></tr><tr><td>2.2.33.23. New features Red Hat OpenShift Service Mesh version 2.2.12</td><td>50</td></tr><tr><td> 2.2.33.23.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.12</td><td>50</td></tr><tr><td>2.2.33.24. New features Red Hat OpenShift Service Mesh version 2.2.11</td><td>51</td></tr><tr><td> 2.2.33.24.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.11</td><td>51</td></tr><tr><td>2.2.33.25. New features Red Hat OpenShift Service Mesh version 2.2.10</td><td>51</td></tr><tr><td> 2.2.33.25.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.10</td><td>51</td></tr><tr><td>2.2.33.26. New features Red Hat OpenShift Service Mesh version 2.2.9</td><td>51</td></tr><tr><td> 2.2.33.26.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.9</td><td>51</td></tr><tr><td>2.2.33.27. New features Red Hat OpenShift Service Mesh version 2.2.8</td><td>52</td></tr><tr><td> 2.2.33.27.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.8</td><td>52</td></tr><tr><td>2.2.33.28. New features Red Hat OpenShift Service Mesh version 2.2.7</td><td>52</td></tr><tr><td> 2.2.33.28.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.7</td><td>52</td></tr><tr><td>2.2.33.29. New features Red Hat OpenShift Service Mesh version 2.2.6</td><td>52</td></tr><tr><td> 2.2.33.29.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.6</td><td>52</td></tr><tr><td>2.2.33.30. New features Red Hat OpenShift Service Mesh version 2.2.5</td><td>53</td></tr><tr><td> 2.2.33.30.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.5</td><td>53</td></tr><tr><td>2.2.33.31. New features Red Hat OpenShift Service Mesh version 2.2.4</td><td>53</td></tr><tr><td> 2.2.33.31.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.4</td><td>53</td></tr><tr><td>2.2.33.32. New features Red Hat OpenShift Service Mesh version 2.2.3</td><td>53</td></tr><tr><td> 2.2.33.32.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.3</td><td>54</td></tr><tr><td>2.2.33.33. New features Red Hat OpenShift Service Mesh version 2.2.2</td><td>54</td></tr><tr><td> 2.2.33.33.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.2</td><td>54</td></tr><tr><td> 2.2.33.33.2. Copy route labels</td><td>54</td></tr><tr><td>2.2.33.34. New features Red Hat OpenShift Service Mesh version 2.2.1</td><td>54</td></tr><tr><td> 2.2.33.34.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2.1</td><td>54</td></tr><tr><td>2.2.33.35. New features Red Hat OpenShift Service Mesh 2.2</td><td>55</td></tr><tr><td> 2.2.33.35.1. Component versions included in Red Hat OpenShift Service Mesh version 2.2</td><td>55</td></tr><tr><td> 2.2.33.35.2. WasmPlugin API</td><td>55</td></tr><tr><td> 2.2.33.35.3. Red Hat OpenShift Service on AWS support</td><td>55</td></tr><tr><td> 2.2.33.35.4. istio-node DaemonSet renamed</td><td>55</td></tr><tr><td> 2.2.33.35.5. Envoy sidecar networking changes</td><td>55</td></tr><tr><td> 2.2.33.35.6. Service Mesh Control Plane 1.1</td><td>55</td></tr><tr><td> 2.2.33.35.7. Istio 1.12 Support</td><td>56</td></tr><tr><td> 2.2.33.35.8. Kubernetes Gateway API</td><td>56</td></tr><tr><td> 2.2.33.35.8.1. Installing the Gateway API CRDs</td><td>56</td></tr><tr><td> 2.2.33.35.8.2. Enabling Kubernetes Gateway API</td><td>56</td></tr><tr><td> 2.2.33.35.8.3. Manually linking an existing gateway to a Gateway resource</td><td>57</td></tr><tr><td>2.2.33.36. New features Red Hat OpenShift Service Mesh 2.1.6</td><td>57</td></tr><tr><td> 2.2.33.36.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.6</td><td>57</td></tr><tr><td>2.2.33.37. New features Red Hat OpenShift Service Mesh 2.1.5.2</td><td>57</td></tr><tr><td> 2.2.33.37.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.5.2</td><td>57</td></tr><tr><td>2.2.33.38. New features Red Hat OpenShift Service Mesh 2.1.5.1</td><td>58</td></tr><tr><td> 2.2.33.38.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.5.1</td><td>58</td></tr><tr><td>2.2.33.39. New features Red Hat OpenShift Service Mesh 2.1.5</td><td>58</td></tr><tr><td> 2.2.33.39.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.5</td><td>58</td></tr><tr><td>2.2.33.40. New features Red Hat OpenShift Service Mesh 2.1.4</td><td>58</td></tr><tr><td> 2.2.33.40.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.4</td><td>59</td></tr></table>\n<hr/>\n<table>\n<tr>\n<td>2.2.33.41. New features Red Hat OpenShift Service Mesh 2.1.3</td>\n<td>59</td>\n</tr>\n<tr>\n<td> 2.2.33.41.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.3</td>\n<td>59</td>\n</tr>\n<tr>\n<td>2.2.33.42. New features Red Hat OpenShift Service Mesh 2.1.2.1</td>\n<td>59</td>\n</tr>\n<tr>\n<td> 2.2.33.42.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.2.1</td>\n<td>59</td>\n</tr>\n<tr>\n<td>2.2.33.43. New features Red Hat OpenShift Service Mesh 2.1.2</td>\n<td>60</td>\n</tr>\n<tr>\n<td> 2.2.33.43.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.2</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.2.33.44. New features Red Hat OpenShift Service Mesh 2.1.1</td>\n<td>60</td>\n</tr>\n<tr>\n<td> 2.2.33.44.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1.1</td>\n<td>60</td>\n</tr>\n<tr>\n<td> 2.2.33.44.2. Disabling network policies</td>\n<td>60</td>\n</tr>\n<tr>\n<td>2.2.33.45. New features and enhancements Red Hat OpenShift Service Mesh 2.1</td>\n<td>61</td>\n</tr>\n<tr>\n<td> 2.2.33.45.1. Component versions included in Red Hat OpenShift Service Mesh version 2.1</td>\n<td>61</td>\n</tr>\n<tr>\n<td> 2.2.33.45.2. Service Mesh Federation</td>\n<td>62</td>\n</tr>\n<tr>\n<td> 2.2.33.45.3. OVN-Kubernetes Container Network Interface (CNI) generally available</td>\n<td>62</td>\n</tr>\n<tr>\n<td> 2.2.33.45.4. Service Mesh WebAssembly (WASM) Extensions</td>\n<td>62</td>\n</tr>\n<tr>\n<td> 2.2.33.45.5. 3scale WebAssembly Adapter (WASM)</td>\n<td>62</td>\n</tr>\n<tr>\n<td> 2.2.33.45.6. Istio 1.9 Support</td>\n<td>62</td>\n</tr>\n<tr>\n<td> 2.2.33.45.7. Improved Service Mesh operator performance</td>\n<td>63</td>\n</tr>\n<tr>\n<td> 2.2.33.45.8. Kiali updates</td>\n<td>63</td>\n</tr>\n<tr>\n<td>2.2.33.46. New features Red Hat OpenShift Service Mesh 2.0.11.1</td>\n<td>63</td>\n</tr>\n<tr>\n<td> 2.2.33.46.1. Component versions included in Red Hat OpenShift Service Mesh version 2.0.11.1</td>\n<td>63</td>\n</tr>\n<tr>\n<td>2.2.33.47. New features Red Hat OpenShift Service Mesh 2.0.11</td>\n<td>64</td>\n</tr>\n<tr>\n<td> 2.2.33.47.1. Component versions included in Red Hat OpenShift Service Mesh version 2.0.11</td>\n<td>64</td>\n</tr>\n<tr>\n<td>2.2.33.48. New features Red Hat OpenShift Service Mesh 2.0.10</td>\n<td>64</td>\n</tr>\n<tr>\n<td> 2.2.33.48.1. Component versions included in Red Hat OpenShift Service Mesh version 2.0.10</td>\n<td>64</td>\n</tr>\n<tr>\n<td>2.2.33.49. New features Red Hat OpenShift Service Mesh 2.0.9</td>\n<td>64</td>\n</tr>\n<tr>\n<td> 2.2.33.49.1. Component versions included in Red Hat OpenShift Service Mesh version 2.0.9</td>\n<td>64</td>\n</tr>\n<tr>\n<td>2.2.33.50. New features Red Hat OpenShift Service Mesh 2.0.8</td>\n<td>65</td>\n</tr>\n<tr>\n<td>2.2.33.51. New features Red Hat OpenShift Service Mesh 2.0.7.1</td>\n<td>65</td>\n</tr>\n<tr>\n<td> 2.2.33.51.1. Change in how Red Hat OpenShift Service Mesh handles URI fragments</td>\n<td>65</td>\n</tr>\n<tr>\n<td> 2.2.33.51.2. Required update for authorization policies</td>\n<td>66</td>\n</tr>\n<tr>\n<td>2.2.33.52. New features Red Hat OpenShift Service Mesh 2.0.7</td>\n<td>67</td>\n</tr>\n<tr>\n<td>2.2.33.53. Red Hat OpenShift Service Mesh on Red Hat OpenShift Dedicated and Microsoft Azure Red Hat OpenShift</td>\n<td>67</td>\n</tr>\n<tr>\n<td>2.2.33.54. New features Red Hat OpenShift Service Mesh 2.0.6</td>\n<td>67</td>\n</tr>\n<tr>\n<td>2.2.33.55. New features Red Hat OpenShift Service Mesh 2.0.5</td>\n<td>67</td>\n</tr>\n<tr>\n<td>2.2.33.56. New features Red Hat OpenShift Service Mesh 2.0.4</td>\n<td>67</td>\n</tr>\n<tr>\n<td> 2.2.33.56.1. Manual updates required by CVE-2021-29492 and CVE-2021-31920</td>\n<td>67</td>\n</tr>\n<tr>\n<td> 2.2.33.56.2. Updating the path normalization configuration</td>\n<td>68</td>\n</tr>\n<tr>\n<td> 2.2.33.56.3. Path normalization configuration examples</td>\n<td>69</td>\n</tr>\n<tr>\n<td> 2.2.33.56.4. Configuring your SMCP for path normalization</td>\n<td>70</td>\n</tr>\n<tr>\n<td> 2.2.33.56.5. Configuring for case normalization</td>\n<td>70</td>\n</tr>\n<tr>\n<td>2.2.33.57. New features Red Hat OpenShift Service Mesh 2.0.3</td>\n<td>71</td>\n</tr>\n<tr>\n<td>2.2.33.58. New features Red Hat OpenShift Service Mesh 2.0.2</td>\n<td>71</td>\n</tr>\n<tr>\n<td>2.2.33.59. New features Red Hat OpenShift Service Mesh 2.0.1</td>\n<td>71</td>\n</tr>\n<tr>\n<td>2.2.33.60. New features Red Hat OpenShift Service Mesh 2.0</td>\n<td>71</td>\n</tr>\n<tr>\n<td>2.2.34. Technology Preview</td>\n<td>72</td>\n</tr>\n<tr>\n<td>2.2.35. Deprecated and removed features</td>\n<td>72</td>\n</tr>\n<tr>\n<td> 2.2.35.1. Deprecated and removed features in Red Hat OpenShift Service Mesh 2.5</td>\n<td>72</td>\n</tr>\n<tr>\n<td> 2.2.35.2. Deprecated and removed features in Red Hat OpenShift Service Mesh 2.4</td>\n<td>73</td>\n</tr>\n<tr>\n<td> 2.2.35.3. Deprecated and removed features in Red Hat OpenShift Service Mesh 2.3</td>\n<td>73</td>\n</tr>\n<tr>\n<td> 2.2.35.4. Deprecated features in Red Hat OpenShift Service Mesh 2.2</td>\n<td>73</td>\n</tr>\n<tr>\n<td> 2.2.35.5. Removed features in Red Hat OpenShift Service Mesh 2.2</td>\n<td>74</td>\n</tr>\n<tr>\n<td> 2.2.35.6. Removed features in Red Hat OpenShift Service Mesh 2.1</td>\n<td>74</td>\n</tr>\n</table>\n<hr/><table><tr><td>2.2.35.7. Deprecated features in Red Hat OpenShift Service Mesh 2.0</td><td>74</td></tr><tr><td>2.2.36. Known issues</td><td>74</td></tr><tr><td>2.2.36.1. Service Mesh known issues</td><td>75</td></tr><tr><td>2.2.36.2. Kiali known issues</td><td>78</td></tr><tr><td>2.2.37. Fixed issues</td><td>79</td></tr><tr><td>2.2.37.1. Service Mesh fixed issues</td><td>79</td></tr><tr><td>2.3. UPGRADING SERVICE MESH</td><td>86</td></tr><tr><td>2.3.1. Understanding versioning</td><td>86</td></tr><tr><td>2.3.1.1. How versioning affects Service Mesh upgrades</td><td>86</td></tr><tr><td>2.3.1.2. Understanding Service Mesh versions</td><td>86</td></tr><tr><td>2.3.2. Upgrade considerations</td><td>87</td></tr><tr><td>2.3.2.1. Known issues that may affect upgrade</td><td>87</td></tr><tr><td>2.3.3. Upgrading the Operators</td><td>88</td></tr><tr><td>2.3.4. Upgrading the control plane</td><td>89</td></tr><tr><td>2.3.4.1. Upgrade changes from version 2.5 to version 2.6</td><td>90</td></tr><tr><td>2.3.4.1.1. Red Hat OpenShift Distributed Tracing Platform (Jaeger) default setting change</td><td>90</td></tr><tr><td>2.3.4.1.2. Envoy sidecar container default setting change</td><td>90</td></tr><tr><td>2.3.4.2. Upgrade changes from version 2.4 to version 2.5</td><td>90</td></tr><tr><td>2.3.4.2.1. Istio OpenShift Routing (IOR) default setting change</td><td>90</td></tr><tr><td>2.3.4.2.2. Istio proxy concurrency configuration enhancement</td><td>90</td></tr><tr><td>2.3.4.3. Upgrade changes from version 2.3 to version 2.4</td><td>90</td></tr><tr><td>2.3.4.4. Upgrade changes from version 2.2 to version 2.3</td><td>91</td></tr><tr><td>2.3.4.5. Upgrade changes from version 2.1 to version 2.2</td><td>91</td></tr><tr><td>2.3.4.6. Upgrade changes from version 2.0 to version 2.1</td><td>91</td></tr><tr><td>2.3.4.7. Upgrading the Service Mesh control plane</td><td>92</td></tr><tr><td>2.3.4.8. Migrating Red Hat OpenShift Service Mesh from version 1.1 to version 2.0</td><td>93</td></tr><tr><td>2.3.4.8.1. Upgrading Red Hat OpenShift Service Mesh</td><td>93</td></tr><tr><td>2.3.4.8.2. Configuring the 2.0 ServiceMeshControlPlane</td><td>95</td></tr><tr><td>2.3.4.8.2.1. Architecture changes</td><td>95</td></tr><tr><td>2.3.4.8.2.2. Annotation changes</td><td>96</td></tr><tr><td>2.3.4.8.2.3. Behavioral changes</td><td>96</td></tr><tr><td>2.3.4.8.2.4. Migration details for unsupported resources</td><td>96</td></tr><tr><td>2.3.4.8.2.5. Mixer plugins</td><td>98</td></tr><tr><td>2.3.4.8.2.6. Mutual TLS changes</td><td>98</td></tr><tr><td>2.3.4.8.2.6.1. Other mTLS Examples</td><td>98</td></tr><tr><td>2.3.4.8.3. Configuration recipes</td><td>101</td></tr><tr><td>2.3.4.8.3.1. Mutual TLS in a data plane</td><td>101</td></tr><tr><td>2.3.4.8.3.2. Custom signing key</td><td>101</td></tr><tr><td>2.3.4.8.3.3. Tracing</td><td>101</td></tr><tr><td>2.3.4.8.3.4. Visualization</td><td>102</td></tr><tr><td>2.3.4.8.3.5. Resource utilization and scheduling</td><td>102</td></tr><tr><td>2.3.4.8.4. Next steps for migrating your applications and workloads</td><td>104</td></tr><tr><td>2.3.5. Upgrading the data plane</td><td>104</td></tr><tr><td>2.3.5.1. Updating your applications and workloads</td><td>104</td></tr><tr><td>2.4. UNDERSTANDING SERVICE MESH</td><td>104</td></tr><tr><td>2.4.1. What is Red Hat OpenShift Service Mesh?</td><td>104</td></tr><tr><td>2.4.2. Service Mesh architecture</td><td>105</td></tr><tr><td>2.4.3. Understanding Kiali</td><td>107</td></tr><tr><td>2.4.3.1. Kiali overview</td><td>107</td></tr><tr><td>2.4.3.2. Kiali architecture</td><td>108</td></tr><tr><td>2.4.3.3. Kiali features</td><td>109</td></tr><tr><td>2.4.4. Understanding distributed tracing</td><td>109</td></tr><tr><td>2.4.4.1. Key concepts in distributed tracing</td><td>110</td></tr></table><hr/>\n<hr/>\n<table>\n<tr>\n<td>2.4.4.2. Red Hat OpenShift Distributed Tracing Platform architecture</td>\n<td>111</td>\n</tr>\n<tr>\n<td>2.4.4.3. Red Hat OpenShift Distributed Tracing Platform features</td>\n<td>111</td>\n</tr>\n<tr>\n<td>2.4.5. Next steps</td>\n<td>112</td>\n</tr>\n<tr>\n<td>2.5. SERVICE MESH DEPLOYMENT MODELS</td>\n<td>112</td>\n</tr>\n<tr>\n<td>2.5.1. Cluster-Wide (Single Tenant) mesh deployment model</td>\n<td>112</td>\n</tr>\n<tr>\n<td>2.5.2. Multitenant deployment model</td>\n<td>112</td>\n</tr>\n<tr>\n<td>2.5.2.1. About migrating to a cluster-wide mesh</td>\n<td>113</td>\n</tr>\n<tr>\n<td>2.5.2.1.1. Including and excluding namespaces from a cluster-wide mesh by using the web console</td>\n<td>113</td>\n</tr>\n<tr>\n<td>2.5.2.1.2. Including and excluding namespaces from a cluster-wide mesh by using the CLI</td>\n<td>114</td>\n</tr>\n<tr>\n<td>2.5.2.1.3. Defining which namespaces receive sidecar injection in a cluster-wide mesh by using the web console</td>\n<td>116</td>\n</tr>\n<tr>\n<td>2.5.2.1.4. Defining which namespaces receive sidecar injection in a cluster-wide mesh by using the CLI</td>\n<td>117</td>\n</tr>\n<tr>\n<td>2.5.2.1.5. Excluding individual pods from a cluster-wide mesh by using the web console</td>\n<td>118</td>\n</tr>\n<tr>\n<td>2.5.2.1.6. Excluding individual pods from a cluster-wide mesh by using the CLI</td>\n<td>119</td>\n</tr>\n<tr>\n<td>2.5.3. Multimesh or federated deployment model</td>\n<td>120</td>\n</tr>\n<tr>\n<td>2.6. SERVICE MESH AND ISTIO DIFFERENCES</td>\n<td>121</td>\n</tr>\n<tr>\n<td>2.6.1. Differences between Istio and Red Hat OpenShift Service Mesh</td>\n<td>121</td>\n</tr>\n<tr>\n<td>2.6.1.1. Command-line tool</td>\n<td>121</td>\n</tr>\n<tr>\n<td>2.6.1.2. Installation and upgrades</td>\n<td>121</td>\n</tr>\n<tr>\n<td>2.6.1.3. Automatic injection</td>\n<td>121</td>\n</tr>\n<tr>\n<td>2.6.1.4. Istio Role Based Access Control features</td>\n<td>121</td>\n</tr>\n<tr>\n<td>2.6.1.5. OpenSSL</td>\n<td>122</td>\n</tr>\n<tr>\n<td>2.6.1.6. External workloads</td>\n<td>122</td>\n</tr>\n<tr>\n<td>2.6.1.7. Virtual Machine Support</td>\n<td>122</td>\n</tr>\n<tr>\n<td>2.6.1.8. Component modifications</td>\n<td>122</td>\n</tr>\n<tr>\n<td>2.6.1.9. Envoy filters</td>\n<td>123</td>\n</tr>\n<tr>\n<td>2.6.1.10. Envoy services</td>\n<td>123</td>\n</tr>\n<tr>\n<td>2.6.1.11. Istio Container Network Interface (CNI) plugin</td>\n<td>123</td>\n</tr>\n<tr>\n<td>2.6.1.12. Global mTLS settings</td>\n<td>123</td>\n</tr>\n<tr>\n<td>2.6.1.13. Gateways</td>\n<td>123</td>\n</tr>\n<tr>\n<td>2.6.1.14. Multicluster configurations</td>\n<td>123</td>\n</tr>\n<tr>\n<td>2.6.1.15. Custom Certificate Signing Requests (CSR)</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.1.16. Routes for Istio Gateways</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.1.16.1. Catch-all domains</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.1.16.2. Subdomains</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.1.16.3. Transport layer security</td>\n<td>124</td>\n</tr>\n<tr>\n<td>Additional resources</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.2. Multitenant installations</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.2.1. Multitenancy versus cluster-wide installations</td>\n<td>124</td>\n</tr>\n<tr>\n<td>2.6.2.2. Cluster scoped resources</td>\n<td>125</td>\n</tr>\n<tr>\n<td>2.6.3. Kiali and service mesh</td>\n<td>125</td>\n</tr>\n<tr>\n<td>2.6.4. Distributed tracing and service mesh</td>\n<td>125</td>\n</tr>\n<tr>\n<td>2.7. PREPARING TO INSTALL SERVICE MESH</td>\n<td>126</td>\n</tr>\n<tr>\n<td>2.7.1. Prerequisites</td>\n<td>126</td>\n</tr>\n<tr>\n<td>2.7.2. Supported configurations</td>\n<td>127</td>\n</tr>\n<tr>\n<td>2.7.2.1. Supported platforms</td>\n<td>127</td>\n</tr>\n<tr>\n<td>2.7.2.2. Unsupported configurations</td>\n<td>127</td>\n</tr>\n<tr>\n<td>2.7.2.3. Supported network configurations</td>\n<td>127</td>\n</tr>\n<tr>\n<td>2.7.2.4. Supported configurations for Service Mesh</td>\n<td>127</td>\n</tr>\n<tr>\n<td>2.7.2.5. Supported configurations for Kiali</td>\n<td>128</td>\n</tr>\n<tr>\n<td>2.7.2.6. Supported configurations for Distributed Tracing</td>\n<td>128</td>\n</tr>\n<tr>\n<td>2.7.2.7. Supported WebAssembly module</td>\n<td>128</td>\n</tr>\n<tr>\n<td>2.7.3. Next steps</td>\n<td>128</td>\n</tr>\n</table>\n<table><tr><td>2.8. INSTALLING THE OPERATORS</td><td>128</td></tr><tr><td> 2.8.1. Service Mesh Operators overview</td><td>129</td></tr><tr><td> 2.8.2. Installing the Operators</td><td>130</td></tr><tr><td> 2.8.3. Configuring the Service Mesh Operator to run on infrastructure nodes</td><td>131</td></tr><tr><td> 2.8.4. Verifying the Service Mesh Operator is running on infrastructure node</td><td>132</td></tr><tr><td> 2.8.5. Next steps</td><td>132</td></tr><tr><td>2.9. CREATING THE SERVICEMESHCONTROLPLANE</td><td>133</td></tr><tr><td> 2.9.1. About ServiceMeshControlPlane</td><td>133</td></tr><tr><td> 2.9.1.1. Deploying the Service Mesh control plane from the web console</td><td>133</td></tr><tr><td> 2.9.1.2. Deploying the Service Mesh control plane using the CLI</td><td>134</td></tr><tr><td> 2.9.1.3. Validating your SMCP installation with the CLI</td><td>135</td></tr><tr><td> 2.9.2. About control plane components and infrastructure nodes</td><td>136</td></tr><tr><td> 2.9.2.1. Configuring all control plane components to run on infrastructure nodes using the web console</td><td>136</td></tr><tr><td> 2.9.2.2. Configuring individual control plane components to run on infrastructure nodes using the web console</td><td>137</td></tr><tr><td> 2.9.2.3. Configuring all control plane components to run on infrastructure nodes using the CLI</td><td>138</td></tr><tr><td> 2.9.2.4. Configuring individual control plane components to run on infrastructure nodes using the CLI</td><td>139</td></tr><tr><td> 2.9.2.5. Verifying the Service Mesh control plane is running on infrastructure nodes</td><td>141</td></tr><tr><td> 2.9.3. About control plane and cluster-wide deployments</td><td>141</td></tr><tr><td> 2.9.3.1. Configuring the control plane for cluster-wide deployment with the web console</td><td>141</td></tr><tr><td> 2.9.3.2. Configuring the control plane for cluster-wide deployment with the CLI</td><td>142</td></tr><tr><td> 2.9.3.3. Customizing the member roll for a cluster-wide mesh</td><td>143</td></tr><tr><td> 2.9.4. Validating your SMCP installation with Kiali</td><td>144</td></tr><tr><td> 2.9.5. Additional resources</td><td>146</td></tr><tr><td> 2.9.6. Next steps</td><td>146</td></tr><tr><td>2.10. ADDING SERVICES TO A SERVICE MESH</td><td>146</td></tr><tr><td> 2.10.1. About adding projects to a service mesh</td><td>147</td></tr><tr><td> 2.10.2. Creating the Red Hat OpenShift Service Mesh member roll</td><td>147</td></tr><tr><td> 2.10.2.1. Creating the member roll from the web console</td><td>147</td></tr><tr><td> 2.10.2.2. Creating the member roll from the CLI</td><td>148</td></tr><tr><td> 2.10.3. About adding projects using the ServiceMeshMemberRoll resource</td><td>149</td></tr><tr><td> 2.10.3.1. Adding or removing projects from the mesh using the ServiceMeshMemberRoll resource with the web console</td><td>150</td></tr><tr><td> 2.10.3.2. Adding or removing projects from the mesh using ServiceMeshMemberRoll resource with the CLI</td><td>151</td></tr><tr><td> 2.10.4. About adding projects using the ServiceMeshMember resource</td><td>152</td></tr><tr><td> 2.10.4.1. Adding a project to the mesh using the ServiceMeshMember resource with the web console</td><td>152</td></tr><tr><td> 2.10.4.2. Adding a project to the mesh using the ServiceMeshMember resource with the CLI</td><td>153</td></tr><tr><td> 2.10.5. About adding projects using label selectors</td><td>155</td></tr><tr><td> 2.10.5.1. Adding a project to the mesh using label selectors with the web console</td><td>155</td></tr><tr><td> 2.10.5.2. Adding a project to the mesh using label selectors with the CLI</td><td>156</td></tr><tr><td> 2.10.6. Bookinfo example application</td><td>157</td></tr><tr><td> 2.10.6.1. Installing the Bookinfo application</td><td>158</td></tr><tr><td> 2.10.6.2. Adding default destination rules</td><td>160</td></tr><tr><td> 2.10.6.3. Verifying the Bookinfo installation</td><td>160</td></tr><tr><td> 2.10.6.4. Removing the Bookinfo application</td><td>162</td></tr><tr><td> 2.10.6.4.1. Delete the Bookinfo project</td><td>162</td></tr><tr><td> 2.10.6.4.2. Remove the Bookinfo project from the Service Mesh member roll</td><td>163</td></tr><tr><td> 2.10.7. Next steps</td><td>163</td></tr><tr><td>2.11. ENABLING SIDECAR INJECTION</td><td>163</td></tr><tr><td> 2.11.1. Prerequisites</td><td>164</td></tr><tr><td> 2.11.2. Enabling automatic sidecar injection</td><td>164</td></tr><tr><td> 2.11.3. Validating sidecar injection</td><td>165</td></tr></table>\n<hr/>\n<table>\n<tr>\n<td>2.11.4. Setting proxy environment variables through annotations</td>\n<td>166</td>\n</tr>\n<tr>\n<td>2.11.5. Updating sidecar proxies</td>\n<td>167</td>\n</tr>\n<tr>\n<td>2.11.6. Next steps</td>\n<td>167</td>\n</tr>\n<tr>\n<td>2.12. MANAGING USERS AND PROFILES</td>\n<td>167</td>\n</tr>\n<tr>\n<td>2.12.1. Creating the Red Hat OpenShift Service Mesh members</td>\n<td>167</td>\n</tr>\n<tr>\n<td>2.12.2. Creating Service Mesh control plane profiles</td>\n<td>168</td>\n</tr>\n<tr>\n<td>2.12.2.1. Creating the ConfigMap</td>\n<td>168</td>\n</tr>\n<tr>\n<td>2.12.2.2. Setting the correct network policy</td>\n<td>169</td>\n</tr>\n<tr>\n<td>2.13. SECURITY</td>\n<td>169</td>\n</tr>\n<tr>\n<td>2.13.1. About mutual Transport Layer Security (mTLS)</td>\n<td>170</td>\n</tr>\n<tr>\n<td>2.13.1.1. Enabling strict mTLS across the service mesh</td>\n<td>170</td>\n</tr>\n<tr>\n<td>2.13.1.1.1. Configuring sidecars for incoming connections for specific services</td>\n<td>171</td>\n</tr>\n<tr>\n<td>2.13.1.1.2. Configuring sidecars for outgoing connections</td>\n<td>171</td>\n</tr>\n<tr>\n<td>2.13.1.1.3. Setting the minimum and maximum protocol versions</td>\n<td>172</td>\n</tr>\n<tr>\n<td>2.13.1.2. Validating encryption with Kiali</td>\n<td>173</td>\n</tr>\n<tr>\n<td>2.13.2. Configuring Role Based Access Control (RBAC)</td>\n<td>174</td>\n</tr>\n<tr>\n<td>2.13.2.1. Configure intra-project communication</td>\n<td>175</td>\n</tr>\n<tr>\n<td>2.13.2.1.1. Restrict access to services outside a namespace</td>\n<td>175</td>\n</tr>\n<tr>\n<td>2.13.2.1.2. Creating allow-all and default deny-all authorization policies</td>\n<td>176</td>\n</tr>\n<tr>\n<td>2.13.2.2. Allow or deny access to the ingress gateway</td>\n<td>176</td>\n</tr>\n<tr>\n<td>2.13.2.3. Restrict access with JSON Web Token</td>\n<td>177</td>\n</tr>\n<tr>\n<td>2.13.3. Configuring cipher suites and ECDH curves</td>\n<td>177</td>\n</tr>\n<tr>\n<td>2.13.4. Configuring JSON Web Key Sets resolver certificate authority</td>\n<td>178</td>\n</tr>\n<tr>\n<td>2.13.5. Adding an external certificate authority key and certificate</td>\n<td>179</td>\n</tr>\n<tr>\n<td>2.13.5.1. Adding an existing certificate and key</td>\n<td>180</td>\n</tr>\n<tr>\n<td>2.13.5.2. Verifying your certificates</td>\n<td>181</td>\n</tr>\n<tr>\n<td>2.13.5.3. Removing the certificates</td>\n<td>182</td>\n</tr>\n<tr>\n<td>2.13.6. About integrating Service Mesh with cert-manager and istio-csr</td>\n<td>182</td>\n</tr>\n<tr>\n<td>2.13.6.1. Installing cert-manager</td>\n<td>183</td>\n</tr>\n<tr>\n<td>2.13.7. Additional resources</td>\n<td>187</td>\n</tr>\n<tr>\n<td>2.14. MANAGING TRAFFIC IN YOUR SERVICE MESH</td>\n<td>187</td>\n</tr>\n<tr>\n<td>2.14.1. Using gateways</td>\n<td>187</td>\n</tr>\n<tr>\n<td>2.14.1.1. Enabling gateway injection</td>\n<td>189</td>\n</tr>\n<tr>\n<td>2.14.1.2. Deploying automatic gateway injection</td>\n<td>189</td>\n</tr>\n<tr>\n<td>2.14.1.3. Managing ingress traffic</td>\n<td>192</td>\n</tr>\n<tr>\n<td>2.14.1.3.1. Determining the ingress IP and ports</td>\n<td>192</td>\n</tr>\n<tr>\n<td>2.14.1.3.1.1. Determining ingress ports with a load balancer</td>\n<td>192</td>\n</tr>\n<tr>\n<td>2.14.1.3.1.2. Determining ingress ports without a load balancer</td>\n<td>193</td>\n</tr>\n<tr>\n<td>2.14.1.4. Configuring an ingress gateway</td>\n<td>193</td>\n</tr>\n<tr>\n<td>2.14.2. Understanding automatic routes</td>\n<td>195</td>\n</tr>\n<tr>\n<td>2.14.2.1. Routes with subdomains</td>\n<td>195</td>\n</tr>\n<tr>\n<td>2.14.2.2. Creating subdomain routes</td>\n<td>196</td>\n</tr>\n<tr>\n<td>2.14.2.3. Route labels and annotations</td>\n<td>196</td>\n</tr>\n<tr>\n<td>2.14.2.4. Disabling automatic route creation</td>\n<td>197</td>\n</tr>\n<tr>\n<td>2.14.2.4.1. Disabling automatic route creation for specific cases</td>\n<td>197</td>\n</tr>\n<tr>\n<td>2.14.2.4.2. Disabling automatic route creation for all cases</td>\n<td>197</td>\n</tr>\n<tr>\n<td>2.14.3. Understanding service entries</td>\n<td>197</td>\n</tr>\n<tr>\n<td>2.14.4. Using VirtualServices</td>\n<td>198</td>\n</tr>\n<tr>\n<td>2.14.4.1. Configuring VirtualServices</td>\n<td>199</td>\n</tr>\n<tr>\n<td>2.14.4.2. VirtualService configuration reference</td>\n<td>199</td>\n</tr>\n<tr>\n<td>2.14.5. Understanding destination rules</td>\n<td>200</td>\n</tr>\n<tr>\n<td>2.14.6. Understanding network policies</td>\n<td>201</td>\n</tr>\n<tr>\n<td>2.14.6.1. Disabling automatic NetworkPolicy creation</td>\n<td>201</td>\n</tr>\n</table>\n<table><tr><td>2.14.7. Configuring sidecars for traffic management</td><td>202</td></tr><tr><td>2.14.8. Routing Tutorial</td><td>203</td></tr><tr><td> 2.14.8.1. Bookinfo routing tutorial</td><td>203</td></tr><tr><td> 2.14.8.2. Applying a virtual service</td><td>203</td></tr><tr><td> 2.14.8.3. Testing the new route configuration</td><td>204</td></tr><tr><td> 2.14.8.4. Route based on user identity</td><td>204</td></tr><tr><td>2.15. GATEWAY MIGRATION</td><td>205</td></tr><tr><td> 2.15.1. About gateway migration</td><td>205</td></tr><tr><td> 2.15.2. Migrate from SMCP-Defined gateways to gateway injection</td><td>205</td></tr><tr><td> 2.15.3. Additional resources</td><td>208</td></tr><tr><td>2.16. ROUTE MIGRATION</td><td>208</td></tr><tr><td> 2.16.1. Migrating from Istio OpenShift Routing to explicitly-managed routes</td><td>208</td></tr><tr><td> 2.16.2. Additional resources</td><td>209</td></tr><tr><td>2.17. METRICS, LOGS, AND TRACES</td><td>209</td></tr><tr><td> 2.17.1. Discovering console addresses</td><td>209</td></tr><tr><td> 2.17.2. Accessing the Kiali console</td><td>211</td></tr><tr><td> 2.17.3. Viewing service mesh data in the Kiali console</td><td>212</td></tr><tr><td> 2.17.3.1. Changing graph layouts in Kiali</td><td>212</td></tr><tr><td> 2.17.3.2. Viewing logs in the Kiali console</td><td>213</td></tr><tr><td> 2.17.3.3. Viewing metrics in the Kiali console</td><td>214</td></tr><tr><td> 2.17.4. Distributed tracing</td><td>215</td></tr><tr><td> 2.17.4.1. Configuring the Red Hat OpenShift Distributed Tracing Platform and the Red Hat build of OpenTelemetry</td><td>215</td></tr><tr><td> 2.17.4.1.1. Configuring the OpenTelemetryCollector in a mTLS encrypted Service Mesh member namespace</td><td>218</td></tr><tr><td> 2.17.4.1.2. Configuring the Red Hat OpenShift Distributed Tracing Platform in a mTLS encrypted Service Mesh member namespace</td><td>219</td></tr><tr><td> 2.17.4.2. Connecting an existing distributed tracing Jaeger instance</td><td>219</td></tr><tr><td> 2.17.4.3. Adjusting the sampling rate</td><td>220</td></tr><tr><td> 2.17.5. Accessing the Jaeger console</td><td>221</td></tr><tr><td> 2.17.6. Accessing the Grafana console</td><td>223</td></tr><tr><td> 2.17.7. Accessing the Prometheus console</td><td>223</td></tr><tr><td> 2.17.8. Integrating with user-workload monitoring</td><td>223</td></tr><tr><td> 2.17.9. Additional resources</td><td>228</td></tr><tr><td>2.18. PERFORMANCE AND SCALABILITY</td><td>228</td></tr><tr><td> 2.18.1. Setting limits on compute resources</td><td>228</td></tr><tr><td> 2.18.2. Load test results</td><td>230</td></tr><tr><td> 2.18.2.1. Service Mesh Control plane performance</td><td>230</td></tr><tr><td> 2.18.2.2. Data plane performance</td><td>231</td></tr><tr><td> 2.18.2.2.1. CPU and memory consumption</td><td>231</td></tr><tr><td> 2.18.2.2.2. Additional latency</td><td>231</td></tr><tr><td>2.19. CONFIGURING SERVICE MESH FOR PRODUCTION</td><td>231</td></tr><tr><td> 2.19.1. Configuring your ServiceMeshControlPlane resource for production</td><td>232</td></tr><tr><td> 2.19.2. Additional resources</td><td>233</td></tr><tr><td>2.20. CONNECTING SERVICE MESHES</td><td>233</td></tr><tr><td> 2.20.1. Federation overview</td><td>233</td></tr><tr><td> 2.20.2. Federation features</td><td>233</td></tr><tr><td> 2.20.3. Federation security</td><td>234</td></tr><tr><td> 2.20.4. Federation limitations</td><td>234</td></tr><tr><td> 2.20.5. Federation prerequisites</td><td>234</td></tr><tr><td> 2.20.6. Planning your mesh federation</td><td>235</td></tr><tr><td> 2.20.7. Mesh federation across clusters</td><td>236</td></tr><tr><td> 2.20.7.1. Exposing the federation ingress on clusters running on bare metal</td><td>236</td></tr></table>\n<hr/>\n<table>\n<tr>\n<td>2.20.7.2. Exposing the federation ingress on clusters running on IBM Power and IBM Z</td>\n<td>236</td>\n</tr>\n<tr>\n<td>2.20.7.3. Exposing the federation ingress on Amazon Web Services (AWS)</td>\n<td>236</td>\n</tr>\n<tr>\n<td>2.20.7.4. Exposing the federation ingress on Azure</td>\n<td>236</td>\n</tr>\n<tr>\n<td>2.20.7.5. Exposing the federation ingress on Google Cloud</td>\n<td>237</td>\n</tr>\n<tr>\n<td>2.20.8. Federation implementation checklist</td>\n<td>237</td>\n</tr>\n<tr>\n<td>2.20.9. Configuring a Service Mesh control plane for federation</td>\n<td>237</td>\n</tr>\n<tr>\n<td>2.20.9.1. Understanding federation gateways</td>\n<td>239</td>\n</tr>\n<tr>\n<td>2.20.9.2. Understanding federation trust domain parameters</td>\n<td>243</td>\n</tr>\n<tr>\n<td>2.20.10. Joining a federated mesh</td>\n<td>244</td>\n</tr>\n<tr>\n<td>2.20.10.1. Creating a ServiceMeshPeer resource</td>\n<td>247</td>\n</tr>\n<tr>\n<td>2.20.11. Exporting a service from a federated mesh</td>\n<td>249</td>\n</tr>\n<tr>\n<td>2.20.11.1. Creating an ExportedServiceSet</td>\n<td>253</td>\n</tr>\n<tr>\n<td>2.20.12. Importing a service into a federated mesh</td>\n<td>255</td>\n</tr>\n<tr>\n<td>2.20.12.1. Creating an ImportedServiceSet</td>\n<td>258</td>\n</tr>\n<tr>\n<td>2.20.13. Configuring a federated mesh for failover</td>\n<td>259</td>\n</tr>\n<tr>\n<td>2.20.13.1. Configuring an ImportedServiceSet for failover</td>\n<td>260</td>\n</tr>\n<tr>\n<td>2.20.13.2. Configuring a DestinationRule for failover</td>\n<td>261</td>\n</tr>\n<tr>\n<td>2.20.14. Removing a service from the federated mesh</td>\n<td>263</td>\n</tr>\n<tr>\n<td>2.20.14.1. To remove a service from a single mesh</td>\n<td>263</td>\n</tr>\n<tr>\n<td>2.20.14.2. To remove a service from the entire federated mesh</td>\n<td>263</td>\n</tr>\n<tr>\n<td>2.20.15. Removing a mesh from the federated mesh</td>\n<td>263</td>\n</tr>\n<tr>\n<td>2.21. EXTENSIONS</td>\n<td>263</td>\n</tr>\n<tr>\n<td>2.21.1. WebAssembly modules overview</td>\n<td>263</td>\n</tr>\n<tr>\n<td>2.21.2. WasmPlugin container format</td>\n<td>264</td>\n</tr>\n<tr>\n<td>2.21.3. WasmPlugin API reference</td>\n<td>265</td>\n</tr>\n<tr>\n<td>2.21.3.1. Deploying WasmPlugin resources</td>\n<td>270</td>\n</tr>\n<tr>\n<td>2.21.4. ServiceMeshExtension container format</td>\n<td>270</td>\n</tr>\n<tr>\n<td>2.21.5. ServiceMeshExtension reference</td>\n<td>271</td>\n</tr>\n<tr>\n<td>2.21.5.1. Deploying ServiceMeshExtension resources</td>\n<td>273</td>\n</tr>\n<tr>\n<td>2.21.6. Migrating from ServiceMeshExtension to WasmPlugin resources</td>\n<td>274</td>\n</tr>\n<tr>\n<td>2.21.6.1. API changes</td>\n<td>274</td>\n</tr>\n<tr>\n<td>2.21.6.2. Container image format changes</td>\n<td>275</td>\n</tr>\n<tr>\n<td>2.21.6.3. Migrating to WasmPlugin resources</td>\n<td>275</td>\n</tr>\n<tr>\n<td>2.22. OPENSHIFT SERVICE MESH CONSOLE PLUGIN</td>\n<td>276</td>\n</tr>\n<tr>\n<td>2.22.1. About the OpenShift Service Mesh Console plugin</td>\n<td>276</td>\n</tr>\n<tr>\n<td>2.22.2. Installing OpenShift Service Mesh Console plugin using the OpenShift Container Platform web console</td>\n<td>277</td>\n</tr>\n<tr>\n<td>2.22.3. Installing OpenShift Service Mesh Console plugin using the CLI</td>\n<td>278</td>\n</tr>\n<tr>\n<td>2.22.4. Uninstalling OpenShift Service Mesh Console plugin using the OpenShift Container Platform web console</td>\n<td>279</td>\n</tr>\n<tr>\n<td>2.22.5. Uninstalling OpenShift Service Mesh Console plugin using the CLI</td>\n<td>279</td>\n</tr>\n<tr>\n<td>2.22.6. Additional resources</td>\n<td>279</td>\n</tr>\n<tr>\n<td>2.23. USING THE 3SCALE WEBASSEMBLY MODULE</td>\n<td>279</td>\n</tr>\n<tr>\n<td>2.23.1. Compatibility</td>\n<td>280</td>\n</tr>\n<tr>\n<td>2.23.2. Usage as a stand-alone module</td>\n<td>280</td>\n</tr>\n<tr>\n<td>2.23.3. Prerequisites</td>\n<td>280</td>\n</tr>\n<tr>\n<td>2.23.4. Configuring the threescale-wasm-auth module</td>\n<td>280</td>\n</tr>\n<tr>\n<td>2.23.4.1. The WasmPlugin API extension</td>\n<td>280</td>\n</tr>\n<tr>\n<td>2.23.5. Applying 3scale external ServiceEntry objects</td>\n<td>282</td>\n</tr>\n<tr>\n<td>2.23.6. The 3scale WebAssembly module configuration</td>\n<td>284</td>\n</tr>\n<tr>\n<td>2.23.6.1. Configuring the 3scale WebAssembly module</td>\n<td>284</td>\n</tr>\n<tr>\n<td>2.23.6.2. The 3scale WebAssembly module api object</td>\n<td>285</td>\n</tr>\n<tr>\n<td>2.23.6.3. The 3scale WebAssembly module system object</td>\n<td>285</td>\n</tr>\n</table>\n\n<table>\n<tr><td>2.23.6.4. The 3scale WebAssembly module upstream object</td><td>286</td></tr>\n<tr><td>2.23.6.5. The 3scale WebAssembly module backend object</td><td>287</td></tr>\n<tr><td>2.23.6.6. The 3scale WebAssembly module services object</td><td>288</td></tr>\n<tr><td>2.23.6.7. The 3scale WebAssembly module credentials object</td><td>289</td></tr>\n<tr><td>2.23.6.8. The 3scale WebAssembly module lookup queries</td><td>290</td></tr>\n<tr><td>2.23.6.9. The 3scale WebAssembly module source object</td><td>291</td></tr>\n<tr><td>2.23.6.10. The 3scale WebAssembly module operations object</td><td>292</td></tr>\n<tr><td>2.23.6.11. The 3scale WebAssembly module mapping_rules object</td><td>292</td></tr>\n<tr><td>2.23.6.12. The 3scale WebAssembly module mapping_rule object</td><td>293</td></tr>\n<tr><td>2.23.7. The 3scale WebAssembly module examples for credentials use cases</td><td>295</td></tr>\n<tr><td>2.23.7.1. API key (user_key) in query string parameters</td><td>295</td></tr>\n<tr><td>2.23.7.2. Application ID and key</td><td>295</td></tr>\n<tr><td>2.23.7.3. Authorization header</td><td>296</td></tr>\n<tr><td>2.23.7.4. OpenID Connect (OIDC) use case</td><td>298</td></tr>\n<tr><td>2.23.7.5. Picking up the JWT token from a header</td><td>300</td></tr>\n<tr><td>2.23.8. 3scale WebAssembly module minimal working configuration</td><td>300</td></tr>\n<tr><td>2.24. USING THE 3SCALE ISTIO ADAPTER</td><td>301</td></tr>\n<tr><td>2.24.1. Integrate the 3scale adapter with Red Hat OpenShift Service Mesh</td><td>302</td></tr>\n<tr><td>2.24.1.1. Generating 3scale custom resources</td><td>303</td></tr>\n<tr><td>2.24.1.1.1. Generate templates from URL examples</td><td>304</td></tr>\n<tr><td>2.24.1.2. Generating manifests from a deployed adapter</td><td>305</td></tr>\n<tr><td>2.24.1.3. Routing service traffic through the adapter</td><td>306</td></tr>\n<tr><td>2.24.2. Configure the integration settings in 3scale</td><td>306</td></tr>\n<tr><td>2.24.3. Caching behavior</td><td>307</td></tr>\n<tr><td>2.24.4. Authenticating requests</td><td>307</td></tr>\n<tr><td>2.24.4.1. Applying authentication patterns</td><td>307</td></tr>\n<tr><td>2.24.4.1.1. API key authentication method</td><td>307</td></tr>\n<tr><td>2.24.4.1.2. Application ID and application key pair authentication method</td><td>308</td></tr>\n<tr><td>2.24.4.1.3. OpenID authentication method</td><td>308</td></tr>\n<tr><td>2.24.4.1.4. Hybrid authentication method</td><td>309</td></tr>\n<tr><td>2.24.5. 3scale Adapter metrics</td><td>310</td></tr>\n<tr><td>2.24.6. 3scale backend cache</td><td>310</td></tr>\n<tr><td>2.24.6.1. Advantages of enabling backend cache</td><td>311</td></tr>\n<tr><td>2.24.6.2. Trade-offs for having lower latencies</td><td>311</td></tr>\n<tr><td>2.24.6.3. Backend cache configuration settings</td><td>312</td></tr>\n<tr><td>2.24.7. 3scale Istio Adapter APIcast emulation</td><td>312</td></tr>\n<tr><td>2.24.8. 3scale Istio adapter verification</td><td>312</td></tr>\n<tr><td>2.24.9. 3scale Istio adapter troubleshooting checklist</td><td>313</td></tr>\n<tr><td>2.25. TROUBLESHOOTING YOUR SERVICE MESH</td><td>313</td></tr>\n<tr><td>2.25.1. Understanding Service Mesh versions</td><td>313</td></tr>\n<tr><td>2.25.2. Troubleshooting Operator installation</td><td>314</td></tr>\n<tr><td>2.25.2.1. Validating Operator installation</td><td>314</td></tr>\n<tr><td>2.25.2.2. Troubleshooting service mesh Operators</td><td>315</td></tr>\n<tr><td>2.25.2.2.1. Viewing Operator pod logs</td><td>316</td></tr>\n<tr><td>2.25.3. Troubleshooting the control plane</td><td>316</td></tr>\n<tr><td>2.25.3.1. Validating the Service Mesh control plane installation</td><td>316</td></tr>\n<tr><td>2.25.3.1.1. Accessing the Kiali console</td><td>319</td></tr>\n<tr><td>2.25.3.1.2. Accessing the Jaeger console</td><td>320</td></tr>\n<tr><td>2.25.3.2. Troubleshooting the Service Mesh control plane</td><td>321</td></tr>\n<tr><td>2.25.4. Troubleshooting the data plane</td><td>321</td></tr>\n<tr><td>2.25.4.1. Troubleshooting sidecar injection</td><td>322</td></tr>\n<tr><td>2.25.4.1.1. Troubleshooting Istio sidecar injection</td><td>322</td></tr>\n<tr><td>2.25.4.1.2. Troubleshooting Jaeger agent sidecar injection</td><td>322</td></tr>\n</table>\n<hr/><table><tr><td>2.26. TROUBLESHOOTING ENVOY PROXY</td><td>322</td></tr><tr><td> 2.26.1. Enabling Envoy access logs</td><td>322</td></tr><tr><td> 2.26.2. Getting support</td><td>323</td></tr><tr><td> 2.26.2.1. About the Red Hat Knowledgebase</td><td>323</td></tr><tr><td> 2.26.2.2. Searching the Red Hat Knowledgebase</td><td>323</td></tr><tr><td> 2.26.2.3. About collecting service mesh data</td><td>324</td></tr><tr><td> 2.26.2.4. Submitting a support case</td><td>325</td></tr><tr><td>2.27. SERVICE MESH CONTROL PLANE CONFIGURATION REFERENCE</td><td>326</td></tr><tr><td> 2.27.1. Service Mesh Control plane parameters</td><td>326</td></tr><tr><td> 2.27.2. spec parameters</td><td>333</td></tr><tr><td> 2.27.2.1. general parameters</td><td>333</td></tr><tr><td> 2.27.2.2. profiles parameters</td><td>334</td></tr><tr><td> 2.27.2.3. techPreview parameters</td><td>334</td></tr><tr><td> 2.27.2.4. tracing parameters</td><td>335</td></tr><tr><td> 2.27.2.5. version parameter</td><td>336</td></tr><tr><td> 2.27.2.6. 3scale configuration</td><td>336</td></tr><tr><td> 2.27.3. status parameter</td><td>338</td></tr><tr><td> 2.27.4. Additional resources</td><td>340</td></tr><tr><td>2.28. KIALI CONFIGURATION REFERENCE</td><td>340</td></tr><tr><td> 2.28.1. Specifying Kiali configuration in the SMCP</td><td>340</td></tr><tr><td> 2.28.2. Specifying Kiali configuration in a Kiali custom resource</td><td>344</td></tr><tr><td>2.29. UNINSTALLING SERVICE MESH</td><td>345</td></tr><tr><td> 2.29.1. Removing the Red Hat OpenShift Service Mesh control plane</td><td>345</td></tr><tr><td> 2.29.1.1. Removing the Service Mesh control plane using the web console</td><td>345</td></tr><tr><td> 2.29.1.2. Removing the Service Mesh control plane using the CLI</td><td>345</td></tr><tr><td> 2.29.2. Removing the installed Operators</td><td>346</td></tr><tr><td> 2.29.2.1. Removing the Operators</td><td>346</td></tr><tr><td> 2.29.3. Clean up Operator resources</td><td>346</td></tr></table><h1>CHAPTER 1. SERVICE MESH 3.X</h1><h2>1.1. SERVICE MESH OVERVIEW</h2><p>Red Hat OpenShift Service Mesh manages and secures communication between microservices by providing traffic management, advanced routing, and load balancing. Red Hat OpenShift Service Mesh also enhances security through features like mutual TLS, and offers observability with metrics, logging, and tracing to monitor and troubleshoot applications.</p><h3>NOTE</h3><p>Because Red Hat OpenShift Service Mesh 3.0 releases on a different cadence from OpenShift Container Platform, the Service Mesh documentation is available as a separate documentation set at <a href=\"#\">Red Hat OpenShift Service Mesh</a>.</p><h2>CHAPTER 2. SERVICE MESH 2.X</h2><h3>2.1. ABOUT OPENSHIFT SERVICE MESH</h3><h4>NOTE</h4><p>Because Red Hat OpenShift Service Mesh releases on a different cadence from OpenShift Container Platform and because the Red Hat OpenShift Service Mesh Operator supports deploying multiple versions of the <b>ServiceMeshControlPlane</b>, the Service Mesh documentation does not maintain separate documentation sets for minor versions of the product. The current documentation set applies to the most recent version of Service Mesh unless version-specific limitations are called out in a particular topic or for a particular feature.</p><p>For additional information about the Red Hat OpenShift Service Mesh life cycle and supported platforms, refer to the <a href=\"#\">Platform Life Cycle Policy</a>.</p><h4>2.1.1. Introduction to Red Hat OpenShift Service Mesh</h4><p>Red Hat OpenShift Service Mesh addresses a variety of problems in a microservice architecture by creating a centralized point of control in an application. It adds a transparent layer on existing distributed applications without requiring any changes to the application code.</p><p>Microservice architectures split the work of enterprise applications into modular services, which can make scaling and maintenance easier. However, as an enterprise application built on a microservice architecture grows in size and complexity, it becomes difficult to understand and manage. Service Mesh can address those architecture problems by capturing or intercepting traffic between services and can modify, redirect, or create new requests to other services.</p><p>Service Mesh, which is based on the open source <a href=\"#\">Istio project</a>, provides an easy way to create a network of deployed services that provides discovery, load balancing, service-to-service authentication, failure recovery, metrics, and monitoring. A service mesh also provides more complex operational functionality, including A/B testing, canary releases, access control, and end-to-end authentication.</p><h4>NOTE</h4><p>Red Hat OpenShift Service Mesh 3 is generally available. For more information, see <a href=\"#\">Red Hat OpenShift Service Mesh 3.0</a>.</p><h4>2.1.2. Core features</h4><p>Red Hat OpenShift Service Mesh provides a number of key capabilities uniformly across a network of services:</p><ul><li>● <b>Traffic Management</b> – Control the flow of traffic and API calls between services, make calls more reliable, and make the network more robust in the face of adverse conditions.</li><li>● <b>Service Identity and Security</b> – Provide services in the mesh with a verifiable identity and provide the ability to protect service traffic as it flows over networks of varying degrees of trustworthiness.</li><li>● <b>Policy Enforcement</b> – Apply organizational policy to the interaction between services, ensure access policies are enforced and resources are fairly distributed among consumers. Policy changes are made by configuring the mesh, not by changing application code.</li></ul>\n<ul>\n<li>• <b>Telemetry</b> - Gain understanding of the dependencies between services and the nature and flow of traffic between them, providing the ability to quickly identify issues.</li>\n</ul>\n\n<h2>2.2. SERVICE MESH RELEASE NOTES</h2>\n\n<h3>2.2.1. Red Hat OpenShift Service Mesh version 2.6.11</h3>\n\n<p>This release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.11, and includes the <b>ServiceMeshControlPlane</b> resource version updates for 2.6.11.</p>\n\n<p>This release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<p>The most current version of the Red Hat OpenShift Service Mesh Operator can be used with all supported versions of Service Mesh. The version of Service Mesh is specified using the <b>ServiceMeshControlPlane</b>.</p>\n\n<p>You can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh automatically ensures a compatible version of Kiali.</p>\n\n<h4>2.2.1.1. Component updates</h4>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.2. Red Hat OpenShift Service Mesh version 2.6.10</h3>\n\n<p>This release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.10, and includes the <b>ServiceMeshControlPlane</b> resource version updates for 2.6.10.</p>\n\n<p>This release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<p>You can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh automatically ensures a compatible version of Kiali.</p>\n\n<h4>2.2.2.1. Component updates</h4>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.3. Red Hat OpenShift Service Mesh version 2.6.9</h3>\n\n<p>This release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.9, and includes the following <b>ServiceMeshControlPlane</b> resource version updates: 2.6.9 and 2.5.12.</p>\n\n<p>This release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<p>You can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh automatically ensures a compatible version of Kiali.</p>\n\n<h4>2.2.3.1. Component updates</h4>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.22</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.4. Red Hat OpenShift Service Mesh version 2.5.12</h3>\n\n<p>This release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.9 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).</p>\n\n<h4>2.2.4.1. Component updates</h4>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.22</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.5. Red Hat OpenShift Service Mesh version 2.6.8</h3>\n\n<p>This release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.8, and includes the following <b>ServiceMeshControlPlane</b> resource version updates: 2.6.8 and 2.5.11.</p>\n\n<p>This release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<p>You can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh automatically ensures a compatible version of Kiali.</p>\n\n<h3>2.2.5.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.21</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.6. Red Hat OpenShift Service Mesh version 2.5.11</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.8 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).</p>\n\n<h3>2.2.6.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.21</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.7. Red Hat OpenShift Service Mesh version 2.6.7</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.7, and includes the following <b>ServiceMeshControlPlane</b> resource version updates: 2.6.7 and 2.5.10.</p>\n\n<p>This release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<p>You can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh is specified by using the <b>ServiceMeshControlPlane</b> resource. The version of Service Mesh automatically ensures a compatible version of Kiali.</p>\n\n<h3>2.2.7.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.20</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.8. Red Hat OpenShift Service Mesh version 2.5.10</h3>\n\n<p>This release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.7 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).</p>\n\n<h4>2.2.8.1. Component updates</h4>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.20</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.9. Red Hat OpenShift Service Mesh version 2.6.6</h3>\n\n<p>This release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.6, and includes the following <b>ServiceMeshControlPlane</b> resource version updates: 2.6.6, 2.5.9, and 2.4.15.</p>\n\n<p>This release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<p>You can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh is specified by using the <b>ServiceMeshControlPlane</b> resource. The version of Service Mesh automatically ensures a compatible version of Kiali.</p>\n\n<h4>2.2.9.1. Component updates</h4>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.19</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.9.2. New features</h3>\n\n<ul>\n<li>• With this update, the Operator for Red Hat OpenShift Service Mesh 2.6 is renamed to Red Hat OpenShift Service Mesh 2 to align with the release of Red Hat OpenShift Service Mesh 3.0 and improve clarity.</li>\n</ul>\n\n<h2>2.2.10. Red Hat OpenShift Service Mesh version 2.5.9</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.6 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).</p>\n\n<h3>2.2.10.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.19</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.11. Red Hat OpenShift Service Mesh version 2.4.15</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.6 and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<h3>2.2.11.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.16.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.24.12</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.65.20</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.12. Red Hat OpenShift Service Mesh version 2.6.5</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.5, and includes the following <b>ServiceMeshControlPlane</b> resource version updates: 2.6.5, 2.5.8, and 2.4.14.</p>\n\n<p>This release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<p>You can use the most current version of the Kiali Operator provided by Red Hat with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh is specified by using the <b>ServiceMeshControlPlane</b> resource. The version of Service Mesh automatically ensures a compatible version of Kiali.</p>\n\n<h3>2.2.12.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.18</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.12.2. New features</h3>\n\n<ul>\n<li>• Red Hat OpenShift Distributed Tracing Platform Stack is now supported on IBM Z.</li>\n</ul>\n\n<h3>2.2.12.3. Fixed issues</h3>\n\n<ul>\n<li>• <a href=\"#\">OSSM-8608</a> Previously, terminating a Container Network Interface (CNI) pod during the installation phase while copying binaries could leave Istio-CNI temporary files on the node file system. Repeated occurrences could eventually fill up the node disk space. Now, while terminating a CNI pod during the installation phase, existing temporary files are deleted before copying the CNI binary, ensuring that only one temporary file per Istio version exists on the node file system.</li>\n</ul>\n\n<h2>2.2.13. Red Hat OpenShift Service Mesh version 2.5.8</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.5 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).</p>\n\n<h3>2.2.13.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.18</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.13.2. Fixed issues</h3>\n\n<ul>\n<li>● <a href=\"#\">OSSM-8608</a> Previously, terminating a Container Network Interface (CNI) pod during the installation phase while copying binaries could leave Istio-CNI temporary files on the node file system. Repeated occurrences could eventually fill up the node disk space. Now, while terminating a CNI pod during the installation phase, existing temporary files are deleted before copying the CNI binary, ensuring that only one temporary file per Istio version exists on the node file system.</li>\n</ul>\n\n<h2>2.2.14. Red Hat OpenShift Service Mesh version 2.4.14</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.5 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).</p>\n\n<h3>2.2.14.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.16.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.24.12</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.65.19</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.14.2. Fixed issues</h3>\n\n<ul>\n<li>● <a href=\"#\">OSSM-8608</a> Previously, terminating a Container Network Interface (CNI) pod during the installation phase while copying binaries could leave Istio-CNI temporary files on the node file system. Repeated occurrences could eventually fill up the node disk space. Now, while terminating a CNI pod during the installation phase, existing temporary files are deleted before copying the CNI binary, ensuring that only one temporary file per Istio version exists on the node file system.</li>\n</ul>\n\n<h2>2.2.15. Red Hat OpenShift Service Mesh version 2.6.4</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.4, and includes the following <b>ServiceMeshControlPlane</b> resource version updates: 2.6.4, 2.5.7, and 2.4.13.</p>\n\n<p>This release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<p>The most current version of the Kiali Operator provided by Red Hat can be used with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh is specified by using the <b>ServiceMeshControlPlane</b> resource. The version of Service Mesh automatically ensures a compatible version of Kiali.</p>\n\n<h3>2.2.15.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.17</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.16. Red Hat OpenShift Service Mesh version 2.5.7</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.4 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).</p>\n\n<h3>2.2.16.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.17</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.17. Red Hat OpenShift Service Mesh version 2.4.13</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.4 and is supported on OpenShift Container Platform 4.14 and later. This release addresses Common Vulnerabilities and Exposures (CVEs).</p>\n\n<h3>2.2.17.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.16.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.24.12</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.65.18</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.18. Red Hat OpenShift Service Mesh version 2.6.3</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.3, and includes the following <b>ServiceMeshControlPlane</b> resource version updates: 2.6.3, 2.5.6, and 2.4.12.</p>\n\n<p>This release addresses Common Vulnerabilities and Exposures (CVEs) and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<p>The most current version of the Kiali Operator provided by Red Hat can be used with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh is specified by using the <b>ServiceMeshControlPlane</b> resource. The version of Service Mesh automatically ensures a compatible version of Kiali.</p>\n\n<h3>2.2.18.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.16</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.19. Red Hat OpenShift Service Mesh version 2.5.6</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.3, addresses Common Vulnerabilities and Exposures (CVEs), and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<h3>2.2.19.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.18.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.26.8</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.16</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.20. Red Hat OpenShift Service Mesh version 2.4.12</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh is included with the Red Hat OpenShift Service Mesh Operator 2.6.3, addresses Common Vulnerabilities and Exposures (CVEs), and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<h3>2.2.20.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.16.7</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.24.12</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Kiali Server</td>\n<td>1.65.17</td>\n</tr>\n</tbody>\n</table>\n\n<h2>2.2.21. Red Hat OpenShift Service Mesh version 2.6.2</h2>\n\n<p>This release of Red Hat OpenShift Service Mesh updates the Red Hat OpenShift Service Mesh Operator version to 2.6.2, and includes the following <b>ServiceMeshControlPlane</b> resource version updates: 2.6.2, 2.5.5 and 2.4.11.</p>\n\n<p>This release addresses Common Vulnerabilities and Exposures (CVEs), contains bug fixes, and is supported on OpenShift Container Platform 4.14 and later.</p>\n\n<p>The most current version of the Kiali Operator provided by Red Hat can be used with all supported versions of Red Hat OpenShift Service Mesh. The version of Service Mesh is specified by using the <b>ServiceMeshControlPlane</b> resource. The version of Service Mesh automatically ensures a compatible version of Kiali.</p>\n\n<h3>2.2.21.1. Component updates</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Component</th>\n<th>Version</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Istio</td>\n<td>1.20.8</td>\n</tr>\n<tr>\n<td>Envoy Proxy</td>\n<td>1.28.7</td>\n</tr>\n<tr>\n<td>Kiali Server</td>\n<td>1.73.15</td>\n</tr>\n</tbody>\n</table>\n\n<h3>2.2.21.2. New features</h3>\n\n<ul>\n<li>• The cert-manager Operator for Red Hat OpenShift is now supported on IBM Power, IBM Z, and IBM® LinuxONE.</li>\n</ul>\n\n<h3>2.2.21.3. Fixed issues</h3>\n\n<ul>\n<li>• <a href=\"#\">OSSM-8099</a> Previously, there was an issue supporting persistent session labels when the endpoints were in the draining phase. Now, there is a method of handling draining endpoints for the stateful header sessions.</li>\n<li>• <a href=\"#\">OSSM-8001</a> Previously, when <b>runAsUser</b> and <b>runAsGroup</b> were set to the same value in pods, the proxy GID was incorrectly set to match the container's GID, causing traffic interception issues with iptables rules applied by Istio CNI. Now, containers can have the same value for runAsUser and runAsGroup, and iptables rules apply correctly.</li>\n<li>• <a href=\"#\">OSSM-8074</a> Previously, the Kiali Operator failed to install the Kiali server when a Service Mesh had a numeric-only namespace (e.g., <b>12345</b>). Now, namespaces with only numerals work correctly.</li>\n</ul>\n\n<h2>2.2.22. Red Hat OpenShift Service Mesh version 2.5.5</h2>"},"page_stats":{"kind":"list like","value":[{"page_number":1,"error":false,"token_count":249,"num_chunks":5},{"page_number":2,"error":false,"token_count":48,"num_chunks":1},{"page_number":3,"error":false,"token_count":88,"num_chunks":2},{"page_number":4,"error":false,"token_count":587,"num_chunks":11},{"page_number":5,"error":false,"token_count":2040,"num_chunks":4},{"page_number":6,"error":false,"token_count":1852,"num_chunks":3},{"page_number":7,"error":false,"token_count":2523,"num_chunks":3},{"page_number":8,"error":false,"token_count":2305,"num_chunks":3},{"page_number":9,"error":false,"token_count":2478,"num_chunks":3},{"page_number":10,"error":false,"token_count":1770,"num_chunks":3},{"page_number":11,"error":false,"token_count":1959,"num_chunks":3},{"page_number":12,"error":false,"token_count":1851,"num_chunks":3},{"page_number":13,"error":false,"token_count":2035,"num_chunks":3},{"page_number":14,"error":false,"token_count":1717,"num_chunks":3},{"page_number":15,"error":false,"token_count":2012,"num_chunks":3},{"page_number":16,"error":false,"token_count":1894,"num_chunks":3},{"page_number":17,"error":false,"token_count":991,"num_chunks":3},{"page_number":18,"error":false,"token_count":82,"num_chunks":2},{"page_number":19,"error":false,"token_count":430,"num_chunks":8},{"page_number":20,"error":false,"token_count":1182,"num_chunks":18},{"page_number":21,"error":false,"token_count":1206,"num_chunks":17},{"page_number":22,"error":false,"token_count":1114,"num_chunks":14},{"page_number":23,"error":false,"token_count":1183,"num_chunks":15},{"page_number":24,"error":false,"token_count":1136,"num_chunks":14},{"page_number":25,"error":false,"token_count":1186,"num_chunks":15},{"page_number":26,"error":false,"token_count":1159,"num_chunks":15},{"page_number":27,"error":false,"token_count":1151,"num_chunks":14},{"page_number":28,"error":false,"token_count":1109,"num_chunks":13},{"page_number":29,"error":false,"token_count":1128,"num_chunks":14},{"page_number":30,"error":false,"token_count":1210,"num_chunks":14}],"string":"[\n {\n \"page_number\": 1,\n \"error\": false,\n \"token_count\": 249,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 2,\n \"error\": false,\n \"token_count\": 48,\n \"num_chunks\": 1\n },\n {\n \"page_number\": 3,\n \"error\": false,\n \"token_count\": 88,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 4,\n \"error\": false,\n \"token_count\": 587,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 5,\n \"error\": false,\n \"token_count\": 2040,\n \"num_chunks\": 4\n },\n {\n \"page_number\": 6,\n \"error\": false,\n \"token_count\": 1852,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 7,\n \"error\": false,\n \"token_count\": 2523,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 8,\n \"error\": false,\n \"token_count\": 2305,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 9,\n \"error\": false,\n \"token_count\": 2478,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 10,\n \"error\": false,\n \"token_count\": 1770,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 11,\n \"error\": false,\n \"token_count\": 1959,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 12,\n \"error\": false,\n \"token_count\": 1851,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 13,\n \"error\": false,\n \"token_count\": 2035,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 14,\n \"error\": false,\n \"token_count\": 1717,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 15,\n \"error\": false,\n \"token_count\": 2012,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 16,\n \"error\": false,\n \"token_count\": 1894,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 17,\n \"error\": false,\n \"token_count\": 991,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 18,\n \"error\": false,\n \"token_count\": 82,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 19,\n \"error\": false,\n \"token_count\": 430,\n \"num_chunks\": 8\n },\n {\n \"page_number\": 20,\n \"error\": false,\n \"token_count\": 1182,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 21,\n \"error\": false,\n \"token_count\": 1206,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 22,\n \"error\": false,\n \"token_count\": 1114,\n \"num_chunks\": 14\n },\n {\n \"page_number\": 23,\n \"error\": false,\n \"token_count\": 1183,\n \"num_chunks\": 15\n },\n {\n \"page_number\": 24,\n \"error\": false,\n \"token_count\": 1136,\n \"num_chunks\": 14\n },\n {\n \"page_number\": 25,\n \"error\": false,\n \"token_count\": 1186,\n \"num_chunks\": 15\n },\n {\n \"page_number\": 26,\n \"error\": false,\n \"token_count\": 1159,\n \"num_chunks\": 15\n },\n {\n \"page_number\": 27,\n \"error\": false,\n \"token_count\": 1151,\n \"num_chunks\": 14\n },\n {\n \"page_number\": 28,\n \"error\": false,\n \"token_count\": 1109,\n \"num_chunks\": 13\n },\n {\n \"page_number\": 29,\n \"error\": false,\n \"token_count\": 1128,\n \"num_chunks\": 14\n },\n {\n \"page_number\": 30,\n \"error\": false,\n \"token_count\": 1210,\n \"num_chunks\": 14\n }\n]","isConversational":false}}},{"rowIdx":98,"cells":{"source_id":{"kind":"string","value":"OpenShift_Container_Platform-4.21-Specialized_hardware_and_driver_enablement-en-US"},"pdf_url":{"kind":"string","value":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/specialized_hardware_and_driver_enablement/OpenShift_Container_Platform-4.21-Specialized_hardware_and_driver_enablement-en-US.pdf"},"status":{"kind":"string","value":"success"},"processed_at":{"kind":"string","value":"2026-04-15T18:40:01.021382+00:00"},"elapsed_seconds":{"kind":"number","value":68.57,"string":"68.57"},"num_pages":{"kind":"number","value":94,"string":"94"},"num_pages_processed":{"kind":"number","value":30,"string":"30"},"max_pages_per_paper":{"kind":"number","value":30,"string":"30"},"pdf_exceeds_page_limit":{"kind":"bool","value":true,"string":"true"},"failed_pages":{"kind":"list like","value":[],"string":"[]","isConversational":false},"prompt_type":{"kind":"string","value":"ocr_layout"},"model_id":{"kind":"string","value":"datalab-to/chandra-ocr-2"},"script_version":{"kind":"timestamp","value":"2026-04-15T00:00:00","string":"2026-04-15T00:00:00"},"markdown":{"kind":"string","value":"# OpenShift Container Platform 4.21\n\n## Specialized hardware and driver enablement\n\nLearn about hardware enablement on OpenShift Container Platform## OpenShift Container Platform 4.21 Specialized hardware and driver enablement\n\n---\n\nLearn about hardware enablement on OpenShift Container Platform## Legal Notice\n\nCopyright © Red Hat.\n\nExcept as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.\n\nRed Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.\n\nRed Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.\n\nLinux ® is the registered trademark of Linus Torvalds in the United States and other countries.\n\nXFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.\n\nThe OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.\n\nAll other trademarks are the property of their respective owners.\n\n## Abstract\n\nThis document provides an overview of hardware enablement in OpenShift Container Platform.# Table of Contents\n\n<table>\n<tr>\n<td><b>CHAPTER 1. ABOUT SPECIALIZED HARDWARE AND DRIVER ENABLEMENT</b> .....</td>\n<td><b>6</b></td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. DRIVER TOOLKIT</b> .....</td>\n<td><b>7</b></td>\n</tr>\n<tr>\n<td> 2.1. ABOUT THE DRIVER TOOLKIT</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 2.1.1. Background</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 2.1.2. Purpose</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.2. PULLING THE DRIVER TOOLKIT CONTAINER IMAGE</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.2.1. Pulling the Driver Toolkit container image from registry.redhat.io</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.2.2. Finding the Driver Toolkit image URL in the payload</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.3. USING THE DRIVER TOOLKIT</td>\n<td>9</td>\n</tr>\n<tr>\n<td> 2.3.1. Build and run the simple-kmod driver container on a cluster</td>\n<td>9</td>\n</tr>\n<tr>\n<td> 2.4. ADDITIONAL RESOURCES</td>\n<td>13</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. NODE FEATURE DISCOVERY OPERATOR</b> .....</td>\n<td><b>14</b></td>\n</tr>\n<tr>\n<td> 3.1. INSTALLING THE NODE FEATURE DISCOVERY OPERATOR</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 3.1.1. Installing the NFD Operator using the CLI</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 3.1.2. Installing the NFD Operator using the web console</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 3.2. USING THE NODE FEATURE DISCOVERY OPERATOR</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 3.2.1. Creating a NodeFeatureDiscovery CR by using the CLI</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 3.2.2. Creating a NodeFeatureDiscovery CR by using the CLI in a disconnected environment</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.3. Creating a NodeFeatureDiscovery CR by using the web console</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 3.3. CONFIGURING THE NODE FEATURE DISCOVERY OPERATOR</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.3.1. core</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.3.1.1. core.sleepInterval</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.3.1.2. core.sources</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.3.1.3. core.labelWhitelist</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.3.1.4. core.noPublish</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.2. core.klog</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.2.1. core.klog.addDirHeader</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.2.2. core.klog.alsologtostderr</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.2.3. core.klog.logBacktraceAt</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.2.4. core.klog.logDir</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.3.2.5. core.klog.logFile</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.3.2.6. core.klog.logFileMaxSize</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.3.2.7. core.klog.logtostderr</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.3.2.8. core.klog.skipHeaders</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.3.2.9. core.klog.skipLogHeaders</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.3.2.10. core.klog.stderrthreshold</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 3.3.2.11. core.klog.v</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 3.3.2.12. core.klog.vmodule</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 3.3.3. sources</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 3.3.3.1. sources.cpu.cpuid.attributeBlacklist</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 3.3.3.2. sources.cpu.cpuid.attributeWhitelist</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 3.3.3.3. sources.kernel.kconfigFile</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.3.3.4. sources.kernel.configOpts</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.3.3.5. sources.pci.deviceClassWhitelist</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.3.3.6. sources.pci.deviceLabelFields</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.3.3.7. sources.usb.deviceClassWhitelist</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.3.3.8. sources.usb.deviceLabelFields</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.3.3.9. sources.custom</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.4. ABOUT THE NODEFEATURERULE CUSTOM RESOURCE</td>\n<td>29</td>\n</tr>\n</table><table>\n<tr>\n<td>3.5. USING THE NODEFEATURERULE CUSTOM RESOURCE</td>\n<td>29</td>\n</tr>\n<tr>\n<td>3.6. USING THE NFD TOPOLOGY UPDATER</td>\n<td>30</td>\n</tr>\n<tr>\n<td> 3.6.1. NodeResourceTopology CR</td>\n<td>30</td>\n</tr>\n<tr>\n<td> 3.6.2. NFD Topology Updater command-line flags</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.6.2.1. -ca-file</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.6.2.2. -cert-file</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.6.2.3. -h, -help</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.6.2.4. -key-file</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.6.2.5. -kubelet-config-file</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.6.2.6. -no-publish</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.6.2.7. -oneshot</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.6.2.8. -podresources-socket</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.6.2.9. -server</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.6.2.10. -server-name-override</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.6.2.11. -sleep-interval</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.6.2.12. -version</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.6.2.13. -watch-namespace</td>\n<td>33</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. KERNEL MODULE MANAGEMENT OPERATOR</b> .....</td>\n<td><b>35</b></td>\n</tr>\n<tr>\n<td> 4.1. ABOUT THE KERNEL MODULE MANAGEMENT OPERATOR</td>\n<td>35</td>\n</tr>\n<tr>\n<td> 4.2. INSTALLING THE KERNEL MODULE MANAGEMENT OPERATOR</td>\n<td>35</td>\n</tr>\n<tr>\n<td> 4.2.1. Installing the Kernel Module Management Operator using the web console</td>\n<td>35</td>\n</tr>\n<tr>\n<td> 4.2.2. Installing the Kernel Module Management Operator by using the CLI</td>\n<td>36</td>\n</tr>\n<tr>\n<td> 4.2.3. Installing the Kernel Module Management Operator on earlier versions of OpenShift Container Platform</td>\n<td>37</td>\n</tr>\n<tr>\n<td> 4.3. CONFIGURING THE KERNEL MODULE MANAGEMENT OPERATOR</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 4.3.1. Unloading the kernel module</td>\n<td>41</td>\n</tr>\n<tr>\n<td> 4.3.2. Setting the kernel firmware search path</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 4.4. UNINSTALLING THE KERNEL MODULE MANAGEMENT OPERATOR</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 4.4.1. Uninstalling a Red Hat catalog installation</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 4.4.2. Uninstalling a CLI installation</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.5. KERNEL MODULE DEPLOYMENT</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.5.1. The Module custom resource definition</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.5.2. Set soft dependencies between kernel modules</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 4.6. SECURITY AND PERMISSIONS</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 4.6.1. ServiceAccounts and SecurityContextConstraints</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 4.6.2. Pod security standards</td>\n<td>46</td>\n</tr>\n<tr>\n<td> 4.7. REPLACING IN-TREE MODULES WITH OUT-OF-TREE MODULES</td>\n<td>46</td>\n</tr>\n<tr>\n<td> 4.7.1. Example Module CR</td>\n<td>47</td>\n</tr>\n<tr>\n<td> 4.8. USING IN-TREE MODULES WITH THE DEVICE PLUGIN</td>\n<td>49</td>\n</tr>\n<tr>\n<td> 4.9. SYMBOLIC LINKS FOR IN-TREE DEPENDENCIES</td>\n<td>49</td>\n</tr>\n<tr>\n<td> 4.10. CREATING A KMOD IMAGE</td>\n<td>50</td>\n</tr>\n<tr>\n<td> 4.10.1. Running depmod</td>\n<td>51</td>\n</tr>\n<tr>\n<td> 4.10.2. Building in the cluster</td>\n<td>52</td>\n</tr>\n<tr>\n<td> 4.10.3. Using the Driver Toolkit</td>\n<td>53</td>\n</tr>\n<tr>\n<td> 4.11. USING SIGNING WITH KERNEL MODULE MANAGEMENT (KMM)</td>\n<td>53</td>\n</tr>\n<tr>\n<td> 4.11.1. Prerequisites</td>\n<td>54</td>\n</tr>\n<tr>\n<td> 4.12. ADDING THE KEYS FOR SECUREBOOT</td>\n<td>54</td>\n</tr>\n<tr>\n<td> 4.12.1. Checking the keys</td>\n<td>55</td>\n</tr>\n<tr>\n<td> 4.13. SIGNING KMODS IN A PRE-BUILT IMAGE</td>\n<td>55</td>\n</tr>\n<tr>\n<td> 4.14. BUILDING AND SIGNING A KMOD IMAGE</td>\n<td>56</td>\n</tr>\n<tr>\n<td> 4.15. USING TOLERATIONS FOR KERNEL MODULE SCHEDULING</td>\n<td>58</td>\n</tr>\n<tr>\n<td> 4.16. APPLYING TOLERATIONS TO KERNEL MODULE PODS</td>\n<td>58</td>\n</tr>\n</table>---\n\n<table>\n<tr><td>4.17. KMM HUB AND SPOKE</td><td>60</td></tr>\n<tr><td> 4.17.1. KMM-Hub</td><td>60</td></tr>\n<tr><td> 4.17.2. Installing KMM-Hub</td><td>61</td></tr>\n<tr><td> 4.17.2.1. Installing KMM-Hub using the Operator Lifecycle Manager</td><td>61</td></tr>\n<tr><td> 4.17.2.2. Installing KMM-Hub by creating KMM resources</td><td>61</td></tr>\n<tr><td> 4.17.3. Using the ManagedClusterModule CRD</td><td>62</td></tr>\n<tr><td> 4.17.4. Running KMM on the spoke</td><td>62</td></tr>\n<tr><td>4.18. CUSTOMIZING UPGRADES FOR KERNEL MODULES</td><td>64</td></tr>\n<tr><td>4.19. DAY 1 KERNEL MODULE LOADING</td><td>66</td></tr>\n<tr><td> 4.19.1. Day 1 supported use cases</td><td>66</td></tr>\n<tr><td> 4.19.2. OOT kernel module loading flow</td><td>66</td></tr>\n<tr><td> 4.19.3. The kernel module image</td><td>67</td></tr>\n<tr><td> 4.19.4. In-tree module replacement</td><td>67</td></tr>\n<tr><td> 4.19.5. MCO yaml creation</td><td>67</td></tr>\n<tr><td> 4.19.6. The MachineConfigPool</td><td>68</td></tr>\n<tr><td>4.20. MANAGING DAY 1 KMOD IMAGES</td><td>68</td></tr>\n<tr><td>4.21. DEBUGGING AND TROUBLESHOOTING</td><td>70</td></tr>\n<tr><td>4.22. KMM FIRMWARE SUPPORT</td><td>70</td></tr>\n<tr><td> 4.22.1. Configuring the lookup path on nodes</td><td>70</td></tr>\n<tr><td> 4.22.2. Building a kmod image</td><td>71</td></tr>\n<tr><td> 4.22.3. Tuning the Module resource</td><td>71</td></tr>\n<tr><td>4.23. DAY 0 THROUGH DAY 2 KMOD INSTALLATION</td><td>71</td></tr>\n<tr><td> 4.23.1. Layering background</td><td>72</td></tr>\n<tr><td> 4.23.2. Lifecycle management</td><td>72</td></tr>\n<tr><td> 4.23.2.1. Treat the kmod as an in-tree driver</td><td>72</td></tr>\n<tr><td> 4.23.2.2. Use ordered upgrade</td><td>73</td></tr>\n<tr><td>4.24. TROUBLESHOOTING KMM</td><td>73</td></tr>\n<tr><td> 4.24.1. Reading Operator logs</td><td>73</td></tr>\n<tr><td> 4.24.2. Observing events</td><td>73</td></tr>\n<tr><td> 4.24.2.1. Build & sign</td><td>73</td></tr>\n<tr><td> 4.24.2.2. Module load or unload</td><td>74</td></tr>\n<tr><td> 4.24.3. Using the must-gather tool</td><td>74</td></tr>\n<tr><td> 4.24.3.1. Gathering data for KMM</td><td>74</td></tr>\n<tr><td> 4.24.3.2. Gathering data for KMM-Hub</td><td>76</td></tr>\n<tr><td><b>CHAPTER 5. KERNEL MODULE MANAGEMENT OPERATOR RELEASE NOTES</b> .....</td><td><b>79</b></td></tr>\n<tr><td> 5.1. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.2</td><td>79</td></tr>\n<tr><td> 5.1.1. New features</td><td>79</td></tr>\n<tr><td> 5.2. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.3</td><td>79</td></tr>\n<tr><td> 5.2.1. New features</td><td>79</td></tr>\n<tr><td> 5.3. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.4</td><td>79</td></tr>\n<tr><td> 5.3.1. New features and enhancements</td><td>79</td></tr>\n<tr><td> 5.3.2. Notable technical changes</td><td>80</td></tr>\n<tr><td> 5.3.3. Bug fixes</td><td>80</td></tr>\n<tr><td> 5.3.4. Known issues</td><td>86</td></tr>\n<tr><td> 5.4. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.4.1</td><td>86</td></tr>\n<tr><td> 5.4.1. Known issues</td><td>86</td></tr>\n<tr><td> 5.5. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.5</td><td>86</td></tr>\n<tr><td> 5.5.1. New features and enhancements</td><td>86</td></tr>\n<tr><td> 5.5.2. Bug fixes</td><td>86</td></tr>\n<tr><td> 5.6. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.5.1</td><td>88</td></tr>\n<tr><td> 5.6.1. Known issues</td><td>88</td></tr>\n<tr><td> 5.7. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.6</td><td>88</td></tr>\n</table>\n\n---<table><tr><td>5.7.1. New features and enhancements</td><td>88</td></tr><tr><td>5.7.2. Bug fixes</td><td>89</td></tr><tr><td>5.7.3. Known issues</td><td>90</td></tr></table># CHAPTER 1. ABOUT SPECIALIZED HARDWARE AND DRIVER ENABLEMENT\n\nThe Driver Toolkit (DTK) is a container image in the OpenShift Container Platform payload which is meant to be used as a base image on which to build driver containers. The Driver Toolkit image contains the kernel packages commonly required as dependencies to build or install kernel modules as well as a few tools needed in driver containers. The version of these packages will match the kernel version running on the RHCOS nodes in the corresponding OpenShift Container Platform release.\n\nDriver containers are container images used for building and deploying out-of-tree kernel modules and drivers on container operating systems such as Red Hat Enterprise Linux CoreOS (RHCOS). Kernel modules and drivers are software libraries running with a high level of privilege in the operating system kernel. They extend the kernel functionalities or provide the hardware-specific code required to control new devices. Examples include hardware devices like field-programmable gate arrays (FPGA) or graphics processing units (GPU), and software-defined storage solutions, which all require kernel modules on client machines. Driver containers are the first layer of the software stack used to enable these technologies on OpenShift Container Platform deployments.## CHAPTER 2. DRIVER TOOLKIT\n\nLearn about the Driver Toolkit and how you can use it as a base image for driver containers for enabling special software and hardware devices on OpenShift Container Platform deployments.\n\n### 2.1. ABOUT THE DRIVER TOOLKIT\n\n#### 2.1.1. Background\n\nThe Driver Toolkit is a container image in the OpenShift Container Platform payload used as a base image on which you can build driver containers. The Driver Toolkit image includes the kernel packages commonly required as dependencies to build or install kernel modules, as well as a few tools needed in driver containers. The version of these packages will match the kernel version running on the Red Hat Enterprise Linux CoreOS (RHCOS) nodes in the corresponding OpenShift Container Platform release.\n\nDriver containers are container images used for building and deploying out-of-tree kernel modules and drivers on container operating systems like RHCOS. Kernel modules and drivers are software libraries running with a high level of privilege in the operating system kernel. They extend the kernel functionalities or provide the hardware-specific code required to control new devices. Examples include hardware devices like Field Programmable Gate Arrays (FPGA) or GPUs, and software-defined storage (SDS) solutions, such as Lustre parallel file systems, which require kernel modules on client machines. Driver containers are the first layer of the software stack used to enable these technologies on Kubernetes.\n\nThe list of kernel packages in the Driver Toolkit includes the following and their dependencies:\n\n- • **kernel-core**\n- • **kernel-devel**\n- • **kernel-headers**\n- • **kernel-modules**\n- • **kernel-modules-extra**\n\nIn addition, the Driver Toolkit also includes the corresponding real-time kernel packages:\n\n- • **kernel-rt-core**\n- • **kernel-rt-devel**\n- • **kernel-rt-modules**\n- • **kernel-rt-modules-extra**\n\nThe Driver Toolkit also has several tools that are commonly needed to build and install kernel modules, including:\n\n- • **elfutils-libelf-devel**\n- • **kmod**\n- • **binutils-kabi-dw**- • **kernel-abi-whitelists**\n- • dependencies for the above\n\n### 2.1.2. Purpose\n\nPrior to the Driver Toolkit's existence, users would install kernel packages in a pod or build config on OpenShift Container Platform using [entitled builds](#) or by installing from the kernel RPMs in the hosts **machine-os-content**. The Driver Toolkit simplifies the process by removing the entitlement step, and avoids the privileged operation of accessing the machine-os-content in a pod. The Driver Toolkit can also be used by partners who have access to pre-released OpenShift Container Platform versions to prebuild driver-containers for their hardware devices for future OpenShift Container Platform releases.\n\nThe Driver Toolkit is also used by the Kernel Module Management (KMM), which is currently available as a community Operator in the software catalog. KMM supports out-of-tree and third-party kernel drivers and the support software for the underlying operating system. Users can create modules for KMM to build and deploy a driver container, as well as support software like a device plugin, or metrics. Modules can include a build config to build a driver container-based on the Driver Toolkit, or KMM can deploy a prebuilt driver container.\n\n## 2.2. PULLING THE DRIVER TOOLKIT CONTAINER IMAGE\n\nThe **driver-toolkit** image is available from the [Container images section of the Red Hat Ecosystem Catalog](#) and in the OpenShift Container Platform release payload. The image corresponding to the most recent minor release of OpenShift Container Platform will be tagged with the version number in the catalog. The image URL for a specific release can be found using the **oc adm** CLI command.\n\n### 2.2.1. Pulling the Driver Toolkit container image from registry.redhat.io\n\nInstructions for pulling the **driver-toolkit** image from **registry.redhat.io** with **podman** or in OpenShift Container Platform can be found on the [Red Hat Ecosystem Catalog](#). The driver-toolkit image for the latest minor release are tagged with the minor release version on **registry.redhat.io**, for example: **registry.redhat.io/openshift4/driver-toolkit-rhel8:v4.21**.\n\n### 2.2.2. Finding the Driver Toolkit image URL in the payload\n\n#### Prerequisites\n\n- • You obtained the image [pull secret from Red Hat OpenShift Cluster Manager](#).\n- • You installed the OpenShift CLI (**oc**).\n\n#### Procedure\n\n1. 1. Use the **oc adm** command to extract the image URL of the **driver-toolkit** corresponding to a certain release:\n\n- • For an x86 image, the command is as follows:\n\n```\n$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.21.z-x86_64 --image-for=driver-toolkit\n```\n\n- • For an ARM image, the command is as follows:```\n$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.21.z-aarch64 --\nimage-for=driver-toolkit\n```\n\n### Example output\n\n```\nquay.io/openshift-release-dev/ocp-v4.0-art-\ndev@sha256:b53883ca2bac5925857148c4a1abc300ced96c222498e3bc134fe7ce3a1dd404\n```\n\n1. 2. Obtain this image using a valid pull secret, such as the pull secret required to install OpenShift Container Platform:\n\n```\n$ podman pull --authfile=path/to/pullsecret.json quay.io/openshift-release-dev/ocp-v4.0-art-\ndev@sha256:<SHA>\n```\n\n## 2.3. USING THE DRIVER TOOLKIT\n\nAs an example, the Driver Toolkit can be used as the base image for building a very simple kernel module called **simple-kmod**.\n\n### NOTE\n\nThe Driver Toolkit includes the necessary dependencies, **openssl**, **mokutil**, and **keyutils**, needed to sign a kernel module. However, in this example, the **simple-kmod** kernel module is not signed and therefore cannot be loaded on systems with **Secure Boot** enabled.\n\n### 2.3.1. Build and run the simple-kmod driver container on a cluster\n\n#### Prerequisites\n\n- • You have a running OpenShift Container Platform cluster.\n- • You set the Image Registry Operator state to **Managed** for your cluster.\n- • You installed the OpenShift CLI (**oc**).\n- • You are logged into the OpenShift CLI as a user with **cluster-admin** privileges.\n\n#### Procedure\n\nCreate a namespace. For example:\n\n```\n$ oc new-project simple-kmod-demo\n```\n\n1. 1. The YAML defines an **ImageStream** for storing the **simple-kmod** driver container image, and a **BuildConfig** for building the container. Save this YAML as **0000-buildconfig.yaml.template**.\n\n```\napiVersion: image.openshift.io/v1\nkind: ImageStream\nmetadata:\n labels:\n app: simple-kmod-driver-container\n``````\nname: simple-kmod-driver-container\nnamespace: simple-kmod-demo\nspec: {}\n---\napiVersion: build.openshift.io/v1\nkind: BuildConfig\nmetadata:\n labels:\n app: simple-kmod-driver-build\n name: simple-kmod-driver-build\n namespace: simple-kmod-demo\nspec:\n nodeSelector:\n node-role.kubernetes.io/worker: \"\"\n runPolicy: \"Serial\"\n triggers:\n - type: \"ConfigChange\"\n - type: \"ImageChange\"\n source:\n dockerfile: |\n ARG DTK\n FROM ${DTK} as builder\n\n ARG KVER\n\n WORKDIR /build/\n\n RUN git clone https://github.com/openshift-psap/simple-kmod.git\n\n WORKDIR /build/simple-kmod\n\n RUN make all install KVER=${KVER}\n\n FROM registry.redhat.io/ubi8/ubi-minimal\n\n ARG KVER\n\n # Required for installing `modprobe`\n RUN microdnf install kmod\n\n COPY --from=builder /lib/modules/${KVER}/simple-kmod.ko /lib/modules/${KVER}/\n COPY --from=builder /lib/modules/${KVER}/simple-procfs-kmod.ko\n/lib/modules/${KVER}/\n RUN depmod ${KVER}\n strategy:\n dockerStrategy:\n buildArgs:\n - name: KMODVER\n value: DEMO\n # $ oc adm release info quay.io/openshift-release-dev/ocp-release:<cluster version>-\nx86_64 --image-for=driver-toolkit\n - name: DTK\n value: quay.io/openshift-release-dev/ocp-v4.0-art-\ndev@sha256:34864ccd2f4b6e385705a730864c04a40908e57ace44457a783d739e377cae\n - name: KVER\n value: 4.18.0-372.26.1.el8_6.x86_64\n``````\n\noutput:\nto:\n kind: ImageStreamTag\n name: simple-kmod-driver-container:demo\n\n```\n\n1. 2. Substitute the correct driver toolkit image for the OpenShift Container Platform version you are running in place of “DRIVER\\_TOOLKIT\\_IMAGE” with the following commands.\n\n```\n$ OCP_VERSION=$(oc get clusterversion/version -ojsonpath={.status.desired.version})\n```\n\n```\n$ DRIVER_TOOLKIT_IMAGE=$(oc adm release info $OCP_VERSION --image-for=driver-toolkit)\n```\n\n```\n$ sed \"s#DRIVER_TOOLKIT_IMAGE#${DRIVER_TOOLKIT_IMAGE}#\" 0000-buildconfig.yaml.template > 0000-buildconfig.yaml\n```\n\n1. 3. Create the image stream and build config with\n\n```\n$ oc create -f 0000-buildconfig.yaml\n```\n\n1. 4. After the builder pod completes successfully, deploy the driver container image as a **DaemonSet**.\n\n1. a. The driver container must run with the privileged security context in order to load the kernel modules on the host. The following YAML file contains the RBAC rules and the **DaemonSet** for running the driver container. Save this YAML as **1000-drivercontainer.yaml**.\n\n```\n\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n name: simple-kmod-driver-container\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: Role\nmetadata:\n name: simple-kmod-driver-container\nrules:\n- apiGroups:\n - security.openshift.io\nresources:\n - securitycontextconstraints\nverbs:\n - use\nresourceNames:\n - privileged\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: RoleBinding\nmetadata:\n name: simple-kmod-driver-container\nroleRef:\n apiGroup: rbac.authorization.k8s.io\n kind: Role\n name: simple-kmod-driver-container\n\n``````\n\nsubjects:\n- kind: ServiceAccount\n name: simple-kmod-driver-container\nuserNames:\n- system:serviceaccount:simple-kmod-demo:simple-kmod-driver-container\n---\napiVersion: apps/v1\nkind: DaemonSet\nmetadata:\n name: simple-kmod-driver-container\nspec:\n selector:\n matchLabels:\n app: simple-kmod-driver-container\n template:\n metadata:\n labels:\n app: simple-kmod-driver-container\n spec:\n serviceAccount: simple-kmod-driver-container\n serviceAccountName: simple-kmod-driver-container\n containers:\n - image: image-registry.openshift-image-registry.svc:5000/simple-kmod-\ndemo/simple-kmod-driver-container:demo\n name: simple-kmod-driver-container\n imagePullPolicy: Always\n command: [sleep, infinity]\n lifecycle:\n postStart:\n exec:\n command: [\"modprobe\", \"-v\", \"-a\", \"simple-kmod\", \"simple-procfs-kmod\"]\n preStop:\n exec:\n command: [\"modprobe\", \"-r\", \"-a\", \"simple-kmod\", \"simple-procfs-kmod\"]\n securityContext:\n privileged: true\n nodeSelector:\n node-role.kubernetes.io/worker: \"\"\n\n```\n\nb. Create the RBAC rules and daemon set:\n\n```\n$ oc create -f 1000-drivercontainer.yaml\n```\n\n5. After the pods are running on the worker nodes, verify that the **simple\\_kmod** kernel module is loaded successfully on the host machines with **lsmod**.\n\na. Verify that the pods are running:\n\n```\n$ oc get pod -n simple-kmod-demo\n```\n\n### Example output\n\n<table>\n<thead>\n<tr>\n<th>NAME</th>\n<th>READY</th>\n<th>STATUS</th>\n<th>RESTARTS</th>\n<th>AGE</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>simple-kmod-driver-build-1-build</td>\n<td>0/1</td>\n<td>Completed</td>\n<td>0</td>\n<td>6m</td>\n</tr>\n<tr>\n<td>simple-kmod-driver-container-b22fd</td>\n<td>1/1</td>\n<td>Running</td>\n<td>0</td>\n<td>40s</td>\n</tr>\n</tbody>\n</table>```\nsimple-kmod-driver-container-jz9vn 1/1 Running 0 40s \nsimple-kmod-driver-container-p45cc 1/1 Running 0 40s\n```\n\nb. Execute the **lsmod** command in the driver container pod:\n\n```\n$ oc exec -it pod/simple-kmod-driver-container-p45cc -- lsmod | grep simple\n```\n\n#### Example output\n\n```\nsimple_proofs_kmod 16384 0 \nsimple_kmod 16384 0\n```\n\n## 2.4. ADDITIONAL RESOURCES\n\n- • For more information about configuring registry storage for your cluster, see [Image Registry Operator in OpenShift Container Platform](#).## CHAPTER 3. NODE FEATURE DISCOVERY OPERATOR\n\nLearn about the Node Feature Discovery (NFD) Operator and how you can use it to expose node-level information by orchestrating Node Feature Discovery, a Kubernetes add-on for detecting hardware features and system configuration.\n\nThe Node Feature Discovery Operator (NFD) manages the detection of hardware features and configuration in an OpenShift Container Platform cluster by labeling the nodes with hardware-specific information. NFD labels the host with node-specific attributes, such as PCI cards, kernel, operating system version, and so on.\n\nThe NFD Operator can be found on the Operator Hub by searching for “Node Feature Discovery”.\n\n### 3.1. INSTALLING THE NODE FEATURE DISCOVERY OPERATOR\n\nThe Node Feature Discovery (NFD) Operator orchestrates all resources needed to run the NFD daemon set. As a cluster administrator, you can install the NFD Operator by using the OpenShift Container Platform CLI or the web console.\n\n#### 3.1.1. Installing the NFD Operator using the CLI\n\nAs a cluster administrator, you can install the NFD Operator using the CLI.\n\n##### Prerequisites\n\n- • An OpenShift Container Platform cluster\n- • Install the OpenShift CLI (**oc**).\n- • Log in as a user with **cluster-admin** privileges.\n\n##### Procedure\n\n1. 1. Create a namespace for the NFD Operator.\n 1. a. Create the following **Namespace** custom resource (CR) that defines the **openshift-nfd** namespace, and then save the YAML in the **nfd-namespace.yaml** file. Set **cluster-monitoring** to **\"true\"**.\n\n```\napiVersion: v1\nkind: Namespace\nmetadata:\n name: openshift-nfd\n labels:\n name: openshift-nfd\n openshift.io/cluster-monitoring: \"true\"\n```\n\n1. b. Create the namespace by running the following command:\n\n```\n$ oc create -f nfd-namespace.yaml\n```\n\n1. 2. Install the NFD Operator in the namespace you created in the previous step by creating the following objects:\n 1. a. Create the following **OperatorGroup** CR and save the YAML in the **nfd**a. Create the following **OperatorGroup** CR and save the YAML in the **nfd-operatorgroup.yaml** file:\n\n```\napiVersion: operators.coreos.com/v1\nkind: OperatorGroup\nmetadata:\n generateName: openshift-nfd-\n name: openshift-nfd\n namespace: openshift-nfd\nspec:\n targetNamespaces:\n - openshift-nfd\n```\n\nb. Create the **OperatorGroup** CR by running the following command:\n\n```\n$ oc create -f nfd-operatorgroup.yaml\n```\n\nc. Create the following **Subscription** CR and save the YAML in the **nfd-sub.yaml** file:\n\n### Example Subscription\n\n```\napiVersion: operators.coreos.com/v1alpha1\nkind: Subscription\nmetadata:\n name: nfd\n namespace: openshift-nfd\nspec:\n channel: \"stable\"\n installPlanApproval: Automatic\n name: nfd\n source: redhat-operators\n sourceNamespace: openshift-marketplace\n```\n\nd. Create the subscription object by running the following command:\n\n```\n$ oc create -f nfd-sub.yaml\n```\n\ne. Change to the **openshift-nfd** project:\n\n```\n$ oc project openshift-nfd\n```\n\n### Verification\n\n- • To verify that the Operator deployment is successful, run:\n\n```\n$ oc get pods\n```\n\n### Example output\n\n```\nNAME READY STATUS RESTARTS AGE\nnfd-controller-manager-7f86ccfb58-vgr4x 2/2 Running 0 10m\n```\n\nA successful deployment shows a **Running** status.### 3.1.2. Installing the NFD Operator using the web console\n\nAs a cluster administrator, you can install the NFD Operator using the web console.\n\n#### Procedure\n\n1. 1. In the OpenShift Container Platform web console, click **Ecosystem** → **Software Catalog**.\n2. 2. Choose **Node Feature Discovery** from the list of available Operators, and then click **Install**.\n3. 3. On the **Install Operator** page, select **A specific namespace on the cluster**, and then click **Install**. You do not need to create a namespace because it is created for you.\n\n#### Verification\n\nTo verify that the NFD Operator installed successfully:\n\n1. 1. Navigate to the **Ecosystem** → **Installed Operators** page.\n2. 2. Ensure that **Node Feature Discovery** is listed in the **openshift-nfd** project with a **Status** of **InstallSucceeded**.\n\n#### NOTE\n\nDuring installation an Operator might display a **Failed** status. If the installation later succeeds with an **InstallSucceeded** message, you can ignore the **Failed** message.\n\n#### Troubleshooting\n\nIf the Operator does not appear as installed, troubleshoot further:\n\n1. 1. Navigate to the **Ecosystem** → **Installed Operators** page and inspect the **Operator Subscriptions** and **Install Plans** tabs for any failure or errors under **Status**.\n2. 2. Navigate to the **Workloads** → **Pods** page and check the logs for pods in the **openshift-nfd** project.\n\n## 3.2. USING THE NODE FEATURE DISCOVERY OPERATOR\n\nThe Node Feature Discovery (NFD) Operator orchestrates all resources needed to run the Node-Feature-Discovery daemon set by watching for a **NodeFeatureDiscovery** custom resource (CR). Based on the **NodeFeatureDiscovery** CR, the Operator creates the operand (NFD) components in the selected namespace. You can edit the CR to use another namespace, image, image pull policy, and **nfd-worker-conf** config map, among other options.\n\nAs a cluster administrator, you can create a **NodeFeatureDiscovery** CR by using the OpenShift CLI (**oc**) or the web console.**NOTE**\n\nStarting with version 4.12, the **operand.image** field in the **NodeFeatureDiscovery** CR is mandatory. If the NFD Operator is deployed by using Operator Lifecycle Manager (OLM), OLM automatically sets the **operand.image** field. If you create the **NodeFeatureDiscovery** CR by using the OpenShift Container Platform CLI or the OpenShift Container Platform web console, you must set the **operand.image** field explicitly.\n\n**3.2.1. Creating a NodeFeatureDiscovery CR by using the CLI**\n\nAs a cluster administrator, you can create a **NodeFeatureDiscovery** CR instance by using the OpenShift CLI (**oc**).\n\n**NOTE**\n\nThe **spec.operand.image** setting requires a **-rhel9** image to be defined for use with OpenShift Container Platform releases 4.13 and later.\n\nThe following example shows the use of **-rhel9** to acquire the correct image.\n\n**Prerequisites**\n\n- • You have access to an OpenShift Container Platform cluster\n- • You installed the OpenShift CLI (**oc**).\n- • You logged in as a user with **cluster-admin** privileges.\n- • You installed the NFD Operator.\n\n**Procedure**\n\n1. 1. Create a **NodeFeatureDiscovery** CR:\n\n**Example NodeFeatureDiscovery CR**\n\n```\napiVersion: nfd.openshift.io/v1\nkind: NodeFeatureDiscovery\nmetadata:\n name: nfd-instance\n namespace: openshift-nfd\nspec:\n instance: \"\" # instance is empty by default\n topologyUpdater: false # False by default\n operand:\n image: registry.redhat.io/openshift4/ose-node-feature-discovery-rhel9:v4.21 1\n imagePullPolicy: Always\n workerConfig:\n configData: |\n core:\n # labelWhiteList:\n # noPublish: false\n sleepInterval: 60s\n``````\n# sources: [all]\n# klog:\n# addDirHeader: false\n# alsoLogtostderr: false\n# logBacktraceAt:\n# logtostderr: true\n# skipHeaders: false\n# stderrthreshold: 2\n# v: 0\n# vmodule:\n## NOTE: the following options are not dynamically run-time configurable\n## and require a nfd-worker restart to take effect after being changed\n# logDir:\n# logFile:\n# logFileMaxSize: 1800\n# skipLogHeaders: false\nsources:\n cpu:\n cpuid:\n# NOTE: whitelist has priority over blacklist\n attributeBlacklist:\n - \"BMI1\"\n - \"BMI2\"\n - \"CLMUL\"\n - \"CMOV\"\n - \"CX16\"\n - \"ERMS\"\n - \"F16C\"\n - \"HTT\"\n - \"LZCNT\"\n - \"MMX\"\n - \"MMXEXT\"\n - \"NX\"\n - \"POPCNT\"\n - \"RDRAND\"\n - \"RDSEED\"\n - \"RDTSCP\"\n - \"SGX\"\n - \"SSE\"\n - \"SSE2\"\n - \"SSE3\"\n - \"SSE4.1\"\n - \"SSE4.2\"\n - \"SSSE3\"\n attributeWhitelist:\nkernel:\n kconfigFile: \"/path/to/kconfig\"\n configOpts:\n - \"NO_HZ\"\n - \"X86\"\n - \"DMI\"\npci:\n deviceClassWhitelist:\n - \"0200\"\n - \"03\"\n - \"12\"\n``````\n\ndeviceLabelFields:\n - \"class\"\ncustomConfig:\n configData: |\n - name: \"more.kernel.features\"\n matchOn:\n - loadedKMod: [\"example_kmod3\"]\n\n```\n\n**1** The **operand.image** field is mandatory.\n\n2. Create the **NodeFeatureDiscovery** CR by running the following command:\n\n```\n$ oc apply -f <filename>\n```\n\n## Verification\n\n1. Check that the **NodeFeatureDiscovery** CR was created by running the following command:\n\n```\n$ oc get pods\n```\n\n### Example output\n\n<table>\n<thead>\n<tr>\n<th>NAME</th>\n<th>READY</th>\n<th>STATUS</th>\n<th>RESTARTS</th>\n<th>AGE</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>nfd-controller-manager-7f86ccfb58-vgr4x</td>\n<td>2/2</td>\n<td>Running</td>\n<td>0</td>\n<td>11m</td>\n</tr>\n<tr>\n<td>nfd-master-hcn64</td>\n<td>1/1</td>\n<td>Running</td>\n<td>0</td>\n<td>60s</td>\n</tr>\n<tr>\n<td>nfd-master-lnnxx</td>\n<td>1/1</td>\n<td>Running</td>\n<td>0</td>\n<td>60s</td>\n</tr>\n<tr>\n<td>nfd-master-mp6hr</td>\n<td>1/1</td>\n<td>Running</td>\n<td>0</td>\n<td>60s</td>\n</tr>\n<tr>\n<td>nfd-worker-vgcz9</td>\n<td>1/1</td>\n<td>Running</td>\n<td>0</td>\n<td>60s</td>\n</tr>\n<tr>\n<td>nfd-worker-xqbw5</td>\n<td>1/1</td>\n<td>Running</td>\n<td>0</td>\n<td>60s</td>\n</tr>\n</tbody>\n</table>\n\nA successful deployment shows a **Running** status.\n\n### 3.2.2. Creating a NodeFeatureDiscovery CR by using the CLI in a disconnected environment\n\nAs a cluster administrator, you can create a **NodeFeatureDiscovery** CR instance by using the OpenShift CLI (**oc**).\n\n#### Prerequisites\n\n- • You have access to an OpenShift Container Platform cluster\n- • You installed the OpenShift CLI (**oc**).\n- • You logged in as a user with **cluster-admin** privileges.\n- • You installed the NFD Operator.\n- • You have access to a mirror registry with the required images.\n- • You installed the **skopeo** CLI tool.\n\n**Procedure**## Procedure\n\n1. Determine the digest of the registry image:\n\n1. Run the following command:\n\n```\n$ skopeo inspect docker://registry.redhat.io/openshift4/ose-node-feature-discovery:\n<openshift_version>\n```\n\n### Example command\n\n```\n$ skopeo inspect docker://registry.redhat.io/openshift4/ose-node-feature-discovery:v4.12\n```\n\n1. Inspect the output to identify the image digest:\n\n### Example output\n\n```\n{\n ...\n \"Digest\":\n \"sha256:1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef\",\n ...\n}\n```\n\n1. Use the **skopeo** CLI tool to copy the image from **registry.redhat.io** to your mirror registry, by running the following command:\n\n```\nskopeo copy docker://registry.redhat.io/openshift4/ose-node-feature-\ndiscovery@<image_digest> docker://<mirror_registry>/openshift4/ose-node-feature-\ndiscovery@<image_digest>\n```\n\n### Example command\n\n```\nskopeo copy docker://registry.redhat.io/openshift4/ose-node-feature-\ndiscovery@sha256:1234567890abcdef1234567890abcdef1234567890abcd\nef docker://<your-mirror-registry>/openshift4/ose-node-feature-\ndiscovery@sha256:1234567890abcdef1234567890abcdef1234567890abcd\nef\n```\n\n1. Create a **NodeFeatureDiscovery** CR:\n\n### Example NodeFeatureDiscovery CR\n\n```\napiVersion: nfd.openshift.io/v1\nkind: NodeFeatureDiscovery\nmetadata:\n name: nfd-instance\nspec:\n operand:\n image: <mirror_registry>/openshift4/ose-node-feature-discovery@<image_digest> 1\n imagePullPolicy: Always\n workerConfig:\n configData: |\n core:\n``````\n# labelWhiteList:\n# noPublish: false\n# sleepInterval: 60s\n# sources: [all]\n# klog:\n# addDirHeader: false\n# alsologtostderr: false\n# logBacktraceAt:\n# logtostderr: true\n# skipHeaders: false\n# stderrthreshold: 2\n# v: 0\n# vmodule:\n## NOTE: the following options are not dynamically run-time configurable\n## and require a nfd-worker restart to take effect after being changed\n# logDir:\n# logFile:\n# logFileMaxSize: 1800\n# skipLogHeaders: false\nsources:\n cpu:\n cpuid:\n# NOTE: whitelist has priority over blacklist\n attributeBlacklist:\n - \"BMI1\"\n - \"BMI2\"\n - \"CLMUL\"\n - \"CMOV\"\n - \"CX16\"\n - \"ERMS\"\n - \"F16C\"\n - \"HTT\"\n - \"LZCNT\"\n - \"MMX\"\n - \"MMXEXT\"\n - \"NX\"\n - \"POPCNT\"\n - \"RDRAND\"\n - \"RDSEED\"\n - \"RDTSCP\"\n - \"SGX\"\n - \"SSE\"\n - \"SSE2\"\n - \"SSE3\"\n - \"SSE4.1\"\n - \"SSE4.2\"\n - \"SSSE3\"\n attributeWhitelist:\nkernel:\n kconfigFile: \"/path/to/kconfig\"\n configOpts:\n - \"NO_HZ\"\n - \"X86\"\n - \"DMI\"\npci:\n deviceClassWhitelist:\n``````\n- \"0200\" \n- \"03\" \n- \"12\" \ndeviceLabelFields: \n - \"class\" \ncustomConfig: \n configData: | \n - name: \"more.kernel.features\" \n matchOn: \n - loadedKMod: [\"example_kmod3\"]\n```\n\n**1** The **operand.image** field is mandatory.\n\n4. Create the **NodeFeatureDiscovery** CR by running the following command:\n\n```\n$ oc apply -f <filename>\n```\n\n## Verification\n\n1. Check the status of the **NodeFeatureDiscovery** CR by running the following command:\n\n```\n$ oc get nodefeaturediscovery nfd-instance -o yaml\n```\n\n2. Check that the pods are running without **ImagePullBackOff** errors by running the following command:\n\n```\n$ oc get pods -n <nfd_namespace>\n```\n\n### 3.2.3. Creating a NodeFeatureDiscovery CR by using the web console\n\nAs a cluster administrator, you can create a **NodeFeatureDiscovery** CR by using the OpenShift Container Platform web console.\n\n#### Prerequisites\n\n- • You have access to an OpenShift Container Platform cluster\n- • You logged in as a user with **cluster-admin** privileges.\n- • You installed the NFD Operator.\n\n#### Procedure\n\n1. 1. Navigate to the **Ecosystem → Installed Operators** page.\n2. 2. In the **Node Feature Discovery** section, under **Provided APIs**, click **Create instance**.\n3. 3. Edit the values of the **NodeFeatureDiscovery** CR.\n4. 4. Click **Create**.## NOTE\n\nStarting with version 4.12, the **operand.image** field in the **NodeFeatureDiscovery** CR is mandatory. If the NFD Operator is deployed by using Operator Lifecycle Manager (OLM), OLM automatically sets the **operand.image** field. If you create the **NodeFeatureDiscovery** CR by using the OpenShift Container Platform CLI or the OpenShift Container Platform web console, you must set the **operand.image** field explicitly.\n\n## 3.3. CONFIGURING THE NODE FEATURE DISCOVERY OPERATOR\n\n### 3.3.1. core\n\nThe **core** section contains common configuration settings that are not specific to any particular feature source.\n\n#### 3.3.1.1. core.sleepInterval\n\n**core.sleepInterval** specifies the interval between consecutive passes of feature detection or re-detection, and thus also the interval between node re-labeling. A non-positive value implies infinite sleep interval; no re-detection or re-labeling is done.\n\nThis value is overridden by the deprecated **--sleep-interval** command-line flag, if specified.\n\n#### Example usage\n\n```\ncore:\n sleepInterval: 60s 1\n```\n\nThe default value is **60s**.\n\n#### 3.3.1.2. core.sources\n\n**core.sources** specifies the list of enabled feature sources. A special value **all** enables all feature sources.\n\nThis value is overridden by the deprecated **--sources** command-line flag, if specified.\n\nDefault: **[all]**\n\n#### Example usage\n\n```\ncore:\n sources:\n - system\n - custom\n```\n\n#### 3.3.1.3. core.labelWhiteList\n\n**core.labelWhiteList** specifies a regular expression for filtering feature labels based on the label name. Non-matching labels are not published.The regular expression is only matched against the basename part of the label, the part of the name after '/'. The label prefix, or namespace, is omitted.\n\nThis value is overridden by the deprecated **--label-whitelist** command-line flag, if specified.\n\nDefault: **null**\n\n### Example usage\n\n```\ncore: \n labelWhiteList: '^cpu-cpuid'\n```\n\n#### 3.3.1.4. core.noPublish\n\nSetting **core.noPublish** to **true** disables all communication with the **nfd-master**. It is effectively a dry run flag; **nfd-worker** runs feature detection normally, but no labeling requests are sent to **nfd-master**.\n\nThis value is overridden by the **--no-publish** command-line flag, if specified.\n\nExample:\n\n### Example usage\n\n```\ncore: \n noPublish: true \n```\n\nThe default value is **false**.\n\n#### 3.3.2. core.klog\n\nThe following options specify the logger configuration, most of which can be dynamically adjusted at run-time.\n\nThe logger options can also be specified using command-line flags, which take precedence over any corresponding config file options.\n\n##### 3.3.2.1. core.klog.addDirHeader\n\nIf set to **true**, **core.klog.addDirHeader** adds the file directory to the header of the log messages.\n\nDefault: **false**\n\nRun-time configurable: yes\n\n##### 3.3.2.2. core.klog.alsologtostderr\n\nLog to standard error as well as files.\n\nDefault: **false**\n\nRun-time configurable: yes\n\n##### 3.3.2.3. core.klog.logBacktraceAtWhen logging hits line file:N, emit a stack trace.\n\nDefault: **empty**\n\nRun-time configurable: yes\n\n#### 3.3.2.4. core.klog.logDir\n\nIf non-empty, write log files in this directory.\n\nDefault: **empty**\n\nRun-time configurable: no\n\n#### 3.3.2.5. core.klog.logFile\n\nIf not empty, use this log file.\n\nDefault: **empty**\n\nRun-time configurable: no\n\n#### 3.3.2.6. core.klog.logFileSize\n\n**core.klog.logFileSize** defines the maximum size a log file can grow to. Unit is megabytes. If the value is **0**, the maximum file size is unlimited.\n\nDefault: **1800**\n\nRun-time configurable: no\n\n#### 3.3.2.7. core.klog.logtostderr\n\nLog to standard error instead of files\n\nDefault: **true**\n\nRun-time configurable: yes\n\n#### 3.3.2.8. core.klog.skipHeaders\n\nIf **core.klog.skipHeaders** is set to **true**, avoid header prefixes in the log messages.\n\nDefault: **false**\n\nRun-time configurable: yes\n\n#### 3.3.2.9. core.klog.skipLogHeaders\n\nIf **core.klog.skipLogHeaders** is set to **true**, avoid headers when opening log files.\n\nDefault: **false**\n\nRun-time configurable: no### 3.3.2.10. core.klog.stderrthreshold\n\nLogs at or above this threshold go to stderr.\n\nDefault: **2**\n\nRun-time configurable: yes\n\n### 3.3.2.11. core.klog.v\n\n**core.klog.v** is the number for the log level verbosity.\n\nDefault: **0**\n\nRun-time configurable: yes\n\n### 3.3.2.12. core.klog.vmodule\n\n**core.klog.vmodule** is a comma-separated list of **pattern=N** settings for file-filtered logging.\n\nDefault: **empty**\n\nRun-time configurable: yes\n\n## 3.3.3. sources\n\nThe **sources** section contains feature source specific configuration parameters.\n\n### 3.3.3.1. sources.cpu.cpuid.attributeBlacklist\n\nPrevent publishing **cpuid** features listed in this option.\n\nThis value is overridden by **sources.cpu.cpuid.attributeWhitelist**, if specified.\n\nDefault: **[BMI1, BMI2, CLMUL, CMOV, CX16, ERMS, F16C, HTT, LZCNT, MMX, MMXEXT, NX, POPCNT, RDRAND, RDSEED, RDTSCP, SGX, SGXLC, SSE, SSE2, SSE3, SSE4.1, SSE4.2, SSSE3]**\n\n#### Example usage\n\n```\nsources:\n cpu:\n cpuid:\n attributeBlacklist: [MMX, MMXEXT]\n```\n\n### 3.3.3.2. sources.cpu.cpuid.attributeWhitelist\n\nOnly publish the **cpuid** features listed in this option.\n\n**sources.cpu.cpuid.attributeWhitelist** takes precedence over **sources.cpu.cpuid.attributeBlacklist**.\n\nDefault: **empty**\n\n#### Example usage"},"html":{"kind":"string","value":"<h1>OpenShift Container Platform 4.21</h1><h2>Specialized hardware and driver enablement</h2><p>Learn about hardware enablement on OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 Specialized hardware and driver enablement</h2><hr/><p>Learn about hardware enablement on OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.</p><p>Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.</p><p>Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.</p><p>Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.</p><p>XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.</p><p>The OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.</p><p>All other trademarks are the property of their respective owners.</p><h2>Abstract</h2><p>This document provides an overview of hardware enablement in OpenShift Container Platform.</p>\n<h1>Table of Contents</h1>\n\n<table>\n<tr>\n<td><b>CHAPTER 1. ABOUT SPECIALIZED HARDWARE AND DRIVER ENABLEMENT</b> .....</td>\n<td><b>6</b></td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. DRIVER TOOLKIT</b> .....</td>\n<td><b>7</b></td>\n</tr>\n<tr>\n<td> 2.1. ABOUT THE DRIVER TOOLKIT</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 2.1.1. Background</td>\n<td>7</td>\n</tr>\n<tr>\n<td> 2.1.2. Purpose</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.2. PULLING THE DRIVER TOOLKIT CONTAINER IMAGE</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.2.1. Pulling the Driver Toolkit container image from registry.redhat.io</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.2.2. Finding the Driver Toolkit image URL in the payload</td>\n<td>8</td>\n</tr>\n<tr>\n<td> 2.3. USING THE DRIVER TOOLKIT</td>\n<td>9</td>\n</tr>\n<tr>\n<td> 2.3.1. Build and run the simple-kmod driver container on a cluster</td>\n<td>9</td>\n</tr>\n<tr>\n<td> 2.4. ADDITIONAL RESOURCES</td>\n<td>13</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. NODE FEATURE DISCOVERY OPERATOR</b> .....</td>\n<td><b>14</b></td>\n</tr>\n<tr>\n<td> 3.1. INSTALLING THE NODE FEATURE DISCOVERY OPERATOR</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 3.1.1. Installing the NFD Operator using the CLI</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 3.1.2. Installing the NFD Operator using the web console</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 3.2. USING THE NODE FEATURE DISCOVERY OPERATOR</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 3.2.1. Creating a NodeFeatureDiscovery CR by using the CLI</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 3.2.2. Creating a NodeFeatureDiscovery CR by using the CLI in a disconnected environment</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.3. Creating a NodeFeatureDiscovery CR by using the web console</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 3.3. CONFIGURING THE NODE FEATURE DISCOVERY OPERATOR</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.3.1. core</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.3.1.1. core.sleepInterval</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.3.1.2. core.sources</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.3.1.3. core.labelWhitelist</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.3.1.4. core.noPublish</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.2. core.klog</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.2.1. core.klog.addDirHeader</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.2.2. core.klog.alsologtostderr</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.2.3. core.klog.logBacktraceAt</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.2.4. core.klog.logDir</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.3.2.5. core.klog.logFile</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.3.2.6. core.klog.logFileMaxSize</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.3.2.7. core.klog.logtostderr</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.3.2.8. core.klog.skipHeaders</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.3.2.9. core.klog.skipLogHeaders</td>\n<td>25</td>\n</tr>\n<tr>\n<td> 3.3.2.10. core.klog.stderrthreshold</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 3.3.2.11. core.klog.v</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 3.3.2.12. core.klog.vmodule</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 3.3.3. sources</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 3.3.3.1. sources.cpu.cpuid.attributeBlacklist</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 3.3.3.2. sources.cpu.cpuid.attributeWhitelist</td>\n<td>26</td>\n</tr>\n<tr>\n<td> 3.3.3.3. sources.kernel.kconfigFile</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.3.3.4. sources.kernel.configOpts</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.3.3.5. sources.pci.deviceClassWhitelist</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.3.3.6. sources.pci.deviceLabelFields</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.3.3.7. sources.usb.deviceClassWhitelist</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.3.3.8. sources.usb.deviceLabelFields</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.3.3.9. sources.custom</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.4. ABOUT THE NODEFEATURERULE CUSTOM RESOURCE</td>\n<td>29</td>\n</tr>\n</table>\n\n<table>\n<tr>\n<td>3.5. USING THE NODEFEATURERULE CUSTOM RESOURCE</td>\n<td>29</td>\n</tr>\n<tr>\n<td>3.6. USING THE NFD TOPOLOGY UPDATER</td>\n<td>30</td>\n</tr>\n<tr>\n<td> 3.6.1. NodeResourceTopology CR</td>\n<td>30</td>\n</tr>\n<tr>\n<td> 3.6.2. NFD Topology Updater command-line flags</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.6.2.1. -ca-file</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.6.2.2. -cert-file</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.6.2.3. -h, -help</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.6.2.4. -key-file</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.6.2.5. -kubelet-config-file</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.6.2.6. -no-publish</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.6.2.7. -oneshot</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.6.2.8. -podresources-socket</td>\n<td>32</td>\n</tr>\n<tr>\n<td> 3.6.2.9. -server</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.6.2.10. -server-name-override</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.6.2.11. -sleep-interval</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.6.2.12. -version</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.6.2.13. -watch-namespace</td>\n<td>33</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. KERNEL MODULE MANAGEMENT OPERATOR</b> .....</td>\n<td><b>35</b></td>\n</tr>\n<tr>\n<td> 4.1. ABOUT THE KERNEL MODULE MANAGEMENT OPERATOR</td>\n<td>35</td>\n</tr>\n<tr>\n<td> 4.2. INSTALLING THE KERNEL MODULE MANAGEMENT OPERATOR</td>\n<td>35</td>\n</tr>\n<tr>\n<td> 4.2.1. Installing the Kernel Module Management Operator using the web console</td>\n<td>35</td>\n</tr>\n<tr>\n<td> 4.2.2. Installing the Kernel Module Management Operator by using the CLI</td>\n<td>36</td>\n</tr>\n<tr>\n<td> 4.2.3. Installing the Kernel Module Management Operator on earlier versions of OpenShift Container Platform</td>\n<td>37</td>\n</tr>\n<tr>\n<td> 4.3. CONFIGURING THE KERNEL MODULE MANAGEMENT OPERATOR</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 4.3.1. Unloading the kernel module</td>\n<td>41</td>\n</tr>\n<tr>\n<td> 4.3.2. Setting the kernel firmware search path</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 4.4. UNINSTALLING THE KERNEL MODULE MANAGEMENT OPERATOR</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 4.4.1. Uninstalling a Red Hat catalog installation</td>\n<td>42</td>\n</tr>\n<tr>\n<td> 4.4.2. Uninstalling a CLI installation</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.5. KERNEL MODULE DEPLOYMENT</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.5.1. The Module custom resource definition</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.5.2. Set soft dependencies between kernel modules</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 4.6. SECURITY AND PERMISSIONS</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 4.6.1. ServiceAccounts and SecurityContextConstraints</td>\n<td>45</td>\n</tr>\n<tr>\n<td> 4.6.2. Pod security standards</td>\n<td>46</td>\n</tr>\n<tr>\n<td> 4.7. REPLACING IN-TREE MODULES WITH OUT-OF-TREE MODULES</td>\n<td>46</td>\n</tr>\n<tr>\n<td> 4.7.1. Example Module CR</td>\n<td>47</td>\n</tr>\n<tr>\n<td> 4.8. USING IN-TREE MODULES WITH THE DEVICE PLUGIN</td>\n<td>49</td>\n</tr>\n<tr>\n<td> 4.9. SYMBOLIC LINKS FOR IN-TREE DEPENDENCIES</td>\n<td>49</td>\n</tr>\n<tr>\n<td> 4.10. CREATING A KMOD IMAGE</td>\n<td>50</td>\n</tr>\n<tr>\n<td> 4.10.1. Running depmod</td>\n<td>51</td>\n</tr>\n<tr>\n<td> 4.10.2. Building in the cluster</td>\n<td>52</td>\n</tr>\n<tr>\n<td> 4.10.3. Using the Driver Toolkit</td>\n<td>53</td>\n</tr>\n<tr>\n<td> 4.11. USING SIGNING WITH KERNEL MODULE MANAGEMENT (KMM)</td>\n<td>53</td>\n</tr>\n<tr>\n<td> 4.11.1. Prerequisites</td>\n<td>54</td>\n</tr>\n<tr>\n<td> 4.12. ADDING THE KEYS FOR SECUREBOOT</td>\n<td>54</td>\n</tr>\n<tr>\n<td> 4.12.1. Checking the keys</td>\n<td>55</td>\n</tr>\n<tr>\n<td> 4.13. SIGNING KMODS IN A PRE-BUILT IMAGE</td>\n<td>55</td>\n</tr>\n<tr>\n<td> 4.14. BUILDING AND SIGNING A KMOD IMAGE</td>\n<td>56</td>\n</tr>\n<tr>\n<td> 4.15. USING TOLERATIONS FOR KERNEL MODULE SCHEDULING</td>\n<td>58</td>\n</tr>\n<tr>\n<td> 4.16. APPLYING TOLERATIONS TO KERNEL MODULE PODS</td>\n<td>58</td>\n</tr>\n</table>\n\n<hr/>\n<table>\n<tr><td>4.17. KMM HUB AND SPOKE</td><td>60</td></tr>\n<tr><td> 4.17.1. KMM-Hub</td><td>60</td></tr>\n<tr><td> 4.17.2. Installing KMM-Hub</td><td>61</td></tr>\n<tr><td> 4.17.2.1. Installing KMM-Hub using the Operator Lifecycle Manager</td><td>61</td></tr>\n<tr><td> 4.17.2.2. Installing KMM-Hub by creating KMM resources</td><td>61</td></tr>\n<tr><td> 4.17.3. Using the ManagedClusterModule CRD</td><td>62</td></tr>\n<tr><td> 4.17.4. Running KMM on the spoke</td><td>62</td></tr>\n<tr><td>4.18. CUSTOMIZING UPGRADES FOR KERNEL MODULES</td><td>64</td></tr>\n<tr><td>4.19. DAY 1 KERNEL MODULE LOADING</td><td>66</td></tr>\n<tr><td> 4.19.1. Day 1 supported use cases</td><td>66</td></tr>\n<tr><td> 4.19.2. OOT kernel module loading flow</td><td>66</td></tr>\n<tr><td> 4.19.3. The kernel module image</td><td>67</td></tr>\n<tr><td> 4.19.4. In-tree module replacement</td><td>67</td></tr>\n<tr><td> 4.19.5. MCO yaml creation</td><td>67</td></tr>\n<tr><td> 4.19.6. The MachineConfigPool</td><td>68</td></tr>\n<tr><td>4.20. MANAGING DAY 1 KMOD IMAGES</td><td>68</td></tr>\n<tr><td>4.21. DEBUGGING AND TROUBLESHOOTING</td><td>70</td></tr>\n<tr><td>4.22. KMM FIRMWARE SUPPORT</td><td>70</td></tr>\n<tr><td> 4.22.1. Configuring the lookup path on nodes</td><td>70</td></tr>\n<tr><td> 4.22.2. Building a kmod image</td><td>71</td></tr>\n<tr><td> 4.22.3. Tuning the Module resource</td><td>71</td></tr>\n<tr><td>4.23. DAY 0 THROUGH DAY 2 KMOD INSTALLATION</td><td>71</td></tr>\n<tr><td> 4.23.1. Layering background</td><td>72</td></tr>\n<tr><td> 4.23.2. Lifecycle management</td><td>72</td></tr>\n<tr><td> 4.23.2.1. Treat the kmod as an in-tree driver</td><td>72</td></tr>\n<tr><td> 4.23.2.2. Use ordered upgrade</td><td>73</td></tr>\n<tr><td>4.24. TROUBLESHOOTING KMM</td><td>73</td></tr>\n<tr><td> 4.24.1. Reading Operator logs</td><td>73</td></tr>\n<tr><td> 4.24.2. Observing events</td><td>73</td></tr>\n<tr><td> 4.24.2.1. Build & sign</td><td>73</td></tr>\n<tr><td> 4.24.2.2. Module load or unload</td><td>74</td></tr>\n<tr><td> 4.24.3. Using the must-gather tool</td><td>74</td></tr>\n<tr><td> 4.24.3.1. Gathering data for KMM</td><td>74</td></tr>\n<tr><td> 4.24.3.2. Gathering data for KMM-Hub</td><td>76</td></tr>\n<tr><td><b>CHAPTER 5. KERNEL MODULE MANAGEMENT OPERATOR RELEASE NOTES</b> .....</td><td><b>79</b></td></tr>\n<tr><td> 5.1. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.2</td><td>79</td></tr>\n<tr><td> 5.1.1. New features</td><td>79</td></tr>\n<tr><td> 5.2. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.3</td><td>79</td></tr>\n<tr><td> 5.2.1. New features</td><td>79</td></tr>\n<tr><td> 5.3. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.4</td><td>79</td></tr>\n<tr><td> 5.3.1. New features and enhancements</td><td>79</td></tr>\n<tr><td> 5.3.2. Notable technical changes</td><td>80</td></tr>\n<tr><td> 5.3.3. Bug fixes</td><td>80</td></tr>\n<tr><td> 5.3.4. Known issues</td><td>86</td></tr>\n<tr><td> 5.4. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.4.1</td><td>86</td></tr>\n<tr><td> 5.4.1. Known issues</td><td>86</td></tr>\n<tr><td> 5.5. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.5</td><td>86</td></tr>\n<tr><td> 5.5.1. New features and enhancements</td><td>86</td></tr>\n<tr><td> 5.5.2. Bug fixes</td><td>86</td></tr>\n<tr><td> 5.6. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.5.1</td><td>88</td></tr>\n<tr><td> 5.6.1. Known issues</td><td>88</td></tr>\n<tr><td> 5.7. RELEASE NOTES FOR KERNEL MODULE MANAGEMENT OPERATOR 2.6</td><td>88</td></tr>\n</table>\n<hr/>\n<table><tr><td>5.7.1. New features and enhancements</td><td>88</td></tr><tr><td>5.7.2. Bug fixes</td><td>89</td></tr><tr><td>5.7.3. Known issues</td><td>90</td></tr></table><h1>CHAPTER 1. ABOUT SPECIALIZED HARDWARE AND DRIVER ENABLEMENT</h1><p>The Driver Toolkit (DTK) is a container image in the OpenShift Container Platform payload which is meant to be used as a base image on which to build driver containers. The Driver Toolkit image contains the kernel packages commonly required as dependencies to build or install kernel modules as well as a few tools needed in driver containers. The version of these packages will match the kernel version running on the RHCOS nodes in the corresponding OpenShift Container Platform release.</p><p>Driver containers are container images used for building and deploying out-of-tree kernel modules and drivers on container operating systems such as Red Hat Enterprise Linux CoreOS (RHCOS). Kernel modules and drivers are software libraries running with a high level of privilege in the operating system kernel. They extend the kernel functionalities or provide the hardware-specific code required to control new devices. Examples include hardware devices like field-programmable gate arrays (FPGA) or graphics processing units (GPU), and software-defined storage solutions, which all require kernel modules on client machines. Driver containers are the first layer of the software stack used to enable these technologies on OpenShift Container Platform deployments.</p><h2>CHAPTER 2. DRIVER TOOLKIT</h2><p>Learn about the Driver Toolkit and how you can use it as a base image for driver containers for enabling special software and hardware devices on OpenShift Container Platform deployments.</p><h3>2.1. ABOUT THE DRIVER TOOLKIT</h3><h4>2.1.1. Background</h4><p>The Driver Toolkit is a container image in the OpenShift Container Platform payload used as a base image on which you can build driver containers. The Driver Toolkit image includes the kernel packages commonly required as dependencies to build or install kernel modules, as well as a few tools needed in driver containers. The version of these packages will match the kernel version running on the Red Hat Enterprise Linux CoreOS (RHCOS) nodes in the corresponding OpenShift Container Platform release.</p><p>Driver containers are container images used for building and deploying out-of-tree kernel modules and drivers on container operating systems like RHCOS. Kernel modules and drivers are software libraries running with a high level of privilege in the operating system kernel. They extend the kernel functionalities or provide the hardware-specific code required to control new devices. Examples include hardware devices like Field Programmable Gate Arrays (FPGA) or GPUs, and software-defined storage (SDS) solutions, such as Lustre parallel file systems, which require kernel modules on client machines. Driver containers are the first layer of the software stack used to enable these technologies on Kubernetes.</p><p>The list of kernel packages in the Driver Toolkit includes the following and their dependencies:</p><ul><li>• <b>kernel-core</b></li><li>• <b>kernel-devel</b></li><li>• <b>kernel-headers</b></li><li>• <b>kernel-modules</b></li><li>• <b>kernel-modules-extra</b></li></ul><p>In addition, the Driver Toolkit also includes the corresponding real-time kernel packages:</p><ul><li>• <b>kernel-rt-core</b></li><li>• <b>kernel-rt-devel</b></li><li>• <b>kernel-rt-modules</b></li><li>• <b>kernel-rt-modules-extra</b></li></ul><p>The Driver Toolkit also has several tools that are commonly needed to build and install kernel modules, including:</p><ul><li>• <b>elfutils-libelf-devel</b></li><li>• <b>kmod</b></li><li>• <b>binutils-kabi-dw</b></li></ul><ul><li>• <b>kernel-abi-whitelists</b></li><li>• dependencies for the above</li></ul><h3>2.1.2. Purpose</h3><p>Prior to the Driver Toolkit's existence, users would install kernel packages in a pod or build config on OpenShift Container Platform using <a href=\"#\">entitled builds</a> or by installing from the kernel RPMs in the hosts <b>machine-os-content</b>. The Driver Toolkit simplifies the process by removing the entitlement step, and avoids the privileged operation of accessing the machine-os-content in a pod. The Driver Toolkit can also be used by partners who have access to pre-released OpenShift Container Platform versions to prebuild driver-containers for their hardware devices for future OpenShift Container Platform releases.</p><p>The Driver Toolkit is also used by the Kernel Module Management (KMM), which is currently available as a community Operator in the software catalog. KMM supports out-of-tree and third-party kernel drivers and the support software for the underlying operating system. Users can create modules for KMM to build and deploy a driver container, as well as support software like a device plugin, or metrics. Modules can include a build config to build a driver container-based on the Driver Toolkit, or KMM can deploy a prebuilt driver container.</p><h2>2.2. PULLING THE DRIVER TOOLKIT CONTAINER IMAGE</h2><p>The <b>driver-toolkit</b> image is available from the <a href=\"#\">Container images section of the Red Hat Ecosystem Catalog</a> and in the OpenShift Container Platform release payload. The image corresponding to the most recent minor release of OpenShift Container Platform will be tagged with the version number in the catalog. The image URL for a specific release can be found using the <b>oc adm</b> CLI command.</p><h3>2.2.1. Pulling the Driver Toolkit container image from registry.redhat.io</h3><p>Instructions for pulling the <b>driver-toolkit</b> image from <b>registry.redhat.io</b> with <b>podman</b> or in OpenShift Container Platform can be found on the <a href=\"#\">Red Hat Ecosystem Catalog</a>. The driver-toolkit image for the latest minor release are tagged with the minor release version on <b>registry.redhat.io</b>, for example: <b>registry.redhat.io/openshift4/driver-toolkit-rhel8:v4.21</b>.</p><h3>2.2.2. Finding the Driver Toolkit image URL in the payload</h3><h4>Prerequisites</h4><ul><li>• You obtained the image <a href=\"#\">pull secret from Red Hat OpenShift Cluster Manager</a>.</li><li>• You installed the OpenShift CLI (<b>oc</b>).</li></ul><h4>Procedure</h4><ol><li>1. Use the <b>oc adm</b> command to extract the image URL of the <b>driver-toolkit</b> corresponding to a certain release:</li></ol><ul><li>• For an x86 image, the command is as follows:</li></ul><pre>$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.21.z-x86_64 --image-for=driver-toolkit</pre><ul><li>• For an ARM image, the command is as follows:</li></ul>\n<pre>$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.21.z-aarch64 --\nimage-for=driver-toolkit</pre>\n\n<h3>Example output</h3>\n\n<pre>quay.io/openshift-release-dev/ocp-v4.0-art-\ndev@sha256:b53883ca2bac5925857148c4a1abc300ced96c222498e3bc134fe7ce3a1dd404</pre>\n\n<ol>\n<li>2. Obtain this image using a valid pull secret, such as the pull secret required to install OpenShift Container Platform:</li>\n</ol>\n\n<pre>$ podman pull --authfile=path/to/pullsecret.json quay.io/openshift-release-dev/ocp-v4.0-art-\ndev@sha256:<SHA></pre>\n\n<h2>2.3. USING THE DRIVER TOOLKIT</h2>\n\n<p>As an example, the Driver Toolkit can be used as the base image for building a very simple kernel module called <b>simple-kmod</b>.</p>\n\n<h3>NOTE</h3>\n\n<p>The Driver Toolkit includes the necessary dependencies, <b>openssl</b>, <b>mokutil</b>, and <b>keyutils</b>, needed to sign a kernel module. However, in this example, the <b>simple-kmod</b> kernel module is not signed and therefore cannot be loaded on systems with <b>Secure Boot</b> enabled.</p>\n\n<h3>2.3.1. Build and run the simple-kmod driver container on a cluster</h3>\n\n<h4>Prerequisites</h4>\n\n<ul>\n<li>• You have a running OpenShift Container Platform cluster.</li>\n<li>• You set the Image Registry Operator state to <b>Managed</b> for your cluster.</li>\n<li>• You installed the OpenShift CLI (<b>oc</b>).</li>\n<li>• You are logged into the OpenShift CLI as a user with <b>cluster-admin</b> privileges.</li>\n</ul>\n\n<h4>Procedure</h4>\n\n<p>Create a namespace. For example:</p>\n\n<pre>$ oc new-project simple-kmod-demo</pre>\n\n<ol>\n<li>1. The YAML defines an <b>ImageStream</b> for storing the <b>simple-kmod</b> driver container image, and a <b>BuildConfig</b> for building the container. Save this YAML as <b>0000-buildconfig.yaml.template</b>.</li>\n</ol>\n\n<pre>apiVersion: image.openshift.io/v1\nkind: ImageStream\nmetadata:\n labels:\n app: simple-kmod-driver-container</pre>\n<pre>name: simple-kmod-driver-container\nnamespace: simple-kmod-demo\nspec: {}\n---\napiVersion: build.openshift.io/v1\nkind: BuildConfig\nmetadata:\n labels:\n app: simple-kmod-driver-build\n name: simple-kmod-driver-build\n namespace: simple-kmod-demo\nspec:\n nodeSelector:\n node-role.kubernetes.io/worker: \"\"\n runPolicy: \"Serial\"\n triggers:\n - type: \"ConfigChange\"\n - type: \"ImageChange\"\n source:\n dockerfile: |\n ARG DTK\n FROM ${DTK} as builder\n\n ARG KVER\n\n WORKDIR /build/\n\n RUN git clone https://github.com/openshift-psap/simple-kmod.git\n\n WORKDIR /build/simple-kmod\n\n RUN make all install KVER=${KVER}\n\n FROM registry.redhat.io/ubi8/ubi-minimal\n\n ARG KVER\n\n # Required for installing `modprobe`\n RUN microdnf install kmod\n\n COPY --from=builder /lib/modules/${KVER}/simple-kmod.ko /lib/modules/${KVER}/\n COPY --from=builder /lib/modules/${KVER}/simple-procfs-kmod.ko\n/lib/modules/${KVER}/\n RUN depmod ${KVER}\n strategy:\n dockerStrategy:\n buildArgs:\n - name: KMODVER\n value: DEMO\n # $ oc adm release info quay.io/openshift-release-dev/ocp-release:<cluster version>-\nx86_64 --image-for=driver-toolkit\n - name: DTK\n value: quay.io/openshift-release-dev/ocp-v4.0-art-\ndev@sha256:34864ccd2f4b6e385705a730864c04a40908e57ace44457a783d739e377cae\n - name: KVER\n value: 4.18.0-372.26.1.el8_6.x86_64</pre>\n<pre>\noutput:\nto:\n kind: ImageStreamTag\n name: simple-kmod-driver-container:demo\n</pre>\n\n<ol>\n<li>2. Substitute the correct driver toolkit image for the OpenShift Container Platform version you are running in place of “DRIVER_TOOLKIT_IMAGE” with the following commands.</li>\n</ol>\n\n<pre>$ OCP_VERSION=$(oc get clusterversion/version -ojsonpath={.status.desired.version})</pre>\n\n<pre>$ DRIVER_TOOLKIT_IMAGE=$(oc adm release info $OCP_VERSION --image-for=driver-toolkit)</pre>\n\n<pre>$ sed \"s#DRIVER_TOOLKIT_IMAGE#${DRIVER_TOOLKIT_IMAGE}#\" 0000-buildconfig.yaml.template > 0000-buildconfig.yaml</pre>\n\n<ol>\n<li>3. Create the image stream and build config with</li>\n</ol>\n\n<pre>$ oc create -f 0000-buildconfig.yaml</pre>\n\n<ol>\n<li>4. After the builder pod completes successfully, deploy the driver container image as a <b>DaemonSet</b>.</li>\n</ol>\n\n<ol type=\"a\">\n<li>a. The driver container must run with the privileged security context in order to load the kernel modules on the host. The following YAML file contains the RBAC rules and the <b>DaemonSet</b> for running the driver container. Save this YAML as <b>1000-drivercontainer.yaml</b>.</li>\n</ol>\n\n<pre>\napiVersion: v1\nkind: ServiceAccount\nmetadata:\n name: simple-kmod-driver-container\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: Role\nmetadata:\n name: simple-kmod-driver-container\nrules:\n- apiGroups:\n - security.openshift.io\nresources:\n - securitycontextconstraints\nverbs:\n - use\nresourceNames:\n - privileged\n---\napiVersion: rbac.authorization.k8s.io/v1\nkind: RoleBinding\nmetadata:\n name: simple-kmod-driver-container\nroleRef:\n apiGroup: rbac.authorization.k8s.io\n kind: Role\n name: simple-kmod-driver-container\n</pre>\n\n<pre>\nsubjects:\n- kind: ServiceAccount\n name: simple-kmod-driver-container\nuserNames:\n- system:serviceaccount:simple-kmod-demo:simple-kmod-driver-container\n---\napiVersion: apps/v1\nkind: DaemonSet\nmetadata:\n name: simple-kmod-driver-container\nspec:\n selector:\n matchLabels:\n app: simple-kmod-driver-container\n template:\n metadata:\n labels:\n app: simple-kmod-driver-container\n spec:\n serviceAccount: simple-kmod-driver-container\n serviceAccountName: simple-kmod-driver-container\n containers:\n - image: image-registry.openshift-image-registry.svc:5000/simple-kmod-\ndemo/simple-kmod-driver-container:demo\n name: simple-kmod-driver-container\n imagePullPolicy: Always\n command: [sleep, infinity]\n lifecycle:\n postStart:\n exec:\n command: [\"modprobe\", \"-v\", \"-a\", \"simple-kmod\", \"simple-procfs-kmod\"]\n preStop:\n exec:\n command: [\"modprobe\", \"-r\", \"-a\", \"simple-kmod\", \"simple-procfs-kmod\"]\n securityContext:\n privileged: true\n nodeSelector:\n node-role.kubernetes.io/worker: \"\"\n</pre>\n\n<p>b. Create the RBAC rules and daemon set:</p>\n\n<pre>$ oc create -f 1000-drivercontainer.yaml</pre>\n\n<p>5. After the pods are running on the worker nodes, verify that the <b>simple_kmod</b> kernel module is loaded successfully on the host machines with <b>lsmod</b>.</p>\n\n<p>a. Verify that the pods are running:</p>\n\n<pre>$ oc get pod -n simple-kmod-demo</pre>\n\n<h3>Example output</h3>\n\n<table>\n<thead>\n<tr>\n<th>NAME</th>\n<th>READY</th>\n<th>STATUS</th>\n<th>RESTARTS</th>\n<th>AGE</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>simple-kmod-driver-build-1-build</td>\n<td>0/1</td>\n<td>Completed</td>\n<td>0</td>\n<td>6m</td>\n</tr>\n<tr>\n<td>simple-kmod-driver-container-b22fd</td>\n<td>1/1</td>\n<td>Running</td>\n<td>0</td>\n<td>40s</td>\n</tr>\n</tbody>\n</table>\n<pre>simple-kmod-driver-container-jz9vn 1/1 Running 0 40s<br/>simple-kmod-driver-container-p45cc 1/1 Running 0 40s</pre><p>b. Execute the <b>lsmod</b> command in the driver container pod:</p><pre>$ oc exec -it pod/simple-kmod-driver-container-p45cc -- lsmod | grep simple</pre><h4>Example output</h4><pre>simple_proofs_kmod 16384 0<br/>simple_kmod 16384 0</pre><h2>2.4. ADDITIONAL RESOURCES</h2><ul><li>• For more information about configuring registry storage for your cluster, see <a href=\"#\">Image Registry Operator in OpenShift Container Platform</a>.</li></ul>\n<h2>CHAPTER 3. NODE FEATURE DISCOVERY OPERATOR</h2>\n\n<p>Learn about the Node Feature Discovery (NFD) Operator and how you can use it to expose node-level information by orchestrating Node Feature Discovery, a Kubernetes add-on for detecting hardware features and system configuration.</p>\n\n<p>The Node Feature Discovery Operator (NFD) manages the detection of hardware features and configuration in an OpenShift Container Platform cluster by labeling the nodes with hardware-specific information. NFD labels the host with node-specific attributes, such as PCI cards, kernel, operating system version, and so on.</p>\n\n<p>The NFD Operator can be found on the Operator Hub by searching for “Node Feature Discovery”.</p>\n\n<h3>3.1. INSTALLING THE NODE FEATURE DISCOVERY OPERATOR</h3>\n\n<p>The Node Feature Discovery (NFD) Operator orchestrates all resources needed to run the NFD daemon set. As a cluster administrator, you can install the NFD Operator by using the OpenShift Container Platform CLI or the web console.</p>\n\n<h4>3.1.1. Installing the NFD Operator using the CLI</h4>\n\n<p>As a cluster administrator, you can install the NFD Operator using the CLI.</p>\n\n<h5>Prerequisites</h5>\n\n<ul>\n<li>• An OpenShift Container Platform cluster</li>\n<li>• Install the OpenShift CLI (<b>oc</b>).</li>\n<li>• Log in as a user with <b>cluster-admin</b> privileges.</li>\n</ul>\n\n<h5>Procedure</h5>\n\n<ol>\n<li>1. Create a namespace for the NFD Operator.\n <ol type=\"a\">\n<li>a. Create the following <b>Namespace</b> custom resource (CR) that defines the <b>openshift-nfd</b> namespace, and then save the YAML in the <b>nfd-namespace.yaml</b> file. Set <b>cluster-monitoring</b> to <b>\"true\"</b>.</li>\n</ol>\n</li>\n</ol>\n\n<pre>apiVersion: v1\nkind: Namespace\nmetadata:\n name: openshift-nfd\n labels:\n name: openshift-nfd\n openshift.io/cluster-monitoring: \"true\"</pre>\n\n<ol type=\"a\">\n<li>b. Create the namespace by running the following command:</li>\n</ol>\n\n<pre>$ oc create -f nfd-namespace.yaml</pre>\n\n<ol>\n<li>2. Install the NFD Operator in the namespace you created in the previous step by creating the following objects:\n <ol type=\"a\">\n<li>a. Create the following <b>OperatorGroup</b> CR and save the YAML in the <b>nfd</b></li>\n</ol>\n</li>\n</ol>\n\n<p>a. Create the following <b>OperatorGroup</b> CR and save the YAML in the <b>nfd-operatorgroup.yaml</b> file:</p>\n\n<pre>apiVersion: operators.coreos.com/v1\nkind: OperatorGroup\nmetadata:\n generateName: openshift-nfd-\n name: openshift-nfd\n namespace: openshift-nfd\nspec:\n targetNamespaces:\n - openshift-nfd</pre>\n\n<p>b. Create the <b>OperatorGroup</b> CR by running the following command:</p>\n\n<pre>$ oc create -f nfd-operatorgroup.yaml</pre>\n\n<p>c. Create the following <b>Subscription</b> CR and save the YAML in the <b>nfd-sub.yaml</b> file:</p>\n\n<h3>Example Subscription</h3>\n\n<pre>apiVersion: operators.coreos.com/v1alpha1\nkind: Subscription\nmetadata:\n name: nfd\n namespace: openshift-nfd\nspec:\n channel: \"stable\"\n installPlanApproval: Automatic\n name: nfd\n source: redhat-operators\n sourceNamespace: openshift-marketplace</pre>\n\n<p>d. Create the subscription object by running the following command:</p>\n\n<pre>$ oc create -f nfd-sub.yaml</pre>\n\n<p>e. Change to the <b>openshift-nfd</b> project:</p>\n\n<pre>$ oc project openshift-nfd</pre>\n\n<h3>Verification</h3>\n\n<ul>\n<li>• To verify that the Operator deployment is successful, run:</li>\n</ul>\n\n<pre>$ oc get pods</pre>\n\n<h3>Example output</h3>\n\n<pre>NAME READY STATUS RESTARTS AGE\nnfd-controller-manager-7f86ccfb58-vgr4x 2/2 Running 0 10m</pre>\n\n<p>A successful deployment shows a <b>Running</b> status.</p>\n\n<h3>3.1.2. Installing the NFD Operator using the web console</h3>\n\n<p>As a cluster administrator, you can install the NFD Operator using the web console.</p>\n\n<h4>Procedure</h4>\n\n<ol>\n<li>1. In the OpenShift Container Platform web console, click <b>Ecosystem</b> → <b>Software Catalog</b>.</li>\n<li>2. Choose <b>Node Feature Discovery</b> from the list of available Operators, and then click <b>Install</b>.</li>\n<li>3. On the <b>Install Operator</b> page, select <b>A specific namespace on the cluster</b>, and then click <b>Install</b>. You do not need to create a namespace because it is created for you.</li>\n</ol>\n\n<h4>Verification</h4>\n\n<p>To verify that the NFD Operator installed successfully:</p>\n\n<ol>\n<li>1. Navigate to the <b>Ecosystem</b> → <b>Installed Operators</b> page.</li>\n<li>2. Ensure that <b>Node Feature Discovery</b> is listed in the <b>openshift-nfd</b> project with a <b>Status</b> of <b>InstallSucceeded</b>.</li>\n</ol>\n\n<h4>NOTE</h4>\n\n<p>During installation an Operator might display a <b>Failed</b> status. If the installation later succeeds with an <b>InstallSucceeded</b> message, you can ignore the <b>Failed</b> message.</p>\n\n<h4>Troubleshooting</h4>\n\n<p>If the Operator does not appear as installed, troubleshoot further:</p>\n\n<ol>\n<li>1. Navigate to the <b>Ecosystem</b> → <b>Installed Operators</b> page and inspect the <b>Operator Subscriptions</b> and <b>Install Plans</b> tabs for any failure or errors under <b>Status</b>.</li>\n<li>2. Navigate to the <b>Workloads</b> → <b>Pods</b> page and check the logs for pods in the <b>openshift-nfd</b> project.</li>\n</ol>\n\n<h2>3.2. USING THE NODE FEATURE DISCOVERY OPERATOR</h2>\n\n<p>The Node Feature Discovery (NFD) Operator orchestrates all resources needed to run the Node-Feature-Discovery daemon set by watching for a <b>NodeFeatureDiscovery</b> custom resource (CR). Based on the <b>NodeFeatureDiscovery</b> CR, the Operator creates the operand (NFD) components in the selected namespace. You can edit the CR to use another namespace, image, image pull policy, and <b>nfd-worker-conf</b> config map, among other options.</p>\n\n<p>As a cluster administrator, you can create a <b>NodeFeatureDiscovery</b> CR by using the OpenShift CLI (<b>oc</b>) or the web console.</p>\n<b>NOTE</b>\n<p>Starting with version 4.12, the <b>operand.image</b> field in the <b>NodeFeatureDiscovery</b> CR is mandatory. If the NFD Operator is deployed by using Operator Lifecycle Manager (OLM), OLM automatically sets the <b>operand.image</b> field. If you create the <b>NodeFeatureDiscovery</b> CR by using the OpenShift Container Platform CLI or the OpenShift Container Platform web console, you must set the <b>operand.image</b> field explicitly.</p>\n<b>3.2.1. Creating a NodeFeatureDiscovery CR by using the CLI</b>\n<p>As a cluster administrator, you can create a <b>NodeFeatureDiscovery</b> CR instance by using the OpenShift CLI (<b>oc</b>).</p>\n<b>NOTE</b>\n<p>The <b>spec.operand.image</b> setting requires a <b>-rhel9</b> image to be defined for use with OpenShift Container Platform releases 4.13 and later.</p>\n\n<p>The following example shows the use of <b>-rhel9</b> to acquire the correct image.</p>\n<b>Prerequisites</b>\n<ul>\n<li>• You have access to an OpenShift Container Platform cluster</li>\n<li>• You installed the OpenShift CLI (<b>oc</b>).</li>\n<li>• You logged in as a user with <b>cluster-admin</b> privileges.</li>\n<li>• You installed the NFD Operator.</li>\n</ul>\n<b>Procedure</b>\n<ol>\n<li>1. Create a <b>NodeFeatureDiscovery</b> CR:</li>\n</ol>\n<b>Example NodeFeatureDiscovery CR</b>\n<pre>apiVersion: nfd.openshift.io/v1\nkind: NodeFeatureDiscovery\nmetadata:\n name: nfd-instance\n namespace: openshift-nfd\nspec:\n instance: \"\" # instance is empty by default\n topologyUpdater: false # False by default\n operand:\n image: registry.redhat.io/openshift4/ose-node-feature-discovery-rhel9:v4.21 <b>1</b>\n imagePullPolicy: Always\n workerConfig:\n configData: |\n core:\n # labelWhiteList:\n # noPublish: false\n sleepInterval: 60s</pre>\n<pre># sources: [all]\n# klog:\n# addDirHeader: false\n# alsoLogtostderr: false\n# logBacktraceAt:\n# logtostderr: true\n# skipHeaders: false\n# stderrthreshold: 2\n# v: 0\n# vmodule:\n## NOTE: the following options are not dynamically run-time configurable\n## and require a nfd-worker restart to take effect after being changed\n# logDir:\n# logFile:\n# logFileMaxSize: 1800\n# skipLogHeaders: false\nsources:\n cpu:\n cpuid:\n# NOTE: whitelist has priority over blacklist\n attributeBlacklist:\n - \"BMI1\"\n - \"BMI2\"\n - \"CLMUL\"\n - \"CMOV\"\n - \"CX16\"\n - \"ERMS\"\n - \"F16C\"\n - \"HTT\"\n - \"LZCNT\"\n - \"MMX\"\n - \"MMXEXT\"\n - \"NX\"\n - \"POPCNT\"\n - \"RDRAND\"\n - \"RDSEED\"\n - \"RDTSCP\"\n - \"SGX\"\n - \"SSE\"\n - \"SSE2\"\n - \"SSE3\"\n - \"SSE4.1\"\n - \"SSE4.2\"\n - \"SSSE3\"\n attributeWhitelist:\nkernel:\n kconfigFile: \"/path/to/kconfig\"\n configOpts:\n - \"NO_HZ\"\n - \"X86\"\n - \"DMI\"\npci:\n deviceClassWhitelist:\n - \"0200\"\n - \"03\"\n - \"12\"</pre>\n<pre>\ndeviceLabelFields:\n - \"class\"\ncustomConfig:\n configData: |\n - name: \"more.kernel.features\"\n matchOn:\n - loadedKMod: [\"example_kmod3\"]\n</pre>\n\n<p><b>1</b> The <b>operand.image</b> field is mandatory.</p>\n\n<p>2. Create the <b>NodeFeatureDiscovery</b> CR by running the following command:</p>\n\n<pre>$ oc apply -f <filename></pre>\n\n<h2>Verification</h2>\n\n<p>1. Check that the <b>NodeFeatureDiscovery</b> CR was created by running the following command:</p>\n\n<pre>$ oc get pods</pre>\n\n<h3>Example output</h3>\n\n<table>\n<thead>\n<tr>\n<th>NAME</th>\n<th>READY</th>\n<th>STATUS</th>\n<th>RESTARTS</th>\n<th>AGE</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>nfd-controller-manager-7f86ccfb58-vgr4x</td>\n<td>2/2</td>\n<td>Running</td>\n<td>0</td>\n<td>11m</td>\n</tr>\n<tr>\n<td>nfd-master-hcn64</td>\n<td>1/1</td>\n<td>Running</td>\n<td>0</td>\n<td>60s</td>\n</tr>\n<tr>\n<td>nfd-master-lnnxx</td>\n<td>1/1</td>\n<td>Running</td>\n<td>0</td>\n<td>60s</td>\n</tr>\n<tr>\n<td>nfd-master-mp6hr</td>\n<td>1/1</td>\n<td>Running</td>\n<td>0</td>\n<td>60s</td>\n</tr>\n<tr>\n<td>nfd-worker-vgcz9</td>\n<td>1/1</td>\n<td>Running</td>\n<td>0</td>\n<td>60s</td>\n</tr>\n<tr>\n<td>nfd-worker-xqbw5</td>\n<td>1/1</td>\n<td>Running</td>\n<td>0</td>\n<td>60s</td>\n</tr>\n</tbody>\n</table>\n\n<p>A successful deployment shows a <b>Running</b> status.</p>\n\n<h3>3.2.2. Creating a NodeFeatureDiscovery CR by using the CLI in a disconnected environment</h3>\n\n<p>As a cluster administrator, you can create a <b>NodeFeatureDiscovery</b> CR instance by using the OpenShift CLI (<b>oc</b>).</p>\n\n<h4>Prerequisites</h4>\n\n<ul>\n<li>• You have access to an OpenShift Container Platform cluster</li>\n<li>• You installed the OpenShift CLI (<b>oc</b>).</li>\n<li>• You logged in as a user with <b>cluster-admin</b> privileges.</li>\n<li>• You installed the NFD Operator.</li>\n<li>• You have access to a mirror registry with the required images.</li>\n<li>• You installed the <b>skopeo</b> CLI tool.</li>\n</ul>\n\n<p><b>Procedure</b></p>\n\n<h2>Procedure</h2>\n\n<ol>\n<li>Determine the digest of the registry image:</li>\n</ol>\n\n<ol type=\"a\">\n<li>Run the following command:</li>\n</ol>\n\n<pre>$ skopeo inspect docker://registry.redhat.io/openshift4/ose-node-feature-discovery:\n<openshift_version></pre>\n\n<h3>Example command</h3>\n\n<pre>$ skopeo inspect docker://registry.redhat.io/openshift4/ose-node-feature-discovery:v4.12</pre>\n\n<ol type=\"a\">\n<li>Inspect the output to identify the image digest:</li>\n</ol>\n\n<h3>Example output</h3>\n\n<pre>{\n ...\n \"Digest\":\n \"sha256:1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef\",\n ...\n}</pre>\n\n<ol>\n<li>Use the <b>skopeo</b> CLI tool to copy the image from <b>registry.redhat.io</b> to your mirror registry, by running the following command:</li>\n</ol>\n\n<pre>skopeo copy docker://registry.redhat.io/openshift4/ose-node-feature-\ndiscovery@<image_digest> docker://<mirror_registry>/openshift4/ose-node-feature-\ndiscovery@<image_digest></pre>\n\n<h3>Example command</h3>\n\n<pre>skopeo copy docker://registry.redhat.io/openshift4/ose-node-feature-\ndiscovery@sha256:1234567890abcdef1234567890abcdef1234567890abcd\nef docker://<your-mirror-registry>/openshift4/ose-node-feature-\ndiscovery@sha256:1234567890abcdef1234567890abcdef1234567890abcd\nef</pre>\n\n<ol>\n<li>Create a <b>NodeFeatureDiscovery</b> CR:</li>\n</ol>\n\n<h3>Example NodeFeatureDiscovery CR</h3>\n\n<pre>apiVersion: nfd.openshift.io/v1\nkind: NodeFeatureDiscovery\nmetadata:\n name: nfd-instance\nspec:\n operand:\n image: <mirror_registry>/openshift4/ose-node-feature-discovery@<image_digest> 1\n imagePullPolicy: Always\n workerConfig:\n configData: |\n core:</pre>\n<pre># labelWhiteList:\n# noPublish: false\n# sleepInterval: 60s\n# sources: [all]\n# klog:\n# addDirHeader: false\n# alsologtostderr: false\n# logBacktraceAt:\n# logtostderr: true\n# skipHeaders: false\n# stderrthreshold: 2\n# v: 0\n# vmodule:\n## NOTE: the following options are not dynamically run-time configurable\n## and require a nfd-worker restart to take effect after being changed\n# logDir:\n# logFile:\n# logFileMaxSize: 1800\n# skipLogHeaders: false\nsources:\n cpu:\n cpuid:\n# NOTE: whitelist has priority over blacklist\n attributeBlacklist:\n - \"BMI1\"\n - \"BMI2\"\n - \"CLMUL\"\n - \"CMOV\"\n - \"CX16\"\n - \"ERMS\"\n - \"F16C\"\n - \"HTT\"\n - \"LZCNT\"\n - \"MMX\"\n - \"MMXEXT\"\n - \"NX\"\n - \"POPCNT\"\n - \"RDRAND\"\n - \"RDSEED\"\n - \"RDTSCP\"\n - \"SGX\"\n - \"SSE\"\n - \"SSE2\"\n - \"SSE3\"\n - \"SSE4.1\"\n - \"SSE4.2\"\n - \"SSSE3\"\n attributeWhitelist:\nkernel:\n kconfigFile: \"/path/to/kconfig\"\n configOpts:\n - \"NO_HZ\"\n - \"X86\"\n - \"DMI\"\npci:\n deviceClassWhitelist:</pre><pre>- \"0200\"<br/>- \"03\"<br/>- \"12\"<br/>deviceLabelFields:<br/> - \"class\"<br/>customConfig:<br/> configData: |<br/> - name: \"more.kernel.features\"<br/> matchOn:<br/> - loadedKMod: [\"example_kmod3\"]</pre><p><b>1</b> The <b>operand.image</b> field is mandatory.</p><p>4. Create the <b>NodeFeatureDiscovery</b> CR by running the following command:</p><pre>$ oc apply -f <filename></pre><h2>Verification</h2><p>1. Check the status of the <b>NodeFeatureDiscovery</b> CR by running the following command:</p><pre>$ oc get nodefeaturediscovery nfd-instance -o yaml</pre><p>2. Check that the pods are running without <b>ImagePullBackOff</b> errors by running the following command:</p><pre>$ oc get pods -n <nfd_namespace></pre><h3>3.2.3. Creating a NodeFeatureDiscovery CR by using the web console</h3><p>As a cluster administrator, you can create a <b>NodeFeatureDiscovery</b> CR by using the OpenShift Container Platform web console.</p><h4>Prerequisites</h4><ul><li>• You have access to an OpenShift Container Platform cluster</li><li>• You logged in as a user with <b>cluster-admin</b> privileges.</li><li>• You installed the NFD Operator.</li></ul><h4>Procedure</h4><ol><li>1. Navigate to the <b>Ecosystem → Installed Operators</b> page.</li><li>2. In the <b>Node Feature Discovery</b> section, under <b>Provided APIs</b>, click <b>Create instance</b>.</li><li>3. Edit the values of the <b>NodeFeatureDiscovery</b> CR.</li><li>4. Click <b>Create</b>.</li></ol>\n<h2>NOTE</h2>\n\n<p>Starting with version 4.12, the <b>operand.image</b> field in the <b>NodeFeatureDiscovery</b> CR is mandatory. If the NFD Operator is deployed by using Operator Lifecycle Manager (OLM), OLM automatically sets the <b>operand.image</b> field. If you create the <b>NodeFeatureDiscovery</b> CR by using the OpenShift Container Platform CLI or the OpenShift Container Platform web console, you must set the <b>operand.image</b> field explicitly.</p>\n\n<h2>3.3. CONFIGURING THE NODE FEATURE DISCOVERY OPERATOR</h2>\n\n<h3>3.3.1. core</h3>\n\n<p>The <b>core</b> section contains common configuration settings that are not specific to any particular feature source.</p>\n\n<h4>3.3.1.1. core.sleepInterval</h4>\n\n<p><b>core.sleepInterval</b> specifies the interval between consecutive passes of feature detection or re-detection, and thus also the interval between node re-labeling. A non-positive value implies infinite sleep interval; no re-detection or re-labeling is done.</p>\n\n<p>This value is overridden by the deprecated <b>--sleep-interval</b> command-line flag, if specified.</p>\n\n<h4>Example usage</h4>\n\n<pre>core:\n sleepInterval: 60s <b>1</b></pre>\n\n<p>The default value is <b>60s</b>.</p>\n\n<h4>3.3.1.2. core.sources</h4>\n\n<p><b>core.sources</b> specifies the list of enabled feature sources. A special value <b>all</b> enables all feature sources.</p>\n\n<p>This value is overridden by the deprecated <b>--sources</b> command-line flag, if specified.</p>\n\n<p>Default: <b>[all]</b></p>\n\n<h4>Example usage</h4>\n\n<pre>core:\n sources:\n - system\n - custom</pre>\n\n<h4>3.3.1.3. core.labelWhiteList</h4>\n\n<p><b>core.labelWhiteList</b> specifies a regular expression for filtering feature labels based on the label name. Non-matching labels are not published.</p>\n<p>The regular expression is only matched against the basename part of the label, the part of the name after '/'. The label prefix, or namespace, is omitted.</p><p>This value is overridden by the deprecated <b>--label-whitelist</b> command-line flag, if specified.</p><p>Default: <b>null</b></p><h3>Example usage</h3><pre>core:<br/> labelWhiteList: '^cpu-cpuid'</pre><h4>3.3.1.4. core.noPublish</h4><p>Setting <b>core.noPublish</b> to <b>true</b> disables all communication with the <b>nfd-master</b>. It is effectively a dry run flag; <b>nfd-worker</b> runs feature detection normally, but no labeling requests are sent to <b>nfd-master</b>.</p><p>This value is overridden by the <b>--no-publish</b> command-line flag, if specified.</p><p>Example:</p><h3>Example usage</h3><pre>core:<br/> noPublish: true </pre><p>The default value is <b>false</b>.</p><h4>3.3.2. core.klog</h4><p>The following options specify the logger configuration, most of which can be dynamically adjusted at run-time.</p><p>The logger options can also be specified using command-line flags, which take precedence over any corresponding config file options.</p><h5>3.3.2.1. core.klog.addDirHeader</h5><p>If set to <b>true</b>, <b>core.klog.addDirHeader</b> adds the file directory to the header of the log messages.</p><p>Default: <b>false</b></p><p>Run-time configurable: yes</p><h5>3.3.2.2. core.klog.alsologtostderr</h5><p>Log to standard error as well as files.</p><p>Default: <b>false</b></p><p>Run-time configurable: yes</p><h5>3.3.2.3. core.klog.logBacktraceAt</h5><p>When logging hits line file:N, emit a stack trace.</p><p>Default: <b>empty</b></p><p>Run-time configurable: yes</p><h4>3.3.2.4. core.klog.logDir</h4><p>If non-empty, write log files in this directory.</p><p>Default: <b>empty</b></p><p>Run-time configurable: no</p><h4>3.3.2.5. core.klog.logFile</h4><p>If not empty, use this log file.</p><p>Default: <b>empty</b></p><p>Run-time configurable: no</p><h4>3.3.2.6. core.klog.logFileSize</h4><p><b>core.klog.logFileSize</b> defines the maximum size a log file can grow to. Unit is megabytes. If the value is <b>0</b>, the maximum file size is unlimited.</p><p>Default: <b>1800</b></p><p>Run-time configurable: no</p><h4>3.3.2.7. core.klog.logtostderr</h4><p>Log to standard error instead of files</p><p>Default: <b>true</b></p><p>Run-time configurable: yes</p><h4>3.3.2.8. core.klog.skipHeaders</h4><p>If <b>core.klog.skipHeaders</b> is set to <b>true</b>, avoid header prefixes in the log messages.</p><p>Default: <b>false</b></p><p>Run-time configurable: yes</p><h4>3.3.2.9. core.klog.skipLogHeaders</h4><p>If <b>core.klog.skipLogHeaders</b> is set to <b>true</b>, avoid headers when opening log files.</p><p>Default: <b>false</b></p><p>Run-time configurable: no</p><h3>3.3.2.10. core.klog.stderrthreshold</h3><p>Logs at or above this threshold go to stderr.</p><p>Default: <b>2</b></p><p>Run-time configurable: yes</p><h3>3.3.2.11. core.klog.v</h3><p><b>core.klog.v</b> is the number for the log level verbosity.</p><p>Default: <b>0</b></p><p>Run-time configurable: yes</p><h3>3.3.2.12. core.klog.vmodule</h3><p><b>core.klog.vmodule</b> is a comma-separated list of <b>pattern=N</b> settings for file-filtered logging.</p><p>Default: <b>empty</b></p><p>Run-time configurable: yes</p><h2>3.3.3. sources</h2><p>The <b>sources</b> section contains feature source specific configuration parameters.</p><h3>3.3.3.1. sources.cpu.cpuid.attributeBlacklist</h3><p>Prevent publishing <b>cpuid</b> features listed in this option.</p><p>This value is overridden by <b>sources.cpu.cpuid.attributeWhitelist</b>, if specified.</p><p>Default: <b>[BMI1, BMI2, CLMUL, CMOV, CX16, ERMS, F16C, HTT, LZCNT, MMX, MMXEXT, NX, POPCNT, RDRAND, RDSEED, RDTSCP, SGX, SGXLC, SSE, SSE2, SSE3, SSE4.1, SSE4.2, SSSE3]</b></p><h4>Example usage</h4><pre>sources:\n cpu:\n cpuid:\n attributeBlacklist: [MMX, MMXEXT]</pre><h3>3.3.3.2. sources.cpu.cpuid.attributeWhitelist</h3><p>Only publish the <b>cpuid</b> features listed in this option.</p><p><b>sources.cpu.cpuid.attributeWhitelist</b> takes precedence over <b>sources.cpu.cpuid.attributeBlacklist</b>.</p><p>Default: <b>empty</b></p><h4>Example usage</h4>"},"page_stats":{"kind":"list like","value":[{"page_number":1,"error":false,"token_count":255,"num_chunks":5},{"page_number":2,"error":false,"token_count":48,"num_chunks":1},{"page_number":3,"error":false,"token_count":95,"num_chunks":2},{"page_number":4,"error":false,"token_count":586,"num_chunks":11},{"page_number":5,"error":false,"token_count":1941,"num_chunks":4},{"page_number":6,"error":false,"token_count":1927,"num_chunks":3},{"page_number":7,"error":false,"token_count":1746,"num_chunks":3},{"page_number":8,"error":false,"token_count":194,"num_chunks":3},{"page_number":9,"error":false,"token_count":110,"num_chunks":2},{"page_number":10,"error":false,"token_count":406,"num_chunks":5},{"page_number":11,"error":false,"token_count":950,"num_chunks":14},{"page_number":12,"error":false,"token_count":1279,"num_chunks":18},{"page_number":13,"error":false,"token_count":1294,"num_chunks":20},{"page_number":14,"error":false,"token_count":597,"num_chunks":3},{"page_number":15,"error":false,"token_count":882,"num_chunks":12},{"page_number":16,"error":false,"token_count":924,"num_chunks":10},{"page_number":17,"error":false,"token_count":454,"num_chunks":9},{"page_number":18,"error":false,"token_count":1205,"num_chunks":18},{"page_number":19,"error":false,"token_count":1058,"num_chunks":19},{"page_number":20,"error":false,"token_count":1264,"num_chunks":18},{"page_number":21,"error":false,"token_count":1089,"num_chunks":17},{"page_number":22,"error":false,"token_count":530,"num_chunks":3},{"page_number":23,"error":false,"token_count":1323,"num_chunks":17},{"page_number":24,"error":false,"token_count":1205,"num_chunks":18},{"page_number":25,"error":false,"token_count":512,"num_chunks":3},{"page_number":26,"error":false,"token_count":968,"num_chunks":17},{"page_number":27,"error":false,"token_count":1219,"num_chunks":22},{"page_number":28,"error":false,"token_count":1249,"num_chunks":26},{"page_number":29,"error":false,"token_count":1263,"num_chunks":29},{"page_number":30,"error":false,"token_count":1303,"num_chunks":27}],"string":"[\n {\n \"page_number\": 1,\n \"error\": false,\n \"token_count\": 255,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 2,\n \"error\": false,\n \"token_count\": 48,\n \"num_chunks\": 1\n },\n {\n \"page_number\": 3,\n \"error\": false,\n \"token_count\": 95,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 4,\n \"error\": false,\n \"token_count\": 586,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 5,\n \"error\": false,\n \"token_count\": 1941,\n \"num_chunks\": 4\n },\n {\n \"page_number\": 6,\n \"error\": false,\n \"token_count\": 1927,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 7,\n \"error\": false,\n \"token_count\": 1746,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 8,\n \"error\": false,\n \"token_count\": 194,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 9,\n \"error\": false,\n \"token_count\": 110,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 10,\n \"error\": false,\n \"token_count\": 406,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 11,\n \"error\": false,\n \"token_count\": 950,\n \"num_chunks\": 14\n },\n {\n \"page_number\": 12,\n \"error\": false,\n \"token_count\": 1279,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 13,\n \"error\": false,\n \"token_count\": 1294,\n \"num_chunks\": 20\n },\n {\n \"page_number\": 14,\n \"error\": false,\n \"token_count\": 597,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 15,\n \"error\": false,\n \"token_count\": 882,\n \"num_chunks\": 12\n },\n {\n \"page_number\": 16,\n \"error\": false,\n \"token_count\": 924,\n \"num_chunks\": 10\n },\n {\n \"page_number\": 17,\n \"error\": false,\n \"token_count\": 454,\n \"num_chunks\": 9\n },\n {\n \"page_number\": 18,\n \"error\": false,\n \"token_count\": 1205,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 19,\n \"error\": false,\n \"token_count\": 1058,\n \"num_chunks\": 19\n },\n {\n \"page_number\": 20,\n \"error\": false,\n \"token_count\": 1264,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 21,\n \"error\": false,\n \"token_count\": 1089,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 22,\n \"error\": false,\n \"token_count\": 530,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 23,\n \"error\": false,\n \"token_count\": 1323,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 24,\n \"error\": false,\n \"token_count\": 1205,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 25,\n \"error\": false,\n \"token_count\": 512,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 26,\n \"error\": false,\n \"token_count\": 968,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 27,\n \"error\": false,\n \"token_count\": 1219,\n \"num_chunks\": 22\n },\n {\n \"page_number\": 28,\n \"error\": false,\n \"token_count\": 1249,\n \"num_chunks\": 26\n },\n {\n \"page_number\": 29,\n \"error\": false,\n \"token_count\": 1263,\n \"num_chunks\": 29\n },\n {\n \"page_number\": 30,\n \"error\": false,\n \"token_count\": 1303,\n \"num_chunks\": 27\n }\n]","isConversational":false}}},{"rowIdx":99,"cells":{"source_id":{"kind":"string","value":"OpenShift_Container_Platform-4.21-Storage-en-US"},"pdf_url":{"kind":"string","value":"https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/storage/OpenShift_Container_Platform-4.21-Storage-en-US.pdf"},"status":{"kind":"string","value":"success"},"processed_at":{"kind":"string","value":"2026-04-15T18:41:10.161659+00:00"},"elapsed_seconds":{"kind":"number","value":69.13,"string":"69.13"},"num_pages":{"kind":"number","value":324,"string":"324"},"num_pages_processed":{"kind":"number","value":30,"string":"30"},"max_pages_per_paper":{"kind":"number","value":30,"string":"30"},"pdf_exceeds_page_limit":{"kind":"bool","value":true,"string":"true"},"failed_pages":{"kind":"list like","value":[],"string":"[]","isConversational":false},"prompt_type":{"kind":"string","value":"ocr_layout"},"model_id":{"kind":"string","value":"datalab-to/chandra-ocr-2"},"script_version":{"kind":"timestamp","value":"2026-04-15T00:00:00","string":"2026-04-15T00:00:00"},"markdown":{"kind":"string","value":"# OpenShift Container Platform 4.21\n\n## Storage\n\nConfiguring and managing storage in OpenShift Container Platform# OpenShift Container Platform 4.21 Storage\n\n---\n\nConfiguring and managing storage in OpenShift Container Platform## Legal Notice\n\nCopyright © Red Hat.\n\nExcept as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.\n\nRed Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.\n\nRed Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.\n\nLinux ® is the registered trademark of Linus Torvalds in the United States and other countries.\n\nXFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.\n\nThe OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.\n\nAll other trademarks are the property of their respective owners.\n\n## Abstract\n\nThis document provides instructions for configuring persistent volumes from various storage back ends and managing dynamic allocation from Pods.# Table of Contents\n\n<table>\n<tr>\n<td><b>CHAPTER 1. OPENSHIFT CONTAINER PLATFORM STORAGE OVERVIEW</b> .....</td>\n<td><b>11</b></td>\n</tr>\n<tr>\n<td> 1.1. GLOSSARY OF COMMON TERMS FOR OPENSHIFT CONTAINER PLATFORM STORAGE</td>\n<td>11</td>\n</tr>\n<tr>\n<td> 1.2. STORAGE TYPES</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.2.1. Ephemeral storage</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.2.2. Persistent storage</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.3. CONTAINER STORAGE INTERFACE (CSI)</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.4. DYNAMIC PROVISIONING</td>\n<td>14</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. UNDERSTANDING EPHEMERAL STORAGE</b> .....</td>\n<td><b>15</b></td>\n</tr>\n<tr>\n<td> 2.1. OVERVIEW OF EPHEMERAL STORAGE</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2. TYPES OF EPHEMERAL STORAGE</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2.1. Root</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2.2. Runtime</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.3. EPHEMERAL STORAGE MANAGEMENT</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.3.1. Ephemeral storage limits and requests units</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.3.2. Ephemeral storage requests and limits example</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.3.3. Ephemeral storage configuration effects pod scheduling and eviction</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.4. ADDITIONAL RESOURCES</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.5. MONITORING EPHEMERAL STORAGE</td>\n<td>17</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. UNDERSTANDING PERSISTENT STORAGE</b> .....</td>\n<td><b>19</b></td>\n</tr>\n<tr>\n<td> 3.1. PERSISTENT STORAGE OVERVIEW</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2. LIFECYCLE OF A VOLUME AND CLAIM</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.1. Provision storage</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.2. Bind claims</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.3. Use pods and claimed PVs</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 3.2.4. Storage Object in Use Protection</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 3.2.5. Release a persistent volume</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 3.2.6. Reclaim policy for persistent volumes</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.2.7. Reclaiming a persistent volume manually</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.2.8. Changing the reclaim policy of a persistent volume</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.3. PERSISTENT VOLUMES</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 3.3.1. Types of PVs</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.3.2. Capacity</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.3. Access modes</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.4. Phase</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.3.4.1. Last phase transition time</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.3.4.2. Mount options</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.4. PERSISTENT VOLUME CLAIMS</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.4.1. Volume Attributes Classes</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 3.4.1.1. Limitations</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 3.4.1.2. Defining Volume Attributes Classes</td>\n<td>30</td>\n</tr>\n<tr>\n<td> 3.4.1.3. Applying a Volume Attributes Class to a PVC</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.4.1.4. Deleting Volume Attributes Classes</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.5. BLOCK VOLUME SUPPORT</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.5.1. Block volume examples</td>\n<td>34</td>\n</tr>\n<tr>\n<td> 3.6. REDUCE POD TIMEOUTS BY USING FSGROUP</td>\n<td>36</td>\n</tr>\n<tr>\n<td> 3.6.1. Changing fsGroup at the namespace level</td>\n<td>37</td>\n</tr>\n<tr>\n<td> 3.6.2. Changing fsGroup at the pod level</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 3.7. REDUCING POD TIMEOUTS USING SELINUXCHANGEPOLICY</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 3.7.1. Testing the RWO and RWX and SELinux mount option feature</td>\n<td>40</td>\n</tr>\n</table><table>\n<tr>\n<td>3.7.2. Opting out of the SELinux mount option default</td>\n<td>40</td>\n</tr>\n<tr>\n<td> 3.7.2.1. Changing seLinuxChangePolicy at the namespace level</td>\n<td>40</td>\n</tr>\n<tr>\n<td> 3.7.2.2. Changing seLinuxChangePolicy at the pod level</td>\n<td>41</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. CONFIGURING PERSISTENT STORAGE</b> .....</td>\n<td><b>43</b></td>\n</tr>\n<tr>\n<td>4.1. PERSISTENT STORAGE USING AWS ELASTIC BLOCK STORE</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.1.1. Creating the EBS storage class</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.1.2. Creating the persistent volume claim</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.1.3. Volume format</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 4.1.4. Maximum number of EBS volumes on a node</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 4.1.5. Encrypting container persistent volumes on AWS with a KMS key</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 4.1.6. Additional resources</td>\n<td>46</td>\n</tr>\n<tr>\n<td>4.2. PERSISTENT STORAGE USING AZURE</td>\n<td>46</td>\n</tr>\n<tr>\n<td> 4.2.1. Creating the Azure storage class</td>\n<td>46</td>\n</tr>\n<tr>\n<td> 4.2.2. Creating the persistent volume claim</td>\n<td>47</td>\n</tr>\n<tr>\n<td> 4.2.3. Volume format</td>\n<td>48</td>\n</tr>\n<tr>\n<td> 4.2.4. Machine sets that deploy machines with ultra disks using PVCs</td>\n<td>48</td>\n</tr>\n<tr>\n<td> 4.2.4.1. Creating machines with ultra disks by using machine sets</td>\n<td>48</td>\n</tr>\n<tr>\n<td> 4.2.4.2. Troubleshooting resources for machine sets that enable ultra disks</td>\n<td>51</td>\n</tr>\n<tr>\n<td> 4.2.4.2.1. Unable to mount a persistent volume claim backed by an ultra disk</td>\n<td>51</td>\n</tr>\n<tr>\n<td>4.3. PERSISTENT STORAGE USING AZURE FILE</td>\n<td>51</td>\n</tr>\n<tr>\n<td> 4.3.1. Create the Azure File share persistent volume claim</td>\n<td>52</td>\n</tr>\n<tr>\n<td> 4.3.2. Mount the Azure File share in a pod</td>\n<td>54</td>\n</tr>\n<tr>\n<td>4.4. PERSISTENT STORAGE USING CINDER</td>\n<td>54</td>\n</tr>\n<tr>\n<td> 4.4.1. Manual provisioning with Cinder</td>\n<td>55</td>\n</tr>\n<tr>\n<td> 4.4.1.1. Creating the persistent volume</td>\n<td>55</td>\n</tr>\n<tr>\n<td> 4.4.1.2. Persistent volume formatting</td>\n<td>56</td>\n</tr>\n<tr>\n<td> 4.4.1.3. Cinder volume security</td>\n<td>56</td>\n</tr>\n<tr>\n<td>4.5. PERSISTENT STORAGE USING FIBRE CHANNEL</td>\n<td>57</td>\n</tr>\n<tr>\n<td> 4.5.1. Provisioning</td>\n<td>58</td>\n</tr>\n<tr>\n<td> 4.5.1.1. Enforcing disk quotas</td>\n<td>58</td>\n</tr>\n<tr>\n<td> 4.5.1.2. Fibre Channel volume security</td>\n<td>59</td>\n</tr>\n<tr>\n<td>4.6. PERSISTENT STORAGE USING FLEXVOLUME</td>\n<td>59</td>\n</tr>\n<tr>\n<td> 4.6.1. About FlexVolume drivers</td>\n<td>59</td>\n</tr>\n<tr>\n<td> 4.6.2. FlexVolume driver example</td>\n<td>60</td>\n</tr>\n<tr>\n<td> 4.6.3. Installing FlexVolume drivers</td>\n<td>60</td>\n</tr>\n<tr>\n<td> 4.6.4. Consuming storage using FlexVolume drivers</td>\n<td>62</td>\n</tr>\n<tr>\n<td>4.7. PERSISTENT STORAGE USING GCE PERSISTENT DISK</td>\n<td>63</td>\n</tr>\n<tr>\n<td> 4.7.1. Creating the GCE storage class</td>\n<td>64</td>\n</tr>\n<tr>\n<td> 4.7.2. Creating the persistent volume claim</td>\n<td>64</td>\n</tr>\n<tr>\n<td> 4.7.3. Volume format</td>\n<td>64</td>\n</tr>\n<tr>\n<td>4.8. PERSISTENT STORAGE USING ISCSI</td>\n<td>64</td>\n</tr>\n<tr>\n<td> 4.8.1. Provisioning</td>\n<td>65</td>\n</tr>\n<tr>\n<td> 4.8.2. Enforce disk quotas</td>\n<td>65</td>\n</tr>\n<tr>\n<td> 4.8.3. iSCSI volume security</td>\n<td>65</td>\n</tr>\n<tr>\n<td> 4.8.3.1. Challenge Handshake Authentication Protocol (CHAP) configuration</td>\n<td>66</td>\n</tr>\n<tr>\n<td> 4.8.4. iSCSI multipathing</td>\n<td>66</td>\n</tr>\n<tr>\n<td> 4.8.5. iSCSI custom initiator IQN</td>\n<td>67</td>\n</tr>\n<tr>\n<td>4.9. PERSISTENT STORAGE USING NFS</td>\n<td>67</td>\n</tr>\n<tr>\n<td> 4.9.1. Provisioning</td>\n<td>68</td>\n</tr>\n<tr>\n<td> 4.9.2. Enforce disk quotas</td>\n<td>69</td>\n</tr>\n<tr>\n<td> 4.9.3. NFS volume security</td>\n<td>69</td>\n</tr>\n<tr>\n<td> 4.9.3.1. Group IDs</td>\n<td>70</td>\n</tr>\n</table><table>\n<tr>\n<td>4.9.3.2. User IDs</td>\n<td>71</td>\n</tr>\n<tr>\n<td>4.9.3.3. SELinux</td>\n<td>72</td>\n</tr>\n<tr>\n<td>4.9.3.4. Export settings</td>\n<td>72</td>\n</tr>\n<tr>\n<td>4.9.4. Reclaiming resources</td>\n<td>73</td>\n</tr>\n<tr>\n<td>4.9.5. Additional configuration and troubleshooting</td>\n<td>74</td>\n</tr>\n<tr>\n<td>4.10. RED HAT OPENSHIFT DATA FOUNDATION</td>\n<td>74</td>\n</tr>\n<tr>\n<td>4.11. PERSISTENT STORAGE USING VMWARE VSPHERE VOLUMES</td>\n<td>74</td>\n</tr>\n<tr>\n<td>4.11.1. Dynamically provisioning VMware vSphere volumes</td>\n<td>75</td>\n</tr>\n<tr>\n<td>4.11.2. Prerequisites</td>\n<td>75</td>\n</tr>\n<tr>\n<td>4.11.2.1. Dynamically provisioning VMware vSphere volumes using the UI</td>\n<td>75</td>\n</tr>\n<tr>\n<td>4.11.2.2. Dynamically provisioning VMware vSphere volumes using the CLI</td>\n<td>76</td>\n</tr>\n<tr>\n<td>4.11.3. Statically provisioning VMware vSphere volumes</td>\n<td>77</td>\n</tr>\n<tr>\n<td>4.11.3.1. Formatting VMware vSphere volumes</td>\n<td>78</td>\n</tr>\n<tr>\n<td><b>CHAPTER 5. PERSISTENT STORAGE USING LOCAL STORAGE</b></td>\n<td><b>79</b></td>\n</tr>\n<tr>\n<td>5.1. LOCAL STORAGE OVERVIEW</td>\n<td>79</td>\n</tr>\n<tr>\n<td>5.1.1. Overview of HostPath Provisioner functionality</td>\n<td>79</td>\n</tr>\n<tr>\n<td>5.1.2. Overview of Local Storage Operator functionality</td>\n<td>79</td>\n</tr>\n<tr>\n<td>5.1.3. Overview of LVM Storage functionality</td>\n<td>80</td>\n</tr>\n<tr>\n<td>5.1.4. Comparison of LVM Storage, LSO, and HPP</td>\n<td>80</td>\n</tr>\n<tr>\n<td>5.1.4.1. Comparison of the support for storage types and filesystems</td>\n<td>80</td>\n</tr>\n<tr>\n<td>5.1.4.2. Comparison of the support for core functionalities</td>\n<td>80</td>\n</tr>\n<tr>\n<td>5.1.4.3. Comparison of performance and isolation capabilities</td>\n<td>82</td>\n</tr>\n<tr>\n<td>5.1.4.4. Comparison of the support for additional functionalities</td>\n<td>82</td>\n</tr>\n<tr>\n<td>5.2. PERSISTENT STORAGE USING LOCAL VOLUMES</td>\n<td>83</td>\n</tr>\n<tr>\n<td>5.2.1. Installing the Local Storage Operator</td>\n<td>83</td>\n</tr>\n<tr>\n<td>5.2.2. Provisioning local volumes by using the Local Storage Operator</td>\n<td>86</td>\n</tr>\n<tr>\n<td>5.2.3. Provisioning local volumes without the Local Storage Operator</td>\n<td>90</td>\n</tr>\n<tr>\n<td>5.2.4. Creating the local volume persistent volume claim</td>\n<td>92</td>\n</tr>\n<tr>\n<td>5.2.5. Attach the local claim</td>\n<td>92</td>\n</tr>\n<tr>\n<td>5.2.6. Automating discovery and provisioning for local storage devices</td>\n<td>93</td>\n</tr>\n<tr>\n<td>5.2.7. Using tolerations with Local Storage Operator pods</td>\n<td>97</td>\n</tr>\n<tr>\n<td>5.2.8. Local Storage Operator Metrics</td>\n<td>98</td>\n</tr>\n<tr>\n<td>5.2.9. Deleting the Local Storage Operator resources</td>\n<td>98</td>\n</tr>\n<tr>\n<td>5.2.9.1. Removing a local volume or local volume set</td>\n<td>98</td>\n</tr>\n<tr>\n<td>5.2.9.2. Uninstalling the Local Storage Operator</td>\n<td>100</td>\n</tr>\n<tr>\n<td>5.3. PERSISTENT STORAGE USING HOSTPATH</td>\n<td>101</td>\n</tr>\n<tr>\n<td>5.3.1. Overview</td>\n<td>101</td>\n</tr>\n<tr>\n<td>5.3.2. Statically provisioning hostPath volumes</td>\n<td>102</td>\n</tr>\n<tr>\n<td>5.3.3. Mounting the hostPath share in a privileged pod</td>\n<td>103</td>\n</tr>\n<tr>\n<td>5.4. PERSISTENT STORAGE USING LOGICAL VOLUME MANAGER STORAGE</td>\n<td>104</td>\n</tr>\n<tr>\n<td>5.4.1. Logical Volume Manager Storage installation</td>\n<td>104</td>\n</tr>\n<tr>\n<td>5.4.1.1. Prerequisites to install LVM Storage</td>\n<td>105</td>\n</tr>\n<tr>\n<td>5.4.1.2. Installing LVM Storage by using the CLI</td>\n<td>105</td>\n</tr>\n<tr>\n<td>5.4.1.3. Installing LVM Storage by using the web console</td>\n<td>107</td>\n</tr>\n<tr>\n<td>5.4.1.4. Installing LVM Storage in a disconnected environment</td>\n<td>108</td>\n</tr>\n<tr>\n<td>5.4.1.5. Installing LVM Storage by using RHACM</td>\n<td>110</td>\n</tr>\n<tr>\n<td>5.4.2. About the LVMCluster custom resource</td>\n<td>112</td>\n</tr>\n<tr>\n<td>5.4.2.1. Explanation of fields in the LVMCluster CR</td>\n<td>113</td>\n</tr>\n<tr>\n<td>5.4.2.2. Limitations to configure the size of the devices used in LVM Storage</td>\n<td>117</td>\n</tr>\n<tr>\n<td>5.4.2.3. About adding devices to a volume group</td>\n<td>119</td>\n</tr>\n<tr>\n<td>5.4.2.4. About removing devices and device classes from a volume group</td>\n<td>120</td>\n</tr>\n<tr>\n<td>5.4.2.4.1. Removing the device paths in the deviceSelector.paths field</td>\n<td>120</td>\n</tr>\n</table><table>\n<tr>\n<td>5.4.2.4.2. Removing the deviceClass from the LVMCluster</td>\n<td>121</td>\n</tr>\n<tr>\n<td>5.4.2.5. Devices not supported by LVM Storage</td>\n<td>121</td>\n</tr>\n<tr>\n<td>5.4.3. Ways to create an LVMCluster custom resource</td>\n<td>122</td>\n</tr>\n<tr>\n<td>5.4.3.1. Reusing a volume group from the previous LVM Storage installation</td>\n<td>123</td>\n</tr>\n<tr>\n<td>5.4.3.2. Creating an LVMCluster CR by using the CLI</td>\n<td>124</td>\n</tr>\n<tr>\n<td>5.4.3.3. Creating an LVMCluster CR by using the web console</td>\n<td>127</td>\n</tr>\n<tr>\n<td>5.4.3.4. Creating an LVMCluster CR by using RHACM</td>\n<td>128</td>\n</tr>\n<tr>\n<td>5.4.4. Ways to delete an LVMCluster custom resource</td>\n<td>129</td>\n</tr>\n<tr>\n<td>5.4.4.1. Deleting an LVMCluster CR by using the CLI</td>\n<td>130</td>\n</tr>\n<tr>\n<td>5.4.4.2. Deleting an LVMCluster CR by using the web console</td>\n<td>130</td>\n</tr>\n<tr>\n<td>5.4.4.3. Deleting an LVMCluster CR by using RHACM</td>\n<td>131</td>\n</tr>\n<tr>\n<td>5.4.5. Provisioning storage</td>\n<td>134</td>\n</tr>\n<tr>\n<td>5.4.6. Ways to scale up the storage of clusters</td>\n<td>136</td>\n</tr>\n<tr>\n<td>5.4.6.1. Scaling up the storage of clusters by using the CLI</td>\n<td>136</td>\n</tr>\n<tr>\n<td>5.4.6.2. Scaling up the storage of clusters by using the web console</td>\n<td>138</td>\n</tr>\n<tr>\n<td>5.4.6.3. Scaling up the storage of clusters by using RHACM</td>\n<td>139</td>\n</tr>\n<tr>\n<td>5.4.7. Expanding a persistent volume claim</td>\n<td>141</td>\n</tr>\n<tr>\n<td>5.4.8. Deleting a persistent volume claim</td>\n<td>142</td>\n</tr>\n<tr>\n<td>5.4.9. About volume snapshots</td>\n<td>142</td>\n</tr>\n<tr>\n<td>5.4.9.1. Limitations for creating volume snapshots in multi-node topology</td>\n<td>143</td>\n</tr>\n<tr>\n<td>5.4.9.2. Creating volume snapshots</td>\n<td>143</td>\n</tr>\n<tr>\n<td>5.4.9.3. Restoring volume snapshots</td>\n<td>144</td>\n</tr>\n<tr>\n<td>5.4.9.4. Deleting volume snapshots</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.4.10. About volume clones</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.4.10.1. Limitations for creating volume clones in multi-node topology</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.4.10.2. Creating volume clones</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.4.10.3. Deleting volume clones</td>\n<td>148</td>\n</tr>\n<tr>\n<td>5.4.11. Updating LVM Storage</td>\n<td>148</td>\n</tr>\n<tr>\n<td>5.4.12. Monitoring LVM Storage</td>\n<td>150</td>\n</tr>\n<tr>\n<td>5.4.12.1. Metrics</td>\n<td>150</td>\n</tr>\n<tr>\n<td>5.4.12.2. Alerts</td>\n<td>150</td>\n</tr>\n<tr>\n<td>5.4.13. Uninstalling LVM Storage by using the CLI</td>\n<td>151</td>\n</tr>\n<tr>\n<td>5.4.14. Uninstalling LVM Storage by using the web console</td>\n<td>152</td>\n</tr>\n<tr>\n<td>5.4.15. Uninstalling LVM Storage installed using RHACM</td>\n<td>153</td>\n</tr>\n<tr>\n<td>5.4.16. Downloading log files and diagnostic information using must-gather</td>\n<td>155</td>\n</tr>\n<tr>\n<td>5.4.17. Troubleshooting persistent storage</td>\n<td>156</td>\n</tr>\n<tr>\n<td>5.4.17.1. Investigating a PVC stuck in the Pending state</td>\n<td>156</td>\n</tr>\n<tr>\n<td>5.4.17.2. Recovering from a missing storage class</td>\n<td>156</td>\n</tr>\n<tr>\n<td>5.4.17.3. Recovering from node failure</td>\n<td>158</td>\n</tr>\n<tr>\n<td>5.4.17.4. Recovering from disk failure</td>\n<td>158</td>\n</tr>\n<tr>\n<td>5.4.17.5. Performing a forced clean-up</td>\n<td>160</td>\n</tr>\n<tr>\n<td><b>CHAPTER 6. USING CONTAINER STORAGE INTERFACE (CSI)</b> .....</td>\n<td><b>162</b></td>\n</tr>\n<tr>\n<td>6.1. CONFIGURING CSI VOLUMES</td>\n<td>162</td>\n</tr>\n<tr>\n<td>6.1.1. CSI architecture</td>\n<td>162</td>\n</tr>\n<tr>\n<td>6.1.1.1. External CSI controllers</td>\n<td>162</td>\n</tr>\n<tr>\n<td>6.1.1.2. CSI driver daemon set</td>\n<td>163</td>\n</tr>\n<tr>\n<td>6.1.2. CSI drivers supported by OpenShift Container Platform</td>\n<td>163</td>\n</tr>\n<tr>\n<td>6.1.3. Dynamic provisioning</td>\n<td>166</td>\n</tr>\n<tr>\n<td>6.1.4. Example using the CSI driver</td>\n<td>167</td>\n</tr>\n<tr>\n<td>6.2. CSI INLINE EPHEMERAL VOLUMES</td>\n<td>167</td>\n</tr>\n<tr>\n<td>6.2.1. Overview of CSI inline ephemeral volumes</td>\n<td>167</td>\n</tr>\n<tr>\n<td>6.2.1.1. Support limitations</td>\n<td>168</td>\n</tr>\n</table>---\n\n<table><tr><td>6.2.2. CSI Volume Admission plugin</td><td>168</td></tr><tr><td> 6.2.2.1. Overview</td><td>168</td></tr><tr><td> 6.2.2.2. Pod security profile enforcement</td><td>169</td></tr><tr><td> 6.2.2.3. Pod security profile warning</td><td>169</td></tr><tr><td> 6.2.2.4. Pod security profile audit</td><td>169</td></tr><tr><td> 6.2.2.5. Default behavior for the CSI Volume Admission plugin</td><td>170</td></tr><tr><td>6.2.3. Embedding a CSI inline ephemeral volume in the pod specification</td><td>170</td></tr><tr><td>6.2.4. Additional resources</td><td>171</td></tr><tr><td>6.3. CSI VOLUME SNAPSHOTS</td><td>171</td></tr><tr><td> 6.3.1. Overview of CSI volume snapshots</td><td>171</td></tr><tr><td> 6.3.2. CSI snapshot controller and sidecar</td><td>172</td></tr><tr><td> 6.3.2.1. External controller</td><td>172</td></tr><tr><td> 6.3.2.2. External sidecar</td><td>172</td></tr><tr><td> 6.3.3. About the CSI Snapshot Controller Operator</td><td>172</td></tr><tr><td> 6.3.3.1. Volume snapshot CRDs</td><td>172</td></tr><tr><td> 6.3.4. Volume snapshot provisioning</td><td>173</td></tr><tr><td> 6.3.4.1. Dynamic provisioning</td><td>173</td></tr><tr><td> 6.3.4.2. Manual provisioning</td><td>173</td></tr><tr><td> 6.3.5. Creating a volume snapshot</td><td>173</td></tr><tr><td> 6.3.6. Deleting a volume snapshot</td><td>176</td></tr><tr><td> 6.3.7. Restoring a volume snapshot</td><td>177</td></tr><tr><td> 6.3.8. Changing the maximum number of snapshots for vSphere</td><td>179</td></tr><tr><td> 6.3.9. Additional resources</td><td>180</td></tr><tr><td>6.4. CSI VOLUME GROUP SNAPSHOTS</td><td>180</td></tr><tr><td> 6.4.1. Overview of CSI volume group snapshots</td><td>181</td></tr><tr><td> 6.4.2. CSI volume group snapshots limitations</td><td>181</td></tr><tr><td> 6.4.3. Creating a volume group snapshot class</td><td>182</td></tr><tr><td> 6.4.4. Creating a volume group snapshot</td><td>182</td></tr><tr><td> 6.4.5. Restoring a volume group snapshot</td><td>185</td></tr><tr><td> 6.4.6. Additional resources</td><td>186</td></tr><tr><td>6.5. CSI VOLUME CLONING</td><td>186</td></tr><tr><td> 6.5.1. Overview of CSI volume cloning</td><td>186</td></tr><tr><td> 6.5.1.1. Support limitations</td><td>187</td></tr><tr><td> 6.5.2. Provisioning a CSI volume clone</td><td>187</td></tr><tr><td>6.6. VOLUME POPULATORS</td><td>188</td></tr><tr><td> 6.6.1. Volume populators overview</td><td>188</td></tr><tr><td> 6.6.2. Creating volume populators</td><td>189</td></tr><tr><td> 6.6.2.1. Creating CRDs for volume populators</td><td>189</td></tr><tr><td> 6.6.2.2. Creating prepopulated volumes using volume populators</td><td>193</td></tr><tr><td> 6.6.2.3. Uninstalling volume populators</td><td>195</td></tr><tr><td>6.7. MANAGING THE DEFAULT STORAGE CLASS</td><td>195</td></tr><tr><td> 6.7.1. Overview</td><td>195</td></tr><tr><td> 6.7.2. Managing the default storage class using the web console</td><td>196</td></tr><tr><td> 6.7.3. Managing the default storage class using the CLI</td><td>197</td></tr><tr><td> 6.7.4. Absent or multiple default storage classes</td><td>197</td></tr><tr><td> 6.7.4.1. Multiple default storage classes</td><td>197</td></tr><tr><td> 6.7.4.2. Absent default storage class</td><td>197</td></tr><tr><td> 6.7.5. Changing the default storage class</td><td>198</td></tr><tr><td>6.8. CSI AUTOMATIC MIGRATION</td><td>199</td></tr><tr><td> 6.8.1. Overview</td><td>199</td></tr><tr><td> 6.8.2. Storage class implications</td><td>200</td></tr><tr><td>6.9. AWS ELASTIC BLOCK STORE CSI DRIVER OPERATOR</td><td>200</td></tr><tr><td> 6.9.1. Overview</td><td>200</td></tr></table>\n\n---<table><tr><td>6.9.2. About CSI</td><td>200</td></tr><tr><td>6.9.3. User-managed encryption</td><td>201</td></tr><tr><td>6.10. AWS ELASTIC FILE SERVICE CSI DRIVER OPERATOR</td><td>201</td></tr><tr><td>6.10.1. Overview</td><td>201</td></tr><tr><td>6.10.2. About CSI</td><td>202</td></tr><tr><td>6.10.3. Setting up the AWS EFS CSI Driver Operator</td><td>202</td></tr><tr><td>6.10.3.1. Obtaining a role Amazon Resource Name for Security Token Service</td><td>202</td></tr><tr><td>6.10.3.2. Installing the AWS EFS CSI Driver Operator</td><td>204</td></tr><tr><td>6.10.3.3. Installing the AWS EFS CSI Driver</td><td>205</td></tr><tr><td>6.10.4. Creating the AWS EFS storage class</td><td>205</td></tr><tr><td>6.10.4.1. Creating the AWS EFS storage class using the console</td><td>206</td></tr><tr><td>6.10.4.2. Creating the AWS EFS storage class using the CLI</td><td>206</td></tr><tr><td>6.10.5. AWS EFS CSI cross account support</td><td>207</td></tr><tr><td>6.10.6. One Zone file systems</td><td>215</td></tr><tr><td>6.10.6.1. One Zone file systems overview</td><td>215</td></tr><tr><td>6.10.6.2. Setting up One Zone file systems with STS</td><td>216</td></tr><tr><td>6.10.7. Dynamic provisioning for Amazon Elastic File Storage</td><td>217</td></tr><tr><td>6.10.8. Creating static PVs with Amazon Elastic File Storage</td><td>218</td></tr><tr><td>6.10.9. Amazon Elastic File Storage security</td><td>219</td></tr><tr><td>6.10.10. AWS EFS storage CSI usage metrics</td><td>219</td></tr><tr><td>6.10.10.1. Usage metrics overview</td><td>220</td></tr><tr><td>6.10.10.2. Enabling usage metrics using the web console</td><td>220</td></tr><tr><td>6.10.10.3. Enabling usage metrics using the CLI</td><td>221</td></tr><tr><td>6.10.11. Amazon Elastic File Storage troubleshooting</td><td>221</td></tr><tr><td>6.10.12. Uninstalling the AWS EFS CSI Driver Operator</td><td>222</td></tr><tr><td>6.10.13. Additional resources</td><td>223</td></tr><tr><td>6.11. AZURE DISK CSI DRIVER OPERATOR</td><td>224</td></tr><tr><td>6.11.1. Overview</td><td>224</td></tr><tr><td>6.11.2. About CSI</td><td>224</td></tr><tr><td>6.11.3. Creating a storage class with storage account type</td><td>224</td></tr><tr><td>6.11.4. Performance plus for Azure Disk</td><td>225</td></tr><tr><td>6.11.4.1. Overview</td><td>225</td></tr><tr><td>6.11.4.2. Limitations</td><td>226</td></tr><tr><td>6.11.4.3. Creating a storage class to use performance plus enhanced disks</td><td>226</td></tr><tr><td>6.11.4.4. Enabling performance plus by snapshot or cloning</td><td>227</td></tr><tr><td>6.11.5. User-managed encryption</td><td>228</td></tr><tr><td>6.11.6. Machine sets that deploy machines with ultra disks using PVCs</td><td>228</td></tr><tr><td>6.11.6.1. Creating machines with ultra disks by using machine sets</td><td>229</td></tr><tr><td>6.11.6.2. Troubleshooting resources for machine sets that enable ultra disks</td><td>232</td></tr><tr><td>6.11.6.2.1. Unable to mount a persistent volume claim backed by an ultra disk</td><td>232</td></tr><tr><td>6.11.7. Additional resources</td><td>232</td></tr><tr><td>6.12. AZURE FILE CSI DRIVER OPERATOR</td><td>232</td></tr><tr><td>6.12.1. Overview</td><td>232</td></tr><tr><td>6.12.2. About CSI</td><td>233</td></tr><tr><td>6.12.3. NFS support</td><td>233</td></tr><tr><td>6.12.4. Azure File cross-subscription support</td><td>234</td></tr><tr><td>6.12.4.1. Dynamic provisioning across subscriptions for Azure File</td><td>234</td></tr><tr><td>6.12.4.2. Static provisioning across subscriptions for Azure File by creating a PV and PVC:</td><td>236</td></tr><tr><td>6.12.5. Static provisioning for Azure File</td><td>238</td></tr><tr><td>6.13. AZURE STACK HUB CSI DRIVER OPERATOR</td><td>241</td></tr><tr><td>6.13.1. Overview</td><td>241</td></tr><tr><td>6.13.2. About CSI</td><td>242</td></tr><tr><td>6.13.3. Additional resources</td><td>242</td></tr></table>---\n\n<table>\n<tr>\n<td>6.14. GCP PD CSI DRIVER OPERATOR</td>\n<td>242</td>\n</tr>\n<tr>\n<td> 6.14.1. Overview</td>\n<td>242</td>\n</tr>\n<tr>\n<td> 6.14.2. About CSI</td>\n<td>243</td>\n</tr>\n<tr>\n<td> 6.14.3. Reducing permissions while using the GCP PD CSI Driver Operator</td>\n<td>243</td>\n</tr>\n<tr>\n<td> 6.14.4. GCP PD CSI driver storage class parameters</td>\n<td>244</td>\n</tr>\n<tr>\n<td> 6.14.5. C3 instance type for bare metal and N4 machine series</td>\n<td>244</td>\n</tr>\n<tr>\n<td> 6.14.5.1. C3 and N4 instance type limitations</td>\n<td>244</td>\n</tr>\n<tr>\n<td> 6.14.5.2. Storage pools for hyperdisk-balanced disks overview</td>\n<td>245</td>\n</tr>\n<tr>\n<td> 6.14.5.3. Setting up hyperdisk-balanced disks</td>\n<td>245</td>\n</tr>\n<tr>\n<td> 6.14.5.4. Additional resources</td>\n<td>250</td>\n</tr>\n<tr>\n<td> 6.14.6. Creating a custom-encrypted persistent volume</td>\n<td>250</td>\n</tr>\n<tr>\n<td> 6.14.7. User-managed encryption</td>\n<td>252</td>\n</tr>\n<tr>\n<td> 6.14.8. Additional resources</td>\n<td>252</td>\n</tr>\n<tr>\n<td>6.15. GOOGLE CLOUD FILESTORE CSI DRIVER OPERATOR</td>\n<td>252</td>\n</tr>\n<tr>\n<td> 6.15.1. Overview</td>\n<td>252</td>\n</tr>\n<tr>\n<td> 6.15.2. About CSI</td>\n<td>253</td>\n</tr>\n<tr>\n<td> 6.15.3. Installing the Google Cloud Filestore CSI Driver Operator</td>\n<td>253</td>\n</tr>\n<tr>\n<td> 6.15.3.1. Preparing to install the Google Cloud Filestore CSI Driver Operator with Workload Identity</td>\n<td>253</td>\n</tr>\n<tr>\n<td> 6.15.3.2. Installing the Google Cloud Filestore CSI Driver Operator</td>\n<td>255</td>\n</tr>\n<tr>\n<td> 6.15.4. Creating a storage class for GCP Filestore Storage</td>\n<td>257</td>\n</tr>\n<tr>\n<td> 6.15.5. NFS export options</td>\n<td>258</td>\n</tr>\n<tr>\n<td> 6.15.6. Destroying clusters and GCP Filestore</td>\n<td>259</td>\n</tr>\n<tr>\n<td> 6.15.7. Additional resources</td>\n<td>260</td>\n</tr>\n<tr>\n<td>6.16. IBM CLOUD VPC BLOCK CSI DRIVER OPERATOR</td>\n<td>260</td>\n</tr>\n<tr>\n<td> 6.16.1. Overview</td>\n<td>260</td>\n</tr>\n<tr>\n<td> 6.16.2. About CSI</td>\n<td>260</td>\n</tr>\n<tr>\n<td> 6.16.3. User-managed encryption</td>\n<td>261</td>\n</tr>\n<tr>\n<td>6.17. IBM POWER VIRTUAL SERVER BLOCK CSI DRIVER OPERATOR</td>\n<td>261</td>\n</tr>\n<tr>\n<td> 6.17.1. Introduction</td>\n<td>261</td>\n</tr>\n<tr>\n<td> 6.17.2. Overview</td>\n<td>261</td>\n</tr>\n<tr>\n<td> 6.17.3. About CSI</td>\n<td>262</td>\n</tr>\n<tr>\n<td>6.18. OPENSTACK CINDER CSI DRIVER OPERATOR</td>\n<td>262</td>\n</tr>\n<tr>\n<td> 6.18.1. Overview</td>\n<td>262</td>\n</tr>\n<tr>\n<td> 6.18.2. About CSI</td>\n<td>262</td>\n</tr>\n<tr>\n<td> 6.18.3. Making OpenStack Cinder CSI the default storage class</td>\n<td>262</td>\n</tr>\n<tr>\n<td>6.19. OPENSTACK MANILA CSI DRIVER OPERATOR</td>\n<td>264</td>\n</tr>\n<tr>\n<td> 6.19.1. Overview</td>\n<td>264</td>\n</tr>\n<tr>\n<td> 6.19.2. About CSI</td>\n<td>264</td>\n</tr>\n<tr>\n<td> 6.19.3. Manila CSI Driver Operator limitations</td>\n<td>265</td>\n</tr>\n<tr>\n<td> 6.19.4. Dynamically provisioning Manila CSI volumes</td>\n<td>265</td>\n</tr>\n<tr>\n<td> 6.19.5. Customizing Manila share access rules</td>\n<td>267</td>\n</tr>\n<tr>\n<td>6.20. SECRETS STORE CONTAINER STORAGE INTERFACE DRIVER OPERATOR</td>\n<td>269</td>\n</tr>\n<tr>\n<td> 6.20.1. Overview</td>\n<td>269</td>\n</tr>\n<tr>\n<td> 6.20.1.1. Secrets store providers</td>\n<td>270</td>\n</tr>\n<tr>\n<td> 6.20.2. About CSI</td>\n<td>270</td>\n</tr>\n<tr>\n<td> 6.20.3. Support for disconnected environments</td>\n<td>270</td>\n</tr>\n<tr>\n<td> 6.20.4. Support for network policies</td>\n<td>270</td>\n</tr>\n<tr>\n<td> 6.20.5. Installing the Secrets Store CSI driver</td>\n<td>271</td>\n</tr>\n<tr>\n<td> 6.20.6. Uninstalling the Secrets Store CSI Driver Operator</td>\n<td>272</td>\n</tr>\n<tr>\n<td> 6.20.7. Additional resources</td>\n<td>273</td>\n</tr>\n<tr>\n<td>6.21. CIFS/SMB CSI DRIVER OPERATOR</td>\n<td>273</td>\n</tr>\n<tr>\n<td> 6.21.1. About CSI</td>\n<td>273</td>\n</tr>\n<tr>\n<td> 6.21.2. Limitations</td>\n<td>273</td>\n</tr>\n</table><table>\n<tbody>\n<tr>\n<td>6.21.3. Installing the CIFS/SMB CSI Driver Operator</td>\n<td>274</td>\n</tr>\n<tr>\n<td>6.21.4. Installing the CIFS/SMB CSI Driver</td>\n<td>274</td>\n</tr>\n<tr>\n<td>6.21.5. Dynamic provisioning</td>\n<td>275</td>\n</tr>\n<tr>\n<td>6.21.6. Static provisioning</td>\n<td>277</td>\n</tr>\n<tr>\n<td>6.21.7. Additional resources</td>\n<td>282</td>\n</tr>\n<tr>\n<td><b>6.22. VMWARE VSPHERE CSI DRIVER OPERATOR</b></td>\n<td><b>282</b></td>\n</tr>\n<tr>\n<td>6.22.1. Overview</td>\n<td>282</td>\n</tr>\n<tr>\n<td>6.22.2. About CSI</td>\n<td>282</td>\n</tr>\n<tr>\n<td>6.22.3. vSphere CSI limitations</td>\n<td>283</td>\n</tr>\n<tr>\n<td>6.22.4. vSphere storage policy</td>\n<td>283</td>\n</tr>\n<tr>\n<td>6.22.5. ReadWriteMany vSphere volume support</td>\n<td>283</td>\n</tr>\n<tr>\n<td>6.22.6. VMware vSphere CSI Driver Operator requirements</td>\n<td>284</td>\n</tr>\n<tr>\n<td>6.22.7. Removing a third-party vSphere CSI Driver Operator</td>\n<td>284</td>\n</tr>\n<tr>\n<td>6.22.8. vSphere persistent disks encryption</td>\n<td>285</td>\n</tr>\n<tr>\n<td>6.22.8.1. Using datastore URL</td>\n<td>286</td>\n</tr>\n<tr>\n<td>6.22.8.2. Using tag-based placement</td>\n<td>286</td>\n</tr>\n<tr>\n<td>6.22.9. Multiple vCenter support for vSphere CSI</td>\n<td>287</td>\n</tr>\n<tr>\n<td>6.22.9.1. Configuring multiple vCenters during installation</td>\n<td>287</td>\n</tr>\n<tr>\n<td>6.22.10. vSphere CSI topology overview</td>\n<td>287</td>\n</tr>\n<tr>\n<td>6.22.10.1. vSphere CSI topology requirements</td>\n<td>288</td>\n</tr>\n<tr>\n<td>6.22.10.2. Creating vSphere storage topology during installation</td>\n<td>288</td>\n</tr>\n<tr>\n<td>6.22.10.2.1. Procedure</td>\n<td>289</td>\n</tr>\n<tr>\n<td>6.22.10.3. Creating vSphere storage topology postinstallation</td>\n<td>289</td>\n</tr>\n<tr>\n<td>6.22.10.3.1. Procedure</td>\n<td>289</td>\n</tr>\n<tr>\n<td>6.22.10.4. Creating vSphere storage topology without an infra topology</td>\n<td>290</td>\n</tr>\n<tr>\n<td>6.22.10.4.1. Procedure</td>\n<td>291</td>\n</tr>\n<tr>\n<td>6.22.10.5. Results</td>\n<td>294</td>\n</tr>\n<tr>\n<td>6.22.11. Changing the maximum number of snapshots for vSphere</td>\n<td>294</td>\n</tr>\n<tr>\n<td>6.22.12. Migrating CNS volumes between datastores for vSphere</td>\n<td>296</td>\n</tr>\n<tr>\n<td>6.22.13. Disabling and enabling storage on vSphere</td>\n<td>297</td>\n</tr>\n<tr>\n<td>6.22.13.1. Consequences of disabling and enabling storage on vSphere</td>\n<td>297</td>\n</tr>\n<tr>\n<td>6.22.13.2. Disabling and enabling storage on vSphere</td>\n<td>297</td>\n</tr>\n<tr>\n<td>6.22.14. Adding bare-metal nodes</td>\n<td>298</td>\n</tr>\n<tr>\n<td>6.22.15. Increasing maximum volumes per node for vSphere</td>\n<td>299</td>\n</tr>\n<tr>\n<td>6.22.15.1. Increasing the maximum allowable volumes per node for vSphere</td>\n<td>299</td>\n</tr>\n<tr>\n<td>6.22.16. Additional resources</td>\n<td>300</td>\n</tr>\n<tr>\n<td><b>CHAPTER 7. GENERIC EPHEMERAL VOLUMES</b> .....</td>\n<td><b>302</b></td>\n</tr>\n<tr>\n<td>7.1. OVERVIEW OF GENERIC EPHEMERAL VOLUMES</td>\n<td>302</td>\n</tr>\n<tr>\n<td>7.2. LIFECYCLE AND PERSISTENT VOLUME CLAIMS</td>\n<td>302</td>\n</tr>\n<tr>\n<td>7.3. SECURITY</td>\n<td>303</td>\n</tr>\n<tr>\n<td>7.4. PERSISTENT VOLUME CLAIM NAMING</td>\n<td>303</td>\n</tr>\n<tr>\n<td>7.5. CREATING GENERIC EPHEMERAL VOLUMES</td>\n<td>303</td>\n</tr>\n<tr>\n<td><b>CHAPTER 8. EXPANDING PERSISTENT VOLUMES</b> .....</td>\n<td><b>305</b></td>\n</tr>\n<tr>\n<td>8.1. ENABLING VOLUME EXPANSION SUPPORT</td>\n<td>305</td>\n</tr>\n<tr>\n<td>8.2. EXPANDING CSI VOLUMES</td>\n<td>305</td>\n</tr>\n<tr>\n<td>8.3. EXPANDING FLEXVOLUME WITH A SUPPORTED DRIVER</td>\n<td>306</td>\n</tr>\n<tr>\n<td>8.4. EXPANDING LOCAL VOLUMES</td>\n<td>306</td>\n</tr>\n<tr>\n<td>8.5. EXPANDING PERSISTENT VOLUME CLAIMS (PVCS) WITH A FILE SYSTEM</td>\n<td>307</td>\n</tr>\n<tr>\n<td>8.6. RECOVERING FROM FAILURE WHEN EXPANDING VOLUMES</td>\n<td>308</td>\n</tr>\n<tr>\n<td>8.7. VIEWING THE STATUS OF VOLUME RESIZE</td>\n<td>308</td>\n</tr>\n<tr>\n<td>8.8. ADDITIONAL RESOURCES</td>\n<td>308</td>\n</tr>\n</tbody>\n</table>---\n\n<table><tr><td><b>CHAPTER 9. DYNAMIC PROVISIONING</b> .....</td><td><b>309</b></td></tr><tr><td> 9.1. ABOUT DYNAMIC PROVISIONING</td><td>309</td></tr><tr><td> 9.2. AVAILABLE DYNAMIC PROVISIONING PLUGINS</td><td>309</td></tr><tr><td> 9.3. DEFINING A STORAGE CLASS</td><td>310</td></tr><tr><td> 9.3.1. Basic StorageClass object definition</td><td>310</td></tr><tr><td> 9.3.2. Storage class annotations</td><td>311</td></tr><tr><td> 9.3.3. RHOSP Cinder object definition</td><td>312</td></tr><tr><td> 9.3.4. RHOSP Manila Container Storage Interface (CSI) object definition</td><td>312</td></tr><tr><td> 9.3.5. AWS Elastic Block Store (EBS) object definition</td><td>312</td></tr><tr><td> 9.3.6. Azure Disk object definition</td><td>313</td></tr><tr><td> 9.3.7. Azure File object definition</td><td>314</td></tr><tr><td> 9.3.7.1. Considerations when using Azure File</td><td>315</td></tr><tr><td> 9.3.8. GCE PersistentDisk (gcePD) object definition</td><td>316</td></tr><tr><td> 9.3.9. VMware vSphere object definition</td><td>316</td></tr><tr><td> 9.4. CHANGING THE DEFAULT STORAGE CLASS</td><td>317</td></tr><tr><td><b>CHAPTER 10. DETACH VOLUMES AFTER NON-GRACEFUL NODE SHUTDOWN</b> .....</td><td><b>319</b></td></tr><tr><td> 10.1. OVERVIEW</td><td>319</td></tr><tr><td> 10.2. ADDING AN OUT-OF-SERVICE Taint MANUALLY FOR AUTOMATIC VOLUME DETACHMENT</td><td>319</td></tr></table># CHAPTER 1. OPENSHIFT CONTAINER PLATFORM STORAGE OVERVIEW\n\nOpenShift Container Platform supports multiple types of storage, both for on-premise and cloud providers. You can manage container storage for persistent and non-persistent data in an OpenShift Container Platform cluster.\n\n## 1.1. GLOSSARY OF COMMON TERMS FOR OPENSHIFT CONTAINER PLATFORM STORAGE\n\nThis glossary defines common terms that are used in the storage content.\n\n### Access modes\n\nVolume access modes describe volume capabilities. You can use access modes to match persistent volume claim (PVC) and persistent volume (PV). The following are the examples of access modes:\n\n- • ReadWriteOnce (RWO)\n- • ReadOnlyMany (ROX)\n- • ReadWriteMany (RWX)\n- • ReadWriteOncePod (RWOP)\n\n### Cinder\n\nThe Block Storage service for Red Hat OpenStack Platform (RHOSP) which manages the administration, security, and scheduling of all volumes.\n\n### Config map\n\nA config map provides a way to inject configuration data into pods. You can reference the data stored in a config map in a volume of type **ConfigMap**. Applications running in a pod can use this data.\n\n### Container Storage Interface (CSI)\n\nAn API specification for the management of container storage across different container orchestration (CO) systems.\n\n### Dynamic Provisioning\n\nThe framework allows you to create storage volumes on-demand, eliminating the need for cluster administrators to pre-provision persistent storage.\n\n### Ephemeral storage\n\nPods and containers can require temporary or transient local storage for their operation. The lifetime of this ephemeral storage does not extend beyond the life of the individual pod, and this ephemeral storage cannot be shared across pods.\n\n### Fiber channel\n\nA networking technology that is used to transfer data among data centers, computer servers, switches and storage.\n\n### FlexVolume\n\nFlexVolume is an out-of-tree plugin interface that uses an exec-based model to interface with storage drivers. You must install the FlexVolume driver binaries in a pre-defined volume plugin path on each node and in some cases the control plane nodes.\n\n### fsGroupThe fsGroup defines a file system group ID of a pod.\n\n### iSCSI\n\nInternet Small Computer Systems Interface (iSCSI) is an Internet Protocol-based storage networking standard for linking data storage facilities. An iSCSI volume allows an existing iSCSI (SCSI over IP) volume to be mounted into your Pod.\n\n### hostPath\n\nA hostPath volume in an OpenShift Container Platform cluster mounts a file or directory from the host node's filesystem into your pod.\n\n### KMS key\n\nThe Key Management Service (KMS) helps you achieve the required level of encryption of your data across different services. You can use the KMS key to encrypt, decrypt, and re-encrypt data.\n\n### Local volumes\n\nA local volume represents a mounted local storage device such as a disk, partition or directory.\n\n### Nested mount points\n\nA nested mount point is a mount point that attempts to use a mount point created by a previous volume.\n\n## Example pod definition with nested mount points\n\n```\nkind: Pod\napiVersion: v1\nmetadata:\n name: webapp\n labels:\n name: webapp\nspec:\n containers:\n - name: webapp\n image: nginx\n ports:\n - containerPort: 80\n name: \"http-server\"\n volumeMounts:\n - mountPath: /mnt/web\n name: web\n - mountPath: /mnt/web/redis 1\n name: redis\n volumes:\n - name: redis\n persistentVolumeClaim:\n claimName: \"redis\"\n - name: web\n persistentVolumeClaim:\n claimName: \"web\"\n```\n\n**1** Nested mount point\n\nDo *not* use nested mount points because OpenShift Container Platform does not guarantee the order in which mount points are created. Such usage is prone to race conditions and undefined behavior.## NFS\n\nA Network File System (NFS) that allows remote hosts to mount file systems over a network and interact with those file systems as though they are mounted locally. This enables system administrators to consolidate resources onto centralized servers on the network.\n\n## OpenShift Data Foundation\n\nA provider of agnostic persistent storage for OpenShift Container Platform supporting file, block, and object storage, either in-house or in hybrid clouds\n\n### Persistent storage\n\nPods and containers can require permanent storage for their operation. OpenShift Container Platform uses the Kubernetes persistent volume (PV) framework to allow cluster administrators to provision persistent storage for a cluster. Developers can use PVC to request PV resources without having specific knowledge of the underlying storage infrastructure.\n\n### Persistent volumes (PV)\n\nOpenShift Container Platform uses the Kubernetes persistent volume (PV) framework to allow cluster administrators to provision persistent storage for a cluster. Developers can use PVC to request PV resources without having specific knowledge of the underlying storage infrastructure.\n\n### Persistent volume claims (PVCs)\n\nYou can use a PVC to mount a PersistentVolume into a Pod. You can access the storage without knowing the details of the cloud environment.\n\n### Pod\n\nOne or more containers with shared resources, such as volume and IP addresses, running in your OpenShift Container Platform cluster. A pod is the smallest compute unit defined, deployed, and managed.\n\n### Reclaim policy\n\nA policy that tells the cluster what to do with the volume after it is released. A volume's reclaim policy can be **Retain**, **Recycle**, or **Delete**.\n\n### Role-based access control (RBAC)\n\nRole-based access control (RBAC) is a method of regulating access to computer or network resources based on the roles of individual users within your organization.\n\n### Stateless applications\n\nA stateless application is an application program that does not save client data generated in one session for use in the next session with that client.\n\n### Stateful applications\n\nA stateful application is an application program that saves data to persistent disk storage. A server, client, and applications can use a persistent disk storage. You can use the **Statefulset** object in OpenShift Container Platform to manage the deployment and scaling of a set of Pods, and provides guarantee about the ordering and uniqueness of these Pods.\n\n### Static provisioning\n\nA cluster administrator creates a number of PVs. PVs contain the details of storage. PVs exist in the Kubernetes API and are available for consumption.\n\n### Storage\n\nOpenShift Container Platform supports many types of storage, both for on-premise and cloud providers. You can manage container storage for persistent and non-persistent data in an OpenShift Container Platform cluster.\n\n### Storage classA storage class provides a way for administrators to describe the classes of storage they offer. Different classes might map to quality of service levels, backup policies, arbitrary policies determined by the cluster administrators.\n\n### **VMware vSphere's Virtual Machine Disk (VMDK) volumes**\n\nVirtual Machine Disk (VMDK) is a file format that describes containers for virtual hard disk drives that is used in virtual machines.\n\n## **1.2. STORAGE TYPES**\n\nOpenShift Container Platform storage is broadly classified into two categories, namely ephemeral storage and persistent storage.\n\n### **1.2.1. Ephemeral storage**\n\nPods and containers are ephemeral or transient in nature and designed for stateless applications. Ephemeral storage allows administrators and developers to better manage the local storage for some of their operations. For more information about ephemeral storage overview, types, and management, see [Understanding ephemeral storage](#).\n\n### **1.2.2. Persistent storage**\n\nStateful applications deployed in containers require persistent storage. OpenShift Container Platform uses a pre-provisioned storage framework called persistent volumes (PV) to allow cluster administrators to provision persistent storage. The data inside these volumes can exist beyond the lifecycle of an individual pod. Developers can use persistent volume claims (PVCs) to request storage requirements. For more information about persistent storage overview, configuration, and lifecycle, see [Understanding persistent storage](#).\n\n## **1.3. CONTAINER STORAGE INTERFACE (CSI)**\n\nCSI is an API specification for the management of container storage across different container orchestration (CO) systems. You can manage the storage volumes within the container native environments, without having specific knowledge of the underlying storage infrastructure. With the CSI, storage works uniformly across different container orchestration systems, regardless of the storage vendors you are using. For more information about CSI, see [Using Container Storage Interface \\(CSI\\)](#).\n\n## **1.4. DYNAMIC PROVISIONING**\n\nDynamic Provisioning allows you to create storage volumes on-demand, eliminating the need for cluster administrators to pre-provision storage. For more information about dynamic provisioning, see [Dynamic provisioning](#).# CHAPTER 2. UNDERSTANDING EPHEMERAL STORAGE\n\nTo manage temporary data that exists only for the duration of a workload, review the properties of ephemeral storage.\n\n## 2.1. OVERVIEW OF EPHEMERAL STORAGE\n\nTo manage local storage for stateless applications, use ephemeral storage. Ephemeral storage is designed for the transient nature of pods and containers. You can use this feature to handle operations that require storage only for the duration of the lifecycle for the workload. Both developers and administrators can use the feature.\n\nIn addition to persistent storage, pods and containers can require ephemeral or transient local storage for their operation. The lifetime of this ephemeral storage does not extend beyond the life of the individual pod, and this ephemeral storage cannot be shared across pods.\n\nPods use ephemeral local storage for scratch space, caching, and logs. Issues related to the lack of local storage accounting and isolation include the following:\n\n- • Pods cannot detect how much local storage is available to them.\n- • Pods cannot request guaranteed local storage.\n- • Local storage is a best-effort resource.\n- • Pods can be evicted due to other pods filling the local storage, after which new pods are not admitted until sufficient storage is reclaimed.\n\nUnlike persistent volumes, ephemeral storage is unstructured and the space is shared between all pods running on a node, in addition to other uses by the system, the container runtime, and OpenShift Container Platform. The ephemeral storage framework allows pods to specify their transient local storage needs. It also allows OpenShift Container Platform to schedule pods where appropriate, and to protect the node against excessive use of local storage.\n\nWhile the ephemeral storage framework allows administrators and developers to better manage local storage, I/O throughput and latency are not directly affected.\n\n## 2.2. TYPES OF EPHEMERAL STORAGE\n\nTo provision ephemeral local storage, you can create the primary partition by using either root or runtime methods. This storage is always made available in the primary partition, providing temporary space for your workloads.\n\n### 2.2.1. Root\n\nThis partition holds the kubelet root directory, `/var/lib/kubelet/` by default, and `/var/log/` directory. This partition can be shared between user pods, the OS, and Kubernetes system daemons. This partition can be consumed by pods through **EmptyDir** volumes, container logs, image layers, and container-writable layers. Kubelet manages shared access and isolation of this partition. This partition is ephemeral, and applications cannot expect any performance SLAs, such as disk IOPS, from this partition.\n\n### 2.2.2. Runtime\n\nThis is an optional partition that runtimes can use for overlay file systems. OpenShift Container Platformattempts to identify and provide shared access along with isolation to this partition. Container image layers and writable layers are stored here. If the runtime partition exists, the **root** partition does not hold any image layer or other writable storage.\n\n## 2.3. EPHEMERAL STORAGE MANAGEMENT\n\nCluster administrators can manage ephemeral storage within a project by setting quotas that define the limit ranges and number of requests for ephemeral storage across all pods in a non-terminal state. Developers can also set requests and limits on this compute resource at the pod and container level.\n\nYou can manage local ephemeral storage by specifying requests and limits. Each container in a pod can specify the following:\n\n- • **spec.containers[].resources.limits.ephemeral-storage**\n- • **spec.containers[].resources.requests.ephemeral-storage**\n\n### 2.3.1. Ephemeral storage limits and requests units\n\nLimits and requests for ephemeral storage are measured in byte quantities. You can express storage as a plain integer or as a fixed-point number using one of these suffixes: E, P, T, G, M, k. You can also use the power-of-two equivalents: Ei, Pi, Ti, Gi, Mi, Ki.\n\nFor example, the following quantities all represent approximately the same value: 128974848, 129e6, 129M, and 123Mi.\n\n#### IMPORTANT\n\nThe suffixes for each byte quantity are case-sensitive. Be sure to use the correct case. Use the case-sensitive \"M\", such as used in \"400M\", to set the request at 400 megabytes. Use the case-sensitive \"400Mi\" to request 400 mebibytes. If you specify \"400m\" of ephemeral storage, the storage request is only 0.4 bytes.\n\n### 2.3.2. Ephemeral storage requests and limits example\n\nThe following example configuration file shows a pod with two containers:\n\n- • Each container requests 2GiB of local ephemeral storage.\n- • Each container has a limit of 4GiB of local ephemeral storage.\n- • At the pod level, kubelet works out an overall pod storage limit by adding up the limits of all the containers in that pod.\n - ◦ In this case, the total storage usage at the pod level is the sum of the disk usage from all containers plus the pod's **emptyDir** volumes.\n - ◦ Therefore, the pod has a request of 4GiB of local ephemeral storage, and a limit of 8GiB of local ephemeral storage.\n\n#### Example ephemeral storage configuration with quotas and limits\n\n```\napiVersion: v1\nkind: Pod\nmetadata:\n``````\n\nname: frontend\nspec:\n containers:\n - name: app\n image: images.my-company.example/app:v4\n resources:\n requests:\n ephemeral-storage: \"2Gi\" 1\n limits:\n ephemeral-storage: \"4Gi\" 2\n volumeMounts:\n - name: ephemeral\n mountPath: \"/tmp\"\n - name: log-aggregator\n image: images.my-company.example/log-aggregator:v6\n resources:\n requests:\n ephemeral-storage: \"2Gi\"\n limits:\n ephemeral-storage: \"4Gi\"\n volumeMounts:\n - name: ephemeral\n mountPath: \"/tmp\"\n volumes:\n - name: ephemeral\n emptyDir: {}\n\n```\n\n- 1 Container request for local ephemeral storage.\n- 2 Container limit for local ephemeral storage.\n\n### 2.3.3. Ephemeral storage configuration effects pod scheduling and eviction\n\nThe settings in the pod spec affect both how the scheduler makes a decision about scheduling pods and when kubelet evicts pods.\n\n- • First, the scheduler ensures that the sum of the resource requests of the scheduled containers is less than the capacity of the node. In this case, the pod can be assigned to a node only if the node's available ephemeral storage (allocatable resource) is more than 4GiB.\n- • Second, at the container level, because the first container sets a resource limit, kubelet eviction manager measures the disk usage of this container and evicts the pod if the storage usage of the container exceeds its limit (4GiB). The kubelet eviction manager also marks the pod for eviction if the total usage exceeds the overall pod storage limit (8GiB).\n\n## 2.4. ADDITIONAL RESOURCES\n\n- • [Resources managed by quotas](#)\n\n## 2.5. MONITORING EPHEMERAL STORAGETo monitor ephemeral storage usage, use the **/bin/df** utility. By using this tool, you can track disk space consumption on the volumes where ephemeral container data resides, specifically **/var/lib/kubelet** and **/var/lib/containers**.\n\nWhen you use the **df** command, the available space for only **/var/lib/kubelet** is shown if **/var/lib/containers** is placed on a separate disk by the cluster administrator.\n\n### Procedure\n\n- • To show the human-readable values of used and available space in **/var/lib**, enter the following command:\n\n```\n$ df -h /var/lib\n```\n\nThe output shows the ephemeral storage usage in **/var/lib**:\n\n### Example output\n\n```\nFilesystem Size Used Avail Use% Mounted on\n/dev/disk/by-partuuid/4cd1448a-01 69G 32G 34G 49% /\n```# CHAPTER 3. UNDERSTANDING PERSISTENT STORAGE\n\n## 3.1. PERSISTENT STORAGE OVERVIEW\n\nStateful applications deployed in containers require persistent storage. {microshift-short} uses a pre-provisioned storage framework called persistent volumes (PV) to allow node administrators to provision persistent storage. The data inside these volumes can exist beyond the lifecycle of an individual pod. Developers can use persistent volume claims (PVCs) to request storage requirements.\n\nManaging storage is a distinct problem from managing compute resources. OpenShift Container Platform uses the Kubernetes persistent volume (PV) framework to allow cluster administrators to provision persistent storage for a cluster. Developers can use persistent volume claims (PVCs) to request PV resources without having specific knowledge of the underlying storage infrastructure.\n\nPVCs are specific to a project, and are created and used by developers as a means to use a PV. PV resources on their own are not scoped to any single project; they can be shared across the entire OpenShift Container Platform node and claimed from any project. After a PV is bound to a PVC, that PV can not then be bound to additional PVCs. This has the effect of scoping a bound PV to a single namespace, that of the binding project.\n\nPVs are defined by a **PersistentVolume** API object, which represents a piece of existing storage in the cluster that was either statically provisioned by the cluster administrator or dynamically provisioned using a **StorageClass** object. It is a resource in the cluster just like a node is a cluster resource.\n\nPVs are volume plugins like **Volumes** but have a lifecycle that is independent of any individual pod that uses the PV. PV objects capture the details of the implementation of the storage, be that NFS, iSCSI, or a cloud-provider-specific storage system.\n\n### IMPORTANT\n\nHigh availability of storage in the infrastructure is left to the underlying storage provider.\n\nPVCs are defined by a **PersistentVolumeClaim** API object, which represents a request for storage by a developer. It is similar to a pod in that pods consume node resources and PVCs consume PV resources. For example, pods can request specific levels of resources, such as CPU and memory, while PVCs can request specific storage capacity and access modes. For example, they can be mounted once read-write or many times read-only.\n\n## 3.2. LIFECYCLE OF A VOLUME AND CLAIM\n\nPVs are resources in the cluster. PVCs are requests for those resources and also act as claim checks to the resource. The interaction between PVs and PVCs have the following lifecycle.\n\n### 3.2.1. Provision storage\n\nIn response to requests from a developer defined in a PVC, a cluster administrator configures one or more dynamic provisioners that provision storage and a matching PV.\n\nAlternatively, a cluster administrator can create a number of PVs in advance that carry the details of the real storage that is available for use. PVs exist in the API and are available for use.\n\n### 3.2.2. Bind claimsWhen you create a PVC, you request a specific amount of storage, specify the required access mode, and create a storage class to describe and classify the storage. The control loop in the master watches for new PVCs and binds the new PVC to an appropriate PV. If an appropriate PV does not exist, a provisioner for the storage class creates one.\n\nThe size of all PVs might exceed your PVC size. This is especially true with manually provisioned PVs. To minimize the excess, OpenShift Container Platform binds to the smallest PV that matches all other criteria.\n\nClaims remain unbound indefinitely if a matching volume does not exist or can not be created with any available provisioner servicing a storage class. Claims are bound as matching volumes become available. For example, a cluster with many manually provisioned 50Gi volumes would not match a PVC requesting 100Gi. The PVC can be bound when a 100Gi PV is added to the cluster.\n\n### 3.2.3. Use pods and claimed PVs\n\nPods use claims as volumes. The cluster inspects the claim to find the bound volume and mounts that volume for a pod. For those volumes that support multiple access modes, you must specify which mode applies when you use the claim as a volume in a pod.\n\nOnce you have a claim and that claim is bound, the bound PV belongs to you for as long as you need it. You can schedule pods and access claimed PVs by including **persistentVolumeClaim** in the pod's volumes block.\n\n#### NOTE\n\nIf you attach persistent volumes that have high file counts to pods, those pods can fail or can take a long time to start. For more information, see [When using Persistent Volumes with high file counts in OpenShift, why do pods fail to start or take an excessive amount of time to achieve \"Ready\" state?](#)\n\n### 3.2.4. Storage Object in Use Protection\n\nThe Storage Object in Use Protection feature ensures that PVCs in active use by a pod and PVs that are bound to PVCs are not removed from the system, as this can result in data loss.\n\nStorage Object in Use Protection is enabled by default.\n\n#### NOTE\n\nA PVC is in active use by a pod when a **Pod** object exists that uses the PVC.\n\nIf a user deletes a PVC that is in active use by a pod, the PVC is not removed immediately. PVC removal is postponed until the PVC is no longer actively used by any pods. Also, if a cluster admin deletes a PV that is bound to a PVC, the PV is not removed immediately. PV removal is postponed until the PV is no longer bound to a PVC.\n\n### 3.2.5. Release a persistent volume\n\nWhen you are finished with a volume, you can delete the PVC object from the API, which allows reclamation of the resource. The volume is considered released when the claim is deleted, but it is not yet available for another claim. The previous claimant's data remains on the volume and must be handled according to policy.### 3.2.6. Reclaim policy for persistent volumes\n\nThe reclaim policy of a persistent volume tells the cluster what to do with the volume after it is released. A volume's reclaim policy can be **Retain**, **Recycle**, or **Delete**.\n\n- • **Retain** reclaim policy allows manual reclamation of the resource for those volume plugins that support it.\n- • **Recycle** reclaim policy recycles the volume back into the pool of unbound persistent volumes once it is released from its claim.\n\n#### IMPORTANT\n\nThe **Recycle** reclaim policy is deprecated in OpenShift Container Platform 4. Dynamic provisioning is recommended for equivalent and better functionality.\n\n- • **Delete** reclaim policy deletes both the **PersistentVolume** object from OpenShift Container Platform and the associated storage asset in external infrastructure, such as Amazon Elastic Block Store (Amazon EBS) or VMware vSphere.\n\n#### NOTE\n\nDynamically provisioned volumes are always deleted.\n\n### 3.2.7. Reclaiming a persistent volume manually\n\nWhen a persistent volume claim (PVC) is deleted, the persistent volume (PV) still exists and is considered \"released\". However, the PV is not yet available for another claim because the data of the previous claimant remains on the volume.\n\n#### Procedure\n\nTo manually reclaim the PV as a cluster administrator:\n\n1. 1. Delete the PV by running the following command:\n\n```\n$ oc delete pv <pv_name>\n```\n\nThe associated storage asset in the external infrastructure, such as an AWS EBS, GCE PD, Azure Disk, or Cinder volume, still exists after the PV is deleted.\n\n1. 2. Clean up the data on the associated storage asset.\n2. 3. Delete the associated storage asset. Alternately, to reuse the same storage asset, create a new PV with the storage asset definition.\n\nThe reclaimed PV is now available for use by another PVC.\n\n### 3.2.8. Changing the reclaim policy of a persistent volume\n\nYou can change the reclaim policy of a persistent volume.\n\n#### Procedure1. 1. List the persistent volumes in your cluster:\n\n```\n$ oc get pv\n```\n\n### Example output\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>NAME</th>\n<th>CAPACITY</th>\n<th>ACCESSMODES</th>\n<th>RECLAIMPOLICY</th>\n<th>STATUS</th>\n</tr>\n<tr>\n<th>CLAIM</th>\n<th>STORAGECLASS</th>\n<th>REASON</th>\n<th>AGE</th>\n<th></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>pvc-b6efd8da-b7b5-11e6-9d58-0ed433a7dd94</td>\n<td>4Gi</td>\n<td>RWO</td>\n<td>Delete</td>\n<td>Bound</td>\n</tr>\n<tr>\n<td>default/claim1</td>\n<td>manual</td>\n<td>10s</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>pvc-b95650f8-b7b5-11e6-9d58-0ed433a7dd94</td>\n<td>4Gi</td>\n<td>RWO</td>\n<td>Delete</td>\n<td>Bound</td>\n</tr>\n<tr>\n<td>default/claim2</td>\n<td>manual</td>\n<td>6s</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>pvc-bb3ca71d-b7b5-11e6-9d58-0ed433a7dd94</td>\n<td>4Gi</td>\n<td>RWO</td>\n<td>Delete</td>\n<td>Bound</td>\n</tr>\n<tr>\n<td>default/claim3</td>\n<td>manual</td>\n<td>3s</td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\n1. 2. Choose one of your persistent volumes and change its reclaim policy:\n\n```\n$ oc patch pv <your-pv-name> -p '{\"spec\":{\"persistentVolumeReclaimPolicy\":\"Retain\"}}'\n```\n\n1. 3. Verify that your chosen persistent volume has the right policy:\n\n```\n$ oc get pv\n```\n\n### Example output\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>NAME</th>\n<th>CAPACITY</th>\n<th>ACCESSMODES</th>\n<th>RECLAIMPOLICY</th>\n<th>STATUS</th>\n</tr>\n<tr>\n<th>CLAIM</th>\n<th>STORAGECLASS</th>\n<th>REASON</th>\n<th>AGE</th>\n<th></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>pvc-b6efd8da-b7b5-11e6-9d58-0ed433a7dd94</td>\n<td>4Gi</td>\n<td>RWO</td>\n<td>Delete</td>\n<td>Bound</td>\n</tr>\n<tr>\n<td>default/claim1</td>\n<td>manual</td>\n<td>10s</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>pvc-b95650f8-b7b5-11e6-9d58-0ed433a7dd94</td>\n<td>4Gi</td>\n<td>RWO</td>\n<td>Delete</td>\n<td>Bound</td>\n</tr>\n<tr>\n<td>default/claim2</td>\n<td>manual</td>\n<td>6s</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>pvc-bb3ca71d-b7b5-11e6-9d58-0ed433a7dd94</td>\n<td>4Gi</td>\n<td>RWO</td>\n<td>Retain</td>\n<td>Bound</td>\n</tr>\n<tr>\n<td>default/claim3</td>\n<td>manual</td>\n<td>3s</td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\nIn the preceding output, the volume bound to claim **default/claim3** now has a **Retain** reclaim policy. The volume will not be automatically deleted when a user deletes claim **default/claim3**.\n\n## 3.3. PERSISTENT VOLUMES\n\nEach PV contains a **spec** and **status**, which is the specification and status of the volume, for example:\n\n### PersistentVolume object definition example\n\n```\napiVersion: v1\nkind: PersistentVolume\nmetadata:\n name: pv0001 1\nspec:\n capacity:\n storage: 5Gi 2\n accessModes:\n - ReadWriteOnce 3\n``````\npersistentVolumeReclaimPolicy: Retain 4 \n... \nstatus: \n...\n```\n\n1. 1 Name of the persistent volume.\n2. 2 The amount of storage available to the volume.\n3. 3 The access mode, defining the read-write and mount permissions.\n4. 4 The reclaim policy, indicating how the resource should be handled once it is released.\n\nYou can view the name of a PVC that is bound to a PV by running the following command:\n\n```\n$ oc get pv <pv_name> -o jsonpath='{.spec.claimRef.name}'\n```\n\n### 3.3.1. Types of PVs\n\nOpenShift Container Platform supports the following persistent volume plugins:\n\n- • AWS Elastic Block Store (EBS), which is installed by default.\n- • AWS Elastic File Store (EFS)\n- • Azure Disk\n- • Azure File\n- • Cinder\n- • Fibre Channel\n- • GCP Persistent Disk\n- • GCP Filestore\n- • IBM Power Virtual Server Block\n- • IBM Cloud® VPC Block\n- • HostPath\n- • iSCSI\n- • Local volume\n- • LVM Storage\n- • NFS\n- • OpenStack Manila\n- • Red Hat OpenShift Data Foundation\n- • CIFS/SMB- • VMware vSphere\n\n### 3.3.2. Capacity\n\nGenerally, a persistent volume (PV) has a specific storage capacity. This is set by using the **capacity** attribute of the PV.\n\nCurrently, storage capacity is the only resource that can be set or requested. Future attributes may include IOPS, throughput, and so on.\n\n### 3.3.3. Access modes\n\nA persistent volume can be mounted on a host in any way supported by the resource provider. Providers have different capabilities and each PV's access modes are set to the specific modes supported by that particular volume. For example, NFS can support multiple read-write clients, but a specific NFS PV might be exported on the server as read-only. Each PV gets its own set of access modes describing that specific PV's capabilities.\n\nClaims are matched to volumes with similar access modes. The only two matching criteria are access modes and size. A claim's access modes represent a request. Therefore, you might be granted more, but never less. For example, if a claim requests RWO, but the only volume available is an NFS PV (RWO+ROX+RWX), the claim would then match NFS because it supports RWO.\n\nDirect matches are always attempted first. The volume's modes must match or contain more modes than you requested. The size must be greater than or equal to what is expected. If two types of volumes, such as NFS and iSCSI, have the same set of access modes, either of them can match a claim with those modes. There is no ordering between types of volumes and no way to choose one type over another.\n\nAll volumes with the same modes are grouped, and then sorted by size, smallest to largest. The binder gets the group with matching modes and iterates over each, in size order, until one size matches.\n\n#### IMPORTANT\n\nVolume access modes describe volume capabilities. They are not enforced constraints. The storage provider is responsible for runtime errors resulting from invalid use of the resource. Errors in the provider show up at runtime as mount errors.\n\nFor example, NFS offers **ReadWriteOnce** access mode. If you want to use the volume's ROX capability, mark the claims as **ReadOnlyMany**.\n\niSCSI and Fibre Channel volumes do not currently have any fencing mechanisms. You must ensure the volumes are only used by one node at a time. In certain situations, such as draining a node, the volumes can be used simultaneously by two nodes. Before draining the node, delete the pods that use the volumes.\n\nThe following table lists the access modes:\n\n**Table 3.1. Access modes**\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Access Mode</th>\n<th>CLI abbreviation</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>ReadWriteOnce</td>\n<td><b>RWO</b></td>\n<td>The volume can be mounted as read-write by a single node.</td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Access Mode</th>\n<th>CLI abbreviation</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>ReadWriteOncePod</td>\n<td><b>RWOP</b></td>\n<td>The volume can be mounted as read-write by a single pod on a single node.</td>\n</tr>\n<tr>\n<td>ReadOnlyMany</td>\n<td><b>ROX</b></td>\n<td>The volume can be mounted as read-only by many nodes.</td>\n</tr>\n<tr>\n<td>ReadWriteMany</td>\n<td><b>RWX</b></td>\n<td>The volume can be mounted as read-write by many nodes.</td>\n</tr>\n</tbody>\n</table>\n\nTable 3.2. Supported access modes for persistent volumes\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Volume plugin</th>\n<th>ReadWriteOnce [1]</th>\n<th>ReadWriteOncePod</th>\n<th>ReadOnlyMany</th>\n<th>ReadWriteMany</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>AWS EBS [2]</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>AWS EFS</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n</tr>\n<tr>\n<td>Azure File</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n</tr>\n<tr>\n<td>Azure Disk</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>CIFS/SMB</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n</tr>\n<tr>\n<td>Cinder</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Fibre Channel</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■<sup>[3]</sup></td>\n</tr>\n<tr>\n<td>GCP Persistent Disk</td>\n<td>■<sup>[4]</sup></td>\n<td>■</td>\n<td>■</td>\n<td>■<sup>[4]</sup></td>\n</tr>\n<tr>\n<td>GCP Filestore</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n</tr>\n<tr>\n<td>HostPath</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>IBM Power Virtual Server Disk</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n</tr>\n<tr>\n<td>IBM Cloud® VPC Disk</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table><table border=\"1\">\n<thead>\n<tr>\n<th>Volume plugin</th>\n<th>ReadWriteOnce [1]</th>\n<th>ReadWriteOncePod</th>\n<th>ReadOnlyMany</th>\n<th>ReadWriteMany</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>iSCSI</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■<sup>[3]</sup></td>\n</tr>\n<tr>\n<td>Local volume</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>LVM Storage</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>NFS</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n</tr>\n<tr>\n<td>OpenStack Manila</td>\n<td></td>\n<td>■</td>\n<td></td>\n<td>■</td>\n</tr>\n<tr>\n<td>Red Hat OpenShift Data Foundation</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td>■</td>\n</tr>\n<tr>\n<td>VMware vSphere</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td>■<sup>[5]</sup></td>\n</tr>\n</tbody>\n</table>\n\n1. 1. ReadWriteOnce (RWO) volumes cannot be mounted on multiple nodes. If a node fails, the system does not allow the attached RWO volume to be mounted on a new node because it is already assigned to the failed node. If you encounter a multi-attach error message as a result, force delete the pod on a shutdown or crashed node to avoid data loss in critical workloads, such as when dynamic persistent volumes are attached.\n2. 2. Use a recreate deployment strategy for pods that rely on AWS EBS.\n3. 3. Only raw block volumes support the **ReadWriteMany** (RWX) access mode for Fibre Channel and iSCSI. For more information, see \"Block volume support\".\n4. 4. For GCP hyperdisk-balanced disks:\n - • The supported access modes are:\n - ◦ **ReadWriteOnce**\n - ◦ **ReadWriteMany**\n - • Cloning and snapshotting is disabled for disks with **ReadWriteMany** access mode enabled.\n - • You can attach a single hyperdisk-balanced disk volume in **ReadWriteMany** to a maximum of 8 instances.\n - • You can only resize a disk in **ReadWriteMany** if you detach the disk from all instances.\n - • [Additional limitations.](#)\n5. 5. If the underlying vSphere environment supports the vSAN file service, the vSphere Container"},"html":{"kind":"string","value":"<h1>OpenShift Container Platform 4.21</h1><h2>Storage</h2><p>Configuring and managing storage in OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Storage</h1><hr/><p>Configuring and managing storage in OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.</p><p>Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.</p><p>Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.</p><p>Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.</p><p>XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.</p><p>The OpenStack ® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.</p><p>All other trademarks are the property of their respective owners.</p><h2>Abstract</h2><p>This document provides instructions for configuring persistent volumes from various storage back ends and managing dynamic allocation from Pods.</p>\n<h1>Table of Contents</h1>\n\n<table>\n<tr>\n<td><b>CHAPTER 1. OPENSHIFT CONTAINER PLATFORM STORAGE OVERVIEW</b> .....</td>\n<td><b>11</b></td>\n</tr>\n<tr>\n<td> 1.1. GLOSSARY OF COMMON TERMS FOR OPENSHIFT CONTAINER PLATFORM STORAGE</td>\n<td>11</td>\n</tr>\n<tr>\n<td> 1.2. STORAGE TYPES</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.2.1. Ephemeral storage</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.2.2. Persistent storage</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.3. CONTAINER STORAGE INTERFACE (CSI)</td>\n<td>14</td>\n</tr>\n<tr>\n<td> 1.4. DYNAMIC PROVISIONING</td>\n<td>14</td>\n</tr>\n<tr>\n<td><b>CHAPTER 2. UNDERSTANDING EPHEMERAL STORAGE</b> .....</td>\n<td><b>15</b></td>\n</tr>\n<tr>\n<td> 2.1. OVERVIEW OF EPHEMERAL STORAGE</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2. TYPES OF EPHEMERAL STORAGE</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2.1. Root</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.2.2. Runtime</td>\n<td>15</td>\n</tr>\n<tr>\n<td> 2.3. EPHEMERAL STORAGE MANAGEMENT</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.3.1. Ephemeral storage limits and requests units</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.3.2. Ephemeral storage requests and limits example</td>\n<td>16</td>\n</tr>\n<tr>\n<td> 2.3.3. Ephemeral storage configuration effects pod scheduling and eviction</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.4. ADDITIONAL RESOURCES</td>\n<td>17</td>\n</tr>\n<tr>\n<td> 2.5. MONITORING EPHEMERAL STORAGE</td>\n<td>17</td>\n</tr>\n<tr>\n<td><b>CHAPTER 3. UNDERSTANDING PERSISTENT STORAGE</b> .....</td>\n<td><b>19</b></td>\n</tr>\n<tr>\n<td> 3.1. PERSISTENT STORAGE OVERVIEW</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2. LIFECYCLE OF A VOLUME AND CLAIM</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.1. Provision storage</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.2. Bind claims</td>\n<td>19</td>\n</tr>\n<tr>\n<td> 3.2.3. Use pods and claimed PVs</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 3.2.4. Storage Object in Use Protection</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 3.2.5. Release a persistent volume</td>\n<td>20</td>\n</tr>\n<tr>\n<td> 3.2.6. Reclaim policy for persistent volumes</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.2.7. Reclaiming a persistent volume manually</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.2.8. Changing the reclaim policy of a persistent volume</td>\n<td>21</td>\n</tr>\n<tr>\n<td> 3.3. PERSISTENT VOLUMES</td>\n<td>22</td>\n</tr>\n<tr>\n<td> 3.3.1. Types of PVs</td>\n<td>23</td>\n</tr>\n<tr>\n<td> 3.3.2. Capacity</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.3. Access modes</td>\n<td>24</td>\n</tr>\n<tr>\n<td> 3.3.4. Phase</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.3.4.1. Last phase transition time</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.3.4.2. Mount options</td>\n<td>27</td>\n</tr>\n<tr>\n<td> 3.4. PERSISTENT VOLUME CLAIMS</td>\n<td>28</td>\n</tr>\n<tr>\n<td> 3.4.1. Volume Attributes Classes</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 3.4.1.1. Limitations</td>\n<td>29</td>\n</tr>\n<tr>\n<td> 3.4.1.2. Defining Volume Attributes Classes</td>\n<td>30</td>\n</tr>\n<tr>\n<td> 3.4.1.3. Applying a Volume Attributes Class to a PVC</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.4.1.4. Deleting Volume Attributes Classes</td>\n<td>31</td>\n</tr>\n<tr>\n<td> 3.5. BLOCK VOLUME SUPPORT</td>\n<td>33</td>\n</tr>\n<tr>\n<td> 3.5.1. Block volume examples</td>\n<td>34</td>\n</tr>\n<tr>\n<td> 3.6. REDUCE POD TIMEOUTS BY USING FSGROUP</td>\n<td>36</td>\n</tr>\n<tr>\n<td> 3.6.1. Changing fsGroup at the namespace level</td>\n<td>37</td>\n</tr>\n<tr>\n<td> 3.6.2. Changing fsGroup at the pod level</td>\n<td>38</td>\n</tr>\n<tr>\n<td> 3.7. REDUCING POD TIMEOUTS USING SELINUXCHANGEPOLICY</td>\n<td>39</td>\n</tr>\n<tr>\n<td> 3.7.1. Testing the RWO and RWX and SELinux mount option feature</td>\n<td>40</td>\n</tr>\n</table>\n\n<table>\n<tr>\n<td>3.7.2. Opting out of the SELinux mount option default</td>\n<td>40</td>\n</tr>\n<tr>\n<td> 3.7.2.1. Changing seLinuxChangePolicy at the namespace level</td>\n<td>40</td>\n</tr>\n<tr>\n<td> 3.7.2.2. Changing seLinuxChangePolicy at the pod level</td>\n<td>41</td>\n</tr>\n<tr>\n<td><b>CHAPTER 4. CONFIGURING PERSISTENT STORAGE</b> .....</td>\n<td><b>43</b></td>\n</tr>\n<tr>\n<td>4.1. PERSISTENT STORAGE USING AWS ELASTIC BLOCK STORE</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.1.1. Creating the EBS storage class</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.1.2. Creating the persistent volume claim</td>\n<td>43</td>\n</tr>\n<tr>\n<td> 4.1.3. Volume format</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 4.1.4. Maximum number of EBS volumes on a node</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 4.1.5. Encrypting container persistent volumes on AWS with a KMS key</td>\n<td>44</td>\n</tr>\n<tr>\n<td> 4.1.6. Additional resources</td>\n<td>46</td>\n</tr>\n<tr>\n<td>4.2. PERSISTENT STORAGE USING AZURE</td>\n<td>46</td>\n</tr>\n<tr>\n<td> 4.2.1. Creating the Azure storage class</td>\n<td>46</td>\n</tr>\n<tr>\n<td> 4.2.2. Creating the persistent volume claim</td>\n<td>47</td>\n</tr>\n<tr>\n<td> 4.2.3. Volume format</td>\n<td>48</td>\n</tr>\n<tr>\n<td> 4.2.4. Machine sets that deploy machines with ultra disks using PVCs</td>\n<td>48</td>\n</tr>\n<tr>\n<td> 4.2.4.1. Creating machines with ultra disks by using machine sets</td>\n<td>48</td>\n</tr>\n<tr>\n<td> 4.2.4.2. Troubleshooting resources for machine sets that enable ultra disks</td>\n<td>51</td>\n</tr>\n<tr>\n<td> 4.2.4.2.1. Unable to mount a persistent volume claim backed by an ultra disk</td>\n<td>51</td>\n</tr>\n<tr>\n<td>4.3. PERSISTENT STORAGE USING AZURE FILE</td>\n<td>51</td>\n</tr>\n<tr>\n<td> 4.3.1. Create the Azure File share persistent volume claim</td>\n<td>52</td>\n</tr>\n<tr>\n<td> 4.3.2. Mount the Azure File share in a pod</td>\n<td>54</td>\n</tr>\n<tr>\n<td>4.4. PERSISTENT STORAGE USING CINDER</td>\n<td>54</td>\n</tr>\n<tr>\n<td> 4.4.1. Manual provisioning with Cinder</td>\n<td>55</td>\n</tr>\n<tr>\n<td> 4.4.1.1. Creating the persistent volume</td>\n<td>55</td>\n</tr>\n<tr>\n<td> 4.4.1.2. Persistent volume formatting</td>\n<td>56</td>\n</tr>\n<tr>\n<td> 4.4.1.3. Cinder volume security</td>\n<td>56</td>\n</tr>\n<tr>\n<td>4.5. PERSISTENT STORAGE USING FIBRE CHANNEL</td>\n<td>57</td>\n</tr>\n<tr>\n<td> 4.5.1. Provisioning</td>\n<td>58</td>\n</tr>\n<tr>\n<td> 4.5.1.1. Enforcing disk quotas</td>\n<td>58</td>\n</tr>\n<tr>\n<td> 4.5.1.2. Fibre Channel volume security</td>\n<td>59</td>\n</tr>\n<tr>\n<td>4.6. PERSISTENT STORAGE USING FLEXVOLUME</td>\n<td>59</td>\n</tr>\n<tr>\n<td> 4.6.1. About FlexVolume drivers</td>\n<td>59</td>\n</tr>\n<tr>\n<td> 4.6.2. FlexVolume driver example</td>\n<td>60</td>\n</tr>\n<tr>\n<td> 4.6.3. Installing FlexVolume drivers</td>\n<td>60</td>\n</tr>\n<tr>\n<td> 4.6.4. Consuming storage using FlexVolume drivers</td>\n<td>62</td>\n</tr>\n<tr>\n<td>4.7. PERSISTENT STORAGE USING GCE PERSISTENT DISK</td>\n<td>63</td>\n</tr>\n<tr>\n<td> 4.7.1. Creating the GCE storage class</td>\n<td>64</td>\n</tr>\n<tr>\n<td> 4.7.2. Creating the persistent volume claim</td>\n<td>64</td>\n</tr>\n<tr>\n<td> 4.7.3. Volume format</td>\n<td>64</td>\n</tr>\n<tr>\n<td>4.8. PERSISTENT STORAGE USING ISCSI</td>\n<td>64</td>\n</tr>\n<tr>\n<td> 4.8.1. Provisioning</td>\n<td>65</td>\n</tr>\n<tr>\n<td> 4.8.2. Enforce disk quotas</td>\n<td>65</td>\n</tr>\n<tr>\n<td> 4.8.3. iSCSI volume security</td>\n<td>65</td>\n</tr>\n<tr>\n<td> 4.8.3.1. Challenge Handshake Authentication Protocol (CHAP) configuration</td>\n<td>66</td>\n</tr>\n<tr>\n<td> 4.8.4. iSCSI multipathing</td>\n<td>66</td>\n</tr>\n<tr>\n<td> 4.8.5. iSCSI custom initiator IQN</td>\n<td>67</td>\n</tr>\n<tr>\n<td>4.9. PERSISTENT STORAGE USING NFS</td>\n<td>67</td>\n</tr>\n<tr>\n<td> 4.9.1. Provisioning</td>\n<td>68</td>\n</tr>\n<tr>\n<td> 4.9.2. Enforce disk quotas</td>\n<td>69</td>\n</tr>\n<tr>\n<td> 4.9.3. NFS volume security</td>\n<td>69</td>\n</tr>\n<tr>\n<td> 4.9.3.1. Group IDs</td>\n<td>70</td>\n</tr>\n</table>\n\n<table>\n<tr>\n<td>4.9.3.2. User IDs</td>\n<td>71</td>\n</tr>\n<tr>\n<td>4.9.3.3. SELinux</td>\n<td>72</td>\n</tr>\n<tr>\n<td>4.9.3.4. Export settings</td>\n<td>72</td>\n</tr>\n<tr>\n<td>4.9.4. Reclaiming resources</td>\n<td>73</td>\n</tr>\n<tr>\n<td>4.9.5. Additional configuration and troubleshooting</td>\n<td>74</td>\n</tr>\n<tr>\n<td>4.10. RED HAT OPENSHIFT DATA FOUNDATION</td>\n<td>74</td>\n</tr>\n<tr>\n<td>4.11. PERSISTENT STORAGE USING VMWARE VSPHERE VOLUMES</td>\n<td>74</td>\n</tr>\n<tr>\n<td>4.11.1. Dynamically provisioning VMware vSphere volumes</td>\n<td>75</td>\n</tr>\n<tr>\n<td>4.11.2. Prerequisites</td>\n<td>75</td>\n</tr>\n<tr>\n<td>4.11.2.1. Dynamically provisioning VMware vSphere volumes using the UI</td>\n<td>75</td>\n</tr>\n<tr>\n<td>4.11.2.2. Dynamically provisioning VMware vSphere volumes using the CLI</td>\n<td>76</td>\n</tr>\n<tr>\n<td>4.11.3. Statically provisioning VMware vSphere volumes</td>\n<td>77</td>\n</tr>\n<tr>\n<td>4.11.3.1. Formatting VMware vSphere volumes</td>\n<td>78</td>\n</tr>\n<tr>\n<td><b>CHAPTER 5. PERSISTENT STORAGE USING LOCAL STORAGE</b></td>\n<td><b>79</b></td>\n</tr>\n<tr>\n<td>5.1. LOCAL STORAGE OVERVIEW</td>\n<td>79</td>\n</tr>\n<tr>\n<td>5.1.1. Overview of HostPath Provisioner functionality</td>\n<td>79</td>\n</tr>\n<tr>\n<td>5.1.2. Overview of Local Storage Operator functionality</td>\n<td>79</td>\n</tr>\n<tr>\n<td>5.1.3. Overview of LVM Storage functionality</td>\n<td>80</td>\n</tr>\n<tr>\n<td>5.1.4. Comparison of LVM Storage, LSO, and HPP</td>\n<td>80</td>\n</tr>\n<tr>\n<td>5.1.4.1. Comparison of the support for storage types and filesystems</td>\n<td>80</td>\n</tr>\n<tr>\n<td>5.1.4.2. Comparison of the support for core functionalities</td>\n<td>80</td>\n</tr>\n<tr>\n<td>5.1.4.3. Comparison of performance and isolation capabilities</td>\n<td>82</td>\n</tr>\n<tr>\n<td>5.1.4.4. Comparison of the support for additional functionalities</td>\n<td>82</td>\n</tr>\n<tr>\n<td>5.2. PERSISTENT STORAGE USING LOCAL VOLUMES</td>\n<td>83</td>\n</tr>\n<tr>\n<td>5.2.1. Installing the Local Storage Operator</td>\n<td>83</td>\n</tr>\n<tr>\n<td>5.2.2. Provisioning local volumes by using the Local Storage Operator</td>\n<td>86</td>\n</tr>\n<tr>\n<td>5.2.3. Provisioning local volumes without the Local Storage Operator</td>\n<td>90</td>\n</tr>\n<tr>\n<td>5.2.4. Creating the local volume persistent volume claim</td>\n<td>92</td>\n</tr>\n<tr>\n<td>5.2.5. Attach the local claim</td>\n<td>92</td>\n</tr>\n<tr>\n<td>5.2.6. Automating discovery and provisioning for local storage devices</td>\n<td>93</td>\n</tr>\n<tr>\n<td>5.2.7. Using tolerations with Local Storage Operator pods</td>\n<td>97</td>\n</tr>\n<tr>\n<td>5.2.8. Local Storage Operator Metrics</td>\n<td>98</td>\n</tr>\n<tr>\n<td>5.2.9. Deleting the Local Storage Operator resources</td>\n<td>98</td>\n</tr>\n<tr>\n<td>5.2.9.1. Removing a local volume or local volume set</td>\n<td>98</td>\n</tr>\n<tr>\n<td>5.2.9.2. Uninstalling the Local Storage Operator</td>\n<td>100</td>\n</tr>\n<tr>\n<td>5.3. PERSISTENT STORAGE USING HOSTPATH</td>\n<td>101</td>\n</tr>\n<tr>\n<td>5.3.1. Overview</td>\n<td>101</td>\n</tr>\n<tr>\n<td>5.3.2. Statically provisioning hostPath volumes</td>\n<td>102</td>\n</tr>\n<tr>\n<td>5.3.3. Mounting the hostPath share in a privileged pod</td>\n<td>103</td>\n</tr>\n<tr>\n<td>5.4. PERSISTENT STORAGE USING LOGICAL VOLUME MANAGER STORAGE</td>\n<td>104</td>\n</tr>\n<tr>\n<td>5.4.1. Logical Volume Manager Storage installation</td>\n<td>104</td>\n</tr>\n<tr>\n<td>5.4.1.1. Prerequisites to install LVM Storage</td>\n<td>105</td>\n</tr>\n<tr>\n<td>5.4.1.2. Installing LVM Storage by using the CLI</td>\n<td>105</td>\n</tr>\n<tr>\n<td>5.4.1.3. Installing LVM Storage by using the web console</td>\n<td>107</td>\n</tr>\n<tr>\n<td>5.4.1.4. Installing LVM Storage in a disconnected environment</td>\n<td>108</td>\n</tr>\n<tr>\n<td>5.4.1.5. Installing LVM Storage by using RHACM</td>\n<td>110</td>\n</tr>\n<tr>\n<td>5.4.2. About the LVMCluster custom resource</td>\n<td>112</td>\n</tr>\n<tr>\n<td>5.4.2.1. Explanation of fields in the LVMCluster CR</td>\n<td>113</td>\n</tr>\n<tr>\n<td>5.4.2.2. Limitations to configure the size of the devices used in LVM Storage</td>\n<td>117</td>\n</tr>\n<tr>\n<td>5.4.2.3. About adding devices to a volume group</td>\n<td>119</td>\n</tr>\n<tr>\n<td>5.4.2.4. About removing devices and device classes from a volume group</td>\n<td>120</td>\n</tr>\n<tr>\n<td>5.4.2.4.1. Removing the device paths in the deviceSelector.paths field</td>\n<td>120</td>\n</tr>\n</table>\n\n<table>\n<tr>\n<td>5.4.2.4.2. Removing the deviceClass from the LVMCluster</td>\n<td>121</td>\n</tr>\n<tr>\n<td>5.4.2.5. Devices not supported by LVM Storage</td>\n<td>121</td>\n</tr>\n<tr>\n<td>5.4.3. Ways to create an LVMCluster custom resource</td>\n<td>122</td>\n</tr>\n<tr>\n<td>5.4.3.1. Reusing a volume group from the previous LVM Storage installation</td>\n<td>123</td>\n</tr>\n<tr>\n<td>5.4.3.2. Creating an LVMCluster CR by using the CLI</td>\n<td>124</td>\n</tr>\n<tr>\n<td>5.4.3.3. Creating an LVMCluster CR by using the web console</td>\n<td>127</td>\n</tr>\n<tr>\n<td>5.4.3.4. Creating an LVMCluster CR by using RHACM</td>\n<td>128</td>\n</tr>\n<tr>\n<td>5.4.4. Ways to delete an LVMCluster custom resource</td>\n<td>129</td>\n</tr>\n<tr>\n<td>5.4.4.1. Deleting an LVMCluster CR by using the CLI</td>\n<td>130</td>\n</tr>\n<tr>\n<td>5.4.4.2. Deleting an LVMCluster CR by using the web console</td>\n<td>130</td>\n</tr>\n<tr>\n<td>5.4.4.3. Deleting an LVMCluster CR by using RHACM</td>\n<td>131</td>\n</tr>\n<tr>\n<td>5.4.5. Provisioning storage</td>\n<td>134</td>\n</tr>\n<tr>\n<td>5.4.6. Ways to scale up the storage of clusters</td>\n<td>136</td>\n</tr>\n<tr>\n<td>5.4.6.1. Scaling up the storage of clusters by using the CLI</td>\n<td>136</td>\n</tr>\n<tr>\n<td>5.4.6.2. Scaling up the storage of clusters by using the web console</td>\n<td>138</td>\n</tr>\n<tr>\n<td>5.4.6.3. Scaling up the storage of clusters by using RHACM</td>\n<td>139</td>\n</tr>\n<tr>\n<td>5.4.7. Expanding a persistent volume claim</td>\n<td>141</td>\n</tr>\n<tr>\n<td>5.4.8. Deleting a persistent volume claim</td>\n<td>142</td>\n</tr>\n<tr>\n<td>5.4.9. About volume snapshots</td>\n<td>142</td>\n</tr>\n<tr>\n<td>5.4.9.1. Limitations for creating volume snapshots in multi-node topology</td>\n<td>143</td>\n</tr>\n<tr>\n<td>5.4.9.2. Creating volume snapshots</td>\n<td>143</td>\n</tr>\n<tr>\n<td>5.4.9.3. Restoring volume snapshots</td>\n<td>144</td>\n</tr>\n<tr>\n<td>5.4.9.4. Deleting volume snapshots</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.4.10. About volume clones</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.4.10.1. Limitations for creating volume clones in multi-node topology</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.4.10.2. Creating volume clones</td>\n<td>146</td>\n</tr>\n<tr>\n<td>5.4.10.3. Deleting volume clones</td>\n<td>148</td>\n</tr>\n<tr>\n<td>5.4.11. Updating LVM Storage</td>\n<td>148</td>\n</tr>\n<tr>\n<td>5.4.12. Monitoring LVM Storage</td>\n<td>150</td>\n</tr>\n<tr>\n<td>5.4.12.1. Metrics</td>\n<td>150</td>\n</tr>\n<tr>\n<td>5.4.12.2. Alerts</td>\n<td>150</td>\n</tr>\n<tr>\n<td>5.4.13. Uninstalling LVM Storage by using the CLI</td>\n<td>151</td>\n</tr>\n<tr>\n<td>5.4.14. Uninstalling LVM Storage by using the web console</td>\n<td>152</td>\n</tr>\n<tr>\n<td>5.4.15. Uninstalling LVM Storage installed using RHACM</td>\n<td>153</td>\n</tr>\n<tr>\n<td>5.4.16. Downloading log files and diagnostic information using must-gather</td>\n<td>155</td>\n</tr>\n<tr>\n<td>5.4.17. Troubleshooting persistent storage</td>\n<td>156</td>\n</tr>\n<tr>\n<td>5.4.17.1. Investigating a PVC stuck in the Pending state</td>\n<td>156</td>\n</tr>\n<tr>\n<td>5.4.17.2. Recovering from a missing storage class</td>\n<td>156</td>\n</tr>\n<tr>\n<td>5.4.17.3. Recovering from node failure</td>\n<td>158</td>\n</tr>\n<tr>\n<td>5.4.17.4. Recovering from disk failure</td>\n<td>158</td>\n</tr>\n<tr>\n<td>5.4.17.5. Performing a forced clean-up</td>\n<td>160</td>\n</tr>\n<tr>\n<td><b>CHAPTER 6. USING CONTAINER STORAGE INTERFACE (CSI)</b> .....</td>\n<td><b>162</b></td>\n</tr>\n<tr>\n<td>6.1. CONFIGURING CSI VOLUMES</td>\n<td>162</td>\n</tr>\n<tr>\n<td>6.1.1. CSI architecture</td>\n<td>162</td>\n</tr>\n<tr>\n<td>6.1.1.1. External CSI controllers</td>\n<td>162</td>\n</tr>\n<tr>\n<td>6.1.1.2. CSI driver daemon set</td>\n<td>163</td>\n</tr>\n<tr>\n<td>6.1.2. CSI drivers supported by OpenShift Container Platform</td>\n<td>163</td>\n</tr>\n<tr>\n<td>6.1.3. Dynamic provisioning</td>\n<td>166</td>\n</tr>\n<tr>\n<td>6.1.4. Example using the CSI driver</td>\n<td>167</td>\n</tr>\n<tr>\n<td>6.2. CSI INLINE EPHEMERAL VOLUMES</td>\n<td>167</td>\n</tr>\n<tr>\n<td>6.2.1. Overview of CSI inline ephemeral volumes</td>\n<td>167</td>\n</tr>\n<tr>\n<td>6.2.1.1. Support limitations</td>\n<td>168</td>\n</tr>\n</table>\n<hr/><table><tr><td>6.2.2. CSI Volume Admission plugin</td><td>168</td></tr><tr><td> 6.2.2.1. Overview</td><td>168</td></tr><tr><td> 6.2.2.2. Pod security profile enforcement</td><td>169</td></tr><tr><td> 6.2.2.3. Pod security profile warning</td><td>169</td></tr><tr><td> 6.2.2.4. Pod security profile audit</td><td>169</td></tr><tr><td> 6.2.2.5. Default behavior for the CSI Volume Admission plugin</td><td>170</td></tr><tr><td>6.2.3. Embedding a CSI inline ephemeral volume in the pod specification</td><td>170</td></tr><tr><td>6.2.4. Additional resources</td><td>171</td></tr><tr><td>6.3. CSI VOLUME SNAPSHOTS</td><td>171</td></tr><tr><td> 6.3.1. Overview of CSI volume snapshots</td><td>171</td></tr><tr><td> 6.3.2. CSI snapshot controller and sidecar</td><td>172</td></tr><tr><td> 6.3.2.1. External controller</td><td>172</td></tr><tr><td> 6.3.2.2. External sidecar</td><td>172</td></tr><tr><td> 6.3.3. About the CSI Snapshot Controller Operator</td><td>172</td></tr><tr><td> 6.3.3.1. Volume snapshot CRDs</td><td>172</td></tr><tr><td> 6.3.4. Volume snapshot provisioning</td><td>173</td></tr><tr><td> 6.3.4.1. Dynamic provisioning</td><td>173</td></tr><tr><td> 6.3.4.2. Manual provisioning</td><td>173</td></tr><tr><td> 6.3.5. Creating a volume snapshot</td><td>173</td></tr><tr><td> 6.3.6. Deleting a volume snapshot</td><td>176</td></tr><tr><td> 6.3.7. Restoring a volume snapshot</td><td>177</td></tr><tr><td> 6.3.8. Changing the maximum number of snapshots for vSphere</td><td>179</td></tr><tr><td> 6.3.9. Additional resources</td><td>180</td></tr><tr><td>6.4. CSI VOLUME GROUP SNAPSHOTS</td><td>180</td></tr><tr><td> 6.4.1. Overview of CSI volume group snapshots</td><td>181</td></tr><tr><td> 6.4.2. CSI volume group snapshots limitations</td><td>181</td></tr><tr><td> 6.4.3. Creating a volume group snapshot class</td><td>182</td></tr><tr><td> 6.4.4. Creating a volume group snapshot</td><td>182</td></tr><tr><td> 6.4.5. Restoring a volume group snapshot</td><td>185</td></tr><tr><td> 6.4.6. Additional resources</td><td>186</td></tr><tr><td>6.5. CSI VOLUME CLONING</td><td>186</td></tr><tr><td> 6.5.1. Overview of CSI volume cloning</td><td>186</td></tr><tr><td> 6.5.1.1. Support limitations</td><td>187</td></tr><tr><td> 6.5.2. Provisioning a CSI volume clone</td><td>187</td></tr><tr><td>6.6. VOLUME POPULATORS</td><td>188</td></tr><tr><td> 6.6.1. Volume populators overview</td><td>188</td></tr><tr><td> 6.6.2. Creating volume populators</td><td>189</td></tr><tr><td> 6.6.2.1. Creating CRDs for volume populators</td><td>189</td></tr><tr><td> 6.6.2.2. Creating prepopulated volumes using volume populators</td><td>193</td></tr><tr><td> 6.6.2.3. Uninstalling volume populators</td><td>195</td></tr><tr><td>6.7. MANAGING THE DEFAULT STORAGE CLASS</td><td>195</td></tr><tr><td> 6.7.1. Overview</td><td>195</td></tr><tr><td> 6.7.2. Managing the default storage class using the web console</td><td>196</td></tr><tr><td> 6.7.3. Managing the default storage class using the CLI</td><td>197</td></tr><tr><td> 6.7.4. Absent or multiple default storage classes</td><td>197</td></tr><tr><td> 6.7.4.1. Multiple default storage classes</td><td>197</td></tr><tr><td> 6.7.4.2. Absent default storage class</td><td>197</td></tr><tr><td> 6.7.5. Changing the default storage class</td><td>198</td></tr><tr><td>6.8. CSI AUTOMATIC MIGRATION</td><td>199</td></tr><tr><td> 6.8.1. Overview</td><td>199</td></tr><tr><td> 6.8.2. Storage class implications</td><td>200</td></tr><tr><td>6.9. AWS ELASTIC BLOCK STORE CSI DRIVER OPERATOR</td><td>200</td></tr><tr><td> 6.9.1. Overview</td><td>200</td></tr></table><hr/><table><tr><td>6.9.2. About CSI</td><td>200</td></tr><tr><td>6.9.3. User-managed encryption</td><td>201</td></tr><tr><td>6.10. AWS ELASTIC FILE SERVICE CSI DRIVER OPERATOR</td><td>201</td></tr><tr><td>6.10.1. Overview</td><td>201</td></tr><tr><td>6.10.2. About CSI</td><td>202</td></tr><tr><td>6.10.3. Setting up the AWS EFS CSI Driver Operator</td><td>202</td></tr><tr><td>6.10.3.1. Obtaining a role Amazon Resource Name for Security Token Service</td><td>202</td></tr><tr><td>6.10.3.2. Installing the AWS EFS CSI Driver Operator</td><td>204</td></tr><tr><td>6.10.3.3. Installing the AWS EFS CSI Driver</td><td>205</td></tr><tr><td>6.10.4. Creating the AWS EFS storage class</td><td>205</td></tr><tr><td>6.10.4.1. Creating the AWS EFS storage class using the console</td><td>206</td></tr><tr><td>6.10.4.2. Creating the AWS EFS storage class using the CLI</td><td>206</td></tr><tr><td>6.10.5. AWS EFS CSI cross account support</td><td>207</td></tr><tr><td>6.10.6. One Zone file systems</td><td>215</td></tr><tr><td>6.10.6.1. One Zone file systems overview</td><td>215</td></tr><tr><td>6.10.6.2. Setting up One Zone file systems with STS</td><td>216</td></tr><tr><td>6.10.7. Dynamic provisioning for Amazon Elastic File Storage</td><td>217</td></tr><tr><td>6.10.8. Creating static PVs with Amazon Elastic File Storage</td><td>218</td></tr><tr><td>6.10.9. Amazon Elastic File Storage security</td><td>219</td></tr><tr><td>6.10.10. AWS EFS storage CSI usage metrics</td><td>219</td></tr><tr><td>6.10.10.1. Usage metrics overview</td><td>220</td></tr><tr><td>6.10.10.2. Enabling usage metrics using the web console</td><td>220</td></tr><tr><td>6.10.10.3. Enabling usage metrics using the CLI</td><td>221</td></tr><tr><td>6.10.11. Amazon Elastic File Storage troubleshooting</td><td>221</td></tr><tr><td>6.10.12. Uninstalling the AWS EFS CSI Driver Operator</td><td>222</td></tr><tr><td>6.10.13. Additional resources</td><td>223</td></tr><tr><td>6.11. AZURE DISK CSI DRIVER OPERATOR</td><td>224</td></tr><tr><td>6.11.1. Overview</td><td>224</td></tr><tr><td>6.11.2. About CSI</td><td>224</td></tr><tr><td>6.11.3. Creating a storage class with storage account type</td><td>224</td></tr><tr><td>6.11.4. Performance plus for Azure Disk</td><td>225</td></tr><tr><td>6.11.4.1. Overview</td><td>225</td></tr><tr><td>6.11.4.2. Limitations</td><td>226</td></tr><tr><td>6.11.4.3. Creating a storage class to use performance plus enhanced disks</td><td>226</td></tr><tr><td>6.11.4.4. Enabling performance plus by snapshot or cloning</td><td>227</td></tr><tr><td>6.11.5. User-managed encryption</td><td>228</td></tr><tr><td>6.11.6. Machine sets that deploy machines with ultra disks using PVCs</td><td>228</td></tr><tr><td>6.11.6.1. Creating machines with ultra disks by using machine sets</td><td>229</td></tr><tr><td>6.11.6.2. Troubleshooting resources for machine sets that enable ultra disks</td><td>232</td></tr><tr><td>6.11.6.2.1. Unable to mount a persistent volume claim backed by an ultra disk</td><td>232</td></tr><tr><td>6.11.7. Additional resources</td><td>232</td></tr><tr><td>6.12. AZURE FILE CSI DRIVER OPERATOR</td><td>232</td></tr><tr><td>6.12.1. Overview</td><td>232</td></tr><tr><td>6.12.2. About CSI</td><td>233</td></tr><tr><td>6.12.3. NFS support</td><td>233</td></tr><tr><td>6.12.4. Azure File cross-subscription support</td><td>234</td></tr><tr><td>6.12.4.1. Dynamic provisioning across subscriptions for Azure File</td><td>234</td></tr><tr><td>6.12.4.2. Static provisioning across subscriptions for Azure File by creating a PV and PVC:</td><td>236</td></tr><tr><td>6.12.5. Static provisioning for Azure File</td><td>238</td></tr><tr><td>6.13. AZURE STACK HUB CSI DRIVER OPERATOR</td><td>241</td></tr><tr><td>6.13.1. Overview</td><td>241</td></tr><tr><td>6.13.2. About CSI</td><td>242</td></tr><tr><td>6.13.3. Additional resources</td><td>242</td></tr></table>\n<hr/>\n<table>\n<tr>\n<td>6.14. GCP PD CSI DRIVER OPERATOR</td>\n<td>242</td>\n</tr>\n<tr>\n<td> 6.14.1. Overview</td>\n<td>242</td>\n</tr>\n<tr>\n<td> 6.14.2. About CSI</td>\n<td>243</td>\n</tr>\n<tr>\n<td> 6.14.3. Reducing permissions while using the GCP PD CSI Driver Operator</td>\n<td>243</td>\n</tr>\n<tr>\n<td> 6.14.4. GCP PD CSI driver storage class parameters</td>\n<td>244</td>\n</tr>\n<tr>\n<td> 6.14.5. C3 instance type for bare metal and N4 machine series</td>\n<td>244</td>\n</tr>\n<tr>\n<td> 6.14.5.1. C3 and N4 instance type limitations</td>\n<td>244</td>\n</tr>\n<tr>\n<td> 6.14.5.2. Storage pools for hyperdisk-balanced disks overview</td>\n<td>245</td>\n</tr>\n<tr>\n<td> 6.14.5.3. Setting up hyperdisk-balanced disks</td>\n<td>245</td>\n</tr>\n<tr>\n<td> 6.14.5.4. Additional resources</td>\n<td>250</td>\n</tr>\n<tr>\n<td> 6.14.6. Creating a custom-encrypted persistent volume</td>\n<td>250</td>\n</tr>\n<tr>\n<td> 6.14.7. User-managed encryption</td>\n<td>252</td>\n</tr>\n<tr>\n<td> 6.14.8. Additional resources</td>\n<td>252</td>\n</tr>\n<tr>\n<td>6.15. GOOGLE CLOUD FILESTORE CSI DRIVER OPERATOR</td>\n<td>252</td>\n</tr>\n<tr>\n<td> 6.15.1. Overview</td>\n<td>252</td>\n</tr>\n<tr>\n<td> 6.15.2. About CSI</td>\n<td>253</td>\n</tr>\n<tr>\n<td> 6.15.3. Installing the Google Cloud Filestore CSI Driver Operator</td>\n<td>253</td>\n</tr>\n<tr>\n<td> 6.15.3.1. Preparing to install the Google Cloud Filestore CSI Driver Operator with Workload Identity</td>\n<td>253</td>\n</tr>\n<tr>\n<td> 6.15.3.2. Installing the Google Cloud Filestore CSI Driver Operator</td>\n<td>255</td>\n</tr>\n<tr>\n<td> 6.15.4. Creating a storage class for GCP Filestore Storage</td>\n<td>257</td>\n</tr>\n<tr>\n<td> 6.15.5. NFS export options</td>\n<td>258</td>\n</tr>\n<tr>\n<td> 6.15.6. Destroying clusters and GCP Filestore</td>\n<td>259</td>\n</tr>\n<tr>\n<td> 6.15.7. Additional resources</td>\n<td>260</td>\n</tr>\n<tr>\n<td>6.16. IBM CLOUD VPC BLOCK CSI DRIVER OPERATOR</td>\n<td>260</td>\n</tr>\n<tr>\n<td> 6.16.1. Overview</td>\n<td>260</td>\n</tr>\n<tr>\n<td> 6.16.2. About CSI</td>\n<td>260</td>\n</tr>\n<tr>\n<td> 6.16.3. User-managed encryption</td>\n<td>261</td>\n</tr>\n<tr>\n<td>6.17. IBM POWER VIRTUAL SERVER BLOCK CSI DRIVER OPERATOR</td>\n<td>261</td>\n</tr>\n<tr>\n<td> 6.17.1. Introduction</td>\n<td>261</td>\n</tr>\n<tr>\n<td> 6.17.2. Overview</td>\n<td>261</td>\n</tr>\n<tr>\n<td> 6.17.3. About CSI</td>\n<td>262</td>\n</tr>\n<tr>\n<td>6.18. OPENSTACK CINDER CSI DRIVER OPERATOR</td>\n<td>262</td>\n</tr>\n<tr>\n<td> 6.18.1. Overview</td>\n<td>262</td>\n</tr>\n<tr>\n<td> 6.18.2. About CSI</td>\n<td>262</td>\n</tr>\n<tr>\n<td> 6.18.3. Making OpenStack Cinder CSI the default storage class</td>\n<td>262</td>\n</tr>\n<tr>\n<td>6.19. OPENSTACK MANILA CSI DRIVER OPERATOR</td>\n<td>264</td>\n</tr>\n<tr>\n<td> 6.19.1. Overview</td>\n<td>264</td>\n</tr>\n<tr>\n<td> 6.19.2. About CSI</td>\n<td>264</td>\n</tr>\n<tr>\n<td> 6.19.3. Manila CSI Driver Operator limitations</td>\n<td>265</td>\n</tr>\n<tr>\n<td> 6.19.4. Dynamically provisioning Manila CSI volumes</td>\n<td>265</td>\n</tr>\n<tr>\n<td> 6.19.5. Customizing Manila share access rules</td>\n<td>267</td>\n</tr>\n<tr>\n<td>6.20. SECRETS STORE CONTAINER STORAGE INTERFACE DRIVER OPERATOR</td>\n<td>269</td>\n</tr>\n<tr>\n<td> 6.20.1. Overview</td>\n<td>269</td>\n</tr>\n<tr>\n<td> 6.20.1.1. Secrets store providers</td>\n<td>270</td>\n</tr>\n<tr>\n<td> 6.20.2. About CSI</td>\n<td>270</td>\n</tr>\n<tr>\n<td> 6.20.3. Support for disconnected environments</td>\n<td>270</td>\n</tr>\n<tr>\n<td> 6.20.4. Support for network policies</td>\n<td>270</td>\n</tr>\n<tr>\n<td> 6.20.5. Installing the Secrets Store CSI driver</td>\n<td>271</td>\n</tr>\n<tr>\n<td> 6.20.6. Uninstalling the Secrets Store CSI Driver Operator</td>\n<td>272</td>\n</tr>\n<tr>\n<td> 6.20.7. Additional resources</td>\n<td>273</td>\n</tr>\n<tr>\n<td>6.21. CIFS/SMB CSI DRIVER OPERATOR</td>\n<td>273</td>\n</tr>\n<tr>\n<td> 6.21.1. About CSI</td>\n<td>273</td>\n</tr>\n<tr>\n<td> 6.21.2. Limitations</td>\n<td>273</td>\n</tr>\n</table>\n\n<table>\n<tbody>\n<tr>\n<td>6.21.3. Installing the CIFS/SMB CSI Driver Operator</td>\n<td>274</td>\n</tr>\n<tr>\n<td>6.21.4. Installing the CIFS/SMB CSI Driver</td>\n<td>274</td>\n</tr>\n<tr>\n<td>6.21.5. Dynamic provisioning</td>\n<td>275</td>\n</tr>\n<tr>\n<td>6.21.6. Static provisioning</td>\n<td>277</td>\n</tr>\n<tr>\n<td>6.21.7. Additional resources</td>\n<td>282</td>\n</tr>\n<tr>\n<td><b>6.22. VMWARE VSPHERE CSI DRIVER OPERATOR</b></td>\n<td><b>282</b></td>\n</tr>\n<tr>\n<td>6.22.1. Overview</td>\n<td>282</td>\n</tr>\n<tr>\n<td>6.22.2. About CSI</td>\n<td>282</td>\n</tr>\n<tr>\n<td>6.22.3. vSphere CSI limitations</td>\n<td>283</td>\n</tr>\n<tr>\n<td>6.22.4. vSphere storage policy</td>\n<td>283</td>\n</tr>\n<tr>\n<td>6.22.5. ReadWriteMany vSphere volume support</td>\n<td>283</td>\n</tr>\n<tr>\n<td>6.22.6. VMware vSphere CSI Driver Operator requirements</td>\n<td>284</td>\n</tr>\n<tr>\n<td>6.22.7. Removing a third-party vSphere CSI Driver Operator</td>\n<td>284</td>\n</tr>\n<tr>\n<td>6.22.8. vSphere persistent disks encryption</td>\n<td>285</td>\n</tr>\n<tr>\n<td>6.22.8.1. Using datastore URL</td>\n<td>286</td>\n</tr>\n<tr>\n<td>6.22.8.2. Using tag-based placement</td>\n<td>286</td>\n</tr>\n<tr>\n<td>6.22.9. Multiple vCenter support for vSphere CSI</td>\n<td>287</td>\n</tr>\n<tr>\n<td>6.22.9.1. Configuring multiple vCenters during installation</td>\n<td>287</td>\n</tr>\n<tr>\n<td>6.22.10. vSphere CSI topology overview</td>\n<td>287</td>\n</tr>\n<tr>\n<td>6.22.10.1. vSphere CSI topology requirements</td>\n<td>288</td>\n</tr>\n<tr>\n<td>6.22.10.2. Creating vSphere storage topology during installation</td>\n<td>288</td>\n</tr>\n<tr>\n<td>6.22.10.2.1. Procedure</td>\n<td>289</td>\n</tr>\n<tr>\n<td>6.22.10.3. Creating vSphere storage topology postinstallation</td>\n<td>289</td>\n</tr>\n<tr>\n<td>6.22.10.3.1. Procedure</td>\n<td>289</td>\n</tr>\n<tr>\n<td>6.22.10.4. Creating vSphere storage topology without an infra topology</td>\n<td>290</td>\n</tr>\n<tr>\n<td>6.22.10.4.1. Procedure</td>\n<td>291</td>\n</tr>\n<tr>\n<td>6.22.10.5. Results</td>\n<td>294</td>\n</tr>\n<tr>\n<td>6.22.11. Changing the maximum number of snapshots for vSphere</td>\n<td>294</td>\n</tr>\n<tr>\n<td>6.22.12. Migrating CNS volumes between datastores for vSphere</td>\n<td>296</td>\n</tr>\n<tr>\n<td>6.22.13. Disabling and enabling storage on vSphere</td>\n<td>297</td>\n</tr>\n<tr>\n<td>6.22.13.1. Consequences of disabling and enabling storage on vSphere</td>\n<td>297</td>\n</tr>\n<tr>\n<td>6.22.13.2. Disabling and enabling storage on vSphere</td>\n<td>297</td>\n</tr>\n<tr>\n<td>6.22.14. Adding bare-metal nodes</td>\n<td>298</td>\n</tr>\n<tr>\n<td>6.22.15. Increasing maximum volumes per node for vSphere</td>\n<td>299</td>\n</tr>\n<tr>\n<td>6.22.15.1. Increasing the maximum allowable volumes per node for vSphere</td>\n<td>299</td>\n</tr>\n<tr>\n<td>6.22.16. Additional resources</td>\n<td>300</td>\n</tr>\n<tr>\n<td><b>CHAPTER 7. GENERIC EPHEMERAL VOLUMES</b> .....</td>\n<td><b>302</b></td>\n</tr>\n<tr>\n<td>7.1. OVERVIEW OF GENERIC EPHEMERAL VOLUMES</td>\n<td>302</td>\n</tr>\n<tr>\n<td>7.2. LIFECYCLE AND PERSISTENT VOLUME CLAIMS</td>\n<td>302</td>\n</tr>\n<tr>\n<td>7.3. SECURITY</td>\n<td>303</td>\n</tr>\n<tr>\n<td>7.4. PERSISTENT VOLUME CLAIM NAMING</td>\n<td>303</td>\n</tr>\n<tr>\n<td>7.5. CREATING GENERIC EPHEMERAL VOLUMES</td>\n<td>303</td>\n</tr>\n<tr>\n<td><b>CHAPTER 8. EXPANDING PERSISTENT VOLUMES</b> .....</td>\n<td><b>305</b></td>\n</tr>\n<tr>\n<td>8.1. ENABLING VOLUME EXPANSION SUPPORT</td>\n<td>305</td>\n</tr>\n<tr>\n<td>8.2. EXPANDING CSI VOLUMES</td>\n<td>305</td>\n</tr>\n<tr>\n<td>8.3. EXPANDING FLEXVOLUME WITH A SUPPORTED DRIVER</td>\n<td>306</td>\n</tr>\n<tr>\n<td>8.4. EXPANDING LOCAL VOLUMES</td>\n<td>306</td>\n</tr>\n<tr>\n<td>8.5. EXPANDING PERSISTENT VOLUME CLAIMS (PVCS) WITH A FILE SYSTEM</td>\n<td>307</td>\n</tr>\n<tr>\n<td>8.6. RECOVERING FROM FAILURE WHEN EXPANDING VOLUMES</td>\n<td>308</td>\n</tr>\n<tr>\n<td>8.7. VIEWING THE STATUS OF VOLUME RESIZE</td>\n<td>308</td>\n</tr>\n<tr>\n<td>8.8. ADDITIONAL RESOURCES</td>\n<td>308</td>\n</tr>\n</tbody>\n</table>\n<hr/><table><tr><td><b>CHAPTER 9. DYNAMIC PROVISIONING</b> .....</td><td><b>309</b></td></tr><tr><td> 9.1. ABOUT DYNAMIC PROVISIONING</td><td>309</td></tr><tr><td> 9.2. AVAILABLE DYNAMIC PROVISIONING PLUGINS</td><td>309</td></tr><tr><td> 9.3. DEFINING A STORAGE CLASS</td><td>310</td></tr><tr><td> 9.3.1. Basic StorageClass object definition</td><td>310</td></tr><tr><td> 9.3.2. Storage class annotations</td><td>311</td></tr><tr><td> 9.3.3. RHOSP Cinder object definition</td><td>312</td></tr><tr><td> 9.3.4. RHOSP Manila Container Storage Interface (CSI) object definition</td><td>312</td></tr><tr><td> 9.3.5. AWS Elastic Block Store (EBS) object definition</td><td>312</td></tr><tr><td> 9.3.6. Azure Disk object definition</td><td>313</td></tr><tr><td> 9.3.7. Azure File object definition</td><td>314</td></tr><tr><td> 9.3.7.1. Considerations when using Azure File</td><td>315</td></tr><tr><td> 9.3.8. GCE PersistentDisk (gcePD) object definition</td><td>316</td></tr><tr><td> 9.3.9. VMware vSphere object definition</td><td>316</td></tr><tr><td> 9.4. CHANGING THE DEFAULT STORAGE CLASS</td><td>317</td></tr><tr><td><b>CHAPTER 10. DETACH VOLUMES AFTER NON-GRACEFUL NODE SHUTDOWN</b> .....</td><td><b>319</b></td></tr><tr><td> 10.1. OVERVIEW</td><td>319</td></tr><tr><td> 10.2. ADDING AN OUT-OF-SERVICE Taint MANUALLY FOR AUTOMATIC VOLUME DETACHMENT</td><td>319</td></tr></table><h1>CHAPTER 1. OPENSHIFT CONTAINER PLATFORM STORAGE OVERVIEW</h1><p>OpenShift Container Platform supports multiple types of storage, both for on-premise and cloud providers. You can manage container storage for persistent and non-persistent data in an OpenShift Container Platform cluster.</p><h2>1.1. GLOSSARY OF COMMON TERMS FOR OPENSHIFT CONTAINER PLATFORM STORAGE</h2><p>This glossary defines common terms that are used in the storage content.</p><h3>Access modes</h3><p>Volume access modes describe volume capabilities. You can use access modes to match persistent volume claim (PVC) and persistent volume (PV). The following are the examples of access modes:</p><ul><li>• ReadWriteOnce (RWO)</li><li>• ReadOnlyMany (ROX)</li><li>• ReadWriteMany (RWX)</li><li>• ReadWriteOncePod (RWOP)</li></ul><h3>Cinder</h3><p>The Block Storage service for Red Hat OpenStack Platform (RHOSP) which manages the administration, security, and scheduling of all volumes.</p><h3>Config map</h3><p>A config map provides a way to inject configuration data into pods. You can reference the data stored in a config map in a volume of type <b>ConfigMap</b>. Applications running in a pod can use this data.</p><h3>Container Storage Interface (CSI)</h3><p>An API specification for the management of container storage across different container orchestration (CO) systems.</p><h3>Dynamic Provisioning</h3><p>The framework allows you to create storage volumes on-demand, eliminating the need for cluster administrators to pre-provision persistent storage.</p><h3>Ephemeral storage</h3><p>Pods and containers can require temporary or transient local storage for their operation. The lifetime of this ephemeral storage does not extend beyond the life of the individual pod, and this ephemeral storage cannot be shared across pods.</p><h3>Fiber channel</h3><p>A networking technology that is used to transfer data among data centers, computer servers, switches and storage.</p><h3>FlexVolume</h3><p>FlexVolume is an out-of-tree plugin interface that uses an exec-based model to interface with storage drivers. You must install the FlexVolume driver binaries in a pre-defined volume plugin path on each node and in some cases the control plane nodes.</p><h3>fsGroup</h3><p>The fsGroup defines a file system group ID of a pod.</p><h3>iSCSI</h3><p>Internet Small Computer Systems Interface (iSCSI) is an Internet Protocol-based storage networking standard for linking data storage facilities. An iSCSI volume allows an existing iSCSI (SCSI over IP) volume to be mounted into your Pod.</p><h3>hostPath</h3><p>A hostPath volume in an OpenShift Container Platform cluster mounts a file or directory from the host node's filesystem into your pod.</p><h3>KMS key</h3><p>The Key Management Service (KMS) helps you achieve the required level of encryption of your data across different services. You can use the KMS key to encrypt, decrypt, and re-encrypt data.</p><h3>Local volumes</h3><p>A local volume represents a mounted local storage device such as a disk, partition or directory.</p><h3>Nested mount points</h3><p>A nested mount point is a mount point that attempts to use a mount point created by a previous volume.</p><h2>Example pod definition with nested mount points</h2><pre>kind: Pod\napiVersion: v1\nmetadata:\n name: webapp\n labels:\n name: webapp\nspec:\n containers:\n - name: webapp\n image: nginx\n ports:\n - containerPort: 80\n name: \"http-server\"\n volumeMounts:\n - mountPath: /mnt/web\n name: web\n - mountPath: /mnt/web/redis <b>1</b>\n name: redis\n volumes:\n - name: redis\n persistentVolumeClaim:\n claimName: \"redis\"\n - name: web\n persistentVolumeClaim:\n claimName: \"web\"</pre><p><b>1</b> Nested mount point</p><p>Do <i>not</i> use nested mount points because OpenShift Container Platform does not guarantee the order in which mount points are created. Such usage is prone to race conditions and undefined behavior.</p><h2>NFS</h2><p>A Network File System (NFS) that allows remote hosts to mount file systems over a network and interact with those file systems as though they are mounted locally. This enables system administrators to consolidate resources onto centralized servers on the network.</p><h2>OpenShift Data Foundation</h2><p>A provider of agnostic persistent storage for OpenShift Container Platform supporting file, block, and object storage, either in-house or in hybrid clouds</p><h3>Persistent storage</h3><p>Pods and containers can require permanent storage for their operation. OpenShift Container Platform uses the Kubernetes persistent volume (PV) framework to allow cluster administrators to provision persistent storage for a cluster. Developers can use PVC to request PV resources without having specific knowledge of the underlying storage infrastructure.</p><h3>Persistent volumes (PV)</h3><p>OpenShift Container Platform uses the Kubernetes persistent volume (PV) framework to allow cluster administrators to provision persistent storage for a cluster. Developers can use PVC to request PV resources without having specific knowledge of the underlying storage infrastructure.</p><h3>Persistent volume claims (PVCs)</h3><p>You can use a PVC to mount a PersistentVolume into a Pod. You can access the storage without knowing the details of the cloud environment.</p><h3>Pod</h3><p>One or more containers with shared resources, such as volume and IP addresses, running in your OpenShift Container Platform cluster. A pod is the smallest compute unit defined, deployed, and managed.</p><h3>Reclaim policy</h3><p>A policy that tells the cluster what to do with the volume after it is released. A volume's reclaim policy can be <b>Retain</b>, <b>Recycle</b>, or <b>Delete</b>.</p><h3>Role-based access control (RBAC)</h3><p>Role-based access control (RBAC) is a method of regulating access to computer or network resources based on the roles of individual users within your organization.</p><h3>Stateless applications</h3><p>A stateless application is an application program that does not save client data generated in one session for use in the next session with that client.</p><h3>Stateful applications</h3><p>A stateful application is an application program that saves data to persistent disk storage. A server, client, and applications can use a persistent disk storage. You can use the <b>Statefulset</b> object in OpenShift Container Platform to manage the deployment and scaling of a set of Pods, and provides guarantee about the ordering and uniqueness of these Pods.</p><h3>Static provisioning</h3><p>A cluster administrator creates a number of PVs. PVs contain the details of storage. PVs exist in the Kubernetes API and are available for consumption.</p><h3>Storage</h3><p>OpenShift Container Platform supports many types of storage, both for on-premise and cloud providers. You can manage container storage for persistent and non-persistent data in an OpenShift Container Platform cluster.</p><h3>Storage class</h3><p>A storage class provides a way for administrators to describe the classes of storage they offer. Different classes might map to quality of service levels, backup policies, arbitrary policies determined by the cluster administrators.</p><h3><b>VMware vSphere's Virtual Machine Disk (VMDK) volumes</b></h3><p>Virtual Machine Disk (VMDK) is a file format that describes containers for virtual hard disk drives that is used in virtual machines.</p><h2><b>1.2. STORAGE TYPES</b></h2><p>OpenShift Container Platform storage is broadly classified into two categories, namely ephemeral storage and persistent storage.</p><h3><b>1.2.1. Ephemeral storage</b></h3><p>Pods and containers are ephemeral or transient in nature and designed for stateless applications. Ephemeral storage allows administrators and developers to better manage the local storage for some of their operations. For more information about ephemeral storage overview, types, and management, see <a href=\"#\">Understanding ephemeral storage</a>.</p><h3><b>1.2.2. Persistent storage</b></h3><p>Stateful applications deployed in containers require persistent storage. OpenShift Container Platform uses a pre-provisioned storage framework called persistent volumes (PV) to allow cluster administrators to provision persistent storage. The data inside these volumes can exist beyond the lifecycle of an individual pod. Developers can use persistent volume claims (PVCs) to request storage requirements. For more information about persistent storage overview, configuration, and lifecycle, see <a href=\"#\">Understanding persistent storage</a>.</p><h2><b>1.3. CONTAINER STORAGE INTERFACE (CSI)</b></h2><p>CSI is an API specification for the management of container storage across different container orchestration (CO) systems. You can manage the storage volumes within the container native environments, without having specific knowledge of the underlying storage infrastructure. With the CSI, storage works uniformly across different container orchestration systems, regardless of the storage vendors you are using. For more information about CSI, see <a href=\"#\">Using Container Storage Interface (CSI)</a>.</p><h2><b>1.4. DYNAMIC PROVISIONING</b></h2><p>Dynamic Provisioning allows you to create storage volumes on-demand, eliminating the need for cluster administrators to pre-provision storage. For more information about dynamic provisioning, see <a href=\"#\">Dynamic provisioning</a>.</p><h1>CHAPTER 2. UNDERSTANDING EPHEMERAL STORAGE</h1><p>To manage temporary data that exists only for the duration of a workload, review the properties of ephemeral storage.</p><h2>2.1. OVERVIEW OF EPHEMERAL STORAGE</h2><p>To manage local storage for stateless applications, use ephemeral storage. Ephemeral storage is designed for the transient nature of pods and containers. You can use this feature to handle operations that require storage only for the duration of the lifecycle for the workload. Both developers and administrators can use the feature.</p><p>In addition to persistent storage, pods and containers can require ephemeral or transient local storage for their operation. The lifetime of this ephemeral storage does not extend beyond the life of the individual pod, and this ephemeral storage cannot be shared across pods.</p><p>Pods use ephemeral local storage for scratch space, caching, and logs. Issues related to the lack of local storage accounting and isolation include the following:</p><ul><li>• Pods cannot detect how much local storage is available to them.</li><li>• Pods cannot request guaranteed local storage.</li><li>• Local storage is a best-effort resource.</li><li>• Pods can be evicted due to other pods filling the local storage, after which new pods are not admitted until sufficient storage is reclaimed.</li></ul><p>Unlike persistent volumes, ephemeral storage is unstructured and the space is shared between all pods running on a node, in addition to other uses by the system, the container runtime, and OpenShift Container Platform. The ephemeral storage framework allows pods to specify their transient local storage needs. It also allows OpenShift Container Platform to schedule pods where appropriate, and to protect the node against excessive use of local storage.</p><p>While the ephemeral storage framework allows administrators and developers to better manage local storage, I/O throughput and latency are not directly affected.</p><h2>2.2. TYPES OF EPHEMERAL STORAGE</h2><p>To provision ephemeral local storage, you can create the primary partition by using either root or runtime methods. This storage is always made available in the primary partition, providing temporary space for your workloads.</p><h3>2.2.1. Root</h3><p>This partition holds the kubelet root directory, <code>/var/lib/kubelet/</code> by default, and <code>/var/log/</code> directory. This partition can be shared between user pods, the OS, and Kubernetes system daemons. This partition can be consumed by pods through <b>EmptyDir</b> volumes, container logs, image layers, and container-writable layers. Kubelet manages shared access and isolation of this partition. This partition is ephemeral, and applications cannot expect any performance SLAs, such as disk IOPS, from this partition.</p><h3>2.2.2. Runtime</h3><p>This is an optional partition that runtimes can use for overlay file systems. OpenShift Container Platform</p>\n<p>attempts to identify and provide shared access along with isolation to this partition. Container image layers and writable layers are stored here. If the runtime partition exists, the <b>root</b> partition does not hold any image layer or other writable storage.</p>\n\n<h2>2.3. EPHEMERAL STORAGE MANAGEMENT</h2>\n\n<p>Cluster administrators can manage ephemeral storage within a project by setting quotas that define the limit ranges and number of requests for ephemeral storage across all pods in a non-terminal state. Developers can also set requests and limits on this compute resource at the pod and container level.</p>\n\n<p>You can manage local ephemeral storage by specifying requests and limits. Each container in a pod can specify the following:</p>\n\n<ul>\n<li>• <b>spec.containers[].resources.limits.ephemeral-storage</b></li>\n<li>• <b>spec.containers[].resources.requests.ephemeral-storage</b></li>\n</ul>\n\n<h3>2.3.1. Ephemeral storage limits and requests units</h3>\n\n<p>Limits and requests for ephemeral storage are measured in byte quantities. You can express storage as a plain integer or as a fixed-point number using one of these suffixes: E, P, T, G, M, k. You can also use the power-of-two equivalents: Ei, Pi, Ti, Gi, Mi, Ki.</p>\n\n<p>For example, the following quantities all represent approximately the same value: 128974848, 129e6, 129M, and 123Mi.</p>\n\n<h4>IMPORTANT</h4>\n\n<p>The suffixes for each byte quantity are case-sensitive. Be sure to use the correct case. Use the case-sensitive \"M\", such as used in \"400M\", to set the request at 400 megabytes. Use the case-sensitive \"400Mi\" to request 400 mebibytes. If you specify \"400m\" of ephemeral storage, the storage request is only 0.4 bytes.</p>\n\n<h3>2.3.2. Ephemeral storage requests and limits example</h3>\n\n<p>The following example configuration file shows a pod with two containers:</p>\n\n<ul>\n<li>• Each container requests 2GiB of local ephemeral storage.</li>\n<li>• Each container has a limit of 4GiB of local ephemeral storage.</li>\n<li>• At the pod level, kubelet works out an overall pod storage limit by adding up the limits of all the containers in that pod.\n <ul>\n<li>◦ In this case, the total storage usage at the pod level is the sum of the disk usage from all containers plus the pod's <b>emptyDir</b> volumes.</li>\n<li>◦ Therefore, the pod has a request of 4GiB of local ephemeral storage, and a limit of 8GiB of local ephemeral storage.</li>\n</ul>\n</li>\n</ul>\n\n<h4>Example ephemeral storage configuration with quotas and limits</h4>\n\n<pre>apiVersion: v1\nkind: Pod\nmetadata:</pre>\n\n<pre>\nname: frontend\nspec:\n containers:\n - name: app\n image: images.my-company.example/app:v4\n resources:\n requests:\n ephemeral-storage: \"2Gi\" 1\n limits:\n ephemeral-storage: \"4Gi\" 2\n volumeMounts:\n - name: ephemeral\n mountPath: \"/tmp\"\n - name: log-aggregator\n image: images.my-company.example/log-aggregator:v6\n resources:\n requests:\n ephemeral-storage: \"2Gi\"\n limits:\n ephemeral-storage: \"4Gi\"\n volumeMounts:\n - name: ephemeral\n mountPath: \"/tmp\"\n volumes:\n - name: ephemeral\n emptyDir: {}\n</pre>\n\n<ul style=\"list-style-type: none;\">\n<li>1 Container request for local ephemeral storage.</li>\n<li>2 Container limit for local ephemeral storage.</li>\n</ul>\n\n<h3>2.3.3. Ephemeral storage configuration effects pod scheduling and eviction</h3>\n\n<p>The settings in the pod spec affect both how the scheduler makes a decision about scheduling pods and when kubelet evicts pods.</p>\n\n<ul style=\"list-style-type: none;\">\n<li>• First, the scheduler ensures that the sum of the resource requests of the scheduled containers is less than the capacity of the node. In this case, the pod can be assigned to a node only if the node's available ephemeral storage (allocatable resource) is more than 4GiB.</li>\n<li>• Second, at the container level, because the first container sets a resource limit, kubelet eviction manager measures the disk usage of this container and evicts the pod if the storage usage of the container exceeds its limit (4GiB). The kubelet eviction manager also marks the pod for eviction if the total usage exceeds the overall pod storage limit (8GiB).</li>\n</ul>\n\n<h2>2.4. ADDITIONAL RESOURCES</h2>\n\n<ul style=\"list-style-type: none;\">\n<li>• <a href=\"#\">Resources managed by quotas</a></li>\n</ul>\n\n<h2>2.5. MONITORING EPHEMERAL STORAGE</h2>\n<p>To monitor ephemeral storage usage, use the <b>/bin/df</b> utility. By using this tool, you can track disk space consumption on the volumes where ephemeral container data resides, specifically <b>/var/lib/kubelet</b> and <b>/var/lib/containers</b>.</p><p>When you use the <b>df</b> command, the available space for only <b>/var/lib/kubelet</b> is shown if <b>/var/lib/containers</b> is placed on a separate disk by the cluster administrator.</p><h3>Procedure</h3><ul><li>• To show the human-readable values of used and available space in <b>/var/lib</b>, enter the following command:</li></ul><pre>$ df -h /var/lib</pre><p>The output shows the ephemeral storage usage in <b>/var/lib</b>:</p><h3>Example output</h3><pre>Filesystem Size Used Avail Use% Mounted on\n/dev/disk/by-partuuid/4cd1448a-01 69G 32G 34G 49% /</pre><h1>CHAPTER 3. UNDERSTANDING PERSISTENT STORAGE</h1><h2>3.1. PERSISTENT STORAGE OVERVIEW</h2><p>Stateful applications deployed in containers require persistent storage. {microshift-short} uses a pre-provisioned storage framework called persistent volumes (PV) to allow node administrators to provision persistent storage. The data inside these volumes can exist beyond the lifecycle of an individual pod. Developers can use persistent volume claims (PVCs) to request storage requirements.</p><p>Managing storage is a distinct problem from managing compute resources. OpenShift Container Platform uses the Kubernetes persistent volume (PV) framework to allow cluster administrators to provision persistent storage for a cluster. Developers can use persistent volume claims (PVCs) to request PV resources without having specific knowledge of the underlying storage infrastructure.</p><p>PVCs are specific to a project, and are created and used by developers as a means to use a PV. PV resources on their own are not scoped to any single project; they can be shared across the entire OpenShift Container Platform node and claimed from any project. After a PV is bound to a PVC, that PV can not then be bound to additional PVCs. This has the effect of scoping a bound PV to a single namespace, that of the binding project.</p><p>PVs are defined by a <b>PersistentVolume</b> API object, which represents a piece of existing storage in the cluster that was either statically provisioned by the cluster administrator or dynamically provisioned using a <b>StorageClass</b> object. It is a resource in the cluster just like a node is a cluster resource.</p><p>PVs are volume plugins like <b>Volumes</b> but have a lifecycle that is independent of any individual pod that uses the PV. PV objects capture the details of the implementation of the storage, be that NFS, iSCSI, or a cloud-provider-specific storage system.</p><h3>IMPORTANT</h3><p>High availability of storage in the infrastructure is left to the underlying storage provider.</p><p>PVCs are defined by a <b>PersistentVolumeClaim</b> API object, which represents a request for storage by a developer. It is similar to a pod in that pods consume node resources and PVCs consume PV resources. For example, pods can request specific levels of resources, such as CPU and memory, while PVCs can request specific storage capacity and access modes. For example, they can be mounted once read-write or many times read-only.</p><h2>3.2. LIFECYCLE OF A VOLUME AND CLAIM</h2><p>PVs are resources in the cluster. PVCs are requests for those resources and also act as claim checks to the resource. The interaction between PVs and PVCs have the following lifecycle.</p><h3>3.2.1. Provision storage</h3><p>In response to requests from a developer defined in a PVC, a cluster administrator configures one or more dynamic provisioners that provision storage and a matching PV.</p><p>Alternatively, a cluster administrator can create a number of PVs in advance that carry the details of the real storage that is available for use. PVs exist in the API and are available for use.</p><h3>3.2.2. Bind claims</h3><p>When you create a PVC, you request a specific amount of storage, specify the required access mode, and create a storage class to describe and classify the storage. The control loop in the master watches for new PVCs and binds the new PVC to an appropriate PV. If an appropriate PV does not exist, a provisioner for the storage class creates one.</p><p>The size of all PVs might exceed your PVC size. This is especially true with manually provisioned PVs. To minimize the excess, OpenShift Container Platform binds to the smallest PV that matches all other criteria.</p><p>Claims remain unbound indefinitely if a matching volume does not exist or can not be created with any available provisioner servicing a storage class. Claims are bound as matching volumes become available. For example, a cluster with many manually provisioned 50Gi volumes would not match a PVC requesting 100Gi. The PVC can be bound when a 100Gi PV is added to the cluster.</p><h3>3.2.3. Use pods and claimed PVs</h3><p>Pods use claims as volumes. The cluster inspects the claim to find the bound volume and mounts that volume for a pod. For those volumes that support multiple access modes, you must specify which mode applies when you use the claim as a volume in a pod.</p><p>Once you have a claim and that claim is bound, the bound PV belongs to you for as long as you need it. You can schedule pods and access claimed PVs by including <b>persistentVolumeClaim</b> in the pod's volumes block.</p><h4>NOTE</h4><p>If you attach persistent volumes that have high file counts to pods, those pods can fail or can take a long time to start. For more information, see <a href=\"#\">When using Persistent Volumes with high file counts in OpenShift, why do pods fail to start or take an excessive amount of time to achieve \"Ready\" state?</a></p><h3>3.2.4. Storage Object in Use Protection</h3><p>The Storage Object in Use Protection feature ensures that PVCs in active use by a pod and PVs that are bound to PVCs are not removed from the system, as this can result in data loss.</p><p>Storage Object in Use Protection is enabled by default.</p><h4>NOTE</h4><p>A PVC is in active use by a pod when a <b>Pod</b> object exists that uses the PVC.</p><p>If a user deletes a PVC that is in active use by a pod, the PVC is not removed immediately. PVC removal is postponed until the PVC is no longer actively used by any pods. Also, if a cluster admin deletes a PV that is bound to a PVC, the PV is not removed immediately. PV removal is postponed until the PV is no longer bound to a PVC.</p><h3>3.2.5. Release a persistent volume</h3><p>When you are finished with a volume, you can delete the PVC object from the API, which allows reclamation of the resource. The volume is considered released when the claim is deleted, but it is not yet available for another claim. The previous claimant's data remains on the volume and must be handled according to policy.</p>\n<h3>3.2.6. Reclaim policy for persistent volumes</h3>\n\n<p>The reclaim policy of a persistent volume tells the cluster what to do with the volume after it is released. A volume's reclaim policy can be <b>Retain</b>, <b>Recycle</b>, or <b>Delete</b>.</p>\n\n<ul>\n<li>• <b>Retain</b> reclaim policy allows manual reclamation of the resource for those volume plugins that support it.</li>\n<li>• <b>Recycle</b> reclaim policy recycles the volume back into the pool of unbound persistent volumes once it is released from its claim.</li>\n</ul>\n\n<h4>IMPORTANT</h4>\n\n<p>The <b>Recycle</b> reclaim policy is deprecated in OpenShift Container Platform 4. Dynamic provisioning is recommended for equivalent and better functionality.</p>\n\n<ul>\n<li>• <b>Delete</b> reclaim policy deletes both the <b>PersistentVolume</b> object from OpenShift Container Platform and the associated storage asset in external infrastructure, such as Amazon Elastic Block Store (Amazon EBS) or VMware vSphere.</li>\n</ul>\n\n<h4>NOTE</h4>\n\n<p>Dynamically provisioned volumes are always deleted.</p>\n\n<h3>3.2.7. Reclaiming a persistent volume manually</h3>\n\n<p>When a persistent volume claim (PVC) is deleted, the persistent volume (PV) still exists and is considered \"released\". However, the PV is not yet available for another claim because the data of the previous claimant remains on the volume.</p>\n\n<h4>Procedure</h4>\n\n<p>To manually reclaim the PV as a cluster administrator:</p>\n\n<ol>\n<li>1. Delete the PV by running the following command:</li>\n</ol>\n\n<pre>$ oc delete pv <pv_name></pre>\n\n<p>The associated storage asset in the external infrastructure, such as an AWS EBS, GCE PD, Azure Disk, or Cinder volume, still exists after the PV is deleted.</p>\n\n<ol>\n<li>2. Clean up the data on the associated storage asset.</li>\n<li>3. Delete the associated storage asset. Alternately, to reuse the same storage asset, create a new PV with the storage asset definition.</li>\n</ol>\n\n<p>The reclaimed PV is now available for use by another PVC.</p>\n\n<h3>3.2.8. Changing the reclaim policy of a persistent volume</h3>\n\n<p>You can change the reclaim policy of a persistent volume.</p>\n\n<h4>Procedure</h4>\n\n<ol>\n<li>1. List the persistent volumes in your cluster:</li>\n</ol>\n\n<pre>$ oc get pv</pre>\n\n<h3>Example output</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>NAME</th>\n<th>CAPACITY</th>\n<th>ACCESSMODES</th>\n<th>RECLAIMPOLICY</th>\n<th>STATUS</th>\n</tr>\n<tr>\n<th>CLAIM</th>\n<th>STORAGECLASS</th>\n<th>REASON</th>\n<th>AGE</th>\n<th></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>pvc-b6efd8da-b7b5-11e6-9d58-0ed433a7dd94</td>\n<td>4Gi</td>\n<td>RWO</td>\n<td>Delete</td>\n<td>Bound</td>\n</tr>\n<tr>\n<td>default/claim1</td>\n<td>manual</td>\n<td>10s</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>pvc-b95650f8-b7b5-11e6-9d58-0ed433a7dd94</td>\n<td>4Gi</td>\n<td>RWO</td>\n<td>Delete</td>\n<td>Bound</td>\n</tr>\n<tr>\n<td>default/claim2</td>\n<td>manual</td>\n<td>6s</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>pvc-bb3ca71d-b7b5-11e6-9d58-0ed433a7dd94</td>\n<td>4Gi</td>\n<td>RWO</td>\n<td>Delete</td>\n<td>Bound</td>\n</tr>\n<tr>\n<td>default/claim3</td>\n<td>manual</td>\n<td>3s</td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\n<ol>\n<li>2. Choose one of your persistent volumes and change its reclaim policy:</li>\n</ol>\n\n<pre>$ oc patch pv <your-pv-name> -p '{\"spec\":{\"persistentVolumeReclaimPolicy\":\"Retain\"}}'</pre>\n\n<ol>\n<li>3. Verify that your chosen persistent volume has the right policy:</li>\n</ol>\n\n<pre>$ oc get pv</pre>\n\n<h3>Example output</h3>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>NAME</th>\n<th>CAPACITY</th>\n<th>ACCESSMODES</th>\n<th>RECLAIMPOLICY</th>\n<th>STATUS</th>\n</tr>\n<tr>\n<th>CLAIM</th>\n<th>STORAGECLASS</th>\n<th>REASON</th>\n<th>AGE</th>\n<th></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>pvc-b6efd8da-b7b5-11e6-9d58-0ed433a7dd94</td>\n<td>4Gi</td>\n<td>RWO</td>\n<td>Delete</td>\n<td>Bound</td>\n</tr>\n<tr>\n<td>default/claim1</td>\n<td>manual</td>\n<td>10s</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>pvc-b95650f8-b7b5-11e6-9d58-0ed433a7dd94</td>\n<td>4Gi</td>\n<td>RWO</td>\n<td>Delete</td>\n<td>Bound</td>\n</tr>\n<tr>\n<td>default/claim2</td>\n<td>manual</td>\n<td>6s</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>pvc-bb3ca71d-b7b5-11e6-9d58-0ed433a7dd94</td>\n<td>4Gi</td>\n<td>RWO</td>\n<td>Retain</td>\n<td>Bound</td>\n</tr>\n<tr>\n<td>default/claim3</td>\n<td>manual</td>\n<td>3s</td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\n<p>In the preceding output, the volume bound to claim <b>default/claim3</b> now has a <b>Retain</b> reclaim policy. The volume will not be automatically deleted when a user deletes claim <b>default/claim3</b>.</p>\n\n<h2>3.3. PERSISTENT VOLUMES</h2>\n\n<p>Each PV contains a <b>spec</b> and <b>status</b>, which is the specification and status of the volume, for example:</p>\n\n<h3>PersistentVolume object definition example</h3>\n\n<pre>apiVersion: v1\nkind: PersistentVolume\nmetadata:\n name: pv0001 <b>1</b>\nspec:\n capacity:\n storage: 5Gi <b>2</b>\n accessModes:\n - ReadWriteOnce <b>3</b></pre>\n<pre>persistentVolumeReclaimPolicy: Retain 4<br/>...<br/>status:<br/>...</pre><ol style=\"list-style-type: none;\"><li>1 Name of the persistent volume.</li><li>2 The amount of storage available to the volume.</li><li>3 The access mode, defining the read-write and mount permissions.</li><li>4 The reclaim policy, indicating how the resource should be handled once it is released.</li></ol><p>You can view the name of a PVC that is bound to a PV by running the following command:</p><pre>$ oc get pv <pv_name> -o jsonpath='{.spec.claimRef.name}'</pre><h3>3.3.1. Types of PVs</h3><p>OpenShift Container Platform supports the following persistent volume plugins:</p><ul style=\"list-style-type: none;\"><li>• AWS Elastic Block Store (EBS), which is installed by default.</li><li>• AWS Elastic File Store (EFS)</li><li>• Azure Disk</li><li>• Azure File</li><li>• Cinder</li><li>• Fibre Channel</li><li>• GCP Persistent Disk</li><li>• GCP Filestore</li><li>• IBM Power Virtual Server Block</li><li>• IBM Cloud® VPC Block</li><li>• HostPath</li><li>• iSCSI</li><li>• Local volume</li><li>• LVM Storage</li><li>• NFS</li><li>• OpenStack Manila</li><li>• Red Hat OpenShift Data Foundation</li><li>• CIFS/SMB</li></ul>\n<ul>\n<li>• VMware vSphere</li>\n</ul>\n\n<h3>3.3.2. Capacity</h3>\n\n<p>Generally, a persistent volume (PV) has a specific storage capacity. This is set by using the <b>capacity</b> attribute of the PV.</p>\n\n<p>Currently, storage capacity is the only resource that can be set or requested. Future attributes may include IOPS, throughput, and so on.</p>\n\n<h3>3.3.3. Access modes</h3>\n\n<p>A persistent volume can be mounted on a host in any way supported by the resource provider. Providers have different capabilities and each PV's access modes are set to the specific modes supported by that particular volume. For example, NFS can support multiple read-write clients, but a specific NFS PV might be exported on the server as read-only. Each PV gets its own set of access modes describing that specific PV's capabilities.</p>\n\n<p>Claims are matched to volumes with similar access modes. The only two matching criteria are access modes and size. A claim's access modes represent a request. Therefore, you might be granted more, but never less. For example, if a claim requests RWO, but the only volume available is an NFS PV (RWO+ROX+RWX), the claim would then match NFS because it supports RWO.</p>\n\n<p>Direct matches are always attempted first. The volume's modes must match or contain more modes than you requested. The size must be greater than or equal to what is expected. If two types of volumes, such as NFS and iSCSI, have the same set of access modes, either of them can match a claim with those modes. There is no ordering between types of volumes and no way to choose one type over another.</p>\n\n<p>All volumes with the same modes are grouped, and then sorted by size, smallest to largest. The binder gets the group with matching modes and iterates over each, in size order, until one size matches.</p>\n\n<h4>IMPORTANT</h4>\n\n<p>Volume access modes describe volume capabilities. They are not enforced constraints. The storage provider is responsible for runtime errors resulting from invalid use of the resource. Errors in the provider show up at runtime as mount errors.</p>\n\n<p>For example, NFS offers <b>ReadWriteOnce</b> access mode. If you want to use the volume's ROX capability, mark the claims as <b>ReadOnlyMany</b>.</p>\n\n<p>iSCSI and Fibre Channel volumes do not currently have any fencing mechanisms. You must ensure the volumes are only used by one node at a time. In certain situations, such as draining a node, the volumes can be used simultaneously by two nodes. Before draining the node, delete the pods that use the volumes.</p>\n\n<p>The following table lists the access modes:</p>\n\n<p><b>Table 3.1. Access modes</b></p>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Access Mode</th>\n<th>CLI abbreviation</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>ReadWriteOnce</td>\n<td><b>RWO</b></td>\n<td>The volume can be mounted as read-write by a single node.</td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Access Mode</th>\n<th>CLI abbreviation</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>ReadWriteOncePod</td>\n<td><b>RWOP</b></td>\n<td>The volume can be mounted as read-write by a single pod on a single node.</td>\n</tr>\n<tr>\n<td>ReadOnlyMany</td>\n<td><b>ROX</b></td>\n<td>The volume can be mounted as read-only by many nodes.</td>\n</tr>\n<tr>\n<td>ReadWriteMany</td>\n<td><b>RWX</b></td>\n<td>The volume can be mounted as read-write by many nodes.</td>\n</tr>\n</tbody>\n</table>\nTable 3.2. Supported access modes for persistent volumes\n<table border=\"1\">\n<thead>\n<tr>\n<th>Volume plugin</th>\n<th>ReadWriteOnce [1]</th>\n<th>ReadWriteOncePod</th>\n<th>ReadOnlyMany</th>\n<th>ReadWriteMany</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>AWS EBS [2]</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>AWS EFS</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n</tr>\n<tr>\n<td>Azure File</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n</tr>\n<tr>\n<td>Azure Disk</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>CIFS/SMB</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n</tr>\n<tr>\n<td>Cinder</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Fibre Channel</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■<sup>[3]</sup></td>\n</tr>\n<tr>\n<td>GCP Persistent Disk</td>\n<td>■<sup>[4]</sup></td>\n<td>■</td>\n<td>■</td>\n<td>■<sup>[4]</sup></td>\n</tr>\n<tr>\n<td>GCP Filestore</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n</tr>\n<tr>\n<td>HostPath</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>IBM Power Virtual Server Disk</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n</tr>\n<tr>\n<td>IBM Cloud® VPC Disk</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n\n<table border=\"1\">\n<thead>\n<tr>\n<th>Volume plugin</th>\n<th>ReadWriteOnce [1]</th>\n<th>ReadWriteOncePod</th>\n<th>ReadOnlyMany</th>\n<th>ReadWriteMany</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>iSCSI</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■<sup>[3]</sup></td>\n</tr>\n<tr>\n<td>Local volume</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>LVM Storage</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>NFS</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n<td>■</td>\n</tr>\n<tr>\n<td>OpenStack Manila</td>\n<td></td>\n<td>■</td>\n<td></td>\n<td>■</td>\n</tr>\n<tr>\n<td>Red Hat OpenShift Data Foundation</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td>■</td>\n</tr>\n<tr>\n<td>VMware vSphere</td>\n<td>■</td>\n<td>■</td>\n<td></td>\n<td>■<sup>[5]</sup></td>\n</tr>\n</tbody>\n</table>\n\n<ol>\n<li>1. ReadWriteOnce (RWO) volumes cannot be mounted on multiple nodes. If a node fails, the system does not allow the attached RWO volume to be mounted on a new node because it is already assigned to the failed node. If you encounter a multi-attach error message as a result, force delete the pod on a shutdown or crashed node to avoid data loss in critical workloads, such as when dynamic persistent volumes are attached.</li>\n<li>2. Use a recreate deployment strategy for pods that rely on AWS EBS.</li>\n<li>3. Only raw block volumes support the <b>ReadWriteMany</b> (RWX) access mode for Fibre Channel and iSCSI. For more information, see \"Block volume support\".</li>\n<li>4. For GCP hyperdisk-balanced disks:\n <ul>\n<li>• The supported access modes are:\n <ul>\n<li>◦ <b>ReadWriteOnce</b></li>\n<li>◦ <b>ReadWriteMany</b></li>\n</ul>\n</li>\n<li>• Cloning and snapshotting is disabled for disks with <b>ReadWriteMany</b> access mode enabled.</li>\n<li>• You can attach a single hyperdisk-balanced disk volume in <b>ReadWriteMany</b> to a maximum of 8 instances.</li>\n<li>• You can only resize a disk in <b>ReadWriteMany</b> if you detach the disk from all instances.</li>\n<li>• <a href=\"#\">Additional limitations.</a></li>\n</ul>\n</li>\n<li>5. If the underlying vSphere environment supports the vSAN file service, the vSphere Container</li>\n</ol>"},"page_stats":{"kind":"list like","value":[{"page_number":1,"error":false,"token_count":249,"num_chunks":5},{"page_number":2,"error":false,"token_count":48,"num_chunks":1},{"page_number":3,"error":false,"token_count":88,"num_chunks":2},{"page_number":4,"error":false,"token_count":591,"num_chunks":11},{"page_number":5,"error":false,"token_count":1850,"num_chunks":4},{"page_number":6,"error":false,"token_count":1930,"num_chunks":3},{"page_number":7,"error":false,"token_count":1948,"num_chunks":3},{"page_number":8,"error":false,"token_count":1997,"num_chunks":3},{"page_number":9,"error":false,"token_count":1683,"num_chunks":3},{"page_number":10,"error":false,"token_count":1731,"num_chunks":3},{"page_number":11,"error":false,"token_count":2016,"num_chunks":3},{"page_number":12,"error":false,"token_count":1961,"num_chunks":3},{"page_number":13,"error":false,"token_count":690,"num_chunks":3},{"page_number":14,"error":false,"token_count":82,"num_chunks":2},{"page_number":15,"error":false,"token_count":1230,"num_chunks":24},{"page_number":16,"error":false,"token_count":955,"num_chunks":17},{"page_number":17,"error":false,"token_count":1442,"num_chunks":27},{"page_number":18,"error":false,"token_count":951,"num_chunks":15},{"page_number":19,"error":false,"token_count":1134,"num_chunks":17},{"page_number":20,"error":false,"token_count":1297,"num_chunks":18},{"page_number":21,"error":false,"token_count":832,"num_chunks":10},{"page_number":22,"error":false,"token_count":558,"num_chunks":10},{"page_number":23,"error":false,"token_count":1263,"num_chunks":19},{"page_number":24,"error":false,"token_count":1323,"num_chunks":20},{"page_number":25,"error":false,"token_count":1383,"num_chunks":24},{"page_number":26,"error":false,"token_count":1812,"num_chunks":17},{"page_number":27,"error":false,"token_count":641,"num_chunks":9},{"page_number":28,"error":false,"token_count":1333,"num_chunks":19},{"page_number":29,"error":false,"token_count":962,"num_chunks":5},{"page_number":30,"error":false,"token_count":893,"num_chunks":4}],"string":"[\n {\n \"page_number\": 1,\n \"error\": false,\n \"token_count\": 249,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 2,\n \"error\": false,\n \"token_count\": 48,\n \"num_chunks\": 1\n },\n {\n \"page_number\": 3,\n \"error\": false,\n \"token_count\": 88,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 4,\n \"error\": false,\n \"token_count\": 591,\n \"num_chunks\": 11\n },\n {\n \"page_number\": 5,\n \"error\": false,\n \"token_count\": 1850,\n \"num_chunks\": 4\n },\n {\n \"page_number\": 6,\n \"error\": false,\n \"token_count\": 1930,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 7,\n \"error\": false,\n \"token_count\": 1948,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 8,\n \"error\": false,\n \"token_count\": 1997,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 9,\n \"error\": false,\n \"token_count\": 1683,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 10,\n \"error\": false,\n \"token_count\": 1731,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 11,\n \"error\": false,\n \"token_count\": 2016,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 12,\n \"error\": false,\n \"token_count\": 1961,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 13,\n \"error\": false,\n \"token_count\": 690,\n \"num_chunks\": 3\n },\n {\n \"page_number\": 14,\n \"error\": false,\n \"token_count\": 82,\n \"num_chunks\": 2\n },\n {\n \"page_number\": 15,\n \"error\": false,\n \"token_count\": 1230,\n \"num_chunks\": 24\n },\n {\n \"page_number\": 16,\n \"error\": false,\n \"token_count\": 955,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 17,\n \"error\": false,\n \"token_count\": 1442,\n \"num_chunks\": 27\n },\n {\n \"page_number\": 18,\n \"error\": false,\n \"token_count\": 951,\n \"num_chunks\": 15\n },\n {\n \"page_number\": 19,\n \"error\": false,\n \"token_count\": 1134,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 20,\n \"error\": false,\n \"token_count\": 1297,\n \"num_chunks\": 18\n },\n {\n \"page_number\": 21,\n \"error\": false,\n \"token_count\": 832,\n \"num_chunks\": 10\n },\n {\n \"page_number\": 22,\n \"error\": false,\n \"token_count\": 558,\n \"num_chunks\": 10\n },\n {\n \"page_number\": 23,\n \"error\": false,\n \"token_count\": 1263,\n \"num_chunks\": 19\n },\n {\n \"page_number\": 24,\n \"error\": false,\n \"token_count\": 1323,\n \"num_chunks\": 20\n },\n {\n \"page_number\": 25,\n \"error\": false,\n \"token_count\": 1383,\n \"num_chunks\": 24\n },\n {\n \"page_number\": 26,\n \"error\": false,\n \"token_count\": 1812,\n \"num_chunks\": 17\n },\n {\n \"page_number\": 27,\n \"error\": false,\n \"token_count\": 641,\n \"num_chunks\": 9\n },\n {\n \"page_number\": 28,\n \"error\": false,\n \"token_count\": 1333,\n \"num_chunks\": 19\n },\n {\n \"page_number\": 29,\n \"error\": false,\n \"token_count\": 962,\n \"num_chunks\": 5\n },\n {\n \"page_number\": 30,\n \"error\": false,\n \"token_count\": 893,\n \"num_chunks\": 4\n }\n]","isConversational":false}}}],"truncated":false,"partial":false},"paginationData":{"pageIndex":0,"numItemsPerPage":100,"numTotalItems":111,"offset":0,"length":100}},"jwt":"eyJhbGciOiJFZERTQSJ9.eyJyZWFkIjp0cnVlLCJwZXJtaXNzaW9ucyI6eyJyZXBvLmNvbnRlbnQucmVhZCI6dHJ1ZX0sImlhdCI6MTc3NjU2ODY5OCwic3ViIjoiL2RhdGFzZXRzL3Nyb2Vja2VyL29wZW5zaGlmdC1kb2NzLWNoYW5kcmEyLW9jci10ZXN0IiwiZXhwIjoxNzc2NTcyMjk4LCJpc3MiOiJodHRwczovL2h1Z2dpbmdmYWNlLmNvIn0.ZlbAsaxBdgdL7FYfqI5bUF4BFzqY_yUNHve7_3pvh4pSmsEnduoHzQaPnrMowNNnCiR1JMamEio9dvt0cYtsDg","displayUrls":true,"splitSizeSummaries":[{"config":"default","split":"train","numRows":111,"numBytesParquet":3963785}]},"discussionsStats":{"closed":0,"open":1,"total":1},"fullWidth":true,"hasGatedAccess":true,"hasFullAccess":true,"isEmbedded":false,"savedQueries":{"community":[],"user":[]}}">
source_id stringlengths 44 103 | pdf_url stringlengths 132 250 | status stringclasses 1
value | processed_at stringlengths 32 32 | elapsed_seconds float64 11.9 579 | num_pages int64 7 1.78k | num_pages_processed int64 7 30 | max_pages_per_paper int64 30 30 | pdf_exceeds_page_limit bool 2
classes | failed_pages listlengths 0 0 | prompt_type stringclasses 1
value | model_id stringclasses 1
value | script_version timestamp[ms]date 2026-04-15 00:00:00 2026-04-15 00:00:00 | markdown stringlengths 2.27k 125k | html stringlengths 2.39k 126k | page_stats listlengths 7 30 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
OpenShift_Container_Platform-4.21-Advanced_networking-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/advanced_networking/OpenShift_Container_Platform-4.21-Advanced_networking-en-US.pdf | success | 2026-04-15T16:51:34.808250+00:00 | 136.56 | 204 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Advanced networking
Specialized and advanced networking topics in OpenShift Container Platform## OpenShift Container Platform 4.21 Advanced networking
---
Specialized and advanced networking topics in OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as... | <h1>OpenShift Container Platform 4.21</h1><h2>Advanced networking</h2><p>Specialized and advanced networking topics in OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 Advanced networking</h2><hr/><p>Specialized and advanced networking topics in OpenShift Container Platform</p><h2>Legal Notice</h2>... | [
{
"page_number": 1,
"error": false,
"token_count": 248,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-AI_workloads-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/ai_workloads/OpenShift_Container_Platform-4.21-AI_workloads-en-US.pdf | success | 2026-04-15T16:52:41.053934+00:00 | 66.22 | 73 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## AI workloads
Running AI workloads on OpenShift Container Platform# OpenShift Container Platform 4.21 AI workloads
---
Running AI workloads on OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in th... | <h1>OpenShift Container Platform 4.21</h1><h2>AI workloads</h2><p>Running AI workloads on OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 AI workloads</h1><hr/><p>Running AI workloads on OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted be... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 89,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-API_overview-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/api_overview/OpenShift_Container_Platform-4.21-API_overview-en-US.pdf | success | 2026-04-15T16:53:35.061832+00:00 | 53.98 | 32 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## API overview
Overview content for the OpenShift Container Platform API# OpenShift Container Platform 4.21 API overview
---
Overview content for the OpenShift Container Platform API## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrat... | <h1>OpenShift Container Platform 4.21</h1><h2>API overview</h2><p>Overview content for the OpenShift Container Platform API</p><h1>OpenShift Container Platform 4.21 API overview</h1><hr/><p>Overview content for the OpenShift Container Platform API</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwis... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 88,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Architecture-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/architecture/OpenShift_Container_Platform-4.21-Architecture-en-US.pdf | success | 2026-04-15T16:54:42.952116+00:00 | 67.86 | 73 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Architecture
An overview of the architecture for OpenShift Container Platform# OpenShift Container Platform 4.21 Architecture
---
An overview of the architecture for OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of... | <h1>OpenShift Container Platform 4.21</h1><h2>Architecture</h2><p>An overview of the architecture for OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Architecture</h1><hr/><p>An overview of the architecture for OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Exce... | [
{
"page_number": 1,
"error": false,
"token_count": 248,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 87,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Authentication_and_authorization-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/authentication_and_authorization/OpenShift_Container_Platform-4.21-Authentication_and_authorization-en-US.pdf | success | 2026-04-15T16:55:55.162250+00:00 | 72.19 | 250 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Authentication and authorization
Configuring user authentication and access controls for users and services# OpenShift Container Platform 4.21 Authentication and authorization
---
Configuring user authentication and access controls for users and services## Legal Notice
Copyri... | <h1>OpenShift Container Platform 4.21</h1><h2>Authentication and authorization</h2><p>Configuring user authentication and access controls for users and services</p><h1>OpenShift Container Platform 4.21 Authentication and authorization</h1><hr/><p>Configuring user authentication and access controls for users and service... | [
{
"page_number": 1,
"error": false,
"token_count": 253,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 91,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Authorization_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/authorization_apis/OpenShift_Container_Platform-4.21-Authorization_APIs-en-US.pdf | success | 2026-04-15T16:56:57.054770+00:00 | 61.87 | 90 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Authorization APIs
Reference guide for authorization APIs# OpenShift Container Platform 4.21 Authorization APIs
---
Reference guide for authorization APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation... | <h1>OpenShift Container Platform 4.21</h1><h2>Authorization APIs</h2><p>Reference guide for authorization APIs</p><h1>OpenShift Container Platform 4.21 Authorization APIs</h1><hr/><p>Reference guide for authorization APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of... | [
{
"page_number": 1,
"error": false,
"token_count": 242,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Autoscale_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/autoscale_apis/OpenShift_Container_Platform-4.21-Autoscale_APIs-en-US.pdf | success | 2026-04-15T16:58:04.530654+00:00 | 67.46 | 92 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Autoscale APIs
Reference guide for autoscale APIs# OpenShift Container Platform 4.21 Autoscale APIs
---
Reference guide for autoscale APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by... | <h1>OpenShift Container Platform 4.21</h1><h2>Autoscale APIs</h2><p>Reference guide for autoscale APIs</p><h1>OpenShift Container Platform 4.21 Autoscale APIs</h1><hr/><p>Reference guide for autoscale APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustratio... | [
{
"page_number": 1,
"error": false,
"token_count": 249,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 86,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Backup_and_restore-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/backup_and_restore/OpenShift_Container_Platform-4.21-Backup_and_restore-en-US.pdf | success | 2026-04-15T16:59:24.178906+00:00 | 79.63 | 465 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Backup and restore
Backing up and restoring your OpenShift Container Platform cluster# OpenShift Container Platform 4.21 Backup and restore
---
Backing up and restoring your OpenShift Container Platform cluster## Legal Notice
Copyright © Red Hat.
Except as otherwise noted be... | <h1>OpenShift Container Platform 4.21</h1><h2>Backup and restore</h2><p>Backing up and restoring your OpenShift Container Platform cluster</p><h1>OpenShift Container Platform 4.21 Backup and restore</h1><hr/><p>Backing up and restoring your OpenShift Container Platform cluster</p><h2>Legal Notice</h2><p>Copyright © Red... | [
{
"page_number": 1,
"error": false,
"token_count": 248,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Building_applications-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/building_applications/OpenShift_Container_Platform-4.21-Building_applications-en-US.pdf | success | 2026-04-15T17:00:35.615987+00:00 | 71.42 | 196 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Building applications
Creating and managing applications on OpenShift Container Platform# OpenShift Container Platform 4.21 Building applications
---
Creating and managing applications on OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise no... | <h1>OpenShift Container Platform 4.21</h1><h2>Building applications</h2><p>Creating and managing applications on OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Building applications</h1><hr/><p>Creating and managing applications on OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright... | [
{
"page_number": 1,
"error": false,
"token_count": 249,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 88,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Builds_using_BuildConfig-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/builds_using_buildconfig/OpenShift_Container_Platform-4.21-Builds_using_BuildConfig-en-US.pdf | success | 2026-04-15T17:01:45.698707+00:00 | 70.06 | 114 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Builds using BuildConfig
Builds# OpenShift Container Platform 4.21 Builds using BuildConfig
---
Builds## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons ... | <h1>OpenShift Container Platform 4.21</h1><h2>Builds using BuildConfig</h2><p>Builds</p><h1>OpenShift Container Platform 4.21 Builds using BuildConfig</h1><hr/><p>Builds</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are license... | [
{
"page_number": 1,
"error": false,
"token_count": 242,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 83,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Builds_using_Shipwright-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/builds_using_shipwright/OpenShift_Container_Platform-4.21-Builds_using_Shipwright-en-US.pdf | success | 2026-04-15T17:01:59.429693+00:00 | 12.58 | 7 | 7 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Builds using Shipwright
An extensible build framework to build container images on an OpenShift cluster# OpenShift Container Platform 4.21 Builds using Shipwright
---
An extensible build framework to build container images on an OpenShift cluster## Legal Notice
Copyright © Re... | <h1>OpenShift Container Platform 4.21</h1><h2>Builds using Shipwright</h2><p>An extensible build framework to build container images on an OpenShift cluster</p><h1>OpenShift Container Platform 4.21 Builds using Shipwright</h1><hr/><p>An extensible build framework to build container images on an OpenShift cluster</p><h2... | [
{
"page_number": 1,
"error": false,
"token_count": 255,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 94,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-CICD_overview-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/cicd_overview/OpenShift_Container_Platform-4.21-CICD_overview-en-US.pdf | success | 2026-04-15T17:02:18.642892+00:00 | 19.21 | 8 | 8 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## CI/CD overview
Contains information about CI/CD for OpenShift Container Platform## OpenShift Container Platform 4.21 CI/CD overview
---
Contains information about CI/CD for OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the ... | <h1>OpenShift Container Platform 4.21</h1><h2>CI/CD overview</h2><p>Contains information about CI/CD for OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 CI/CD overview</h2><hr/><p>Contains information about CI/CD for OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><... | [
{
"page_number": 1,
"error": false,
"token_count": 249,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 92,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-CLI_tools-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/cli_tools/OpenShift_Container_Platform-4.21-CLI_tools-en-US.pdf | success | 2026-04-15T17:03:33.219481+00:00 | 74.58 | 146 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## CLI tools
Learning how to use the command-line tools for OpenShift Container Platform## OpenShift Container Platform 4.21 CLI tools
---
Learning how to use the command-line tools for OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted b... | <h1>OpenShift Container Platform 4.21</h1><h2>CLI tools</h2><p>Learning how to use the command-line tools for OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 CLI tools</h2><hr/><p>Learning how to use the command-line tools for OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red... | [
{
"page_number": 1,
"error": false,
"token_count": 252,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 92,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Cluster_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/cluster_apis/OpenShift_Container_Platform-4.21-Cluster_APIs-en-US.pdf | success | 2026-04-15T17:04:28.417342+00:00 | 55.19 | 30 | 30 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Cluster APIs
Reference guide for cluster APIs# OpenShift Container Platform 4.21 Cluster APIs
---
Reference guide for cluster APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat... | <h1>OpenShift Container Platform 4.21</h1><h2>Cluster APIs</h2><p>Reference guide for cluster APIs</p><h1>OpenShift Container Platform 4.21 Cluster APIs</h1><hr/><p>Reference guide for cluster APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in th... | [
{
"page_number": 1,
"error": false,
"token_count": 242,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Cluster_Observability_Operator-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/cluster_observability_operator/OpenShift_Container_Platform-4.21-Cluster_Observability_Operator-en-US.pdf | success | 2026-04-15T17:04:40.521441+00:00 | 12.08 | 7 | 7 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Cluster Observability Operator
Configuring and using the Cluster Observability Operator in OpenShift Container Platform# OpenShift Container Platform 4.21 Cluster Observability Operator
---
Configuring and using the Cluster Observability Operator in OpenShift Container Platfor... | <h1>OpenShift Container Platform 4.21</h1><h2>Cluster Observability Operator</h2><p>Configuring and using the Cluster Observability Operator in OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Cluster Observability Operator</h1><hr/><p>Configuring and using the Cluster Observability Operator in Ope... | [
{
"page_number": 1,
"error": false,
"token_count": 256,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 95,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Common_object_reference-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/common_object_reference/OpenShift_Container_Platform-4.21-Common_object_reference-en-US.pdf | success | 2026-04-15T17:05:54.852438+00:00 | 74.33 | 335 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Common object reference
Reference guide common API objects# OpenShift Container Platform 4.21 Common object reference
---
Reference guide common API objects## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentati... | <h1>OpenShift Container Platform 4.21</h1><h2>Common object reference</h2><p>Reference guide common API objects</p><h1>OpenShift Container Platform 4.21 Common object reference</h1><hr/><p>Reference guide common API objects</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text ... | [
{
"page_number": 1,
"error": false,
"token_count": 247,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 85,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Config_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/config_apis/OpenShift_Container_Platform-4.21-Config_APIs-en-US.pdf | success | 2026-04-15T17:07:03.372863+00:00 | 68.5 | 627 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Config APIs
Reference guide for config APIs# OpenShift Container Platform 4.21 Config APIs
---
Reference guide for config APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat und... | <h1>OpenShift Container Platform 4.21</h1><h2>Config APIs</h2><p>Reference guide for config APIs</p><h1>OpenShift Container Platform 4.21 Config APIs</h1><hr/><p>Reference guide for config APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this d... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Configuring_network_settings-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/configuring_network_settings/OpenShift_Container_Platform-4.21-Configuring_network_settings-en-US.pdf | success | 2026-04-15T17:08:08.859339+00:00 | 65.46 | 45 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Configuring network settings
General networking configuration processes in OpenShift Container Platform## OpenShift Container Platform 4.21 Configuring network settings
---
General networking configuration processes in OpenShift Container Platform## Legal Notice
Copyright © R... | <h1>OpenShift Container Platform 4.21</h1><h2>Configuring network settings</h2><p>General networking configuration processes in OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 Configuring network settings</h2><hr/><p>General networking configuration processes in OpenShift Container Platform</p><h2... | [
{
"page_number": 1,
"error": false,
"token_count": 252,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Console_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/console_apis/OpenShift_Container_Platform-4.21-Console_APIs-en-US.pdf | success | 2026-04-15T17:09:15.800368+00:00 | 66.92 | 107 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Console APIs
Reference guide for console APIs# OpenShift Container Platform 4.21 Console APIs
---
Reference guide for console APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat... | <h1>OpenShift Container Platform 4.21</h1><h2>Console APIs</h2><p>Reference guide for console APIs</p><h1>OpenShift Container Platform 4.21 Console APIs</h1><hr/><p>Reference guide for console APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in th... | [
{
"page_number": 1,
"error": false,
"token_count": 241,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Disconnected_environments-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/disconnected_environments/OpenShift_Container_Platform-4.21-Disconnected_environments-en-US.pdf | success | 2026-04-15T17:10:37.455191+00:00 | 81.63 | 194 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Disconnected environments
Managing OpenShift Container Platform clusters in a disconnected environment## OpenShift Container Platform 4.21 Disconnected environments
---
Managing OpenShift Container Platform clusters in a disconnected environment## Legal Notice
Copyright © Red... | <h1>OpenShift Container Platform 4.21</h1><h2>Disconnected environments</h2><p>Managing OpenShift Container Platform clusters in a disconnected environment</p><h2>OpenShift Container Platform 4.21 Disconnected environments</h2><hr/><p>Managing OpenShift Container Platform clusters in a disconnected environment</p><h2>L... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Edge_computing-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/edge_computing/OpenShift_Container_Platform-4.21-Edge_computing-en-US.pdf | success | 2026-04-15T17:11:55.931344+00:00 | 77.29 | 505 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Edge computing
Configure and deploy OpenShift Container Platform clusters at the network edge## OpenShift Container Platform 4.21 Edge computing
---
Configure and deploy OpenShift Container Platform clusters at the network edge## Legal Notice
Copyright © Red Hat.
Except as o... | <h1>OpenShift Container Platform 4.21</h1><h2>Edge computing</h2><p>Configure and deploy OpenShift Container Platform clusters at the network edge</p><h2>OpenShift Container Platform 4.21 Edge computing</h2><hr/><p>Configure and deploy OpenShift Container Platform clusters at the network edge</p><h2>Legal Notice</h2><p... | [
{
"page_number": 1,
"error": false,
"token_count": 252,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 91,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-etcd-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/etcd/OpenShift_Container_Platform-4.21-etcd-en-US.pdf | success | 2026-04-15T17:13:14.378465+00:00 | 78.42 | 99 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## etcd
Providing redundancy with etcd## OpenShift Container Platform 4.21 etcd
---
Providing redundancy with etcd## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative... | <h1>OpenShift Container Platform 4.21</h1><h2>etcd</h2><p>Providing redundancy with etcd</p><h2>OpenShift Container Platform 4.21 etcd</h2><hr/><p>Providing redundancy with etcd</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 85,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Extension_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/extension_apis/OpenShift_Container_Platform-4.21-Extension_APIs-en-US.pdf | success | 2026-04-15T17:14:21.957934+00:00 | 67.56 | 143 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Extension APIs
Reference guide for extension APIs# OpenShift Container Platform 4.21 Extension APIs
---
Reference guide for extension APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by... | <h1>OpenShift Container Platform 4.21</h1><h2>Extension APIs</h2><p>Reference guide for extension APIs</p><h1>OpenShift Container Platform 4.21 Extension APIs</h1><hr/><p>Reference guide for extension APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustratio... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Extensions-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/extensions/OpenShift_Container_Platform-4.21-Extensions-en-US.pdf | success | 2026-04-15T17:15:27.113051+00:00 | 65.13 | 118 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Extensions
Working with extensions in OpenShift Container Platform using Operator Lifecycle Manager (OLM) v1.## OpenShift Container Platform 4.21 Extensions
---
Working with extensions in OpenShift Container Platform using Operator Lifecycle Manager (OLM) v1.## Legal Notice
C... | <h1>OpenShift Container Platform 4.21</h1><h2>Extensions</h2><p>Working with extensions in OpenShift Container Platform using Operator Lifecycle Manager (OLM) v1.</p><h2>OpenShift Container Platform 4.21 Extensions</h2><hr/><p>Working with extensions in OpenShift Container Platform using Operator Lifecycle Manager (OLM... | [
{
"page_number": 1,
"error": false,
"token_count": 253,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 96,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-GitOps-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/gitops/OpenShift_Container_Platform-4.21-GitOps-en-US.pdf | success | 2026-04-15T17:15:39.586728+00:00 | 12.45 | 7 | 7 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## GitOps
A declarative way to implement continuous deployment for cloud native applications.## OpenShift Container Platform 4.21 GitOps
---
A declarative way to implement continuous deployment for cloud native applications.## Legal Notice
Copyright © Red Hat.
Except as otherwi... | <h1>OpenShift Container Platform 4.21</h1><h2>GitOps</h2><p>A declarative way to implement continuous deployment for cloud native applications.</p><h2>OpenShift Container Platform 4.21 GitOps</h2><hr/><p>A declarative way to implement continuous deployment for cloud native applications.</p><h2>Legal Notice</h2><p>Copyr... | [
{
"page_number": 1,
"error": false,
"token_count": 250,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Hardware_accelerators-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/hardware_accelerators/OpenShift_Container_Platform-4.21-Hardware_accelerators-en-US.pdf | success | 2026-04-15T17:16:52.199366+00:00 | 72.61 | 86 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Hardware accelerators
Hardware accelerators# OpenShift Container Platform 4.21 Hardware accelerators
---
Hardware accelerators## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat und... | <h1>OpenShift Container Platform 4.21</h1><h2>Hardware accelerators</h2><p>Hardware accelerators</p><h1>OpenShift Container Platform 4.21 Hardware accelerators</h1><hr/><p>Hardware accelerators</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this d... | [
{
"page_number": 1,
"error": false,
"token_count": 245,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 83,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Hardware_networks-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/hardware_networks/OpenShift_Container_Platform-4.21-Hardware_networks-en-US.pdf | success | 2026-04-15T17:18:04.608027+00:00 | 72.39 | 145 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Hardware networks
Configuring hardware-specific networking features in OpenShift Container Platform## OpenShift Container Platform 4.21 Hardware networks
---
Configuring hardware-specific networking features in OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
... | <h1>OpenShift Container Platform 4.21</h1><h2>Hardware networks</h2><p>Configuring hardware-specific networking features in OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 Hardware networks</h2><hr/><p>Configuring hardware-specific networking features in OpenShift Container Platform</p><h2>Legal N... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Hosted_control_planes-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/hosted_control_planes/OpenShift_Container_Platform-4.21-Hosted_control_planes-en-US.pdf | success | 2026-04-15T17:19:17.238259+00:00 | 72.61 | 438 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Hosted control planes
Using hosted control planes with OpenShift Container Platform## OpenShift Container Platform 4.21 Hosted control planes
---
Using hosted control planes with OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below... | <h1>OpenShift Container Platform 4.21</h1><h2>Hosted control planes</h2><p>Using hosted control planes with OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 Hosted control planes</h2><hr/><p>Using hosted control planes with OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat... | [
{
"page_number": 1,
"error": false,
"token_count": 248,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Image_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/image_apis/OpenShift_Container_Platform-4.21-Image_APIs-en-US.pdf | success | 2026-04-15T17:20:23.459970+00:00 | 66.2 | 186 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Image APIs
Reference guide for image APIs# OpenShift Container Platform 4.21 Image APIs
---
Reference guide for image APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under t... | <h1>OpenShift Container Platform 4.21</h1><h2>Image APIs</h2><p>Reference guide for image APIs</p><h1>OpenShift Container Platform 4.21 Image APIs</h1><hr/><p>Reference guide for image APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this docum... | [
{
"page_number": 1,
"error": false,
"token_count": 241,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Images-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/images/OpenShift_Container_Platform-4.21-Images-en-US.pdf | success | 2026-04-15T17:21:34.627794+00:00 | 71.14 | 111 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Images
Creating and managing images and imagestreams in OpenShift Container Platform# OpenShift Container Platform 4.21 Images
---
Creating and managing images and imagestreams in OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted belo... | <h1>OpenShift Container Platform 4.21</h1><h2>Images</h2><p>Creating and managing images and imagestreams in OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Images</h1><hr/><p>Creating and managing images and imagestreams in OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red H... | [
{
"page_number": 1,
"error": false,
"token_count": 250,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Ingress_and_load_balancing-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/ingress_and_load_balancing/OpenShift_Container_Platform-4.21-Ingress_and_load_balancing-en-US.pdf | success | 2026-04-15T17:22:49.782287+00:00 | 74 | 208 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Ingress and load balancing
Exposing services and managing external traffic in OpenShift Container Platform# OpenShift Container Platform 4.21 Ingress and load balancing
---
Exposing services and managing external traffic in OpenShift Container Platform## Legal Notice
Copyrigh... | <h1>OpenShift Container Platform 4.21</h1><h2>Ingress and load balancing</h2><p>Exposing services and managing external traffic in OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Ingress and load balancing</h1><hr/><p>Exposing services and managing external traffic in OpenShift Container Platform<... | [
{
"page_number": 1,
"error": false,
"token_count": 249,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 94,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installation_configuration-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installation_configuration/OpenShift_Container_Platform-4.21-Installation_configuration-en-US.pdf | success | 2026-04-15T17:23:58.655727+00:00 | 68.85 | 50 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installation configuration
Cluster-wide configuration during installations# OpenShift Container Platform 4.21 Installation configuration
---
Cluster-wide configuration during installations## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and i... | <h1>OpenShift Container Platform 4.21</h1><h2>Installation configuration</h2><p>Cluster-wide configuration during installations</p><h1>OpenShift Container Platform 4.21 Installation configuration</h1><hr/><p>Cluster-wide configuration during installations</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as ... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installation_overview-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installation_overview/OpenShift_Container_Platform-4.21-Installation_overview-en-US.pdf | success | 2026-04-15T17:25:06.333101+00:00 | 67.65 | 46 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installation overview
Overview content for installing OpenShift Container Platform# OpenShift Container Platform 4.21 Installation overview
---
Overview content for installing OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, t... | <h1>OpenShift Container Platform 4.21</h1><h2>Installation overview</h2><p>Overview content for installing OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Installation overview</h1><hr/><p>Overview content for installing OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.<... | [
{
"page_number": 1,
"error": false,
"token_count": 245,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 87,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_a_Two_Node_OpenShift_Cluster-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_a_two_node_openshift_cluster/OpenShift_Container_Platform-4.21-Installing_a_Two_Node_OpenShift_Cluster-en-US.pdf | success | 2026-04-15T17:25:49.170677+00:00 | 42.81 | 28 | 28 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing a Two Node OpenShift Cluster
Installing OpenShift Container Platform on two nodes# OpenShift Container Platform 4.21 Installing a Two Node OpenShift Cluster
---
Installing OpenShift Container Platform on two nodes## Legal Notice
Copyright © Red Hat.
Except as othe... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing a Two Node OpenShift Cluster</h2><p>Installing OpenShift Container Platform on two nodes</p><h1>OpenShift Container Platform 4.21 Installing a Two Node OpenShift Cluster</h1><hr/><p>Installing OpenShift Container Platform on two nodes</p><h2>Legal Notice</h2><p>C... | [
{
"page_number": 1,
"error": false,
"token_count": 254,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 93,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_an_on-premise_cluster_with_the_Agent-based_Installer-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_an_on-premise_cluster_with_the_agent-based_installer/OpenShift_Container_Platform-4.21-Installing_an_on-premise_cluster_with_the_Agent-based_Installer-en-US.pdf | success | 2026-04-15T17:26:52.395787+00:00 | 63.21 | 131 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing an on-premise cluster with the Agent-based Installer
Installing an on-premise OpenShift Container Platform cluster with the Agent-based Installer# OpenShift Container Platform 4.21 Installing an on-premise cluster with the Agent-based Installer
---
Installing an on-... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing an on-premise cluster with the Agent-based Installer</h2><p>Installing an on-premise OpenShift Container Platform cluster with the Agent-based Installer</p><h1>OpenShift Container Platform 4.21 Installing an on-premise cluster with the Agent-based Installer</h1><... | [
{
"page_number": 1,
"error": false,
"token_count": 264,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 104,
"num_chunks": 2
},
{
"page_number": 4,
"err... |
OpenShift_Container_Platform-4.21-Installing_IBM_Cloud_Bare_Metal_Classic-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_ibm_cloud_bare_metal_classic/OpenShift_Container_Platform-4.21-Installing_IBM_Cloud_Bare_Metal_Classic-en-US.pdf | success | 2026-04-15T17:27:51.051348+00:00 | 58.63 | 29 | 29 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing IBM Cloud Bare Metal (Classic)
Installing OpenShift Container Platform on IBM Cloud Bare Metal (Classic)# OpenShift Container Platform 4.21 Installing IBM Cloud Bare Metal (Classic)
---
Installing OpenShift Container Platform on IBM Cloud Bare Metal (Classic)## Lega... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing IBM Cloud Bare Metal (Classic)</h2><p>Installing OpenShift Container Platform on IBM Cloud Bare Metal (Classic)</p><h1>OpenShift Container Platform 4.21 Installing IBM Cloud Bare Metal (Classic)</h1><hr/><p>Installing OpenShift Container Platform on IBM Cloud Bar... | [
{
"page_number": 1,
"error": false,
"token_count": 257,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 97,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_a_single_node-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_a_single_node/OpenShift_Container_Platform-4.21-Installing_on_a_single_node-en-US.pdf | success | 2026-04-15T17:28:51.925344+00:00 | 60.85 | 37 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on a single node
Installing OpenShift Container Platform on a single node# OpenShift Container Platform 4.21 Installing on a single node
---
Installing OpenShift Container Platform on a single node## Legal Notice
Copyright © Red Hat.
Except as otherwise noted belo... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on a single node</h2><p>Installing OpenShift Container Platform on a single node</p><h1>OpenShift Container Platform 4.21 Installing on a single node</h1><hr/><p>Installing OpenShift Container Platform on a single node</p><h2>Legal Notice</h2><p>Copyright © Red H... | [
{
"page_number": 1,
"error": false,
"token_count": 253,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 91,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_Alibaba_Cloud-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_alibaba_cloud/OpenShift_Container_Platform-4.21-Installing_on_Alibaba_Cloud-en-US.pdf | success | 2026-04-15T17:29:10.553768+00:00 | 18.6 | 8 | 8 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on Alibaba Cloud
Installing OpenShift Container Platform on Alibaba Cloud# OpenShift Container Platform 4.21 Installing on Alibaba Cloud
---
Installing OpenShift Container Platform on Alibaba Cloud## Legal Notice
Copyright © Red Hat.
Except as otherwise noted belo... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on Alibaba Cloud</h2><p>Installing OpenShift Container Platform on Alibaba Cloud</p><h1>OpenShift Container Platform 4.21 Installing on Alibaba Cloud</h1><hr/><p>Installing OpenShift Container Platform on Alibaba Cloud</p><h2>Legal Notice</h2><p>Copyright © Red H... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 89,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_any_platform-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_any_platform/OpenShift_Container_Platform-4.21-Installing_on_any_platform-en-US.pdf | success | 2026-04-15T17:30:20.985522+00:00 | 70.43 | 72 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on any platform
Installing OpenShift Container Platform on any platform# OpenShift Container Platform 4.21 Installing on any platform
---
Installing OpenShift Container Platform on any platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, t... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on any platform</h2><p>Installing OpenShift Container Platform on any platform</p><h1>OpenShift Container Platform 4.21 Installing on any platform</h1><hr/><p>Installing OpenShift Container Platform on any platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.<... | [
{
"page_number": 1,
"error": false,
"token_count": 251,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 89,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_AWS-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_aws/OpenShift_Container_Platform-4.21-Installing_on_AWS-en-US.pdf | success | 2026-04-15T17:31:33.037961+00:00 | 72.03 | 564 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on AWS
Installing OpenShift Container Platform on Amazon Web Services# OpenShift Container Platform 4.21 Installing on AWS
---
Installing OpenShift Container Platform on Amazon Web Services## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the t... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on AWS</h2><p>Installing OpenShift Container Platform on Amazon Web Services</p><h1>OpenShift Container Platform 4.21 Installing on AWS</h1><hr/><p>Installing OpenShift Container Platform on Amazon Web Services</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><... | [
{
"page_number": 1,
"error": false,
"token_count": 250,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 89,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_Azure-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_azure/OpenShift_Container_Platform-4.21-Installing_on_Azure-en-US.pdf | success | 2026-04-15T17:32:46.327090+00:00 | 72.13 | 425 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on Azure
Installing OpenShift Container Platform on Azure# OpenShift Container Platform 4.21 Installing on Azure
---
Installing OpenShift Container Platform on Azure## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on Azure</h2><p>Installing OpenShift Container Platform on Azure</p><h1>OpenShift Container Platform 4.21 Installing on Azure</h1><hr/><p>Installing OpenShift Container Platform on Azure</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise no... | [
{
"page_number": 1,
"error": false,
"token_count": 249,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 87,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_Azure_Stack_Hub-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_azure_stack_hub/OpenShift_Container_Platform-4.21-Installing_on_Azure_Stack_Hub-en-US.pdf | success | 2026-04-15T17:33:57.038684+00:00 | 70.69 | 132 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on Azure Stack Hub
Installing OpenShift Container Platform on Azure Stack Hub# OpenShift Container Platform 4.21 Installing on Azure Stack Hub
---
Installing OpenShift Container Platform on Azure Stack Hub## Legal Notice
Copyright © Red Hat.
Except as otherwise no... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on Azure Stack Hub</h2><p>Installing OpenShift Container Platform on Azure Stack Hub</p><h1>OpenShift Container Platform 4.21 Installing on Azure Stack Hub</h1><hr/><p>Installing OpenShift Container Platform on Azure Stack Hub</p><h2>Legal Notice</h2><p>Copyright... | [
{
"page_number": 1,
"error": false,
"token_count": 252,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 91,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_bare_metal-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_bare_metal/OpenShift_Container_Platform-4.21-Installing_on_bare_metal-en-US.pdf | success | 2026-04-15T17:35:15.971979+00:00 | 78.91 | 553 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on bare metal
Installing OpenShift Container Platform on bare metal# OpenShift Container Platform 4.21 Installing on bare metal
---
Installing OpenShift Container Platform on bare metal## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text ... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on bare metal</h2><p>Installing OpenShift Container Platform on bare metal</p><h1>OpenShift Container Platform 4.21 Installing on bare metal</h1><hr/><p>Installing OpenShift Container Platform on bare metal</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Ex... | [
{
"page_number": 1,
"error": false,
"token_count": 251,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 89,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_Google_Cloud-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_google_cloud/OpenShift_Container_Platform-4.21-Installing_on_Google_Cloud-en-US.pdf | success | 2026-04-15T17:36:34.534689+00:00 | 78.54 | 476 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on Google Cloud
Installing OpenShift Container Platform on Google Cloud# OpenShift Container Platform 4.21 Installing on Google Cloud
---
Installing OpenShift Container Platform on Google Cloud## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, t... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on Google Cloud</h2><p>Installing OpenShift Container Platform on Google Cloud</p><h1>OpenShift Container Platform 4.21 Installing on Google Cloud</h1><hr/><p>Installing OpenShift Container Platform on Google Cloud</p><h2>Legal Notice</h2><p>Copyright © Red Hat.<... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 89,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_IBM_Cloud-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_ibm_cloud/OpenShift_Container_Platform-4.21-Installing_on_IBM_Cloud-en-US.pdf | success | 2026-04-15T17:37:40.099578+00:00 | 65.54 | 133 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on IBM Cloud
Installing OpenShift Container Platform on IBM Cloud Bare Metal (Classic)# OpenShift Container Platform 4.21 Installing on IBM Cloud
---
Installing OpenShift Container Platform on IBM Cloud Bare Metal (Classic)## Legal Notice
Copyright © Red Hat.
Exce... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on IBM Cloud</h2><p>Installing OpenShift Container Platform on IBM Cloud Bare Metal (Classic)</p><h1>OpenShift Container Platform 4.21 Installing on IBM Cloud</h1><hr/><p>Installing OpenShift Container Platform on IBM Cloud Bare Metal (Classic)</p><h2>Legal Notic... | [
{
"page_number": 1,
"error": false,
"token_count": 255,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 93,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_IBM_Power-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_ibm_power/OpenShift_Container_Platform-4.21-Installing_on_IBM_Power-en-US.pdf | success | 2026-04-15T17:38:55.255066+00:00 | 75.13 | 147 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on IBM Power
Installing OpenShift Container Platform on IBM Power# OpenShift Container Platform 4.21 Installing on IBM Power
---
Installing OpenShift Container Platform on IBM Power## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of a... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on IBM Power</h2><p>Installing OpenShift Container Platform on IBM Power</p><h1>OpenShift Container Platform 4.21 Installing on IBM Power</h1><hr/><p>Installing OpenShift Container Platform on IBM Power</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except... | [
{
"page_number": 1,
"error": false,
"token_count": 251,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 89,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_IBM_Power_Virtual_Server-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_ibm_power_virtual_server/OpenShift_Container_Platform-4.21-Installing_on_IBM_Power_Virtual_Server-en-US.pdf | success | 2026-04-15T17:40:05.119606+00:00 | 69.84 | 108 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on IBM Power Virtual Server
Installing OpenShift Container Platform on IBM Power Virtual Server# OpenShift Container Platform 4.21 Installing on IBM Power Virtual Server
---
Installing OpenShift Container Platform on IBM Power Virtual Server## Legal Notice
Copyrigh... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on IBM Power Virtual Server</h2><p>Installing OpenShift Container Platform on IBM Power Virtual Server</p><h1>OpenShift Container Platform 4.21 Installing on IBM Power Virtual Server</h1><hr/><p>Installing OpenShift Container Platform on IBM Power Virtual Server<... | [
{
"page_number": 1,
"error": false,
"token_count": 255,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 93,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_IBM_PowerVC-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_ibm_powervc/OpenShift_Container_Platform-4.21-Installing_on_IBM_PowerVC-en-US.pdf | success | 2026-04-15T17:41:01.300765+00:00 | 56.16 | 31 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on IBM PowerVC
Installing OpenShift Container Platform on IBM PowerVC# OpenShift Container Platform 4.21 Installing on IBM PowerVC
---
Installing OpenShift Container Platform on IBM PowerVC## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the t... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on IBM PowerVC</h2><p>Installing OpenShift Container Platform on IBM PowerVC</p><h1>OpenShift Container Platform 4.21 Installing on IBM PowerVC</h1><hr/><p>Installing OpenShift Container Platform on IBM PowerVC</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><... | [
{
"page_number": 1,
"error": false,
"token_count": 253,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 91,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_IBM_Z_and_IBM_LinuxONE-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_ibm_z_and_ibm_linuxone/OpenShift_Container_Platform-4.21-Installing_on_IBM_Z_and_IBM_LinuxONE-en-US.pdf | success | 2026-04-15T17:42:15.260309+00:00 | 73.94 | 323 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on IBM Z and IBM LinuxONE
Installing OpenShift Container Platform on IBM Z and IBM LinuxONE# OpenShift Container Platform 4.21 Installing on IBM Z and IBM LinuxONE
---
Installing OpenShift Container Platform on IBM Z and IBM LinuxONE## Legal Notice
Copyright © Red ... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on IBM Z and IBM LinuxONE</h2><p>Installing OpenShift Container Platform on IBM Z and IBM LinuxONE</p><h1>OpenShift Container Platform 4.21 Installing on IBM Z and IBM LinuxONE</h1><hr/><p>Installing OpenShift Container Platform on IBM Z and IBM LinuxONE</p><h2>L... | [
{
"page_number": 1,
"error": false,
"token_count": 254,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 97,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_Nutanix-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_nutanix/OpenShift_Container_Platform-4.21-Installing_on_Nutanix-en-US.pdf | success | 2026-04-15T17:43:26.914498+00:00 | 71.63 | 102 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on Nutanix
Installing OpenShift Container Platform on Nutanix# OpenShift Container Platform 4.21 Installing on Nutanix
---
Installing OpenShift Container Platform on Nutanix## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illus... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on Nutanix</h2><p>Installing OpenShift Container Platform on Nutanix</p><h1>OpenShift Container Platform 4.21 Installing on Nutanix</h1><hr/><p>Installing OpenShift Container Platform on Nutanix</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as othe... | [
{
"page_number": 1,
"error": false,
"token_count": 253,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 91,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_OpenStack-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_openstack/OpenShift_Container_Platform-4.21-Installing_on_OpenStack-en-US.pdf | success | 2026-04-15T17:44:45.159536+00:00 | 77.07 | 185 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on OpenStack
Installing OpenShift Container Platform on OpenStack# OpenShift Container Platform 4.21 Installing on OpenStack
---
Installing OpenShift Container Platform on OpenStack## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of a... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on OpenStack</h2><p>Installing OpenShift Container Platform on OpenStack</p><h1>OpenShift Container Platform 4.21 Installing on OpenStack</h1><hr/><p>Installing OpenShift Container Platform on OpenStack</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except... | [
{
"page_number": 1,
"error": false,
"token_count": 247,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 89,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_Oracle_Database_Appliance-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_oracle_database_appliance/OpenShift_Container_Platform-4.21-Installing_on_Oracle_Database_Appliance-en-US.pdf | success | 2026-04-15T17:45:08.249366+00:00 | 23.07 | 10 | 10 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on Oracle Database Appliance
Installing OpenShift Container Platform on Installing on Oracle Database Appliance# OpenShift Container Platform 4.21 Installing on Oracle Database Appliance
---
Installing OpenShift Container Platform on Installing on Oracle Database Ap... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on Oracle Database Appliance</h2><p>Installing OpenShift Container Platform on Installing on Oracle Database Appliance</p><h1>OpenShift Container Platform 4.21 Installing on Oracle Database Appliance</h1><hr/><p>Installing OpenShift Container Platform on Installi... | [
{
"page_number": 1,
"error": false,
"token_count": 256,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 96,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_Oracle_Distributed_Cloud-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_oracle_distributed_cloud/OpenShift_Container_Platform-4.21-Installing_on_Oracle_Distributed_Cloud-en-US.pdf | success | 2026-04-15T17:46:18.178558+00:00 | 69.93 | 31 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on Oracle Distributed Cloud
Installing OpenShift Container Platform on Oracle Distributed Cloud# OpenShift Container Platform 4.21 Installing on Oracle Distributed Cloud
---
Installing OpenShift Container Platform on Oracle Distributed Cloud## Legal Notice
Copyrigh... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on Oracle Distributed Cloud</h2><p>Installing OpenShift Container Platform on Oracle Distributed Cloud</p><h1>OpenShift Container Platform 4.21 Installing on Oracle Distributed Cloud</h1><hr/><p>Installing OpenShift Container Platform on Oracle Distributed Cloud<... | [
{
"page_number": 1,
"error": false,
"token_count": 249,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 91,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_Oracle_Edge_Cloud-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_oracle_edge_cloud/OpenShift_Container_Platform-4.21-Installing_on_Oracle_Edge_Cloud-en-US.pdf | success | 2026-04-15T17:46:59.492435+00:00 | 41.29 | 27 | 27 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on Oracle Edge Cloud
Installing OpenShift Container Platform on Oracle Edge Cloud# OpenShift Container Platform 4.21 Installing on Oracle Edge Cloud
---
Installing OpenShift Container Platform on Oracle Edge Cloud## Legal Notice
Copyright © Red Hat.
Except as othe... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on Oracle Edge Cloud</h2><p>Installing OpenShift Container Platform on Oracle Edge Cloud</p><h1>OpenShift Container Platform 4.21 Installing on Oracle Edge Cloud</h1><hr/><p>Installing OpenShift Container Platform on Oracle Edge Cloud</p><h2>Legal Notice</h2><p>C... | [
{
"page_number": 1,
"error": false,
"token_count": 253,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 91,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on_VMware_vSphere-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on_vmware_vsphere/OpenShift_Container_Platform-4.21-Installing_on_VMware_vSphere-en-US.pdf | success | 2026-04-15T17:48:05.014625+00:00 | 65.51 | 340 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on VMware vSphere
Installing OpenShift Container Platform on vSphere# OpenShift Container Platform 4.21 Installing on VMware vSphere
---
Installing OpenShift Container Platform on vSphere## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the tex... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on VMware vSphere</h2><p>Installing OpenShift Container Platform on vSphere</p><h1>OpenShift Container Platform 4.21 Installing on VMware vSphere</h1><hr/><p>Installing OpenShift Container Platform on vSphere</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>... | [
{
"page_number": 1,
"error": false,
"token_count": 252,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Installing_on-premise_with_Assisted_Installer-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/installing_on-premise_with_assisted_installer/OpenShift_Container_Platform-4.21-Installing_on-premise_with_Assisted_Installer-en-US.pdf | success | 2026-04-15T17:48:16.941439+00:00 | 11.9 | 7 | 7 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Installing on-premise with Assisted Installer
Installing OpenShift Container Platform on-premise with the Assisted Installer# OpenShift Container Platform 4.21 Installing on-premise with Assisted Installer
---
Installing OpenShift Container Platform on-premise with the Assiste... | <h1>OpenShift Container Platform 4.21</h1><h2>Installing on-premise with Assisted Installer</h2><p>Installing OpenShift Container Platform on-premise with the Assisted Installer</p><h1>OpenShift Container Platform 4.21 Installing on-premise with Assisted Installer</h1><hr/><p>Installing OpenShift Container Platform on-... | [
{
"page_number": 1,
"error": false,
"token_count": 256,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 99,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Jenkins-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/jenkins/OpenShift_Container_Platform-4.21-Jenkins-en-US.pdf | success | 2026-04-15T17:49:28.026260+00:00 | 71.08 | 44 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Jenkins
Jenkins# OpenShift Container Platform 4.21 Jenkins
---
Jenkins## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unpo... | <h1>OpenShift Container Platform 4.21</h1><h2>Jenkins</h2><p>Jenkins</p><h1>OpenShift Container Platform 4.21 Jenkins</h1><hr/><p>Jenkins</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative ... | [
{
"page_number": 1,
"error": false,
"token_count": 240,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 79,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Kubernetes_NMState-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/kubernetes_nmstate/OpenShift_Container_Platform-4.21-Kubernetes_NMState-en-US.pdf | success | 2026-04-15T17:50:35.324755+00:00 | 67.28 | 45 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Kubernetes NMState
Observing and updating node network state and configuration using Kubernetes NMState in OpenShift Container Platform## OpenShift Container Platform 4.21 Kubernetes NMState
---
Observing and updating node network state and configuration using Kubernetes NMSta... | <h1>OpenShift Container Platform 4.21</h1><h2>Kubernetes NMState</h2><p>Observing and updating node network state and configuration using Kubernetes NMState in OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 Kubernetes NMState</h2><hr/><p>Observing and updating node network state and configuration... | [
{
"page_number": 1,
"error": false,
"token_count": 255,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 98,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Logging-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/logging/OpenShift_Container_Platform-4.21-Logging-en-US.pdf | success | 2026-04-15T17:50:47.682247+00:00 | 12.33 | 7 | 7 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Logging
Configuring and using logging in OpenShift Container Platform# OpenShift Container Platform 4.21 Logging
---
Configuring and using logging in OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustratio... | <h1>OpenShift Container Platform 4.21</h1><h2>Logging</h2><p>Configuring and using logging in OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Logging</h1><hr/><p>Configuring and using logging in OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise ... | [
{
"page_number": 1,
"error": false,
"token_count": 245,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 88,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Machine_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/machine_apis/OpenShift_Container_Platform-4.21-Machine_APIs-en-US.pdf | success | 2026-04-15T17:51:59.451365+00:00 | 71.77 | 321 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Machine APIs
Reference guide for machine APIs# OpenShift Container Platform 4.21 Machine APIs
---
Reference guide for machine APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat... | <h1>OpenShift Container Platform 4.21</h1><h2>Machine APIs</h2><p>Reference guide for machine APIs</p><h1>OpenShift Container Platform 4.21 Machine APIs</h1><hr/><p>Reference guide for machine APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in th... | [
{
"page_number": 1,
"error": false,
"token_count": 242,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Machine_configuration-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/machine_configuration/OpenShift_Container_Platform-4.21-Machine_configuration-en-US.pdf | success | 2026-04-15T18:01:50.748655+00:00 | 578.65 | 130 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Machine configuration
Managing and applying configuration and updates of the base operating system and container runtimes in OpenShift Container Platform## OpenShift Container Platform 4.21 Machine configuration
---
Managing and applying configuration and updates of the base o... | <h1>OpenShift Container Platform 4.21</h1><h2>Machine configuration</h2><p>Managing and applying configuration and updates of the base operating system and container runtimes in OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 Machine configuration</h2><hr/><p>Managing and applying configuration an... | [
{
"page_number": 1,
"error": false,
"token_count": 260,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 99,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Machine_management-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/machine_management/OpenShift_Container_Platform-4.21-Machine_management-en-US.pdf | success | 2026-04-15T18:03:15.700638+00:00 | 84.93 | 377 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Machine management
Adding and maintaining cluster machines# OpenShift Container Platform 4.21 Machine management
---
Adding and maintaining cluster machines## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentati... | <h1>OpenShift Container Platform 4.21</h1><h2>Machine management</h2><p>Adding and maintaining cluster machines</p><h1>OpenShift Container Platform 4.21 Machine management</h1><hr/><p>Adding and maintaining cluster machines</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text ... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Metadata_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/metadata_apis/OpenShift_Container_Platform-4.21-Metadata_APIs-en-US.pdf | success | 2026-04-15T18:04:21.312622+00:00 | 65.59 | 103 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Metadata APIs
Reference guide for metadata APIs# OpenShift Container Platform 4.21 Metadata APIs
---
Reference guide for metadata APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red... | <h1>OpenShift Container Platform 4.21</h1><h2>Metadata APIs</h2><p>Reference guide for metadata APIs</p><h1>OpenShift Container Platform 4.21 Metadata APIs</h1><hr/><p>Reference guide for metadata APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations i... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Migrating_from_version_3_to_4-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/migrating_from_version_3_to_4/OpenShift_Container_Platform-4.21-Migrating_from_version_3_to_4-en-US.pdf | success | 2026-04-15T18:05:02.453892+00:00 | 41.12 | 17 | 17 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Migrating from version 3 to 4
Migrating to OpenShift Container Platform 4# OpenShift Container Platform 4.21 Migrating from version 3 to 4
---
Migrating to OpenShift Container Platform 4## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and ill... | <h1>OpenShift Container Platform 4.21</h1><h2>Migrating from version 3 to 4</h2><p>Migrating to OpenShift Container Platform 4</p><h1>OpenShift Container Platform 4.21 Migrating from version 3 to 4</h1><hr/><p>Migrating to OpenShift Container Platform 4</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as ot... | [
{
"page_number": 1,
"error": false,
"token_count": 253,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 95,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Monitoring-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/monitoring/OpenShift_Container_Platform-4.21-Monitoring-en-US.pdf | success | 2026-04-15T18:05:15.224007+00:00 | 12.76 | 7 | 7 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Monitoring
Configuring and using the monitoring stack in OpenShift Container Platform# OpenShift Container Platform 4.21 Monitoring
---
Configuring and using the monitoring stack in OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted be... | <h1>OpenShift Container Platform 4.21</h1><h2>Monitoring</h2><p>Configuring and using the monitoring stack in OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Monitoring</h1><hr/><p>Configuring and using the monitoring stack in OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red... | [
{
"page_number": 1,
"error": false,
"token_count": 252,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Monitoring_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/monitoring_apis/OpenShift_Container_Platform-4.21-Monitoring_APIs-en-US.pdf | success | 2026-04-15T18:06:57.415091+00:00 | 102.19 | 1,778 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Monitoring APIs
Reference guide for monitoring APIs# OpenShift Container Platform 4.21 Monitoring APIs
---
Reference guide for monitoring APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are license... | <h1>OpenShift Container Platform 4.21</h1><h2>Monitoring APIs</h2><p>Reference guide for monitoring APIs</p><h1>OpenShift Container Platform 4.21 Monitoring APIs</h1><hr/><p>Reference guide for monitoring APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustr... | [
{
"page_number": 1,
"error": false,
"token_count": 242,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Multiple_networks-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/multiple_networks/OpenShift_Container_Platform-4.21-Multiple_networks-en-US.pdf | success | 2026-04-15T18:08:08.984998+00:00 | 71.56 | 136 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Multiple networks
Configuring and managing multiple network interfaces and virtual routing in
OpenShift Container Platform## OpenShift Container Platform 4.21 Multiple networks
---
Configuring and managing multiple network interfaces and virtual routing in OpenShift Containe... | <h1>OpenShift Container Platform 4.21</h1><h2>Multiple networks</h2><p>Configuring and managing multiple network interfaces and virtual routing in<br/>OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 Multiple networks</h2><hr/><p>Configuring and managing multiple network interfaces and virtual rout... | [
{
"page_number": 1,
"error": false,
"token_count": 257,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 94,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Network_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/network_apis/OpenShift_Container_Platform-4.21-Network_APIs-en-US.pdf | success | 2026-04-15T18:09:29.016776+00:00 | 80.02 | 762 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Network APIs
Reference guide for network APIs# OpenShift Container Platform 4.21 Network APIs
---
Reference guide for network APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat... | <h1>OpenShift Container Platform 4.21</h1><h2>Network APIs</h2><p>Reference guide for network APIs</p><h1>OpenShift Container Platform 4.21 Network APIs</h1><hr/><p>Reference guide for network APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in th... | [
{
"page_number": 1,
"error": false,
"token_count": 241,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Network_Observability-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/network_observability/OpenShift_Container_Platform-4.21-Network_Observability-en-US.pdf | success | 2026-04-15T18:10:54.604912+00:00 | 85.57 | 275 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Network Observability
Configuring and using the Network Observability Operator in OpenShift Container Platform# OpenShift Container Platform 4.21 Network Observability
---
Configuring and using the Network Observability Operator in OpenShift Container Platform## Legal Notice
... | <h1>OpenShift Container Platform 4.21</h1><h2>Network Observability</h2><p>Configuring and using the Network Observability Operator in OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Network Observability</h1><hr/><p>Configuring and using the Network Observability Operator in OpenShift Container P... | [
{
"page_number": 1,
"error": false,
"token_count": 255,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 94,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Network_security-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/network_security/OpenShift_Container_Platform-4.21-Network_security-en-US.pdf | success | 2026-04-15T18:12:00.236106+00:00 | 65.62 | 109 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Network security
Securing network traffic and enforcing network policies in OpenShift Container Platform## OpenShift Container Platform 4.21 Network security
---
Securing network traffic and enforcing network policies in OpenShift Container Platform## Legal Notice
Copyright ©... | <h1>OpenShift Container Platform 4.21</h1><h2>Network security</h2><p>Securing network traffic and enforcing network policies in OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 Network security</h2><hr/><p>Securing network traffic and enforcing network policies in OpenShift Container Platform</p><... | [
{
"page_number": 1,
"error": false,
"token_count": 252,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 92,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Networking_Operators-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/networking_operators/OpenShift_Container_Platform-4.21-Networking_Operators-en-US.pdf | success | 2026-04-15T18:13:25.840837+00:00 | 73.28 | 211 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Networking Operators
Managing networking-specific Operators in OpenShift Container Platform# OpenShift Container Platform 4.21 Networking Operators
---
Managing networking-specific Operators in OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherw... | <h1>OpenShift Container Platform 4.21</h1><h2>Networking Operators</h2><p>Managing networking-specific Operators in OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Networking Operators</h1><hr/><p>Managing networking-specific Operators in OpenShift Container Platform</p><h2>Legal Notice</h2><p>Cop... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 88,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Networking_overview-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/networking_overview/OpenShift_Container_Platform-4.21-Networking_overview-en-US.pdf | success | 2026-04-15T18:13:53.238465+00:00 | 27.38 | 14 | 14 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Networking overview
Understanding fundamental networking concepts and general tasks in OpenShift Container Platform## OpenShift Container Platform 4.21 Networking overview
---
Understanding fundamental networking concepts and general tasks in OpenShift Container Platform## Leg... | <h1>OpenShift Container Platform 4.21</h1><h2>Networking overview</h2><p>Understanding fundamental networking concepts and general tasks in OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 Networking overview</h2><hr/><p>Understanding fundamental networking concepts and general tasks in OpenShift C... | [
{
"page_number": 1,
"error": false,
"token_count": 251,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 91,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Node_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/node_apis/OpenShift_Container_Platform-4.21-Node_APIs-en-US.pdf | success | 2026-04-15T18:15:00.286209+00:00 | 67.04 | 94 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Node APIs
Reference guide for node APIs# OpenShift Container Platform 4.21 Node APIs
---
Reference guide for node APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the C... | <h1>OpenShift Container Platform 4.21</h1><h2>Node APIs</h2><p>Reference guide for node APIs</p><h1>OpenShift Container Platform 4.21 Node APIs</h1><hr/><p>Reference guide for node APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documenta... | [
{
"page_number": 1,
"error": false,
"token_count": 242,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Nodes-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/nodes/OpenShift_Container_Platform-4.21-Nodes-en-US.pdf | success | 2026-04-15T18:16:23.380177+00:00 | 83.08 | 603 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Nodes
Configuring and managing nodes in OpenShift Container Platform# OpenShift Container Platform 4.21 Nodes
---
Configuring and managing nodes in OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations... | <h1>OpenShift Container Platform 4.21</h1><h2>Nodes</h2><p>Configuring and managing nodes in OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Nodes</h1><hr/><p>Configuring and managing nodes in OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise no... | [
{
"page_number": 1,
"error": false,
"token_count": 249,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 88,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-OAuth_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/oauth_apis/OpenShift_Container_Platform-4.21-OAuth_APIs-en-US.pdf | success | 2026-04-15T18:17:27.118131+00:00 | 63.72 | 50 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## OAuth APIs
Reference guide for OAuth APIs# OpenShift Container Platform 4.21 OAuth APIs
---
Reference guide for OAuth APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under t... | <h1>OpenShift Container Platform 4.21</h1><h2>OAuth APIs</h2><p>Reference guide for OAuth APIs</p><h1>OpenShift Container Platform 4.21 OAuth APIs</h1><hr/><p>Reference guide for OAuth APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this docum... | [
{
"page_number": 1,
"error": false,
"token_count": 241,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Observability_overview-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/observability_overview/OpenShift_Container_Platform-4.21-Observability_overview-en-US.pdf | success | 2026-04-15T18:17:45.765486+00:00 | 18.63 | 8 | 8 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Observability overview
Contains information about observability for OpenShift Container Platform## OpenShift Container Platform 4.21 Observability overview
---
Contains information about observability for OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Excep... | <h1>OpenShift Container Platform 4.21</h1><h2>Observability overview</h2><p>Contains information about observability for OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 Observability overview</h2><hr/><p>Contains information about observability for OpenShift Container Platform</p><h2>Legal Notice<... | [
{
"page_number": 1,
"error": false,
"token_count": 251,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-OpenShift_Lightspeed-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/openshift_lightspeed/OpenShift_Container_Platform-4.21-OpenShift_Lightspeed-en-US.pdf | success | 2026-04-15T18:17:57.761417+00:00 | 11.99 | 7 | 7 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## OpenShift Lightspeed
About OpenShift Lightspeed# OpenShift Container Platform 4.21 OpenShift Lightspeed
---
About OpenShift Lightspeed## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red... | <h1>OpenShift Container Platform 4.21</h1><h2>OpenShift Lightspeed</h2><p>About OpenShift Lightspeed</p><h1>OpenShift Container Platform 4.21 OpenShift Lightspeed</h1><hr/><p>About OpenShift Lightspeed</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations i... | [
{
"page_number": 1,
"error": false,
"token_count": 243,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 85,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-OpenShift_sandboxed_containers-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/openshift_sandboxed_containers/OpenShift_Container_Platform-4.21-OpenShift_sandboxed_containers-en-US.pdf | success | 2026-04-15T18:18:09.781531+00:00 | 12.02 | 7 | 7 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## OpenShift sandboxed containers
OpenShift sandboxed containers guide# OpenShift Container Platform 4.21 OpenShift sandboxed containers
---
OpenShift sandboxed containers guide## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations i... | <h1>OpenShift Container Platform 4.21</h1><h2>OpenShift sandboxed containers</h2><p>OpenShift sandboxed containers guide</p><h1>OpenShift Container Platform 4.21 OpenShift sandboxed containers</h1><hr/><p>OpenShift sandboxed containers guide</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise note... | [
{
"page_number": 1,
"error": false,
"token_count": 250,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 88,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Operator_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/operator_apis/OpenShift_Container_Platform-4.21-Operator_APIs-en-US.pdf | success | 2026-04-15T18:19:27.529975+00:00 | 77.75 | 748 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Operator APIs
Reference guide for Operator APIs# OpenShift Container Platform 4.21 Operator APIs
---
Reference guide for Operator APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red... | <h1>OpenShift Container Platform 4.21</h1><h2>Operator APIs</h2><p>Reference guide for Operator APIs</p><h1>OpenShift Container Platform 4.21 Operator APIs</h1><hr/><p>Reference guide for Operator APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations i... | [
{
"page_number": 1,
"error": false,
"token_count": 242,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-OperatorHub_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/operatorhub_apis/OpenShift_Container_Platform-4.21-OperatorHub_APIs-en-US.pdf | success | 2026-04-15T18:20:43.825142+00:00 | 76.28 | 719 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## OperatorHub APIs
Reference guide for OperatorHub APIs# OpenShift Container Platform 4.21 OperatorHub APIs
---
Reference guide for OperatorHub APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are lic... | <h1>OpenShift Container Platform 4.21</h1><h2>OperatorHub APIs</h2><p>Reference guide for OperatorHub APIs</p><h1>OpenShift Container Platform 4.21 OperatorHub APIs</h1><hr/><p>Reference guide for OperatorHub APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and ill... | [
{
"page_number": 1,
"error": false,
"token_count": 243,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 86,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Operators-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/operators/OpenShift_Container_Platform-4.21-Operators-en-US.pdf | success | 2026-04-15T18:21:55.407190+00:00 | 70.11 | 223 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Operators
Working with Operators in OpenShift Container Platform# OpenShift Container Platform 4.21 Operators
---
Working with Operators in OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this... | <h1>OpenShift Container Platform 4.21</h1><h2>Operators</h2><p>Working with Operators in OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Operators</h1><hr/><p>Working with Operators in OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted belo... | [
{
"page_number": 1,
"error": false,
"token_count": 243,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 86,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Overview-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/overview/OpenShift_Container_Platform-4.21-Overview-en-US.pdf | success | 2026-04-15T18:23:10.730137+00:00 | 75.31 | 44 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Overview
Introduction to OpenShift Container Platform# OpenShift Container Platform 4.21 Overview
---
Introduction to OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are lic... | <h1>OpenShift Container Platform 4.21</h1><h2>Overview</h2><p>Introduction to OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Overview</h1><hr/><p>Introduction to OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and ill... | [
{
"page_number": 1,
"error": false,
"token_count": 245,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-OVN-Kubernetes_network_plugin-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/ovn-kubernetes_network_plugin/OpenShift_Container_Platform-4.21-OVN-Kubernetes_network_plugin-en-US.pdf | success | 2026-04-15T18:24:36.615866+00:00 | 85.88 | 105 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## OVN-Kubernetes network plugin
In-depth configuration and troubleshooting for the OVN-Kubernetes network plugin
in OpenShift Container Platform## OpenShift Container Platform 4.21 OVN-Kubernetes network plugin
---
In-depth configuration and troubleshooting for the OVN-Kuberne... | <h1>OpenShift Container Platform 4.21</h1><h2>OVN-Kubernetes network plugin</h2><p>In-depth configuration and troubleshooting for the OVN-Kubernetes network plugin<br/>in OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 OVN-Kubernetes network plugin</h2><hr/><p>In-depth configuration and troublesho... | [
{
"page_number": 1,
"error": false,
"token_count": 263,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 100,
"num_chunks": 2
},
{
"page_number": 4,
"err... |
OpenShift_Container_Platform-4.21-Pipelines-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/pipelines/OpenShift_Container_Platform-4.21-Pipelines-en-US.pdf | success | 2026-04-15T18:24:48.983567+00:00 | 12.36 | 7 | 7 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Pipelines
Contains information about Pipelines for OpenShift Container Platform# OpenShift Container Platform 4.21 Pipelines
---
Contains information about Pipelines for OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the tex... | <h1>OpenShift Container Platform 4.21</h1><h2>Pipelines</h2><p>Contains information about Pipelines for OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Pipelines</h1><hr/><p>Contains information about Pipelines for OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>... | [
{
"page_number": 1,
"error": false,
"token_count": 249,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 89,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Policy_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/policy_apis/OpenShift_Container_Platform-4.21-Policy_APIs-en-US.pdf | success | 2026-04-15T18:25:27.066476+00:00 | 38.08 | 26 | 26 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Policy APIs
Reference guide for policy APIs# OpenShift Container Platform 4.21 Policy APIs
---
Reference guide for policy APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat und... | <h1>OpenShift Container Platform 4.21</h1><h2>Policy APIs</h2><p>Reference guide for policy APIs</p><h1>OpenShift Container Platform 4.21 Policy APIs</h1><hr/><p>Reference guide for policy APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this d... | [
{
"page_number": 1,
"error": false,
"token_count": 245,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Postinstallation_configuration-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/postinstallation_configuration/OpenShift_Container_Platform-4.21-Postinstallation_configuration-en-US.pdf | success | 2026-04-15T18:26:41.647561+00:00 | 74.58 | 421 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Postinstallation configuration
Day 2 operations for OpenShift Container Platform# OpenShift Container Platform 4.21 Postinstallation configuration
---
Day 2 operations for OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the t... | <h1>OpenShift Container Platform 4.21</h1><h2>Postinstallation configuration</h2><p>Day 2 operations for OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Postinstallation configuration</h1><hr/><p>Day 2 operations for OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><... | [
{
"page_number": 1,
"error": false,
"token_count": 251,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 89,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Project_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/project_apis/OpenShift_Container_Platform-4.21-Project_APIs-en-US.pdf | success | 2026-04-15T18:27:11.953846+00:00 | 30.29 | 19 | 19 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Project APIs
Reference guide for project APIs# OpenShift Container Platform 4.21 Project APIs
---
Reference guide for project APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat... | <h1>OpenShift Container Platform 4.21</h1><h2>Project APIs</h2><p>Reference guide for project APIs</p><h1>OpenShift Container Platform 4.21 Project APIs</h1><hr/><p>Reference guide for project APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in th... | [
{
"page_number": 1,
"error": false,
"token_count": 242,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Provisioning_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/provisioning_apis/OpenShift_Container_Platform-4.21-Provisioning_APIs-en-US.pdf | success | 2026-04-15T18:28:16.208087+00:00 | 64.25 | 181 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Provisioning APIs
Reference guide for provisioning APIs# OpenShift Container Platform 4.21 Provisioning APIs
---
Reference guide for provisioning APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are... | <h1>OpenShift Container Platform 4.21</h1><h2>Provisioning APIs</h2><p>Reference guide for provisioning APIs</p><h1>OpenShift Container Platform 4.21 Provisioning APIs</h1><hr/><p>Reference guide for provisioning APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and... | [
{
"page_number": 1,
"error": false,
"token_count": 248,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 85,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-RBAC_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/rbac_apis/OpenShift_Container_Platform-4.21-RBAC_APIs-en-US.pdf | success | 2026-04-15T18:29:23.560969+00:00 | 67.34 | 48 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## RBAC APIs
Reference guide for RBAC APIs# OpenShift Container Platform 4.21 RBAC APIs
---
Reference guide for RBAC APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the C... | <h1>OpenShift Container Platform 4.21</h1><h2>RBAC APIs</h2><p>Reference guide for RBAC APIs</p><h1>OpenShift Container Platform 4.21 RBAC APIs</h1><hr/><p>Reference guide for RBAC APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documenta... | [
{
"page_number": 1,
"error": false,
"token_count": 248,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 86,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Registry-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/registry/OpenShift_Container_Platform-4.21-Registry-en-US.pdf | success | 2026-04-15T18:30:34.006265+00:00 | 70.43 | 69 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Registry
Configuring registries for OpenShift Container Platform# OpenShift Container Platform 4.21 Registry
---
Configuring registries for OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this... | <h1>OpenShift Container Platform 4.21</h1><h2>Registry</h2><p>Configuring registries for OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Registry</h1><hr/><p>Configuring registries for OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted belo... | [
{
"page_number": 1,
"error": false,
"token_count": 248,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 87,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Release_notes-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/release_notes/OpenShift_Container_Platform-4.21-Release_notes-en-US.pdf | success | 2026-04-15T18:31:41.548281+00:00 | 66.43 | 64 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Release notes
Highlights of what is new and what has changed with this OpenShift Container Platform release# OpenShift Container Platform 4.21 Release notes
---
Highlights of what is new and what has changed with this OpenShift Container Platform release## Legal Notice
Copyri... | <h1>OpenShift Container Platform 4.21</h1><h2>Release notes</h2><p>Highlights of what is new and what has changed with this OpenShift Container Platform release</p><h1>OpenShift Container Platform 4.21 Release notes</h1><hr/><p>Highlights of what is new and what has changed with this OpenShift Container Platform releas... | [
{
"page_number": 1,
"error": false,
"token_count": 256,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 95,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Role_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/role_apis/OpenShift_Container_Platform-4.21-Role_APIs-en-US.pdf | success | 2026-04-15T18:32:40.991805+00:00 | 59.43 | 46 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Role APIs
Reference guide for role APIs# OpenShift Container Platform 4.21 Role APIs
---
Reference guide for role APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the C... | <h1>OpenShift Container Platform 4.21</h1><h2>Role APIs</h2><p>Reference guide for role APIs</p><h1>OpenShift Container Platform 4.21 Role APIs</h1><hr/><p>Reference guide for role APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations in this documenta... | [
{
"page_number": 1,
"error": false,
"token_count": 245,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Scalability_and_performance-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/scalability_and_performance/OpenShift_Container_Platform-4.21-Scalability_and_performance-en-US.pdf | success | 2026-04-15T18:33:51.253367+00:00 | 70.25 | 434 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Scalability and performance
Scaling your OpenShift Container Platform cluster and tuning performance in production environments## OpenShift Container Platform 4.21 Scalability and performance
---
Scaling your OpenShift Container Platform cluster and tuning performance in produ... | <h1>OpenShift Container Platform 4.21</h1><h2>Scalability and performance</h2><p>Scaling your OpenShift Container Platform cluster and tuning performance in production environments</p><h2>OpenShift Container Platform 4.21 Scalability and performance</h2><hr/><p>Scaling your OpenShift Container Platform cluster and tuni... | [
{
"page_number": 1,
"error": false,
"token_count": 256,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 94,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Schedule_and_quota_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/schedule_and_quota_apis/OpenShift_Container_Platform-4.21-Schedule_and_quota_APIs-en-US.pdf | success | 2026-04-15T18:34:55.030140+00:00 | 63.76 | 102 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Schedule and quota APIs
Reference guide for schedule and quota APIs# OpenShift Container Platform 4.21 Schedule and quota APIs
---
Reference guide for schedule and quota APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations i... | <h1>OpenShift Container Platform 4.21</h1><h2>Schedule and quota APIs</h2><p>Reference guide for schedule and quota APIs</p><h1>OpenShift Container Platform 4.21 Schedule and quota APIs</h1><hr/><p>Reference guide for schedule and quota APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise note... | [
{
"page_number": 1,
"error": false,
"token_count": 246,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 88,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Security_and_compliance-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/security_and_compliance/OpenShift_Container_Platform-4.21-Security_and_compliance-en-US.pdf | success | 2026-04-15T18:36:11.168334+00:00 | 76.13 | 583 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Security and compliance
Learning about and managing security for OpenShift Container Platform# OpenShift Container Platform 4.21 Security and compliance
---
Learning about and managing security for OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as ot... | <h1>OpenShift Container Platform 4.21</h1><h2>Security and compliance</h2><p>Learning about and managing security for OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Security and compliance</h1><hr/><p>Learning about and managing security for OpenShift Container Platform</p><h2>Legal Notice</h2><p... | [
{
"page_number": 1,
"error": false,
"token_count": 251,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Security_APIs-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/security_apis/OpenShift_Container_Platform-4.21-Security_APIs-en-US.pdf | success | 2026-04-15T18:37:18.757573+00:00 | 67.58 | 101 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Security APIs
Reference guide for security APIs# OpenShift Container Platform 4.21 Security APIs
---
Reference guide for security APIs## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red... | <h1>OpenShift Container Platform 4.21</h1><h2>Security APIs</h2><p>Reference guide for security APIs</p><h1>OpenShift Container Platform 4.21 Security APIs</h1><hr/><p>Reference guide for security APIs</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted below, the text of and illustrations i... | [
{
"page_number": 1,
"error": false,
"token_count": 241,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 84,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Serverless-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/serverless/OpenShift_Container_Platform-4.21-Serverless-en-US.pdf | success | 2026-04-15T18:37:30.775362+00:00 | 12 | 7 | 7 | 30 | false | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Serverless
OpenShift Serverless installation, usage, and release notes# OpenShift Container Platform 4.21 Serverless
---
OpenShift Serverless installation, usage, and release notes## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrat... | <h1>OpenShift Container Platform 4.21</h1><h2>Serverless</h2><p>OpenShift Serverless installation, usage, and release notes</p><h1>OpenShift Container Platform 4.21 Serverless</h1><hr/><p>OpenShift Serverless installation, usage, and release notes</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwis... | [
{
"page_number": 1,
"error": false,
"token_count": 247,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 90,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Service_Mesh-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/service_mesh/OpenShift_Container_Platform-4.21-Service_Mesh-en-US.pdf | success | 2026-04-15T18:38:52.437517+00:00 | 81.66 | 351 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Service Mesh
Service Mesh installation, usage, and release notes# OpenShift Container Platform 4.21 Service Mesh
---
Service Mesh installation, usage, and release notes## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this... | <h1>OpenShift Container Platform 4.21</h1><h2>Service Mesh</h2><p>Service Mesh installation, usage, and release notes</p><h1>OpenShift Container Platform 4.21 Service Mesh</h1><hr/><p>Service Mesh installation, usage, and release notes</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as otherwise noted belo... | [
{
"page_number": 1,
"error": false,
"token_count": 249,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 88,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Specialized_hardware_and_driver_enablement-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/specialized_hardware_and_driver_enablement/OpenShift_Container_Platform-4.21-Specialized_hardware_and_driver_enablement-en-US.pdf | success | 2026-04-15T18:40:01.021382+00:00 | 68.57 | 94 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Specialized hardware and driver enablement
Learn about hardware enablement on OpenShift Container Platform## OpenShift Container Platform 4.21 Specialized hardware and driver enablement
---
Learn about hardware enablement on OpenShift Container Platform## Legal Notice
Copyrig... | <h1>OpenShift Container Platform 4.21</h1><h2>Specialized hardware and driver enablement</h2><p>Learn about hardware enablement on OpenShift Container Platform</p><h2>OpenShift Container Platform 4.21 Specialized hardware and driver enablement</h2><hr/><p>Learn about hardware enablement on OpenShift Container Platform<... | [
{
"page_number": 1,
"error": false,
"token_count": 255,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 95,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
OpenShift_Container_Platform-4.21-Storage-en-US | https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/pdf/storage/OpenShift_Container_Platform-4.21-Storage-en-US.pdf | success | 2026-04-15T18:41:10.161659+00:00 | 69.13 | 324 | 30 | 30 | true | [] | ocr_layout | datalab-to/chandra-ocr-2 | 2026-04-15T00:00:00 | # OpenShift Container Platform 4.21
## Storage
Configuring and managing storage in OpenShift Container Platform# OpenShift Container Platform 4.21 Storage
---
Configuring and managing storage in OpenShift Container Platform## Legal Notice
Copyright © Red Hat.
Except as otherwise noted below, the text of and illus... | <h1>OpenShift Container Platform 4.21</h1><h2>Storage</h2><p>Configuring and managing storage in OpenShift Container Platform</p><h1>OpenShift Container Platform 4.21 Storage</h1><hr/><p>Configuring and managing storage in OpenShift Container Platform</p><h2>Legal Notice</h2><p>Copyright © Red Hat.</p><p>Except as othe... | [
{
"page_number": 1,
"error": false,
"token_count": 249,
"num_chunks": 5
},
{
"page_number": 2,
"error": false,
"token_count": 48,
"num_chunks": 1
},
{
"page_number": 3,
"error": false,
"token_count": 88,
"num_chunks": 2
},
{
"page_number": 4,
"erro... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.