OCP docs update 2025/08/04

Author: syedriko

ocp-product-docs-plaintext/4.15/applications/deployments/managing-deployment-processes.txt

@@ -176,7 +176,7 @@ A DeploymentConfig object can contain triggers, which drive the creation of new
 If no triggers are defined on a DeploymentConfig object, a config change trigger is added by default. If triggers are defined as an empty field, deployments must be started manually.
 ----
 
-## Config change deployment triggers
+### Config change deployment triggers
 
 The config change trigger results in a new replication controller whenever configuration changes are detected in the pod template of the DeploymentConfig object.
 
@@ -200,7 +200,7 @@ spec:
 ```
 
 
-## Image change deployment triggers
+### Image change deployment triggers
 
 The image change trigger results in a new replication controller whenever the content of an image stream tag changes (when a new version of the image is pushed).
 

ocp-product-docs-plaintext/4.15/applications/deployments/what-deployments-are.txt

@@ -247,29 +247,29 @@ However, deployment rollouts are driven from a controller manager. The controlle
 
 ## Deployment-specific features
 
-## Rollover
+### Rollover
 
 The deployment process for Deployment objects is driven by a controller loop, in contrast to DeploymentConfig objects that use deployer pods for every new rollout. This means that the Deployment object can have as many active replica sets as possible, and eventually the deployment controller will scale down all old replica sets and scale up the newest one.
 
 DeploymentConfig objects can have at most one deployer pod running, otherwise multiple deployers might conflict when trying to scale up what they think should be the newest replication controller. Because of this, only two replication controllers can be active at any point in time. Ultimately, this results in faster rapid rollouts for Deployment objects.
 
-## Proportional scaling
+### Proportional scaling
 
 Because the deployment controller is the sole source of truth for the sizes of new and old replica sets owned by a Deployment object, it can scale ongoing rollouts. Additional replicas are distributed proportionally based on the size of each replica set.
 
 DeploymentConfig objects cannot be scaled when a rollout is ongoing because the controller will have issues with the deployer process about the size of the new replication controller.
 
-## Pausing mid-rollout
+### Pausing mid-rollout
 
 Deployments can be paused at any point in time, meaning you can also pause ongoing rollouts. However, you currently cannot pause deployer pods; if you try to pause a deployment in the middle of a rollout, the deployer process is not affected and continues until it finishes.
 
 ## DeploymentConfig object-specific features
 
-## Automatic rollbacks
+### Automatic rollbacks
 
 Currently, deployments do not support automatically rolling back to the last successfully deployed replica set in case of a failure.
 
-## Triggers
+### Triggers
 
 Deployments have an implicit config change trigger in that every change in the pod template of a deployment automatically triggers a new rollout.
 If you do not want new rollouts on pod template changes, pause the deployment:
@@ -280,10 +280,10 @@ $ oc rollout pause deployments/<name>
 ```
 
 
-## Lifecycle hooks
+### Lifecycle hooks
 
 Deployments do not yet support any lifecycle hooks.
 
-## Custom strategies
+### Custom strategies
 
 Deployments do not support user-specified custom deployment strategies.

ocp-product-docs-plaintext/4.15/applications/pruning-objects.txt

@@ -401,7 +401,7 @@ If the registry is secured by a certificate authority different from the one use
 
 ## Image pruning problems
 
-## Images not being pruned
+### Images not being pruned
 
 If your images keep accumulating and the prune command removes just a small
 portion of what you expect, ensure that you understand the image prune
@@ -451,7 +451,7 @@ be avoided, unless the image must be preserved for an undefined amount of time.
 Such tags tend to have just one image in their history, which prevents
 them from ever being pruned.
 
-## Using a secure connection against insecure registry
+### Using a secure connection against insecure registry
 
 If you see a message similar to the following in the output of the oc adm prune images
 command, then your registry is not secured and the oc adm prune images
@@ -467,7 +467,7 @@ error: error communicating with registry: Get https://172.30.30.30:5000/healthz:
 client to use an insecure connection by appending --force-insecure  to the
 command; however, this is not recommended.
 
-## Using an insecure connection against a secured registry
+### Using an insecure connection against a secured registry
 
 If you see one of the following errors in the output of the oc adm prune images
 command, it means that your registry is secured using a certificate signed by a
@@ -485,7 +485,7 @@ By default, the certificate authority data stored in the user’s configurat
 
 Use the --certificate-authority option to provide the right certificate authority for the container image registry server.
 
-## Using the wrong certificate authority
+### Using the wrong certificate authority
 
 The following error means that the certificate authority used to sign the certificate of the secured container image registry is different from the authority used by the client:
 

ocp-product-docs-plaintext/4.15/installing/installing_aws/installing-aws-china.txt

@@ -460,7 +460,7 @@ However, you must have an active subscription to access this page.
 Installing the cluster requires that you manually create the installation configuration file.
 
 * You have uploaded a custom RHCOS AMI.
