Merge pull request #76691 from aireilly/TELCODOCS-1689

TELCODOCS-1689 - Recommend ACM PolicyGenerator over ztp PolicyGenTemplate for managed cluster polices

Author: aireilly

_attributes/common-attributes.adoc

@@ -46,7 +46,7 @@ endif::[]
 :rh-storage: OpenShift Data Foundation
 :rh-rhacm-first: Red Hat Advanced Cluster Management (RHACM)
 :rh-rhacm: RHACM
-:rh-rhacm-version: 2.9
+:rh-rhacm-version: 2.10
 :sandboxed-containers-first: OpenShift sandboxed containers
 :sandboxed-containers-operator: OpenShift sandboxed containers Operator
 :sandboxed-containers-version: 1.5

_topic_maps/_topic_map.yml

@@ -3034,22 +3034,38 @@ Topics:
   File: ztp-updating-gitops
 - Name: Installing managed clusters with RHACM and SiteConfig resources
   File: ztp-deploying-far-edge-sites
-- Name: Configuring managed clusters with policies and PolicyGenTemplate resources
-  File: ztp-configuring-managed-clusters-policies
-- Name: Manually installing a single-node OpenShift cluster with ZTP
+- Name: Manually installing a single-node OpenShift cluster with GitOps ZTP
   File: ztp-manual-install
 - Name: Recommended single-node OpenShift cluster configuration for vDU application workloads
   File: ztp-reference-cluster-configuration-for-vdu
 - Name: Validating cluster tuning for vDU application workloads
   File: ztp-vdu-validating-cluster-tuning
 - Name: Advanced managed cluster configuration with SiteConfig resources
   File: ztp-advanced-install-ztp
-- Name: Advanced managed cluster configuration with PolicyGenTemplate resources
-  File: ztp-advanced-policy-config
+- Name: Managing cluster polices with PolicyGenerator resources
+  Dir: policygenerator_for_ztp
+  Distros: openshift-origin,openshift-enterprise
+  Topics:
+  - Name: Configuring managed cluster policies by using PolicyGenerator resources
+    File: ztp-configuring-managed-clusters-policygenerator
+  - Name: Advanced managed cluster configuration with PolicyGenerator resources
+    File: ztp-advanced-policygenerator-config
+  - Name: Updating managed clusters in a disconnected environment with PolicyGenerator resources and TALM
+    File: ztp-talm-updating-managed-policies-pg
+- Name: Managing cluster polices with PolicyGenTemplate resources
+  Dir: policygentemplate_for_ztp
+  Distros: openshift-origin,openshift-enterprise
+  Topics:
+  - Name: Configuring managed cluster policies by using PolicyGenTemplate resources
+    File: ztp-configuring-managed-clusters-policies
+  - Name: Advanced managed cluster configuration with PolicyGenTemplate resources
+    File: ztp-advanced-policy-config
+  - Name: Updating managed clusters in a disconnected environment with PolicyGenTemplate resources and TALM
+    File: ztp-talm-updating-managed-policies
+- Name: Using hub templates in PolicyGenerator or PolicyGenTemplate CRs
+  File: ztp-using-hub-cluster-templates
 - Name: Updating managed clusters with the Topology Aware Lifecycle Manager
   File: cnf-talm-for-cluster-upgrades
-- Name: Updating managed clusters in a disconnected environment with the Topology Aware Lifecycle Manager
-  File: ztp-talm-updating-managed-policies
 - Name: Expanding single-node OpenShift clusters with GitOps ZTP
   File: ztp-sno-additional-worker-node
 - Name: Pre-caching images for single-node OpenShift deployments

edge_computing/cnf-talm-for-cluster-upgrades.adoc

@@ -8,12 +8,18 @@ toc::[]
 
 You can use the {cgu-operator-first} to manage the software lifecycle of multiple clusters. {cgu-operator} uses {rh-rhacm-first} policies to perform changes on the target clusters.
 
-:FeatureName: {cgu-operator-full}
+:Featurename: Using PolicyGenerator resources with {ztp}
+include::snippets/technology-preview.adoc[]
 
 include::modules/cnf-about-topology-aware-lifecycle-manager-config.adoc[leveloffset=+1]
 
 include::modules/cnf-about-topology-aware-lifecycle-manager-policies.adoc[leveloffset=+1]
 
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../edge_computing/policygenerator_for_ztp/ztp-configuring-managed-clusters-policygenerator.adoc#ztp-the-policygentemplate_ztp-configuring-managed-clusters-policygenerator[About the PolicyGenerator CRD]
+
 include::modules/cnf-topology-aware-lifecycle-manager-installation-web-console.adoc[leveloffset=+1]
 
 include::modules/cnf-topology-aware-lifecycle-manager-installation-cli.adoc[leveloffset=+1]
