-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.15, 4.16, 4.17, 4.18, 4.19, 4.20
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
Proposed
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The autoscaler is not considering nodepools in different zones as similar because it is not ignoring the topology.k8s.aws/zone-id label. This label is applied only to nodes created for HostedClusters, not self managed clusters.
Version-Release number of selected component (if applicable):
4.20
How reproducible:
Always
Steps to Reproduce:
1. Create an AWS hosted cluster with nodepools in different zones and autoscaling enabled. 2. Add workloads to cause autoscaling.
Actual results:
Nodes are not scaled evenly across zones
Expected results:
Nodes are scaled evenly across zones
Additional info:
The topology.k8s.aws/zone-id label is not being ignored by the autoscaler when considering similar nodegroups.
- account is impacted by
-
OCPSTRAT-2239 Hosted Clusters expose CAO's BalancingIgnoredLabels
-
- Release Pending
-