-* You have an SSH public key on your local machine to provide to the installation program. The key will be used for SSH authentication onto your cluster nodes for debugging and disaster recovery.
+* You have an SSH public key on your local machine for use with the installation program. You can use the key for SSH authentication onto your cluster nodes for debugging and disaster recovery.
 * You have obtained the Red Hat OpenShift Container Platform installation program and the pull secret for your
 cluster.
 
@@ -473,25 +473,19 @@ $ mkdir <installation_directory>
 
 [IMPORTANT]
 ----
-You must create a directory. Some installation assets, like bootstrap X.509
-certificates have short expiration intervals, so you must not reuse an
-installation directory. If you want to reuse individual files from another
-cluster installation, you can copy them into your directory. However, the file
-names for the installation assets might change between releases. Use caution
-when copying installation files from an earlier Red Hat OpenShift Container Platform version.
+You must create a directory. Some installation assets, such as bootstrap X.509 certificates have short expiration intervals, so you must not reuse an installation directory. If you want to reuse individual files from another cluster installation, you can copy them into your directory. However, the file names for the installation assets might change between releases. Use caution when copying installation files from an earlier Red Hat OpenShift Container Platform version.
 ----
-2. Customize the sample install-config.yaml file template that is provided and save
-it in the <installation_directory>.
+2. Customize the provided sample install-config.yaml file template and save the file in the <installation_directory>.
 
 [NOTE]
 ----
 You must name this configuration file install-config.yaml.
 ----
-3. Back up the install-config.yaml file so that you can use it to install multiple clusters.
+3. Back up the install-config.yaml file so that you can use it to install many clusters.
 
 [IMPORTANT]
 ----
-The install-config.yaml file is consumed during the next step of the installation process. You must back it up now.
+Back up the install-config.yaml file now, because the installation process consumes the file in the next step.
 ----
 
 * Installation configuration parameters for AWS

ocp-product-docs-plaintext/4.15/installing/installing_aws/installing-aws-government-region.txt

@@ -378,7 +378,7 @@ However, you must have an active subscription to access this page.
 
 Installing the cluster requires that you manually create the installation configuration file.
 
-* You have an SSH public key on your local machine to provide to the installation program. The key will be used for SSH authentication onto your cluster nodes for debugging and disaster recovery.
+* You have an SSH public key on your local machine for use with the installation program. You can use the key for SSH authentication onto your cluster nodes for debugging and disaster recovery.
 * You have obtained the Red Hat OpenShift Container Platform installation program and the pull secret for your
 cluster.
 
@@ -391,25 +391,19 @@ $ mkdir <installation_directory>
 
 [IMPORTANT]
 ----
-You must create a directory. Some installation assets, like bootstrap X.509
-certificates have short expiration intervals, so you must not reuse an
-installation directory. If you want to reuse individual files from another
-cluster installation, you can copy them into your directory. However, the file
-names for the installation assets might change between releases. Use caution
-when copying installation files from an earlier Red Hat OpenShift Container Platform version.
+You must create a directory. Some installation assets, such as bootstrap X.509 certificates have short expiration intervals, so you must not reuse an installation directory. If you want to reuse individual files from another cluster installation, you can copy them into your directory. However, the file names for the installation assets might change between releases. Use caution when copying installation files from an earlier Red Hat OpenShift Container Platform version.
 ----
-2. Customize the sample install-config.yaml file template that is provided and save
-it in the <installation_directory>.
+2. Customize the provided sample install-config.yaml file template and save the file in the <installation_directory>.
 
 [NOTE]
 ----
 You must name this configuration file install-config.yaml.
 ----
-3. Back up the install-config.yaml file so that you can use it to install multiple clusters.
+3. Back up the install-config.yaml file so that you can use it to install many clusters.
 
 [IMPORTANT]
 ----
-The install-config.yaml file is consumed during the next step of the installation process. You must back it up now.
+Back up the install-config.yaml file now, because the installation process consumes the file in the next step.
 ----
 
 * Installation configuration parameters for AWS

ocp-product-docs-plaintext/4.15/installing/installing_aws/installing-aws-private.txt

@@ -312,7 +312,7 @@ However, you must have an active subscription to access this page.
 
 Installing the cluster requires that you manually create the installation configuration file.
 
-* You have an SSH public key on your local machine to provide to the installation program. The key will be used for SSH authentication onto your cluster nodes for debugging and disaster recovery.
+* You have an SSH public key on your local machine for use with the installation program. You can use the key for SSH authentication onto your cluster nodes for debugging and disaster recovery.
 * You have obtained the Red Hat OpenShift Container Platform installation program and the pull secret for your
 cluster.
 
@@ -325,25 +325,19 @@ $ mkdir <installation_directory>
 
 [IMPORTANT]
 ----
-You must create a directory. Some installation assets, like bootstrap X.509
-certificates have short expiration intervals, so you must not reuse an
-installation directory. If you want to reuse individual files from another
-cluster installation, you can copy them into your directory. However, the file
-names for the installation assets might change between releases. Use caution
-when copying installation files from an earlier Red Hat OpenShift Container Platform version.
+You must create a directory. Some installation assets, such as bootstrap X.509 certificates have short expiration intervals, so you must not reuse an installation directory. If you want to reuse individual files from another cluster installation, you can copy them into your directory. However, the file names for the installation assets might change between releases. Use caution when copying installation files from an earlier Red Hat OpenShift Container Platform version.
 ----
