Bug 2043043 - Cluster Autoscaler should use K8s 1.23 dependencies
Summary: Cluster Autoscaler should use K8s 1.23 dependencies
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.0
Assignee: Mike Fedosin
QA Contact: sunzhaohua
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-20 14:24 UTC by Joel Speed
Modified: 2022-03-10 16:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:41:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift kubernetes-autoscaler pull 218 0 None open Bug 2043043: Rebase Autoscaler onto upstream release-1.23 branch 2022-01-20 14:25:46 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:41:37 UTC

Description Joel Speed 2022-01-20 14:24:37 UTC
We should be using the same client library version as the core of the openshift cluster and in particular the openshift and kube API servers

Comment 2 sunzhaohua 2022-01-21 06:47:40 UTC
Verified
clusterversion: 4.10.0-0.nightly-2022-01-20-225034
Run a regression testing for autoscaler cases on aws, all cases passed, --balance-similar-node-groups also works as expected. 
Test result: https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/ocp-common/job/Runner/283668/console

Comment 6 errata-xmlrpc 2022-03-10 16:41:21 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0056


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