Merge pull request #460 from syedriko/syedriko-ols-1937

Python deps and docs update, week of 2025/07/21

Author: openshift-merge-bot[bot]

ocp-product-docs-plaintext/4.15/backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-about-kopia.txt

@@ -15,6 +15,12 @@ Kopia uses content-addressable storage for snapshots:
 
 OADP 1.3 supports Kopia as the backup mechanism for pod volume backup in addition to Restic. You must choose one or the other at installation by setting the uploaderType field in the DataProtectionApplication custom resource (CR). The possible values are restic or kopia. If you do not specify an  uploaderType, OADP 1.3 defaults to using Kopia as the backup mechanism. The data is written to and read from a unified repository.
 
+
+[IMPORTANT]
+----
+Using the Kopia client to modify the Kopia backup repositories is not supported and can affect the integrity of Kopia backups. OADP does not support directly connecting to the Kopia repository and can offer support only on a best-effort basis.
+----
+
 The following example shows a DataProtectionApplication CR configured for using Kopia:
 
 

ocp-product-docs-plaintext/4.15/backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.txt

@@ -30,7 +30,7 @@ You can use a saved etcd backup to restore a previous cluster state or restore a
 
 [NOTE]
 ----
-If your cluster uses a control plane machine set, see "Troubleshooting the control plane machine set" for a more simple etcd recovery procedure.
+If your cluster uses a control plane machine set, see "Recovering a degraded etcd Operator" in "Troubleshooting the control plane machine set" for an etcd recovery procedure.
 ----
 
 
@@ -682,6 +682,8 @@ $ oc whoami
 
 ----
 
+* Recovering a degraded etcd Operator
+
 # Restoring a cluster manually from an etcd backup
 
 The restore procedure described in the section "Restoring to a previous cluster state":

ocp-product-docs-plaintext/4.15/backup_and_restore/control_plane_backup_and_restore/replacing-unhealthy-etcd-member.txt

@@ -151,7 +151,7 @@ This procedure details the steps to replace an etcd member that is unhealthy eit
 
 [NOTE]
 ----
-If your cluster uses a control plane machine set, see "Recovering a degraded etcd Operator" in "Troubleshooting the control plane machine set" for a more simple etcd recovery procedure.
+If your cluster uses a control plane machine set, see "Recovering a degraded etcd Operator" in "Troubleshooting the control plane machine set" for an etcd recovery procedure.
 ----
 
 * You have identified the unhealthy etcd member.

ocp-product-docs-plaintext/4.15/installing/disconnected_install/installing-mirroring-creating-registry.txt

@@ -296,6 +296,16 @@ These release notes track the development of the mirror registry for Red Ha
 
 The following sections provide details for each 2.0 release of the mirror registry for Red Hat OpenShift.
 
+### Mirror registry for Red Hat OpenShift 2.0.7
+
+Issued: 14 July 2025
+
+Mirror registry for Red Hat OpenShift is now available with Red Hat Quay 3.12.10.
+
+The following advisory is available for the mirror registry for Red Hat OpenShift:
+
+* RHBA-2025:9645 - mirror registry for Red Hat OpenShift 2.0.7
+
 ### Mirror registry for Red Hat OpenShift 2.0.6
 
 Issued: 28 April 2025

ocp-product-docs-plaintext/4.15/installing/installing_ibm_z/installing-ibm-z-lpar.txt

@@ -1358,7 +1358,7 @@ The rootfs image is the same for FCP and DASD.
 2. An empty string.
 3. The gateway.
 4. The netmask.
-5. The machine host and domain name in the form hostname.domainname. Omit this value to let RHCOS decide.
+5. The machine host and domain name in the form hostname.domainname. If you omit this value, RHCOS obtains the hostname through a reverse DNS lookup.
 6. The network interface name. If you omit this value, RHCOS applies the IP configuration to all available interfaces.
 7. If you use static IP addresses, specify none.
 * For coreos.inst.ignition_url=, specify the Ignition file for the machine role. Use bootstrap.ign, master.ign, or worker.ign. Only HTTP and HTTPS protocols are supported.

ocp-product-docs-plaintext/4.15/installing/installing_ibm_z/installing-ibm-z.txt

@@ -1361,7 +1361,7 @@ The rootfs image is the same for FCP and DASD.
 2. An empty string.
 3. The gateway.
 4. The netmask.