-2. Customize the sample install-config.yaml file template that is provided and save
-it in the <installation_directory>.
+2. Customize the provided sample install-config.yaml file template and save the file in the <installation_directory>.
 
 [NOTE]
 ----
 You must name this configuration file install-config.yaml.
 ----
-3. Back up the install-config.yaml file so that you can use it to install multiple clusters.
+3. Back up the install-config.yaml file so that you can use it to install many clusters.
 
 [IMPORTANT]
 ----
-The install-config.yaml file is consumed during the next step of the installation process. You must back it up now.
+Back up the install-config.yaml file now, because the installation process consumes the file in the next step.
 ----
 
 * Installation configuration parameters for AWS

ocp-product-docs-plaintext/4.15/installing/installing_aws/installing-aws-secret-region.txt

@@ -490,7 +490,7 @@ However, you must have an active subscription to access this page.
 Installing the cluster requires that you manually create the installation configuration file.
 
 * You have uploaded a custom RHCOS AMI.
-* You have an SSH public key on your local machine to provide to the installation program. The key will be used for SSH authentication onto your cluster nodes for debugging and disaster recovery.
+* You have an SSH public key on your local machine for use with the installation program. You can use the key for SSH authentication onto your cluster nodes for debugging and disaster recovery.
 * You have obtained the Red Hat OpenShift Container Platform installation program and the pull secret for your
 cluster.
 
@@ -503,25 +503,19 @@ $ mkdir <installation_directory>
 
 [IMPORTANT]
 ----
-You must create a directory. Some installation assets, like bootstrap X.509
-certificates have short expiration intervals, so you must not reuse an
-installation directory. If you want to reuse individual files from another
-cluster installation, you can copy them into your directory. However, the file
-names for the installation assets might change between releases. Use caution
-when copying installation files from an earlier Red Hat OpenShift Container Platform version.
+You must create a directory. Some installation assets, such as bootstrap X.509 certificates have short expiration intervals, so you must not reuse an installation directory. If you want to reuse individual files from another cluster installation, you can copy them into your directory. However, the file names for the installation assets might change between releases. Use caution when copying installation files from an earlier Red Hat OpenShift Container Platform version.
 ----
-2. Customize the sample install-config.yaml file template that is provided and save
-it in the <installation_directory>.
+2. Customize the provided sample install-config.yaml file template and save the file in the <installation_directory>.
 
 [NOTE]
 ----
 You must name this configuration file install-config.yaml.
 ----
-3. Back up the install-config.yaml file so that you can use it to install multiple clusters.
+3. Back up the install-config.yaml file so that you can use it to install many clusters.
 
 [IMPORTANT]
 ----
-The install-config.yaml file is consumed during the next step of the installation process. You must back it up now.
+Back up the install-config.yaml file now, because the installation process consumes the file in the next step.
 ----
 
 * Installation configuration parameters for AWS

ocp-product-docs-plaintext/4.15/installing/installing_azure/installing-azure-government-region.txt

@@ -335,7 +335,7 @@ However, you must have an active subscription to access this page.
 
 Installing the cluster requires that you manually create the installation configuration file.
 
-* You have an SSH public key on your local machine to provide to the installation program. The key will be used for SSH authentication onto your cluster nodes for debugging and disaster recovery.
+* You have an SSH public key on your local machine for use with the installation program. You can use the key for SSH authentication onto your cluster nodes for debugging and disaster recovery.
 * You have obtained the Red Hat OpenShift Container Platform installation program and the pull secret for your
 cluster.
 
@@ -348,25 +348,19 @@ $ mkdir <installation_directory>
 
 [IMPORTANT]
 ----
-You must create a directory. Some installation assets, like bootstrap X.509
-certificates have short expiration intervals, so you must not reuse an
-installation directory. If you want to reuse individual files from another
-cluster installation, you can copy them into your directory. However, the file
-names for the installation assets might change between releases. Use caution
-when copying installation files from an earlier Red Hat OpenShift Container Platform version.
+You must create a directory. Some installation assets, such as bootstrap X.509 certificates have short expiration intervals, so you must not reuse an installation directory. If you want to reuse individual files from another cluster installation, you can copy them into your directory. However, the file names for the installation assets might change between releases. Use caution when copying installation files from an earlier Red Hat OpenShift Container Platform version.
 ----
-2. Customize the sample install-config.yaml file template that is provided and save
-it in the <installation_directory>.
+2. Customize the provided sample install-config.yaml file template and save the file in the <installation_directory>.
 
 [NOTE]
 ----
 You must name this configuration file install-config.yaml.
 ----
-3. Back up the install-config.yaml file so that you can use it to install multiple clusters.
+3. Back up the install-config.yaml file so that you can use it to install many clusters.
 
 [IMPORTANT]
 ----
-The install-config.yaml file is consumed during the next step of the installation process. You must back it up now.
+Back up the install-config.yaml file now, because the installation process consumes the file in the next step.
 ----
 
 * Installation configuration parameters for Azure