@@ -27,7 +33,7 @@ include::modules/cnf-topology-aware-lifecycle-manager-policies-concept.adoc[leve
 [role="_additional-resources"]
 .Additional resources
 
-For more information about the `PolicyGenTemplate` CRD, see xref:../edge_computing/ztp-configuring-managed-clusters-policies.adoc#ztp-the-policygentemplate_ztp-configuring-managed-clusters-policies[About the PolicyGenTemplate CRD].
+* xref:../edge_computing/policygenerator_for_ztp/ztp-configuring-managed-clusters-policygenerator.adoc#ztp-the-policygentemplate_ztp-configuring-managed-clusters-policygenerator[About the PolicyGenerator CRD]
 
 include::modules/cnf-topology-aware-lifecycle-manager-about-subscription-crs.adoc[leveloffset=+2]
 
@@ -50,8 +56,8 @@ include::modules/cnf-topology-aware-lifecycle-manager-troubleshooting.adoc[level
 [role="_additional-resources"]
 .Additional resources
 
-* For information about troubleshooting, see xref:../support/troubleshooting/troubleshooting-operator-issues.adoc#troubleshooting-operator-issues[OpenShift Container Platform Troubleshooting Operator Issues].
+* xref:../support/troubleshooting/troubleshooting-operator-issues.adoc#troubleshooting-operator-issues[{product-title} Troubleshooting Operator Issues]
 
-* For more information about using {cgu-operator-full} in the ZTP workflow, see xref:../edge_computing/ztp-talm-updating-managed-policies.adoc#ztp-topology-aware-lifecycle-manager[Updating managed policies with {cgu-operator-full}].
+* xref:../edge_computing/policygenerator_for_ztp/ztp-talm-updating-managed-policies-pg.adoc#ztp-topology-aware-lifecycle-manager[Updating managed policies with {cgu-operator-full}]
 
-* For more information about the `PolicyGenTemplate` CRD, see xref:../edge_computing/ztp-configuring-managed-clusters-policies.adoc#ztp-the-policygentemplate_ztp-configuring-managed-clusters-policies[About the PolicyGenTemplate CRD]
+* xref:../edge_computing/policygenerator_for_ztp/ztp-configuring-managed-clusters-policygenerator.adoc#ztp-the-policygentemplate_ztp-configuring-managed-clusters-policygenerator[About the PolicyGenerator CRD]

edge_computing/policygenerator_for_ztp/_attributes

@@ -0,0 +1 @@
+../../_attributes/

edge_computing/policygenerator_for_ztp/images

@@ -0,0 +1 @@
+../../images/

edge_computing/policygenerator_for_ztp/modules

@@ -0,0 +1 @@
+../../modules/

edge_computing/policygenerator_for_ztp/snippets

@@ -0,0 +1 @@
+../../snippets/

edge_computing/policygenerator_for_ztp/ztp-advanced-policygenerator-config.adoc

@@ -0,0 +1,129 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="ztp-advanced-policygenerator-config"]
+= Advanced managed cluster configuration with PolicyGenerator resources
+include::_attributes/common-attributes.adoc[]
+:context: ztp-advanced-policygenerator-config
+:policy-gen-cr: PolicyGenerator
+:policy-prefix: acm-
+:rangen-yaml-path: policies.manifests
+:argocd-folder: out/argocd/example/acmpolicygenerator/
+
+toc::[]
+
+You can use `{policy-gen-cr}` CRs to deploy custom functionality in your managed clusters.
+
+:Featurename: Using PolicyGenerator resources with {ztp}
+include::snippets/technology-preview.adoc[]
+
+[NOTE]
+====
+For more information about `PolicyGenerator` resources, see the {rh-rhacm} link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/{rh-rhacm-version}/html/governance/integrate-third-party-policy-controllers#policy-generator[Policy Generator] documentation.
+====
+
+include::modules/ztp-deploying-additional-changes-to-clusters.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../edge_computing/ztp-advanced-install-ztp.adoc#ztp-customizing-the-install-extra-manifests_ztp-advanced-install-ztp[Customizing extra installation manifests in the {ztp} pipeline]
+
+include::modules/ztp-using-pgt-to-update-source-crs.adoc[leveloffset=+1]
+
+include::modules/ztp-adding-new-content-to-gitops-ztp.adoc[leveloffset=+1]
+
+include::modules/ztp-configuring-pgt-compliance-eval-timeouts.adoc[leveloffset=+1]
+
+include::modules/ztp-creating-a-validator-inform-policy.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../edge_computing/ztp-updating-gitops.adoc#ztp-updating-gitops[Upgrading {ztp}]
+
+include::modules/ztp-using-pgt-to-configure-power-states.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../scalability_and_performance/low_latency_tuning/cnf-tuning-low-latency-nodes-with-perf-profile.adoc#configuring-workload-hints_cnf-low-latency-perf-profile[Configuring node power consumption and realtime processing with workload hints]
+
+include::modules/ztp-using-pgt-to-configure-performance-mode.adoc[leveloffset=+2]
+
+include::modules/ztp-using-pgt-to-configure-high-performance-mode.adoc[leveloffset=+2]
+
+include::modules/ztp-using-pgt-to-configure-power-saving-mode.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../scalability_and_performance/low_latency_tuning/cnf-tuning-low-latency-nodes-with-perf-profile.adoc#cnf-configuring-power-saving-for-nodes_cnf-low-latency-perf-profile[Configuring power saving for nodes that run colocated high and low priority workloads]
+
+* xref:../../edge_computing/ztp-reference-cluster-configuration-for-vdu.adoc#ztp-du-configuring-host-firmware-requirements_sno-configure-for-vdu[Configuring host firmware for low latency and high performance]
+
+* xref:../../edge_computing/ztp-preparing-the-hub-cluster.adoc#ztp-preparing-the-ztp-git-repository_ztp-preparing-the-hub-cluster[Preparing the {ztp} site configuration repository]
+
+include::modules/ztp-using-pgt-to-maximize-power-saving-mode.adoc[leveloffset=+2]
+
+include::modules/ztp-provisioning-lvm-storage.adoc[leveloffset=+1]
+
+[id="ztp-advanced-policy-config-ptp_{context}"]
+== Configuring PTP events with {policy-gen-cr} CRs
+
+You can use the {ztp} pipeline to configure PTP events that use HTTP or AMQP transport.
+
+include::snippets/ptp-amq-interconnect-eol.adoc[]
+
+include::modules/ztp-configuring-ptp-fast-events.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../edge_computing/policygenerator_for_ztp/ztp-advanced-policygenerator-config.adoc#ztp-using-pgt-to-update-source-crs_ztp-advanced-policygenerator-config[Using {policy-gen-cr} CRs to override source CRs content]
+
+include::modules/ztp-configuring-ptp-fast-events-amqp.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../networking/ptp/using-ptp-events.adoc#cnf-installing-amq-interconnect-messaging-bus_using-ptp-events[Installing the AMQ messaging bus]
+
+* xref:../../registry/index.adoc#registry-overview[{product-registry} overview]
+
+[id="ztp-advanced-policy-config-bare-metal_{context}"]
+== Configuring bare-metal events with {policy-gen-cr} CRs
+
+You can use the {ztp} pipeline to configure bare-metal events that use HTTP or AMQP transport.
+
+include::snippets/ptp-amq-interconnect-eol.adoc[]
+
+include::modules/ztp-configuring-hwevents-using-pgt.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../scalability_and_performance/using-rfhe.adoc#nw-rfhe-installing-operator-cli_using-rfhe[Installing the {redfish-operator} using the CLI]
+
+* xref:../../scalability_and_performance/using-rfhe.adoc#nw-rfhe-creating-hardware-event_using-rfhe[Creating the bare-metal event and Secret CRs]
+
+include::modules/ztp-creating-hwevents-amqp.adoc[leveloffset=+2]
+
+include::modules/ztp-add-local-reg-for-sno-duprofile.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../registry/index.adoc#registry-overview[{product-title} registry overview]
+
+include::modules/ztp-configuring-disk-partitioning.adoc[leveloffset=+2]
+
+include::modules/ztp-configuring-pgt-image-registry.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../registry/accessing-the-registry.adoc#accessing-the-registry[Accessing the registry]
+
+:!policy-gen-cr:
+:!policy-prefix:
+:!rangen-yaml-path:
+:!argocd-folder:

…nfiguring-managed-clusters-policies.adoc …ng-managed-clusters-policygenerator.adocedge_computing/ztp-configuring-managed-clusters-policies.adoc renamed to edge_computing/policygenerator_for_ztp/ztp-configuring-managed-clusters-policygenerator.adoc edge_computing/ztp-configuring-managed-clusters-policies.adoc renamed to edge_computing/policygenerator_for_ztp/ztp-configuring-managed-clusters-policygenerator.adoc

@@ -1,12 +1,27 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="ztp-configuring-managed-clusters-policies"]
-= Configuring managed clusters with policies and PolicyGenTemplate resources
+[id="ztp-configuring-managed-clusters-policygenerator"]
+= Configuring managed cluster policies by using PolicyGenerator resources
 include::_attributes/common-attributes.adoc[]
