Bug 1958766 - [DOCS] Clarify master node size limitation is only for IPI
Summary: [DOCS] Clarify master node size limitation is only for IPI
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.5
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: 4.5.z
Assignee: Sara Thomas
QA Contact: Xiaoli Tian
Vikram Goyal
URL:
Whiteboard:
Depends On: 1842424
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-10 06:28 UTC by Robert Sandu
Modified: 2022-04-07 06:46 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1842424
Environment:
Last Closed: 2021-06-15 15:40:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Robert Sandu 2021-05-10 06:28:00 UTC
+++ This bug was initially created as a clone of Bug #1842424 +++

NOTE: cloning as this request is still valid for RHOCP 4.6.z and higher.

Document URL: 

https://docs.openshift.com/container-platform/4.4/scalability_and_performance/recommended-host-practices.html#master-node-sizing_

Section Number and Name: 

Master node sizing

Describe the issue: 

Looks like the following description was written for IPI and changing instance type at IaaS layer. This description is confusing for UPI users.

> Because you cannot modify the master node size in a running OpenShift Container Platform 4.4 cluster, you must estimate your total node count and use the suggested master size during installation.

IN Baremetal UPI on vSphere, users can modify VM resource allocation without recreating the VM and increase the amount of CPU and/or memory.

Suggestions for improvement: 

Clearly state that this note is talking about IPI instance type change. It's not talking about the amount of resources change of VM.

Additional information:

--- Additional comment from Vikram Goyal on 2021-03-15 05:44:54 UTC ---

OCP 4.4 is EOL after OCP 4.7 GA.

This is a notification that this bug is being CLOSED as EOL as per the previous comment on this bug.

See my announcement email here [2].

If you have a customer case with a support exception or if you think this issue still applies on 4.5+, please reopen and include those details. When reopening, please change the reported version to 4.5+.

[1]: https://access.redhat.com/support/policy/updates/openshift
[2]: http://mailman-int.corp.redhat.com/archives/openshift-ccs/2021-February/msg00051.html

Comment 2 Sara Thomas 2021-05-19 20:38:11 UTC
@geliu , can you take a look at this for QA?

Comment 3 ge liu 2021-05-20 02:29:25 UTC
@jhou, I'm not sure if you may confirm this updates. thanks

Comment 4 Jianwei Hou 2021-05-31 01:50:35 UTC
The modification looks good


Note You need to log in before you can comment on or make changes to this bug.