Bug 1733523

Summary: [DOCS] No mention about adding Infrastructure node on bare metal UPI
Product: OpenShift Container Platform Reporter: Daein Park <dapark>
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: NEW --- QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 4.1.0CC: aos-bugs, jokerman, rbohne, rsandu, toshio.oya, wsun
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Daein Park 2019-07-26 11:32:36 UTC
Document URL: 

* Creating infrastructure MachineSets
    [ https://docs.openshift.com/container-platform/4.1/machine_management/creating-infrastructure-machinesets.html ]

Section Number and Name: 


Describe the issue: 

This section describing about adding Infrastructure node, but the target environment is only AWS.
v4.1 does not only support AWS IPI, but bare metal UPI, vSphere UPI, AWS UPI are also suppored.

Suggestions for improvement: 

Add same section with IPI for AWS for bare metal UPI, at least, we should provide configuration steps and explanation about how to configure infrastructure node in UPI. It's important for CU's subscription counting.

Additional information: 

User is usually considering to add infra node for logging, monitoring, ingress router components due to not counting as paid subscriptions.