-:context: ztp-configuring-managed-clusters-policies
+:context: ztp-configuring-managed-clusters-policygenerator
+:policy-gen-cr: PolicyGenerator
+:policy-prefix: acm-
+:argocd-folder: out/argocd/example/acmpolicygenerator/
+:placement-rule-cr: Placement
+:binding-field: policyDefaults.placement.labelSelector
 
 toc::[]
 
-Applied policy custom resources (CRs) configure the managed clusters that you provision. You can customize how {rh-rhacm-first} uses `PolicyGenTemplate` CRs to generate the applied policy CRs.
+Applied `Policy` custom resources (CRs) configure the managed clusters that you provision. You can customize how {rh-rhacm-first} uses `{policy-gen-cr}` CRs to generate the applied `Policy` CRs.
+
+:Featurename: Using PolicyGenerator resources with {ztp}
+include::snippets/technology-preview.adoc[]
+
+[NOTE]
+====
+For more information about `PolicyGenerator` resources, see the {rh-rhacm} link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/{rh-rhacm-version}/html/governance/integrate-third-party-policy-controllers#policy-generator[Policy Generator] documentation.
+====
+
+include::modules/ztp-comparing-pgt-and-rhacm-pg-patching-strategies.adoc[leveloffset=+1]
 
 include::modules/ztp-the-policygentemplate.adoc[leveloffset=+1]
 
