From ec48f99b11eab8ff721a8aea9ce02d71fafc8007 Mon Sep 17 00:00:00 2001 From: Kevin Quinn Date: Tue, 17 Feb 2026 17:25:08 +0000 Subject: [PATCH] TELCODOCS-2764: DITA compatibility fixes for vDU reference cluster configuration Fix all 29 AsciiDocDITA Vale errors and warnings across the assembly and its 24 included modules: add [role="_abstract"] short descriptions, add missing content-type attribute, rewrite related-links to contain only xrefs, extract inline assembly content to new concept modules, and attach trailing NOTE to last procedure step. Co-Authored-By: Claude Opus 4.6 --- ...ference-cluster-configuration-for-vdu.adoc | 28 +++++++------------ .../ztp-du-host-firmware-requirements.adoc | 3 +- ...tp-enabling-workload-partitioning-sno.adoc | 1 + modules/ztp-low-latency.adoc | 1 + .../ztp-managed-cluster-network-prereqs.adoc | 1 + ...du-configuring-crun-container-runtime.adoc | 1 + ...guring-logging-locally-and-forwarding.adoc | 1 + modules/ztp-sno-du-configuring-lvms.adoc | 1 + ...sno-du-configuring-performance-addons.adoc | 1 + modules/ztp-sno-du-configuring-sriov.adoc | 1 + ...-configuring-the-container-mountspace.adoc | 1 + .../ztp-sno-du-configuring-the-operators.adoc | 1 + modules/ztp-sno-du-configuring-time-sync.adoc | 1 + modules/ztp-sno-du-disabling-crio-wipe.adoc | 1 + ...-sno-du-disabling-network-diagnostics.adoc | 1 + modules/ztp-sno-du-enabling-kdump.adoc | 1 + modules/ztp-sno-du-enabling-sctp.adoc | 1 + ...recommended-cluster-install-manifests.adoc | 17 +++++++++++ ...stinstallation-cluster-configurations.adoc | 15 ++++++++++ ...esource-usage-with-cluster-monitoring.adoc | 1 + ...educing-resource-usage-with-olm-pprof.adoc | 1 + ...-sno-du-removing-the-console-operator.adoc | 1 + modules/ztp-sno-du-setting-rcu-normal.adoc | 1 + ...ors-needed-for-platform-configuration.adoc | 1 + ...p-sno-du-tuning-the-performance-patch.adoc | 1 + 25 files changed, 65 insertions(+), 19 deletions(-) create mode 100644 modules/ztp-sno-du-recommended-cluster-install-manifests.adoc create mode 100644 modules/ztp-sno-du-recommended-postinstallation-cluster-configurations.adoc diff --git a/edge_computing/ztp-reference-cluster-configuration-for-vdu.adoc b/edge_computing/ztp-reference-cluster-configuration-for-vdu.adoc index b193c3f34b28..646f9f938991 100644 --- a/edge_computing/ztp-reference-cluster-configuration-for-vdu.adoc +++ b/edge_computing/ztp-reference-cluster-configuration-for-vdu.adoc @@ -11,9 +11,9 @@ Use the following reference information to understand the {sno} configurations r [role="_additional-resources"] .Additional resources -* To deploy a single cluster by hand, see xref:../edge_computing/ztp-manual-install.adoc#ztp-manual-install[Manually installing a {sno} cluster with {ztp}]. +* xref:../edge_computing/ztp-manual-install.adoc#ztp-manual-install[Manually installing a {sno} cluster with {ztp}] -* To deploy a fleet of clusters using {ztp-first}, see xref:../edge_computing/ztp-deploying-far-edge-sites.adoc#ztp-deploying-far-edge-sites[Deploying far edge sites with {ztp}]. +* xref:../edge_computing/ztp-deploying-far-edge-sites.adoc#ztp-deploying-far-edge-sites[Deploying far edge sites with {ztp}] include::modules/ztp-low-latency.adoc[leveloffset=+1] @@ -36,17 +36,12 @@ include::modules/ztp-enabling-workload-partitioning-sno.adoc[leveloffset=+1] * xref:../security/network_bound_disk_encryption/nbde-about-disk-encryption-technology.adoc#nbde-tpm-encryption_nbde-implementation[TPM encryption] -[id="ztp-sno-install-time-cluster-config"] -== Recommended cluster install manifests +include::modules/ztp-sno-du-recommended-cluster-install-manifests.adoc[leveloffset=+1] -The ZTP pipeline applies the following custom resources (CRs) during cluster installation. These configuration CRs ensure that the cluster meets the feature and performance requirements necessary for running a vDU application. - -[NOTE] -==== -When using the {ztp} plugin and `ClusterInstance` CRs for cluster deployment, the following `MachineConfig` CRs are included by default. -==== +[role="_additional-resources"] +.Additional resources -Use the `ClusterInstance` `extraManifestRefs` to alter the CRs that are included by default. For more information, see xref:../edge_computing/ztp-advanced-install-ztp.adoc#ztp-advanced-install-ztp[Advanced managed cluster configuration with ClusterInstance CRs]. +* xref:../edge_computing/ztp-advanced-install-ztp.adoc#ztp-advanced-install-ztp[Advanced managed cluster configuration with ClusterInstance CRs] include::modules/ztp-sno-du-configuring-the-container-mountspace.adoc[leveloffset=+2] @@ -63,15 +58,12 @@ include::modules/ztp-sno-du-configuring-crun-container-runtime.adoc[leveloffset= [role="_additional-resources"] .Additional resources -[id="ztp-sno-post-install-time-cluster-config"] -== Recommended postinstallation cluster configurations +include::modules/ztp-sno-du-recommended-postinstallation-cluster-configurations.adoc[leveloffset=+1] -When the cluster installation is complete, the ZTP pipeline applies the following custom resources (CRs) that are required to run DU workloads. +[role="_additional-resources"] +.Additional resources -[NOTE] -==== -In {ztp} v4.10 and earlier, you configure UEFI secure boot with a `MachineConfig` CR. This is no longer required in {ztp} v4.11 and later. In v4.11, you configure UEFI secure boot for {sno} clusters by updating the `spec.nodes[].bootMode` field in the `ClusterInstance` CR that you use to install the cluster. For more information, see xref:../edge_computing/ztp-deploying-far-edge-sites.adoc#ztp-deploying-a-site_ztp-deploying-far-edge-sites[Deploying a managed cluster with ClusterInstance and {ztp}]. -==== +* xref:../edge_computing/ztp-deploying-far-edge-sites.adoc#ztp-deploying-a-site_ztp-deploying-far-edge-sites[Deploying a managed cluster with ClusterInstance and {ztp}] include::modules/ztp-sno-du-configuring-the-operators.adoc[leveloffset=+2] diff --git a/modules/ztp-du-host-firmware-requirements.adoc b/modules/ztp-du-host-firmware-requirements.adoc index 0bf6c574f16f..6d806526c54d 100644 --- a/modules/ztp-du-host-firmware-requirements.adoc +++ b/modules/ztp-du-host-firmware-requirements.adoc @@ -6,6 +6,7 @@ [id="ztp-du-configuring-host-firmware-requirements_{context}"] = Configuring host firmware for low latency and high performance +[role="_abstract"] Bare-metal hosts require the firmware to be configured before the host can be provisioned. The firmware configuration is dependent on the specific hardware and the particular requirements of your installation. .Procedure @@ -61,7 +62,7 @@ The exact firmware configuration depends on your specific hardware and network r |Processor C6 |Disabled |==== - ++ [NOTE] ==== Enable global SR-IOV and VT-d settings in the firmware for the host. These settings are relevant to bare-metal environments. diff --git a/modules/ztp-enabling-workload-partitioning-sno.adoc b/modules/ztp-enabling-workload-partitioning-sno.adoc index f374219f12ea..7095dfb840c7 100644 --- a/modules/ztp-enabling-workload-partitioning-sno.adoc +++ b/modules/ztp-enabling-workload-partitioning-sno.adoc @@ -6,6 +6,7 @@ [id="ztp-workload-partitioning-sno_{context}"] = Workload partitioning in {sno} with {ztp} +[role="_abstract"] Workload partitioning configures {product-title} services, cluster management workloads, and infrastructure pods to run on a reserved number of host CPUs. To configure workload partitioning with {ztp-first}, you configure a `cpuPartitioningMode` field in the `ClusterInstance` custom resource (CR) that you use to install the cluster and you apply a `PerformanceProfile` CR that configures the `isolated` and `reserved` CPUs on the host. diff --git a/modules/ztp-low-latency.adoc b/modules/ztp-low-latency.adoc index dce223417678..0ad9eadbeca2 100644 --- a/modules/ztp-low-latency.adoc +++ b/modules/ztp-low-latency.adoc @@ -6,6 +6,7 @@ [id="ztp-low-latency_{context}"] = Running low latency applications on {product-title} +[role="_abstract"] {product-title} enables low latency processing for applications running on commercial off-the-shelf (COTS) hardware by using several technologies and specialized hardware devices: Real-time kernel for RHCOS:: Ensures workloads are handled with a high degree of process determinism. diff --git a/modules/ztp-managed-cluster-network-prereqs.adoc b/modules/ztp-managed-cluster-network-prereqs.adoc index 2b27860c01e3..551b243d260e 100644 --- a/modules/ztp-managed-cluster-network-prereqs.adoc +++ b/modules/ztp-managed-cluster-network-prereqs.adoc @@ -6,6 +6,7 @@ [id="ztp-managed-cluster-network-prereqs_{context}"] = Connectivity prerequisites for managed cluster networks +[role="_abstract"] Before you can install and provision a managed cluster with the {ztp-first} pipeline, the managed cluster host must meet the following networking prerequisites: * There must be bi-directional connectivity between the {ztp} container in the hub cluster and the Baseboard Management Controller (BMC) of the target bare-metal host. diff --git a/modules/ztp-sno-du-configuring-crun-container-runtime.adoc b/modules/ztp-sno-du-configuring-crun-container-runtime.adoc index ac22be08362f..f577b65b7a90 100644 --- a/modules/ztp-sno-du-configuring-crun-container-runtime.adoc +++ b/modules/ztp-sno-du-configuring-crun-container-runtime.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-configuring-crun-container-runtime_{context}"] = Configuring crun as the default container runtime +[role="_abstract"] The following `ContainerRuntimeConfig` custom resources (CRs) configure crun as the default OCI container runtime for control plane and worker nodes. The crun container runtime is fast and lightweight and has a low memory footprint. diff --git a/modules/ztp-sno-du-configuring-logging-locally-and-forwarding.adoc b/modules/ztp-sno-du-configuring-logging-locally-and-forwarding.adoc index bf657fdf9a52..c0371d913ca4 100644 --- a/modules/ztp-sno-du-configuring-logging-locally-and-forwarding.adoc +++ b/modules/ztp-sno-du-configuring-logging-locally-and-forwarding.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-configuring-logging-locally-and-forwarding_{context}"] = Cluster logging and log forwarding +[role="_abstract"] {sno-caps} clusters that run DU workloads require logging and log forwarding for debugging. The following custom resources (CRs) are required. diff --git a/modules/ztp-sno-du-configuring-lvms.adoc b/modules/ztp-sno-du-configuring-lvms.adoc index 097470a61eed..bb98399aa6d7 100644 --- a/modules/ztp-sno-du-configuring-lvms.adoc +++ b/modules/ztp-sno-du-configuring-lvms.adoc @@ -6,6 +6,7 @@ [id="lvms-configuring-lvms-on-sno_{context}"] = {lvms} +[role="_abstract"] You can dynamically provision local storage on {sno} clusters with {lvms-first}. [NOTE] diff --git a/modules/ztp-sno-du-configuring-performance-addons.adoc b/modules/ztp-sno-du-configuring-performance-addons.adoc index 69bc4fdf52ab..69bcae24d7f4 100644 --- a/modules/ztp-sno-du-configuring-performance-addons.adoc +++ b/modules/ztp-sno-du-configuring-performance-addons.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-configuring-performance-addons_{context}"] = Performance profile +[role="_abstract"] {sno-caps} clusters that run DU workloads require a Node Tuning Operator performance profile to use real-time host capabilities and services. [NOTE] diff --git a/modules/ztp-sno-du-configuring-sriov.adoc b/modules/ztp-sno-du-configuring-sriov.adoc index 2ee382967d83..b4f086d81fe1 100644 --- a/modules/ztp-sno-du-configuring-sriov.adoc +++ b/modules/ztp-sno-du-configuring-sriov.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-configuring-sriov_{context}"] = SR-IOV +[role="_abstract"] Single root I/O virtualization (SR-IOV) is commonly used to enable fronthaul and midhaul networks. The following YAML example configures SR-IOV for a {sno} cluster. [NOTE] diff --git a/modules/ztp-sno-du-configuring-the-container-mountspace.adoc b/modules/ztp-sno-du-configuring-the-container-mountspace.adoc index 34ec04b0852a..86d4f71a7cb2 100644 --- a/modules/ztp-sno-du-configuring-the-container-mountspace.adoc +++ b/modules/ztp-sno-du-configuring-the-container-mountspace.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-configuring-the-container-mountspace_{context}"] = Reduced platform management footprint +[role="_abstract"] To reduce the overall management footprint of the platform, a `MachineConfig` custom resource (CR) is required that places all Kubernetes-specific mount points in a new namespace separate from the host operating system. The following base64-encoded example `MachineConfig` CR illustrates this configuration. diff --git a/modules/ztp-sno-du-configuring-the-operators.adoc b/modules/ztp-sno-du-configuring-the-operators.adoc index 53b3617fd803..a8f84fa8b4e5 100644 --- a/modules/ztp-sno-du-configuring-the-operators.adoc +++ b/modules/ztp-sno-du-configuring-the-operators.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-configuring-the-operators_{context}"] = Operators +[role="_abstract"] {sno-caps} clusters that run DU workloads require the following Operators to be installed: * Local Storage Operator diff --git a/modules/ztp-sno-du-configuring-time-sync.adoc b/modules/ztp-sno-du-configuring-time-sync.adoc index e976bca8866a..0b307e30d9a7 100644 --- a/modules/ztp-sno-du-configuring-time-sync.adoc +++ b/modules/ztp-sno-du-configuring-time-sync.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-configuring-time-sync_{context}"] = Configuring cluster time synchronization +[role="_abstract"] Run a one-time system time synchronization job for control plane or worker nodes. .Recommended one time time-sync for control plane nodes (`99-sync-time-once-master.yaml`) diff --git a/modules/ztp-sno-du-disabling-crio-wipe.adoc b/modules/ztp-sno-du-disabling-crio-wipe.adoc index 913ab96b1df0..e2f1df028d7e 100644 --- a/modules/ztp-sno-du-disabling-crio-wipe.adoc +++ b/modules/ztp-sno-du-disabling-crio-wipe.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-disabling-crio-wipe_{context}"] = Disable automatic CRI-O cache wipe +[role="_abstract"] After an uncontrolled host shutdown or cluster reboot, CRI-O automatically deletes the entire CRI-O cache, causing all images to be pulled from the registry when the node reboots. This can result in unacceptably slow recovery times or recovery failures. To prevent this from happening in {sno} clusters that you install with {ztp}, disable the CRI-O delete cache feature during cluster installation. diff --git a/modules/ztp-sno-du-disabling-network-diagnostics.adoc b/modules/ztp-sno-du-disabling-network-diagnostics.adoc index 30cdb5d48a62..912e8f066ae6 100644 --- a/modules/ztp-sno-du-disabling-network-diagnostics.adoc +++ b/modules/ztp-sno-du-disabling-network-diagnostics.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-disabling-network-diagnostics_{context}"] = Network diagnostics +[role="_abstract"] {sno-caps} clusters that run DU workloads require less inter-pod network connectivity checks to reduce the additional load created by these pods. The following custom resource (CR) disables these checks. .Recommended network diagnostics configuration (`DisableSnoNetworkDiag.yaml`) diff --git a/modules/ztp-sno-du-enabling-kdump.adoc b/modules/ztp-sno-du-enabling-kdump.adoc index fabda399a991..c2a5f165aeda 100644 --- a/modules/ztp-sno-du-enabling-kdump.adoc +++ b/modules/ztp-sno-du-enabling-kdump.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-enabling-kdump_{context}"] = Automatic kernel crash dumps with kdump +[role="_abstract"] `kdump` is a Linux kernel feature that creates a kernel crash dump when the kernel crashes. `kdump` is enabled with the following `MachineConfig` CRs. .Recommended control plane node kdump configuration (`06-kdump-master.yaml`) diff --git a/modules/ztp-sno-du-enabling-sctp.adoc b/modules/ztp-sno-du-enabling-sctp.adoc index 3f9394d013ac..ee25d3badc54 100644 --- a/modules/ztp-sno-du-enabling-sctp.adoc +++ b/modules/ztp-sno-du-enabling-sctp.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-enabling-sctp_{context}"] = SCTP +[role="_abstract"] Stream Control Transmission Protocol (SCTP) is a key protocol used in RAN applications. This `MachineConfig` object adds the SCTP kernel module to the node to enable this protocol. .Recommended control plane node SCTP configuration (`03-sctp-machine-config-master.yaml`) diff --git a/modules/ztp-sno-du-recommended-cluster-install-manifests.adoc b/modules/ztp-sno-du-recommended-cluster-install-manifests.adoc new file mode 100644 index 000000000000..fc1276700d27 --- /dev/null +++ b/modules/ztp-sno-du-recommended-cluster-install-manifests.adoc @@ -0,0 +1,17 @@ +// Module included in the following assemblies: +// +// * edge_computing/ztp-reference-cluster-configuration-for-vdu.adoc + +:_mod-docs-content-type: CONCEPT +[id="ztp-sno-install-time-cluster-config_{context}"] += Recommended cluster install manifests + +[role="_abstract"] +The ZTP pipeline applies the following custom resources (CRs) during cluster installation. These configuration CRs ensure that the cluster meets the feature and performance requirements necessary for running a vDU application. + +[NOTE] +==== +When using the {ztp} plugin and `ClusterInstance` CRs for cluster deployment, the following `MachineConfig` CRs are included by default. +==== + +Use the `ClusterInstance` `extraManifestRefs` to alter the CRs that are included by default. For more information, see "Advanced managed cluster configuration with ClusterInstance CRs". diff --git a/modules/ztp-sno-du-recommended-postinstallation-cluster-configurations.adoc b/modules/ztp-sno-du-recommended-postinstallation-cluster-configurations.adoc new file mode 100644 index 000000000000..d4847460631c --- /dev/null +++ b/modules/ztp-sno-du-recommended-postinstallation-cluster-configurations.adoc @@ -0,0 +1,15 @@ +// Module included in the following assemblies: +// +// * edge_computing/ztp-reference-cluster-configuration-for-vdu.adoc + +:_mod-docs-content-type: CONCEPT +[id="ztp-sno-post-install-time-cluster-config_{context}"] += Recommended postinstallation cluster configurations + +[role="_abstract"] +When the cluster installation is complete, the ZTP pipeline applies the following custom resources (CRs) that are required to run DU workloads. + +[NOTE] +==== +In {ztp} v4.10 and earlier, you configure UEFI secure boot with a `MachineConfig` CR. This is no longer required in {ztp} v4.11 and later. In v4.11, you configure UEFI secure boot for {sno} clusters by updating the `spec.nodes[].bootMode` field in the `ClusterInstance` CR that you use to install the cluster. For more information, see "Deploying a managed cluster with ClusterInstance and {ztp}". +==== diff --git a/modules/ztp-sno-du-reducing-resource-usage-with-cluster-monitoring.adoc b/modules/ztp-sno-du-reducing-resource-usage-with-cluster-monitoring.adoc index 4eaaa7c40a3d..3db53b4f6507 100644 --- a/modules/ztp-sno-du-reducing-resource-usage-with-cluster-monitoring.adoc +++ b/modules/ztp-sno-du-reducing-resource-usage-with-cluster-monitoring.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-reducing-resource-usage-with-cluster-monitoring_{context}"] = Alertmanager +[role="_abstract"] {sno-caps} clusters that run DU workloads require reduced CPU resources consumed by the {product-title} monitoring components. The following `ConfigMap` custom resource (CR) disables Alertmanager. .Recommended cluster monitoring configuration (`ReduceMonitoringFootprint.yaml`) diff --git a/modules/ztp-sno-du-reducing-resource-usage-with-olm-pprof.adoc b/modules/ztp-sno-du-reducing-resource-usage-with-olm-pprof.adoc index 6dbac555abf4..93ce48fd99af 100644 --- a/modules/ztp-sno-du-reducing-resource-usage-with-olm-pprof.adoc +++ b/modules/ztp-sno-du-reducing-resource-usage-with-olm-pprof.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-reducing-resource-usage-with-olm-pprof_{context}"] = Operator Lifecycle Manager +[role="_abstract"] {sno-caps} clusters that run distributed unit workloads require consistent access to CPU resources. Operator Lifecycle Manager (OLM) collects performance data from Operators at regular intervals, resulting in an increase in CPU utilisation. The following `ConfigMap` custom resource (CR) disables the collection of Operator performance data by OLM. .Recommended cluster OLM configuration (`ReduceOLMFootprint.yaml`) diff --git a/modules/ztp-sno-du-removing-the-console-operator.adoc b/modules/ztp-sno-du-removing-the-console-operator.adoc index 37f7a42e4e51..9a321791e845 100644 --- a/modules/ztp-sno-du-removing-the-console-operator.adoc +++ b/modules/ztp-sno-du-removing-the-console-operator.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-removing-the-console-operator_{context}"] = Console Operator +[role="_abstract"] Use the cluster capabilities feature to prevent the Console Operator from being installed. When the node is centrally managed it is not needed. Removing the Operator provides additional space and capacity for application workloads. diff --git a/modules/ztp-sno-du-setting-rcu-normal.adoc b/modules/ztp-sno-du-setting-rcu-normal.adoc index aff5163ed9ce..82ece27bbbe7 100644 --- a/modules/ztp-sno-du-setting-rcu-normal.adoc +++ b/modules/ztp-sno-du-setting-rcu-normal.adoc @@ -6,6 +6,7 @@ [id="ztp-setting-rcu-normal_{context}"] = Setting rcu_normal +[role="_abstract"] The following `MachineConfig` CR configures the system to set `rcu_normal` to 1 after the system has finished startup. This improves kernel latency for vDU applications. .Recommended configuration for disabling `rcu_expedited` after the node has finished startup (`08-set-rcu-normal-master.yaml`) diff --git a/modules/ztp-sno-du-subscribing-to-the-operators-needed-for-platform-configuration.adoc b/modules/ztp-sno-du-subscribing-to-the-operators-needed-for-platform-configuration.adoc index 859831f6072f..59bc84e1ba04 100644 --- a/modules/ztp-sno-du-subscribing-to-the-operators-needed-for-platform-configuration.adoc +++ b/modules/ztp-sno-du-subscribing-to-the-operators-needed-for-platform-configuration.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-subscribing-to-the-operators-needed-for-platform-configuration_{context}"] = Operator subscriptions +[role="_abstract"] {sno-caps} clusters that run DU workloads require the following `Subscription` CRs. The subscription provides the location to download the following Operators: * Local Storage Operator diff --git a/modules/ztp-sno-du-tuning-the-performance-patch.adoc b/modules/ztp-sno-du-tuning-the-performance-patch.adoc index 8bf6e4fe74d7..4d1afdf5c427 100644 --- a/modules/ztp-sno-du-tuning-the-performance-patch.adoc +++ b/modules/ztp-sno-du-tuning-the-performance-patch.adoc @@ -6,6 +6,7 @@ [id="ztp-sno-du-tuning-the-performance-patch_{context}"] = Extended Tuned profile +[role="_abstract"] {sno-caps} clusters that run DU workloads require additional performance tuning configurations necessary for high-performance workloads. The following example `Tuned` CR extends the `Tuned` profile: .Recommended extended `Tuned` profile configuration (`TunedPerformancePatch.yaml`)