:_mod-docs-content-type: ASSEMBLY
[id="ztp-using-hub-cluster-templates-pgt"]
= Using hub templates in PolicyGenerator or PolicyGenTemplate CRs
include::_attributes/common-attributes.adoc[]
:context: hub-cluster-templates-pgt

toc::[]

{cgu-operator-full} supports {rh-rhacm-first} hub cluster template functions in configuration policies used with {ztp-first}.

Hub-side cluster templates allow you to define configuration policies that can be dynamically customized to the target clusters.
This reduces the need to create separate policies for many clusters with similar configurations but with different values.

[IMPORTANT]
====
Policy templates are restricted to the same namespace as the namespace where the policy is defined.
This means you must create the objects referenced in the hub template in the same namespace where the policy is created.
====

include::snippets/pgt-deprecation-notice.adoc[]

[role="_additional-resources"]
.Additional resources

* xref:../edge_computing/policygenerator_for_ztp/ztp-configuring-managed-clusters-policygenerator.adoc#ztp-configuring-managed-clusters-policygenerator[Configuring managed cluster policies by using PolicyGenerator resources]

* xref:../edge_computing/policygenerator_for_ztp/ztp-configuring-managed-clusters-policygenerator.adoc#ztp-comparing-pgt-and-rhacm-pg-patching-strategies_ztp-configuring-managed-clusters-policygenerator[Comparing {rh-rhacm} PolicyGenerator and PolicyGenTemplate resource patching]

* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/{rh-rhacm-version}/html-single/governance/index#template-processing[{rh-rhacm} support for template processing in configuration policies]

include::modules/ztp-specifying-nics-in-pgt-crs-with-hub-cluster-templates.adoc[leveloffset=+1]

include::modules/ztp-syncing-new-configmap-changes-to-existing-pgt-crs.adoc[leveloffset=+1]
