Bug 2043787 - Bump cluster-dns-operator to k8s.io/api 1.23
Summary: Bump cluster-dns-operator to k8s.io/api 1.23
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.0
Assignee: Miciah Dashiel Butler Masters
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-22 01:17 UTC by Miciah Dashiel Butler Masters
Modified: 2022-08-04 22:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:41:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-dns-operator pull 311 0 None open Bug 2043787: Bump to Kubernetes 1.23 and Go 1.17 2022-01-22 01:26:16 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:42:03 UTC

Description Miciah Dashiel Butler Masters 2022-01-22 01:17:24 UTC
Description of problem:

The DNS operator currently vendors Kubernetes 1.22 packages.  OpenShift 4.10 is based on Kubernetes 1.23.  


OpenShift release version:

4.10.


Steps to Reproduce (in detail):

1. Check <https://github.com/openshift/cluster-dns-operator/blob/release-4.10/go.mod>.


Actual results:

Kubernetes packages (k8s.io/api, k8s.io/apimachinery, and k8s.io/client-go) are at version v0.22.4.


Expected results:

Kubernetes packages are at version v0.23.0.


Impact of the problem:

Using old Kubernetes API and client packages brings risk of API compatibility issues.

Comment 3 Hongan Li 2022-01-27 08:13:21 UTC
Checked <https://github.com/openshift/cluster-dns-operator/blob/release-4.10/go.mod> and Kubernetes packages have been updated to version v0.23.0.

Verified with 4.10.0-0.nightly-2022-01-25-023600 and no regression issue.

Comment 6 errata-xmlrpc 2022-03-10 16:41:47 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.