@@ -29,15 +44,14 @@ include::modules/ztp-policygentemplates-for-ran.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../edge_computing/ztp-preparing-the-hub-cluster.adoc#ztp-preparing-the-ztp-git-repository_ztp-preparing-the-hub-cluster[Preparing the {ztp} site configuration repository]
+* xref:../../edge_computing/ztp-preparing-the-hub-cluster.adoc#ztp-preparing-the-ztp-git-repository_ztp-preparing-the-hub-cluster[Preparing the {ztp} site configuration repository]
 
 include::modules/ztp-customizing-a-managed-site-using-pgt.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../edge_computing/ztp-advanced-policy-config.adoc#ztp-creating-a-validator-inform-policy_ztp-advanced-policy-config[Signalling ZTP cluster deployment completion with validator inform policies]
-
+* xref:../../edge_computing/policygenerator_for_ztp/ztp-advanced-policygenerator-config.adoc#ztp-creating-a-validator-inform-policy_ztp-advanced-policy-config[Signalling {ztp} cluster deployment completion with validator inform policies]
 
 include::modules/ztp-monitoring-policy-deployment-progress.adoc[leveloffset=+1]
 
@@ -48,8 +62,14 @@ include::modules/ztp-restarting-policies-reconciliation.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* For information about using {cgu-operator-first} to construct your own `ClusterGroupUpgrade` CR, see xref:../edge_computing/cnf-talm-for-cluster-upgrades.adoc#talo-about-cgu-crs_cnf-topology-aware-lifecycle-manager[About the ClusterGroupUpgrade CR].
+* For information about using {cgu-operator-first} to construct your own `ClusterGroupUpgrade` CR, see xref:../../edge_computing/cnf-talm-for-cluster-upgrades.adoc#talo-about-cgu-crs_cnf-topology-aware-lifecycle-manager[About the ClusterGroupUpgrade CR].
 
 include::modules/ztp-removing-content-from-managed-clusters.adoc[leveloffset=+1]
 
 include::modules/ztp-definition-of-done-for-ztp-installations.adoc[leveloffset=+1]
