mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-06 06:46:26 +01:00
OCP 4.13 - IBM Power Virtual Server using installer-provisioned infrastructure follow up
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
52ff8ac680
commit
ca780ceb1a
@@ -18,7 +18,7 @@ include::snippets/technology-preview.adoc[]
|
||||
* You read the documentation on xref:../../installing/installing-preparing.adoc#installing-preparing[selecting a cluster installation method and preparing it for users].
|
||||
* You xref:../../installing/installing_ibm_powervs/installing-ibm-cloud-account-power-vs.adoc#installing-ibm-cloud-account-power-vs[configured an IBM Cloud account] to host the cluster.
|
||||
* If you use a firewall, you xref:../../installing/install_config/configuring-firewall.adoc#configuring-firewall[configured it to allow the sites] that your cluster requires access to.
|
||||
* You configured the `ccoctl` utility before you installed the cluster. For more information, see xref:../../installing/installing_ibm_powervs/preparing-to-install-on-ibm-power-vs.adoc#choosing-an-method-to-install-ocp-on-power-vs-installer-provisioned[Configuring the Cloud Credential Operator utility].
|
||||
* You configured the `ccoctl` utility before you installed the cluster. For more information, see xref:../../installing/installing_ibm_powervs/preparing-to-install-on-ibm-power-vs.adoc#cco-ccoctl-configuring_preparing-to-install-on-ibm-power-vs[Configuring the Cloud Credential Operator utility].
|
||||
|
||||
include::modules/cluster-entitlements.adoc[leveloffset=+1]
|
||||
|
||||
@@ -60,4 +60,4 @@ include::modules/cluster-telemetry.adoc[leveloffset=+1]
|
||||
== Next steps
|
||||
* xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster]
|
||||
* If necessary, you can
|
||||
xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting]
|
||||
xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting]
|
||||
|
||||
@@ -118,6 +118,7 @@ $ ./openshift-install destroy cluster \
|
||||
<1> For `<installation_directory>`, specify the path to the directory that you
|
||||
stored the installation files in.
|
||||
<2> To view different details, specify `warn`, `debug`, or `error` instead of `info`.
|
||||
ifndef::ibm-power-vs[]
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
@@ -125,10 +126,16 @@ You must specify the directory that contains the cluster definition files for
|
||||
your cluster. The installation program requires the `metadata.json` file in this
|
||||
directory to delete the cluster.
|
||||
====
|
||||
endif::ibm-power-vs[]
|
||||
ifdef::ibm-power-vs[]
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
You might have to run the openshift-install destroy command up to three times to ensure a proper cleanup.
|
||||
* You must specify the directory that contains the cluster definition files for
|
||||
your cluster. The installation program requires the `metadata.json` file in this
|
||||
directory to delete the cluster.
|
||||
|
||||
* You might have to run the `openshift-install destroy` command up to three times to ensure a proper cleanup.
|
||||
====
|
||||
endif::ibm-power-vs[]
|
||||
|
||||
|
||||
Reference in New Issue
Block a user