Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1882728 - compact / 3-node cluster is not documented
Summary: compact / 3-node cluster is not documented
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Xiaoli Tian
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-25 13:04 UTC by Erik M Jacobs
Modified: 2021-04-19 20:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-19 20:27:16 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Erik M Jacobs 2020-09-25 13:04:34 UTC 
OpenShift 4.5 introduced support for "worker-less" / compact / 3-node clusters. The current documentation does not seem to document this anywhere. 

My understanding is that this installtion method is only supported for non-provider-integrated clusters, which the documentation refers to as "bare metal".

The current metal installation documentation specifies that 2 workers are required, and does not detail how to perform a worker-less installation or even that it's supported:

https://docs.openshift.com/container-platform/4.5/installing/installing_bare_metal/installing-bare-metal.html
Comment 4 Kathryn Alexander 2021-04-19 20:27:16 UTC 
This information was added after Erik filed the bug, and he's confirmed that the live version is acceptable: https://docs.openshift.com/container-platform/4.5/installing/installing_bare_metal/installing-bare-metal.html#installation-three-node-cluster_installing-bare-metal
Note You need to log in before you can comment on or make changes to this bug.