+
+:!policy-gen-cr:
+:!policy-prefix:
+:!argocd-folder:
+:!placement-rule-cr:
+:!binding-field:

edge_computing/policygenerator_for_ztp/ztp-talm-updating-managed-policies-pg.adoc

@@ -0,0 +1,70 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="ztp-topology-aware-lifecycle-manager-pg"]
+= Updating managed clusters in a disconnected environment with PolicyGenerator resources and TALM
+include::_attributes/common-attributes.adoc[]
+:context: ztp-talm-pg
+:policy-gen-cr: PolicyGenerator
+:policy-prefix: acm-
+:rangen-yaml-path: policies.manifests
+
+toc::[]
+You can use the {cgu-operator-first} to manage the software lifecycle of managed clusters that you have deployed using {ztp-first} and {cgu-operator-first}.
+{cgu-operator} uses {rh-rhacm-first} {policy-gen-cr} policies to manage and control changes applied to target clusters.
+
+:Featurename: Using PolicyGenerator resources with {ztp}
+include::snippets/technology-preview.adoc[]
+
+[role="_additional-resources"]
+.Additional resources
+
+* For more information about the {cgu-operator-full}, see xref:../../edge_computing/cnf-talm-for-cluster-upgrades.adoc#cnf-about-topology-aware-lifecycle-manager-config_cnf-topology-aware-lifecycle-manager[About the {cgu-operator-full}].
+
+include::modules/cnf-topology-aware-lifecycle-manager-preparing-for-updates.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* For more information about how to update {ztp-first}, see xref:../../edge_computing/ztp-updating-gitops.adoc#ztp-updating-gitops[Upgrading {ztp}].
+
+* For more information about how to mirror an {product-title} image repository, see xref:../../installing/disconnected_install/installing-mirroring-installation-images.adoc#installation-mirror-repository_installing-mirroring-installation-images[Mirroring the {product-title} image repository].
+
+* For more information about how to mirror Operator catalogs for disconnected clusters, see xref:../../installing/disconnected_install/installing-mirroring-installation-images.adoc#olm-mirror-catalog_installing-mirroring-installation-images[Mirroring Operator catalogs for use with disconnected clusters].
+
+* For more information about how to prepare the disconnected environment and mirroring the desired image repository, see xref:../../edge_computing/ztp-preparing-the-hub-cluster.adoc#ztp-preparing-the-hub-cluster[Preparing the disconnected environment].
+
+* For more information about update channels and releases, see xref:../../updating/understanding_updates/understanding-update-channels-release.adoc#understanding-update-channels-releases[Understanding update channels and releases].
+
+include::modules/cnf-topology-aware-lifecycle-manager-platform-update.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* For more information about mirroring the images in a disconnected environment, see xref:../../edge_computing/ztp-preparing-the-hub-cluster.adoc#ztp-acm-adding-images-to-mirror-registry_ztp-preparing-the-hub-cluster[Preparing the disconnected environment].
+
+include::modules/cnf-topology-aware-lifecycle-manager-operator-update.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* For more information about updating {ztp}, see xref:../../edge_computing/ztp-updating-gitops.adoc#ztp-updating-gitops[Upgrading {ztp}].
+
+include::modules/cnf-topology-aware-lifecycle-manager-operator-troubleshooting.adoc[leveloffset=+1]
+
+include::modules/cnf-topology-aware-lifecycle-manager-operator-and-platform-update.adoc[leveloffset=+1]
+
+include::modules/cnf-topology-aware-lifecycle-manager-pao-update.adoc[leveloffset=+1]
+
+include::modules/cnf-topology-aware-lifecycle-manager-precache-user-spec-images.adoc[leveloffset=+1]
+
+include::modules/cnf-topology-aware-lifecycle-manager-creating-custom-resources.adoc[leveloffset=+2]
+
+[role="_additional-resources"]
+.Additional resources
+
+* For more information about the {cgu-operator} precaching workflow, see xref:../../edge_computing/cnf-talm-for-cluster-upgrades.adoc#talo-precache-feature-concept_cnf-topology-aware-lifecycle-manager[Using the container image precache feature].
+
+include::modules/cnf-topology-aware-lifecycle-manager-autocreate-cgu-cr-ztp.adoc[leveloffset=+1]
+
+:!policy-gen-cr:
+:!policy-prefix:
+:!rangen-yaml-path: