Skip to content

Commit

Permalink
Minor edits recommended during review
Browse files Browse the repository at this point in the history
  • Loading branch information
@manojnkumar
manojnkumar committed Apr 23, 2020
1 parent bdf803f commit 5125fb7
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs/user/power/install_upi.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -20,15 +20,15 @@ The steps for performing a UPI-based install are outlined here. Example automati

## Compute

The smallest OpenShift 4.x clusters require the following host:
The smallest OpenShift 4.x cluster requires the following hosts:

* 1 bootstrap machine.

* 3 control plane machines.

* atleast 1 worker machine.
* 2 worker machines.

NOTE: The cluster requires the bootstrap machine to deploy the OpenShift cluster on to the 3 control plane machines, and you can remove the bootstrap machine.
NOTE: The cluster requires the bootstrap machine to deploy the OpenShift cluster on to the 3 control plane machines. Once the installation completes you can remove the bootstrap machine.

All the machines must use Red Hat Enterprise Linux CoreOS (RHCOS) as the operating system.

Expand All @@ -45,7 +45,7 @@ All the machines must use Red Hat Enterprise Linux CoreOS (RHCOS) as the operati
## Network Topology Requirements

The easiest way to get started is to ensure all Power nodes have internet access to pull images for platform containers and provide telemetry data to Red Hat.
OpenShift 4.x also supports air-gapped installs
OpenShift 4.x also supports a restricted network installation.

### Load balancers

Expand Down Expand Up @@ -215,7 +215,7 @@ INFO Waiting up to 30m0s for bootstrapping to complete...
### Configure Image Registry Storage Provisioner


The Cluster Image Registry [Operator][cluster-image-registry-operator] does not pick an storage backend for `None` platform. Therefore, the cluster operator will be stuck in progressing because it is waiting for the administrator to [configure][cluster-image-registry-operator-configuration] a storage backend for the image-registry.
The Cluster Image Registry [Operator][cluster-image-registry-operator] does not pick a storage backend for `None` platform. Therefore, the cluster operator will be stuck in progressing because it is waiting for the administrator to [configure][cluster-image-registry-operator-configuration] a storage backend for the image-registry.
[NFS][openshift-nfs] should be picked as a [storage-backend][nfs-storage-backend].


Expand Down

0 comments on commit 5125fb7

Please sign in to comment.