-5. The machine host and domain name in the form hostname.domainname. Omit this value to let RHCOS decide.
+5. The machine host and domain name in the form hostname.domainname. If you omit this value, RHCOS obtains the hostname through a reverse DNS lookup.
 6. The network interface name. If you omit this value, RHCOS applies the IP configuration to all available interfaces.
 7. If you use static IP addresses, specify none.
 * For coreos.inst.ignition_url=, specify the Ignition file for the machine role. Use bootstrap.ign, master.ign, or worker.ign. Only HTTP and HTTPS protocols are supported.

ocp-product-docs-plaintext/4.15/installing/installing_ibm_z/installing-restricted-networks-ibm-z-lpar.txt

@@ -1281,7 +1281,7 @@ The rootfs image is the same for FCP and DASD.
 2. An empty string.
 3. The gateway.
 4. The netmask.
-5. The machine host and domain name in the form hostname.domainname. Omit this value to let RHCOS decide.
+5. The machine host and domain name in the form hostname.domainname. If you omit this value, RHCOS obtains the hostname through a reverse DNS lookup.
 6. The network interface name. If you omit this value, RHCOS applies the IP configuration to all available interfaces.
 7. If you use static IP addresses, specify none.
 * For coreos.inst.ignition_url=, specify the Ignition file for the machine role. Use bootstrap.ign, master.ign, or worker.ign. Only HTTP and HTTPS protocols are supported.

ocp-product-docs-plaintext/4.15/installing/installing_ibm_z/installing-restricted-networks-ibm-z.txt

@@ -1288,7 +1288,7 @@ The rootfs image is the same for FCP and DASD.
 2. An empty string.
 3. The gateway.
 4. The netmask.
-5. The machine host and domain name in the form hostname.domainname. Omit this value to let RHCOS decide.
+5. The machine host and domain name in the form hostname.domainname. If you omit this value, RHCOS obtains the hostname through a reverse DNS lookup.
 6. The network interface name. If you omit this value, RHCOS applies the IP configuration to all available interfaces.
 7. If you use static IP addresses, specify none.
 * For coreos.inst.ignition_url=, specify the Ignition file for the machine role. Use bootstrap.ign, master.ign, or worker.ign. Only HTTP and HTTPS protocols are supported.

ocp-product-docs-plaintext/4.15/networking/external_dns_operator/nw-installing-external-dns-operator-on-cloud-providers.txt

@@ -100,16 +100,16 @@ $ oc apply -f subscription.yaml
 
 ```terminal
 $ oc -n external-dns-operator \
-    get subscription external-dns-operator \
-    --template='{{.status.installplan.name}}{{"\n"}}'
+  get subscription external-dns-operator \
+  --template='{{.status.installplan.name}}{{"\n"}}'
 ```
 
 2. Verify that the status of the install plan is Complete by running the following command:
 
 ```terminal
 $ oc -n external-dns-operator \
-    get ip <install_plan_name> \
-    --template='{{.status.phase}}{{"\n"}}'
+  get ip <install_plan_name> \
+  --template='{{.status.phase}}{{"\n"}}'
 ```
 
 3. Verify that the status of the external-dns-operator pod is Running by running the following command:

ocp-product-docs-plaintext/4.15/networking/multiple_networks/configuring-additional-network.txt

@@ -502,7 +502,7 @@ The multi-network policy API, which is provided by the MultiNetworkPolicy custom
 
 
 
-For example, the following multi-network policy is valid only if the subnets field is defined in the additional network CNI configuration for the additional network named blue2:
+You can use the k8s.v1.cni.cncf.io/policy-for annotation on a MultiNetworkPolicy object to point to a NetworkAttachmentDefinition (NAD) custom resource (CR). The NAD CR defines the network to which the policy applies. The following example multi-network policy is valid only if the subnets field is defined in the secondary network CNI configuration for the secondary network named blue2:
 
 
 ```yaml
@@ -511,7 +511,7 @@ kind: MultiNetworkPolicy
 metadata:
   name: allow-same-namespace
   annotations:
-    k8s.v1.cni.cncf.io/policy-for: blue2
+    k8s.v1.cni.cncf.io/policy-for: blue2 1
 spec:
   podSelector:
   ingress: