Skip to content

Commit 52b9c43

Browse files
committed
deletefailedcluster
1 parent 9a69615 commit 52b9c43

File tree

4 files changed

+18
-2
lines changed

4 files changed

+18
-2
lines changed

modules/create-wif-cluster-cli.adoc

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -200,6 +200,11 @@ $ ocm create cluster <cluster_name> \ <1>
200200
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.
201201
====
202202

203+
[IMPORTANT]
204+
====
205+
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.
206+
====
207+
203208
[id="ocm-cli-list-wif-commands_{context}"]
204209
== Listing WIF clusters
205210

modules/create-wif-cluster-ocm.adoc

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -208,12 +208,15 @@ In the event of critical security concerns that significantly impact the securit
208208
+
209209
. 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*.
210210
By default, clusters are created with the delete protection feature disabled.
211-
+
212211

213212
.Verification
214213

215214
* 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*.
216215
216+
[IMPORTANT]
217+
====
218+
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.
219+
====
217220
ifeval::["{context}" == "osd-creating-a-cluster-on-aws"]
218221
:!osd-on-aws:
219222
endif::[]

modules/osd-create-cluster-ccs.adoc

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -261,3 +261,7 @@ If you delete a cluster that was installed into a GCP Shared VPC, inform the VPC
261261

262262
* 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*.
263263

264+
[IMPORTANT]
265+
====
266+
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.
267+
====

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,8 +114,12 @@ In the event of critical security concerns that significantly impact the securit
114114
+
115115
. 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*.
116116
By default, clusters are created with the delete protection feature disabled.
117-
+
118117

119118
.Verification
120119

121120
* 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*.
121+
122+
[IMPORTANT]
123+
====
124+
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.
125+
====

0 commit comments

Comments
 (0)