Bug 1996503 - Instance types with less than 8GB memory are listed in AWS UPI templates, but they do not meet memory minimum requirement for cluster
Summary: Instance types with less than 8GB memory are listed in AWS UPI templates, but...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.z
Assignee: Kelly Brown
QA Contact: Yunfei Jiang
Latha S
URL:
Whiteboard:
Depends On: 1996501
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-23 03:09 UTC by Yunfei Jiang
Modified: 2021-12-02 19:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1996501
Environment:
Last Closed: 2021-12-02 19:33:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yunfei Jiang 2021-08-23 03:09:04 UTC
+++ This bug was initially created as a clone of Bug #1996501 +++

Workers with less than 8GB memory can not meet cluster install for minimum requirement (8G at least, https://github.com/openshift/installer/pull/4258), they should be removed from UPI templates:
c4.large 3840MB
c5.large 4096MB
c5a.large 4096MB
c4.xlarge 7680MB

Workers with less than 4GB memory will cause monitor operator degraded:

Events:
  Type     Reason            Age   From               Message
  ----     ------            ----  ----               -------
  Warning  FailedScheduling  19h   default-scheduler  0/5 nodes are available: 2 Insufficient memory, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.


NAME                                       VERSION                             AVAILABLE   PROGRESSING   DEGRADED   SINCE
authentication                             4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
baremetal                                  4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
cloud-credential                           4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
cluster-autoscaler                         4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
config-operator                            4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
console                                    4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
csi-snapshot-controller                    4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
dns                                        4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
etcd                                       4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
image-registry                             4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
ingress                                    4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
insights                                   4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
kube-apiserver                             4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
kube-controller-manager                    4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
kube-scheduler                             4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
kube-storage-version-migrator              4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
machine-api                                4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
machine-approver                           4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
machine-config                             4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
marketplace                                4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
monitoring                                                                     False       True          True       19h
network                                    4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
node-tuning                                4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
openshift-apiserver                        4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
openshift-controller-manager               4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
openshift-samples                          4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
operator-lifecycle-manager                 4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
operator-lifecycle-manager-catalog         4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
operator-lifecycle-manager-packageserver   4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
service-ca                                 4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h
storage                                    4.8.0-0.nightly-2021-08-12-174317   True        False         False      19h


Version:
OCP: 4.6+

Platform:
UPI on AWS

How to reproduce it (as minimally and precisely as possible)?
Setting worker instance with 4GB memory, e.g. c4.large, and install an OCP cluster

Comment 3 Kelly Brown 2021-12-01 19:21:40 UTC
PR for changes: https://github.com/openshift/openshift-docs/pull/39448


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