Merge pull request #93166 from mletalie/OSDOCS-14613

[OSDOCS- 14613]Add warning to users about resources being consumed even if a cluster fails

Author: bmcelvee

modules/create-wif-cluster-cli.adoc

@@ -200,6 +200,11 @@ $ ocm create cluster <cluster_name> \ <1>
 If an {product-title} version is specified, the version must also be supported by the assigned WIF configuration. If a version is specified that is not supported by the assigned WIF configuration, cluster creation will fail.  If this occurs, update the assigned WIF configuration to the desired version or create a new WIF configuration with the desired version in the --version <osd_version> field.
 ====
 
+[IMPORTANT]
+====
+If your cluster deployment fails during installation, certain resources created during the installation process are not automatically removed from your {GCP} account. To remove these resources from your GCP account, you must delete the failed cluster.
+====
+
 [id="ocm-cli-list-wif-commands_{context}"]
 == Listing WIF clusters
 

modules/create-wif-cluster-ocm.adoc

@@ -208,12 +208,15 @@ In the event of critical security concerns that significantly impact the securit
 +
 . Optional: On the *Overview* tab, you can enable the delete protection feature by selecting *Enable*, which is located directly under *Delete Protection: Disabled*. This will prevent your cluster from being deleted. To disable delete protection, select *Disable*.
 By default, clusters are created with the delete protection feature disabled.
-+
 
 .Verification
 
 * You can monitor the progress of the installation in the *Overview* page for your cluster. You can view the installation logs on the same page. Your cluster is ready when the *Status* in the *Details* section of the page is listed as *Ready*.
 
+[IMPORTANT]
+====
+If your cluster deployment fails during installation, certain resources created during the installation process are not automatically removed from your {GCP} account. To remove these resources from your GCP account, you must delete the failed cluster.
+====
 ifeval::["{context}" == "osd-creating-a-cluster-on-aws"]
 :!osd-on-aws:
 endif::[]

modules/osd-create-cluster-ccs.adoc

@@ -261,3 +261,7 @@ If you delete a cluster that was installed into a GCP Shared VPC, inform the VPC
 
 * You can monitor the progress of the installation in the *Overview* page for your cluster. You can view the installation logs on the same page. Your cluster is ready when the *Status* in the *Details* section of the page is listed as *Ready*.
 
+[IMPORTANT]
+====
+If your cluster deployment fails during installation, certain resources created during the installation process are not automatically removed from your {GCP} account. To remove these resources from your GCP account, you must delete the failed cluster.
+====

modules/osd-create-cluster-red-hat-account.adoc

@@ -114,8 +114,12 @@ In the event of critical security concerns that significantly impact the securit
 +
 . Optional: On the *Overview* tab, you can enable the delete protection feature by selecting *Enable*, which is located directly under *Delete Protection: Disabled*. This will prevent your cluster from being deleted. To disable delete protection, select *Disable*.
 By default, clusters are created with the delete protection feature disabled.
-+
 
 .Verification
 
 * You can monitor the progress of the installation in the *Overview* page for your cluster. You can view the installation logs on the same page. Your cluster is ready when the *Status* in the *Details* section of the page is listed as *Ready*.
+
+[IMPORTANT]
+====
+If your cluster deployment fails during installation, certain resources created during the installation process are not automatically removed from your {GCP} account. To remove these resources from your GCP account, you must delete the failed cluster.
+====