'KubeHpaMaxedOut' alert are continuously firing for 'noobaa-endpoint' when OCS 4.x is deployed on OCP v4.4 or above.
Environment
- OpenShift Container Platform 4.4 or above
- Red Hat OpenShift Container Storage 4.x
Issue
-
The following alert is seen after upgrading OCP to 4.4 or deploying a fresh OCS 4.x cluster on OCP 4.4 for
noobaa-endpoint
HPA `openshift-storage/noobaa-endpoint` has been running at max replicas for longer than 15 minutes.
Resolution
-
OCP provides the functionality of silencing the alerts in managing cluster alerts.
-
From the perspective of the OCS, this alert should be ignored. These alerts can be silenced to separate them from the list of active alerts.
-
This issue is being tracked in BZ #1836299
Root Cause
-
The Horizontal Pod Autoscaling(HPA) for the
noobaa-endpoint
pod is set toMAX=1
due to which alertKubeHpaMaxedOut
is seen fornoobaa-endpoint
. -
Autoscaling feature for the
noobaa-endpoint
pod is not available in Red Hat OpenShift Container Storage 4.3 and that is the reasonMAX HPA
value can not be greater than 1.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments