Skip to content

Commit fdfb3db

Browse files
authored
Example output of machine name should start with infrastructure_id
Example output of machine name should start with infrastructure_id not by <cluster_id>
1 parent 47200f9 commit fdfb3db

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

modules/cpmso-limitations.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,9 @@ $ oc get machine \
2525
[source,text]
2626
----
2727
NAME PHASE TYPE REGION ZONE AGE
28-
<cluster_id>-master-0 Running m6i.xlarge us-west-1 us-west-1a 5h19m
29-
<cluster_id>-master-1 Running m6i.xlarge us-west-1 us-west-1b 5h19m
30-
<cluster_id>-master-2 Running m6i.xlarge us-west-1 us-west-1a 5h19m
28+
<infrastructure_id>-master-0 Running m6i.xlarge us-west-1 us-west-1a 5h19m
29+
<infrastructure_id>-master-1 Running m6i.xlarge us-west-1 us-west-1b 5h19m
30+
<infrastructure_id>-master-2 Running m6i.xlarge us-west-1 us-west-1a 5h19m
3131
----
3232
+
3333
.Example output missing preexisting control plane machines
@@ -51,4 +51,4 @@ No resources found in openshift-machine-api namespace.
5151
Attempting to deploy control plane machines as AWS Spot Instances, GCP preemptible VMs, or Azure Spot VMs might cause the cluster to lose etcd quorum. A cluster that loses all control plane machines simultaneously is unrecoverable.
5252
====
5353
54-
* Making changes to the control plane machine set during or prior to installation is not supported. You must make any changes to the control plane machine set only after installation.
54+
* Making changes to the control plane machine set during or prior to installation is not supported. You must make any changes to the control plane machine set only after installation.

0 commit comments

Comments
 (0)