Bug 2087037 - Cluster Autoscaler should use K8s 1.24 dependencies
Summary: Cluster Autoscaler should use K8s 1.24 dependencies
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Mike Fedosin
QA Contact: sunzhaohua
Depends On:
TreeView+ depends on / blocked
Reported: 2022-05-17 07:58 UTC by Joel Speed
Modified: 2022-08-10 11:12 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-10 11:12:29 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift kubernetes-autoscaler pull 227 0 None open Bug 2087037: Rebase Autoscaler onto upstream release-1.24 branch 2022-05-25 14:38:41 UTC
Github openshift kubernetes-autoscaler pull 231 0 None open Bug 2087037: Rebase onto latest master from upstream 2022-05-31 15:35:20 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:12:45 UTC

Description Joel Speed 2022-05-17 07:58: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.

We also want to make sure that the repository is now using Go 1.18.

This bug should be completed by merging a rebase of the autoscaler repo

Comment 4 sunzhaohua 2022-06-09 06:53:23 UTC
Run regression test on IBM, clusterversion: 4.11.0-0.nightly-2022-06-06-201913 except balancesimilarnodegroup doesn't work, all other autoscaler cases works well, move this to Verified.
test run: https://polarion.engineering.redhat.com/polarion/#/project/OSE/testrun?id=20220607-0525

Comment 6 errata-xmlrpc 2022-08-10 11:12:29 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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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.


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