Merge pull request #71984 from SNiemann15/ibmp_readd_tp

jldohmann · web-flow · commit d87738a91d2e · 2024-02-21T17:25:45.000-06:00
[MULTIARCH-4115] Readding the TP statements for IBM PowerVS
diff --git a/installing/installing_ibm_powervs/creating-ibm-power-vs-workspace.adoc b/installing/installing_ibm_powervs/creating-ibm-power-vs-workspace.adoc
@@ -4,6 +4,9 @@
 include::_attributes/common-attributes.adoc[]
 :context: creating-ibm-power-vs-workspace
 
+:FeatureName: {ibm-power-server-name} using installer-provisioned infrastructure
+include::snippets/technology-preview.adoc[]
+
 include::modules/creating-ibm-power-vs-workspace-procedure.adoc[leveloffset=+1]
 
 
diff --git a/installing/installing_ibm_powervs/installing-ibm-cloud-account-power-vs.adoc b/installing/installing_ibm_powervs/installing-ibm-cloud-account-power-vs.adoc
@@ -8,6 +8,9 @@ toc::[]
 
 Before you can install {product-title}, you must configure an {ibm-cloud-name} account.
 
+:FeatureName: {ibm-power-server-title} using installer-provisioned infrastructure
+include::snippets/technology-preview.adoc[]
+
 [id="prerequisites_installing-ibm-cloud-account-power-vs"]
 == Prerequisites
 
diff --git a/installing/installing_ibm_powervs/installing-ibm-power-vs-customizations.adoc b/installing/installing_ibm_powervs/installing-ibm-power-vs-customizations.adoc
@@ -8,6 +8,9 @@ toc::[]
 
 In {product-title} version {product-version}, you can install a customized cluster on infrastructure that the installation program provisions on {ibm-power-server-title}. To customize the installation, you modify parameters in the `install-config.yaml` file before you install the cluster.
 
+:FeatureName: {ibm-power-server-title} using installer-provisioned infrastructure
+include::snippets/technology-preview.adoc[]
+
 [id="prerequisites_installing-ibm-powervs-customizations"]
 == Prerequisites
 
diff --git a/installing/installing_ibm_powervs/installing-ibm-power-vs-private-cluster.adoc b/installing/installing_ibm_powervs/installing-ibm-power-vs-private-cluster.adoc
@@ -8,6 +8,9 @@ toc::[]
 
 In {product-title} version {product-version}, you can install a private cluster into an existing VPC and {ibm-power-server-name} Workspace. The installation program provisions the rest of the required infrastructure, which you can further customize. To customize the installation, you modify parameters in the `install-config.yaml` file before you install the cluster.
 
+:FeatureName: {ibm-power-server-name} using installer-provisioned infrastructure
+include::snippets/technology-preview.adoc[]
+
 [id="prerequisites_installing-ibm-power-vs-private-cluster"]
 == Prerequisites
 
diff --git a/installing/installing_ibm_powervs/installing-ibm-powervs-vpc.adoc b/installing/installing_ibm_powervs/installing-ibm-powervs-vpc.adoc
@@ -8,6 +8,9 @@ toc::[]
 
 In {product-title} version {product-version}, you can install a cluster into an existing Virtual Private Cloud (VPC) on {ibm-cloud-name}. The installation program provisions the rest of the required infrastructure, which you can then further customize. To customize the installation, you modify parameters in the `install-config.yaml` file before you install the cluster.
 
+:FeatureName: {ibm-power-server-name} using installer-provisioned infrastructure
+include::snippets/technology-preview.adoc[]
+
 [id="prerequisites_installing-ibm-powervs-vpc"]
 == Prerequisites
 
diff --git a/installing/installing_ibm_powervs/installing-restricted-networks-ibm-power-vs.adoc b/installing/installing_ibm_powervs/installing-restricted-networks-ibm-power-vs.adoc
@@ -8,6 +8,9 @@ toc::[]
 
 In {product-title} {product-version}, you can install a cluster on {ibm-cloud-name} in a restricted network by creating an internal mirror of the installation release content on an existing Virtual Private Cloud (VPC) on {ibm-cloud-name}.
 
+:FeatureName: {ibm-power-server-name} using installer-provisioned infrastructure
+include::snippets/technology-preview.adoc[]
+
 [id="prerequisites_installing-ibm-power-vs-restricted"]
 == Prerequisites
 
diff --git a/installing/installing_ibm_powervs/preparing-to-install-on-ibm-power-vs.adoc b/installing/installing_ibm_powervs/preparing-to-install-on-ibm-power-vs.adoc
@@ -8,6 +8,9 @@ toc::[]
 
 The installation workflows documented in this section are for {ibm-power-server-name} infrastructure environments.
 
+:FeatureName: {ibm-power-server-name} using installer-provisioned infrastructure
+include::snippets/technology-preview.adoc[]
+
 [id="prerequisites_preparing-to-install-on-ibm-power-vs"]
 == Prerequisites
 
diff --git a/storage/container_storage_interface/persistent-storage-csi-ibm-powervs-block.adoc b/storage/container_storage_interface/persistent-storage-csi-ibm-powervs-block.adoc
@@ -9,13 +9,16 @@ toc::[]
 [id="persistent-storage-csi-ibm-powervs-block-introduction_{context}"]
 == Introduction
 
-The {ibm-power-server-name} Block CSI Driver will be installed through {ibm-power-server-name} Block CSI Driver Operator and the operator is based on libarary-go. The OpenShift library-go is a collection of functions that allow us to build OpenShift operators easily. Most of the functionality of a CSI driver operator is already available there. The {ibm-power-server-name} Block CSI Driver Operator is installed by the cluster-storage-operator. The Cluster-storage-operator installs the {ibm-power-server-name} Block CSI Driver Operator if the Platform type is Power Virtual Servers.
+The {ibm-power-server-name} Block CSI Driver is installed through the {ibm-power-server-name} Block CSI Driver Operator and the operator is based on `library-go`. The {product-title} `library-go` framework is a collection of functions that allows users to build OpenShift operators easily. Most of the functionality of a CSI Driver Operator is already available there. The {ibm-power-server-name} Block CSI Driver Operator is installed by the Cluster Storage Operator. The Cluster Storage Operator installs the {ibm-power-server-name} Block CSI Driver Operator if the platform type is Power Virtual Servers.
 
 [id="persistent-storage-csi-ibm-powervs-block-overview_{context}"]
 == Overview
 
 {product-title} can provision persistent volumes (PVs) by using the Container Storage Interface (CSI) driver for {ibm-power-server-name} Block Storage.
 
+:FeatureName: {ibm-power-server-title} Block CSI Driver Operator
+include::snippets/technology-preview.adoc[leveloffset=+1]
+
 Familiarity with xref:../../storage/understanding-persistent-storage.adoc#understanding-persistent-storage[persistent storage] and xref:../../storage/container_storage_interface/persistent-storage-csi.adoc#persistent-storage-csi[configuring CSI volumes] is helpful when working with a CSI Operator and driver.
 
 To create CSI-provisioned PVs that mount to {ibm-power-server-name} Block storage assets, {product-title} installs the {ibm-power-server-name} Block CSI Driver Operator and the {ibm-power-server-name} Block CSI driver by default in the `openshift-cluster-csi-drivers` namespace.
