Merge pull request #82758 from slovern/TELCODOCS-1949

TELCODOCS-1949 - RHACM support for templates changes from partial ful…

Author: skopacz1

edge_computing/ztp-using-hub-cluster-templates.adoc

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-{cgu-operator-full} supports partial {rh-rhacm-first} hub cluster template functions in configuration policies used with {ztp-first}.
+{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 similiar configurations but with different values.
@@ -26,14 +26,7 @@ include::snippets/pgt-deprecation-notice.adoc[]
 
 * 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]
 
-include::modules/ztp-using-rhacm-hub-cluster-templates.adoc[leveloffset=+1]
-
-[role="_additional-resources"]
-.Additional resources
-
-* link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/{rh-rhacm-version}/html-single/governance/index#hub-templates[{rh-rhacm} support for hub cluster templates in configuration policies]
-
-include::modules/ztp-example-hub-template-functions.adoc[leveloffset=+1]
+* 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]
 

modules/ztp-example-hub-template-functions.adoc

@@ -17,7 +17,14 @@ The following example shows you how to use three `ConfigMap` CRs and one `Policy
 
 [NOTE]
 ====
-When you use the `fromConfigmap` function, the `printf` variable is only available for the template resource `data` key fields. You cannot use it with `name` and `namespace` fields.
+There is a link:https://kubernetes.io/docs/concepts/configuration/configmap/#motivation[1 MiB size limit] (Kubernetes documentation) for `ConfigMap` CRs.
+The effective size for the `ConfigMap` CRs is further limited by the `last-applied-configuration` annotation.
+To avoid the `last-applied-configuration` limitation, add the following annotation to the template `ConfigMap`:
+
+[source,yaml]
+----
+argocd.argoproj.io/sync-options: Replace=true
+----
 ====
 
 .Prerequisites