TELCODOCS-2072: Updating variables and hardcoded versions for Telco content 4.18 GA

Author: rohennes

_attributes/common-attributes.adoc

@@ -56,7 +56,7 @@ endif::[]
 :rh-rhacm-title: Red Hat Advanced Cluster Management
 :rh-rhacm-first: Red Hat Advanced Cluster Management (RHACM)
 :rh-rhacm: RHACM
-:rh-rhacm-version: 2.11
+:rh-rhacm-version: 2.12
 :osc: OpenShift sandboxed containers
 :cert-manager-operator: cert-manager Operator for Red Hat OpenShift
 :secondary-scheduler-operator-full: Secondary Scheduler Operator for Red Hat OpenShift

modules/telco-update-acknowledging-the-update.adoc

@@ -11,7 +11,7 @@ When you update to all versions from 4.11 and later, you must manually acknowled
 [IMPORTANT]
 ====
 Before you acknowledge the update, verify that there are no Kubernetes APIs in use that are removed in the version you are updating to.
-For example, in {product-title} 4.17, there are no API removals.
+For example, in {product-title} 4.18, there are no API removals.
 See "Kubernetes API removals" for more information.
 ====
 

modules/telco-update-acknowledging-the-y-stream-release-update.adoc

@@ -12,7 +12,8 @@ In the output of the `oc adm upgrade` command, a URL is provided that shows the
 [IMPORTANT]
 ====
 Before you acknowledge the update, verify that there are no Kubernetes APIs in use that are removed in the version you are updating to.
-For example, in {product-title} 4.17, there are no API removals. See "Kubernetes API removals" for more information.
+For example, in {product-title} 4.18, there are no API removals.
+See "Kubernetes API removals" for more information.
 ====
 
 .Procedure

modules/ztp-sno-accelerated-ztp.adoc

@@ -34,7 +34,7 @@ spec:
   baseDomain: "example.com"
   pullSecretRef:
     name: "assisted-deployment-pull-secret"
-  clusterImageSetNameRef: "openshift-4.10"
+  clusterImageSetNameRef: "openshift-4.18"
   sshPublicKey: "ssh-rsa AAAA..."
   clusters:
   # ...

modules/ztp-sno-siteconfig-config-reference.adoc

@@ -16,11 +16,6 @@
 a|Configure workload partitioning by setting the value for `cpuPartitioningMode` to `AllNodes`.
 To complete the configuration, specify the `isolated` and `reserved` CPUs in the `PerformanceProfile` CR.
 
-[NOTE]
-====
-Configuring workload partitioning by using the `cpuPartitioningMode` field in the `SiteConfig` CR is a Tech Preview feature in {product-title} 4.13.
-====
-
 |`metadata.name`
 |Set `name` to `assisted-deployment-pull-secret` and create the `assisted-deployment-pull-secret` CR in the same namespace as the `SiteConfig` CR.
 
@@ -51,9 +46,10 @@ For example, `acmpolicygenerator/acm-common-ranGen.yaml` applies to all clusters
 
 |`spec.clusters.diskEncryption`
 a|Configure this field to enable disk encryption with Trusted Platform Module (TPM) and Platform Configuration Registers (PCRs) protection. For more information, see "About disk encryption with TPM and PCR protection".
+
 [NOTE]
 ====
-Configuring disk encryption by using the `diskEncryption` field in the `SiteConfig` CR is a Technology Preview feature in {product-title} 4.17.
+Configuring disk encryption by using the `diskEncryption` field in the `SiteConfig` CR is a Technology Preview feature in {product-title} 4.18.
 ====
 
 |`spec.clusters.diskEncryption.type`

snippets/ztp_example-sno.yaml

@@ -9,7 +9,7 @@ spec:
   baseDomain: "example.com"
   pullSecretRef:
     name: "assisted-deployment-pull-secret"
-  clusterImageSetNameRef: "openshift-4.16"
+  clusterImageSetNameRef: "openshift-4.18"
   sshPublicKey: "ssh-rsa AAAA..."
   clusters:
     - clusterName: "example-sno"