Bug 2019963 - Cluster autoscaler does not scale down due to not replicated pods
Summary: Cluster autoscaler does not scale down due to not replicated pods
Status: CLOSED DUPLICATE of bug 1927478
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Kevin Rizza
QA Contact: Jian Zhang
Depends On:
TreeView+ depends on / blocked
Reported: 2021-11-03 17:52 UTC by oarribas
Modified: 2022-03-16 18:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-11-29 18:58:19 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2053343 1 medium CLOSED Cluster Autoscaler not scaling down nodes which seem to qualify for scale-down 2023-09-18 04:31:53 UTC
Red Hat Knowledge Base (Solution) 6821651 0 None None None 2022-03-16 18:09:41 UTC

Description oarribas 2021-11-03 17:52:54 UTC
Description of problem:

Cluster autoscaler is not able to scale down with message:
node xxxxxxxx cannot be removed: openshift-marketplace/redhat-operators-xxxx is not replicated
node xxxxxxxx cannot be removed: openshift-marketplace/community-operators-xxxx is not replicated

Version-Release number of selected component (if applicable):

OCP 4.7

How reproducible:

When the node to be deleted has one of the `openshift-marketplace` pods running

Actual results:

Cluster autoscaler is not able to scale down.

Expected results:

Cluster autoscaler should be able to scale down.

Additional info:

It's expected behavior as [1], but the `openshift-marketplace` pods needs to configure the required annotation to be able to scale down the nodes if one of the pods are placed in the node selected to be removed.

[1] https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-types-of-pods-can-prevent-ca-from-removing-a-node

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